Manually trigger build for PR
Hi,
I have a open PR on my github project.
I want to manually trigger a build of this PR before merging it, how can I do that?
I looked through all the options and didn't see any way to manually trigger a build.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | 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
1 Posted by Ilya Finkelshte... on 24 Dec, 2018 05:46 PM
AppVeyor starts a PR build when PR is created. It that moment AppVeyor gets a PR-specific webhook from GitHub and triggers PR build. After that
RE-BUILD PRbutton is be available if you open specific PR build from the history.However from what you describe build for this PR was never started. Was AppVeyor project created before PR? Did you see PR webhook was sent (GitHub project Settings > Webhooks > AppVeyor webhook > Recent deliveries). If yes, and response from AppVeyor was 204, check
Eventstab at AppVeyor project level -- if build was skipped for some reason, AppVeyor writes an event there.Let us know what you found.
2 Posted by Riki on 31 Dec, 2018 09:34 AM
Hello,
first let's establish my settings:
In the projects options "don't build on PR" and "don't build on push".
For now that is on purpose as I always want to manually control when a build happens and if that build should be published to nuget.
Yes, I assume so.
I assume AppVeyor only starts a build for PRs automatically and there's no way to manually start a build of a specific PR, is that right?
I guess since I have automatic builds turned off, that makes your following questions irrelevant; but I'll answer them anyway just to make sure.
Yes.
There are no webhook entries in my project on github.
I must have disabled that in the beginning (which was on purpose).
So assuming there's no manual way to handle things, I think it would be best to create a new branch on github (maybe called 'release') and everytime I want to make a build and release it, I'd merge all master changes into the release branch? Or maybe doing something similar based on tags would be better?
Thank you for your support.
Support Staff 3 Posted by Owen McDonnell on 31 Dec, 2018 06:50 PM
If you want total manual control over build triggering, you could always use the rest API.
Otherwise, the method you suggested is an option, but would require that you have a webhook in your GitHub project. Ditto if you wanted to trigger builds based on tags (which also seems like a viable option).
4 Posted by Ilya Finkelshte... on 01 Jan, 2019 02:47 AM
Just noticed that
Start build of Pull Request (GitHub only)is wrong because we already support Bitbucket and GitLab PRs/MRs. Updated the documentation, this is correct link: https://www.appveyor.com/docs/api/projects-builds/#start-build-of-p...Ilya Finkelshteyn closed this discussion on 03 Mar, 2019 09:00 PM.