changes to buildstate strings broke scripts
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
New
|
Undecided
|
Unassigned | ||
Bug Description
Edge suddenly changed build.buildstate strings for all API versions. This broke security publication scripts.
Was "Successfully built", and is now "Successful build". What other strings have changed, and what is the policy on string contents changing under a given API version?
via: https:/
In [1]: primary.
Out[1]: <build at https:/
via: https:/
In [1]: primary.
...
ValueError: Invalid value 'Successfully built' for parameter 'build_state': valid values are: "Pending build", "Successful build", "Failed to build", "Could not build because of missing dependencies", "Could not build because of chroot problem", "Could not build because source package was superseded", "Currently building", "Could not be uploaded correctly"
| Colin Watson (cjwatson) wrote | #1 |
... and why does the API return these human-readable strings rather than some kind of identifier, anyway? If code inside Launchpad isn't comparing against "Successful build", then code outside Launchpad shouldn't have to either ...