Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update YAML syntax for Azure Pipelines #3165

Merged
merged 6 commits into from
Nov 6, 2018
Merged

Update YAML syntax for Azure Pipelines #3165

merged 6 commits into from
Nov 6, 2018

Conversation

davidstaheli
Copy link
Contributor

@davidstaheli davidstaheli commented Nov 5, 2018

The issue

YAML files in the .vsts-ci directory use old syntax. Issue #3164.

The fix

This PR updates the YAML to use the latest syntax. It does so under a new directory name: .azure-pipelines. If/when this PR is merged, the pipelines can point to YAML in this new .azure-pipeines directory and the .vsts-ci directory can be deleted.

The checklist

  • Associated issue
  • A news fragment in the news/ directory to describe this fix with the extension .bugfix, .feature, .behavior, .doc. .vendor. or .trivial (this will appear in the release changelog). Use semantic line breaks and name the file after the issue number or the PR #.

@techalchemy
Copy link
Member

Wow this is a significant improvement, thank you so much for taking the time to clean this up. Every time I go to spend some time fixing this, a million other things pop up. This is a big quality of life improvement

I am excited to figure out how to leverage test analytics to target some of our biggest offenders and speed up our horrifically slow test runtimes. Thanks again, I know people probably look at our configuration as an example and it's a terrible idea because I set it up in beta before yaml was even permitted and converted it and hacked on it until it worked, basically

@davidstaheli
Copy link
Contributor Author

Wow @techalchemy - nice job putting it together so early then. It looked great already!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants