- Github
- Jira
- Nexus
- CloudBees Core
- Pivotal Web Services / Cloud Foundry
- Demo environment
-
Create a feature ticket in jira https://jira.beescloud.com/projects/PHP/issues
-
Do a change in the code: https://github.com/cloudbeers/personal-healthcare-portal/blob/master/src/main/java/com/myinsurance/www/personalhealthcareportal/PersonalHealthcarePortalController.java#L13
- Save the code change as a Feature Branch and create a Pull Request on this Feature Branch
-
Verify that the branch build is triggered https://cd.wordsmith.beescloud.com/teams-front-team/blue/organizations/front-team/personal-healthcare-portal/activity
-
View CloudBees Core and Jenkins capabilities to automatically collect knowledge on the build: unit tests, code coverage, findbugs, "TODO" and "FIXME" comments in the code, Maven details...
-
Merge the pull request https://github.com/cloudbeers/personal-healthcare-portal
-
Verify that the master build is triggered https://cd.wordsmith.beescloud.com/teams-front-team/blue/organizations/front-team/personal-healthcare-portal/activity
-
Once the build of "master" is successful, verify that the application version is deployed on DEV
- Home page has changed: http://personal-healthcare-portal-dev.cfapps.io/
- Application version is a snapshot: http://personal-healthcare-portal-dev.cfapps.io/actuator/info
-
Release the application (
mvn release prepare release:perform
): https://cd.wordsmith.beescloud.com/teams-front-team/blue/organizations/front-team/personal-healthcare-portal-release/activity- "Can't release project due to non released dependencies" <-- check
-
Verify in production the current deployed version:
-
Trigger new deployment in production
- https://cd.wordsmith.beescloud.com/teams-front-team/job/front-team/job/personal-healthcare-portal-deploy-to-production/
- Go to the interactive input and enter the desired version number
-
Verify in production the new deployed version:
-
Last: demo a cross pipeline trigger