Closed j-rivero closed 9 months ago
Are all the abichecker jobs using the
gz
prefix now? > I seeign_*.xml
files in/tmp/pr_xml_configuration
, so I wasn't sure.
The names are using the lib names defined in the yaml file. Citadel is using the ign- prefix but all others are using the gz- now.
Also, I'm seeing abi jobs for each platform (e.g.
gz_sim-abichecker-any_to_any-ubuntu-focal-amd64.xml
,gz_sim-abichecker-any_to_any-ubuntu-jammy-amd64.xml
). I think we only need one.
Good catch. To workaround this, I've excluded manually the libs in the yaml file in d996eb9 and added a CI test for it. I would prefer to solve this in a declarative way instead of coding a hidden solver for it. The rest of jobs listed here that runs on different platforms they are supporting different branches should be fine and needed to have them.
Log is a mix of tabs diffs (introduce quite a lot of noise but the change needed was a bug fix), legitim old jobs change configuration and reports of new jobs present only in the PR. Can not find anything abnormal.
Looking at the trigger branches, for example in gz_transport-abichecker-...focal-amd.xml
, I see
<whiteListTargetBranches>
<org.jenkinsci.plugins.ghprb.GhprbBranch>
<branch>gz-transport11</branch>
</org.jenkinsci.plugins.ghprb.GhprbBranch>
<org.jenkinsci.plugins.ghprb.GhprbBranch>
<branch>gz-transport12</branch>
</org.jenkinsci.plugins.ghprb.GhprbBranch>
</whiteListTargetBranches>
But the gz-transport11
branch doesn't exist on github. It should be ign-transport11
.
But the
gz-transport11
branch doesn't exist on github. It should beign-transport11
.
Should be fixed by #1040
Modify the abichecker job generation to use the new static configuration. Steps done:
Diff from existing gz-physics-abichecker (focal) to the new one (jammy):