Follow-up API check to ensure the release has indeed now a “shipped” state. Baked within the initial call in shipitscript.

https://tools.taskcluster.net/groups/fEFEbmGNQcu52GYvgBAlIw/tasks/aDjGm07GTGyHHRgp_QmByw/details worked smoothly with my pinned 2.1.0-dev shipitscript version

Changes rolled-out to production. Closing this now. Will-reopen if we need to fix anything or add more stuff.

For reference, I found a bug afterwards by doing more testing on maple. shippedAt is kept in a format on local shipitscript, while on Ship-it is kept in isoformat(). Testing that bitwise from a string perspective failed miserably here[1]. Mea culpa. Since I couldn't find a cleaner way to tweak existing local shipitscript time to be more like the Ship-it one, I went on and treated `shippedAt` case as a separate one for time comparison. PR to fix this is here[3]. currently pending review. Follow-up rerun for that particular task went on green smoothly here[2] [1]: https://taskcluster-artifacts.net/Dsl8DpRLTeaj2aIl5KPJaw/0/public/logs/live_backing.log [2]: https://taskcluster-artifacts.net/Dsl8DpRLTeaj2aIl5KPJaw/1/public/logs/live_backing.log [3]: https://github.com/mozilla-releng/shipitscript/pull/11/files

For reference, how timing is kept in Ship-it - https://github.com/mozilla-releng/ship-it/blob/master/kickoff/model.py#L38

https://taskcluster-artifacts.net/bQ8rNeIQQMyWG7M2lYnzmA/0/public/logs/live_backing.log https://taskcluster-artifacts.net/ErB2BDyPRa2wOLei6hDfaA/0/public/logs/live_backing.log