for release promotion with taskcluster
Created attachment 8835137 [details] [diff] [review] wip patch not sure if the beetmover bits should be tied in at this point too
Created attachment 8835511 [details] [diff] [review] wip patch https://public-artifacts.taskcluster.net/Mb6D-h2aSUKpn5ds7vTkSw/0/public/full-task-graph.json Not sure if this is the right approach, if this job should be under android builds or included in another kind
Created attachment 8835547 [details] [diff] [review] wip patch no sure if this is on the right track or if the source tarball should be included in another kind
Comment on attachment 8835547 [details] [diff] [review] wip patch Review of attachment 8835547 [details] [diff] [review]: ----------------------------------------------------------------- Oooooh! This looks much fancier that https://github.com/mozilla/releasetasks/blob/master/releasetasks/templates/firefox/source.yml.tmpl! Initially I thought about implementing this task the same way as Firefox (in releasetasks). But this looks much cleaner... On the other hand generating source tarballs for every CI build is a bit a waste of time and space. If we can limit these only to nightly style graphs, that would be great!
Created attachment 8835683 [details] [review] pull request
Rail could you look at my PR and provide feedback?
Rail, I committed some more changes to the PR, ran the tests locally and they all passed https://github.com/mozilla/releasetasks/pull/213
rail let me know if I'm missing anything in the updated pr
Created attachment 8840622 [details] [review] includes work for bug 1338161
The PR looks good to me. Thanks!
So looking at the tasks associated with the candidates_fennec hook that aki added last night, I don't see the source tarball task. https://bugzilla.mozilla.org/show_bug.cgi?id=1338161#c2 https://tools.taskcluster.net/task-group-inspector/#/QQjEh3q1TOu2liv57iHawg?_k=xa1zb8 Is this expected or should it be included when we run releasetasks but not against the graph on jamun?
IIRC, what we discussed in Toronto was: 1) we trigger releasetasks. this can do things like tagging (skip?) and source tarball 2) releasetasks triggers a candidates_fennec type graph for fennec. this is essentially like the hook, except it populates things like build_number automatically so the graph i triggered was (2), though manually triggered instead of through releasetasks. Aiui, bug 1338161 was about adding a decision task to releaserunner that would trigger (2), so triggering releaserunner would trigger both the source tarball and the build. The way things stand currently , releaserunner will trigger the source tarball, and releaseduty will then have to trigger the candidates_fennec manually after manually updating the build_number etc.
Okay, thanks aki, that clarifies it.