I have long been a fan of the DevOps pipeline available on the bluemix platform. I was impressed by the original jazz version and the migration to the new pipelines was an enjoyable upgrade on what was presented before. My issue had always been that my source code needed to be managed on bluemix git repositories. As part of a larger practice we had a git repository server behind our firewall and I couldn’t get the pipeline to connect to it.
In a recent study on DevOps-driven innovation, Forrester Research reminds us that "DevOps is about people first." Implicitly, at whatever velocity, a DevOps program that fails to innovate on customer experience is like running in place.
There are several cases where it is useful to be able to stand up additional WebSphere capacity for a limited time period, without needing to worry about data center server capacity and software licenses. Typical examples include batch type workloads, test of new code at infrequent intervals, maybe as part of an overall application modernization strategy.
Do you want to use specific build input to deploy your app to IBM Bluemix as a part of an IBM Continuous Delivery toolchain? Now you can!
Rapidly developing and iterating applications that noticeably innovate user experience in any market or industry has become a competitive necesssity. Cloud native development is the term for using cloud platforms and services along with DevOps processes and practices, tool-chain-driven automation, and data-driven performance reviews to delight customers beyond current expectations. As software organizations make the transition […]
In this post, we'll talk about how you can create a DevOps toolchain in Bluemix using Bluemix Continuous Delivery if you've already built and deployed an application.
This is the last of three parts on preparing and deploying an MVP application
Do you have sample applications built for IBM Bluemix that you want to share with others? It’s now a whole lot easier, with the introduction of the new Deploy to Bluemix button.