Replies: 2 comments
-
Yes we do, but it's pretty simple; stages:
- e2e
cypress:
allow_failure: false
dependencies: []
before_script: []
rules:
- if: $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH
image: cypress/browsers:node12.14.1-chrome85-ff81
stage: e2e
script:
# install dependencies
- if [ -f "package-lock.json" ]; then npm ci; fi
# run Cypress tests, with dashboard key if it is set in the env vars
- if [ ! -z $CYPRESS_DASHBOARD_KEY ] && [ -f "cypress.json" ]; then ELECTRON_EXTRA_LAUNCH_ARGS="--js-flags=--expose-gc --disable-dev-shm-usage" CYPRESS_EXCLUDE_TAGS=local npx cypress run --browser electron --record --key $CYPRESS_DASHBOARD_KEY --parallel; fi
- if [ -z $CYPRESS_DASHBOARD_KEY ] && [ -f "cypress.json" ]; then ELECTRON_EXTRA_LAUNCH_ARGS="--js-flags=--expose-gc --disable-dev-shm-usage" CYPRESS_EXCLUDE_TAGS=local npx cypress run --browser electron; fi
artifacts:
paths:
- cypress/videos
- cypress/screenshots
|
Beta Was this translation helpful? Give feedback.
0 replies
-
As we use Bitbucket Pipelines, maybe it's interesting for others, how it can be defined there:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am pretty sure you at Elgentos run the testing suite via GitLab, @peterjaap? Mind sharing the configuration for it? I will most probably look into running the testing suite via Bitbucket Pipelines. I'll happily share the configuration if anyone is interested.
Beta Was this translation helpful? Give feedback.
All reactions