disable_publish_on_pr and do_not_increment_build_number
Would it be possible to get more information around these properties?
Does it configure the actual pull *request* (as in, when it is created), when a new commit is added, and/or when it is accepted into the main branch?
We'd like to bump our build number each time a PR is accepted into a new branch, and then deploy to the project nuget feed.
Any assistance on further explaining these properties and the proper configuration for our desired deployment would be greatly appreciated.
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 Mike-EEE on 18 Nov, 2019 07:58 PM
I enjoy asking questions on here as I find it helps find an answer faster, basically of my own doing. xD
Anyways, I found the History tab, and it appears it is doing exactly what we want:
- PRs and subsequent PR commits create new builds, but do not deploy to the project nuget and they do not increase the build number
- When accepting a PR this kicks off a new build which increments the build number and publishes a nuget on the project feed.
Here are the configurations:
```
pull_requests:
do_not_increment_build_number: true
nuget:
project_feed: true
disable_publish_on_pr: true
```
Hopefully this will help someone else with the same questions.
Support Staff 2 Posted by Feodor Fitsner on 18 Nov, 2019 10:16 PM
Thanks for sharing your findings!
Mike-EEE closed this discussion on 19 Nov, 2019 11:10 AM.