You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current state comprises the only remaining snowflake aspect and is particularly relevant due to our EC2 spot instance usage - it should be addressed accordingly. Given Git is to be considered a precondition for pretty much everything in (our) software development these days, and is readily available on the master, I vote to include it directly via BOSH.
The only argument to the contrary would be more control over the Git versions, but this can optionally still be done, and conversely unqualified jobs might get executed on either the master or the slave, thus it seems reasonable to use the same Git version in both scenarios. Our Windows slave comes with Git readily installed too btw. (baked into the AMI).
Whether jobs can be executed on both master and slave depends on the setup of course, but our current one allows this (even though I'm not a fan of using the master for actual builds).
git
is packaged and installed on the master node as a dependancy of thejenkins_master job
This is not the case for the slave nodes, so attempting to use git on a slave fails with:
The question is, who is responsible for installing git on the slaves? BOSH (as above), or Jenkins?
The text was updated successfully, but these errors were encountered: