Commit Graph

7 Commits

Author SHA1 Message Date
Roy Clarkson
b7e27cd84a Remove 'set -u' parameter because staging script is failing on an unbound var
Staging for releases is failing on an unbound variable. This is because there
is no suffix to append in the new Spring version format.

/opt/concourse-java.sh: line 81: $2: unbound variable
2020-11-19 16:18:05 -05:00
Yuxin Bai
c16b20f567 Trying to set git config with CLI 2020-11-18 15:27:12 -05:00
Gareth Clay
81ec2f15a3 Update publication config
* Allows publication to a custom maven repo, as we do in CI tasks
* Adds `SKIP_TESTS` (defaults to `false`) param for quicker testing
of CI build task with `fly execute`
2020-07-09 14:44:15 +01:00
Gareth Clay
7ca3239ba6 Pipeline refresh
* Migrate PR pipeline definition into main repo
* Move credentials from LastPass to CredHub
* Reference docker images in tasks to allow use of `fly execute`
* Make use of var templating everywhere to make `fly execute` easier
still
* Move pipelines to `app-broker` Concourse team
* Separate CI management scripts from Concourse task scripts
* Template git-repo-staging user data
* .envrc
* Fix `InMemoryServiceInstanceBindingStateRepositoryTest` failure when
the time rolls over into a new minute during test execution :D

closes #381
2020-06-15 09:50:34 +01:00
Gareth Clay
1d3ff3d371 Perform staging version bumps in a branch
To prevent clashes with our Github branch protection rules

closes #388
2020-06-11 15:57:07 +01:00
Gareth Clay
f2ec97d977 Updates to the staging process
* Pipeline now fetches tags so the task doesn't have to
* Staging jobs now take git versions that have passed ATs. This avoids
the need to run all the tests again, taking staging down from ~20 mins
to ~2
* Version bumps are done on a branch to avoid pushing to protected
`master branch`
* Debug output and script tidying
2020-06-08 15:06:04 -04:00
Alberto Rios
7b8c877cf0 Adding release pipeline
Integrating existing pipeline with a new release pipeline

It is composed by three different groups:

- The first group is a basic build so that we can always be sure which build we will be getting when releasing, followed by the acceptance tests.

- The second group are the releases.

- The last group is the CI image used by the different tasks.
2019-08-28 17:44:26 +02:00