Branch workflows now include not just unit tests but integration tests using Docker Compositions

[nutjob4life]

🗒️ Summary

Merge this to resolve #269 which adds a full integration test to the branch-triggered workflow.

⚙️ Test Data and/or Report

You can see a run of this in the sandbox. Yes, the run is "in the red", but that's because integration tests currently have 34 failed assertions. Successful exposition!

♻️ Related Issues

• Add registry/docker compose integration tests to github action on dev branches #269

[sonatype-lift]

Sonatype Lift is retiring

Sonatype Lift will be retiring on Sep 12, 2023, with its analysis stopping on Aug 12, 2023. We understand that this news may come as a disappointment, and Sonatype is committed to helping you transition off it seamlessly. If you’d like to retain your data, please export your issues from the web console.
We are extremely grateful and thank you for your support over the years.

📖 Read about the impacts and timeline

[alexdunnjpl]

LGTM!

Now we just have to get around to resolving those failing tests 🥲

[alexdunnjpl]

@nutjob4life actually, real-talk, would it be viable to have that as a separate stage? If only so that unit-test regressions don't get ignored because "BIT/BT always fails now".

[nutjob4life]

LGTM!

Now we just have to get around to resolving those failing tests 🥲

Sooo faaast @alexdunnjpl! 🏎▁▂▃▄▅▆▆▇▇██💨

[nutjob4life]

@nutjob4life actually, real-talk, would it be viable to have that as a separate stage? If only so that unit-test regressions don't get ignored because "BIT/BT always fails now".

Absolutely, @alexdunnjpl

[alexdunnjpl]

Just saw that comment/link after missing it the first time.

@jordanpadams your thoughts on the above? Should I open a ticket for it?

[jordanpadams]

@alexdunnjpl See #397 comments