lmp/jobserv: add main-next ci job #386
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is a temporary solution to get the main-next build on ci and generate the proper sstate-cache until the branch is ready for integration and merged on main. Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
Member
|
Sorry, do we actually need main-next now that main is open for dev? |
Member
Author
Cuurently I have no way to test build on the CI because the PR job is the same for all branches. |
Member
Indeed, that is a bit annoying. |
ricardosalveti
approved these changes
May 20, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a temporary solution to get the main-next build on ci and generate the proper sstate-cache until the branch is ready for integration and merged on main.