don't worry, you'll have it! It's not obvious, but that arch field is really
just giving it more of a hint of what to use for figuring out which one to
track. This is because while you might have snap "xyz" with version "1.4", the
revision will be different for each arch. However, even though those revisions
are different, you want to track them and release them all as one snap/version.
So when we push a card to the trello dashboard, it will have the revision for
amd64, but in reality it's tracking multiple archs/revisions.
As proof, here's what the json would look like for one of those snaps:
"mesa-core20": {
"latest": {
"stable": {
"amd64": {
"version": "21.2.6",
"revision": 125,
"grade": "stable"
},
"arm64": {
"version": "21.2.6",
"revision": 126,
"grade": "stable"
},
"armhf": {
"version": "21.2.6",
"revision": 128,
"grade": "stable"
},
"ppc64el": {
"version": "21.2.6",
"revision": 129,
"grade": "stable"
},
"riscv64": {
"version": "21.2.6",
"revision": 130,
"grade": "stable"
},
"s390x": {
"version": "21.2.6",
"revision": 127,
"grade": "stable"
}
},
"beta": {
"amd64": {
"version": "21.2.6",
"revision": 125,
"grade": "stable"
},
"arm64": {
"version": "21.2.6",
"revision": 126,
"grade": "stable"
},
"armhf": {
"version": "21.2.6",
"revision": 128,
"grade": "stable"
},
"ppc64el": {
"version": "21.2.6",
"revision": 129,
"grade": "stable"
},
"riscv64": {
"version": "21.2.6",
"revision": 130,
"grade": "stable"
},
"s390x": {
"version": "21.2.6",
"revision": 127,
"grade": "stable"
}
}
}
},
--
https://code.launchpad.net/~pwlars/hwcert-jenkins-jobs/+git/hwcert-data/+merge/439846
Your team Canonical Hardware Certification is requested to review the proposed
merge of ~pwlars/hwcert-jenkins-jobs/+git/hwcert-data:mir-snaps into
~canonical-hw-cert/hwcert-jenkins-jobs/+git/hwcert-data:master.
--
Mailing list: https://launchpad.net/~canonical-hw-cert
Post to : [email protected]
Unsubscribe : https://launchpad.net/~canonical-hw-cert
More help : https://help.launchpad.net/ListHelp
