Hi, I have created the following jobs:
- cTAKES-trunk-Java-1.8 <https://builds.apache.org/view/C/view/Apache%20cTAKES/job/cTAKES-trunk-Java-1.8/> - cTAKES-trunk-Java-1.9 <https://builds.apache.org/view/C/view/Apache%20cTAKES/job/cTAKES-trunk-Java-1.9/> As you may see, both of them fail, and this is the proper behavior. The previous job (i.e. ctakes-trunk-compiletest <https://builds.apache.org/view/C/view/Apache%20cTAKES/job/ctakes-trunk-compiletest/>) used the default Jenkins behavior, which uses: -Dmaven.test.failure.ignore=true. As a consequence, each build was reported as stable. Another consequence was the improper identification of tests (34 tests instead of 70 tests). I left the old jobs untouched, and the community should choose which jobs prefers to use and how it would like to proceed forward. Are there any features that the community was looking for Jenkins integration (e.g. Jenkinsfile, javadocs, support for 3.x and 4.x etc)? Alex On Thu, Sep 28, 2017 at 7:43 PM, Alexandru Zbarcea <[email protected]> wrote: > Thank you James for your feedback, > > Alex > > On Thu, Sep 28, 2017 at 7:05 PM, James Masanz <[email protected]> > wrote: > >> Thanks Alex, that's great! >> >> -- James >> >> On Thu, Sep 28, 2017 at 5:40 PM, Alexandru Zbarcea <[email protected]> >> wrote: >> >> > Hi, >> > >> > I have created a new Jira Issue[1] regarding CI/CD where I started to >> work >> > on improvements of the current pipeline. >> > >> > I have helped Apache Infra in the past and I have enough karma to help >> this >> > project with the right automation. >> > >> > I look forward to your feedback and advice, and maybe we can collect in >> > CTAKES-458 [1] those things that would improve cTAKES build and release >> > process. >> > >> > Alex >> > >> > [1] - https://issues.apache.org/jira/browse/CTAKES-458 >> > >> > >
