102.0.1 submission was created automatically but builds were not updated
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
People
(Reporter: pascalc, Assigned: gbrown)
References
Details
Last week was our first dot release auto-submitted to the Windows Store, we realized after shipping it that the Windows store was still serving 102.0 and indeed looking at the packages listed, they were the same as the ones for the initial release.
I created a new submission manually and uploaded 102.0.1 msix builds so we are fine now.
It's not clear to our team if we did some manual error with the submission when we updated the rollout rate and maybe republished 102.0 or if automation didn't actually succeed in uploading the builds and the created submission fell back to the builds already in the store.
Filing this bug just in case it wasn't a human error.
Our next dot release is probably like 3 or 4 weeks away.
|
Assignee | |
Comment 1•2 years ago
|
||
That is troubling. I wonder if the do-not-commit strategy of bug 1776696 just doesn't work. The logs look fine: bug 1776696 appears to be working as designed. But I didn't "watch" that run or the subsequent submission, so I don't know what happened on the Store.
I won't make any changes for now, but let's keep this in mind and watch the next run carefully.
|
||
Comment 2•2 years ago
|
||
:gbrown FYI the same problem occurred with 103.0 RC1. The push task was green, Submission 34 was created, but the packages in the submission are both from the previous release "v102.0.1.0"
Link to the task log https://firefox-ci-tc.services.mozilla.com/tasks/QybKr0mnQ2WWPBJJC8KF1A/runs/0/logs/public/logs/live_backing.log
I'll remove the packages and manually add the correct ones later today.
|
|
Assignee | |
Comment 3•2 years ago
|
||
Sorry to hear it. The log looks fine to me, again. I think the do-not-commit strategy of bug 1776696 just doesn't work.
I suppose the only remaining option is the other idea from bug 1776696:
Or, MSIX(push) could set the isPackageRollout field to true, and set the packageRolloutPercentage to a specific value. Is there any interest in that?
That is an option, we would also need to enable "Always provide the newest packages when customers manually check for updates". I'm not sure if that's available through the API? The flow here would be - Set the rollout to 25% (or a lower value), enable the "Always provide the newest packages..." option, and submit for certification. We then manually release on release day.
I'll try that.
|
|
Assignee | |
Comment 4•2 years ago
|
||
On the release channel, during the rollout I see:
"packageDeliveryOptions":
{"packageRollout":
{"isPackageRollout":true,"packageRolloutPercentage":25.0,"packageRolloutStatus":"PackageRolloutInProgress","fallbackSubmissionId":"1152921505695035997"},
"isMandatoryUpdate":false,"mandatoryUpdateEffectiveDate":"1601-01-01T00:00:00.0000000Z"
}
and once we go to 100%, I see:
"packageDeliveryOptions":
{"packageRollout":{"isPackageRollout":true,"packageRolloutPercentage":100.0,"packageRolloutStatus":"PackageRolloutComplete","fallbackSubmissionId":"1152921505695035997"},
"isMandatoryUpdate":false,
"mandatoryUpdateEffectiveDate":"1601-01-01T00:00:00.0000000Z"
}
Docs say to set "isPackageRollout" and "packageRolloutPercentage" (packageRolloutStatus and fallbackSubmissionId are read-only).
|
|
Assignee | |
Comment 5•2 years ago
|
||
See also https://bugzilla.mozilla.org/show_bug.cgi?id=1776696#c12: I'm going to undo bug 1776696 and set the package rollout %; relman will need to cancel certification, edit the submission, and re-submit. I think that's the best I can do.
|
|
Assignee | |
Comment 6•2 years ago
|
||
|
|
Assignee | |
Comment 7•2 years ago
|
||
:dmeehan - See https://bugzilla.mozilla.org/show_bug.cgi?id=1776696#c12 and https://bugzilla.mozilla.org/show_bug.cgi?id=1779435#c5. Will that be okay?
|
|
||
Comment 8•2 years ago
|
||
We have a dot release next week, we can keep an eye on your fix as summarized comment 7.
It's better to have the correct packages, and when needed a few manual submission tweaks versus having to manually upload. I'll mention it to the rest of relman also.
|
|
Assignee | |
Comment 9•2 years ago
|
||
Sounds good. Thanks.
Description
•