Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Won't Fix
-
None
-
None
-
None
-
None
Description
- create-release should not fail when building in unsigned mode on something like Jenkins:
$ docker run -i -t --privileged -v /home/jenkins/jenkins-slave/workspace/aw-explore/run2:/home/jenkins/jenkins-slave/workspace/aw-explore/run2 -v /home/jenkins/jenkins-slave/workspace/aw-explore/source/target/artifacts:/home/jenkins/jenkins-slave/workspace/aw-explore/source/target/artifacts -v /home/jenkins/jenkins-slave/workspace/aw-explore/source:/build/source -u jenkins -w /build/source hadoop/createrelease:3.1.0-SNAPSHOT_24658 /build/source/dev-support/bin/create-release --mvncache=/maven --native --dockercache --logdir=/home/jenkins/jenkins-slave/workspace/aw-explore/run2 --indocker
the input device is not a TTY
- docker executable is always found via path. users should be allowed to specify a location
- JVM location throws errors on non-Linux systems.
- create-release should exit early if no JAVA_HOME detected
- docker build command line should be output to the screen
- create-release on OS X should be smarter about homebrew location
- remove the dependence on Oracle JDK
Attachments
Attachments
Issue Links
- is depended upon by
-
HADOOP-14816 Update Dockerfile to use Xenial
- Resolved