

Production consisted of the same microservice versions.

At the time before the pipeline deployed the change to the test environment both existing environments test and
#Run a local cloud foundry instance how to#
Run integration tests to check whether the gameplay between the two microservices workĪnd explains how to setup a concourse pipeline in order to test and deploy single microservices independently without affecting the overall microservice system.Deploy a second Service (not finished yet).Dry your pipeline: extract tasks and reuse them.Use planceholders/variables in the pipeline.Refactoring the Pipeline (not finished yet).Step 8: Specify a concourse job to deploy the UAA to the production environment.Step 7: Send an email once a new version of the UAA is deployed to the test environment.Step 6: Specify a concourse job to deploy the UAA to the test environment.Step 4b: Store the war file to Artifactory.Step 4a: Setup local Artifactory server.Step 3 - Create concourse job to build the UAA and run the unit tests.Step 2 - Create and Publish a Docker Image.Step 1 - Setup Git Repo for the pipeline and create files.Pipe the first service to production (Java App).First simple pipeline without deploying anything.Learn the basic concourse.ci concepts and setup a hello world pipeline.
#Run a local cloud foundry instance install#
Install the fly CLI and login using the fly CLI.Setup a concourse.ci Server with Vagrant.MonsterWriter - The most enjoyable way to write a thesis, paper, article or blog post.
