Secret Deployment Events API features for mabl
Download as PPTX, PDF0 likes186 views
The document discusses the Deployment Events API by Mabl, which uses machine intelligence to speed up bug detection and resolution during software deployment. Key features include a Chrome extension for training tests, auto-healing for broken tests, and integration with CI/CD pipelines, allowing for automated testing across multiple browsers. Resources for support, documentation, and community interaction are also highlighted.
Secret Deployment Events API features for mabl
- 1. secrets of the deployment events api
- 2. about mabl ■ uses machine intelligence to help engineers find and fix bugs faster ■ install chrome extension to train journeys (tests) in your browser ■ journeys run in the cloud in parallel. no infrastructure to manage ■ auto-healing saves time spent on fixing broken tests ■ test on multiple browsers: chrome, firefox, and IE 11 ■ new features shipped all the time. 2
- 3. agenda for today’s webinar overview ■ help resources ■ plans ■ triggers 3 deployment events api ■ native integrations ■ curl builder ■ standard flags ■ secret flags ■ parsing returned data execution results api ■ standard use ■ data out ■ other export options (big query) 5
- 4. resources ■ help.mabl.com ■ live chat support ■ slack.mabl.com community 4
- 5. add deployment trigger to plan ■ that allows the plan to run from a deployment event 5
- 6. deployments api ■ settings ■ pick your api ▲ deployment events ▲ execution results 6
- 7. API integrates mabl with your CI/CD pipeline 7 ■ this can be an ML signal ■ use this post-deploy ■ gate changes on pass/fail status
- 8. curl builder 8 ■ specify application / environment ■ trigger on deployments ■ run curl command from terminal to test
- 9. curl builder arguments 9 ■ -s silent ■ -u api key ■ -H headers ▲ -d data for headers ▲ JSON
- 10. curl hidden arguments 10 ■ specify plan by label --plan_labels array of strings ■ plan overrides ▲ starting URL uri string ▲ override browsers browser_types array of strings ▲ link agent link_agent_label string (agent name) ▲ run multiplier run_multiplier
- 11. what do you get back? 11 ■ deployment event ID ■ list of every plan that was kicked off ■ empty array means nothing was kicked off
- 12. execution results api ■ settings ■ pick your API ▲ deployment events ▲ execution results 12
- 13. execution results API 13 ■ using the deployment event id, poll the api ■ once mabl returns pass/fail status you can: ▲ trigger deployments to a new environment ▲ kick off notifications to key people ▲ initiate roll-back on plan failure We use it in our Jenkins plugin to show status of tests
- 14. curl builder 14 ■ Deployment event ID ■ that’s all you need
Editor's Notes
- #4: Mention Parsing the returned datain
- #6: Make sure you have the Deployment API Trigger added.
- #8: Push / roll back on plan status
- #9: https://app.mabl.com/workspaces/TncIqFsil09N6MHfJJmT5w-w/settings/apis
- #10: Advice on how to use labels and when to run. Labels: Smoke-test, end-to-end, Prod, Staging, Matthew, other names, mabl-link agent,
- #11: Advice on how to use labels and when to run. Labels: Smoke-test, end-to-end, Prod, Staging, Matthew, other names, mabl-link agent,
- #13: Getting data in and out of mabl. Here are some of the integrations we offer. I’ll talk more about using the CI / CD integrations a little later.
- #14: Advice on how to use labels and when to run. Labels: Smoke-test, end-to-end, Prod, Staging, Matthew, other names, mabl-link agent,
- #15: https://app.mabl.com/workspaces/TncIqFsil09N6MHfJJmT5w-w/settings/apis