Feature #6196: Build all active branches
Deploy our Puppet recipes for Jenkins from scratch
The objective is to have our current Jenkins setup easy to replicate and document on how to do so.
#8 Updated by Dr_Whax about 5 years ago
We're thinking of adding this to the following page: https://tails.boum.org/contribute/working_together/roles/sysadmins/
Or do we want another page for this? /roles/ci-team/ ?
#14 Updated by intrigeri about 5 years ago
I put done to 100%. I can't choose the status with resolved, only with fix committed.
... because this ticket is marked as blocked by #6922, which has Confirmed status. Given that you apparently managed to resolve #8636 without #6922 being fixed first, that relationship seems to be buggy. So please delete it and close this ticket, otherwise we'll be twisting Redmine semantics in confusing way.
#15 Updated by bertagaz about 5 years ago
- % Done changed from 100 to 80
I believe we haven't really finished this task, we still have one final last step to have this deployment in a working state (deploying a local Tails git clone and hook it into jenkins to trigger builds on changes).
Regarding #6922, the relationship between the 2 tickets makes sense. It is being worked on, but I'm unsure of when it will be finished, in the coming week if everything goes fine.
This tickets are not really blockers for the 1.3 release anyway, this milestone was mainly there to be an indication and they can be delayed a bit.
#21 Updated by intrigeri almost 5 years ago
Alright, we have a build working. If the build finishes successfully, I declare this ticket as resolved.
Good, it means that our Puppet stuff is starting to be good enough that one can replicate it given enough hand-holding!
Hence, I don't see why this ticket could be marked as resolved yet, for the same reasons that we discussed two weeks ago on this very ticket. Did I miss anything?
(Details: my understanding of the relationship between this ticket and #6922 (that I asked to be clarified 2 weeks ago, and then bertagaz confirmed to make sense in #8636#note-15) is that the idea was to write doc (#6922), and then use this from scratch deployment (#8636) to validate both the doc and the Puppet code. So, it seems that we've now validated the Puppet bits, but not the doc yet -- since it doesn't exist.)