#release-engineering - October 2019

Create Jenkinsfile to deploy UI code to S3 bucket.

does anyone here use the serverless framework? If so, do you have a CICD pipeline for it(looking for a way to do automated rollbacks upon failure, manual gates for going to prod etc)

We implemented this with Codefresh

We used approval steps for gates

And implemented unlimited staging environments

@Andriy Knysh (Cloud Posse) can share more

@Adam is one happy camper

@Adam has joined the channel

@Andriy Knysh (Cloud Posse) 👆️🏻 I'd love to hear more about this. 😉🙏🏻

i understand 🙂 this is in a private repo implemented for a customer. We need to discuss with @Adam how to share it

@Brij S we use the serverless framework a lot and are also struggling with CI/CD. I'd love to hear what you've come up with so far and how you're doing branching.

as of now, the best ive got for you is to use github actions and codepipeline 😓

its definitely not the best idea, but it 'works'

I actually jotted down some notes on serverless and CICD, it's on my list for an upcoming project coming from one of my dev teams. I'm not sure what part of CICD you're struggling with, but I think it's key to decide what resources live with what development lifecycle.

My notes aren't really good for public consumption since it's all shorthand, but, the general concept is that you should figure out the demarcation of what serverless manages, and what your other IaC manages. Then your CICD for serverless can become much easier, as it just pulls in dependencies through SSM, or CloudFormation exports, or any number of things.

Here's a link talking about this by using cloudformation exports as an intermediary: https://theburningmonk.com/2019/03/making-terraform-and-serverless-framework-work-together/

trying to wrap my head around releasing node apps vs semantic versioning (version change in package.json) and making it simple for developers. Couple ideas, but open for more:
1) with release branch - release is merging from master to release, then use https://github.com/semantic-release/semantic-release to bump version, tag git, and package
2) when developer bumps version in package.json- detect that and release then? Any tooling for this style though?

With CircleCi, we can use either a merge or a specific tag to get a release going. It can do the version bump on its own so develop doesn't have to think about it

Does anyone pay for Serverless Enterprise?

here is something that is starting to annoy me, maybe someone here knows about this problem and maybe knows how to fix it,
I just started to learn and use Jenkins shared libraries, first loving it one place to make changes in all of my multi repo env
my problem is that in every one of my builds I have pollSCM configured (mandatory), and every time I push a new change to my shared library master branch (which is configured in the Jenkins main config), every build I got starts to run
if I make changes or add new things I have to wait sometimes 1 hour before the queue clears which is not good,
Does anyone maybe know how to fix this problem??

Only solution I've found is to not use pollSCM with Jenkinfile pulled from a separate repo. Options : use web hooks from code repo only or move Jenkinsfile to code repo. PollSCM triggers on any SCM reference in the job. When the Jenkinfile and shared libraries are not directly pulled from SCM by the job, they won't trigger it

after adding @Library(value="jenkins_shared_libraries", changelog=false) _ I managed to fix the problem