#release-engineering - November 2019

Very cool GitHub action

Need a suggestion : We are hosting a React website on S3, deployed through Jenkins. We have a story to set the site’s environment variables at deployment time (e.g. APIs URL, Vertex Cloud Auth Server , Redirection URL, etc.) but wanted to ping you guys to see if you are doing something like this today

Anyone have trouble finding the line with abstraction in Jenkins pipeline libs? I forked someone's codebase at worked and played around with it. While it works, you have to drudge through documentation that's formatted for github which is terrible compared to typical code documentation. You (or someone) end up trying to write reusable code but end up with a bunch of one-offs (multiple docker run stages). You're forced to figure out all the variables that are set by hoping the person that wrote the documentation didn't miss anything, so you end up looking through the code to verify. I think with my current project I'm going to leave most of the logic in our pipeline.yaml and let it tell the story of how our build works instead of the Jenkinsfile. I'm pretty sure I could write a book about it or find someone else that's already gone through my grief. Just venting a bit too 🙂

@MattyB today at #office-hours I want to ask more about people’s experience with Jenkins and #kubernetes

Join us if free!

My motivation is we are starting a Jenkins project next week.

Thanks for the invite. Just registered.

That is great @Erik Osterman (Cloud Posse)
Jenkins is a swiss knife in the CI/CD world and it must be in SweetOps team's backpack

haha, yea, it was and then it wasn't 😃 it's a love/hate relationship.

but seeing as how many companies still use it, I totally agree!

yea, but in most cases Jenkins is very redundant for usual operations - build couple images and push them to registry. For this purpose I choose "free" CI tools linke Drone, GitlabCI and etc. Or if we need self managed solution - GitLab CI

But if we need some advanced logic in or pipelines - Jenkins is that we need

Updated our alpine packages repo: https://github.com/cloudposse/packages/tree/master/.github/workflows

- auto update packages (open a PR every night)

- auto label PR with each package updated (great for mono repos)

- auto clean up branches on merge

- auto assign PR for review

(all github actions)

anyone else trying mergify? started using it to auto-approve/merge prs that dependabot creates, with conditions that the required status checks pass... https://doc.mergify.io/

certainly some overlap in what it does and github actions

No, but have somethings bookmarked to achieve the same thing with actions

Want to use actions :-)

super, waiting to see what they will have in the end

yeh - i'm getting a bit annoyed at the "we're going to work on a thing" announcements

it's becoming common

I was going to try , https://github.com/cloudposse/terraform-aws-ecs-atlantis, is there anything I should know about using this repo?

we want to run atlantis in ECS

We assume you BYO Docker container

We use geodesic

BYO= ?

build your own ?

Bring your own

or I can use the one in docker registry?

Perhaps but untested

We have a more opinionated approach where by we deploy Atlantis in each AWS account we want to manage

And have a one to one correlation between AWS accounts and GitHub repos

This ensures webhooks and repos and accounts are all aligned

well we want the same

each account with it’s own atlantis

🤘

Give it a shot

but you have multiples repos per account

I guess

Join us for #office-hours if you get stuck

I have a strip-down version of the ecs-web-app module that we use for all ECS related tasks

that is very similar to what is on that repo

but this

is kinda weird

you are only allowing https/http and 53 out from atlantis ?

Have anyone try https://www.gocd.org/ ?

CircleCi seems to be having outages on weekly basis. Is this common for other CI/CD platforms?

Never used to happen. Haven't used it much in the last year. Suspect they may be going through some growing pains

We've been pretty happy with BuildKite

I'm very happy with Codefresh, when their macOS supports comes out of beta I'm planning to move our react native app over and shutdown our CircleCI account.

I don't suppose anybody has gotten these Jenkins automated upgrades working with the Docker image? We have them in our current version, but I'm looking in to moving Jenkins off of Windows and want to make sure we keep the feature.

https://wiki.jenkins.io/display/JENKINS/Automated+Upgrade

I wouldn't be shocked if I were misinterpreting this document to some extent.

for anyone who has used github actions, if I was to create a git action that had

on:
  push:
    branches:
      - master

would you think this runs when a PR is merged to master?

I basically want to run a workflow when master has a change

You can test it by creating a PR to a dummy branch.

But yeah, it will run when a PR is merged to master