-
Notifications
You must be signed in to change notification settings - Fork 565
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
Feature/puppet helper num executors #260
Feature/puppet helper num executors #260
Conversation
jhoblitt
commented
Mar 26, 2015
- add get_num_executors()/set_num_executors() methods to puppet_helper
- add jenkins::cli::exec defined type
- add executors param to jenkins class
I ended up making a fair number of minor house keeping changes while working on this branch so I've split them out as separate commits and moved them to the beginning of the patch series. I would be happy to submit them as a separate PR, if requested. I had some difficulty choosing a description name for the new defined type. I originally called it As One of my intents for |
3de868f
to
b0953c6
Compare
It looks like my local bundle was in a funny state. The travis build failed as some forward porting is required for rspec > 3. |
f869b46
to
6f3ef22
Compare
Thank you for a pull request! Please check this document for how the Jenkins project handles pull requests |
The build failed due to puppet 3.5.0/ruby 1.9.3 and I suspect Travis gltiched. I can't manually restart the build myself so I'll push some sort of whitespace change to kick it.
|
6f3ef22
to
5382627
Compare
gem 'rspec-its' | ||
gem 'puppet-lint', '>= 0.3.2' | ||
gem 'rspec-puppet', '>= 1.0.1' | ||
gem 'puppetlabs_spec_helper', :github => 'jenkins-infra/puppetlabs_spec_helper' | ||
gem 'puppetlabs_spec_helper', :require => false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why was the jenkins-infra fork of the spec helper removed here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't recall specifically what it was breaking for me at the time, likely beaker, but 0.10.2 is needed for future parser/puppet 4.0.0 anyways.
@rtyler I'd be happy to split out the house keeping changes as a separate PR if that would help get them merged. I have a fairly substantially amount on work in this module that I'm not quite ready to break up into PRs and feed back yet but it all needs the basic house keeping so unit/acceptance testing works. |
5a6c4d5
to
78c350e
Compare
@rtyler My working branch is now over 70 commits and 3000 lines added ahead of your master. I'd really like to get some of these small house keeping commits merged as they will be common to any feature branches I split with a clean history for a PR. I have broken 11 commits out from this branch as individual PRs. #270 #271 #272 #273 #274 #275 #276 #277 #278 #279 #280 |
@jhoblitt all merged up, thanks for the house cleaning! I think this change can be merged once it's rebased atop the newest master |
78c350e
to
f693e20
Compare
These methods may be used to get/set the number of executors for the master. Eg.: java -jar /usr/lib/jenkins/jenkins-cli.jar -s http://localhost:8080 groovy /usr/lib/jenkins/puppet_helper.groovy get_num_executors java -jar /usr/lib/jenkins/jenkins-cli.jar -s http://localhost:8080 groovy /usr/lib/jenkins/puppet_helper.groovy set_num_executors 42
Due to resource containment, it was not possible for a consumer of `jenkins::cli` to both have a dependency on `Class['jenkins::cli']` and to notify `Exec['reload-jenkins']`. It is recommended that notifications be instead be sent to `Class['jenkins::cli::reload']` to ease any future refactoring.
Similar semantics as `class { 'jenkins::slave': executors => ... }` but for the Jenkins master.
f693e20
to
f6ebc21
Compare
@rtyler thanks for the merge campaign! I've rebased on the current master. |
…tors Feature/puppet helper num executors