juju metadata generate-tools never updates the version. We take a snapshot of all the stream metadata before we release in case we want to rollback. We have snapshots back to 2014-11-14, 2 years. we can see juju always selects the first and oldest version of agents found, and places that version as the version for the series-arch.
So there is no reason to rollback because stream are consistent, and validation of stream confirms that the value doesn't change. I think the juju metadata plugin needs fixing.
As the QA team intends to stop using the metadata plugin, our replacement tool can place the *last* and most recent version of agents found in the version fields.
juju metadata generate-tools never updates the version. We take a snapshot of all the stream metadata before we release in case we want to rollback. We have snapshots back to 2014-11-14, 2 years. we can see juju always selects the first and oldest version of agents found, and places that version as the version for the series-arch.
So there is no reason to rollback because stream are consistent, and validation of stream confirms that the value doesn't change. I think the juju metadata plugin needs fixing.
As the QA team intends to stop using the metadata plugin, our replacement tool can place the *last* and most recent version of agents found in the version fields.