Using build image on all the generated builders on the acceptance/integration tests

pacostas commented 4 months ago

Related issue

Summary

On each release we ship one builder image and multiple run images despite we generate from the create.sh script multiple build.oci images one for each engine, majorVersion. Therefor On our integration/acceptance tests, is uneccesary to test all the build.oci images located under each build-<engine>-<majorVersion> as we:

dont ship them on any container registry or on the release assets
They dont participate on the build process when we build an app, as the builder uses only the one that is pushed on the container registry/release assets https://github.com/paketo-community/builder-ubi-base/blob/47a0a253e7429b1145cef1e35c9eb5aef87c0dc7/builder.toml#L74

Use Cases

This PR alters the function utils.GenerateBuilder to always point the builder image to build/build.oci

Checklist

[x] I have viewed, signed, and submitted the Contributor License Agreement.
[x] I have linked issue(s) that this PR should close using keywords or the Github UI (See docs)
[x] I have added an integration test, if necessary.
[x] I have reviewed the styleguide for guidance on my code quality.
[x] I'm happy with the commit history on this PR (I have rebased/squashed as needed).

pacostas commented 4 months ago

Acceptance workflow has been tested here https://github.com/pacostas/ubi-base-stack/actions/runs/8081169572/job/22079462874

pacostas commented 4 months ago

pushed wrong branch

paketo-community / ubi-base-stack