Merge lp:~gandelman-a/charms/precise/jenkins-slave/extension_executors into lp:charms/jenkins-slave
Proposed by
Adam Gandelman
Status: | Work in progress |
---|---|
Proposed branch: | lp:~gandelman-a/charms/precise/jenkins-slave/extension_executors |
Merge into: | lp:charms/jenkins-slave |
Diff against target: |
48 lines (+15/-2) 4 files modified
config.yaml (+3/-0) hooks/slave-relation-joined (+6/-1) metadata.yaml (+5/-0) revision (+1/-1) |
To merge this branch: | bzr merge lp:~gandelman-a/charms/precise/jenkins-slave/extension_executors |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Review Queue (community) | cbt | Needs Fixing | |
Adam Israel (community) | Needs Fixing | ||
James Page | Pending | ||
Review via email: mp+191744@code.launchpad.net |
Description of the change
* Allows the # of executors to be configurable, defaulting to # of cores
* Adds the jenkins extenions interface, much like the master charm. This allows custom subordinates to be associated with the slaves and reduces the need to fork the main principle charm.
To post a comment you must log in.
Unmerged revisions
- 12. By Adam Gandelman
-
Fix inspection of config.
- 11. By Adam Gandelman
-
Add jenkins-extension interface and make # executors configurable.
Hey Adam, thanks for the charm contribution and apologies for the delay in review. I took a look at the charm and ran into a few issues.
The initial charm proof didn't run cleanly, so I fixed those issues and continued on.
I deployed jenkins and jenkins-slave per the README, and added the relation between the news.
Once the relation is joined, changes to to the charm's executors config setting do not trigger jenkins master- relation- changed, where jenkins gets the value from the relation, like I would expect.
I then noticed that the executor count determined in slave-relation- joined isn't reflected back in the charm's config, so if a user is working with the juju gui, they don't see that value.
But -- if I destroyed the relation and manually set the executors to 3 (through juju GUI) and then added the relation, jenkins node configuration UI showed 6 executors.
Some of this may be expected behavior to someone more familiar with Jenkins. If so, it would be good to add these kind of caveats to the README.
Here's my branch, for reference:
lp:~aisrael/charms/precise/jenkins-slave/fix-extensions-executors
If you have any questions/ comments/ concerns about the review contact us in #juju on irc.freenode.net or email the mailing list <email address hidden>, or ask a question tagged with "juju" on http:// askubuntu. com.