Triggering AWS codepipeline/codebuild from a scheduled lambda and blocking commit trigger

Question

I have a codepipeline using AWS codebuild building an AMI I planning on running on a weekly schedule for a fresh server image.

I want to run it as a scheduled task, I thought of using lambda scheduled tasks for that, but didn't see an option of running pipeline source from lambda (I thought of using the api from lambda for that, but I rather have a mode declarative solution using the existing tools) Does anyone know of a built in solution for that?
I DON'T want it to run on code push, how can that be enabled?

Edit: clarification

Why codepipeline? Because the task is too long for lambda. And I don't want to spin an ec2 instance for that (Billed by the hour) or keep an almost not working instance. Any other AWS tools that can handle that?

If you don't want to run on code push, CodePipeline may not be ideal for you, as it revolves around the continuous integration (CI) model, which explicitly triggers on every push. Are you dependent on CodePipeline for other reasons? Some additional detail on your rollout process might be helpful. — Unsigned
– Unsigned, Commented Jul 11, 2017 at 21:38

TimB · Accepted Answer · 2017-08-28 23:21:08Z

5

AWS CodePipeline is now available as a CloudWatch events target. CloudWatch events supports scheduling, so you can use this to automatically start your pipeline on a schedule.

An option called PollForSourceChanges was also recently added on source actions which when set to false will not start your pipeline automatically via the existing polling mechanism.

It is intended to be used in conjunction with CloudWatch events for customers who want to start their pipeline exclusively from CloudWatch events.

It sounds like a combination of these two features would suit your use-case well.

answered Aug 28, 2017 at 23:21

TimB

1,61711 silver badges10 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

gkrizek · Accepted Answer · 2017-07-14 15:52:46Z

3

You can use the CLI command disable-stage-transition (or the corresponding API call with an SDK)

You can disable Inbound transitions to your Source stage. That will force it to not watch for changes. Then you can create a Lambda function and set it to a schedule. In the Lambda function you can use the enable-stage-transition call to turn back on the source input.

If you don't care about changes in your repository at all, you never have to turn on the Inbound Source transition and simply call the start-pipeline-execution command.

answered Jul 14, 2017 at 15:52

gkrizek

1,1064 gold badges13 silver badges18 bronze badges

3 Comments

alonisser Over a year ago

Looks like an interesting solution! I'll check it out

alonisser Over a year ago

Disabling stage transition, has strange side effects, but start-pipeline-execution is the way to go. Thanks!

gkrizek Over a year ago

@alonisser can you describe the strange side effects? I have only been playing around with some tests with it

J W · Accepted Answer · 2021-02-15 13:36:53Z

0

Currently, these are the Codepipeline detection options when using Codecommit

Even though this configures the CloudWatch Events to automatically start when a change occurs, you can just log into the Cloudwatch console and disable or modify the event as you like.

Since the events can run on a schedule, you may not even need lambda

answered Feb 15, 2021 at 13:36

J W

1,39010 silver badges16 bronze badges

Collectives™ on Stack Overflow

Triggering AWS codepipeline/codebuild from a scheduled lambda and blocking commit trigger

Edit: clarification

3 Answers 3

Comments

3 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

Edit: clarification

3 Answers 3

Comments

3 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related