Skip to content

Add a note about triggers on non-default branch to resources.md #14105

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.

Sign up for GitHub

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

Merged
Court72 merged 2 commits into from
Aug 12, 2024
Merged

Add a note about triggers on non-default branch to resources.md #14105

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
710922a
Add a note about triggers on non-default branch to resources.md
yevheniy-solovey-ms Jul 25, 2024
c17bc07
Remove view parameter from URL as suggested by validation build
yevheniy-solovey-ms Jul 25, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions docs/pipelines/process/resources.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -459,6 +459,9 @@ resources:
> [!NOTE]
> Service connections that use [Workload identity federation](/azure/devops/pipelines/library/connect-to-azure#create-an-azure-resource-manager-service-connection-using-workload-identity-federation) aren't supported in `azureSubscription`.

> [!NOTE]
> Trigger evaluation only occurs on the default branch. Make sure to set the correct default branch or merge the YAML file into the current default branch. For more information on how to change the pipeline default branch, visit [The pipeline default branch](/azure/devops/pipelines/process/pipeline-default-branch).

### Container resource variables

Once you define a container as a resource, container image metadata passes to the pipeline as variables. Information like image, registry, and connection details are accessible across all the jobs used in your container deployment tasks.
Expand Down