...
The below image shows the difference between publishing and pushing work to Git. Publishing adds the work to the developer’s cloud, while committing the work to Git kicks off the build process.
...
| Note |
|---|
Work that you publish to your container will be removed from the container each time you start it. The work will still be in your folder on your workstation, so it is not lost. This just means that you will need to republish it to add it back to your container. As this is the case, EmpowerID recommends that you commit your work to Git often. |
The build process takes the EmpowerID stock image, overlays it with the custom work on a developer’s workstation and creates a new image from it. The new image is added to the container registry. Once the image is added the container registry, it can then be deployed to the dev environment automatically or ad-hoc as needed. This process takes about 10 minutes to complete. Once the build has completed, other members of the development team can then pull that image.
...
Moving builds
Every time a developer builds a new image (commits to Git), that developer is capturing code from that point in time and the resulting image is given a tag. While in the development environment, image rotation can occur very quickly. At some point, the team is going to decide that development is complete enough to promote to testing. When this is the case, they pick the relevant tag and promote it to UAT, where it is tested. Once testing is complete and the build is validated, it can be released to production.
...