Because
- The namespaces we were using to track fenix builds in Mozilla central
were incorrect
This commit
- Updates the namespaces and the files with the correct task IDs
Fixes#11647
Because
- Our iOS integration tests only test against the `main` branch even
though we are tracking release and beta branches.
This commit
- Parametrizes the iOS job in the `circleci.yml` to accept different
types of files.
- Adds a `git checkout` to checkout the specific branch that has changed
Fixes#11597
Because
- The tracking id Firefox for iOS beta were being deleted due to how
they operate their repo. The script was looking under protected branches
and a branch is only marked as protected when it is a Release Candidate.
This commit
- Checks both types of branches so we can track beta before it is a
Release Candidate.
Fixes#11479
Because
- We are tracking external firefox versions changes for the clients we
support to better test our integrations with them
This commit
- Adds Firefox for Android (fenix) Release Task ID to the external
tracking script
Fixes#11446
Because
- The title we are using for the PR can be interpreted to mean something
security related by using the word "keys".
This commit
- Changes the wording to closer reference what the PR is actually
updating
Fixes#11470
Because
- We are tracking external firefox versions changes for the clients we
support to better test our integrations with them
This commit
- Adds Firefox for iOS (fennec) to the external tracking script
Fixes#11436
Because
- We want to run certain jobs based on external dependency changes as
they happen.
This commit
- Adds firefox for android (fenix) nightly builds to our key store for
us to track and run tests against.
- Also renamed the old `fenix` key so it properly represents what they
key is tracking.
Fixes#11420
Because
- We want to run less tests per PR but maintain coverage by running
certain UI/enrollment tests only when an external firefox change has
been detected
This commit
- Adds the files and config needed to track firefox desktop versions for
us to test against
Fixes#11402
Because
- The branch that was being created did not match the branch being
pushed within our external integration script
This commit
- Fixes the branch names
Fixes#11363
Because
- We weren't force pushing to the external integrations branch and this
would cause issues if the branch was not deleted.
This commit
- Adds the change to force push to the branch
Fixes#11332
Because
- We are now able to trigger builds based on changes made to Firefox
Beta on mozilla-central. How ever, we weren't using the firefox images
from those tasks.
This commit
- Allows us to run the firefox beta tests against the recently built
version of Firefox Beta.
Fixes#11311
Because
- We want to run our Firefox Beta integration tests when we detect a new
build upstream
This commit
- Adds the configurations for this to be done
Fixes#11232
Because
- The file that stores our trracked key of the fenix taskcluster build
is a bit buried in the repo.
This commit
- Moves that file so that it is a bit easier to find.
Fixes#11277
Because
- we want to use the population sizing schemas for graphql and UI
This commit
- sets up generation of typescript schemas from the pydantic schemas
- sets up publishing the typescript schemas to npm
Because
* It would save time if we push the docker build layers from circleci to dockerhub to reuse locally
This commit
* Uses the new buildkit --cache-from flag to pull in build layers from dockerhub when applicable
* Builds all stages and pushes them with their layers to dockerhub on every merge to main
* Configures local builds to pull those layers from dockerhub
* Removes the build circle stage since each circle task will now be able to pull from dockerhub rather than the local circle docker cache
Because
* It would be nice to run the storybook publishing in parallel, and
* It would be nice to have a published storybook for a PR even if it hasn't yet got passing tests or complete test coverage
This commit
* Moves storybook publishing to a separate circle ci task
Because
* I changed the layout of the docker containers to have separate dev/build/deploy stages
This commit
* Update the circle task to build the deploy image
Because
* We split the docker image into two images, one for local dev and one for deploying to prod so that the prod one would be small ~100mb
* We should find some way to test that the deploy image is working correctly
* A good candidate is to run the integration tests against it
This commit
* Adds a new make up_prod command that sets up an environment that more closely mirrors prod ie
- Use the prod image
- Disable all the yarn watchers
* Reorganizes the dockerfile to move frontend asset building out of the dev container to increase docker cache hits for local dev
Because
* We want to shrink the size of the deployable Docker image down from its current 2.71gb(1gb compressed)
This commit
* Adds a second stage to our Dockerfile for a deploy image which is a much more reasonable 480mb(133mb compressed)
* Use deploy image for Django container in local dev compose
Because
* We want to publish Storybook builds to demo and preview component work
in nimbus-ui
This commit
* Integrates mozilla-fxa/storybook-gcp-publisher into the CircleCI flow
so that Storybooks are built and published to a Google Cloud static
site for every test run
EXP-281
fixes#3427
* Change to continuous deployment fixes#2401
* Formatting improvements
* Can't embed numbered lists I guess
* A little more explicit about what type of deployments we use
Benjamin Forehand Jr
Mike Williams
Yashika Khurana
Jared Lockhart
Les Orchard
Jon Buckley
Jared Kerim
Jared Kerim