The Mirantis Blog
Kubernetes tutorials, product updates and featured articles
While the bleed of apps to infrastructure was inevitable, the move to cloud native architecture makes automation essential. The infrastructure is very much a part of the application.
Ensuring that development and deployment are handled properly can be a challenge at best, and a nightmare at worst. You can hope things will work out, but hope is not a strategy.
Jenkins is crucial for CI/CD. But how do you get it to build the app when changes are pushed to your GitHub repo? Here’s a simple explanation.
Last week we spoke to Ryan Day about using Continuous Integration/Continuous Deployment (CI/CD) to keep not just your own software, but also externally produced software, up to date.
There’s no denying that the last year has seen a great deal of turmoil in the OpenStack world, and here at Mirantis we’re not immune to it. In fact, some would say that we’re part of that turmoil.
On Tuesday, March 3, Christopher Aedo and Nick Chase presented a webinar about Continuous Integration/Continuous Delivery (CI/CD) and how you can use it to create better software. These are the questions and answers.
In this third article in the series, we discuss adding one or more Jenkins slave nodes to the external OpenStack testing platform that you (hopefully) set up in the second article in the series. The Jenkins slave nodes we create today will run Devstack and execute a set of Tempest integration tests against that Devstack environment. Add a Credentials Record on the Jenkins Master Before we can add …