Contains also changes to support libtaskotron 0.4.0 in non-disposable mode.
Details
- Reviewers
tflink - Maniphest Tasks
- T633: Upgrade buildslave and buildslave-configure ansible roles to handle multiple slaves per host
Did some testing with allinone deployment on my laptop but not everything was covered. I guess deploying to dev is a test plan :)
Diff Detail
- Lint
Lint Skipped - Unit
Unit Tests Skipped
A couple of minor concerns but looks pretty good to me, overall.
roles/taskotron/buildmaster-configure/templates/taskotron.master.cfg.j2 | ||
---|---|---|
155 | Don't those %(prop:slavenam)s need to be wrapped in Interpolate instead of used as part of a raw string? | |
199 | If we have multiple buildslaves on the same host, i think this step will cause problems. I wonder if we need to separate out the tmpdirs per-user like we did for the log files | |
roles/taskotron/buildslave/tasks/main.yml | ||
40 | I think we should add the homedir here as well. It's not needed at the moment but enough stuff has been moved around on the master to deal with disk space issues, I'd rather be prepared since we're specifying the homedir in inventory, anyways |
changes look good to me but I caught something new this time around
roles/taskotron/buildslave-configure/tasks/main.yml | ||
---|---|---|
49 | i didn't catch this before but this is not a wise thing to do - that /etc/ssh/ssh_known_hosts is controlled elsewhere by ansible - changing it would end up with a war between the two tasks. why not continue to use the user's .ssh/known_hosts file? |
I just realized that we also write directly into taskotron.log in artifactsdir so I changed master.cfg to reflect that.
I agree that the conditionals around "is dev" or "is not dev" is kinda ugly but I can't think of other reasonable options. We'll just have to remove them once this is all deployed to prod
Don't those %(prop:slavenam)s need to be wrapped in Interpolate instead of used as part of a raw string?