I have noticed some of out vsts builds are failing when trying to create an octopus release today. The error we get is 400 Bad Request. The push package part works fine just the create release step that is failing.
Any ideas ?
We are experiencing the same issue. After troubleshooting for a couple of hours we found that if you un-check “Include Changeset Comments” the task will succeed. My guess is that Azure Devops made a change to the way change-set comments are queried, which in turn broke the task.
Still intermittent 400 even with that off for me
Hi @mmiller1 and @Brendan_Kehoe1,
We have had a few reports of this issue, and created a GitHub issue at https://github.com/OctopusDeploy/OctoTFS/issues/107 to track the progress. We’ll update the issue when we find the underlying cause, so keep an eye on that for any progress.
Others have mentioned that disabling changeset and work items has worked for them, so that might be a valid workaround for now.
If you have any other information, please feel free to add a comment to the GitHub issue, as this will be the central location where we track the progress.
Regards
Matt C
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.