Opened at 2010-06-19T04:27:56Z
Closed at 2011-05-24T05:25:26Z
#1090 closed defect (fixed)
don't upload tarballs of branches (only of trunk)
| Reported by: | zooko | Owned by: | zooko |
|---|---|---|---|
| Priority: | major | Milestone: | soon (release n/a) |
| Component: | dev-infrastructure | Version: | 1.7β |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
Attachments (1)
Change History (5)
Changed at 2010-06-19T04:29:59Z by zooko
comment:1 Changed at 2011-05-20T22:32:18Z by davidsarah
comment:2 Changed at 2011-05-20T22:32:40Z by davidsarah
- Milestone changed from undecided to soon (release n/a)
comment:3 Changed at 2011-05-24T05:02:03Z by zooko
- Status changed from new to assigned
comment:4 Changed at 2011-05-24T05:25:26Z by zooko
- Resolution set to fixed
- Status changed from assigned to closed
I just tested it. Forcing a build with "branch=trunk" results in an upload: http://tahoe-lafs.org/buildbot/builders/tarballs/builds/801/steps/upload-tarballs/logs/stdio , forcing a build with "branch=ticket393" results in no upload: http://tahoe-lafs.org/buildbot/builders/tarballs/builds/803/steps/upload-tarballs/logs/stdio , and forcing a build with no branch specified (which means trunk) results in an upload: http://tahoe-lafs.org/buildbot/builders/tarballs/builds/804/steps/upload-tarballs/logs/stdio
I didn't test, but I think, that if you push a patch to trunk it will trigger with one of the two trunky spellings and if you push a patch to another branch it will trigger with the branchey spelling.
Is this fixed? I know we tried to fix it.