12.1.201907140823-a6463ca184e.d1673968651 QA Issue
Process
Each engineer validates and checks off each of their assigned QA task(s).
- Check off each Merge Request changes that you've tested successfully and note any issues you've created and check them off as they are resolved.
- If a problem is found:
- Create an issue for it and add a sub bullet item under the corresponding validation checklist task. Link the issue there.
- Add the severity label
- Raise the problem in the discussion and tag relevant Engineering and Product managers.
- If a regression is found:
- Create an issue for it
- Add the severity label and the regression label
- Raise the regression in the discussion and tag relevant Engineering and Product managers.
General Quality info can be found in the Quality Handbook.
Note: If you are assigned tasks outside your normal work hours, you're not expected to work overtime. Please complete the tasks as soon as possible during your normal work hours.
Deadline
QA testing on staging.gitlab.com for this issue should be completed by 2019-07-15 10:35 UTC. After this deadline has passed, the issue will be closed automatically.
If the deadline has passed, please perform your task as soon as possible anyway (during your normal work hours). It's important that the testing is performed, even if deployment has proceeded to a later stage.
Merge Requests tested in 12.1.201907140823-a6463ca184e.d1673968651
Community contribution
Community contribution-
@eread | ADD '.git' ending to git clone with CI_JOB_TOKEN for clarity 1st contribution Community contribution ~"Documentation" -
@eread | Description of the optimized path wildcard 1st contribution Community contribution ~"Documentation" docs-only -
@iamphill | add font weight to links in wiki pages to be more distinguishable from static information 1st contribution Community contribution ~"Create" UX frontend groupknowledge ~"wiki" -
@grzesiek | Updates to php:latest Community contribution ~"Verify" devopsverify -
@filipa | Fix UI breaking on forms on Bootstrap Grid system Community contribution ~"P4" ~"S4" UI polish bootstrap4 ~"bug" frontend regression regression:11.0 ~"workflow::In review" -
@rspeicher | Update net-ssh gem to ~> 5.2 Community contribution backend ~"dependency update" -
@mikegreiling | Update mixin-deep to 1.3.2 Community contribution ~"dependency update" frontend security -
@nick.thomas | Handle all approval messages in merge chat message 1st contribution Community contribution ~"Create" approvals devopscreate groupsource code -
@dbalexandre | Improve Project API Community contribution ~"Manage" api backend ~"feature" ~"ready for review" -
@tkuah | Add documentation for customizing the auto-deploy-app helm chart by setting HELM_UPGRADE_EXTRA_ARGS
to--values my-values.yaml
1st contribution Charts Community contribution ~"Configure" ~"Documentation" ~"auto devops" docs-only -
@eread | Docs: fix typo 1st contribution Community contribution ~"Documentation" devopsplan ~"docs-fix" docs-only -
@reprazent | Externalize strings of page '/projects/new' Community contribution ~"internationalization" -
@reprazent | Externalize strings of page '/projects/new' Community contribution ~"internationalization" -
@annabeldunstone | Added css class to fix incorrect line wrap Community contribution ~"Plan" devopsplan -
@rspeicher | Fix simple_format
undefined error #60179 1st contribution Community contribution -
@axil | Fix Markdown example for PlantUML docs Community contribution ~"Documentation" ~"docs-fix" ~"docs:P4" -
@rpaik | Update index.md - Fixing a minor typo on the postgreSQL setup instructions 1st contribution Community contribution ~"Documentation" ~"docs-fix" -
@DouweM | Prevent excessive sanitization of AsciiDoc ouptut Community contribution asciidoc devopscreate ~"feature" groupsource code -
@kushalpandya | change the use of boardService in favor of boardsStore on footer for the board component Community contribution ~"Plan" devopsplan -
@fatihacet | z-index fixed for diff file dropdown Community contribution ~"Create" ~"bug" frontend -
@mikegreiling | Update lodash to 4.7.14 and lodash.mergewith to 4.6.2 Community contribution ~"dependency update" frontend security
Plan ~"Plan"
-
@tristan | Docs: Update Jira integration ~"Documentation" ~"Jira" ~"Plan" devopsplan ~"feature" ~"support-fix" -
@mdelaossa | Remove minimum required characters for fuzzy search if no trigram is used ~"P3" ~"Plan" ~"S3" backend ~"bug" customer database databasereviewed default-priority default-severity devopsplan reproduced on GitLab.com ~"search" ~"workflow::In dev" -
@ntepluhina | Resolve "Clicking edit button in a thread reply doesn’t work" ~"P2" ~"Plan" ~"S2" ~"bug" devopsplan frontend ~"group::team planning" issues merge requests regression regression:12.0 -
@fatihacet | Allow bulk update for group issues - milestones ~"Plan" backend devopsplan ~"feature" frontend issues -
@fatihacet | CE Port of Allow bulk update for group issues ~"Plan" backend ~"feature" frontend ~"group" issues -
@felipe_artur | Skip spam check for task list updates ~"Plan" backend ~"bug" devopsplan issues spam fighting -
@jarka | Port of "Create system notes for scoped labels" ~"Plan" ~"feature" labels -
@jarka | Create system notes for scoped labels ~"Plan" backend ~"feature" -
@digitalmoksha | Scope the :epic_trees feature flag to a group ~"Plan" backend ~"feature" -
@pderichs | Add endpoint to move issues in boards ~"Category::Issue Boards" ~"Plan" backend customer devopsplan direction ~"feature" internal customer -
@acroitor | Fix reply to discussion on promoted epic ~"Accepting merge requests" ~"P2" ~"Plan" ~"S2" backend ~"bug" devopsplan epics ~"group::portfolio management" ~"missed-SLO" reproduced on GitLab.com
Create ~"Create"
-
@mishunov | Resolve "Removing an image via Web IDE shows binary data" ~"Create" Deliverable ~"bug" devopscreate frontend ~"group::editor" missed-deliverable missed:12.0 ~"web ide" workflowready for development -
@ntepluhina | Starting a new discussion only on line without Draft note created on it ~"Accepting merge requests" ~"Create" ~"UX ready" ~"bug" devopscreate frontend groupsource code -
@ntepluhina | Starting a new discussion only on line without Draft note created on it ~"Create" ~"feature" frontend -
@timzallmann | Updates on success of an MR the count on top and in other tabs ~"Create" ~"feature" frontend -
@iamphill | Fixed apollo caching of the root repository file listing ~"Create" ~"feature" frontend -
@nick.thomas | Remove the GraphGL feature flag in EE too ~"Create" ~"feature" master:broken ~"workflow::In dev" -
@iamphill | Fix dropdown styling issues ~"Create" ~"bug" frontend regression -
@oswaldo | Bypass push rules for merge to ref service ~"Create" ~"P1" ~"S1" backend ~"bug" regression -
@oswaldo | [CE port] Bypass push rules for merge to ref service ~"Create" ~"P1" ~"S1" backend ~"bug" regression -
@.luke | GraphQL mutations for managing Notes (EE) ~"Create" GraphQL backend ~"design management" devopscreate ~"feature" groupknowledge -
@.luke | GraphQL mutations for managing Notes ~"Create" Deliverable GraphQL backend ~"design management" devopscreate ~"feature" groupknowledge ~"workflow::In dev" -
@dzaporozhets | Fix wrong URL when creating milestones from instance milestones dashboard ~"Create" ~"P4" ~"S4" ~"bug" devopscreate ~"feature" milestones navigation -
@iamphill | Fixed dropdown hover styles ~"Create" ~"bug" frontend -
@jboyson | Resolve "Move approval user password input from inline to a modal" ~"Create" Deliverable UI polish ~"UX ready" approvals depth devopscreate ~"feature" frontend groupsource code ~"workflow::In review" -
@mishunov | Fixed back navigation for projects filter ~"Create" Deliverable ~"P2" ~"S2" browser:chrome ~"bug" devopsmanage frontend ~"group::editor" ~"search" ~"workflow::In dev" -
@reprazent | Fetch users from Phabricator + link to issues ~"Create" Deliverable backend devopsmanage ~"feature" groupsource code ~"import" ~"importers" ~"phabricator-import" planning priority ~"workflow::In review" -
@reprazent | [EE] Set the name of a user-namespace to the user name ~"Create" ~"bug" database devopscreate routing -
@reprazent | Set the name of a user-namespace to the user name ~"Create" ~"bug" database devopscreate missed:11.10 missed:11.8 routing -
@toupeira | Open WebIDE in fork when user doesn't have access ~"Create" Deliverable ~"P2" ~"S3" backend ~"bug" ~"group::editor" ~"missed-SLO" regression regression:11.3 reproduced on GitLab.com ~"web ide"
Manage ~"Manage"
-
@manojmj | Resolve "Support emails as ID in SCIM" ~"Manage" ~"P1" ~"S2" backend ~"bug" customer devopsmanage ~"estimation:completed" ~"group::access" saml scim ~"workflow::In dev" -
@wortschi | Project list: Add text-secondary to controls container ~"Manage" ~"feature" frontend -
@manojmj | Resolve "Allow a template in a namespace which is out of the hierarchy of the Group owning the template" Deliverable ~"Manage" ~"P2" ~"S2" backend ~"bug" devopsmanage ~"estimation:completed" ~"group::measure" ~"missed-SLO" ~"project templates" -
@lbennett | Group analytics frame Deliverable GitLab Premium ~"Manage" ~"P1" analytics ~"cycle analytics" devopsmanage direction ~"feature" frontend ~"group::measure"
Verify ~"Verify"
-
@axil | Resolve "Follow-up from "Visual Review Toolbar Docs"" ~"Documentation" ~"Verify" devopsverify docs-only ~"technical debt" -
@fabiopitino | Allow ReactiveCaching to support nil value ~"Verify" backend ~"bug" feature flag ~"incident" ~"performance" -
@sarahghp | Review Tools: Add large z-index to toolbar ~"Verify" ~"bug" frontend -
@balasankarc | Add CI variable to provide GitLab FQDN ~"Category::Continuous Integration" ~"Verify" devopsverify ~"feature" ~"group::ci and runner"
Release ~"Release"
-
@dosuken123 | Fix race condition of refs/merge
competing overwrite ~"P1" ~"Release" ~"S1" ~"bug" -
@dosuken123 | CE Port: Fix race condition of refs/merge
competing overwrite ~"P1" ~"Release" ~"S1" auto updated ~"bug" -
@grzesiek | Improve performance of fetching environments statuses Gitaly n+1 ~"Release" environments ~"performance" -
@dosuken123 | Fix race condition on merge train with better exclusive lock ~"P2" ~"Release" ~"S2" ~"bug" ~"devops::release" ~"group::progressive delivery" -
@dosuken123 | CE Port: Fix race condition on merge train with better exclusive lock ~"P2" ~"Release" ~"S2" ~"bug" ~"devops::release" ~"group::progressive delivery" -
@vshushlin | Fix saving domain without certificate for auto_ssl ~"Release" UX UX debt backend ~"devops::release" ~"group::release management" ~"pages" -
@vshushlin | Remove auto ssl feature flags Deliverable ~"Documentation" Product Vision FY20 ~"Release" ~"UX ready" breadth customer ~"devops::release" direction ~"feature" frontend maturitylovable missed-deliverable missed:11.10 missed:11.11 missed:12.0 ~"pages" ~"workflow::In dev" -
@afontaine | Fix Project Badge Buttons ~"Release" ~"bug" devopscreate frontend
Geo ~"Geo"
-
@dbalexandre | Geo - Add note that Internal URL works only with a Load Balancer with TLS termination ~"Documentation" ~"Geo" -
@dbalexandre | Geo - Show why node is unhealthy in the rake task to check the health of the secondary node ~"Geo" Geo Administration ~"bug" customer+ ~"devops::enablement" ~"unplanned" -
@dbalexandre | Fix GeoNode#name backward compatibility ~"Geo" Geo Administration ~"P3" ~"Pick into 11.11" ~"Pick into 12.0" ~"S3" ~"bug" ~"devops::enablement" groupgeo regression:11.11 regression:12.0 -
@brodock | Display the amount for Hashed Storage migration/rollback correctly ~"Geo" ~"P4" ~"Pick into 12.0" ~"S4" ~"bug" customer ~"devops::enablement" groupgeo missed:12.0 -
@dbalexandre | Geo Update note about internal_url ~"Documentation" ~"Geo" -
@mkozono | Geo: Validate file transfers (attachments, LFS objects, artifacts) ~"Geo" ~"Geo : Automatic Verification" ~"Geo Verification/Accuracy"
Gitaly ~"Gitaly"
-
@johncai | Use Rugged if we detect storage is NFS and we can access the disk ~"Gitaly" auto updated ~"performance" -
@jramsay | Enable repository object pools by default ~"Gitaly" ~"workflow::In review"
Package ~"Package"
-
@nkipling | Improve navigation for Package features Deliverable ~"Dependency Proxy" ~"Package" UI polish ~"UX ready" devopspackage direction ~"feature" frontend -
@nkipling | Resolve "Improve Dependency Proxy User Interface" Deliverable ~"Dependency Proxy" ~"Package" devopspackage direction ~"feature" frontend ~"group::package" -
@nkipling | EE port of Follow-up from "Add packages_size to ProjectStatistics" ~"Package" UX devopspackage frontend ~"technical debt" -
@nkipling | Resolve "Clean up delete icons on package screens" ~"Package" UI polish devopspackage ~"group::package"
Configure ~"Configure"
-
@tkuah | EE: Clusters hierarchy CTE ~"Configure" Deliverable ~"P1" ~"feature" ~"kubernetes" ~"performance" -
@tkuah | Clusters hierarchy CTE ~"Configure" Deliverable ~"P1" database ~"feature" ~"kubernetes" ~"performance" -
@tkuah | Reduce N+1 queries in MergeRequestsController#ci_environment_status ~"Configure" Deliverable ~"P1" ~"devops::configure" environments ~"feature" ~"performance" -
@hfyngvason | Create Knative role and binding with service account ~"Configure" ~"Serverless" ~"auto devops" auto updated backend depth ~"devops::configure" ~"feature" ~"group::autodevops and kubernetes" -
@DylanGriffith | EE: Resolve "API support for group-level clusters" ~"Configure" ~"devops::configure" ~"feature" -
@DylanGriffith | Resolve "API support for group-level clusters" ~"Configure" customer ~"devops::configure" ~"feature" ~"kubernetes"
Monitor ~"Monitor"
-
@ayufan | Make unicorn_workers to return meaningful results APM ~"Memory" ~"Monitor" ~"P2" ~"S2" ~"bug" devopsmonitor ~"group::apm" ~"workflow::In dev" -
@syasonik | Expose placeholder element for metrics charts in GFM Health ~"Monitor" backend devopsmonitor ~"feature" ~"group::health" ~"incident management" -
@syasonik | Add docs on project-based dashboard config ~"Documentation" ~"Monitor" devopsmonitor docs-only ~"feature" ~"metrics" -
@rpereira2 | Correct link to external_dashboard doc APM ~"Monitor" ~"bug" devopsmonitor ~"group::apm" -
@splattael | Resolve "Improve default title and description of issues opened from managed Prometheus alerts" ~"Monitor" backend ~"category::incident management" devopsmonitor ~"feature" ~"group::health" ~"workflow::In dev"
Secure ~"Secure"
-
@avielle | Extract vulnerabilities fetch methods from Group ~"Secure" backend devopssecure ~"feature" -
@brytannia | Add policy for dependencies Deliverable Persona: Development Team Lead Persona: Security Analyst ~"Pick into 12.1" ~"Secure" ~"Secure::Software Composition Analysis" analysts api backend customer dependency list devopssecure ~"feature" ~"workflow::In dev" -
@brytannia | Filter DependencyList by package_manager Deliverable Persona: Development Team Lead Persona: Security Analyst ~"Pick into 12.1" ~"Secure" ~"Secure::Software Composition Analysis" analysts api backend customer dependency list devopssecure ~"feature" ~"workflow::In dev" -
@avielle | Make VulnerabilitiesFinder agnostic between Projects and Groups ~"Secure" backend devopssecure ~"feature" -
@caneldem | Propagate python version variable ~"P2" ~"S3" ~"Secure" ~"Secure::Software Composition Analysis" backend ~"bug" customer ~"dependency scanning" devopssecure ~"group::software composition analysis" -
@vzagorodny | "Security Dashboard unavailable" empty state ~"Pick into 12.1" ~"Secure" backend devopssecure ~"feature" feature flag frontend missed:11.10 missed:11.8 security dashboard settings -
@markrian | Add ability to sort Dependency List by Severity Deliverable Persona: Development Team Lead Persona: Security Analyst ~"Secure" ~"Secure::Software Composition Analysis" ~"UX ready" analysts backend customer dependency list depth devopssecure direction ~"feature" feature flag frontend internal customer -
@markrian | Display vulnerabilities in Dependency List Deliverable Persona: Development Team Lead Persona: Security Analyst ~"Secure" ~"Secure::Software Composition Analysis" ~"UX ready" analysts backend customer dependency list depth devopssecure direction ~"feature" feature flag frontend internal customer -
@rossfuhrman | Vulnerabilities API now takes optional pipeline_id Deliverable ~"Pick into 12.1" ~"Secure" ~"Secure::Static and Dynamic Analysis" backend devopssecure ~"feature" -
@rossfuhrman | Vulnerabilities API now supports pipeline_id Deliverable ~"Documentation" ~"Pick into 12.1" ~"Secure" ~"Secure::Static and Dynamic Analysis" devopssecure ~"feature" -
@samdbeckham | Adds a popover to vulnerability-check approvals Deliverable GitLab Ultimate Persona: Security Analyst ~"Secure" ~"Secure::Static and Dynamic Analysis" UX ~"UX ready" analysts backend customer devopssecure direction ~"feature" frontend merge requests missed:12.0 release post item -
@pgascouvaillancourt | Set unique modal IDs ~"Pick into 12.1" ~"Secure" ~"bug" devopspackage frontend -
@samdbeckham | Allows any user to comment on a dismissed vulnerability (Dismissal reason: Step 3) Deliverable GitLab Ultimate Persona: Security Analyst Persona: Software developer ~"Secure" ~"UX ready" analysts backend customer depth devopssecure direction ~"feature" frontend missed:11.11 -
@samdbeckham | CE backport for Dismissal Reasons Deliverable ~"Secure" auto updated devopssecure ~"feature" frontend
frontend
frontend-
@filipa | Removes EE differences for app/views/admin/users/show.html.haml frontend single codebase -
@patrickbajao | Fix typo on confidential MR dropdown ~"bug" forking frontend groupsource code merge requests -
@jivanvl | Support additional panel types - EE APM Deliverable backend devopsmonitor direction ~"feature" frontend ~"group::apm" release post item ~"workflow::In dev" -
@jivanvl | Support additional panel types APM Deliverable backend devopsmonitor direction ~"feature" frontend ~"group::apm" missed-deliverable missed:11.11 release post item ~"workflow::In dev" -
@filipa | Move EE differences for app/views/projects/tree/_tree_content.html.haml
frontend single codebase
database
database-
@mksionek | Add additional condition to count median properly database ~"group::measure"
uncategorized ~"uncategorized"
-
@jivanvl | Regenerate gitlab.pot file ~"internationalization" master:broken -
@syasonik | Push feature flag for embedding metrics backend devopsmonitor ~"feature" feature flag ~"group::health" -
@fjsanpedro | Fix subgroup url in search drop down Deliverable ~"P2" ~"S2" backend ~"bug" devopscreate ~"group::editor" ~"search" ~"workflow::In dev" -
@stanhu | Cache Geo checks for a certain time period instead of per request ~"Geo Performance" gitlab.com groupgeo ~"incident" -
@mksionek | Prepare cycle analytics for group level ~"Category::Value Stream Management" ~"cycle analytics" ~"feature" ~"group::measure" -
@stanhu | Format from
andto
fields in JSON audit log ~"audit events" backend devopsmanage
Automated QA for 12.1.201907140823-a6463ca184e.d1673968651
No QA job could be found for this release!
You will need to set up a dedicated environment for 12.1.201907140823-a6463ca184e.d1673968651 by following the following steps:
Prepare the environments for testing the security fixes
Instructions to prepare environment
- In Google Cloud Console (access to this
should have been granted during on-boarding), create a new VM instance (in the
gitlab-internal
project) from theqa-security-1cpu-3-75gb-ram-ubuntu-16-04-lts
instance template for each version of GitLab. - Find the
.deb
package to install:- First find the pipeline for the
12.1.201907140823+ee.0
tag in the pipelines page. - Then on the pipeline page, click the
Ubuntu-16.04-staging
job in theUpload:gitlab_com
stage (or theStaging_upload
stage for versions prior to 11.5), you will need the job ID later.
- First find the pipeline for the
- Install the
.deb
package from the job artifact:- SSH into the VM via the GCP console.
- Create a
install-gitlab.sh
script in your home folder:TEMP_DEB="$(mktemp)" GITLAB_PACKAGE="https://dev.gitlab.org/api/v4/projects/gitlab%2Fomnibus-gitlab/jobs/${JOB_ID}/artifacts/pkg/ubuntu-xenial/gitlab-ee_${GITLAB_VERSION}-ee.0_amd64.deb" curl -H "PRIVATE-TOKEN: $DEV_TOKEN" "$GITLAB_PACKAGE" -o "$TEMP_DEB" && sudo dpkg -i "$TEMP_DEB" rm -f "$TEMP_DEB"
-
$DEV_TOKEN
needs to be set with adev.gitlab.org
personal access token so that the script can download the package -
$JOB_ID
needs to be set with theUbuntu-16.04-staging
job ID -
$GITLAB_VERSION
needs to be set with the version (without the-ee
prefix, e.g.11.4.10
).
-
- Change the script's permission with
chmod +x install-gitlab.sh
. - Run the script with
./install-gitlab.sh
. - Once GitLab installed, set the
external_url
in/etc/gitlab/gitlab.rb
withsudo vim /etc/gitlab/gitlab.rb
. You can find the VM's IP in the GCP console. - Reconfigure and restart GitLab with
sudo gitlab-ctl reconfigure && sudo gitlab-ctl restart
. - You may need to wait a few minutes after the above command finishes before the instance is actually accessible.
- Set the
root
's user password:- Visit http://IP_OF_THE_GCP_VM and change
root
's password. - Once the environments are ready, capture the information to add to the QA issue.
- Visit http://IP_OF_THE_GCP_VM and change
Automated QA
Instructions to perform automated QA
-
(Optional) If the QA Docker image doesn't exist, you will need to build it manually on your machine, e.g.
# In gitlab-ee › git fetch dev › git checkout v12.1.201907140823-a6463ca184e.d1673968651-ee › cd qa › docker build -t dev.gitlab.org:5005/gitlab/omnibus-gitlab/gitlab-ee-qa:12.1.201907140823-a6463ca184e.d1673968651-ee .
-
Make sure to export the following environment variables (you can find the token under the GitLab QA - Access tokens
1Password items)-
$QA_IMAGE
the URL of the QA image -
$QA_ENV_URL
with the URL of the environment where the package has been deployed (usually https://staging.gitlab.com for the current version, andhttp://IP_OF_THE_GCP_VM
for back-ported versions). -
$GITLAB_USERNAME
withroot
. -
$GITLAB_ADMIN_USERNAME
with$GITLAB_USERNAME
. -
$GITLAB_PASSWORD
with the password you've set for theroot
user. -
$GITLAB_ADMIN_PASSWORD
with$GITLAB_PASSWORD
. -
$GITHUB_ACCESS_TOKEN
with a valid GitHub API token that can access the https://github.com/gitlab-qa/test-project project -
$DEV_USERNAME
with yourdev
username -
$DEV_TOKEN
with a validdev
personal access token that has theread_registry
scope
› export QA_IMAGE="dev.gitlab.org:5005/gitlab/omnibus-gitlab/gitlab-ee-qa:12.1.201907140823-a6463ca184e.d1673968651-ee" › export QA_ENV_URL="<QA_ENV_URL>" › export GITLAB_USERNAME="root" › export GITLAB_ADMIN_USERNAME="$GITLAB_USERNAME" › export GITLAB_PASSWORD="<GITLAB_PASSWORD>" › export GITLAB_ADMIN_PASSWORD="$GITLAB_PASSWORD" › export GITHUB_ACCESS_TOKEN="<GITHUB_ACCESS_TOKEN>" › export DEV_USERNAME="<DEV_USERNAME>" › export DEV_TOKEN="<DEV_TOKEN>"
-
-
Update gitlab-qa
if needed› gem install gitlab-qa
-
Log into the dev
container registry› docker login --username "$DEV_USERNAME" --password "$DEV_TOKEN" dev.gitlab.org:5005
-
Automated QA completed. QA can be parallelized manually (for now): # Tab 1: This should take approximately 4.5 minutes › gitlab-qa Test::Instance::Any $QA_IMAGE $QA_ENV_URL -- qa/specs/features/api/ qa/specs/features/login/ qa/specs/features/merge_request/
# Tab 2: This should take approximately 6 minutes › gitlab-qa Test::Instance::Any $QA_IMAGE $QA_ENV_URL -- qa/specs/features/project/
# Tab 3: This should take approximately 5 minutes › gitlab-qa Test::Instance::Any $QA_IMAGE $QA_ENV_URL -- qa/specs/features/repository/
-
Post results as comments of this issue -
Create Automation Triage RELEASE_MAJOR_VERSION RC#
issues for all the automated QA failures (with failures logs + screenshots) and link it to this issue
Coordinate the Manual QA validation of the release
Click for details
- Notify the Security Engineer to verify the security fixes for the release.
- The manner in which the security fixes are verified can be done in two ways.
- By the Quality Engineer executing the validation with close collaboration and guidance from the Security Engineer.
- By the Security Engineer executing the validation with the Quality Engineer monitoring the steps.
- Note: When encountered with deadline and resource constraints, the work should be assigned for efficiency. Security Engineer should own verifying complex security validations while Quality Engineer is encouraged to help out with simpler validations. However it is important that the Security team signs off on the result of the validation.
- The manner in which the security fixes are verified can be done in two ways.
- Ensure that all the items for validation are validated and checked off before moving forward.
- Hand off the release assignment.
- Once all the validation is completed, Quality Engineer un-assigns themselves from the release issue leaving only the Security Engineer and the Release Manager.
/cc @gl-quality