Displaying #maven-dev/2018-01-02.log:

Tue Jan 2 01:49:18 2018  olamy:Joined the channel
Tue Jan 2 09:23:09 2018  olamy:Joined the channel
Tue Jan 2 09:29:45 2018  olamy:Joined the channel
Tue Jan 2 13:33:47 2018  rfscholte:Joined the channel
Tue Jan 2 14:11:28 2018  stephenc:@rfscholte https://builds.apache.org/job/maven-box/job/maven-javadoc-plugin/job/master/18/ should be much nicer
Tue Jan 2 14:11:38 2018  stephenc:all the excess open tasks removed
Tue Jan 2 14:11:48 2018  stephenc:and I found a way to suppress the duplicate changelog entries
Tue Jan 2 14:12:22 2018  stephenc:plus now the fast fail will at least put the failing node into the build log at the end... so you can see which one to look at
Tue Jan 2 14:43:14 2018  rfscholte:nice work!
Tue Jan 2 15:46:32 2018  rfscholte:Joined the channel
Tue Jan 2 16:40:02 2018  rfscholte:stephenc: hmm, looks like my commits on maven.release-master weren't picked up. Can't see the changes in Jenkins :(
Tue Jan 2 17:11:21 2018  hboutemy:Joined the channel
Tue Jan 2 17:25:53 2018  stephenc:@rfscholte: likely the commits were but a bug in by optimization was causing them not to be reported... should be fixed now (though that means we have to live with duplicate changelogs :-( )
Tue Jan 2 17:27:14 2018  stephenc:rfscholte: I have deleted the builds with missing changelogs and triggered build #16 so you should now have a full changelog
Tue Jan 2 17:34:43 2018  stephenc:just that the full changelog still has duplicate commits :-(
Tue Jan 2 18:04:33 2018  rfscholte:already had the assumption it had to do with your commits today :) clean changelog would have been fine, indeed
Tue Jan 2 18:06:15 2018  rfscholte:I see what you mean... number of commits is incorrect due to these duplicates in the changelog
Tue Jan 2 21:00:43 2018  olamy:Joined the channel

Comments