...
- Build
- Compiles, creates the release artifacts, runs the (fast) unit tests, maybe some smoke tests + static code analysis
- Integration Test
- Runs the more expensive integration tests
- User Acceptance Test
How do we map the stages to Gradle tasks?
- Example pipeline from a Gradle presentation ( https://www.youtube.com/watch?v=L4ZgTCq6dLQ )
- Compile / Unit Tests
- Integration Tests
- Code analysis
- Assemble Distribution
- Publish Binaries (using these binaries in the following steps)
- Acceptance Tests
- User Acceptance Tests
- Canary Deployment
- Production Deployment
To be able to adapt this example pipeline in Kieker, we would have to:
- separate the unit tests from the integration tests
- merge the gradle threshold code into master to be able to have quality gates for code analysis
- think about a way for continouous build numbering without breaking sonatype/maven conventions (we could use the build numbering in snap-ci to do so)
Pipelines
Pull Request Check
...