strong-config/node

Set up CI pipeline

chapati23 opened this issue · 2 comments

chapati23 commented

Description

As this is our first public project where GitHub is the source of truth (and not simply a GitLab-mirror as was in the past), we need to decide on the right approach for us to handle CI/CD in this context. And then implement it.

Tasks

  • Evaluate various CI approaches, add pros & cons for each approach
  • Decide for a CI approach for all @strong-config GitHub repos
  • Implement CI in a DRY and sustainable way

Possible Approaches

There are many options to choose from:

  • Keep CI in our GitLab runners but trigger from GitHub via GitHub Actions (which is unfortunately still in closed beta and I'm still on the waiting list...)
  • Use standard hosted gitlab.com runners via GitLab CI/CD for GitHub
  • Use another CI tool that is free for open source (e.g. Travis CI)
  • Maybe there are more options..
chapati23 commented

@mohoff i believe this will count as "done" after merging #5

could you do me a favor and try out some github magic and add fixes #2 to your PR description? curious to see whether that will auto-close this issue

mohoff commented

saw this too late. Yes, it's done.

CI will be further improved in #13 though