Consider a package whose executable is a git repository. The source code in the git repository is built into a runnable docker container. Each time you update the source code in the repository you expect the changes to be reflected the next time you deploy the package, which implies, you expect the executable to pick up the latest git commit hash of the repository. Thus, you’ll trigger a new build for the package.
When you add a package, the Builds tab displays information about the current build such as build generation number, time of build generation, name of the user who triggered the build, the status of the build, and error message if there is any.
Suppose the current build generation number is i. If you update the source code in the git repository, you may want to trigger a new build for building the same package to reflect the new code changes. As a result, a new build generation number (i+1) is generated. To trigger a new build for a package, click Trigger build.
You may always Trigger a new build irrespective of the status of the previous build. That is you can trigger a new build from either a Complete build or an Error build. However, only those builds that are Complete are suitable for provisioning. The Failed builds are unfit for provisioning.
Besides the names of the components and the executables that constitute a package, you may also view details such as the git repository URL where the source code is hosted, the latest commit SHA number, the commit message and the commit owner’s name by clicking View details/logs.
You may also Rollback to a previous build generation number if there is any, irrespective of the previous build status. Rollbacking to a previous build does not restart the build process. Instead, it would run the corresponding docker container that was created for that build generation.
The Current build generation number is shown below the package ID.
When you deploy a package, the deployment process automatically chooses the current build generation number. Once a package is deployed, the build generation number used in the deployment process is displayed adjacent to the package name.
The builds are automatically restarted on software infrastructure failures. Click Refresh if you observe that the build logs are abruptly disconnected or stopped
When a build fails, you should analyze the corresponding build logs to debug.