Stop CodePipeline from triggering on every GitHub commit/push

Question

When I was first tried out CodePipeline to integrate with GitHub repository, it created a connection with a GitHub app, and the pipeline executes whenever new commits are pushed. That was fine for learning the basics, but now we want to implement a regular build schedule instead (e.g. build every midnight). It seemed rather straight forward enough to define a CloudWatch Events rule with that schedule.  
  
But, I can't find any means to _stop_ the pipeline from reacting to each and every push? The CodePipeline setup console uses GitHub v2 provider, and it shows nothing about trigger conditions.  
  
It appears the webhook method is only applicable to GitHub v1 provider? Don't see anything controllable from GitHub side either.  
  
https://docs.aws.amazon.com/codepipeline/latest/userguide/appendix-github-oauth.html#update-change-detection-console-github  
  
How does the GitHub v2 provider interact with GitHub repository under the hood? And how to control it?

Accepted Answer

Earlier this year (2021), a new option was added to CodeStar Connection-based source actions for CodePipeline - this option now allows you to prevent triggering of the CodePipeline on git commits.  
  
In the console, the option can be found when creating or editing a Source Actions that is attached to a Bitbucket, GitHub (Version 2), or GitHub Enterprise Server source provider.  Under the section named “Change detection options” the option is exposed as a “Start the pipeline on source code change” checkbox.  
  
In the SDK/CLI, this option is known as “DetectChanges”.  More information can be found @ https://docs.aws.amazon.com/codepipeline/latest/userguide/action-reference-CodestarConnectionSource.html#action-reference-CodestarConnectionSource-config

Answer

Testing out another pipeline with _BitBucket_ (because eventually our actual team projects are hosted there), and looks like BitBucket source action has the same deficiency. Not good.  
  
Edited by: icelava on Oct 31, 2020 4:45 AM

Answer

Multiple AWS staff have informed me via other channels that indeed the current GitHub/BitBucket integration feature set lacks this functionality. The exposure of the underlying event rule (for control) will be implemented in future versions.

Answer

GithubActions have a really nice fine grain control when events are fired.  Maybe a combination of that and an S3 SourseAction might solve your issue.

Answer

Looking at the nature of the underlying (CodeStar?) connection that CodePipeline relies on,  
  
https://docs.aws.amazon.com/codepipeline/latest/userguide/action-reference-CodestarConnectionSource.html  
  
_Note_  
_For a CodeStarSourceConnection source action, you do not have to set up a webhook or default to polling. The connections action manages your source change detection for you._  
  
Well, what happens if we don't want the action to do its own thing? - to make it scheduled execution instead?

Stop CodePipeline from triggering on every GitHub commit/push

Contenus pertinents