You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
alzimmermsft opened this issue
Oct 2, 2020
· 1 comment
Labels
ClientThis issue points to a problem in the data-plane of the library.commoncommon module used by all azure SDKs (e.g. client, Mgmt)EngSysThis issue is impacting the engineering system.
Add a validation step in the release pipeline to check that all runtime dependencies are available from Maven. Currently, we only validate versions in our POM files for matching the version tags in external_dependency.txt, version_client.txt, etc. This leaves the possibility where a library is depending on a current, unreleased version of another library but if the version tags match it will be allowed to ship. Once this artifact is in Maven if the other library doesn't ship it could be broken (depending on the dependency [compile/runtime/test] scope).
The text was updated successfully, but these errors were encountered:
alzimmermsft
added
EngSys
This issue is impacting the engineering system.
common
common module used by all azure SDKs (e.g. client, Mgmt)
labels
Oct 2, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
ClientThis issue points to a problem in the data-plane of the library.commoncommon module used by all azure SDKs (e.g. client, Mgmt)EngSysThis issue is impacting the engineering system.
Add a validation step in the release pipeline to check that all runtime dependencies are available from Maven. Currently, we only validate versions in our POM files for matching the version tags in
external_dependency.txt
,version_client.txt
, etc. This leaves the possibility where a library is depending on a current, unreleased version of another library but if the version tags match it will be allowed to ship. Once this artifact is in Maven if the other library doesn't ship it could be broken (depending on the dependency [compile/runtime/test] scope).The text was updated successfully, but these errors were encountered: