Closed Bug 1854172 Opened 2 years ago Closed 2 years ago

tecken deploy: 2023.09.20

Categories

(Tecken :: General, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

Details

We want to do a deploy for tecken tagged 2023.09.20. It's a re-attempt at the 2023.09.18 deploy.

It consists of everything from the failed 2023.09.13 deploy (bug #1852946):

510d292: bug 1746940: fix FileUpload admin; add fake data generator (willkg)
12a8155: bug 1851909: switch to django-admin-cursor-paginator (willkg)
adf576c: bug 1746940: add debug fields to FileUpload model (willkg)
0bfc681: bug 1746940: implement sym data capture at upload (willkg)
0997218: bug 1746940: implement code_file/code_id lookup for download API (willkg)
e4ed26d: bug 1746940: add sym debug data to File page (willkg)
27e4d6e: bug 1746940: remove errant logging.info line (willkg)
23daea4: bug 1746940: fix upload-sym file for Windows modules (willkg)
b84b0ba: bug 1746940: rework download API to support /code_file/code_id/sym_file (willkg)
7614fbc: bug 1746940: fix minor issues with last commit (willkg)
c803233: Update architecture diagram (willkg)

Plus the thing from 2023.09.14 deploy (bug #1853191):

abb9472: bug 1774217: add support for token comments (willkg)

And some additional stuff:

83ef822: Sort gitignore and add __pycache__ (willkg)
a983683: Fix Dockerfile to set PYTHONDONTWRITEBYTECODE (willkg)
c991697: bug 1746940: move info lookup to syminfo API endpoint (willkg)
9321696: bug 1746940: add caching for syminfo API (willkg)
0a94b20: bug 1746940: take out unuseful timing from syminfo api (willkg)
c62180c: bug 1746940: fix metric keys so they're consistent with existing metrics (willkg)
e357b27: bug 1746940: thread refresh_cache through api params (willkg)
f3b84ee: bug 1746940: remove code_file/code_id from download API docs (willkg)

This deploy succeeded. I updated the relevant bugs. Marking as FIXED.

Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
See Also: → 1853219
You need to log in before you can comment on or make changes to this bug.