While I can confirm that compilation works after assuring that mvn is using
the Java 8 and not Java 9, the question is still valid... why on 2018 we
are still unable to compile jenkins plugins using the current stable
version of Java (1.9).
The problem seems to be specific to annotations/hudson
I am still looking for this because the use of JJB is a productivity killer
but I didn't find an answer yet.
I did asked the same question
at
https://stackoverflow.com/questions/45054290/how-to-manage-multiple-jenkins-pipelines-from-a-single-repository
hoping that this will allow us to find a
Did you finish your implementation? Groovy is far from being my native
language and it would be really helpful if you could share a snippet that
is doing the subdirectory Jenkinsfile discovery and loading.
On Thursday, July 21, 2016 at 1:43:18 AM UTC+1, slide wrote:
>
> The way I am planning on
I do like Jenkins pipelines and the fact that now we can control Jenkins
jobs via an inside repository file. I also love the looks of the upcoming
Blue Ocean interface and I can't wait to see it as default interface.
Now, the reality is that there is a serious problem which seems to be
ignored
I am wondering if you've found an workaround, this bug makes AD binding
almost useless in Jenkins.
On Tuesday, November 22, 2011 6:47:24 PM UTC, Maven User wrote:
>
> Hi all -
>
> I think we're having a similar issue to:
>
> https://issues.jenkins-ci.org/browse/JENKINS-4895
>
>
>
Is there a solution for this? /thanks
On Friday, July 15, 2011 1:53:58 PM UTC+1, Martin B. wrote:
>
> Hi all!
>
> I have disabled anonymous access to our Jenkins instance.
> Is it somehow possible to display a custom message on the login screen
> when not logged in?
>
>
>
