https://blog.kgol.xyz/en/tags/gcp/Recent content in GCP on KGOL-BlogHugo -- gohugo.ioen©2025, All Rights ReservedFri, 29 Jul 2022 00:00:00 +0000https://blog.kgol.xyz/en/posts/gcp-cloudbuild-results/Fri, 29 Jul 2022 00:00:00 +0000Fri, 29 Jul 2022 00:00:00 +0000https://blog.kgol.xyz/en/posts/gcp-cloudbuild-results/Pass results directly from a Cloud Build pipeline without storing/retrieving an artifact Background The typical pattern for using a CI/CD pipeline is to provide some input (like a git repo), and the pipeline will perform a combination of commands such as API calls or software compilations. By the end, the pipeline may produce some ‘artifact’. This could be the compiled software binary, X-as-Code State, or a log file. Google Cloud Build is a managed ‘serverless’ CI/CD pipeline service allowing you to run pipelines without the need to maintain any infrastructure and only pay for the compute over the time the pipeline is running.Kieran Goldsworthyfeatured imageGCPCI/CDMan Pageshttps://blog.kgol.xyz/en/posts/interesting-bits-2/Fri, 10 Jan 2020 00:00:00 +1100Fri, 10 Jan 2020 00:00:00 +1100https://blog.kgol.xyz/en/posts/interesting-bits-2/GCP Console Bugs 1 Google Cloud Platform (GCP) has a service called storage which can be useful for hosting static websites. Simply create a ‘bucket’ with the name of your domain (e.g. example1.com) and update your DNS for that domain to be a CNAME pointing to ‘c.storage.googleapis.com’. Navigating to your domain will then server the index.html file at that path in th bucket. I stumbled across a bug almost right way however.Kieran Goldsworthyfeatured imageGCPInteresting Bits