cloud-build-status | status checks with Google Cloud Build
kandi X-RAY | cloud-build-status Summary
kandi X-RAY | cloud-build-status Summary
cloud-build-status is a Python library. cloud-build-status has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.
Google Cloud Build integrates with Github and Bitbucket repositories. When a commit is pushed or a pull request is updated, a build is triggered. However, its status is not reported back to the repository.cloud-build-status provides a Google Cloud Function to perform this step. When enabled, you'll see a status icon next to your commits and pull requests. If you would like a Cloud Build badge as well (as seen above) see my other project. Note: There is now a Github app for Cloud Build, that does report a build's status. However, it doesn't mirror the Github repository to a Google Cloud Source Repository, and instead retrieves a tarball of the commit to build. There are good reasons to prefer a mirror - Cloud Build events will contain information on the repository (whereas the Github app omits some information, such as the owner of the repository). It's also been found that certain changes to the repository - say, changing the name of the repository - are not picked up by the Github app, and it can take quite a bit of work to remove and re-add the app to reflect the changes. In short, it can be preferable to have fine-grained control of the components that make up your CI/CD pipeline.
Google Cloud Build integrates with Github and Bitbucket repositories. When a commit is pushed or a pull request is updated, a build is triggered. However, its status is not reported back to the repository.cloud-build-status provides a Google Cloud Function to perform this step. When enabled, you'll see a status icon next to your commits and pull requests. If you would like a Cloud Build badge as well (as seen above) see my other project. Note: There is now a Github app for Cloud Build, that does report a build's status. However, it doesn't mirror the Github repository to a Google Cloud Source Repository, and instead retrieves a tarball of the commit to build. There are good reasons to prefer a mirror - Cloud Build events will contain information on the repository (whereas the Github app omits some information, such as the owner of the repository). It's also been found that certain changes to the repository - say, changing the name of the repository - are not picked up by the Github app, and it can take quite a bit of work to remove and re-add the app to reflect the changes. In short, it can be preferable to have fine-grained control of the components that make up your CI/CD pipeline.
Support
Quality
Security
License
Reuse
Support
cloud-build-status has a low active ecosystem.
It has 5 star(s) with 4 fork(s). There are 2 watchers for this library.
It had no major release in the last 6 months.
cloud-build-status has no issues reported. There are 1 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of cloud-build-status is current.
Quality
cloud-build-status has no bugs reported.
Security
cloud-build-status has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
cloud-build-status is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
cloud-build-status releases are not available. You will need to build from source code and install.
Build file is available. You can build the component from source.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi has reviewed cloud-build-status and discovered the below as its top functions. This is intended to give you an instant insight into cloud-build-status implemented functionality, and help decide if they suit your requirements.
- Get credentials for a given provider
- Get the ciphertext from a bucket
- Decrypt the given ciphertext using the given key
Get all kandi verified functions for this library.
cloud-build-status Key Features
No Key Features are available at this moment for cloud-build-status.
cloud-build-status Examples and Code Snippets
No Code Snippets are available at this moment for cloud-build-status.
Community Discussions
No Community Discussions are available at this moment for cloud-build-status.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install cloud-build-status
These instructions apply to both Github and Bitbucket. It's recommended that you set the following environment variables first:.
GOOGLE_CLOUD_PROJECT: the project in which cloud resources are created, e.g. my-uniquely-named-project
CREDENTIALS_BUCKET: the GCS bucket in which to store encrypted credentials, e.g. my-uniquely-named-credentials-bucket
BUILD_STATUS_KEYRING: the name of the KMS keyring, e.g. production
BUILD_STATUS_KEY: the name of the KMS key, e.g. cloud-build-status
Follow these instructions. Once you've done so, you'll have:. Make a note of the Google Cloud project you decide to use. From hereon in, all resources are configured in the context of this project.
A Github or Bitbucket repository mirrored to Cloud Source Repositories
A Cloud Build config file (e.g. cloudbuild.yaml) in the repository
A Cloud Build trigger to run a build when a commit is pushed
The function needs credentials with which to authenticate with the Github or Bitbucket API. The credentials need not be the same as that used for mirroring. Note: this step can be repeated whenever you want to rotate the credentials. There is a make task to perform the rotation: make rotate. Nominate a Github user account for this purpose. Create a personal access token. Assign it the repo:status scope.
GOOGLE_CLOUD_PROJECT: the project in which cloud resources are created, e.g. my-uniquely-named-project
CREDENTIALS_BUCKET: the GCS bucket in which to store encrypted credentials, e.g. my-uniquely-named-credentials-bucket
BUILD_STATUS_KEYRING: the name of the KMS keyring, e.g. production
BUILD_STATUS_KEY: the name of the KMS key, e.g. cloud-build-status
Follow these instructions. Once you've done so, you'll have:. Make a note of the Google Cloud project you decide to use. From hereon in, all resources are configured in the context of this project.
A Github or Bitbucket repository mirrored to Cloud Source Repositories
A Cloud Build config file (e.g. cloudbuild.yaml) in the repository
A Cloud Build trigger to run a build when a commit is pushed
The function needs credentials with which to authenticate with the Github or Bitbucket API. The credentials need not be the same as that used for mirroring. Note: this step can be repeated whenever you want to rotate the credentials. There is a make task to perform the rotation: make rotate. Nominate a Github user account for this purpose. Create a personal access token. Assign it the repo:status scope.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page