daily built recipes may error if a manual build has been done

Bug #620248 reported by Steven Sheehy on 2010-08-19
68
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Launchpad itself
High
Unassigned

Bug Description

Recipe build at https://code.launchpad.net/~linuxdcpp-team/+recipe/linuxdcpp/+build/1044 failed due to trying to upload a package that already exists. However, I did not request this build and I doubt anyone else knows about this recipe to request a build since it's only on edge. So first issue is did this get kicked off by some launchpad process or was it requested by a user? If the latter it's no problem, if the former then why was it started if there was no code changes?

Regardless of how it got initiated, it still shouldn't have built a package at all since there were no code changes to the associated branch. Since I use the bzr revno in the package title (and no date) it failed when trying to upload the package since I have a package for the revision already. But at the very least it should've failed before building while checking for branch changes.

Solutions
=========

* Put a timestamp as well as the revision in the debversion

Tim Penhey (thumper) wrote :

This was kicked off by the daily build.

Yes we are in the process of changing how to determine whether to build or not. We are moving to manifests.

Tim Penhey (thumper) wrote :

While not exactly the same as bug 583474, properly implementing manifests should fix this.

Tim Penhey (thumper) on 2010-08-19
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Medium
Christian Reis (kiko) wrote :

When people are using recipes to do daily builds this causes them to receive an email every time a build is tried (IOW, spam them once a day); probably worth considering for a CP or at least a fix next milestone.

Aaron Bentley (abentley) wrote :

It's only once a day if the branches have changed since the last daily build. The reason it happened here is that we always do *one* daily build to start. (The branches can't have changed since the last daily build if there was no last daily build.)

Andreas Hasenack (ahasenack) wrote :

I got the same issue. A daily build was triggered automatically even when there were no changes to any of the branches used in the recipe. But I did have one or more manual builds.

Changed in launchpad:
importance: Medium → High
David Allwicher (aber) wrote :

I have the same problem, because yesterday not all of the recipe builds fetched the newest revision. So today some of the builds are already up to date, while the others need to be build.

summary: - Recipe built duplicate package
+ daily built recipes may error if a manual build has been done
description: updated
Jelmer Vernooij (jelmer) on 2012-02-12
tags: added: recipe
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers