Displaying #maven-dev/2017-01-11.log:

Wed Jan 11 00:25:16 2017  stephenc:Joined the channel
Wed Jan 11 05:05:55 2017  hboutemy:Joined the channel
Wed Jan 11 10:27:05 2017  rfscholte:Joined the channel
Wed Jan 11 19:13:40 2017  rfscholte:Joined the channel
Wed Jan 11 19:52:13 2017  tibor_:Joined the channel
Wed Jan 11 19:54:15 2017  tibor_:@rfscholte: Hi Robert what's new. I had busy week. Now I am going to check ML.
Wed Jan 11 19:56:10 2017  tibor_:Jira is not working.
Wed Jan 11 19:58:23 2017  stephenc:@tibor_ JIRA is working for me
Wed Jan 11 20:03:37 2017  tibor_:@stephenc: and now it is okay for me as well, but a while ago it was https://issues.apache.org/jira/secure/errors.jsp
Wed Jan 11 20:03:42 2017  tibor_:no issue, thx
Wed Jan 11 20:14:14 2017  rfscholte:Joined the channel
Wed Jan 11 20:14:43 2017  rfscholte:tibor_: Jira was being reindexed
Wed Jan 11 20:15:10 2017  tibor_:@rfscholte: Thank you Robert.
Wed Jan 11 20:20:02 2017  stephenc:https://builds.apache.org/job/maven-jenkinsfile/ I wonder how long before infra complains that we are camping out on the windows build agent
Wed Jan 11 20:20:12 2017  stephenc:I'd run on windows-2012-2 if it had git
Wed Jan 11 20:21:37 2017  rfscholte:stephenc: it looks like a corrupt jar to me, because the component lookup fails...
Wed Jan 11 20:21:58 2017  stephenc:@rfscholte well of course it will fail as it is trying to verify the jar it has
Wed Jan 11 20:22:20 2017  stephenc:and the verification fails because the proxy is set to only serve the test jar
Wed Jan 11 20:22:21 2017  tibor_:Did you guys pushed first issue from the reverted ones?
Wed Jan 11 20:22:40 2017  stephenc:@tibor_ we have done nothing on surefire
Wed Jan 11 20:22:48 2017  tibor_:I mean Maven
Wed Jan 11 20:23:06 2017  stephenc:@tibor_ no, currently trying to get the integration tests passing
Wed Jan 11 20:23:15 2017  tibor_:ah, okay
Wed Jan 11 20:23:37 2017  stephenc:all changes need to build clean on a branch as verified by https://builds.apache.org/job/maven-jenkinsfile/ before being merged to master
Wed Jan 11 20:23:45 2017  tibor_:I will check maven-jenkinsfile, I am interested
Wed Jan 11 20:24:07 2017  stephenc:you can stage your changes in a branch and then within 15 minutes after pushing the branch there will *magically* be a build job dedicated for that branch
Wed Jan 11 20:24:30 2017  stephenc:the build job will run the unit and integration tests on linux and windows with both java 7 and java 8
Wed Jan 11 20:24:42 2017  stephenc:takes about 2 hours when the jenkins cluster is idle
Wed Jan 11 20:27:33 2017  tibor_:What's better, jenkinsfile or multibranch. I have never configured before but I want the same in my company.
Wed Jan 11 20:27:57 2017  stephenc:@tibor_ Pipeline Multibranch Plugin for the win
Wed Jan 11 20:28:04 2017  tibor_:Ubuntu
Wed Jan 11 20:29:01 2017  stephenc:@tibor_ https://github.com/jenkins-infra/jenkins.io/pull/540/files is actually what you want
Wed Jan 11 20:29:03 2017  tibor_:parameterized build is not suitable?
Wed Jan 11 20:29:28 2017  stephenc:you can do parameterized also
Wed Jan 11 20:29:49 2017  stephenc:you will also probably want https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Model+Definition+Plugin
Wed Jan 11 20:30:00 2017  stephenc:that's the real joy
Wed Jan 11 20:30:16 2017  stephenc:I'm waiting for the 1.0 release the week of FOSDEM before I pester INFRA to upgrade
Wed Jan 11 20:30:35 2017  tibor_:I appreciate
Wed Jan 11 20:31:08 2017  tibor_:1.0 of what?
Wed Jan 11 20:32:53 2017  stephenc:1.0 release of Pipeline Model Definition
Wed Jan 11 20:33:00 2017  stephenc:that is a much nicer syntax for Jenkinsfile
Wed Jan 11 20:33:11 2017  stephenc:and it should work well with Blue Ocean
Wed Jan 11 20:38:35 2017  tibor_:@stephenc: the Blue Ocean looks interesting. You are good source of information. Thx
Wed Jan 11 20:43:19 2017  stephenc:@tibor_ well I'm one of the Jenkins developers
Wed Jan 11 20:43:47 2017  stephenc:#3 on https://github.com/jenkinsci/jenkins/graphs/contributors
Wed Jan 11 20:49:58 2017  tibor_:@stephenc: I know that you work in CloudBees and established JUnit build. I was that time in JUnit and convinced JUnit committer to use Maven.
Wed Jan 11 20:50:12 2017  tibor_:Unfortunately JUnit 5 uses Gradle
Wed Jan 11 20:59:30 2017  stephenc:@tibor_ ACK well maybe we can win them back with Maven 5.0.0
Wed Jan 11 21:00:51 2017  tibor_:how?
Wed Jan 11 21:01:28 2017  stephenc:well Maven 5.0.0 is going to be awesome
Wed Jan 11 21:01:39 2017  tibor_:feature like new pom structure, maybe.
Wed Jan 11 21:02:27 2017  tibor_:I am looking for incremental build in Maven. Therefore the ambition in Surefire is extensions because users want to run only changed test
Wed Jan 11 21:03:24 2017  tibor_:Maybe SCM extension in Surefire. Some Java Interface and users can implement it. I won't.
Wed Jan 11 21:04:06 2017  tibor_:Eclipse Compiler is different story.
Wed Jan 11 21:04:47 2017  stephenc:@tibor_ you'd need per-test code coverage to have that effectively
Wed Jan 11 21:05:37 2017  tibor_:right, not that easy, I know
Wed Jan 11 21:10:02 2017  stephenc:I'd much rather have the tests run in brittle order first
Wed Jan 11 21:10:37 2017  stephenc:less clear if I want fast or slow first
Wed Jan 11 21:11:10 2017  stephenc:but the tests that are most likely to fail (new or failed last time or have the highest failure rate) should be first in a fail fast mode
Wed Jan 11 21:11:55 2017  tibor_:this was user's requirement as well
Wed Jan 11 21:12:05 2017  tibor_:runorder does not have this?
Wed Jan 11 21:12:35 2017  tibor_:this means, run previously failed tests first
Wed Jan 11 21:12:43 2017  tibor_:Fail-Fast feature was released
Wed Jan 11 21:12:53 2017  tibor_:in 2.19 or 2.19.1
Wed Jan 11 21:16:00 2017  tibor_:check this config: -Dsurefire.runorder="failedfirst"
Wed Jan 11 21:21:12 2017  tibor_:fail-fast: -Dsurefire.skipAfterFailureCount=1, the first failed test stops the plugin

Comments