branch-distro doesn't trigger a scanner run
Bug #574083 reported by
Michael Hudson-Doyle
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Tim Penhey | ||
Bug Description
After the landing of the no-hosted-area branch, the branch-distro.py script still doesn't trigger the scanner to run over the new branches or record that the stacked of the old branches has changed. We should call the branchChanged() method on the branches.
Related branches
lp:~thumper/launchpad/branch-distro-avoid-scan
- Michael Hudson-Doyle: Approve
-
Diff: 23 lines (+3/-0)2 files modifiedlib/lp/codehosting/branchdistro.py (+1/-0)
lib/lp/codehosting/tests/test_branchdistro.py (+2/-0)
| Changed in launchpad-code: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: package-branches trivial |
Revision history for this message
| Michael Hudson-Doyle (mwhudson) wrote | #1 |
| Changed in launchpad-code: | |
| importance: | Low → High |
| assignee: | nobody → Tim Penhey (thumper) |
| milestone: | none → 10.10 |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote Bug fixed by a commit | #2 |
| tags: | added: qa-needstesting |
| Changed in launchpad-code: | |
| status: | Triaged → Fix Committed |
Revision history for this message
| Launchpad QA Bot (lpqabot) wrote Incremental fix | #3 |
| Changed in launchpad-code: | |
| status: | Fix Committed → In Progress |
| Changed in launchpad-code: | |
| status: | In Progress → Fix Committed |
| tags: |
added: qa-ok removed: qa-needstesting |
Revision history for this message
| Jonathan Lange (jml) wrote | #4 |
| Changed in launchpad-code: | |
| importance: | High → Critical |
| tags: | added: new-release-cycle-process |
Revision history for this message
| Jonathan Lange (jml) wrote | #5 |
| Changed in launchpad-code: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We don't strictly _have_ to trigger a scan job, it might be almost as easy and certainly more efficient to write some code to do what the scan job would do (copy the branchrevisions over to the new branch, update the various last_scanned and revision_count fields).