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
Copy file name to clipboardExpand all lines: articles/container-registry/container-registry-tasks-overview.md
+2-3Lines changed: 2 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ Containers provide new levels of virtualization, isolating application and devel
21
21
Build and test container images with ACR Tasks in four ways:
22
22
23
23
*[Quick task](#quick-task): Build and push container images on-demand, in Azure, without needing a local Docker Engine installation. Think `docker build`, `docker push` in the cloud. Build from local source code or a Git repository.
24
-
*[Build on source code commit](#automatic-build-on-source-code-commit): Trigger a container image build automatically when code is committed to a Git repository or a pull request is made.
24
+
*[Build on source code commit](#automatic-build-on-source-code-commit): Trigger a container image build automatically when code is committed to a Git repository.
25
25
*[Build on base image update](#automate-os-and-framework-patching): Trigger a container image build when that image's base image has been updated.
26
26
*[Multi-step tasks](#multi-step-tasks): Define multi-step tasks that build images, run containers as commands, and push images to a registry. This feature of ACR Tasks supports on-demand task execution and parallel image build, test, and push operations.
27
27
@@ -42,8 +42,7 @@ The following table shows a few examples of supported context locations for ACR
42
42
| Local filesystem | Files within a directory on the local filesystem. |`/home/user/projects/myapp`|
43
43
| GitHub master branch | Files within the master (or other default) branch of a GitHub repository. |`https://github.com/gituser/myapp-repo.git`|
44
44
| GitHub branch | Specific branch of a GitHub repo.|`https://github.com/gituser/myapp-repo.git#mybranch`|
45
-
| GitHub PR | Pull request in a GitHub repo. |`https://github.com/gituser/myapp-repo.git#pull/23/head`|
46
-
| GitHub subfolder | Files within a subfolder in a GitHub repo. Example shows combination of PR and subfolder specification. |`https://github.com/gituser/myapp-repo.git#pull/24/head:myfolder`|
45
+
| GitHub subfolder | Files within a subfolder in a GitHub repo. Example shows combination of a branch and subfolder specification. |`https://github.com/gituser/myapp-repo.git#mybranch:myfolder`|
47
46
| Remote tarball | Files in a compressed archive on a remote webserver. |`http://remoteserver/myapp.tar.gz`|
48
47
49
48
ACR Tasks is designed as a container lifecycle primitive. For example, integrate ACR Tasks into your CI/CD solution. By executing [az login][az-login] with a [service principal][az-login-service-principal], your CI/CD solution could then issue [az acr build][az-acr-build] commands to kick off image builds.
0 commit comments