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

Disable builds on the master branch for AppVeyor #9953

Closed
larsbergstrom opened this issue Mar 10, 2016 · 5 comments
Closed

Disable builds on the master branch for AppVeyor #9953

larsbergstrom opened this issue Mar 10, 2016 · 5 comments

Comments

@larsbergstrom
Copy link
Contributor

@larsbergstrom larsbergstrom commented Mar 10, 2016

Currently, AppVeyor builds the master branch every time that something is merged into it (see: https://ci.appveyor.com/project/servo/servo/history). However, that's not entirely useful, since it has already built exactly that commit on the auto branch in order to land it!

We'd like to either disable or no-op the builds on master... but hopefully without breaking AppVeyor builds on PR branches.

@UK992
Copy link
Contributor

@UK992 UK992 commented Mar 30, 2016

May i suggest to enable Rolling builds option, to shorten the build queue. Especially for unnecessary double builds on auto branch.

@larsbergstrom
Copy link
Contributor Author

@larsbergstrom larsbergstrom commented Mar 31, 2016

The last time we turned it on, it just seemed to be randomly canceling tons of builds. Though maybe that was actually servo/homu#23?

@Manishearth @edunham Do you remember what was happening when we last tried Rolling Builds and had so little success? If it was indeed just the try-related madness, turning it on would save a ton of effort :-)

@Manishearth
Copy link
Member

@Manishearth Manishearth commented Mar 31, 2016

I don't recall the reason behind rolling builds failing.

The easy way to make this work is to dynamically check if it's on the master branch and not a PR in the appveyor script and skip the build in that case. There's no configuration to do this.

bors-servo added a commit that referenced this issue Apr 1, 2016
Appveyor: Cancel unnecessary builds on 'auto' branch

This simple script will cancel build on ```auto``` branch if same commit already exist in ```master```.
As a part of solution mentioned in #9953

Tested:
Commit on master: [Appveyor/1.0.300](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.300)
Same commit on auto: [Appveyor/1.0.302](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.301)
Different commit on auto:  [Appveyor/1.0.302](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.302)

r? @larsbergstrom

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/10340)
<!-- Reviewable:end -->
@UK992
Copy link
Contributor

@UK992 UK992 commented May 7, 2016

@larsbergstrom Now that Windows builds running on dedicated buildbot machine, should be auto and try branch removed from appveyor.yml to reduce queue?

@larsbergstrom
Copy link
Contributor Author

@larsbergstrom larsbergstrom commented May 7, 2016

@UK992 Good call! I've excluded them from the AppVeyor settings :-) But yes, we could remove them from the appveyor.yml.

bors-servo added a commit that referenced this issue May 7, 2016
Remove auto and try branch from appveyor.yml

Closes #9953

r? @larsbergstrom

<!-- Reviewable:start -->
---
This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/servo/11066)
<!-- Reviewable:end -->
gecko-dev-updater pushed a commit to marco-c/gecko-dev-comments-removed that referenced this issue Oct 1, 2019
…ranch (from UK992:win32); r=larsbergstrom

This simple script will cancel build on ```auto``` branch if same commit already exist in ```master```.
As a part of solution mentioned in servo/servo#9953

Tested:
Commit on master: [Appveyor/1.0.300](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.300)
Same commit on auto: [Appveyor/1.0.302](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.301)
Different commit on auto:  [Appveyor/1.0.302](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.302)

r? larsbergstrom

Source-Repo: https://github.com/servo/servo
Source-Revision: 5333f564cd2f97ad78d2edc53f3791461b4b9244

UltraBlame original commit: 729ff86b053ff04d197067887c26fdcbe76e1297
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified-and-comments-removed that referenced this issue Oct 1, 2019
…ranch (from UK992:win32); r=larsbergstrom

This simple script will cancel build on ```auto``` branch if same commit already exist in ```master```.
As a part of solution mentioned in servo/servo#9953

Tested:
Commit on master: [Appveyor/1.0.300](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.300)
Same commit on auto: [Appveyor/1.0.302](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.301)
Different commit on auto:  [Appveyor/1.0.302](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.302)

r? larsbergstrom

Source-Repo: https://github.com/servo/servo
Source-Revision: 5333f564cd2f97ad78d2edc53f3791461b4b9244

UltraBlame original commit: 729ff86b053ff04d197067887c26fdcbe76e1297
gecko-dev-updater pushed a commit to marco-c/gecko-dev-wordified that referenced this issue Oct 1, 2019
…ranch (from UK992:win32); r=larsbergstrom

This simple script will cancel build on ```auto``` branch if same commit already exist in ```master```.
As a part of solution mentioned in servo/servo#9953

Tested:
Commit on master: [Appveyor/1.0.300](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.300)
Same commit on auto: [Appveyor/1.0.302](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.301)
Different commit on auto:  [Appveyor/1.0.302](https://ci.appveyor.com/project/UK992/servo-hga0y/build/1.0.302)

r? larsbergstrom

Source-Repo: https://github.com/servo/servo
Source-Revision: 5333f564cd2f97ad78d2edc53f3791461b4b9244

UltraBlame original commit: 729ff86b053ff04d197067887c26fdcbe76e1297
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.