On Sat 2 Dec 2017 at 10:42, Tibor Digana wrote:
> One function in Jenkinsfile is sick.
> It is pure bureaucracy where the Jenkinsfile becomes a beton.
> There is no freedom for developers in Jenkinsfile in that case.
If you don’t want Java 9 then you can turn off Java 9 using the parameters.
N
One function in Jenkinsfile is sick.
It is pure bureaucracy where the Jenkinsfile becomes a beton.
There is no freedom for developers in Jenkinsfile in that case.
The build does not need to have Java 9. It's not the reason to invest
effort. I invest effort to Jigsaw support, JUnit5 and 3.0.
It is
On Sat 2 Dec 2017 at 10:03, Tibor Digana wrote:
> Pls do not do it!
> I want to have it under control in Jenkinsfile and not to share the code
> with other projects.
I do not see that you actually have anything that needs a custom build.
We can add code coverage to the template.
The only repo
Pls do not do it!
I want to have it under control in Jenkinsfile and not to share the code
with other projects.
Surefire project is different and it must be still different.
I see Groovy libraries useful only in situations when I call Hudson API
functions and I need to avoid security issue on these
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.RequireJavaVersion
failed with message:
Detected JDK Version: 9.0.1 is not in the allowed range [1.8,1.9).
Ok finding some bugs then
On 30 November 2017 at 21:59, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> https://builds.apa
https://builds.apache.org/job/maven-wip/job/maven-surefire/job/new-jenkinsfile/
to see what it's like.
We can look into adding jacoco reporting to the standard build if it is
seen as important
