nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

What are your challenges when connecting to Development Tools?

John Funk

There seems to be a plethora of apps in the Atlassian Marketplace for connecting Jira to Development tools - GitHub, GitLab, Bitbucket, Jenkins, etc.

Despite so many, there also seems to be just a handful of actual development tools being connected.

That being the case, what are the challenges you have found in connecting the tools to Jira and what has worked best for you? Do you have this documented? Have you done any videos showing the process?

I am not looking for vendor marketing responses and material. I am looking for actual users who have implemented (or attempted to implement) the connections and what went well, what are the pitfalls, what should you just plain avoid?

Comments

Yong Yang

Hi John,

I have tried to connect GitHub, Bitbucket and GitLab and they work very well and look like the same user experience in Atlassian Cloud platform side.

To get builds and deployments, we have to know and configure CI/CD pipelines in those DVCS tools. However, there are some sample yaml files for us to learn and get pipelines done.

Thanks & Regards,

YY哥

Amanda Barber

We have Jenkins and GitLab connected to Jira. It was mostly painless setup and helpful to see in the development panel in Jira!

Alex Akilov

Our primary challenge is that our environment is highly secured and all of our devops tools are hosted on premise, whereas Atlassian is in the cloud. We don't want any of our proprietary data (e.g. source code) to end up in the cloud so we must make sure that only metadata is allowed to flow from the tools to the cloud. Furthermore, we're not allowed to flow data from the cloud back to on-premise unless it goes through a highly controlled API tunnel that is carefully monitored and secured. The other challenge we face is that any non-human accounts that are normally used for creating tool to tool integration are currently blocked by the Multi Factor authentication requirements that we have on our Atlassian platform. Ideally, there would be a facility within Atlassian to differentiate between "managed" accounts synced from the IDP vs. non-human accounts that are not synced from the IDP. We haven't figured out the magic formula yet on how to get this working so any help would be appreciated.

John Funk

Thanks, YY. Any issues with permissions for users when connecting the tools?

John Funk

Nice! I have only heard good things about the Jenkins connection.

John Funk

Thanks for the feedback, Alex. So other than the magic tunnel, you have figured out all of the other connections?

Also, I suggest you open a support ticket with Atlassian for the magic tunnel request if you haven't already. Please post any link to a JAC ticket if they create one so we can vote on it.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

dev-ops-story

devops-story