How to setup back merge release branch changes to main line

We are trying to use automatic back merging with the Gatekeeper strategy for our release branches (think Gitflow). This has worked pretty much flawlessly for a long time, but now we are having trouble to get it working again after a user that is admin cleaned up all of his SSH keys registered in Bitbucket server. Bamboo is unable to push changes to our mainline branch. We have tried adding a new user specifically for Bamboo and give it the correct R/W permissions on our mainline branch, but the merge still doesn't work. We are having difficulties finding documentation that is clear on how to setup the wanted behaviour from scratch.

A couple of the things we have tried/looked in to:

* Application link - setup correctly and working between applications. Didn't help.
* New user specifically for Bamboo - didn't help
* Adding user keys to Trusted Keys in Bamboo - didn't help
* Adding user permissions to Linked Repository - didn't help.

Exception during push:

Exception during push: com.atlassian.bamboo.plugins.git.GitCommandException: command /usr/local/bin/git push ssh://3d51dcf5-4196-4e93-bf7a-38fe01fdc868@127.0.0.1:54443/itdev/ibe.git develop --verbose failed with code 1. Working directory was [/opt/atlassian/application-data/bamboo/xml-data/build-dir/serverSide/ITDEV-RELNEW98-4/mergeWorkspace]., stderr:
Pushing to ssh://3d51dcf5-4196-4e93-bf7a-38fe01fdc868@127.0.0.1:54443/itdev/ibe.git
Warning: Permanently added '[127.0.0.1]:54443' (RSA) to the list of known hosts.
remote:                             *%%%%%.                            [K
remote:                         %%%         %%%                        [K
remote:                      ,%#               %%                      [K
remote:                     %%                   %%                    [K
remote:                    %#                     %%                   [K
remote:                   %%                       %                   [K
remote:                   %(                       %%                  [K
remote:                   %%%%%%%%%%%%%%%%%%%%%%%%%%%                  [K
remote:                 %#%*%#///////%# %%///////%%%%%%                [K
remote:                ,% %*%%******%#   %%******%(%%,%                [K
remote:                  %%/ %%/**%%/%%%%%%%(**#%( %%#                 [K
remote:                   %%          %%%          %(                  [K
remote:                    %                      .%                   [K
remote:                    *%        %%%%%       .%                    [K
remote:                      %#                 %%                     [K
remote:                       .%%            .%%                       [K
remote:                       .%%.%%,     %%%.%%/                      [K
remote:                 %%%%%%##%.  #%%%%%.  .%((%%%%%%                [K
remote:             %%#(((((((((%%,         #%%(((((((((#%%.           [K
remote:       %%%((((((((((((((((((%%%, .%%%((((((((((((((((((#%%*     [K
remote:     %%(((((((((((((((((((((((((%(((((((((((((((((((((((((#%.   [K
remote:   ,%(((((((((((((((((((((((((((((((((((((((((((((((((((((((%#  [K
remote:   %#((((((((((((((((((((((((((((((((((((((((((((((((((((((((%  [K
remote:   %%%%%%%%%%%%%(((((((((((((((((((((((((((((((((%%%%%%%%%%%%%  [K
remote:  %%            %####((((((###%%%%%%%%#(((((((((%            ,% [K
remote: ,%             %%%%%%#.               %%%((((((%*            %%[K
remote: #%                                       %%%#                %%[K
remote: .%                             .%%%%%%%%%                    %#[K
remote:  %                         #%%%                              % [K
remote:  %                     %%%%                                  %*[K
remote: /%************/#%%%%%%######%%*                        ..,*/(%%[K
remote:               %%######(((((((##################%%              [K
remote:               %%######(((((((((((((((((((((((((%%              [K
remote: //////////////%%%%%%%%#########################%%/////////  ///[K
remote: ----------------------------------------------------[K
remote: 'refs/heads/develop' is read-only.[K
remote: Check your branch permissions configuration with the project administrator.[K
remote: ----------------------------------------------------[K
remote:
To ssh://3d51dcf5-4196-4e93-bf7a-38fe01fdc868@127.0.0.1:54443/itdev/ibe.git
 ! [remote rejected] develop -> develop (pre-receive hook declined)
error: failed to push some refs to 'ssh://3d51dcf5-4196-4e93-bf7a-38fe01fdc868@127.0.0.1:54443/itdev/ibe.git'

Would really appreciate help regarding this!

 

Regards,

 

//Magnus

2 answers

0 votes

Hi Magnus

Were you able to solve this? I have a similar problem.

Using the branch updater stategy Bamboo fails doing the push saying it has write permissons only

0 votes

Most probably you need to visit the Bitbucket Server repository definition in Bamboo and re-save it. This should regenerate the SSH key needed for Bamboo to work.

If you still experience problems please contact Bamboo Support.

Suggest an answer

Log in or Sign up to answer
Community showcase
Asked Thursday in Jira Ops

I'm John Allspaw, Ask Me Anything about incident analysis and postmortems

I'm John Allspaw, co-founder of   Adaptive Capacity Labs, where we help teams use their incidents to learn and improve. We bring research-driven methods and approaches to drive effective inciden...

464 views 2 5
View question

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you