All,
We setup local environment in laptop and developers wrote code ,run testing locally then send a pull request ,once pull request is approved ,it will be pused to production enviornment in Cloud foundry . We observe that some bugs are only foundy in production environment(CF) however we don't find it in developers local enrionment and testing . There maybe inconsistent between local environment(developers' desktop) and production environment in production(CF) . What's best pratices to resove this ?

Thanks in advance !

Hi Lynn,

you can create additional environment in Cloud Foundry using spaces for this purpose. Then you need to alter your workflow so after accepting PR the app is pushed to staging space, where automated tests are ran to verify PR doesn't brake current functionality. After this verification you can push the app to prod space.

For more information please look at Continuous Delivery practice [1]

Alex Zalesov @ Altoros

[1]: http://martinfowler.com/bliki/ContinuousDelivery.html

Hi Alex,

when I get the summary from an app:
http://apidocs.cloudfoundry.org/214/apps/get_app_summary.html

I see a deprecated element: (example: production: false) so the best practice is the development of virtual environments using spaces?

Example:

+ CERT
+ PRE
+ PRO

Is the idea with spaces?

Juan Antonio

Hi Juan,

That is correct. The "production" flag on apps in the CC should not be
used. Instead you should push apps to different spaces with separate
domains associated to each app/space to create a staging/production pattern
as you described.

Best,
Zak Auerbach, CF Release Integration

On Fri, Nov 27, 2015 at 4:31 AM, Juan Antonio Breña Moral <
bren(a)juanantonio.info> wrote:

Hi Alex,

when I get the summary from an app:
http://apidocs.cloudfoundry.org/214/apps/get_app_summary.html

I see a deprecated element: (example: production: false) so the best
practice is the development of virtual environments using spaces?

Example:

+ CERT
+ PRE
+ PRO

Is the idea with spaces?

Juan Antonio