I'm a big +1 on this.
On Tue, Dec 3, 2019 at 11:05 AM Jeff Thompson
wrote:
> For historical reasons, Jenkins still ships with old, deprecated
> protocols, JNLP1-connect, JNLP2-connect, and JNLP3-connect. These all
> have fundamental issues and known bugs. They were all superseded by the
> JNLP4-
Hi,
My current quest is to figure out how to add an SSH public key to a local
user.
After searching multiple sources on the internet, I still have not been
able to find any helpful information on this.
My preferred method would be using the 'Configuration-as-Code' plugin, but
I am happily will
For historical reasons, Jenkins still ships with old, deprecated
protocols, JNLP1-connect, JNLP2-connect, and JNLP3-connect. These all
have fundamental issues and known bugs. They were all superseded by the
JNLP4-connect protocol released in Jenkins 2.27 over three years ago
(October 2016). The
It would be super useful agent and templates could come from workflow
libraries so that they could be shared
man. 2. des. 2019, 17:16 skrev Carlos Sanchez :
> No, It has to live in the same repo
>
> On Mon, Dec 2, 2019, 16:39 YD wrote:
>
>> Hi all
>>
>> in kubernetes plugin i want to use yaml th
Yes, but
yamlFile './k8s/someyaml.yaml'
On Tue, Dec 3, 2019 at 11:41 AM YD wrote:
> thanks Carlos , it did work fine when i copy the file (someyaml.yaml) to
> the root of the repo
> can i put the file in some folder (same repo) and use something like below
> pipeline {
> agent {
>
thanks Carlos , it did work fine when i copy the file (someyaml.yaml) to
the root of the repo
can i put the file in some folder (same repo) and use something like below
pipeline {
agent {
kubernetes
{
yamlFile '/k8s/someyaml.yaml'
}
}
On Monday, December 2, 2019 at 6:16
But I see the function name is ` checkPluginsWithoutWarnings ` for
compatible.
On Tue, Dec 3, 2019 at 3:05 PM 'Björn Pedersen' via Jenkins Users <
jenkinsci-users@googlegroups.com> wrote:
> Hi,
>
> Am Dienstag, 3. Dezember 2019 08:00:10 UTC+1 schrieb YanJun Shi:
>>
>> Hi, everybody
>>
>> W
The same issue has been reported here:
https://issues.jenkins-ci.org/browse/JENKINS-59145
The solution was to skip upgrading the "Prometheus metrics" plugin.
If you have already updated the plugin, then downgrade it and restart JS.
On Thursday, October 17, 2019 at 8:22:26 PM UTC+3, kochrist wrote
Hi Devin,
thanks for the answer. I will give it a try and let you know.
Thank you for your help.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-use
