Azure-devops-docs: Missing Pipeline Resources Documentation
Sprint 159 introduced CD capabilities for your multi-stage YAML pipelines, but there's not any real documentation around how to use it. This is both on the main resources page and the YAML schema page.
Document Details
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: ee4ec9d0-e0d5-4fb4-7c3e-b84abfa290c2
- Version Independent ID: 3e2b80d9-30e5-0c48-49f0-4fcdfedf5eee
- Content: Resources - Azure Pipelines
- Content Source: docs/pipelines/process/resources.md
- Product: devops
- Technology: devops-cicd
- GitHub Login: @vtbassmatt
- Microsoft Alias: macoope
jschwanz
All 4 comments
Seeing this feature in the Sprint 159 update totally confused me. Everything about multistage pipelines (including the documentation) suggested that the tooling was moving towards having CI/CD in a single pipeline definition. Whereas this "CD capability" seems to be taking us back to the classic model of separating build and release into their own definitions. Some high-level guidance on how this feature fits into the larger pipeline model and how it's intended to be used would be very helpful.
JamesInDenver
on 31 Oct 2019
@JamesInDenver Thanks for the feedback. The intention of this feature to enable scenarios where you can split your pipeline and enable triggers and flow of artifacts across. As you grow up in your devops pipeline, you would need to enable complex scenarios where one team owns a part of your devops process and other teams take dependency on it. This feature is an extension of you CICD pipeline where you can enable CI and CD to be separate wherever required. We will provide full traceability across the pipelines. We will consider your feedback and incorporate in our documentation.
ashokirla
on 11 Nov 2019
Agreed, for example I'd love to know if it's possible to reference a pipeline via a service connection
BlairMcc
on 12 Nov 2019
The document has been updated and I'll be closing the issue. Thank you for the feedback and feel free to open a new issue if you have any more feedback.
iamsrivatsa
on 6 Feb 2020
Related issues
michhar
·
3Comments
EM1L
·
3Comments
anlatsko
·
3Comments
csutorasr
·
3Comments
atrauzzi
·
3Comments
Most helpful comment
Seeing this feature in the Sprint 159 update totally confused me. Everything about multistage pipelines (including the documentation) suggested that the tooling was moving towards having CI/CD in a single pipeline definition. Whereas this "CD capability" seems to be taking us back to the classic model of separating build and release into their own definitions. Some high-level guidance on how this feature fits into the larger pipeline model and how it's intended to be used would be very helpful.