Hi,

I wanted to see if anyone has used the Gradle build to publish the
release/snapshot artifacts to custom repo?

So far I found the following (attempting to publish a particular Maven
artifact):

./gradlew :beam-runners-flink_2.11-job-server:publish -Ppublishing
-PdistMgmtSnapshotsUrl=https://somecustomrepo/libs-snapshots --no-parallel
--no-daemon

It gets to the point of attempting deploy to the remote repo, but fails due
to hardcoded server IDs:

https://github.com/apache/beam/blob/b82263390af57a2d52c5d7b257470bc837606e4e/buildSrc/src/main/groovy/org/apache/beam/gradle/BeamModulePlugin.groovy#L817

When the version isn't -SNAPSHOT, then I guess it would instead be
-PisRelease, the build will fail because it expects gpg to run, which I
don't need for what I'm trying to do.

Have others attempted third party builds for the Python SDK or Docker
images? Any gotchas to share?

Thanks,
Thomas

Reply via email to