Closed Bug 1404484 Opened 8 years ago Closed 8 years ago

update python on balrog scriptworkers to avoid ssl warnings

Categories

(Release Engineering :: Release Automation, enhancement)

Product:
Release Engineering
Component:
Release Automation
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1450035

People

(Reporter: mozilla, Unassigned)

Details

Currently our balrog scriptworkers appear to have py2.7.3 on them, and we're getting ssl warnings. If we want to install a newer py27, we'll need to do something in this if/else clause [1]. We have an issue to py3 async-ify balrogscript [2]: even if we don't use async, making the script py3 compatible would allow us to use py3.5. This is my preferred option, but may involve py3-ifying all upstream dependencies. [1] https://hg.mozilla.org/build/puppet/file/tip/modules/packages/manifests/mozilla/python27.pp#l60 [2] https://github.com/mozilla-releng/balrogscript/issues/7
(In reply to Aki Sasaki [:aki] from comment #0) > Currently our balrog scriptworkers appear to have py2.7.3 on them, and we're > getting ssl warnings. If we want to install a newer py27, we'll need to do > something in this if/else clause [1]. If we edit this if/else clause, we need to make sure we explicitly update the servers we intend to update. Updating other servers may break all the things.
Summary: update python on balrog scriptworkers → update python on balrog scriptworkers to avoid ssl warnings
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.