Closed Bug 1520540 Opened 7 years ago Closed 7 years ago

Produce python3 docker images for Balrog

Categories

(Release Engineering Graveyard :: Applications: Balrog (backend), enhancement)

Product:
Release Engineering Graveyard
Component:
Applications: Balrog (backend)
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: catlee, Assigned: catlee)

References

Details

Attachments

(1 file)

Link to GitHub pull-request: https://github.com/mozilla/balrog/pull/858
42 bytes, text/x-github-pull-request
Details | Review

We currently run python3 tests for Balrog, but don't publish any python3 docker images.

We should be publishing both python2 and python3 docker images for Balrog.

Blocks: 1520541
Commit pushed to master at https://github.com/mozilla/balrog https://github.com/mozilla/balrog/commit/892a05a66c1e06b8d32336fdd67224a3df2a9821 Bug 1520540: Build and publish python3 docker images (#858) * Create new labels for py2 docker images * Adding py3 dockerfile * Adding tasks for building py3 docker images * fix Dockerfile argument * The agent is already py3, so revert agent specific changes * Adjust index routes for release events to distinguish py2/py3

Verified that mozilla/balrog:latest-py3 is python3 by running:
docker run --entrypoint /usr/local/bin/python -t -i mozilla/balrog:latest-py3

Assignee: nobody → catlee
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: