Start the move to yaml pipelines.#540
Conversation
sanoursa
left a comment
sanoursa
left a comment
There was a problem hiding this comment.
Do you have any pipelines that are using these new yaml files? Everything seems fine, but I have no way to test or validate any of it
kewillford
left a comment
kewillford
left a comment
There was a problem hiding this comment.
Mostly questions to understand this better.
|
@sanoursa said:
Yep: https://dev.azure.com/gvfs/ci/_build/results?buildId=4061&view=logs |
|
Ignore the failed check. I can't authorize access to the secret file without having the yaml out of my fork and into Microsoft/VFSForGit. Once I do, the checks should come online too. |
|
@kewillford this is ready for another look. Latest build result: https://dev.azure.com/gvfs/ci/_build/results?buildId=4696&view=ms.vss-test-web.test-result-details |
kewillford
left a comment
kewillford
left a comment
There was a problem hiding this comment.
Looks good. Have you verified that this is updating the github status?
|
@kewillford to set up the pipeline to post status, i first have to get the yaml file into the branch, as best as i can tell, because i need to authorize access to the secure file we have in the pipeline. Getting it all configured to post statuses will be my next PR. Thanks for the review! |
4 participants
It's better to have the pipeline config in code, so let's move to yaml.