ci: optimize build-verify.yml workflow#1499
Conversation
|
Welcome to the Microcks community! 💖 Thanks and congrats 🎉 for opening your first pull request here! Be sure to follow the pull request template or please update it accordingly. Hope you have a great time there! 🌟 ~~~~~~~~~ 🌟 📢 If you like Microcks, please ⭐ star ⭐ our repo to support it! 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact. |
|
I tried to move redundant up in a separate I would really appreciate some help here. |
I think that the local Maven repository where artifacts are installed needs to be shared between jobs in order to allow dependency resolution. So typically, to avoid doing |
|
cc @lbroudoux |
|
Hey @inosmeet Thanks for putting all of this together: I took time to read and review it, and it seems good to me. I think it could bring some really nice improvements. However, I noticed that your initial PR was made from the Would you mind closing this one and re-proposing another PR that applies the same set of changes but starting from the Thanks! |
Signed-off-by: Meet Soni <[email protected]>
- Move container image build steps from `build-verify.yml` to `build-container.yml` - Prevent container builds from running on PRs while allowing push and manual triggers Signed-off-by: Meet Soni <[email protected]>
- Extract integration tests and javadoc checks into separate jobs - Allow both to run in parallel, reducing CI execution time Signed-off-by: Meet Soni <[email protected]>
|
Hey @lbroudoux I've rebased the PR on 1.11.x, cherry-picked the commits. Does this work? |
lbroudoux
left a comment
There was a problem hiding this comment.
Let's go with this proposition! I expect some stuff to be broken but we'll see and fix them!
|
You are now a Microcks community contributor! 💖 Thanks and congrats 🚀 on merging your first pull request! We are delighted and very proud of you! 👏 📢 If you're using Microcks in your organization, please add your company name to this list. 🙏 It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact. If you need to know why and how to add yourself to the list, please read the blog post "Join the Microcks Adopters list and Empower the vibrant open source Community 🙌" Kudos and please keep going, we need you 🙌 |
Tests: https://github.com/inosmeet/microcks/actions/runs/13305709368/job/37156118925
This involves some redundant code while parallelizing
integraiton testsandjavadoc check.Related issue(s)
Fixes: #1488
cc @lbroudoux @yada