Files
actions/MIGRATION.md
Marcin Grzejszczak 5d9ddf767f Fixed
2018-06-05 10:50:10 +02:00

41 lines
1.7 KiB
Markdown

# Migration to Spring Cloud Pipelines
- Added Maven wrapper
```bash
$ mvn -N io.takari:maven:wrapper
$ git add .
$ git add -f .mvn
$ git commit -m "Added maven wrapper"
```
- Updated `manifest.yml`
- Added `sc-pipelines.yml`
- provided which module is the main one
- added database as a required service
- Created cloud foundry spaces
```bash
$ cf login -o ... -a ...
$ cf create-space sc-pipelines-test-app-monolith
$ cf create-space sc-pipelines-stage-app-monolith
$ cf create-space sc-pipelines-prod
```
- Added `<distributionManagement>` section for all projects
- Added contract tests (`shortages-prediction-adapters/src/test/groovy/io/dddbyexamples/factory/shortages/prediction/monitoring/persistence/ShortagesDaoTest.groovy`)
- Added stub jar generation in `app-monolith` (in the output stubs jar each module has its own folder)
- Added `<profiles>` for all types of tests for all projects
- that way we can control the whole project from root
- Added base class for rollback tests (for `shortages-prediction-adapters`)
- Configured rollback tests via `sc-contract` plugin under `apicompatibility` profile (for `shortages-prediction-adapters`)
- Added `smoke` tests (just pining health initially) (initially only for `shortages-prediction-adapters` but could be added for more)
- Added `e2e` tests (just pining health initially) (initially only for `shortages-prediction-adapters` but could be added for more)
- Added `ServiceConfiguration` for `cloud` profile (TODO: Verify why that's needed)
- Created the `app-monolith-db` database service for production
- The repo name is `app-monolith`
- it matches the name of the artifact id of module that produces the fat jar