multiple nodejs processes running in a gear

https://bugzilla.redhat.com/show_bug.cgi?id=1077353
Merge pull request #5562 from bparees/nodejs_pid

Merged by openshift-bot
"InvalidByteSequenceError" on the first time do jenkins build for app

https://bugzilla.redhat.com/show_bug.cgi?id=1114948
Restrict carts to set of gear sizes
Automatic commit of package [openshift-origin-cartridge-jenkins-client] release [1.23.2-1].
Automatic commit of package [rubygem-openshift-origin-node] release [1.27.3-1].
Automatic commit of package [openshift-origin-cartridge-jenkins] release [1.23.2-1].
Automatic commit of package [rubygem-openshift-origin-msg-broker-mcollective] release [1.26.2-1].
Automatic commit of package [rubygem-openshift-origin-controller] release [1.27.2-1].
Automatic commit of package [openshift-origin-cartridge-nodejs] release [1.28.2-1].
Automatic commit of package [openshift-origin-node-util] release [1.26.2-1].
application.rb: allow vim to fix whitespace
broker: add PREVENT_ALIAS_COLLISION option.

https://trello.com/c/ASq1CXyv
Normally when an alias is created, OpenShift validates that it is not
already taken and that it is not of a form that could conflict with an
app name; this prevents problems where the node frontend could have two
destinations for the same URL on the same node and can only route one.
Normally it is obviously desirable to prevent this. But in certain use
cases we want to relax this validation, so this option does that (when
set to false). It is not documented in broker.conf comments because it
should not be used unless you really, really know what you're doing.
Merge pull request #5564 from sosiouxme/relax-alias-validation

Merged by openshift-bot
Merge pull request #5559 from derekwaynecarr/restrict_cart_gear_size

Merged by openshift-bot
Merge pull request #5563 from bparees/jenkins_encoding

Merged by openshift-bot