#release-engineering (2020-06)

jenkins_ci All things CI/CD. Specific emphasis on Codefresh and CodeBuild with CodePipeline.

CI/CD Discussions

Archive: https://archive.sweetops.com/release-engineering/

2020-06-30

joshmyers avatar
joshmyers

Hey folks - any appetite for https://github.com/cloudposse/github-status-updater/pull/11 ? I’m in need of a github PR status updater that supports GHE

Github enterprise and ssl insecure support by nicolas-lopez · Pull Request #11 · cloudposse/github-status-updater

Added 3 new options in order to support Github Enterprise and insecure ssl connections Options for Github Enterprise (works as a pair) : -baseURL string Base URL of github enterprise -uploadURL st…

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

merged but binary not created - going to fix action

Github enterprise and ssl insecure support by nicolas-lopez · Pull Request #11 · cloudposse/github-status-updater

Added 3 new options in order to support Github Enterprise and insecure ssl connections Options for Github Enterprise (works as a pair) : -baseURL string Base URL of github enterprise -uploadURL st…

1
:--1:1
Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

new release cut and migrated to github actions

joshmyers avatar
joshmyers

Thanks @Erik Osterman (Cloud Posse)!

joshmyers avatar
joshmyers

Failing that, anyone know a single go binary similar to https://github.com/cloudposse/github-status-updater (Would be nice to have functionality to comment on a PR too)

cloudposse/github-status-updater

Command line utility for updating GitHub commit statuses and enabling required status checks for pull requests - cloudposse/github-status-updater

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

going to get our github actions for this setup

cloudposse/github-status-updater

Command line utility for updating GitHub commit statuses and enabling required status checks for pull requests - cloudposse/github-status-updater

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

our travis has been causing us problems and no longer works.

joshmyers avatar
joshmyers
cloudposse/github-commenter

Command line utility for creating GitHub comments on Commits, Pull Request Reviews or Issues - cloudposse/github-commenter

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

btw, new release cut - updated to use github actions

cloudposse/github-commenter

Command line utility for creating GitHub comments on Commits, Pull Request Reviews or Issues - cloudposse/github-commenter

2020-06-26

2020-06-25

DJ avatar

Question: Are there any best practices out there for managing database dependencies as part of the build and deploy pipeline? For example:

• A team is using Dynamo and need to pre-populate it with some data as part of the initial deploy

• A team is working with SQL in RDS and needs to add a new table with a particular release Looking for ideas on how to keep the database dependencies synced with the code as we roll out releases. Appreciate any help!

Steven avatar
Steven

For the second one, all schema changes should be part of the code base. You can use tools like alembic and flyway to apply the changes during release

:--1:1
roth.andy avatar
roth.andy

Liquibase has been a life saver for me

:--1:2
Andrey Nazarov avatar
Andrey Nazarov

We are also using Liquibase for our Java apps.

:--1:1
Chris Fowles avatar
Chris Fowles

on the second item - we’ve recently started treating the database as a separate item with it’s own version and our legacy monolith depends on a database version

Chris Fowles avatar
Chris Fowles

while it seems counter intuitive, with our monolith deploy times are too lengthy to quickly roll a fix forward, so we need to be able to roll back

Chris Fowles avatar
Chris Fowles

by decoupling the database deploy it means we can roll back a version safely, as our code supports vCurrent and vNext of the database

Chris Fowles avatar
Chris Fowles

previously we were finding that roll backs during an outage event were taking too long because we were trying to confirm if database changes would be destructive

1
:--1:1
DJ avatar

We have a monolith now, but the “plan” is to move to smaller services that all maintain their own system of record.

Tim Birkett avatar
Tim Birkett

Similarly our teams separate data migrations from application deployment. Some migrations take a long time… which brings up other questions…

2020-06-23

wannafly37 avatar
wannafly37

It seems like everytime I run a codebuild build from the UI by pressing the Start Build button it starts 2-3 instances of the build, anyone experience the same?

    keyboard_arrow_up