-
Notifications
You must be signed in to change notification settings - Fork 21.5k
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.
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
Auto sync feature is not working for azure git repo. #39347
Comments
@girishgouda Thanks for the comment. We are actively investigating on the issue and will get back to you shortly with an update. |
@girishgouda Normally, auto sync feature works. Seems, there is an issue related to it. |
Even I am facing the same issue. Auto-Sync feature is not working for the repo which is under Azure Devops. |
I have the same issue.
Errors in the autosync job:
|
Our organization is having the same issue, is there any status update? |
I raised a support ticket with Microsoft and they said that the update to
fix this issue will be released on 10/18 across all regions. Subscribe
again to the sync feature, once the update is available and then the
auto-sync feature will work.
…On Tue 8 Oct, 2019, 6:54 PM Gerbrand van der Weg, ***@***.***> wrote:
Our organization is having the same issue, is there any status update?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#39347?email_source=notifications&email_token=ANJSIOSO2PMX4OB2ACTXFQTQNSCYDA5CNFSM4IZHO3Y2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAUEUMY#issuecomment-539511347>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ANJSIOT6CPN5ROLNAS224PLQNSCYDANCNFSM4IZHO3YQ>
.
|
It doesn't work for me as well, we have AzureDevops git and Auto-Sync enabled. |
Microsoft support have advised that they know about this bug and a fix is planned for deployment on the 12th December.
|
This seemed to work untill (I think) yesterday. Now when I try this the Process-SourceControlWebhook runbook starts but I get an output like this: `Getting Azure Connection information Getting the source control information SourceControl Properties : [RepoUrl = https://XXXX.visualstudio.com/XXXX/_git/Azure-Control] ,[Branch = Control-TEST] , [FolderPath = /Automation_Runbooks/] UrlConnectionInformation: [AccountName = XXXX] [RepoName = Azure-Control] [ProjectName = XXXX] Start a sync job for commit id : 8c8551cf20ab0820f8a1f67ad0f7bb7cb0b9075c Name Value ProvisioningState Running For some reason the job outputs the still running state and can't seem to finish (or even start). because of this the sync job also fails. Edit: Logging in to Azure... GET https://management.azure.com//subscriptions/XXXXXXXX/resourceGroups/Henk_BV_Powershell_Casus/providers/Microsoft.Automation/automationAccounts/HBV-Control-TEST/sourceControls/devops to azure test?api-version=2017-05-15-preview with 0-byte payload received 586-byte response of content type application/json; charset=utf-8 POST https://management.azure.com//subscriptions/XXXXXXXXXX/resourceGroups/Henk_BV_Powershell_Casus/providers/Microsoft.Automation/automationAccounts/HBV-Control-TEST/sourceControls/devops to azure test/listKeys?api-version=2017-05-15-preview with 0-byte payload received 899-byte response of content type application/json; charset=utf-8 Source control information for syncing: [RepoUrl = https://XXXX.visualstudio.com/XXXX/_git/Azure-Control] [Branch = Control-TEST] [FolderPath = /Automation_Runbooks/] Verifying url: https://XXXX.visualstudio.com/XXXX/_git/Azure-Control Connecting to VSTS... Syncing to commit id: 'e685517a1c722475509551714a56910c39dd247e'. GET https://dev.azure.com/XXXX/XXXX/_apis/git/repositories/Azure-Control?api-version=1.0 with 0-byte payload received 1981-byte response of content type application/json; charset=utf-8; api-version=1.0 GET https://dev.azure.com/XXXX/XXXX/_apis/git/repositories/Azure-Control/commits/e685517a1c722475509551714a56910c39dd247e/changes?api-version=1.0 with 0-byte payload received 1012-byte response of content type application/json; charset=utf-8; api-version=1.0 POST https://management.azure.com//subscriptions/XXXXXXXXX/resourceGroups/Henk_BV_Powershell_Casus/providers/Microsoft.Automation/automationAccounts/HBV-Control-TEST/sourceControls/devops to azure test/listKeys?api-version=2017-05-15-preview with 0-byte payload received 899-byte response of content type application/json; charset=utf-8 GET https://dev.azure.com/XXXX/XXXX/_apis/git/repositories/Azure-Control/commits/e685517a1c722475509551714a56910c39dd247e/changes?api-version=1.0 with 0-byte payload received 1012-byte response of content type application/json; charset=utf-8; api-version=1.0 POST https://management.azure.com//subscriptions/XXXXXXXXXXXXXXX/resourceGroups/Henk_BV_Powershell_Casus/providers/Microsoft.Automation/automationAccounts/HBV-Control-TEST/sourceControls/devops to azure test/listKeys?api-version=2017-05-15-preview with 0-byte payload received 899-byte response of content type application/json; charset=utf-8` After this I shows failed. I tried it with another repository and for some reason it does seem to work there. In one of my pipelines I'm checking if the sync job is complete already. Could this be the cause of the "fail" ? Edit2: I ran it again without the check if it's completed and it still doesn't work. I will check some more to see if I can find a difference between the two repositories and see if I can narrow down why it's failing. |
Okay I did some more testing, and from what I see the problem only seems to be when there is folder is defined. When you are syncing the root directory everything seems to work okay. but when using a folder in the directory the script seems to break... |
I did not specify the folder and it does not work. Having the same erros in logs as Ba4bes commented 3 months ago |
Did you set the webhook version to V1.0 as stuartin sugested? |
No, stuartin mention that tomorrow (12 Dec) it will be fixed. Fingers crossed |
For me when not having a subfolder settings the webhook to v1.0 worked |
It still fails but now with different errors:
|
Have same issue (manual sync works OK, but auto sync fails with error "Invalid project or repo name ") |
Due to inactivity with this GitHub issue, I'm going to proceed with closing it. If you are still encountering issues while attempting to setup this feature based on the article, please open a new GitHub issue and I'll include a PM from the product group to participate. #please-close |
Is this by design?
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: