The way the train reports status is severely deficient.

Bug #1514628 reported by Robert Bruce Park on 2015-11-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CI Train [cu2d]
Fix Released
Robert Bruce Park

Bug Description

The status field in bileto is a single string, which we free-form jam information into. This has a lot of limitations.

What I'd like to do is make the field be JSON, with a dict mapping package names to status messages. So you'd have something like this:

{"foo-package": "Built.", "bar-package": "failed on i386"}

and then check-publication-migration could be expanded to just check all possible states and update this continuously. So eg if something gets dirty it would automatically become:

{"foo-package": "Built.", "bar-package": "DIRTY"}

And then if the offending commit is deleted the dirty status would just go away.

Best case scenario, the "dirty file" (the file on disk that indicates a package is dirty) could just go away, and dirtiness would be measured by proactively checking for a) version at dest differing from when package was built, and b) commits in MPs differing from what was built.

By not keeping a "dirty" file but checking external realities regularly we would do away with the train's state becoming inconsistent and requiring manual intervention to fix.

And also by tracking the status of packages *individually* we would dramatically increase the readability of the message (eg each package could be presented on it's own line rather than a huge message like "foo is blah, bar is blah, zip is blah" etc.

The json blob would probably also need a global 'summary', to use in the IRC pings. This would just be a short blurb and not give per-package details.

Related branches

PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:cupstream2distro at revision 1204, scheduled for release in cupstream2distro, milestone Unknown

Changed in cupstream2distro:
status: Triaged → Fix Committed
Changed in cupstream2distro:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers