ci: add .azure-pipelines.yml #3
Closed
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 just a test PR to see if a build is automatically created on Azure Pipelines. It looks like it is. |
The Shippable Continuous Integration service is scheduled for retirement on May 3rd, 2021 [1]. Therefore, a replacement has to be found. This commit introduces .azure-pipelines.yml which serves the same purpose as .shippable.yml but runs on the Microsoft Azure Pipelines infrastructure [2]. Link: [1] https://blog.shippable.com/the-next-step-in-the-evolution-of-shippable-jfrog-pipelines Link: [2] https://azure.microsoft.com/en-us/services/devops/pipelines/ Signed-off-by: Jerome Forissier <jerome@forissier.org> Acked-by: Jens Wiklander <jens.wiklander@linaro.org>
|
This pull request has been marked as a stale pull request because it has been open (more than) 30 days with no activity. Remove the stale label or add a comment, otherwise this pull request will automatically be closed in 5 days. Note, that you can always re-open a closed issue at any time. |
jforissier
pushed a commit
that referenced
this pull request
Jun 24, 2021
Adds checks in e32_relocate() that sym_tab is assigned a symbol table before using it. This fixes coverity scan: CID 1501826 (#1 of 3): Explicit null dereferenced (FORWARD_NULL) CID 1501826 (#2 of 3): Explicit null dereferenced (FORWARD_NULL) CID 1501826 (#3 of 3): Explicit null dereferenced (FORWARD_NULL) Acked-by: Jerome Forissier <jerome@forissier.org> Signed-off-by: Jens Wiklander <jens.wiklander@linaro.org>
jforissier
pushed a commit
that referenced
this pull request
Dec 6, 2023
Use the job ring #3 on i.mx8dxl to avoid resource conflict with other software stacks. Signed-off-by: Clement Faure <clement.faure@nxp.com> Acked-by: Jerome Forissier <jerome.forissier@linaro.org>
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.
The Shippable Continuous Integration service is scheduled for retirement
on May 3rd, 2021 [1]. Therefore, a replacement has to be found.
This commit introduces .azure-pipelines.yml which serves the same
purpose as .shippable.yml but runs on the Microsoft Azure Pipelines
infrastructure [2].
Link: [1] https://blog.shippable.com/the-next-step-in-the-evolution-of-shippable-jfrog-pipelines
Link: [2] https://azure.microsoft.com/en-us/services/devops/pipelines/
Signed-off-by: Jerome Forissier jerome@forissier.org