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

Cannot update paths and switch to branch 'v99' at the same time

Luca Bottoni August 13, 2021

Hi all,

after many and many and many hours of test and readings of documentation (bad documentation) i must ask to anyone.

 

i try to use this pipelines

 

image: node:10.15.3
pipelines:
default:
- step:
name: "prova default"
script:
- git remote -v
- git fetch origin
- git checkout -b v99 origin/release/tag
custom:
test:
- step:
name: release new version tag
# trigger: manual
# caches:
# - node
script:
- git remote -v
- git fetch origin
- git checkout -b v99 origin/release/tag
release:
- step:
name: release new version tag
# trigger: manual
# caches:
# - node
script:
- git remote -v
- git fetch origin
- apt-get update
- apt-get install -y jq # install jq-
- git checkout master
- declare -x VERSION=$(jq -r '.version' package.json)
- echo "package.json version is $VERSION"
- git checkout origin/release/tag
- git merge origin/master
- echo \#\# version $VERSION >> RELEASE.md
- echo new version released >> RELEASE.md
- git add -f RELEASE.md
- git commit -m "version $VERSION released"
- git tag v$VERSION
- git push origin refs/heads/v$VERSION:release/tag --tags

 all steps in my console work fine, but for bitbucket no! the problem is when i try use

- git checkout -b v99 origin/release/tag

+ git checkout -b v99 origin/release/tag
fatal: Cannot update paths and switch to branch 'v99' at the same time.
Did you intend to checkout 'origin/release/tag' which can not be resolved as commit?

the same command in local in my console

 

C:\xampp\htdocs\personal\pipelines-react>git checkout -b v1.9 origin/release/tag
Switched to a new branch 'v1.9'
Branch 'v1.9' set up to track remote branch 'release/tag' from 'origin'.

 

why??how to resolved!!!!?!?!....about 4 hours of tests!!!!!!

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events