Baptiste Mathus

I think this is related to https://github.com/asciidoctor/asciidoctor/issues/1191#issuecomment-157866155 and should just need to have the docker asciidoctor image to be rebuilt from scratch. From the link above, asciidoctor 1.5.3 is deemed...

Perfect thanks! Le 19 nov. 2015 1:10 AM, "Guillaume Scheibel" [email protected] a écrit : > Hi, > > I planned to update the container this weekend. There are several things...

CI tests run seems fishy though. I do see the new tests skipped on Windows, which is expected, but then I do not see them either under any Linux flavor....

OK, my bad :man_facepalming:, didn't click "Show more", and there're too many tests to make it practical to look for a specific one. https://ci.jenkins.io/job/Plugins/job/docker-plugin/job/PR-681/2/testReport/io.jenkins.docker.pipeline/DockerAgentTest/ =>  https://ci.jenkins.io/job/Plugins/job/docker-plugin/job/PR-681/2/testReport/io.jenkins.docker.pipeline/DockerNodeStepTest/ =>  So...

@abayer do you plan to have another look? That would be awesome, thanks!

@abayer this is conflicted FYI.

@jglick well I can show you the code we wrote for that, maybe this can be simplified, but right now I think this is a bit too complicated for what...

@jsoref can you confirm which version of `extra-enforcer-rules` you're using? This should not be reported anymore since https://github.com/mojohaus/extra-enforcer-rules/pull/36

Seems like this got closed unintendedly?

IIRC @stephenc created this project originally, and though I didn't check the commits I'd say this was done on purpose to be able to just use directly the rule name...