| commit | 4bfedc4222b8476ac1cd5411f35fe621a9e386a3 | [log] [tgz] |
|---|---|---|
| author | Simon-Lii <s696li@uwaterloo.ca> | Fri Apr 08 23:08:44 2022 +0000 |
| committer | Simon-Lii <s696li@uwaterloo.ca> | Mon Apr 11 23:52:02 2022 +0000 |
| tree | 0e7545ae416d17bdaa6df04ddb1df2eeacbb827c | |
| parent | b2e1b50d92b96fb2e16d0d142fa8d9961ecd842f [diff] |
Add git clone, gcloud sdk and builder Dockerfile This adds the Builderfile, Gcloudfile and Gitfile. They are called GIT_CLONE, GCLOUD and BUILDER toolchain images on the yaml configuration file. Signed-off-by: Simon-Lii <thesimonli@google.com> Change-Id: I2d9e7e85a823601342b86c3bf1a4b23d9aabd0ca
This application provides the scripts and configuration files to Google Cloudbuild, a CI pipeline on Google Cloud Platform that performs builds. GCB's purpose is to build openbmc image releases.
Python is the main language used. With Python, it is possible to perform shell scripting whilst leveraging Python's Object Oriented Programming capabilities. This allows for unit tests to be integrated very easily, allowing for better code maintainability.
Different Docker containers are used to perform tasks that require a specific environment. These Docker images are stored on Google Cloud Registry.
Artifacts left by the build are stored on Google Cloud Storage.
This application is configurable through substitution variables (environment variables) on Google Cloudbuild's User Interface.
The detailed instructions for this project can be found here
In summary, to perform a build, the user runs a manual trigger. This trigger is setup in advance.
The trigger setups up the following:
The user can run at most 10 builds at the same time.
The artifacts for the builds are located in Google Cloud Storage in the appropriate bucket setup in advance.
An example GCS url: gs://my-release-bucket/my-machine/my-version/