Description
Debian oozie packages built through bigtop do not appear to be valid;
For example, the debs in:
http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Oozie/label=lucid/
contain neither the .war file, the exploded .war file, or the scripts to generate a new .war file.
By overlaying the debianization patches (no idea where they come from, but it seems to be from bigtop...) onto a 3.2.0-incubator tarball and build, the problem becomes clearer:
debian/rules calls debian/install_oozie.sh --build-dir=.
install_oozie.sh effectively does (cd ${SOMEWORKDIR}; tar xvf ${BUILDDIR}/oozie.war);
Changing build-dir=`pwd` seems to fix the issue for me, though there are also probably cleaner ways.
Disconcertingly, this appears in the build output ( http://bigtop01.cloudera.org:8080/job/Bigtop-trunk-Oozie/label=lucid/252/consoleText )
+ jar xf ./oozie.war
java.io.FileNotFoundException: ./oozie.war (No such file or directory)
at java.io.FileInputStream.open(Native Method)
at java.io.FileInputStream.<init>(FileInputStream.java:106)
at java.io.FileInputStream.<init>(FileInputStream.java:66)
at sun.tools.jar.Main.run(Main.java:238)
at sun.tools.jar.Main.main(Main.java:1149)
+ failIfNotOK
+ [ 1 != 0 ]
+ exit 0
which would suggest this failure is not failing the build, even though it produces unstartable packages.
Attachments
Issue Links
- is related to
-
BIGTOP-791 Bump Oozie to 3.3.0
-
- Closed
-
