Organize and Standardize ci Directory Content #152
Merged
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
lindluni
requested review from
christo4ferris,
denyeart,
harrisob,
jyellick,
lehors,
mastersingh24,
mbwhite and
sstone1
as code owners
lindluni
changed the title
ci Directory Content
lehors
approved these changes
Apr 6, 2020
This change organizes the `ci` directory into common-sense subfolders and standardizes pipelines naming schemes. Also removes the dead Jenkins code in the `./scripts` directory Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
|
/azp run |
1 similar comment
|
/azp run |
|
Thanks! |
|
It got hung up on an azure flake, I ended up having to force it from the Azure UI |
|
Thanks Arnaud |
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.
This change organizes the
cidirectory into common-sense subfolders and standardizes pipelines naming schemes.Also removes the dead Jenkins code in the
./scriptsdirectoryAlso creates a single entrypoint for specifying the version of Fabric to test against in the azure-pipelines.yml file which is propogated into each of the network launch filees.
Signed-off-by: Brett Logan brett.t.logan@ibm.com