Sorry to bring this up again, but I am just curious:
Sverre wrote (a) „Both these methods [(checkUpstream and checkDownstream)]
make[s] a call to releaseUtility.getReleaseBranch.” and (b) that both are
annotated with “@NonCPS” and (c) that the latter
(releaseUtility.getReleaseBranch) is
There is an option to restrict job namingŠdo you have it checked on?
From: on behalf of Laura López Senderos
Reply-To:
Date: Tuesday, July 30, 2019 at 5:04 AM
To: Jenkins Users
Subject: Re: Create new item - Item name error 'Only alphanumerical
characters allowed'
Hi,
Here i post our
Louis,
To answer your last question, if you decide to use declarative pipelines in
the end you can use the built-in tools like the declarative directive
generator and snippet generator. They will provide much the same UI as a
classic freestyle project which you configure according to your
Hi,
Here i post our list of plugins with their versions:
Active Directory Plugin - 2.16
Android Emulator Plugin - 3.0
Ant Plugin - 1.9
Apache HttpComponents Client 4.x API Plugin - 4.5.5-3.0
Authentication Tokens API Plugin - 1.3
Authorize Project - 1.3.0
bouncycastle API Plugin - 2.17
Branch
Sverre mentioned that checkUpstream and checkDownstream call “build” and
“println”. Since “build” can be an async step if you pass "wait: true”, and I
wasn’t sure exactly how they were using it, I recommended removing @NonCPS from
those methods.
If checkUpstream and checkDownstream only use
Thank you very much Shaun, you've hit right!
There's an option in Jenkins management to restrict the job names: manage
jenkins -> configure system -> restrict project naming.
We've a pattern to allow only alphanumerical characters, but with some
jenkins or plugin upgrade this pattern has been
Hi everyone,
my Jenkins Pipeline prints the following message:
expected to call java.util.LinkedHashMap.action but wound up catching
org.jenkinsci.plugins.workflow.cps.CpsClosure2.call
The Jenkinsfile is
pipeline {
agent { label "Linux-Agent" }
stages {
stage("Stage") {
steps {
On Tue, Jul 30, 2019 at 4:35 PM Mark Waite
wrote:
> I launch my Windows 10 ssh agents using the instructions from the
> ssh-slaves plugin page:
>
>
> https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/CONFIGURE.md#launch-windows-slaves-using-microsoft-openssh
>
> They use the
I launch my Windows 10 ssh agents using the instructions from the
ssh-slaves plugin page:
https://github.com/jenkinsci/ssh-slaves-plugin/blob/master/doc/CONFIGURE.md#launch-windows-slaves-using-microsoft-openssh
They use the Microsoft OpenSSH server on Windows 10.
I launch JNLP Windows agents
Win 7 64 bit.
>
>>
--
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-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
Thanks once again Mark.
May I bug you for some more info? I was really hoping to answer this on my
own, but I feel like I'm chasing my tail. Whenever I do searches for
Jenkins agent launch methods, I'm predominantly directed to a description
of JNLP usage or, to a lesser extent, SSH; neither
The Chocolatey package for OpenSSH says that it should work on Windows 7
64-bit. I may have missed an earlier email, are your systems 32 or 64-bit
systems?
On Tue, Jul 30, 2019, 10:39 Steve K wrote:
>
> Thanks once again Mark.
> May I bug you for some more info? I was really hoping to answer
Thanks a lot for the clarification/enlightenment, Devin!
From: jenkinsci-users@googlegroups.com On
Behalf Of Devin Nusbaum
Sent: Dienstag, 30. Juli 2019 16:49
To: jenkinsci-users@googlegroups.com
Subject: Re: Pipeline: Expected call wound up catching different method
Sverre mentioned that
13 matches
Mail list logo
