Search the Community
Showing results for tags 'devops'.
Found 8 results
-
The word continuous has become ubiquitous in the realm of Agile development and quality assurance. Continuous delivery, continuous integration, continuous testing, continuous deployment, continuous improvement – what do these terms really mean? If you look at an Agile life cycle that includes steps to plan, prepare, explore, realize, test, deploy and run, continuous integration comes early on, aligned with developers. With all the pockets of new development happening in Agile environments, there’s a lot of changes being made to the code, creating a heightened need for version control. Continuous integration was born out of a need to have a central place to save and store that code change, such as GitHub, and compile that code outside of their machines in the continuous integration server. This process creates the opportunity to match all the other dependencies and things that other people are building. And that's where unit tests live. Continuous integration includes things like ADO, Jenkins, freestyle and pipeline builds. -
devops 4 new feature for DevOps in Jira provide more visibility and better insights
Jimi Wikman posted a blog article in Atlassian
One of the biggest cause for complicated workflows and custom fields is the fact that Jira has never been a deployment tool, but the teams need the visibility of deploys. With this latest update to Jira Software Cloud we see improvements in this field with no less than four new features. DevOps teams or not, this will make life easier for everyone. While there are several add-ons for Jira Software Cloud that will tie together repositories with Jira, this is now a standard feature in Jira. That means that it can be used with no additional cost (except for the Premium features if you don't have Premium of course), which lowers the entry point substantially. Hopefully this will mean the end of operations based statuses in the workflow and custom fields to hold release data. Code in Jira This feature allows you to connect your repo to Jira so you can visually see the repos in a new tab in your project called Code. Doing so if fairly easy, especially if you use Bitbucket, but adding Github for example takes only a few minutes. The biggest benefit of this feature for me however is that you will see the repo information in the Jira issue itself. This provide a lot of information to the viewer on where this issue has been committed. Deployments in Jira This is where things get interesting. With Code in Jira above you can see where your code packages are and their status. With Deployments, you can see where those packages also have been delivered to. This provides a very nice overview of where your code currently is available, which is what most people want to know when they try to build this into their workflows or work views. Premium Features The last two features are only available for the Premium version of Jira Software Cloud. Normally I don't like to have features split between a standard and a more expensive version, but these two features are all about measuring which I think is fine to have as a bonus if you need the more expensive version. Deployment Frequency Cycle Time My Thoughts This is a very good addition to Jira Software Cloud that have been needed for a long time. While I think the Premium features is mostly for numbers people and not really for the daily work I think this still is a solid addition. I would like to see the deployment information on the issues and it needs a connection with Insight, so I can connect deploys to my assets. There is a lot of potential here and I look forward to seeing this taking further in the future. -
One of the biggest cause for complicated workflows and custom fields is the fact that Jira has never been a deployment tool, but the teams need the visibility of deploys. With this latest update to Jira Software Cloud we see improvements in this field with no less than four new features. DevOps teams or not, this will make life easier for everyone. While there are several add-ons for Jira Software Cloud that will tie together repositories with Jira, this is now a standard feature in Jira. That means that it can be used with no additional cost (except for the Premium features if you don't have Premium of course), which lowers the entry point substantially. Hopefully this will mean the end of operations based statuses in the workflow and custom fields to hold release data. Code in Jira This feature allows you to connect your repo to Jira so you can visually see the repos in a new tab in your project called Code. Doing so if fairly easy, especially if you use Bitbucket, but adding Github for example takes only a few minutes. The biggest benefit of this feature for me however is that you will see the repo information in the Jira issue itself. This provide a lot of information to the viewer on where this issue has been committed. Deployments in Jira This is where things get interesting. With Code in Jira above you can see where your code packages are and their status. With Deployments, you can see where those packages also have been delivered to. This provides a very nice overview of where your code currently is available, which is what most people want to know when they try to build this into their workflows or work views. Premium Features The last two features are only available for the Premium version of Jira Software Cloud. Normally I don't like to have features split between a standard and a more expensive version, but these two features are all about measuring which I think is fine to have as a bonus if you need the more expensive version. Deployment Frequency Cycle Time My Thoughts This is a very good addition to Jira Software Cloud that have been needed for a long time. While I think the Premium features is mostly for numbers people and not really for the daily work I think this still is a solid addition. I would like to see the deployment information on the issues and it needs a connection with Insight, so I can connect deploys to my assets. There is a lot of potential here and I look forward to seeing this taking further in the future. View full blog article
-
7 years of experience in IT infrastructure and Development Operations Presently Working as “Devops Engineer” at H&M AB Ability to use a wide variety of open source technologies and tools Design, Implementation and Administration of DevOps Pipeline with Complete CI\CD\CM Experience with systems and IT operations with strong focus on business outcomes Design, Implementation and Administration of Splunk Enterprise 6.x Configuring and Running Docker. Administration of Splunk indexers, Search heads and Forwarders for various business division Complete life cycle management of Linux & Windows servers (Provisioning, Patching, channel management and decommissioning) Experience in Configuration Management/Application Deployments /orchestration using Ansible and Octopus deploy. Experience in Cloud Administration Onsite Coordination with Offshore Delivery Operations- 1 comment
- 1 review
-
- 1
-
-
- development operations specialist
- ansible
- (and 7 more)
-
Project Management | Quality Assurance | Service Management | Scrum Master | DevOps Project Manager- 1 review
-
- 1
-
-
- project management
- team lead
- (and 11 more)
-
automation Jira Cloud Automation - code free automation for everyone!
Jimi Wikman posted a blog article in Atlassian
Automation in Jira have long been requested by the customers and now it is finally here for all Jira Cloud customers. This new feature is actually not new, but it is the popular Automation for Jira app that was purchased by Atlassian in 2019. Not only is this an amazing addition, it is also completely free for all Jira Cloud users. Automation for Jira was purchased by Atlassian back in October 2019 and in March 2020 the automation functionality was made available natively to every single Jira Cloud instance at every tier. In late March the first DevOps triggers was released with the promise of new functionality coming soon. For server users there is still the old app for now. With the new automation feature that is built into Jira Cloud you can now automate a lot of actions. Not only will this free up time for you and your team, it is also super easy to setup with no coding what so ever! This is pretty impressive of course, but when you extend this across other products like Bitbucket and Github, then you get something very nice indeed. I have used the Automation for Jira app before and really liked it's simple, yet powerful features. It is really, really good that this now comes as a standard feature for all Jira Cloud customers. -
Automation in Jira have long been requested by the customers and now it is finally here for all Jira Cloud customers. This new feature is actually not new, but it is the popular Automation for Jira app that was purchased by Atlassian in 2019. Not only is this an amazing addition, it is also completely free for all Jira Cloud users. Automation for Jira was purchased by Atlassian back in October 2019 and in March 2020 the automation functionality was made available natively to every single Jira Cloud instance at every tier. In late March the first DevOps triggers was released with the promise of new functionality coming soon. For server users there is still the old app for now. With the new automation feature that is built into Jira Cloud you can now automate a lot of actions. Not only will this free up time for you and your team, it is also super easy to setup with no coding what so ever! This is pretty impressive of course, but when you extend this across other products like Bitbucket and Github, then you get something very nice indeed. I have used the Automation for Jira app before and really liked it's simple, yet powerful features. It is really, really good that this now comes as a standard feature for all Jira Cloud customers. View full blog article
-
untilJfokus is all about developers! Java, Frontend & Web. Continuous Delivery & DevOps, Internet of Things & Artificial Intelligence, Cloud & Big Data, Future & Trends, Alt.JVM Languages like Scala, Kotlin & more, Agile development... and Superheroes When: 3-5 February 2020 What: Sweden's largest developer conference Where: Stockholm Waterfront Conference Contact: jfokus2020 (a) jfokus.se
