https://github.com/stealthybox/container-builder-github-ci-status

Google Cloud Function responds to PubSub events on the cloud-builds topic to update GitHub CI status.
https://github.com/stealthybox/container-builder-github-ci-status

ci-status cloud-build cloud-functions container-builder github-bot google-container-registry

Last synced: 6 days ago
JSON representation

Google Cloud Function responds to PubSub events on the cloud-builds topic to update GitHub CI status.

• Host: GitHub
• URL: https://github.com/stealthybox/container-builder-github-ci-status
• Owner: stealthybox
• License: mit
• Created: 2017-11-20T16:15:54.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2019-01-14T18:36:23.000Z (almost 6 years ago)
• Last Synced: 2024-08-05T20:30:02.054Z (3 months ago)
• Topics: ci-status, cloud-build, cloud-functions, container-builder, github-bot, google-container-registry
• Language: JavaScript
• Homepage:
• Size: 10.7 KB
• Stars: 23
• Watchers: 7
• Forks: 4
• Open Issues: 2
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-functions - container-builder-github-ci-status - Google Cloud Function responds to PubSub events on the cloud-builds topic to update GitHub CI status. (Cloud Functions)

README

        
# Container Builder GitHub CI connector for Google Cloud Functions

Cloud Function to use the PubSub events on the `cloud-builds` topic to update GitHub CI status.

This function is designed to work with GitHub repositories mirrored under Google Cloud Source Control named `github-${config.repoOwner}-${ghRepoName}`.

If you set this through the Container Builder build trigger UI, this will be named automatically.

## Deploy

[Generate a new token](https://github.com/settings/tokens) with the `repo:status` OAuth scope.

Set the following on `config` in [index.js](./index.js):

- `ciUser`

- `ciAccessToken`

- `repoOwner`

Deploy the cloud function to gcloud:

```

gcloud beta functions deploy setCIStatus --trigger-topic cloud-builds

```

## Behavior

CI Status **context** will be one of:

- `${projectId}/gcb: ${tags.join('/')}`

- `${projectId}/gcb: ${id.substring(0,8)}`

Use the `tags` field in your build request to name your CI.

Otherwise, it falls back to the build-GUID.

CI Status **description** will either be:

- nothing

- a join of all images to be published:  

  `gcr.io/project/image:v1 gcr.io/project/image:latest`

- above all, the duration of the build:  

  `3m 27s`

- possibly with the last-running build step and error status:  

  `3m 27s · test failure`