Use master as fallback for non-existent branches#99
Use master as fallback for non-existent branches#99MartinNowak merged 3 commits intodlang:masterfrom
Conversation
|
Thanks for your pull request, @wilzbach! |
|
Example for such a failure: https://ci.dlang.io/blue/organizations/jenkins/dlang-org%2Fdmd/detail/revert-7416-fix18053/1/pipeline (from dlang/dmd#7505) |
6248688 to
8b602d3
Compare
When a PR is made directly from an upstream branch or to a different branch than `master` or `stable`, the respective branch at the other two repositories might not exist. So let's better check beforehand and softly fallback to `master` otherwise. The same procedure is e.g. used for CircleCi.
8b602d3 to
b4fec00
Compare
|
The failing test is a bad example, it's running a test for the revert branch in dlang/dmd, not for the PR. Limit branch tests wouldn't work with feature branches. In fact https://ci.dlang.io/job/dlang-org/job/dmd/configure already uses While we do have fallbacks for non-existing branch targets, this whole mechanism is to support feature branches. While working on the ctfe feature, we figured, it's better to create feature branches for all dlang repos, to pin them. But anyhow adding the fallbacks simplifies a few things, so let's add them to jenkins. |
Yes, that's why I submitted the PR in the first place. I have seen it a couple of times before in the past, e.g. if someone created a branch under
Feature branches were an awesome idea!
I am currently on my phone and see this is still failing. I will have a look at it soon. |
Already on it ;). |
e97cdb7 to
80096e7
Compare
80096e7 to
aa42f70
Compare
- fixes changelog display in jenkins
aa42f70 to
36848f6
Compare
|
Thanks! |
When a PR is made directly from an upstream branch or to a different
branch than
masterorstable, the respective branch at the other tworepositories might not exist. So let's better check beforehand and
softly fallback to
masterotherwise. The same procedure is e.g. usedfor CircleCi.
Note: I'm doing this more or less blind :/