Hi,
no. I created branch1 from master then create and push commits on branch1
and don't make any changes on master branch during work on branch1. Then I
created a PR from branch1 to master and in the Jenkins. When building the
PR, I don't see any commits in the Recent changes view.
Another asp
Ok. So when you're having a branch and a PR from this branch to the master
(no changes in the master after creating the branch) - can you at least
reproduce the merge log message when building a pull request (see following
example:)
Merging remotes/upstream/master commit 49055790acff662de787b04
Hi,
thanks for answering. I can't upload pictures so here's the textual config
(the default settings):
Discover branches: Exclude branches that are also filed as PRs
Discover pull requests from origin: Merging the pull request with the
current target branch revision
Discover pull requests from
Hello,
anyone got a hint for me? Or does the bitbucket-branch-source-plugin "works
as specified"?
Thanks in advance!
Tom
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send
When building pull requests in a multibranch pipeline with the Bitbucket
branch source plugin, IMO the merge order is wrong which leads to wrong
change view information of the job.
My PR in Bitbucket is set up to merge a task branch into the master branch.
The jenkins build console says:
{code}
