Do you have a Jenkins server that you want to integrate to a toolchain in order to deploy your applications to Bluemix (instead of using the Delivery Pipeline)? With toolchains in IBM® Bluemix® Continuous Delivery, you can integrate your Jenkins server to deploy your applications to Bluemix, but also benefit from this integration to send job notifications to other tools, such as Slack or PagerDuty, as well as track code deployments through tags, labels, and comments in your Git repository.
Once integrated with your toolchain, and your Jenkins (Freestyle or Pipeline) job configured, other tools such as Slack or PagerDuty
will be notified that the given job was started, completed or failed.
Example Slack notifications:
Example: Track your code changes
Once the Jenkins job has successfully deployed your latest commit(s), any issues that are referenced in the commit’s comment are automatically updated with a comment and label pointing to your Bluemix toolchain, application, and org as well as to your Git commit.
Note that the IBM DevOps Insights part of this integration isn’t covered in this post, but you can learn more about it in the References section at the bottom of this page. At this stage, you managed to configure your Jenkins server to have a build job that deploys your application to Bluemix. Congratulations!
Install the IBM DevOps plugin on your Jenkins server: Now let’s add some cool features to this Jenkins integration. Install the IBM Cloud DevOps Plugin.
Configure your Jenkins project: Depending on your Jenkins implementation, you may select to notify tools integrated to your toolchain when using the Freestyle project and Pipeline.
You’re now ready to test the new features you just enabled by launching a new build.
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.