git ubuntu merge extension to push to bileto

Bug #1697009 reported by Christian Ehrhardt  on 2017-06-09
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

Once git ubuntu merge does all the extra niceties of bug 1696775 it would be great to later on extend it for Bileto.

Overall flow chart

create merge proposal
create associated bileto ticket
upload the current version to that bileto ticket
try to auto create diff there
Check if build ok, mark that on the MP and trigger Tests
Check if tests are ok, mark that on the MP

That way it is very close to a full CI+Commit like you have.
Like Verified (=build) + Tested (dep8s).

That will raise the trustworthiness of the contribution for the reviewer.

Robie Basak (racb) on 2017-08-02
Changed in usd-importer:
status: New → Confirmed
importance: Undecided → Wishlist
milestone: none → future

Actually this would be good for any part of "git ubuntu submit" to open up a ppa, push the package to build there and and make an auto-update to the MP linking to said ppa.
Doesn't have to be Bileto, but all-arch would be great.

I know we discussed with the LP Team about ressources for this, but we might implement it all the way keeping it default-off for now. But at least our Team more-and-more adopts the ppa-per-mp workflow - so it would eliminate manual steps and speed up work for us at least.

Robie Basak (racb) on 2017-11-28
tags: added: submit

Bileto is more and mor bit-rotting.
But opening up a ppa and pushing there would still be great.

About the testing after build I discussed with pitti how current tools do so.
Dumping this here as reference.

[10:50] <pitti> cpaelzer: ah, yes! these are upstream tests, set up like
[10:50] <pitti> cpaelzer: the underlying mechanics is just adding a ppa= to the test request, like in
[10:51] <pitti> cpaelzer: you can use the run-autopkgtest CLI for convenience (
[10:52] <pitti> actually no, this script is horribly out of date; I don't think it's being used any more
[10:53] <pitti> it's that script actually:
[10:53] <pitti> (same name, but using the CGI API instead of ssh to snakefruit)
[10:55] <pitti> argh, it's been too long - so that script isn't useful for you, it's indeed the one that directly talks to AMQP and thus you can't access it
[10:56] <pitti> you can trigger them through request.cgi, but ATM you have to build the URL manually; bileto did that, not sure if there's some CLI for that by now

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers