Stop CodePipeline from triggering on every GitHub commit/push

0

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?

icelava
preguntada hace 4 años2503 visualizaciones
5 Respuestas
1
Respuesta aceptada

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

AWS
respondido hace 3 años
0

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?

icelava
respondido hace 4 años
0

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

icelava
respondido hace 4 años
0

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.

icelava
respondido hace 3 años
0

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.

respondido hace 3 años

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.

Pautas para responder preguntas