azure-pipelines-agent: ***NO_CI*** commit message flag not being honored
Have you tried trouble shooting?
Trouble shooting doc Yes, but n/a
Agent Version and Platform
Version of your agent? 1.136.1
OS of the machine running the agent? OSX/Windows/Linux/… All
VSTS Type and Version
VSTS
If VisualStudio.com, what is your account name? multiple
What’s not working?
The ***NO_CI*** commit message flag is no longer being honored, resulting in endlessly recursive builds. This was working just fine until very recently. I’m guessing the root cause may be a change on the VSTS side but not sure
Agent and Worker’s Diagnostic Logs
Logs are located in the agent’s _diag folder. The agent logs are prefixed with Agent_ and the worker logs are prefixed with Worker_. All sensitive information should already be masked out, please double check before pasting here.
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 17 (9 by maintainers)
Ring 4 has completed.
Updates: The deployment has finished on Ring 0/1/2. Ring 3 is deploying right now.
@lifesoccult the deployment that contains the fix has start rolling, it might take in total 3-4 days to hit all VSTS deployment rings (0 -> 5), what’s your VSTS account name? i can help you check which ring your VSTS account belongs to. 😄