How can we improve Azure DevOps?

Automatically start expired pull request build on "Auto-complete"

This suggestion is migrated to Developer Community. Please use below link to view the current status.
https://developercommunity.visualstudio.com/content/idea/365605/automatically-start-expired-pull-request-build-on.html
Currently if we use "Auto-complete" option inside of pull request that has expired build. It will wait until that build is restarted manually and successfully completed. It would be nice if expired pull request build would started automatically when "Auto-complete" option is used.

363 votes
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    Ruslan shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    12 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Espen commented  ·   ·  Flag as inappropriate

        +1 for this one.

        And there should be an option to auto-cancel / re-queue builds that already are in the queue / being built when a PR goes trough and would expire them.

      • Ruolan commented  ·   ·  Flag as inappropriate

        Or at least leave an option for us to choose whether we need to auto-start the build or not.

      • Anonymous commented  ·   ·  Flag as inappropriate

        Having this available will be very beneficial for productivity. Please consider it.

      • Robert commented  ·   ·  Flag as inappropriate

        This really should be a thing. Currently not having this is slowing down our developer velocity.

      • Tobias commented  ·   ·  Flag as inappropriate

        Having this feature would instantly stop discussons on gated pull requests (Speed vs. Quality). Now, developers are annoyed with repeated clicking on expired builds. Please consider this feature soon for upcoming releases.

      • Anonymous commented  ·   ·  Flag as inappropriate

        IMHO, Kyle Burns has the right solution to a very frustrating problem ! A much needed feature.

      • Anonymous commented  ·   ·  Flag as inappropriate

        If you have many features ready for the merge this might result in heavy traffic with unneccessary builds. Therfore it might be an option to trigger 1 "Auto-Complete" and "expired build" Pull request per repository at a time.
        This may be done nightly in a defines time interval.

      • Jonathan Juras commented  ·   ·  Flag as inappropriate

        One of the most frustrating things about using automatic PR completion is that they turn out to be very manual in nature. Having to requeue the build (when that requirement is the only outstanding one) is exceeding frustrating, and can generate a lot of developer angst when they can't see their changes merged in to master after several days (because of constant build expiration).

        This is probably the biggest game changer for the VSTS pipeline on our project.

      • Yu Meng commented  ·   ·  Flag as inappropriate

        Also would be great if it could try rebasing onto or merging (based on a setting) with the branch tip automatically.

      • Kyle Burns commented  ·   ·  Flag as inappropriate

        This would be a very useful feature for teams that are using gated pull requests. To conserve build agent resources and limit time waiting in line, it may be good to limit the automatic re-queuing of the build to the first (FIFO) PR that is in an "Approved" or "Approved with Suggestions" status and has auto complete option set

      Feedback and Knowledge Base