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

Revert 6432dde990f73821610d6b7e8f8e21d210404750: Migrate to new Shipkit plugin #44

Merged
merged 2 commits into from
Feb 6, 2021

Conversation

wmoustafa
Copy link
Contributor

Published artifact signing files are no longer generated as of v1.0.20, and hence Coral repo in Bintray cannot be synced with Maven Central. Version 1.0.20 contains two changes. One of the two changes (#36) upgrades Shipkit plugin to a new version. At the same time, LinkedIn Bintray account did not seem to have recent changes that would make those files no longer be generated. Current theory is that one of the changes in v1.0.20 caused the regression. This patch reverts one of those changes to check if it is correlated.

@wmoustafa wmoustafa merged commit fb20e88 into linkedin:master Feb 6, 2021
@wmoustafa
Copy link
Contributor Author

Reverting seems to have successfully resulted in the files being generated again https://bintray.com/linkedin/maven/coral/1.0.19#files/com%2Flinkedin%2Fcoral%2Fcoral-hive%2F1.0.19.

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

Successfully merging this pull request may close these issues.

2 participants