The Mariner arm64 build is currently failing. When it builds identity service bits, it tries to populate the version by getting the latest 1.5. tag from the identity service repo. There are no 1.5. tags yet, so it sends an empty version which causes make to fail.
The root cause is that we bumped our release version in code much sooner than we normally do (i.e., the period of time between bumping the version in code and actually publishing the bits is usually hours, but this time it's a couple weeks). The problem will resolve automatically once we release, and we don't release Mariner arm64 externally, so we'll simply disable it now, and re-enable as soon as we release.
To test, I ran the CI Build pipeline and confirmed it passes and Mariner arm64 is skipped.
Azure IoT Edge PR checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
The Mariner arm64 build is currently failing. When it builds identity service bits, it tries to populate the version by getting the latest 1.5. tag from the identity service repo. There are no 1.5. tags yet, so it sends an empty version which causes
make
to fail.The root cause is that we bumped our release version in code much sooner than we normally do (i.e., the period of time between bumping the version in code and actually publishing the bits is usually hours, but this time it's a couple weeks). The problem will resolve automatically once we release, and we don't release Mariner arm64 externally, so we'll simply disable it now, and re-enable as soon as we release.
To test, I ran the CI Build pipeline and confirmed it passes and Mariner arm64 is skipped.
Azure IoT Edge PR checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.
General Guidelines and Best Practices
Testing Guidelines