[DNM] test ci

[elfosardo]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[metal3-io-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please ask for approval from elfosardo. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[elfosardo]

/test-ubuntu-integration-main

[elfosardo]

/markdownlint

[elfosardo]

/test-ubuntu-integration-main

[elfosardo]

/test-ubuntu-integration-main

[tuminoid]

/test-ubuntu-integration-main
//test-centos-integration-main

[tuminoid]

/test-centos-integration-main

[tuminoid]

/test-ubuntu-integration-main
/test-centos-integration-main

[tuminoid]

/test-ubuntu-integration-main
/test-centos-integration-main

[tuminoid]

/test-ubuntu-integration-main
/test-centos-integration-main

[tuminoid]

/test-ubuntu-integration-main
/test-centos-integration-main

[kashifest]

the triggers doesnt look correct, we using main branch test trigger here, perhaps we should use the correct branch name. Let me check if everything is up to date in gerrit repo

[kashifest]

/test-ironic-image-build

[kashifest]

ok it seems like we do not have the logic to test the release branches yet , cause for that we have to decide which branch of BMO we should test for a given ironic release branch, currently we run these integration tests based on CAPM3 branches and CAPM3 and BMO branches are coupled together for the integration tests (we should change this), we can also use BMO e2e tests here but then again we need to know for which branch of BMO we should test which branch of ironic!!! the
ironic-image-build pipeline is another thing that we can leverage, currently its only building ironic image and that also from rpm for some legacy reason, we can perhaps improve this and add options to test integration of different ironic image branches with BMO/CAPM3.