-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[jjbb] for scheduling e2e jobs #418
Conversation
@@ -0,0 +1,61 @@ | |||
#!/usr/bin/env groovy |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Quite basic pipeline to only checkout the source code and notify the status in slack/email.
TBC in a follow up
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures
|
Co-authored-by: cachedout <mike.place@elastic.co>
I'll merge this PR now since it's not tested in the CI but creating the required jobs (JJBB) |
…a-fleet-heartbeat-synthetics-e2e-tests * upstream/master: [jjbb] for scheduling e2e jobs (elastic#418) docs: release notes for beta.17 (elastic#415) 1.0.0-beta.17 feat: add --playwright-options (elastic#405) fix: ensure timestamps of events are inorder (elastic#413) fix: do not stash `.nvm` folder (elastic#414) deprecate suite-params option over params (elastic#406) fix: end timestamp should reflect duration (elastic#410) docs: release notes for 1.16.0 (elastic#403) 1.0.0-beta.16 fix: revert Playwright to 1.14.0 (elastic#402) docs: release notes for beta 15 (elastic#400) 1.0.0-beta.15 chore: update deps and fix lint issues (elastic#399) fix: handle page close during response event (elastic#398) chore: require node > 14 for usage (elastic#397) fix: fix megabytes to mbps (elastic#394) feat: enable trace as part of rich-events (elastic#387) feat: use events from PW for network data (elastic#372)
What
Create the JJBB definition (aka the Jenkins UI jobs) for:
Create the e2e pipeline skeleton, the implementation for what to run to be done in a follow up.
Why
It was requested to create a scheduled execution of the new E2E twice a day and notify in slack the outcome.
Further details
I decided to enable a Multibranch Pipeline to be able to test the pipeline manually if needed on a PR basis. It will only be triggered automatically on a daily basis (twice).
In my experience, Multibranch Pipelines help to iterate faster since we can work on a PR basis.
Notifies
#417 and #393