What is New?

OpenShift 3

An important new feature made it into this milestone: the NodeJS application support on OpenShift.

Node.js Debugger

Now it is possible to debug Node.js applications deployed to Openshift. All you need to do is creating a Server Adapter for the app and running it in the Debug mode. After that a new V8 debug session will be created:

Put some breakpoints in the code and start debugging!

Changing the code during the debug session is also supported - just save the file and new changes will be applied automatically. Here is a short demo video which describes the debugging process in action:

What is New?

OpenShift 3

Although our main focus is bug fixes, we continue to work on providing better experience for container based development in JBoss Tools and Developer Studio. Let’s go through a few interesting updates here and you can find more details on the What’s New page.

Common namespace template support

Common namespace was added but templates were still loaded from the hardcoded openshift namespace.
They are now loaded from the configured common namespace (which still default to openshift)

User controlled hostname when creating routes

When an application is being deployed to Openshift, a route is optionally created if required by the user.
Openshift/CDK used to create an xip.io based hostname. User can now set its own hostname.
This allows for both changing the DNS to local IP provider (nip.io) or using you own enterprise DNS naming strategy.

The hostname can be accessed from the Services and Routing Settings page when deploying an application:

Forge

Forge Runtime updated to 3.3.2.Final

The included Forge runtime is now 3.3.2.Final. Read the official announcement here.

New Menu in Forge Console view to trigger the Command Selection Dialog