#release-engineering - February 2020

Any notes on how you guys at Cloud Posse or others that manage many modules as separate repos do your release process? It would be greatly appreciated.

I see the makefile works as the runner for the unit tests which is awesome and I’m assuming happens upon merging to master for module X. But what determines module X is ready to release into an new version? A global find and replace of the old version tag to the new, run all unit & integration tests & if all pass push release?

@IckesJ we talk about it here: https://github.com/cloudposse/docs/issues/335

basically, every time you merge to master, you bump the version.

bugs = patch releases

every other release is a minor release.

major releases are milestone driven.

keep in mind that pre-1.0 has a special meaning in semver

@Julian Gindi might have some more thoughts on this.

@Julian Gindi has joined the channel

Welcome @Julian Gindi !

(he just did a big presentation at a local meetup on semver and when/how to bump versions)

IMO, the main purpose of semver is not to communicate the stability of the functionality. that's almost impossible to guarantee. even a bug fix can be a breaking change for someone else who had a workaround for that bug.

I assume that every change could be breaking for someone.

therefore, IMO the purpose behind semver is to pin software so it only changes when you expect it to.

thus, I hate it when projects don't cut a release for every merge to master.

and that's why I prefer every merge to master to have release so I can gauge our distance from the latest release.

git sha's suck for humans.

All of this I agree with, I do think you can add safety and a bit of structure to internal API’s and set rules on which services can talk to what, but it’s most powerful when used as a final “resolution” for software and being able to see how things change over time.

I have a tool to help with this process, but it’s almost identical to what Erik suggested

do you have a recording of your talk?

We do

This is awesome info guys! Thanks & would love to see/hear the recording

Here is a repo that might “automate” the boring mechanical bits of incrementing semver https://github.com/JulianGindi/auto-semver

thus, I hate it when projects don't cut a release for every merge to master. 100% @Erik Osterman (Cloud Posse)

• Recording of the whole presentation: https://vimeo.com/388711413 (including @Julian Gindi’s talk on SemVer)
• Julian’s deck and notes on SemVer: https://gindi.io/semver.html
• Industry Updates slides: https://slides.com/coreygale/west-la-devops-5-versioning#/4

Thanks @Corey Gale

No problem thanks again for all your support!

@Julian Gindi did you consider showing a github actions code snippet that can be used to automate the semver stuff with your tool?

So we have some bits and pieces, but I should 100% add something like that to the repo. My intention was to have it used with CI and it’s certainly how we use it.

we have a lot of auto-* type actions

auto-approve, auto-assign, auto-merge, auto-readme, etc

Perfect place to slot in an auto-semver

This actions library is great. I just created a couple days ago to do BulkRepoChanges & pipeline in azdo to be able to do a find and replace in files across all our tf module repos &/or run a cmd like pre-commit run -a....auto creates the branch, pr, etc...i was also wondering how you guys managed hundreds of repos. Digging in reading also brought to light dependabot, i haven't seen that before...pretty cool as well.

yea, dependabot is great and pullreminders

oh ya that is nice

@Julian Gindi - nice presentation...I like the aviation angles...I have my instrument rating & loved every second of the learning process.

@IckesJ nice! Absolutely a goal of mine to finish my private and get instrument one day! Will have to talk more… 🙂

Hi, does cloudposse/atlantis:latest supports 0.12.16 ? AFAIK it downloads any version, right ?

@Zachary Loeber has joined the channel

Thoughts? My team is finally picking up on my "dadsgarage" idea. This is my writeup so far.

What are some of the best tools to automate application deployments to Kubernetes? I was looking at Spinnaker and Jenkins X. Has to be cloud-provider agnostic

@UUB28NLDS help keep tabs! 😉

Hi, what do you use for application deployment to ECS? we use .NET core docker containers 🙂