This blog post is an update to a post written by Kim Frederick on the DevOps Services blog in February 2015.
When you think about your delivery pipeline – you know, the automatic and manual steps that transform your source code into a living, breathing, deployed app in the cloud – you can probably break it down into multiple tasks that are executed in stages. You may have a build stage where your code is built and unit tests are executed; or you may have a stage that will deploy your application and then run functional tests. Well, I have great news for you! You can implement your entire delivery pipeline using a Delivery Pipeline in a DevOps toolchain which is part of the IBM Bluemix Continuous Delivery service. Toolchains are integrated sets of tools that make development and operations tasks repeatable and manageable.
With Stages and Jobs, you have more control over your delivery pipeline. As you can see in our example above, there is an FVT stage that has four jobs: a Gate job, a deploy job, a Sauce Labs Tests job, and a Functional Tests job. The PRODUCTION deployment is only triggered when all four of the jobs in the FVT stage are successful. There are three easy-to-use jobs available out of the box: Build, Deploy, and Test.
When you do see a failure, find out why fast! By clicking on View logs and history you can access the detailed logs for each of your jobs. You can see tabs for accessing logs and key information on what was used to execute each job.
If you are a service owner or first responder, you ask yourself "What’s going on with my IBM Cloud application?", "Are my customers satisfied with the service they’re getting?", "Has performance changed recently?" and so on. The answer begins with your organization's plan to design, deliver, operate, and control the IT and cloud services that it offers. This first post of the series begins with monitoring your cloud-based applications.
You can now interact with your own GitHub Enterprise and GitLab instances from Bluemix public!
Both the GitHub and GitLab tiles feature a new server dropdown menu, giving you the freedom to work with code on GitHub, GitLab, or in your own company’s GitHub Enterprise or GitLab instances.
The benefits of a microservices architecture come with a price. The service management solution must deal with the architecture’s inherent dynamics, dependencies, and complexities to ensure that the application is available and performing. Ignoring these considerations could result in the microservice-based applications might behave worse than a monolithic application that was built in the traditional fashion. The principles of managing microservices explained in this post will help you avoid these pitfalls.