Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Join now to unlock these features and more

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Get started Tell me more
Atlassian Community about banner
4,463,064
Community Members
 
Community Events
176
Community Groups

Jenkins return status code 128 when checkout development branch

sidharthan chuvatta
sidharthan chuvatta Oct 07, 2018

'FATAL: Could not checkout d48e00ce5cae12690fc0f05e73bcc8ee7ef1e4e3
hudson.plugins.git.GitException: Command "git checkout -f d48e00ce5cae12690fc0f05e73bcc8ee7ef1e4e3" returned status code 128:'

 

 https://ontashbot@bitbucket.org/ontash/foodapp.git

my bit bucket project repository.

through Jenkins job  what iam doing is merging sidharthan_dev to development branch,at that time the Jenkins job failing with the above error

Answer
Watch
Like Be the first to like this
19195 views

1 answer

0 votes
VICTOR-OSEGHALE
VICTOR-OSEGHALE Atlassian Team Oct 08, 2018

Hi Sidharthan,

Thanks for reaching out here.

There is a related issue in https://issues.jenkins-ci.org/browse/JENKINS-45997. Can you confirm that the workaround provided there resolves this ?

Kind Regards,
Victor

Reply

Suggest an answer

Log in or Sign up to answer
Bitbucket
Bitbucket
TAGS

Atlassian Community Events

See all events