You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.
- [ ] bug report -> please search issues before submitting
- [ x ] feature request
- [ x ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)
Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
see title
OS and Version?
Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?)
Versions
Mention any other details that might be useful
Thanks! We'll be in touch soon.
The text was updated successfully, but these errors were encountered:
boppbo
changed the title
Add scenario/tuorial that shows best practices how to build&deploy with Azure Pipelines
Add scenario/tutorial that shows best practices how to build&deploy with Azure Pipelines
Feb 8, 2019
Thanks, yes that's a good start. But all new projects created from VS template use yaml files. These can already contain parameters. During build they get merged and converted to the template.json. Will this step work on the build server, too?
Currently it seems to be easier to check-in the merged-json-template and delete the yaml files.
If I understood correctly you put placeholders for these parameters in the JSON file and they will be overridden by the pipeline during the build - even passwords, if you have to.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Any log messages given by the failure
Expected/desired behavior
OS and Version?
Versions
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: