Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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.

Atlassian Community about banner
4,464,978
Community Members
 
Community Events
176
Community Groups

bitbucket datacenter connecting to jenkins

i've deployed bitbucket datacenter using the AWS quickstart into private networks with a public load balancer so jira can integrate.

This is the link to details on the quickstart architecture: https://aws.amazon.com/quickstart/architecture/bitbucket/

And I have a jenkins instance with a private load balancer. The bitbucket VPC an subnets can reach the Jenkins load balancer using peered networking and security groups are open.


However, bitbucket can't reach the load balancer when I create app link to jenkins:

Application 'Jenkins-primary' seems to be offline. Click here to Relocate.

 

I'm trying to use these instructions to connect bitbucket and jenkins.

https://plugins.jenkins.io/atlassian-bitbucket-server-integration/

 

Is there a better way to connect these two applications over private networking? Do I need to redeploy bitbucket?

1 answer

1 accepted

0 votes
Answer accepted

If you're using the instructions listed here, when you add the application link URL's, add /login to the jenkins hostname.

The app link requires a 200 response from the jenkins server, and if you go to the default page of a jenkins instance, it throws a 403.

 

My app link is working now after making that change.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS

Atlassian Community Events