Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add defined check for plugin_parent_dir resource #155

Closed
wants to merge 1 commit into from

Conversation

dbeckham
Copy link
Contributor

The management of the basic dependencies of a Jenkins plugin should not
be unnecessarily forced on the user. This change wraps the plugin_parent_dir
resource creation in a defined function to allow the user to create the
Jenkins home directory themselves if necessary.

The use case for this would be a simple symbolic link resource that would link
the default /var/lib/jenkins parent directory to another location for storage
space, or other system reasons.

This fixes #148 in a more backwards compatible way than #149.

The management of the basic dependencies of a Jenkins plugin should not
be unnecessarily forced on the user. This change wraps the plugin_parent_dir
resource creation in a `defined` function to allow the user to create the
Jenkins home directory themselves if necessary.

This fixes voxpupuli#148 in a more backwards compatible way than voxpupuli#149.
@jenkinsadmin
Copy link

Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests

@rtyler rtyler closed this in 4774a5b Sep 24, 2014
@rtyler rtyler added this to the 1.2.0: Nestor milestone Sep 24, 2014
@dbeckham dbeckham deleted the plugin_parent_dir_fix branch March 24, 2015 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Install a plugin should not prevent jenkins home to be a symlink
3 participants