https://platformengineering.org logo
#general
Title
# general
p

Pieter

05/16/2023, 2:05 PM
I am curious if some of you have found a good way to provide a standard set of ci/cd templates via github actions without it ending in tears
t

Tomek Fiechowski

05/16/2023, 2:45 PM
Hello Leon! I found these videos good balance between high level with some insights on certain Platform engineering areas. In my opinion, they set a good outlook on why Platform matter and explains why product mindset is important while building one.

https://www.youtube.com/watch?v=4N2ywun-wTE

https://www.youtube.com/watch?v=52ht63dMQ1g

a standard set of ci/cd templates via github actions without it ending in tears
By CI/CD templates - do you mean only the pipelines definition or service templates (eg. containerised backend app with a database provisioned by default) as well?
p

Pieter

05/16/2023, 4:54 PM
@Tomek Fiechowski I'm just trying to figure it all out at the moment as to what this means in a medium / large corporation
z

Zachary Zaro

05/16/2023, 5:35 PM
not to just plug our own product @Pieter but I'm curious if something like https://www.withcoherence.com/ would help you with sharing best practices across projects without copy/pasting tons of templates
r

Rob Burger

05/17/2023, 7:45 AM
Hey @Pieter! I can speak from a small org size (±20 devs) what we found with GitHub Actions was being able to provide workflow templates that give teams a "golden path" for their apps/services. We're still in the process of moving to an actual IDP, but we try to encourage them not to stray too far from the standard way we do things for the meantime. Specifically, we have a repo with all our (versioned) action workflows in a
.github/workflows/
directory that trigger on
workflow_call
and have
inputs
and
secrets
that can be passed in. This allows teams to create their own workflows in other repos that simply "call" the shared workflow with inputs and secrets. e.g.
Copy code
uses: org-name/repo-name/.github/workflows/build-deploy-v1.yml@master
with:
  input-name: "value"
secrets:
  secret-name: "value"
Works pretty well for us at this scale 🙂 happy to share details! (Might even write up post on our blog soon for the general public...)
7 Views