| id: | status |
|---|---|
| class: | slide |
- 3 different build and deploy systems
- 3 different SCM systems
- 4++ different code quality and code coverage systems
- Multiple different packaging and deployment workflows
| class: | slide |
|---|
- Bamboo (build & deploy)
- BuildForge (build & deploy)
- Jenkins (build & deploy)
- Artifactory (artifact store)
- Clover (code coverage)
- Confluence (wiki)
- Crowd (user mgmt)
- Crucible and FishEye (code review)
- JIRA (ticket/project mgmt)
- Stash (SCM)
- Perforce (SCM)
- Sonar (source quality mgmt)
- Splunk (logs)
- Zenoss (monitoring)
| class: | slide |
|---|
- CloudStack
- Windows/Unix/Mac build machines
- Application servers
- User management for the applications
| class: | slide |
|---|
- BOM tool
- Build Dependency Tool
- uDeploy
- Electric Cloud
- PostgreSQL
- Signing Module
| class: | slide |
|---|---|
| id: | machines1 |
| class: | slide |
|---|---|
| id: | machines2 |
- Machines managed manually with ssh/scripts/build-plans
- Configurations differ between machines
- Buildplans therefor have to be tied to certain machines
- No equal load distribution
- Crash of single machine may block a plan/team
-> "Pets vs. Cattle"
| class: | slide |
|---|
- Bamboo plan to build binaries from sources
- Creates RPMs, stores them in NFS share
- Triggers child plans
- Bamboo childplan using bash scripts to:
- Upload rpms to Artifactory
- Trigger docker container creation in Jenkins
- Jenkins plan that builds docker containers
- Containers are stored in Artifactory
- Bamboo childplan for end2end tests in test environment using Cucumber
| class: | slide |
|---|---|
| id: | RTCGW-Bamboo1 |
| class: | slide |
|---|---|
| id: | RTCGW-Bamboo1a |
| class: | slide |
|---|---|
| id: | RTCGW-Bamboo1b |
| class: | slide |
|---|---|
| id: | RTCGW-Bamboo2 |
| class: | slide |
|---|---|
| id: | RTCGW-Artifactory |
| class: | slide |
|---|---|
| id: | RTCGW-Jenkins1 |
| class: | slide |
|---|---|
| id: | RTCGW-Bamboo3 |







