Adding environment variable to qa-test job to run only smoke tests
What does this MR do?
This MR passes an environment variable called QA_RSPEC_TAGS
, to qa-test
job, which takes the input as --tag smoke
.
This makes the qa pipeline to only run smoke tests in the instance where the entire suite was running for following tests
instance
praefect
decomposition-single-db
decomposition-multiple-db
The following is the time analysis on the qa-run after this change
Time taken before change | Time taken before change |
---|---|
51 mins Example Pipeline | ~26 mins Example CE QA Pipeline, Example EE QA Pipeline |
Related issues
gitlab-org/quality/quality-engineering/team-tasks#1875 (closed)
Checklist
See Definition of done.
For anything in this list which will not be completed, please provide a reason in the MR discussion.
Required
-
MR title and description are up to date, accurate, and descriptive. -
MR targeting the appropriate branch. -
Latest Merge Result pipeline is green. -
When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow.
For GitLab team members
If you don't have access to this, the reviewer should trigger these jobs for you during the review process.
-
The manual Trigger:ee-package
jobs have a green pipeline running against latest commit. -
If config/software
orconfig/patches
directories are changed, make sure thebuild-package-on-all-os
job within theTrigger:ee-package
downstream pipeline succeeded. -
If you are changing anything SSL related, then the Trigger:package:fips
manual job within theTrigger:ee-package
downstream pipeline must succeed. -
If CI configuration is changed, the branch must be pushed to dev.gitlab.org
to confirm regular branch builds aren't broken.
Expected (please provide an explanation if not completing)
-
Test plan indicating conditions for success has been posted and passes. -
Documentation created/updated. -
Tests added. -
Integration tests added to GitLab QA. -
Equivalent MR/issue for the GitLab Chart opened. -
Validate potential values for new configuration settings. Formats such as integer 10
, duration10s
, URIscheme://user:passwd@host:port
may require quotation or other special handling when rendered in a template and written to a configuration file.
Edited by Vishal Patel