#AWS #CodePipeline supports direct pipeline-to-pipeline invocation with a new native action https://aws.amazon.com/about-aws/whats-new/2025/03/aws-codepipeline-invoking-pipeline-new-action-type/ and introduces CodeBuild and Commands rule for stage level condition https://aws.amazon.com/about-aws/whats-new/2025/03/aws-codepipeline-codebuild-commands-rule-stage-level-condition/

Some more new goodies on AWS CodePipeline/CodeBuild
• New CodePipeline console experience for viewing pipeline releases https://aws.amazon.com/about-aws/whats-new/2025/02/aws-codepipeline-console-experience-viewing-pipeline-releases/
• CodeBuild supports merging parallel test reports and new compute options https://aws.amazon.com/about-aws/whats-new/2025/02/aws-codebuild-merging-parallel-test-reports-compute-options/
• CodeBuild supports managed webhooks in GitHub Enterprise https://aws.amazon.com/about-aws/whats-new/2025/02/aws-codebuild-managed-webhooks-github-enterprise/
• CodeBuild supports managed runners for GitLab Self-Managed https://aws.amazon.com/about-aws/whats-new/2025/02/aws-codebuild-managed-runners-gitlab-self-managed/
#AWS #CodePipeline #CodeBuild

CodePipeline adds native EC2 deployment support
https://aws.amazon.com/about-aws/whats-new/2025/02/aws-codepipeline-native-ec2-deployment-support/
Previously, if you wanted to deploy to EC2 instances, you had to use CodeDeploy with an AppSpec file to configure the deployment. Now, you can simply use this new EC2 deploy action in your pipeline to deploy to EC2 instances, without the necessity of managing CodeDeploy resources. This streamlined approach reduces your operational overhead and simplifies your deployment process.
#AWS #CodePipeline #EC2

CodePipeline adds native EKS deployment support
https://aws.amazon.com/about-aws/whats-new/2025/02/aws-codepipeline-native-amazon-eks-deployment-support/
Previously, if you wanted to deploy to a EKS cluster within a private network, you had to initialize and maintain a compute environment within the private network. Now, you can simply provide the name of the cluster and add this action to your pipeline. The pipeline will automatically establish a connection to deploy your application, without additional infrastructure needed.
#AWS #EKS #CodePipeline

SUSE Hack Week is over :( But it was a great time, can't wait for 2025! Day 5 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-5.html
Lot of coding today, actually only coding the whole day :D I solved the annoying problem from yesterday and finished around 2/3 of what was planned. I hope to get the rest done in the next week or two. My Goals were probably too ambitious, as always ;)

SUSE Hack Week day 4 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-4.html
Nothing fancy today. I had to fix a couple of things in my pagure dev instance. Writing the plugin code went fine till I hit a weird issue with one of the tests that I couldn't solve yet. Overall progress was ok but I lost a lot of time with unexpected problems. Let's see what will be finished on the last day tomorrow.

Another day SUSE Hack Week, another recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-3.html
The time I could invest today was pretty limited. I focused on further Architecture improvements. And started with the pagure ci plugin implementation. It's in an early stage but I'm confident that there is more to demonstrate tomorrow.

My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

A couple bug fixes and improvements. Followed by research, tests and design decisions. SUSE Hack Week Day 2 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-2.html

I was hoping for a bit more progress today, bug hunting and planning took quite a while. Three days left, I'm still on track and confident that I have something usable at the end of the week.

I finally fixed a long annoying issue and completed two out of four goals, great first day :) SUSE Hack Week Day 1 recap: https://dominik.wombacher.cc/posts/suse-hack-week-2024-day-1.html
My Project: AWS CodePipeline CI plugin for pagure on code.opensuse.org (https://hackweek.opensuse.org/projects/aws-codepipeline-ci-plugin-for-pagure-on-code-dot-opensuse-dot-org)

My new Blog: Use a Bucket as Git repository and AWS CodePipeline source with git-remote-s3 (https://dominik.wombacher.cc/posts/use-a-bucket-as-git-repository-and-aws-codepipeline-source-with-git-remote-s3.html).

After spending a lot of time over the years creating build pipelines in #Github Actions, AWS #CodePipeline, #Bitbucket Pipelines, and #Jenkins, I gotta say I still prefer Jenkins for the ease of use, extensibility, and the expressiveness of the #Groovy DSL.

#AWS is screwing with me. Got a #CodePipeline with #CloudFormation action that deploys a #stack. Immediately after the stack and all its resources are deployed successfully it switches to cleanup, deletes all the resources and ultimately deletes the just deployed stack. I think it hates me.

Deploy stacks with CDK pipeline to regions where pipeline CloudFormation action is not supported:

https://www.npmjs.com/package/custom-stack-deployment

Source

https://github.com/ygalanter/custom-stack-deployment

cc @vincent (this is the part I was talking about: https://github.com/ygalanter/custom-stack-deployment/blob/main/src/index.ts#L64-L69)

Working on a custom stage for CDK pipelines, and made a CodeBuildStep behave like a Construct. Hacking is fun

I spent my weekend with #argocd, #eks, #codepipeline, #kustomize and all things #gitops to prepare a demo for a client. I feel worn out... But happy! Automation will always be my true passion #devops #aws