toricls / github-codebuild-integration Goto Github PK

I think we are going to need and env variable set before running make
export ENV_FILE_PATH=$(pwd)/env/$YOUR_PROJECT_NAME.env

I was not able to run it on my mac until I set this one, which I figured out looking into the makefile.

We're using AWS Step Functions to wait for build jobs on AWS CodeBuild to complete. Since github-codebuild-integration has built from the context of Serverless Architecture, it should be replaced with Amazon CloudWatch Events to treat build job as an "event" not a status.

To achieve that:

• Remove AWS Step Functions stuffs from the code and the CloudFormation template
• Invoke build-result-notifier Lambda function by CloudWatch Events which is associated with CodeBuild project's status changing

To show build status and its history even if viewer doesn't have any role for AWS Management Console.

Expected use-case is for open source projects or something like that.

split from #3 to make it simple

This feature could support repositories driven by GitHub/Git flow or something like that.

This would be a great feature, valuable resources are wasted when a codebuild project for an older commit on a PR is still running, the latest comment is all that really matters.

Thoughts?

To show build status badge on README

such as skip ci or ci skip

CloudWatch Logs

2019-01-04T06:00:36.687Z	0d594680-0fe6-11e9-9a88-eb8893158f5c	Response body:
 {"Status":"FAILED","Reason":"See the details in CloudWatch Log Stream: 2019/01/04/[$LATEST]13b0b45ca11744a189d233bbac77****","PhysicalResourceId":"2019/01/04/[$LATEST]13b0b45ca11744a189d233bbac77****","StackId":"arn:aws:cloudformation:ap-northeast-1:52829650****:stack/codebuild-sample/e0495320-0fe5-11e9-8940-0ec45775****","RequestId":"ccaf9c0a-3feb-4f91-afae-a260c332256b","LogicalResourceId":"GitHubWebhook","Data":{"Error":"{\"message\":\"As of October 2018, GitHub Services can no longer be added. Please see the blog post for details: https://developer.github.com/changes/2018-04-25-github-services-deprecation\\nYou can use the \\\"Replacing GitHub Services\\\" guide to help you update your services to webhooks: https://developer.github.com/v3/guides/replacing-github-services\\n\",\"documentation_url\":\"https://developer.github.com/v3/repos/hooks/#create-a-hook\"}"}}

• As of October 2018, GitHub Services can no longer be added. Please see the blog post for details: https://developer.github.com/changes/2018-04-25-github-services-deprecation
• You can use the "Replacing GitHub Services" guide to help you update your services to webhooks: https://developer.github.com/v3/guides/replacing-github-services

The GitHub Checks API is a new, rich API meant to provide CI tools the ability to provide feedback into GitHub Pull Requests.

https://blog.github.com/2018-05-07-introducing-checks-api/

Microsoft App Center and Travis CI support this today, and Circle CI is preparing to release support as well. As you look for reasons why gci can go above and beyond what codebuild does, this would be a great way to show what is possible with a top tier integration.

I want to know about build status changes without opening GitHub. Slack notification would be very handy 😃

The current way to use .env file for configuration is too poor to express more complicated or advanced parameters. e.g. arrays, sructured/typed values, maps...

We should consider to use something like YAML, TOML or JSON to represent gci's configurations.

Hi, I assume you saw this:

https://aws.amazon.com/about-aws/whats-new/2017/09/aws-codebuild-now-supports-building-github-pull-requests/

It correctly sends status back to GitHub, so I don't think this project is required anymore.

Expected status description

Actual status description