Mark some builds as optional for `integration_test.yaml`

[DnPlas]

This workflow's automated logic works perfectly fine for when a repository has a charm, a rock, and(or) a Dockerfile that has to be always built and in some cases uploaded as an artefact or published, but we are working under the assumption that that's always the case. In some cases (see temporal-worker), where we have a rockcraft project that can be used as a guide/example, we definitely do not want to build and publish this image to any registry.

AFAICT (according to this guide), there is no option to prevent this from happening, but it would definitely be a great addition.

[arturo-seijas]

Hi @DnPlas ,
If I understand correctly, you want to be able to opt-out from publishing artifacts? In the use case you mention I see value in building the example to make sure it's working, but perhaps you are thinking about opting-out from building them altogether

[syncronize-issues-to-jira]

Thank you for reporting your feedback to us!

The internal ticket has been created: https://warthogs.atlassian.net/browse/ISD-4045.

This message was autogenerated

[DnPlas]

I agree that there is value in building and publishing, but teams may want to opt-out from doing so, and the workflow should provide means to do it. We can leave the decision to the teams, the default can be build and publish, if that's desired.