CI: move 'distcheck' job from zuul to azure pipelines#8334
Closed
bagder wants to merge 3 commits into
Closed
Conversation
bagder
force-pushed
the
bagder/azure-distcheck
branch
from
933b985 to
28721d2
Compare
Member
Author
|
Keeps complaining on line 118 column 7. I wish I understood yaml. |
Member
Author
|
@mback2k can you help me understand what's wrong with this approach/yaml/syntax? I would like to understand, as I want to move over more work from zuul to azure pipelines going forward, for increased reliability. Update: got it working now. |
Thanks to Kushal Das
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.