Skip to content
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

[BUG]: autoCancel is ignored in pr trigger and new builds are triggered #4523

Closed
1 of 4 tasks
JanRajnoha opened this issue Nov 14, 2023 · 5 comments
Closed
1 of 4 tasks

Comments

@JanRajnoha
Copy link

What happened?

I wrote pr trigger with autoCancel set to false, created PR and tried do another commit to test if autoCancel will work, but in PR has been triggered another set of builds and previous has been cancelled

Versions

Azure DevOps online, Windows 11 Canary, on Azure DevOps used hosted windows version in pipelines

Environment type (Please select at least one enviroment where you face this issue)

  • Self-Hosted
  • Microsoft Hosted
  • VMSS Pool
  • Container

Azure DevOps Server type

dev.azure.com (formerly visualstudio.com)

Azure DevOps Server Version (if applicable)

No response

Operation system

Windows 11

Version controll system

git

Relevant log output

No response

@ismayilov-ismayil
Copy link
Contributor

Hi @JanRajnoha, thanks for reporting.
Could you please explain issue a bit more?
Is this possible to share pipeline yaml file and agent log with system.debug enabled? (please consider to remove or mask confidential data)

@JanRajnoha
Copy link
Author

No problem.

in yaml i have this (for triggers):

trigger:
  batch: true
  branches:
    include:
    - '*'
  paths:
    include:
    - list-of-paths

pr:
  autoCancel: false
  branches:
    include:
    - '*'
  paths:
    include:
    - list-of-paths

and from pipeline:
##[error]The build was canceled by Microsoft.VisualStudio.Services.TFS.

@ismayilov-ismayil
Copy link
Contributor

ismayilov-ismayil commented Nov 18, 2023

Dear @JanRajnoha, Thank you for posting this issue. Since this is not related to agent directly, I'm closing it. Please provide your issue in the Developer Community. This is the appropriate place for such cases.

@JanRajnoha
Copy link
Author

Oh, okay, thank you

@PyryViita-ahoAbb
Copy link

PyryViita-ahoAbb commented Jun 11, 2024

workaround: add "condition: or(succeeded(), canceled())"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants