We asked ourselves: How can DevOps be realized with the Atlassian Toolchain? We asked Michael Eberhardt, one of our Atlassian Operations Engineers, about this. Michael has been working for Polygran since the beginning of 2018 and is an expert for Atlassian products. In this interview, he tells us what the Atlassian Toolchain is, its advantages, and how the Atlassian Toolchain can be used to implement DevOps successfully.
What are your responsibilities as an Atlassian Operations Engineer?
As an Atlassian Operations Engineer, you can quickly find yourself working full time. Of course, this includes administration, deployment, updates, and planning of the Atlassian environments and tools. But beyond that, we complete our portfoliowith solutions in the areas of database, web server or endpoint, virtualization, monitoring, storage, and backup. In this way, we guarantee the best possible user experience when using Atlassian products and enable our customers to use the tools correctly in the long term.
What is the Atlassian Toolchain?
As a child of the 90s, I always ask if people know the Power Rangers. When the Power Rangers fought against a superior opponent, they always combined their Zords into a Megazord. I think that’s exactly what it is: The Atlassian Toolchain is the product that results from the combination of all Atlassian tools and is the overpowering opponent to master the DevOps strategy.
“The Atlassian Toolchain is the product that results from the combination of all Atlassian tools and is the overpowering opponent to master the DevOps strategy.”
When is the Atlassian Toolchain used? For which applications is it used?
A classic use case is software development. But we often notice that there is so much more possible. We are currently working on implementing aChange /Configuration Management for our Linux Server and want to use the Atlassian Toolchain for this purpose.
For whom are the Atlassian Toolchain products suitable?
Simply put, for everyone who wants to work together, transparently and sustainably. On the one hand, we have the team leader who always knows the status of his project. On the other hand, specialists only want to concentrate on the project’s work. Classics like Jira or Confluence can, of course, be used with all their known functionalities outside the toolchain.
What advantages does the Atlassian Toolchain offer?
The developer can work centrally from one tool and is automatically informed about the status of development. Extensive build tests ensure the quality of the code and save time and resources. Besides, there is maximum transparency in terms of traceability. he project is transferable during a shutdown, simplifies team communication, is independent of team size, and can enable complete decentralized development without data loss.
What are the limitations or disadvantages of the Atlassian Toolchain?
Within the Atlassian Toolchain, great importance is attached to cross-border work with the other tools in the toolchain. But if you want to leave the toolchain, you usually have to use third-party plug-in implementations. Useful plug-ins typically cost a lot of money and have to be modified and developed further. But honestly, I can’t see any real limit in the toolchain.
Which one is your favorite product from the Atlassian Toolchain?
Definitely the Jira Service Desk: A central contact point for users/colleagues and their problems and wishes. Linked to the knowledge base Confluence, the user is shown the possible solution already when creating a problem. With a little implementation work, there is no more first-level effort.
When should you decide to use the Atlassian Toolchain?
As a passionate and convinced Atlassian Operations Engineer, I naturally say: Always. For example, I find Atlassian’s subsidy for small teams outstanding. This means that you can currently get the entire 10-user toolchain, self-managed, for little license costs in the server version, and Jira Service Desk is also included. But that’s not to say that we can’t make it big, quite the opposite. As I said before, you should be aware that transparency and sustainability can be created in collaboration. But using the toolchain is no guarantee that this will happen. Successful work and I hope you agree with me, depends on so many factors. But if you are looking for optimization, innovation, and facilitation in your daily tasks and are also ready for change, you should choose the Atlassian Toolchain.
“DevOps is more of a philosophy. All elements have to work towards a common goal across all areas.”
How does the Atlassian Toolchain differ from other tools and applications for the DevOps methodology?
I would describe it less as a methodology. DevOps is more of a philosophy. All elements have to work towards a common goal across all areas. I don’t think it makes any difference whether you use the DevOps idea for your software/system development or business management. And this is exactly where I see the difference from other products. With the Atlassian Toolchain, you can realize everything, of course, also because every tool in itself is a sophisticated solution.
Example scenario with Atlassian Toolchain
We asked ourselves: How can DevOps be realized with the Atlassian Toolchain? We asked Michael Eberhardt, one of our Atlassian Operations Engineers, about this. Michael has been working for Polygran since the beginning of 2018 and is an expert for Atlassian products. In this interview, he tells us what the Atlassian Toolchain is, its advantages, and how the Atlassian Toolchain can be used to implement DevOps successfully.
What are your responsibilities as an Atlassian Operations Engineer?
As an Atlassian Operations Engineer, you can quickly find yourself working full time. Of course, this includes administration, deployment, updates, and planning of the Atlassian environments and tools. But beyond that, we complete our portfoliowith solutions in the areas of database, web server or endpoint, virtualization, monitoring, storage, and backup. In this way, we guarantee the best possible user experience when using Atlassian products and enable our customers to use the tools correctly in the long term.
What is the Atlassian Toolchain?
As a child of the 90s, I always ask if people know the Power Rangers. When the Power Rangers fought against a superior opponent, they always combined their Zords into a Megazord. I think that’s exactly what it is: The Atlassian Toolchain is the product that results from the combination of all Atlassian tools and is the overpowering opponent to master the DevOps strategy.
“The Atlassian Toolchain is the product that results from the combination of all Atlassian tools and is the overpowering opponent to master the DevOps strategy.”
When is the Atlassian Toolchain used? For which applications is it used?
A classic use case is software development. But we often notice that there is so much more possible. We are currently working on implementing aChange /Configuration Management for our Linux Server and want to use the Atlassian Toolchain for this purpose.
For whom are the Atlassian Toolchain products suitable?
Simply put, for everyone who wants to work together, transparently and sustainably. On the one hand, we have the team leader who always knows the status of his project. On the other hand, specialists only want to concentrate on the project’s work. Classics like Jira or Confluence can, of course, be used with all their known functionalities outside the toolchain.
What advantages does the Atlassian Toolchain offer?
The developer can work centrally from one tool and is automatically informed about the status of development. Extensive build tests ensure the quality of the code and save time and resources. Besides, there is maximum transparency in terms of traceability. he project is transferable during a shutdown, simplifies team communication, is independent of team size, and can enable complete decentralized development without data loss.
What are the limitations or disadvantages of the Atlassian Toolchain?
Within the Atlassian Toolchain, great importance is attached to cross-border work with the other tools in the toolchain. But if you want to leave the toolchain, you usually have to use third-party plug-in implementations. Useful plug-ins typically cost a lot of money and have to be modified and developed further. But honestly, I can’t see any real limit in the toolchain.
Which one is your favorite product from the Atlassian Toolchain?
Definitely the Jira Service Desk: A central contact point for users/colleagues and their problems and wishes. Linked to the knowledge base Confluence, the user is shown the possible solution already when creating a problem. With a little implementation work, there is no more first-level effort.
When should you decide to use the Atlassian Toolchain?
As a passionate and convinced Atlassian Operations Engineer, I naturally say: Always. For example, I find Atlassian’s subsidy for small teams outstanding. This means that you can currently get the entire 10-user toolchain, self-managed, for little license costs in the server version, and Jira Service Desk is also included. But that’s not to say that we can’t make it big, quite the opposite. As I said before, you should be aware that transparency and sustainability can be created in collaboration. But using the toolchain is no guarantee that this will happen. Successful work and I hope you agree with me, depends on so many factors. But if you are looking for optimization, innovation, and facilitation in your daily tasks and are also ready for change, you should choose the Atlassian Toolchain.
“DevOps is more of a philosophy. All elements have to work towards a common goal across all areas.”
How does the Atlassian Toolchain differ from other tools and applications for the DevOps methodology?
I would describe it less as a methodology. DevOps is more of a philosophy. All elements have to work towards a common goal across all areas. I don’t think it makes any difference whether you use the DevOps idea for your software/system development or business management. And this is exactly where I see the difference from other products. With the Atlassian Toolchain, you can realize everything, of course, also because every tool in itself is a sophisticated solution.
Example scenario with Atlassian Toolchain
