remote-build always recovers, even when --recover is not specified
Bug #1913599 reported by
nymea
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Triaged
|
Low
|
Chris Patterson | ||
Bug Description
To reproduce, start a remote-build, and make the client fail somehow.
Wait for the remote build to finish or fail (doesn't matter).
Then start another remote-build with a different revision of the source code *without* specifying --recover.
=> snapcraft will recover the previous build and report the status instead of actually building the new source.
Given that snapcraft clean doesn't seem to clean remote builds, this makes it close to impossible to use snapcraft remote-build in some sort of automated build environment as one never knows what the build artifact is actually based on.
| summary: |
- remote-build always recovery, even when --recover is not specified + remote-build always recovers, even when --recover is not specified |
| Changed in snapcraft: | |
| status: | New → Confirmed |
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #1 |
| Changed in snapcraft: | |
| status: | Confirmed → Triaged |
| importance: | Undecided → Low |
| assignee: | nobody → Chris Patterson (cjp256) |
To post a comment you must log in.
We should a --no-recover option.
We should add proper documentation/spec.