jenkinsci/jenkins.rb

[FEATURE] Allow project-specific `jenkinsrb-config.json`

Opened this issue · 2 comments

I'm looking to package up a repo that will give collaborators everything they need to spin up a CI infrastructure in the cloud (for developing with the Drupal CMS). In theory, it will makes sense to have one per project.

Do you see value in this?

What would you think about checking an ENV variable called JENKINSRB_HOME before falling back on HOME?
https://github.com/jenkinsci/jenkins.rb/blob/master/ruby-tools/cli/lib/jenkins/config.rb#L24

Or is there a better way you'd rather I approach it from?

Thanks for hearing me out!

That works for me. Also, could pass as a command line option.

Not working on this yet, but will probably take the path of recursing back looking for the first .jenkins/, then defaulting to $HOME/.jenkins/ if nothing found.