#release-engineering (2021-01)

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

CI/CD Discussions

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

2021-01-30

2021-01-28

Andrey Nazarov avatar
Andrey Nazarov

What do you think about tagging every commit landed to master ? In other words, whenever a new commit is merged/pushed to master a new version of the app is created.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
cloudposse/terraform-aws-eks-cluster

Terraform module for provisioning an EKS cluster. Contribute to cloudposse/terraform-aws-eks-cluster development by creating an account on GitHub.

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

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
cloudposse/terraform-aws-eks-cluster

Terraform module for provisioning an EKS cluster. Contribute to cloudposse/terraform-aws-eks-cluster development by creating an account on GitHub.

Andrey Nazarov avatar
Andrey Nazarov

Yes. I’m pro-tagging and we are tagging every new commit in master for all infrastructure code we have where applicable whether it’s a module or a helmfile. My question was more about apps and microservices, because when it comes down to microservices developers sometimes don’t want it to be like that. I thought I read a discussion about pros and cons of tagging every commit somewhere here in Cloud Posse’s slack. However I might be wrong, probably it was elsewhere, because I couldn’t find it. That’s why I asked)

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

Hrmmm I know we have talked about our philosophy on it, but not necessarily in relation to micro services.

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

Personally I don’t see a difference.

Andrey Nazarov avatar
Andrey Nazarov


Personally I don’t see a difference.
Neither do I. Thanks for pointing out your docs! Haven’t seen it before. Interesting.

2021-01-27

Igor Rodionov avatar
Igor Rodionov

Hello. Does anyone use Github deployment API ?

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)
Patrick Jahns avatar
Patrick Jahns

@Igor Rodionov - I am using it since about a week for a project. We currently use the deployment api to trigger a github action that performs a deploy on the environment.

I am considering to try https://deliverybot.dev/ - however don’t have the time yet to deploy it. If anyone has experiences or alternative solutions, that would be great

deliverybot

Simple Continuous Delivery for GitHub

loren avatar
loren

TIL about make …. can’t normally override target-specific vars from envs through a sub-make:

$ cat Makefile
foo: FOO ?= foo
foo:
        @echo "[[email protected]]: FOO=$(FOO)"

test:
        @echo "[[email protected]]: FOO=$(FOO)"
        @$(MAKE) -s foo

$ FOO=bar make test
[test]: FOO=bar
[foo]: FOO=foo

If you want that to work, you have to export the target-specific var:

$ cat Makefile
foo: export FOO ?= foo  ## <==== only change!
foo:
        @echo "[[email protected]]: FOO=$(FOO)"

test:
        @echo "[[email protected]]: FOO=$(FOO)"
        @$(MAKE) -s foo

$ FOO=bar make test
[test]: FOO=bar
[foo]: FOO=bar
1
3
MattyB avatar
MattyB

I was getting ready to do something very similar…thanks for the insight

loren avatar
loren

my pain, your gain! took me literally all day to figure out

loren avatar
loren

of course i was starting with a much more complex Makefile, and went down a lot of weird rabbit-holes first…

loren avatar
loren

i eventually found this link, which has terrible formatting and may be a copy of an original, but it talks about these kinds of gotchas… https://www.cmcrossroads.com/article/basics-getting-environment-variables-gnu-make

The Basics: Getting environment variables into GNU Make

The most basic rule of GNU Make and the environment is that any variable set in the environment when GNU Make is started will be available as a GNU Make macro inside the Makefile.

2021-01-08

2021-01-07

hairyhenderson avatar
hairyhenderson
08:29:44 PM

@hairyhenderson has joined the channel

2021-01-06

2021-01-04

loren avatar
loren

would folks be interested in a build-harness pr that runs the init logic automatically? been playing with it in my own project, and seems to work. kinda abusing the include directive

jose.amengual avatar
jose.amengual

init…..as terraform init or…..

loren avatar
loren

oh sorry, make init, from the build-harness bootstrap

jose.amengual avatar
jose.amengual

yes that sounds good

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

possibly - what does it look like?

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

my main concern is that it should error gracefully if the user doesn’t have make

loren avatar
loren

Found a bug in my patch, so not quite ready. But the user still needs make as a prereq. I’m not addressing that… Just, if you run make foo without first invoking make init then it will handle the clone for you. I should have something tomorrow. Cards on the table, it’s reasonable straightforward but may not be pretty, so definitely hoping to spark discussion and simplify logic, or clean it up or work out a use case I missed…

Matt Gowie avatar
Matt Gowie

I’m interested in this. I’ve thought about this before and figured it was possible with some extra make-fu.

loren avatar
loren

i got derailed yesterday with a customer (dang that paid work!)… trying to get back to it today…

1
loren avatar
loren

@Erik Osterman (Cloud Posse) @Matt Gowie @jose.amengual pr open… https://github.com/cloudposse/build-harness/pull/272

Adds auto-init capability using the bootstrap include directive by lorengordon · Pull Request #272 · cloudposse/build-harness

what These changes will automatically run the make init workflow, and keep the clone up-to-date with the target branch/tag. why People on my team kept forgetting to run make init, and it proved suf…

1
1
    keyboard_arrow_up