[🏗️] CI/CD on GitHub Actions

[bkimminich]

CI/CD on GitHub Actions

The goal of this task is to get as much of the current Travis-CI pipeline running on GitHub actions as a fallback in case we need to drop Travis-CI entirely. See Background below for details.

Builds (on regular push and for pull requests)

• Installing application
• Linting
• Unit tests
• Integration tests
• E2E tests
• Smoke tests

Additional steps (not for PRs)

• Publish coverage data to Codeclimate
• Docker image building (only for develop and master)
• Docker manifest publishing (only for develop and master)
• Deployment to Heroku (only for develop and master)
• Gitter notification
• Slack notification

Deployments (for tag pushes on master)

• Installing application in production mode
• Build pre-packaged distributions
• Attach packages to GitHub release
• Docker image building
• Docker manifest publishing
• Mirror attachments to SourceForge (❌ Currently not working due to issues with looking up an existing draft release!)

Background

Two weeks ago my account on Travis-CI ran out of credits which were introduced in their new billing model https://blog.travis-ci.com/2020-11-02-travis-ci-new-billing. I immediately asked for receiving OSS credits to be still able to run build jobs for free. The approval of those credits is pending since then, and while Travis-CI support was very friendly and also added 50.000 additional credits to my account, CI/CD for Juice Shop is not back to normal yet. The complex nature of our build matrix with 3 OS, 3 NodeJS versions and 2 processor architectures during testing and releasing makes Juice Shop eat up those build credits like candy:

I'm confident that eventually, OSS credits for Juice Shop will be granted. What I do not know is, if the amount of credits will be sufficient for our current build setup. I also do not know when this will happen. Until then, our CI/CD pipeline is offline. That means I can't confidently merge PRs unless I'd verify them manually, which eats up time unnecessarily.

[github-actions]

This thread has been automatically locked because it has not had recent activity after it was closed. 🔒 Please open a new issue for regressions or related bugs.