Production Environment
Initially, the BAM Phoenix API and AngularJS was one repository. In the 1712-Steve batch iteration, this project has been split into two. This repository now just contains the API while the Angular portion is now apart of the janus-webapp.
Here is a diagram of our pipeline. Note that with two different projects, there are two different jobs but both utilize the same pipeline.
The C.I. uses two different GitHub repositories. The first repository, BAM-Phoenix contains the API. The pipeline uses the 1712-api-dev branch and any changes that are approved and merged (via a pull request). This will trigger a build on jenkins via webhook from GitHub. The second repository, janus-webapp contains the Angular portion. The pipeline uses the 1712-bam-dev branch and any changes that are approved and merged will not trigger a build on jenkins. This was manually done by the git master, I recommend having a timed build. For example, every midnight at 12:00am do a jenkins build. Particularly our pipeline utilized the environments.uat.ts to build the angular project.
The C.D. allows us to interact with our application. Both the API and the Angular portion were deployed into the same EC2. Please see below for the link. Note both projects were packaged into a jar for deployed.
As of February 26, 2018, there were approximately 40 API deployments and 20 Angular deployments.
Url: http://34.238.156.119:8080/
User: 1712-steve
Pwd: ***
As of February 26, 2018; There is no production ready BAM available. The 1712-Steve batch did have a running development deployment.
The API is located at this address (if still available):
http://18.219.59.193:9001/api/v1
The Angular portion is located at this address (if still available):
http://18.219.59.193:8088/#/Bam/home