You could try disabling the new, more secure capabilities by setting the
DISABLE_USER_SEED system property to true. That might allow you to get 2.160
working for you, in a less secure fashion.
There is no indication that logins are generally broken, but you’ve apparently
hit some unusual
Yes, it can be downloaded locally and distributed as a "JDK tool" defined
in the "Global tool configuration" of "Manage Jenkins". However, I was
reminded by Arnaud Heritier some time ago that downloading it and
distributing it locally may be a violation of the Oracle license agreement
or the
It started working today, it looks like it was an issue with the website of
Oracle. Could the file be downloaded manually and be provided in a local
path to Jenkins somehow?
On Wednesday, January 16, 2019 at 4:21:53 PM UTC-6, bnext...@gmail.com
wrote:
>
> Hi,
>
> While updating the JDK
I use the option deployAtEnd in the maven plugin to achieve this
Den tor. 17. jan. 2019, 16:59 skrev Cyrille Le Clerc :
> Hello AAron,
>
> This capability is niot av
>
> On Wednesday, January 16, 2019 at 5:16:22 PM UTC+1, Aaron Digulla wrote:
>>
>> Hello,
>>
>> For releases, I'd like to build
all cloud definitions are used by matching the labels of the pod templates
and your job labels
https://wiki.jenkins.io/display/JENKINS/Distributed+builds#Distributedbuilds-Nodelabelsforagents
On Thu, Jan 17, 2019 at 5:29 PM Tristan FAURE
wrote:
> Hello
> The jenkins GUI allows the creation of
Hello
The jenkins GUI allows the creation of several Kubernetes cloud, how does
it work ?
Are they all used or only one ? If many is OK Is there a way to select a
specific cluster in my pipeline ?
Thank you in advance
Tristan FAURE
--
You received this message because you are subscribed to the
Hello AAron,
This capability is niot av
On Wednesday, January 16, 2019 at 5:16:22 PM UTC+1, Aaron Digulla wrote:
>
> Hello,
>
> For releases, I'd like to build and test all Maven modules and after the
> build, deploy everything at once (otherwise, someone has to waste time to
> clean up the
I just upgraded Jenkins from 2.159 to 2.160, and then found that I could not
log on to the web interface.
Clicking "login" prompted me for my credentials as expected, and then returned
me to the Jenkins web page, but not logged in.
Clearing cookies and cache, and using a different browser, did
Hi guys, i just want to make sure are google+ API termination going to
disrupt or impact google login plugin for jenkins? maybe prevent us to
login, or get user information? https://developers.google.com/+/api-shutdown
I have tried to take a look at the
code
