enrich
enrich copied to clipboard
snowplow
Stream: Attach jar files to Github releases
Project: Stream Enrich
Version: 1.3 and upper
Expected behaviour:
Releases for enricher should be available as jar files on Bintray.
Actual behaviour:
It's not clear what's the intended goal of this project regarding artifacts. The documentation mentions that We are steadily moving over to Bintray for hosting binaries and artifacts which don’t have to be hosted on S3, but for the enricher, the last available release is 1.1.3. There are newer releases as Docker images, but that forces teams to either 1. Use Docker if they're not using it or 2. Rewrite their setup if they have dockerised the enricher component already. Also, some teams might not be allowed to use docker images unless they have been certified, for security reasons.
The same problem is present with the Stream Collector and possibly other components. I will fill a separate issue for that one.
Related:
- https://github.com/snowplow/enrich/issues/24
- https://github.com/snowplow/enrich/issues/373
- https://discourse.snowplowanalytics.com/t/snowplow-enrich-1-3-2-released/4199
Thanks for the report @gerardo ! We're sorry that our documentation was misleading. I think we can consider attaching jar files to GitHub releases but I don't think we will upload to Bintray. Another option could be sharing instructions on how to build a fat jar (we generally use sbt-assembly to generate fat jar). If you have an urgency, you might want to try sbt-assembly to generate your own fat jar until we decide on an option.
We'll be updating our documentation and discuss the options for the upcoming release.
Hi @oguzhanunlu, thanks for your prompt answer. Jar files attached to the Github releases would be ideal! But if you don't mind me asking, what is the problem with Bintray?
Also, when is the next release planned?
We found the same issue with the s3 loader https://docs.snowplowanalytics.com/docs/pipeline-components-and-applications/hosted-assets/#4-4-snowplow-s3-loader-resources. The last version available is 0.7.0, but the Github repo mentions the latest version to be 1.0.
Should I fill separate issues for every repo?
Helpful Github action: https://github.com/marketplace/actions/upload-release-assets.
We found the same issue with the s3 loader https://docs.snowplowanalytics.com/docs/pipeline-components-and-applications/hosted-assets/#4-4-snowplow-s3-loader-resources. The last version available is 0.7.0, but the Github repo mentions the latest version to be 1.0.
Should I fill separate issues for every repo?
I've opened an issue for this in the S3 Loader repo @gerardo , thank you for the heads up!