On 5/31/17 3:52 PM, Julian Hyde wrote:
On May 30, 2017, at 2:37 PM, Josh Elser <[email protected]> wrote:
I believe the solution for this in the future is to do something like `mvn
package site -DskipTests -Dcheckstyle.skip` until the first SNAPSHOT after a
release is built by Jenkins.
Thanks, I’ll try that next time.
By the way, I tried to manually create my own snapshot using [1] but it failed
because of Docker config. Do you think it would have worked if I’d updated the
version number in Dockerfile after I released? Or is it not going to be
possible to do snapshots now we have a Docker module? I’m not sure how Jenkins
manages to push snapshots when I can’t create snapshots manually.
Julian
[1]
https://calcite.apache.org/avatica/docs/howto.html#making-a-snapshot-for-calcite-committers
<https://calcite.apache.org/avatica/docs/howto.html#making-a-snapshot-for-calcite-committers>
Oh that's curious. The apache-release profile might be unnecessary for
building/deploying snapshots. Or, Jenkins has something "always" set for
its credentials which developers wouldn't typically have set. Not 100% sure.
We should be able to work around building local snapshots with the
docker module. The quick fix is to not activate the apache-release
profile, but I need to do some digging to figure out if we do need that
when deploying snapshots manually.
