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

Guardian build task #3

Closed
premun opened this issue Apr 12, 2021 · 0 comments · Fixed by #29
Closed

Guardian build task #3

premun opened this issue Apr 12, 2021 · 0 comments · Fixed by #29

Comments

@premun
Copy link
Collaborator

premun commented Apr 12, 2021

Every time we change the C# definition of the pipeline, it needs to be exported into the .yaml file in the repo
which the pipeline is defined by. I currently don't see a way to have the C# definition only.

There should be a build step defined that will run in PRs and verify that the C# definition was exported into the YAML file in the repo.
It will export the definition and compare with the YAML file and fail if it doesn't match.
This way you will have a validation that you did the export before opening a PR.

premun added a commit that referenced this issue May 17, 2021
**Makes the project use the pipeline defined using Sharpliner inside the `Sharpliner.CI` project!**

Adds an AzDO task that will verify whether you have published and commited all changes into YAML files. (resolves #3)

The many empty arrays in the YAML will be gone once we check in aaubry/YamlDotNet#608
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 a pull request may close this issue.

1 participant