Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Pull request not updated

tp-29
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 3, 2019

Hi,

I have an issue with our instance of bitbucket (local instance)

I am trying to set a CI on top of a repo. The workflow used here is the forking workflow.

When a collaborator is creating a pull request, the CI do a checkout of the PR using theses commands

 > git fetch --tags --progress ***.git refs/pull-requests/*:refs/remotes/origin/pr/*
 > git rev-parse refs/remotes/origin/pr/49/from^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/refs/remotes/origin/pr/49/from^{commit} # timeout=10
Checking out Revision 40ba69ea831bffc5339df1dce9e8b254f50efecf (refs/remotes/origin/pr/49/from)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 40ba69ea831bffc5339df1dce9e8b254f50efecf

 All is working fine when the PR is created.

However if the collaborator do a commit in its own repository used for the merge request, the commit is not reflected into the CI. 

The only way to reflect the commit is to reload manually the webpage displaying the PR.

https://***/pull-requests/49/commits

When we do that if we re run the CI, the commit appear correctly.

 

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events