upstream merger hooks do not propagate to downstream jobs' builder_hooks
Bug #1255948 reported by
Michał Sawicz
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Services |
Confirmed
|
Undecided
|
Francis Ginther |
Bug Description
When you change the hooks parameter for a -ci or -autolanding job, that does not propagate to builder_hooks of downstream jobs.
Case at hand:
http://
summary: |
- upstream merger hooks do not propagate to child jobs' builder_hooks + upstream merger hooks do not propagate to downstream jobs' builder_hooks |
Changed in ubuntu-ci-services-itself: | |
assignee: | nobody → Francis Ginther (fginther) |
Changed in ubuntu-ci-services-itself: | |
status: | New → Confirmed |
To post a comment you must log in.
Unfortunately, this is intentional. This used to work as described but we had to change the behavior due to https:/ /bugs.launchpad .net/cupstream2 distro- config/ +bug/1168745.
Essentially we wanted to specify different hook configurations for different builds. An example would be to skip the code coverage hook for armhf builds, allowing the build to complete faster. When there was only one parameter for "hooks" all jobs always inherited from the parent job and there was no way to customize the child jobs as needed.
Given this background, is there still a case for this to be a bug? Beyond running an experiment on a specific build, is there a use case I'm missing?