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

jenkins user and jenkins_home directory not configurable #365

Closed
omar952 opened this issue Sep 3, 2015 · 1 comment · Fixed by #396
Closed

jenkins user and jenkins_home directory not configurable #365

omar952 opened this issue Sep 3, 2015 · 1 comment · Fixed by #396
Labels
enhancement New feature or request
Milestone

Comments

@omar952
Copy link

omar952 commented Sep 3, 2015

Hi,

It seems that the jenkins main manifest to install jenkins master, creates a OS level user named "jenkins" with a home directory of "/var/lib/jenkins". The OS user and home directory are not configurable. I believe this has been done because the yum package to install Jenkins, always installs the master to the /var/lib/jenkins directory.

In my scenario, I have a jenkins user that I have created myself prior to running this manifest which has a home directory of /home/jenkins. Jenkins master is still installed in /var/lib/jenkins, however, this means that jenkins plugins are reinstalled everytime the puppet script is run, as lib/puppet/jenkins.rb always looks in "~jenkins" to find the plugins directory, which in my case does not exist.

My change request would be to allow the OS user and its home directory, as well as the Jenkins home directory to be configurable, so that these can be set by the module user.

Thanks

@tstibbs
Copy link
Contributor

tstibbs commented Sep 4, 2015

Note that afaics if installing on something that uses RPMs (CentOS in my case), jenkins always gets installed into /var/lib/jenkins, regardless of what you set in puppet. So in this case (i.e. on a rhel derivative) jenkins.rb is simply wrong, it should just look in /var/lib/jenkins.

@jhoblitt jhoblitt added the enhancement New feature or request label Oct 11, 2015
@jhoblitt jhoblitt added this to the 1.6.0 - Kato milestone Oct 11, 2015
jhoblitt added a commit to jhoblitt/puppet-jenkins that referenced this issue Oct 11, 2015
* add `manager_user`, `user`, `manage_group`, `group` params to
  `jenkins` class.

* improve consistency of `file` resouce group ownership throughout
  the module

* add 'localstatedir' param to `jenkins` class and consistently use it
  to set the 'data' base dir throughout the module

* Deprecate/noop `username`, `group`, `create_user` params to
  `jenkins::plugin` define; replaced by `user`,`group`,etc. params to
  `jenkins` class

* Deprecate/noop `plugin_dir` param to `jenkins::plugin`; replaced by
  `localstatedir` param to `jenkins` class

closes voxpupuli#356 -- alternative approach
resolves voxpupuli#365
jhoblitt added a commit to jhoblitt/puppet-jenkins that referenced this issue Oct 11, 2015
* add `manager_user`, `user`, `manage_group`, `group` params to
  `jenkins` class.

* improve consistency of `file` resouce group ownership throughout
  the module

* add 'localstatedir' param to `jenkins` class and consistently use it
  to set the 'data' base dir throughout the module

* Deprecate/noop `username`, `group`, `create_user` params to
  `jenkins::plugin` define; replaced by `user`,`group`,etc. params to
  `jenkins` class

* Deprecate/noop `plugin_dir` param to `jenkins::plugin`; replaced by
  `localstatedir` param to `jenkins` class

closes voxpupuli#356 -- alternative approach
resolves voxpupuli#362
resolves voxpupuli#365
jhoblitt added a commit to jhoblitt/puppet-jenkins that referenced this issue Oct 12, 2015
* add `manager_user`, `user`, `manage_group`, `group` params to
  `jenkins` class.

* improve consistency of `file` resouce group ownership throughout
  the module

* add 'localstatedir' param to `jenkins` class and consistently use it
  to set the 'data' base dir throughout the module

* Deprecate/noop `username`, `group`, `create_user` params to
  `jenkins::plugin` define; replaced by `user`,`group`,etc. params to
  `jenkins` class

* Deprecate/noop `plugin_dir` param to `jenkins::plugin`; replaced by
  `localstatedir` param to `jenkins` class

closes voxpupuli#356 -- alternative approach
resolves voxpupuli#362
resolves voxpupuli#365
resolves voxpupuli#219
jhoblitt added a commit to jhoblitt/puppet-jenkins that referenced this issue Oct 12, 2015
* add `manager_user`, `user`, `manage_group`, `group` params to
  `jenkins` class.

* improve consistency of `file` resouce group ownership throughout
  the module

* add 'localstatedir' param to `jenkins` class and consistently use it
  to set the 'data' base dir throughout the module

* Deprecate/noop `username`, `group`, `create_user` params to
  `jenkins::plugin` define; replaced by `user`,`group`,etc. params to
  `jenkins` class

* Deprecate/noop `plugin_dir` param to `jenkins::plugin`; replaced by
  `localstatedir` param to `jenkins` class

closes voxpupuli#356 -- alternative approach
resolves voxpupuli#362
resolves voxpupuli#365
resolves voxpupuli#219
resolves voxpupuli#249
jhoblitt added a commit to jhoblitt/puppet-jenkins that referenced this issue Oct 12, 2015
* add `manager_user`, `user`, `manage_group`, `group` params to
  `jenkins` class.

* improve consistency of `file` resouce group ownership throughout
  the module

* add 'localstatedir' param to `jenkins` class and consistently use it
  to set the 'data' base dir throughout the module

* Deprecate/noop `username`, `group`, `create_user` params to
  `jenkins::plugin` define; replaced by `user`,`group`,etc. params to
  `jenkins` class

* Deprecate/noop `plugin_dir` param to `jenkins::plugin`; replaced by
  `localstatedir` param to `jenkins` class

closes voxpupuli#356 -- alternative approach
resolves voxpupuli#362
resolves voxpupuli#365
resolves voxpupuli#219
resolves voxpupuli#249
resolves voxpupuli#250
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants