Closed
Conversation
|
see also #9 |
6 tasks
Member
|
All UI changes are being blocked until I complete the parity UI config with the new UI config I am implementing to be shared by Bitbucket and GitHub. Here is the GitHub preview
|
|
Any progress on this one? I'm running into the include branches bug and would like to have this if possible. |
Member
|
Will be considered after the combined GitHub/Bitbucket UI refactoring to use common shared behaviours (and may even be fixed by that refactoring) |
Member
|
likely superseded by #53 |
fengxx
pushed a commit
to fengxx/bitbucket-branch-source-plugin
that referenced
this pull request
Mar 13, 2018
[JENKINS-32493] Adapt to Parent POM 2.3.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We need this to include feature branches as well as all pull requests. So, we have the following pattern.
Branch includes: /feature//master /release/
But we also want to build all pull requests. So a new checkbox for "Include all pull requests" was added.
We did this pattern because we were finding that when we pushed a commit to a branch that had an associated pull request, Jenkins was building twice. Once for the pull request and another for the branch associated with that pull request. That was putting a lot of strain on our Jenkins.
I also fixed the pattern notation to allow a wildcard in any position, not just the beginning or end.