Open Bug 1532964 Opened 6 years ago Updated 3 months ago

Fix docker-worker cache scopes within mobile projects

Categories

(Release Engineering :: Release Automation, enhancement)

Product:
Release Engineering
Component:
Release Automation
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: mtabara, Unassigned)

References

Details

Johan did great work so far in enabling to build in-tree mobile docker images. Android-components is the only repository using that AFAIK.

Doing some cleanup scopes in bug 1519493, I noticed we have some potential inconsistencies across associated scopes. I'd be great if we can address these before we enable the same behavior in the other mobile repositories.

Mainly, we're now using docker-worker:cache:android-components-* regardless of their type of release (pull-request, release, etc). I'd like to switch to using:

  • docker-worker:cache:android-components-level-1 for pull-requests
  • docker-worker:cache:android-components-level-3 for other branches + releases.

Also, since we're here, should we insert a mobile keyword there to be consistent in differentianting these scopes than their gecko counterpart? So to have:

docker-worker:cache:mobile:android-components-level-{1,3} instead of our current story?

Severity: normal → S3
QA Contact: sfraser
You need to log in before you can comment on or make changes to this bug.