https://pinot.apache.org/ logo
Join Slack
Powered by
Want to try pinot 0.7.1 release. And we are using ...
# troubleshooting
l
Want to try pinot 0.7.1 release. And we are using the artifacts from jitpack. The following shaded artifact is not available for 0.7.1 release. And we are using this artifact.
Copy code
wget -qO temp.zip <https://jitpack.io/com/github/apache/incubator-pinot/pinot-distribution/e22be7c3a39e840321d3658e7505f21768b228d6/pinot-distribution-e22be7c3a39e840321d3658e7505f21768b228d6-shaded.jar>
However, I can see the shaded artifact is available under maven central here. https://repo1.maven.org/maven2/org/apache/pinot/pinot-distribution/0.7.1/ Any suggestions on how to proceed here? @Kishore G @Xiang Fu
Info: Shaded artifacts were available for old pinot releases in jitpack https://jitpack.io/com/github/apache/incubator-pinot/
x
Maven is used to host all apache libs
we don’t publish to jitpack. I don’t how the libs there are landed
l
Got the root cause
image.png
Build failed on jitpack
x
got it
then I need to patch the release
it’s an issue introduced recently
by npm
l
But how 0.7.1 build passed and uploaded to maven central
x
yes, that was because, the npm update which causes the issue after our apache release 🤣
l
okay. npm version is not locked in out pinot build?
How do we fix this?
x
I cherry-picked the fix and pushed a new tag: release-0.7.1-ui-fix
once it got picked
you should see it from jitpack
l
cool. thanks a lot @Xiang Fu
Jitpack started building this
x
ok.
does jitpack build branch ?
l
image.png
x
seems no?
then I should push a new branch instead of a tag
l
I am also not fully aware how jitpack works. But I see your npm fix is picked up and it started building
x
ok
l
Build log 👆
x
then will let it build
I could delete the tag later on 😛
🤣 1
l
Build complete. Now the distros are available in jitpack too
👍 1
Open in Slack
PreviousNext
Powered by