Pick particular builds to rebuild

James Skimming's Avatar

James Skimming

30 Sep, 2014 04:21 PM

When trigging a manual build, there is no option (that I'm aware of) to choose what to build, it just builds default branch. We often have a need to kick off non default branch builds (see my earlier ticket).

We need to trigger builds in the following scenarios:

  1. Non default branch builds (we can temporarily change settings to achieve this.)
  2. Rebuild Pull Request Build because of intermittent failures (we are currently making non changing commits to trigger builds from GitHub)
  3. Rebuild Pull Requests because the destination branch has changed, usually because other PRs have been merged into master. (We're currently rebasing to trigger a new build).

The first two could presumably be achieved using a rebuild option next to an existing build by rebuilding the same sha, as it's almost always needed because of failed builds that are not genuine build failures.

The last option is probably a little more difficult as I'm not sure GitHub sends out notifications when a PR's merge destination changes. In TeamCity there is the option to configure custom branch specification to build PRs, maybe a similar solution can be employed.

  1. Support Staff 1 Posted by Feodor Fitsner on 30 Sep, 2014 04:31 PM

    Feodor Fitsner's Avatar

    Hi James,

    I see. I've added your comments to the existing issue: https://github.com/appveyor/ci/issues/15

  2. 2 Posted by James Skimming on 13 Nov, 2014 10:43 AM

    James Skimming's Avatar

    Hi Feodor

    The recent changes to allow rebuild are welcome, but it doesn't address my third point, rebuilding pull requests when the destination branch (often master) has changed.

    I imagine it could only work if an automatic merge is still possible, where the PR still has green merge button available.

    TeamCity has this facility, it does this by specify a custom branch specification +:refs/pull/(*/merge), though I don't think GitHub sends a notification as the PR rebuilds are only queued after a pull from another build, usually caused by the master branch build when it changes.

    Is this something that can be added?

  3. Support Staff 3 Posted by Feodor Fitsner on 14 Nov, 2014 02:15 AM

    Feodor Fitsner's Avatar

    Yeah, the item for that is still open: https://github.com/appveyor/ci/issues/34

  4. 4 Posted by James Skimming on 14 Nov, 2014 11:16 AM

    James Skimming's Avatar

    Ahh, that'll be the one I gave a :+1: to last month. Sorry missed it :smile:.

  5. Support Staff 5 Posted by Feodor Fitsner on 14 Nov, 2014 06:49 PM

    Feodor Fitsner's Avatar


  6. James Skimming closed this discussion on 27 Dec, 2015 10:55 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac