Conversation
In Testing, Please Ignore[Logs] (Generated from 3e6ec14, Iteration 9)
|
Automation for azure-sdk-for-pythonA PR has been created for you: |
yungezz
added
bug
Automation for azure-sdk-for-goA PR has been created for you: |
|
Can one of the admins verify this patch? |
|
@lmazuel |
|
|
||
| ``` yaml $(java) && $(multiapi) | ||
| batch: | ||
| - tag: package-2019-06 |
There was a problem hiding this comment.
if there sdk released for this already? what's the impact of removing this line?
There was a problem hiding this comment.
I have added package-subscriptions-2019-06 below, so result is the same
| tag: package-policy-2019-06 | ||
| ``` | ||
|
|
||
| ``` yaml $(package-policy) |
There was a problem hiding this comment.
this was duplicated, and second has overwritten first resulting in wrong version included in some sdks
|
|
||
| ``` yaml $(package-subscriptions) | ||
| tag: package-subscriptions-2018-06 | ||
| tag: package-subscriptions-2019-06 |
There was a problem hiding this comment.
what's the sorting order? it's a mess now.
There was a problem hiding this comment.
what do you mean, there's only one tag in here?
| - tag: package-locks-2016-09 | ||
| - tag: package-locks-2015-01 | ||
| - tag: package-managedapplications-2018-06 | ||
| - tag: package-managedapplications-2017-09 |
There was a problem hiding this comment.
because managedapplications was intentionally generated as single-api, and the second tag was put by mistake here by service team.
basically, in current configuration package-managedapplications-2017-09 will overwrite package-managedapplications-2018-06 meaning that old package was released instead of new one.
so after discussing with @lmazuel I decided to leave it as single api and fix the problem introduced by the service team.
7 participants
No description provided.