4 ms·
Could this be used as a more general CI service without deploying docker containers as the end result? For example to build a C++ project, run tests, and publi
by ProblemFactory 10y ago
Could this be used as a more general CI service without deploying docker containers as the end result?
For example to build a C++ project, run tests, and publish resulting artefacts (binaries, tarballs) in some release repository?
- skj 10y agoAbsolutely. Under the covers, GCCB is an arbitrary execution engine - we run a series of containers for you. On top of that, we provide a lot of nice dressing to make it convenient and easy to build containers. https://cloud.google.com/container-builder/docs/api/build-steps https://cloud.google.com/container-builder/docs/api/build-st... and https://cloud.google.com/container-builder/docs/api/custom-build-steps https://cloud.google.com/container-builder/docs/api/custom-b... are documentation on how to use and create your own custom build steps. Additionally, your build steps have access to the credentials of the service account used to run your build, so pushing to Cloud Storage, for instance, is straightforward (use the gsutil build step).