Since we're offering a source package along with the other artefacts for our Releases, it would make sense to have Try coverage for that. Without this, making any trivial change to the source-package step of the build process is risky (see bug 1338099). (In reply to Ted Mielczarek [:ted.mielczarek] from bug 1338099 comment #36) > While looking into something else today I found myself looking at the > build+release tasks for 53.0b6. The source package task is defined here > currently: > https://github.com/mozilla/releasetasks/blob/master/releasetasks/templates/ > firefox/source.yml.tmpl > > I asked rail on IRC if we could move that into m-c so we could trigger it on > try and he indicated that the only thing stopping it was someone finding > time to do it.
:rail, can you add any additional information about how to do this?
Thanks for filing this! The existing TC build uses the same build image and script we would use for regular linux builds. It's just the matter of passing proper parameters. https://github.com/mozilla/releasetasks/blob/master/releasetasks/templates/firefox/source.yml.tmpl#L45 is what we use for release builds. MOZHARNESS_ACTIONS, MOZHARNESS_SCRIPT and MOZHARNESS_CONFIG are the ones we would need to port to existing build types in https://dxr.mozilla.org/mozilla-central/source/taskcluster/ci/build/linux.yml Something like https://gist.github.com/rail/3d0ba5e8003ff89cb99131a77b63f2a6 may work. Probably we would need to play with something to make this enabled on try either by default or optional. I hope this helps.
Note to self: bug 1341404 contains some useful info about how to do that.
You need to log in before you can comment on or make changes to this bug.