Debian version bump commit: rMSCA0559eb0084bb: Bumping Debian version to 3.7.4-1
Upstream version bump commit: rMSCA5edc56e564a1: Bump version to 3.7.4
Puppet package version change: rOPUP5714bcd7a26e: Bump scap version to 3.7.4-1 (pending)
@fgiunchedi: can you do the upload?
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Bump scap to 3.7.4-3 | operations/puppet | production | +1 -1 | |
| Scap: bump version to 3.7.4-2 | operations/puppet | production | +1 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T176324 Scoring platform team FY18 Q2 | |||
| Declined | None | T179501 Use external dsh group to list pooled ORES nodes | |||
| Resolved | akosiaris | T168073 Switch ORES to dedicated cluster | |||
| Resolved | awight | T181661 Connection timeout from tin to new ores servers | |||
| Resolved | akosiaris | T182347 SCAP: Upload debian package version 3.7.4-3 | |||
| Resolved | akosiaris | T183046 scap 3.7.4-2 is broken |
High priority because the new version of scap will help with debugging T181661: Connection timeout from tin to new ores servers
Package built for both jessie and trusty and uploaded on apt.wikimedia.org. Puppet change merged as well
I'm unclear what happened here, but we're missing an important configuration flag scap3_mediawiki from the current release on tin:
vs
[thcipriani@tin ~]$ grep -i scap3_m /usr/lib/python2.7/dist-packages/scap/config.py [thcipriani@tin ~]$ grep -i scap3_m /usr/lib/python2.7/dist-packages/scap/main.py
I don't see the debian/3.7.4-1 tag in the repo, but I do see 3.7.4 tagged. The configuration flag is present at that tag, could an opsen rebuild and upload a debian/3.7.4-2?
After some investigation it turns out I built master and not release branch which caused all this nice things. I am building 3.7.4-2 to fix this
Change 398507 had a related patch set uploaded (by Thcipriani; owner: Thcipriani):
[operations/puppet@production] Scap: bump version to 3.7.4-2
Change 398507 merged by Alexandros Kosiaris:
[operations/puppet@production] Scap: bump version to 3.7.4-2
I 've went ahead and built and uploaded the package in order to avoid any immediate issues from the botched release. In D916 jenkins doesn't love me, but it's all Java to me :D.
I 've met a number of issues while building, I 'll post notes on Monday asking for a few questions.
D916 accepted. Must be something weird with requests to non-master branch, will check it out.
I 've met a number of issues while building, I 'll post notes on Monday asking for a few questions.
scap release has grown up pretty ad-hoc, so streamlining and sane-making would be great!
Thanks for all your help! I see what I expect on tin, calling this closed:
[thcipriani@tin ~]$ grep -i scap3_m /usr/lib/python2.7/dist-packages/scap/config.py
'scap3_mediawiki': (bool, False),And botched a second time. See T183046. I 've managed to botch 2 times in a row a release of the software. I am the one the blame fully in the latter case but this is becoming weird.
Change 398822 had a related patch set uploaded (by Alexandros Kosiaris; owner: Alexandros Kosiaris):
[operations/puppet@production] Bump scap to 3.7.4-3
Mentioned in SAL (#wikimedia-operations) [2017-12-18T12:20:15Z] <akosiaris> build scap 3.7.4-3 and upload to jessie-wikimedia, stretch-wikimedia, trusty-wikimedia. T183046, T182347
Change 398822 merged by Alexandros Kosiaris:
[operations/puppet@production] Bump scap to 3.7.4-3