recipes attempt to build packages with version older than previous build

Bug #931131 reported by Jelmer Vernooij
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Launchpad should be able to see that a recipe build it's going to fire off will have a version string that's older than that of the last build; it shouldn't even start the build and print a clear error rather than fail confusingly during the upload.

It could also clearly indicate that the next recipe build will have a too old version number on the recipe page.

This is related to bug 670474

Tags: recipe
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Fixing this will also fix some annoying issues that come up when a user requests a build for a recipe daily. We often end up building the package twice, with the second build triggered by the recipe cron job. This second build will fail to upload, because a package with the same version string already exists.

summary: - shouldn't attempt to build out-of-date packages
+ attempts to build packages with version older than previous build
summary: - attempts to build packages with version older than previous build
+ recipes attempt to build packages with version older than previous build
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in launchpad:
status: New → Confirmed
Changed in launchpad:
status: Confirmed → Triaged
importance: Undecided → High
importance: High → Low
Revision history for this message
Aaron Bentley (abentley) wrote :

I had hoped to enhance the recipe builder so that the recipe itself was run before handing the work off to the build farm. It would then compare the manifest to previous successful builds, and if any matched, it would abandon the job. I suppose checking the version number at this time would also make sense.

Aborting builds on the build farm is better than nothing, but waiting until the build starts to determine that it can't succeed seems perverse.

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.