At first, it may seem silly. Why use dedicated deployment automation tools when your Platform-as-a-Service (PaaS) tooling makes it so easy to deploy your application? And yet, there are very good reasons why you may find yourself needing a full-featured, on-prem deployment automation solution even while using PaaS.
I previously described how to deploy an IBM Support Assistant application to be able to transfer data directly from applications in Bluemix to the IBM Support Assistant application. Combining the use of -Xdump:tool in Liberty buildpack applications with an IBM Support Assistant deployment in Bluemix means that you can automatically capture diagnostic data and analyse it using tools like Memory Analyzer without having to download anything locally.
There are teams that will not be able to use the feature rich experience with IBM DevOps Services. For example, teams may have security policies in place that do not allow development teams to host code or use development services that are hosted in a public cloud. In these cases, only on-premise tools are allowed. Fortunately we have an excellent set of deployment and release solutions as part of the IBM UrbanCode portfolio that can be used with Bluemix when organizational constraints or system complexity demands the value provided by the IBM UrbanCode solutions.
When you have a problem with an app you’ve deployed in IBM Bluemix, you want it as easy as possible to diagnose and resolve the problem. Ideally, you’d automatically capture the failure data, and analyze it in Bluemix, without having to download it. One way to do this is to deploy IBM Support Assistant Team Server as a Bluemix application.
After the free 30 trial period for Bluemix, many of our services and runtimes have perpetual free allowances, while others follow a pay-as-you-go (PAYG) pricing model. This blog post talks about our pricing model and the new pricing calculator, answers a few FAQs and explains how the pricing model helps you build and run apps in a really cost-effective manner.
The pace and nature of Development release cycles has changed dramatically. Seasoned developers working in traditional software delivery models are accustomed to a major product release every 12- 24 months, with point release every 3 months, to resolve bugs and introduce new functions that customers have deemed absolutely necessary. This webcast on continuous quality discusses the implications of changes in the traditional release cycle.
The Bluemix UI updates for August are now live in 85 countries! The team kept busy this month and put together a lot of awesome new features since our July refresh. We think you'll enjoy these enhancements, which include: Better Allowances for Runtime Usage, a Cost Estimator, and Redesigned App Details. Read on for more details. Then, go to Bluemix.net and try it out for yourself!
In a recent blog post Dr Nic Williams - aka "Dr Nic" - introduced a new buildpack that can be used to create a server which contains no logic, just serves up resources like HTML / JS / CSS / image / etc resources – aka a “static website”. Dr Nic shows how to deploy it to Pivotal Web Services, and while this should work on Bluemix, you never know until you try. So I tried. And of course it worked. To test the buildpack, I happened to have a perfect example that I have been playing with ....