Closed Bug 1613776 Opened 6 years ago Closed 6 years ago

Normandy v1.130.0

Categories

(Cloud Services :: Operations: Normandy, task)

Product:
Cloud Services
Component:
Operations: Normandy
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: ttran, Assigned: brian)

Details

  • PR 2041: Update dependency webpack-cli to v3.3.10
  • PR 2076: Update babel monorepo to v7.8.0
  • PR 2080: Update dependency karma-firefox-launcher to v1.3.0
  • PR 2065: Update python:3.7-slim Docker digest to 2053d75
  • PR 2077: Update dependency eslint-import-resolver-webpack to v0.12.1
  • PR 2078: Update dependency eslint-plugin-import to v2.20.0
  • PR 2079: Update dependency gh-pages to v2.2.0
  • PR 2082: Update babel monorepo to v7.8.3
  • PR 2085: Update dependency uuid to v3.4.0
  • PR 2083: Update dependency ajv to v6.11.0
  • PR 2084: Update dependency eslint-plugin-react to v7.18.0
  • PR 2086: Update python:3.7-slim Docker digest to 7e256b4
  • PR 2088: Update python:3.7-slim Docker digest to 3625a9b
  • PR 2089: Update dependency @babel/core to v7.8.4
  • PR 2090: Update dependency eslint-plugin-import to v2.20.1
  • PR 2091: Update dependency eslint-plugin-react to v7.18.3

Version v1.130.0

PRs merged since v1.129.0

None

Dependency updates

Migrations

None

Given that it's been a long time since we've ran a Full Functional test suite for Normandy, we've started a run and will leave a comment with the sign-off once we finish.

We have finished running the Normandy - Full Functional suite.

QA’s recommendation: GREEN - SHIP IT 🚢

Reasoning:

  • We have logged one enhancement during testing, but this scenario is most likely not tied to this deploy and moreover it would be quite unlikely to happen.

Testing Summary:

  • Normandy - Full Functional test suite: TestRail;
  • We have also managed to verify the full end to end flow by creating an experiment in the Experimenter (Stage) website, send it to Normandy, publish it and seeing the status change on the website, disable it and seeing the status change once again. Using the pref-flip, addon-experiment, and staged-rollout Experimenter actions.

Tested Platforms:

  • Windows 10 x64;

Tested Firefox versions:

  • Firefox Release 72.0.2
  • Firefox Release 73.0

Regards,
Ciprian

This is now in production.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.