Closed mikaelarguedas closed 6 years ago
Yeah, we've been knowingly living with the catchall behavior. But it would be cleaner to be able to trigger only the default buildfile contents, and not chain to the alternative build targets. But so far we're triggering both simultaneously so it doesn't really make a difference.
One other approach would be to have one job per target, and a meta job per buildfile that will just trigger the target specific jobs.
Noticed this recently when triggering
Brel_trigger-broken-with-non-broken-upstream
also triggered the arm jobs makingBrel_ubv8_trigger-broken-with-non-broken-upstream
ineffective.The issue comes from the fact that we use the view prefix to match the jobs to retrigger.
While the view prefix returns the a specific enough prefix for arm platforms:
It returns only a very generic prefix when using the default build file:
A more specific prefix can be used but is specific to a single target of the build file
We could solve this in several ways, but it depends what is the expected set of job and behaviors we expect (I'll use melodic as an example).
Mrel_trigger-broken-with-non-broken-upstream
is a "catchall" job that triggers all jobs including the ones generated by other build filesMrel_trigger-broken-with-non-broken-upstream
should trigger only the jobs defined in thedefault
build file:Mbin_uA64
,Mbin_uB64
) and modify _get_trigger_broken_with_non_broken_upstream_job_config to return the list of all prefixes generated with the provided build file.