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-faq.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -414,6 +414,7 @@ Configure the Docker proxy to output of the previous command and the port 8888 (
414
414
-[How do I include the .git folder in az acr build command?](#how-do-i-include-the-git-folder-in-az-acr-build-command)
415
415
-[Does Tasks support GitLab for Source commit trigger?](#does-tasks-support-gitLab-for-source-commit-trigger)
416
416
-[ERROR: No access was configured for the VM, hence no subscriptions were found.](#error-no-access-was-configured-for-the-vm-hence-no-subscriptions-were-found)
417
+
-[What git repository management service does Tasks support?](#what-git-repository-management-service-does-Tasks-support)
417
418
418
419
### How do I batch cancel runs?
419
420
@@ -442,6 +443,14 @@ We currently do not support GitLab for Source commit trigger.
442
443
443
444
This could happen if you are using `az login --identity` in your ACR Task. This is a transient error and occurs when the role assignment of your Managed Identity hasn't propagated. Waiting a few seconds before retrying works.
444
445
446
+
### What git repository management service does Tasks support?
447
+
| Git service | Source context | Manual build | Auto build through commit trigger |
0 commit comments