From 4e6b6fd1e60e37109228cc380d6d55ad73f8efa5 Mon Sep 17 00:00:00 2001 From: Mahdi Azarboon <21277296+azarboon@users.noreply.github.com> Date: Sun, 6 Oct 2024 15:01:10 +0800 Subject: [PATCH 1/2] Update 2018-08-06-serverless-cicd-jenkins.adoc --- .../blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc b/content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc index c7cba1096e96..2a1a04c9e884 100644 --- a/content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc +++ b/content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc @@ -60,3 +60,10 @@ The best part is that, in the true spirit of open source, Anubvha shared the cod link:https://github.com/anubhavmishra/hello-oscon[here]. So you can give it a try yourself and build your own serverless CI/CD pipeline with Jenkins. +However, it’s worth noting that Jenkins is not limited to a specific AWS service. In fact you can use Jenkins to deploy your entire serverless environment. As a best practice, make sure that each of followings have their own repository and deployment pipeline: +* Ephemeral environment and all its associated ephemeral resources such as AWS Lambda, Fargate, etc. This ensures that they can be deployed and rolled-back at the same time making it easier to spin-up and discard the ephemeral environment +* Shared resources with long spin-up time e.g. AWS RDS cluster. This way, your ephemeral environments can use the same resource which makes their deployments faster and cheaper +* Shared infrastructure resources such as VPC and subnet, also known as landing zones. Usually these resources are managed by a separate platform team + + + From 76c363ce56616fd88ad6525334f3490b0f2a20f5 Mon Sep 17 00:00:00 2001 From: Mahdi Azarboon <21277296+azarboon@users.noreply.github.com> Date: Sun, 6 Oct 2024 15:06:59 +0800 Subject: [PATCH 2/2] Update 2018-08-06-serverless-cicd-jenkins.adoc --- content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc b/content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc index 2a1a04c9e884..eb81344773ea 100644 --- a/content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc +++ b/content/blog/2018/08/2018-08-06-serverless-cicd-jenkins.adoc @@ -61,6 +61,7 @@ link:https://github.com/anubhavmishra/hello-oscon[here]. So you can give it a try yourself and build your own serverless CI/CD pipeline with Jenkins. However, it’s worth noting that Jenkins is not limited to a specific AWS service. In fact you can use Jenkins to deploy your entire serverless environment. As a best practice, make sure that each of followings have their own repository and deployment pipeline: + * Ephemeral environment and all its associated ephemeral resources such as AWS Lambda, Fargate, etc. This ensures that they can be deployed and rolled-back at the same time making it easier to spin-up and discard the ephemeral environment * Shared resources with long spin-up time e.g. AWS RDS cluster. This way, your ephemeral environments can use the same resource which makes their deployments faster and cheaper * Shared infrastructure resources such as VPC and subnet, also known as landing zones. Usually these resources are managed by a separate platform team