Merge lp:~jtv/launchpad/bug-523449 into lp:launchpad
| Status: | Merged | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Approved by: | Jeroen T. Vermeulen on 2010-02-19 | ||||||||
| Approved revision: | not available | ||||||||
| Merged at revision: | not available | ||||||||
| Proposed branch: | lp:~jtv/launchpad/bug-523449 | ||||||||
| Merge into: | lp:launchpad | ||||||||
| Prerequisite: | lp:~jtv/launchpad/branch-url | ||||||||
| Diff against target: |
88 lines (+30/-4) 3 files modified
lib/lp/translations/model/translationtemplatesbuildjob.py (+1/-1) lib/lp/translations/tests/test_translationtemplatesbuildbehavior.py (+15/-3) lib/lp/translations/tests/test_translationtemplatesbuildjob.py (+14/-0) |
||||||||
| To merge this branch: | bzr merge lp:~jtv/launchpad/bug-523449 | ||||||||
| Related bugs: |
|
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Paul Hummer (community) | code | 2010-02-18 | Approve on 2010-02-18 |
|
Review via email:
|
|||
Commit Message
Pass branch_url to build slave.
| Jeroen T. Vermeulen (jtv) wrote : | # |
| Paul Hummer (rockstar) wrote : | # |
This diff had some changes from the pre-req branch, which is sub-optimal. I wonder why. Did you use a pipe or just merge in some of the revisions from the pre-req branch. It's really odd.
Other than that, this all looks good, assuming that the one single change in the pre-req branch is fixed as well.
| Jeroen T. Vermeulen (jtv) wrote : | # |
Thanks, Paul! Yes, I'm working in a pipe and so in the regular flow of things, I found that I wanted to do one thing differently—move more of the trigger function's logic into the utility. I can backport that change, or leave it in and just land the 4 branches that have accumulated here (all but the first reviewed...) as one. If you're reviewing the prerequisite branch as well, perhaps the easiest thing is to keep things as they are.

= Bug 523449 =
We're farming out the generation of translation templates based on a branch of source code to the build farm. One of the pieces of the puzzle is to tell the slave where it can find the branch. The code you see here takes care of that. It relies on a new method, IBranch. composePublicUR L, which was implemented as bug 523467 but has not landed yet because of review backlog.
This feature is not enabled yet because it is not yet complete. Q/A for this particular part of the job does not make sense; what's needed is end-to-end manual testing of the entire feature.
Test: latesbuild
{{{
./bin/test -vv -t translationtemp
}}}
There is some lint, but none related to my code and none that I can reasonably fix. Mostly pylint being pitifully confused for no good reason.
Jeroen