Retry build link not easily findable on ppa build log page

Bug #144057 reported by Laurent Bigonville
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Medium
Julian Edwards

Bug Description

The rebuild link is not visible enough on the ppa build log page. I had to ask on IRC before finding it

Revision history for this message
Terence Simpson (tsimpson) wrote :

The link to retry a failed build does seem to be a bit obscure, I have seen several people ask how to do this. [1] an example from the launchpad-users list.
It seems the people don't see it until they are told it's there, I include myself in that statement too.

Perhaps making the link in a more visible place or just having a "Note: Use the link on the left to try a rebuild" on a failed build page would help here?

[1] https://lists.ubuntu.com/archives/launchpad-users/2007-September/002118.html

Changed in launchpad:
status: New → Confirmed
Revision history for this message
Celso Providelo (cprov) wrote :

The 'note' idea is a very good suggestion, thanks.

Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

There really should be a series of action buttons on the build page for a build which has not been successful. For example, "Retry" and "Build now" would allow some sort of manual intervention in the build queueing system. The "Build now" button should I suppose only be available for admins :-)

Changed in soyuz:
importance: Undecided → Medium
Revision history for this message
Celso Providelo (cprov) wrote :

Another good point, currently Buildd_Admins have access to the 'Rescore' page which allow them to set a arbitrary score value to a NEEDSBUILD job.

As known by the admins, setting a value higher than 1150 (equivalent to a job for main component, urgency EMERGENCY, older than 14400 seconds and with all dependencies satisfied) will result in a "BUILD NOW" request, i.e., the job will get dispatched to the next IDLE builder.

If you agree, we can modify the 'Rescore' page and include a extra shortcut button labeled 'Build Now' which will set the score to a specific high value, let's say 10000 for tracking purpose.

This *hack-solution* can obviously be jeopardized by simultaneous 'BUILD NOW' requests in the same architecture, that's why maybe we should think about a more effective alternative.

Changed in soyuz:
assignee: nobody → julian-edwards
Changed in soyuz:
status: Confirmed → In Progress
Revision history for this message
Julian Edwards (julian-edwards) wrote :

Note added to bottom of the page to redirect uses to the action menu.

Fixed in RF 5049.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.