- Fixing Spring autoconfig fails when app is using AnnotationConfigWebApplicationContext (CF-11)
- Handle javaee (or other) namespace if present correctly for all Java based plugins.
Change-Id: I738b10fe02217c804defc92801d7021ca2c5d6bb
- run npm install on stager to recompile native modules
- provide modules based on package.json dependencies
- install npm on dev setup
Change-Id: I3e95aaf0982aea77fc280b58fcf965d1342b2ecf
- `rake spec' no longer installs dependencies
- no shelling out
- removed unused code
- single Rakefile
Change-Id: I538674d0649d9ad24060a950c671fadd01eac148
- Add new standalone framework that supports any runtime
- Allow a framework to not have a default runtime
- Allow sending a start command on app create/update
- Fix cc staging json parsing issue to allow quotes
in start command (EM.system strips escaped backslashes)
- Do not assign a web port if no URLs specified
- Confirm app is started by PID if no web port assigned
Change-Id: Ib4e51abf2495ff72dd586727bae85c0997bac28e
- Update rails plugin to use latest live_console
code, which contains fix to redirect stdout and
stderr to remote IO channel (for commands such as puts)
Change-Id: Ifa7faf959b9450730015ef2544e006acc363605f
We won't need that. Vendoring the staging gem also bumps vcap_common
and nats versions in CC and Stager's bundles.
This diff also sunsets an ugly fix in 268b4d (Change I4f2f08).
Test plan:
- Passed unit tests
- Passed BVTs on dev instance
Change-Id: Idab1e6e746432342d1ee7964283dca1bbdfe4bf6
- Removed the logic in agent that uses a file to decide if an app is started
(instead, we use Tomcat7's mechanism that doesn't bind to port until the
app is started). This makes Java web apps no different than other apps
- Update code to generate server.xml such that the bindOnInit attribute is
set to false (thus making it wait until the app is ready to bind to the port)
and remove flags that no longer apply to Tomcat7
Change-Id: If00f30dd636cf50df76fbc3cc99ba3eecb464531
This follows up commit 268b4d (Change Iee47fcf7) to enable overriding
runtime versions through the environment varialbes
VCAP_RUNTIME_${NAME}_VER when running unit and functional tests of
staging plugins.
Change-Id: I2a5d25358c432b40b70fb0c74d938dafc455213e
Update example yaml configs to reference Python 2.6 runtime as python2
lieu of Changes I9d5a37af and I513499da. This is more of a documentation
update as these configs are not used by deployed applications.
Test plan: passed unit tests
Change-Id: Id185299b13dbbb1fdfd4cc3fc67b07b334051798
They are not big (compared with spec), but they aren't useful to
rubygems.
This change doesn't bump the gem version to minimize impact
on other more important in-flight changes on staging.
Change-Id: If5b299823378a85e7bd98f517ee36f6b302602a7
Determines the runtime executables from the environment, falling back
to the current behavior of hardcoded paths in manifests when none is
set. This allows developers using different setups to run the unit
tests.
This patch also includes a interim fix to make the staging unit tests
happy. A more real solution should roll out in a day.
Test plans: pass unit tests, both locally and (seriously) on jenkins
Change-Id: I4f2f086dbaa9da66cdffd21c5d02d3941b7ec288
- Adds ci_reporter to the test group of the two bundles
- Removes leftover code for gemspec in staging Rakefile
- Vendors ci_reporter and its dependencies
- Shortens the env var names it detects
Test plans: pass unit tests locally and in jenkins
Next steps: coverage
Change-Id: Ib75994ad4be766a69436116fd6f9fe86373d65ff
Only check ruby runtimes for Sinatra and Rails when they are
supported. So that we can create a minimal set of staging plugin
manifests in stager functional tests.
Change-Id: I847349a09283fb58d22b52988583911af0d66fe6
- Sinatra - At staging, add a wrapper script to user's app that does a
"require cfautoconfig" and then a require of the user's script to
execute as expected.
- Rails - At staging, add a "01-auto_stage.rb" script to config/initializers
(using 01 is the Rails recommended approach for getting your initializer to
run first). This script does a single "require cfautoconfig"
which ensures that Around Alias is introduced before users initialize Mongo,
Redis, etc in additional initializer scripts
- Bundler Support - At staging, add the cf-autoconfig gem to the app's gems
and append the line ("gem cf-autoconfig") to the app's Gemfile.
- Opt-out: Both staging plugins will skip the all autoconfig steps if they
find a file called config/cloudfoundry.yml in user's app,
and it has "autoconfig: false" or if the app Gemfile includes 'cf-runtime'.
Change-Id: I509bd2e200afe460c3f03d70bdc4083a8a69e009
- Add new uuidtools dependency to stager bundle
- Update minimal uuidtools version for consistency with cc
Change-Id: I3c63c6fde3e7ed42b82d0ee1f276f16a568bbea3
Instead of hardcoding it.
Bumped gem versions and vendored into stager and cc.
Cascade the bump to stager and vendor that to cc
Passed the erlang BVT.
Shorter first-line commit message
Change-Id: I32672737bc23b1266e08cb9d431f53b9ac929b90
* stop requring it via :path ../common
* includes a dependency on em.0.12.11.cf.3 with a fixed up
gemspec to avoid the syck::defaultkey issue.
* bump staging and stager gems after taking new dependencies
* lock 3rd party gems to minor versions in the Gemfiles
Change-Id: I92648154036f8771400578a2ac14904c2c179d6c
Jennifer Hickey
Jesse Zhang
Thomas Risberg
Maria Shaldybina
Patrick Bozeman
Ramnivas Laddad
Ken Robertson
Nicholas Kushmerick
Alex Suraci
Alex Suraci
felixhoo
AB Srinivasan
Eduardo Aceituno