9 Commits

Author SHA1 Message Date
Gareth Clay
9a4bbfabd1 Upgrade to Gradle 7.5.1
Also default to running tasks in parallel
2022-10-13 17:09:45 +01:00
Alberto C. Ríos
4d9ba89034 Reverting distribution repository
To re-enable snapshot publishing
2022-01-10 13:26:14 +01:00
Alberto C. Ríos
36c13258f9 Upating build dist repository 2022-01-07 12:57:45 +01:00
Alberto C. Ríos
56364e4a5d Upgrading dependencies for 1.4
Updating pipelines
2022-01-05 12:43:44 +01: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
6fed6572cb Fix CI log interleaving
* Stop logs from parallel tests interleaving with each other
* Cut down on noise and reduce page load times by only logging std
streams for tests that fail
* @Validated AT cloud foundry configuration
* Remove unnecessary Gradle tasks from the AT job since they've already
been performed as part of `build`
* Stop tests and javadoc Gradle tasks being run against docs subproject
and causing failures

#380
2020-06-09 13:52:13 -04:00
Alberto Rios
eafa10acd9 Increasing gradle memory 2019-11-27 18:02:46 +01: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