We at Midori are happy to announce our new app, Better DevOps Automation for Jira that brings DevOps automation triggers for Jira Data Center (and Server).
Better DevOps Automation is a no-code, low-code automation framework that adds new DevOps triggers to Automation for Jira (see below). It makes the DevOps practices easy to implement for teams using Jira Data Center (and Server). DevOps teams using Jira Data Center have not been enjoying the same rich automation capabilities as their peers using Jira Cloud. We aim to fill this gap with Better DevOps Automation, which is not limited to Bitbucket or even Git. It works with other version control systems like SVN, Mercurial, or Azure DevOps Server.
Better DevOps Automation for Jira is a companion app for Better Commit Policy for Jira. You will need both apps installed plus Automation for Jira to get the DevOps automation fun flowing. So don't forget to check Better Commit Policy out as well.
Actions are triggered when a changeset is pushed to and accepted (or rejected) in the blessed or central repository. There are a number of automation actions and use cases that you can instantly implement:
Better DevOps Automation allows developers to have more control over the exact behavior of their actions using @commands right in the commit message.
Better DevOps Automation introduces Genius Commits that are customizable, work with Jira Data Center (Server), and compatible with any popular VCS.
Genius Commits are the next generation of Smart Commits that unlock more DevOps automation actions. Just like Smart Commits for Bitbucket, you can use the default commands for processing issues. But while Smart Commits provide only 3 commands, Genius Commits come with 11 default commands.
Beyond the default commands, you can create your custom commands as well!
So, an example Genius Commit message that triggers DevOps actions would look like this:
"Fix the FOO-1 bug. @comment Bug fixed! @status Done @build LRT"
In this commit message, you are referencing a Jira issue, which will be commented on and transitioned to Done. A build will be triggered, but you even specified the exact build plan ("LRT") as a parameter of this command. You have direct control over whether you want to run a (potentially expensive) build after a commit or not, and what build plan to trigger.
The real power of Genius Commits shines when you create your own @commands to trigger whatever service or tool you want from the code commit!
Get more facts about Better DevOps Automation in the Documentation or get hands-on experience now with a free trial!
Levente Szabo _Midori_Marketplace Partner
Hi, DevOps community! Are you a DevOps practitioner (or know one in your network)? Do you have DevOps tips, tricks, or learnings you'd like to share with the community? If so, we'd love to hear m...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events