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
The Spring compatibility-tests pipeline does not support unreleased versions. This is needed if some of the Azure libraries that Spring uses go through changes, and we want to validate those changes works correctly for Spring use cases before release.
Here is an example of PR that was failing when trying to run our Spring tests with unreleased versions of Service bus and Event Hubs.
Supporting unreleased requires copying existing logic for the From Source pipeline runs where it looks for unreleased dependencies.
@anuchandy thanks for bringing this up. If we enable this logic in our compatibility-tests, does it mean some jobs will still fail (the ones using the released versions), but the ones using the unreleased version will pass?
Hi @saragluna, thanks for taking a look. The change simply allows our Spring tests to run using SB/EH/Core/* in main when instructed to do so by annotating with unreleased_com.azure. Once those are released, the spring poms will get updated to refer the same from maven. If we don't have any potential change to test, the dependencies will continue to be referenced from Maven as they are currently.
The Spring compatibility-tests pipeline does not support unreleased versions. This is needed if some of the Azure libraries that Spring uses go through changes, and we want to validate those changes works correctly for Spring use cases before release.
Here is an example of PR that was failing when trying to run our Spring tests with unreleased versions of Service bus and Event Hubs.
Supporting unreleased requires copying existing logic for the
From Source pipeline runs
where it looks for unreleased dependencies.Hi @saragluna, could you please help to triage?
The text was updated successfully, but these errors were encountered: