lmp/jobserv: prepare the kirkstone build #371
Open
Conversation
This file contains 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 an old job that is not used in the last 3 years [1]. It is currently back in use as a result of the creation of the bracnh kirkstone but note that this ci job did not exist for this purpose. [1] foundriesio@f74174e Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
This job will start tracking the branch kirksotne. Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
ea1b248 to
35358ac
Compare
All the other jobs have the AKLITE_TAG so add them. Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io>
|
Please add a description to the PR |
|
Can I understand we are going to perform 3 different kind of builds? main, kirkstone and scarthgap? Also, can you, please, describe how the test builds is implemented in a section (or child page) in the confluence page for Release Process? |
right, we will have 3 jobs:
I think this naming is more appropriate as it makes clear what branch form the Yocto LTS we are using.
I can add something but I don't fully understand the tests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Our main release CI job called
build-releaseis tracking thelmp-manifest/mainbranch which is already based onkirksotnebranches for all the layers. So it is time to rename that job tobuild-kirkstoneand also start tracking thelmp-manifest/kirksotnebranch that we already have.This will also remove the old
build-release-stablejob which has not been used for some time now and starts to be problematic because it tracks thekirkstonebranch that you didn't have but we recently created.