This repository has been archived by the owner on Apr 20, 2022. It is now read-only.
Allow to reuse existing services for test environment #114
Comments
marcingrzejszczak
added a commit
that referenced
this issue
Nov 21, 2017
marcingrzejszczak
added a commit
that referenced
this issue
Dec 9, 2017
- Change the CF way of doing prod deployment; fixes #111 - Add switch to delete services in CF (deletes everything for a test space); fixes #112 - Refactor the prod deployment function names; fixes #113 - Allow to reuse existing services for test environment via useExisting; fixes #114 - Separate repo with binaries URL for upload and download; fixes #115 - Allow passing of credentials to upload to repo with binaries; fixes #116 - Parametrize the manifest.yml filename; fixes #117 - Rollback smoke test run the latest tests and not the old ones; fixes #118 - Utilize the keyval resource in the concourse pipeline; fixes #120 - Don't log any URLs cause it can contain the password; fixes #121 - Allow multiple ports for stub runner on CF; fixes #123 - Get last prod-tagged release for back-compatibility and rollback jobs; fixes #124 - latest prod tag could change while pipeline is running; fixes #125 - For CF, PAAS_TEST_SPACE should be PAAS_TEST_SPACE_PREFIX; fixes #126 - Added parametrization of sc-pipelines.yml file in pipelines; fixes #127 - Enabled tag deletion in prod-rollback job; fixes #128 - App manifest is ignored; fixes #129 - Update the docs with step by step to convert your project; fixes #30
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
we could allow setting it in the
sc-pipelines.ymland setting it per environment / per service viauseExistingpropertyThe text was updated successfully, but these errors were encountered: