June 30, 2016 | Written by: Jarek Gawor
Categorized: Compute Services | What's New
Share this post:
In the next few days, we will be updating the community buildpacks across all the Bluemix public regions. After the upgrade, the following buildpack versions will be available:
Will my application be affected?
Any existing application deployed with any of the updated buildpacks will not be affected unless it is re-deployed. Once re-deployed, some applications might be affected by the changes in the buildpack dependencies, defaults or other runtime-specific changes outlined below. Most applications should re-deploy and continue to work without any additional updates.
How can my application be affected?
java_buildpack, the community buildpacks installed on Bluemix have a cache of the key runtime versions and other dependencies. Typically, the cache contains two patch versions for each runtime’s major version. For example, the new
0.12.13 versions of the
0.12.x runtime and
0.10.44 versions of the
If an application requests a specific runtime version that’s not in the cache, the application deployment will fail. Therefore, it is important to check if your application does not rely on a specific dependency that may no longer be in the cache after the buildpack update.
The best practice of specifying runtime versions for your application is to only specify the major version if possible. For example, in case of Node.js applications specify node version as
0.12.x in your
package.json file instead of the full version such as
0.12.11. That way your application will be much less susceptible to the cached runtime version changes with each buildpack update. This will also make it easier for your application to stay atop of latest runtime security updates or bug fixes.
The buildpacks will usually use a default version of the runtime or other key component if an application does not explicitly set it.
The defaults may change between buildpack versions. Therefore, it is also important to check if your application is relying on these defaults, as they may affect your application.
The best practice is to always specify your application dependencies explicitly.
What are the key changes?
You can find what runtime versions are supported and all other details on each buildpack’s release page (see the links above). Below is a short list of the key changes in the new buildpack versions that may affect your application:
- go_buildpack – the godep version was updated to
v62. The buildpack provides the following cached Go versions:
- ruby_buildpack – the default runtime version is now
2.2.4. The default Bundler version is now
1.11.2. The buildpack provides the following cached Ruby versions:
2.3.0. It also includes
- php_buildpack – the default runtime version is now
5.5.43. The default Nginx version is now
1.9.14. The Composer version was updated to
1.0.0 and the HHVM runtime was completely removed. The buildpack provides the following cached PHP versions:
7.0.5. It also provides other cached dependencies such as:
- python_buildpack – the default runtime version is now
2.7.11. The default PIP version is now
8.1.1 and the default setuptools version is
20.3. The buildpack provides the following cached Python versions:
- nodejs_buildpack – the default runtime version is now
4.4.2. The buildpack provides the following cached Node.js versions:
How can I quickly get my application running again?
Most applications will not be affected at all by these updates, while some may require minor updates to the dependencies versions or code. Yet, there might be some small number of applications that require additional effort to get them working again.
If you need to get your application back up and running quickly, re-deploy it with the same buildpack version as before the update using an external buildpack. Specifically, when using the
cf command line client, pass the
-b <buildpackURL> option to specify a GitHub URL of the community buildpack. The following list shows the URLs to use:
- go_buildpack –
- ruby_buildpack –
- php_buildpack –
- python_buildpack –
- nodejs_buildpack –
- java_buildpack –
For best results, use the buildpacks provided on Bluemix.