Hello, responsive community!
Periodically, when checking out from github, there are such errors. if you have
encountered, please share all possible solutions or solutions to accurately
identify the culprit of the problem (network, github...):
The recommended git tool is: /usr/bin/git
using cre
Any chance this is being called from a @NonCPS method? I've seen similar
behaviour in that case.
On Monday, 14 December 2020 at 14:37:55 UTC-8 yannick...@gmail.com wrote:
> Hi,
>
> In a shared library, in a groovy script in /vars, the following code is
> working perfectly:
>
> String call(String
I've since found that removing the node{} wrapping the custom buildDeployMaven
step seems to solve the deadlock.
I'm guessing node{} was allocating an executor for the step, which then
immediately requested another executor for it's internal pipeline{} ?
On Thursday, 17 December 2020 at 15:50:
I've been using Ansible and Configuration-As-Code plugin to prop up Jenkins
Clusters at my company, and I want to prop up a local mirror to prevent the
frequent connection timeouts downloading the main jenkins.war and/or the
plugins from the various (official) sites, as well as generally speed
Are you sure that you have the Kubernetes CLI plugin installed?
https://plugins.jenkins.io/kubernetes-cli/
On Thu, Dec 17, 2020 at 8:50 AM anilkumar panditi <
anilkumar.pand...@gmail.com> wrote:
> Hi,
> My Pipeline is failing with below error.
>
> java.lang.NoSuchMethodError: No such DSL method '
Hi,
My Pipeline is failing with below error.
java.lang.NoSuchMethodError: No such DSL method 'withKubeConfig' found
among steps [approveReceivedEvent, approveRequestedEvent, archive, bat,
build, catchError, checkout, container, containerLog, createEvent,
deleteDir, dir, dockerFingerprintFrom, d
I'm trying to understand a problem with our Jenkins, where it seems
piplines get deadlocked waiting for an executor if we run many of them
simultaneously.
Jenkins 2.271 on Linux x64. We have one master node configured with 4
executors. Running a job singly shows it taking 2 slots in the Build
Anyone tried the ThreadPool in jenkins pipeline? it is not executing as
expected ? Please advise.
import java.util.concurrent.*
class MyRunnable implements Runnable{
Integer l
MyRunnable(Integer l){
this.l = l
}
void run(){
try{
print l
}
catch(Exception e){
FYI: I can, of course, create the job and build it using the `config.xml`
generated on a jenkins instance running locally -> `java -jar
jenkins-cli.jar -s http://localhost:8080 create-job maven-seed-job2 <
seed-maven-job2.xml`
So I suspect a problem with the Job DSL Plugin when the job build is
Each projects in the folder have configured Dependencies.
I can access them with project.getTransitiveDownstreamProjects() or
getTransitiveUpstreamProjects() for each project.
However I need to build all projects in order, based on their dependencies.
Calling this for each projects will only get
Hi
I created a Junit test case which is available
here:
https://github.com/ch007m/jenkins-job-dsl/blob/31efa049a95c333a8dba9b01ff2aa281b3520e34/src/test/java/dev/snowdrop/MavenJobDSLTest.java#L25-L53
where a seed job is created to populate a mavenJob using the DSL groovy
file provided
But
Hi Charles,
I am working on a pipeline (build java > build docker > deploy pod in
Openshift) and currently I have no unit test.
I think you achieved something huge !! Well done by the way :)
Could you please give me someone web links or tips in order to do the same
as you ?
Do you use https://git
Hi,
I think you should not use global variables at all : only global functions.
Trust me : you don't need global variables :)
To use global functions :
# /vars/myGlobFunc.groovy
def call() {
//
}
// This way you can call you function directly in "steps" if you are in
declarative pipeline,
I created 2 groovy scripts that I execute in a jenkins instance to figure
out the list to be used and to be configured within the `build.gradle` file
Jenkins.instance.pluginManager.plugins
.findAll { !(it.shortName in ['job-dsl', 'structs']) }
.collect { "testPlugins
'${it.manifest.mainAttribute
Hi,
Is it possible to access to the jenkins.log or the folder containing the
files as I got this error when I run a junit test case ?
Legacy code started this job. No cause information is available
Running as SYSTEM
Building in workspace /var/folders/t2/jwchtqkn5y76hrfrws7dqtqmgn/T/j
h2639
In my case, I do the following. I have a GlobalVars.groovy file with below
content.
#!/usr/bin/env groovypackage com..;public
class GlobalVars { static String myVar = ""}
Then in my Shared Library class, I use it like below.
GlobalVars.myVar = ""
Try it like this and check. Here, I have decla
16 matches
Mail list logo