Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix keyvault's Track 1 pipeline #42824

Closed
wants to merge 2 commits into from

Conversation

JimSuplizio
Copy link
Member

@JimSuplizio JimSuplizio commented Nov 5, 2024

The following libraries were removed from the sources and from version_data.txt but not from the ci.data.yml which is why the nightly runs of java - keyvault - data have been failing for months.

  • com.microsoft.azure:azure-keyvault
  • com.microsoft.azure:azure-keyvault-cryptography
  • com.microsoft.azure:azure-keyvault-webkey

Also, add batch release parameters just in case these things ever happen to need to be released.

@vcolin7 Being that keyvault data's ci pipeline hasn't built since 2022 and the internal pipeline was just failing to build, in general, I'm not sure keyvault data's internal pipeline can actually build. Even fixing the yml file, the pipeline doesn't seem to be able to build it anymore

@JimSuplizio JimSuplizio self-assigned this Nov 5, 2024
@JimSuplizio JimSuplizio requested review from vcolin7, g2vinay and a team as code owners November 5, 2024 23:50
@JimSuplizio
Copy link
Member Author

@vcolin7 - As per our conversation I'm going to close this PR. For everyone else, the keyvault data libraries are all effectively EOL and it'll be investigated as to whether or not the entire keyvault data can be approved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant