Re: Build failed in Jenkins: SystemML-DailyTest #635

That's great. Thank you Glenn. Deron On Fri, Nov 18, 2016 at 3:28 PM, Glenn Weidner wrote: > We've modified the Jenkins Daily Test job configuration so the workspace > does not get deleted right after the build completes. Next time, the > detailed test logs will be available at: > > https://sp

Re: Build failed in Jenkins: SystemML-DailyTest #635

We've modified the Jenkins Daily Test job configuration so the workspace does not get deleted right after the build completes. Next time, the detailed test logs will be available at: https://sparktc.ibmcloud.com/jenkins/job/SystemML-DailyTest/ws/target/failsafe-reports/ Thanks, Glenn From:

Build failed in Jenkins: SystemML-DailyTest #635

See Changes: [Deron Eriksson] [SYSTEMML-1084] Change .tar.gz artifact extensions to .tgz [Deron Eriksson] [SYSTEMML-1119] Fix duplicate declaration of exec-maven-plugin -- [...trunc

Re: Release process document for SystemML

Thanks Deron, appreciate it. We expect to have Pip Install artifact issue resolved sooner. Then possibly we can create release next week. Until formal release document becomes available, we can use document Luciano may provide. We will need following contents as a part of Release document (I am s

Re: Release process document for SystemML

Hi Arvind, Thank you for bringing this up. Just wanted to let you know we have https://issues.apache.org/jira/browse/SYSTEMML-848 to address this. I would be happy to work with Luciano in the creation of such documentation. Since Luciano has had to do all of our release deployments by himself, I w

Release process document for SystemML

Hi Luciano, Do we have document describing SystemML release process from end to end (Starting from build, tagging RC, and publishing images)?Once Pip Install artifact issue get resolved we want to create another release based on SystemML 0.11 to add Pip Install artifact, possibly next week. Tha

Re: Enabled doclint javadoc checking

+1. Thanks for going in and cleaning out the empty template comments and adding and fixing others. 👍. > On Nov 18, 2016, at 11:03 AM, dusenberr...@gmail.com wrote: > > +1. Thanks, Deron. This is great. > > -- > > Mike Dusenberry > GitHub: github.com/dusenberrymw > LinkedIn: linkedin.com/in/

Re: Enabled doclint javadoc checking

+1. Thanks, Deron. This is great. -- Mike Dusenberry GitHub: github.com/dusenberrymw LinkedIn: linkedin.com/in/mikedusenberry Sent from my iPhone. > On Nov 18, 2016, at 10:26 AM, fschue...@posteo.de wrote: > > Great! Thanks Deron! > > Please everyone also don't just make your javadoc pass t

Re: Enabled doclint javadoc checking

Great! Thanks Deron! Please everyone also don't just make your javadoc pass the build but give it some actual "doc" :) Felix Am 18.11.2016 17:53 schrieb Deron Eriksson: Hi, I have enabled javadoc doclint checking. Previously the default Java 8 doclint checking was turned off by a profile be

Enabled doclint javadoc checking

Hi, I have enabled javadoc doclint checking. Previously the default Java 8 doclint checking was turned off by a profile because of javadoc errors in the project. Since these errors have been fixed, we can now turn on the default Java 8 doclint behavior. Javadoc errors will cause the build to fail,