Set up ci - Githubissues

scout-ch / midata-cypress

2 stars 0 forks source link

Set up ci #2

Closed cleverer closed 4 years ago

cleverer commented 4 years ago

Maybe use travis, as upstream uses it as well

Todo

[x] Action checking PRs
- [x] Store artifacts (videos/screenshots)
[ ] ~~Restructure compose to allow running from images (Check here)~~ Not needed, as users of the repo of course can use the image as well…
[x] Action building the Docker image
[x] Action running the e2e-Tests
- [x] Push results to cypress.io
- [x] Maybe store artifacts (videos/screenshots). However, they'll also be on cypress.io

cleverer commented 4 years ago

Or even better Github Actions

cleverer commented 4 years ago

To have speedy runs, I propose to have a job on master (and/or tags), that builds the docker container and pushes it to github packages. Then the test only spins up those services images (hitobito itself).

carlobeltrame commented 4 years ago

Sounds good! I think we won't have too many different branches anyway, so we can use master as the single source of truth.