You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I have a pipeline that runs when pushing to a branch. I created a manual step to merge that branch back to master. Triggering this step, checking out master always fails.
- git remote set-url origin https://username:${GIT_SECRET}@bitbucket.org/custodyx/cxc
- git remote show origin
- git fetch origin && git branch -avv && git checkout master
Here's I'm using app passwords, but I tried SSH keys to no avail.
Output:
> git remote show origin
* remote origin
Fetch URL: https://username:$GIT_SECRET@bitbucket.org/custodyx/cxc
Push URL: https://username:$GIT_SECRET@bitbucket.org/custodyx/cxc
HEAD branch: master
Remote branch:
pipelines-merge tracked
Local branch configured for 'git pull':
pipelines-merge merges with remote pipelines-merge
Local ref configured for 'git push':
pipelines-merge pushes to pipelines-merge (up to date)
> git fetch origin && git branch -avv && git checkout master
* pipelines-merge 2685089 [origin/pipelines-merge] merge back to master
remotes/origin/pipelines-merge 2685089 merge back to master
error: pathspec 'master' did not match any file(s) known to git.
* pipelines-merge: the branch to merge from
Any variation on authentication method & checking out produces the same result. It's like any other branches are invisible to the pipeline.
Is this expected? What am I doing wrong? Thanks in advance!
I was able to reproduce the error locally. The culprit is the parameter `--depth`. Specifying `depth: full` on bitbucket-pipelines.yml should fix, but then this applies to all steps. I need to do this only in a single step.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is an example:
clone:
depth: full
pipelines:
default:
- step:
name: Cloning
script:
- echo "Clone all the things!"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi everyone, We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.