Re: How to pass one of the jobs output value to the next job input in pipeline script

Thanks .. The question is how to access the variables returned from Job1 in the pipeline .. Once you access the variables, can pass the same value to second job . Job 1: Exported variable : export Docker_image=ABC Pipeline job : def j1BuildResult = build job: 'J1' def j1EnvVariables =

How to pass one of the jobs output value to the next job input in pipeline script

Hi All, I have a pipeline script job and is triggering Jobs. The requirement here is to pass one of the jobs output value to the next job . 1.How to get the value from job to the Pipeline job. 2.From Pipeline how to pass that values to the next job. Regards, Basanta -- You received this

Re: Requirement to run a set of tasks for a build in parallel, The tasks for the build are dynamic it may change

Thanks for the Info .. I am new to this Pipeline so not able to undesrstand.. Need your help for the full code that can be used .. On Monday, April 8, 2019 at 4:43:04 PM UTC+5:30, Akshay Paturkar wrote: > > Hi Basanta , > you can try custom implementation for parallal stage something like below.

Requirement to run a set of tasks for a build in parallel, The tasks for the build are dynamic it may change

Hi All, I have a requirement to run a set of tasks for a build in parallel, The tasks for the build are dynamic it may change. I need some help in the implementation of that below are the details of it. For Component 1 : 2 jobs need to trigger in parallel for Component 2 : 4 jobs need to

Parallel job Execution Through blue ocean

Hi All, Through Blue Ocean Plugin created a pipeline job and want to execute the Jobs inside the "Jenkinsfile" in parallel . Need help on this ..here is the code which is executing sequentally pipeline { agent any parallel { stages { stage('Init') { steps {

Re: Kubernetes plugin - multi clusters

on the Jenkin pipeline select the level and you can provide multiple lavels also . like cloud1 || cloud2 .. This will ensure job will execute on any of one the cloud and this will make sure job will execute on the active cluster if any one of the cluster is down/not active On Friday, January

Prov of pod template failing with "Service account may have been revoked"

Hi , My Jenkins is running on a pod and is configured to K8S. when tried to run a job .. Provision of the pod template failing with below error .. === Waiting for agent to connect (99/100): k8s-pod-vfzmj Jan 22, 2019 8:30:30 AM WARNING

java.io.IOException: remote file operation failed

Hi , Jenkins Job failing with ava.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:717) aused: java.io.IOException: Remote call on JNLP4-connect connection from

OOM seen intermittently while running jobs on K8S Cluster

Hi , While running a job on Kubernetes Cluster .. Just want to know what could be the cause of the failure .. After rerun same job passes after some time. java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at

Jenkins Master Memory is very less and subsequent jobs are failing with with OOM ..

Hi All, When Jenkins Jobs running on Jenkins Master memory is running out and later the jenkins jobs failing with OOM Error. Is there a way to find process which are locking the memory of the Jenkins Master. FATAL: command execution failed java.lang.OutOfMemoryError: unable to create new

Re: Job Failed with "java.lang.OutOfMemoryError: unable to create new native thread" On Kuberentes cluster..

On Sunday, November 11, 2018 at 2:42:43 PM UTC+5:30, pbasan...@gmail.com wrote: > > Hi All, > > While running a job on Kuberentes Cluster > > [EnvInject] - Loading node environment variables. > Building remotely on k8s-prod-cl1-pod1-v1v5j >

Re: Job Failed with "java.lang.OutOfMemoryError: unable to create new native thread" On Kuberentes cluster..

The same job on rerun after some time passed on the same salve node.. On Monday, November 12, 2018 at 11:04:24 AM UTC+5:30, pbasan...@gmail.com wrote: > > Hi , > Thanks for your response. > > on Ulimit -aH , I can see one difference on container and host > > Container : > *open files

Re: Job Failed with "java.lang.OutOfMemoryError: unable to create new native thread" On Kuberentes cluster..

Hi , Thanks for your response. on Ulimit -aH , I can see one difference on container and host Container : *open files (-n) 65536* Slave Host : *open files (-n) 327679* Will that Causeing the OOM Failure . Regards, Basanta On Monday, November 12, 2018

Job Failed with "java.lang.OutOfMemoryError: unable to create new native thread" On Kuberentes cluster..

Hi All, While running a job on Kuberentes Cluster [EnvInject] - Loading node environment variables. Building remotely on k8s-prod-cl1-pod1-v1v5j (K8S_PROD_Cl1_lab1) in workspace

Need to find the way to update the build descriptor with the cause of the build failure

Hi All, Trying to update the build descriptor with the build cause found through the "build analyser plugin". Here is the groovy Post Build Script using to update the build descriptor: = import hudson.model.Action import hudson.model.BuildBadgeAction import hudson.model.ModelObject

Re: Groovy Script to find the Cause of the Build Failure

Hi Rajendra , Thanks for the info Basically through the Build failure analyser plugin able to identify the problem now need a groovy script to get the failure cause and update the build descriptor. Regards, Basanta On Thursday, October 4, 2018 at 10:18:56 AM UTC+5:30, pbasan...@gmail.com

Re: Groovy Script to find the Cause of the Build Failure

Here is the actual output from the console log : *[BFA] Environment from category Environment Issue * *>>> here cause is the Environment * *Want the same cause to be updated on the build descriptor * [BFA] Scanning build for known causes... [BFA] Found failure cause(s):*[BFA] Environment

Re: Groovy Script to find the Cause of the Build Failure

Yes I have Different Failures .. 1. Infrastructure 2. K8S and 3. Environment .. These category of causes created by analyzing the logs through the Build Analyzer Plugin . Now the task is to update the same cause on the build descriptor so that the build metrics plugin will display the cause.

Groovy Script to find the Cause of the Build Failure

Hi All, Need a groovy Postbuild script to find the cause of each Failure .. I am using Build Failure analyzing toll to categorize the build failure and need to update the build descriptor with the Cause of the failure. Regards, Basanta -- You received this message because you are subscribed

Re: plugin to scan the Jenkins console log and determine the type of the failure

Basically i categorized the job .. based on the ERROR on the log .. now need to count how many job on each category .. On Friday, September 28, 2018 at 9:57:53 PM UTC+5:30, pbasan...@gmail.com wrote: > > Basically i categorized the job .. based on the ERROR on the log .. now > need to count

Re: plugin to scan the Jenkins console log and determine the type of the failure

Basically i categorized the job .. based on the ERROR on the log .. now need to count how many job on each category .. On Friday, September 28, 2018 at 8:02:10 PM UTC+5:30, damien.c...@collibra.com wrote: > > If you use MongoDB as backend for the storage of rules and failures (see > plugin

Re: plugin to scan the Jenkins console log and determine the type of the failure

Thanks for you reply ..is there a way to count the Number of Jobs on each category. On Thursday, September 27, 2018 at 4:48:09 PM UTC+5:30, Damien Coraboeuf wrote: > > https://plugins.jenkins.io/build-failure-analyzer ? > > On Thu, Sep 27, 2018 at 12:10 PM > > wrote: > >> Hi >> >> Is there a

plugin to scan the Jenkins console log and determine the type of the failure

Hi Is there a plugin to scan the Jenkins console log and determine the type of the failure (Infrastructure / Artifactory etc..)? and take action .. instead of marking the build as failed /warning. Regards, Basanta -- You received this message because you are subscribed to the Google Groups

Re: downgraded to 2.73.3 from 2.121.3 but plugins not yet

Then difficult to find out the compatibility of the pluigins with the Downgraded Jenkins. On Tuesday, September 25, 2018 at 10:07:33 PM UTC+5:30, slide wrote: > > Plugins will not downgrade just because you downgraded Jenkins itself. > > On Tue, Sep 25, 2018 at 9:31 AM > wrote: > >> Hi, >> >>

downgraded to 2.73.3 from 2.121.3 but plugins not yet

Hi, Even though Jenkin version is downgraded to 2.73.3 from 2.121.3 the Plugin versions still referring to the same version Installed plugins not yet downgraded infact no option to downgrade also. Artifactory Plugin version : 2.16.2 and Kubernetes : 1.8.4 Looks like some thing more need to

Error Noticed on Artifactory plugin 1.16.2 when no artifacts founds on workdir.

Hi All, How we have a Problem on Artifactory plugin 1.16.2 on a new jenkin instance 2.121.3 (Artifactory plugin 1.16.2 ) and here the jobs fails : Artifactory publish plugin throws exception when no artifacts found in the workdir .. This was not seen on enkin instance 2.121.3 with Artifactory

Jenkins is not getting connected to my kubernetes without authentication.

Hi , Using Jenkins ver. 2.121.3 and Kubernetes plugin : 1.12.6. "Manage jenkins" -> "Configure system" , in the cloud section the "Max connections to Kubernetes API" is set to the default 32. But i am getting error in here and the jenkins is not getting connected to my kubernetes without

Re: Is there a way to rerun the failed Jobs (due to the Pod creation failed or any other reason) ?

thank you very much On Monday, August 13, 2018 at 1:22:21 PM UTC+5:30, Björn Pedersen wrote: > > And for pipelines, you should also checkout the retry-block. > > Am Montag, 13. August 2018 09:50:14 UTC+2 schrieb Björn Pedersen: >> >> Hi, >> >> https://plugins.jenkins.io/naginator >>

Is there a way to rerun the failed Jobs (due to the Pod creation failed or any other reason) ?

Hi All, Is there a way to rerun the failed Jobs (due to the Pod creation failed or any other reason). Regards, Basanta -- 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

Re: Build queue hangs after timer task error on Jenkins

Here is the scenario: Basically My Jenkin master is configured with K8S dynmic plugin and Mesos dynamic plugin . While running one of the mesos job .. job hanging because the pod creation is failing on mesos .. and on jenkins log I can see this error .. Aug 07, 2018 11:37:51 PM SEVERE

Build queue hangs after timer task error on Jenkins

Build queue hangs after timer task error on Jenkins.. is there any solution for this .. -- 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

Mesos and Kuberentes configured on the same jenkin instance

Hi , I have a jenkin instance where mesos and K8S clouds configured .. If for some reason jobs need to be executed on mesos not able to start then K8S jobs also not starting . Just want to know is this expected ? Regards, Basanta -- You received this message because you are subscribed to the

jenkin instance where mesos and K8S clouds configured

Hi , I have a jenkin instance where mesos and K8S clouds configured .. If for some reason jobs need to be executed on mesos not able to start then K8S jobs also not starting . Just want to know is this expected ? Regards, Basanta -- You received this message because you are subscribed to the

Jobs failing on Slave node on Linux Host

Hi , I have a master node and jobs are running succesfully .. after adding a slave node the same job failed with below error ..Need help .. > /bin/git fetch --tags --progress https:/// > > +refs/heads/*:refs/remotes/origin/*

How to run jobs on oraclelinux container.

Hi , We have a problem on Jenkins on which container the job will run. By default jenkins job is using jnlp container to run the Jobs. inorder to run the jobs on the oraclelinux image. 1. We Successfully created docker-jnlp-slave image with oraclelinux image. 2. Able to pull docker-jnlp-slave

Re: Failed to connect to http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.local

Yes we installed Jenkins separately (not on K8s cluster). On Tuesday, November 21, 2017 at 1:22:55 PM UTC+5:30, YAN-HONG WANG wrote: > > You use Jenkins, but *not using as a service?* > > *Or?* > > 2017-11-21 8:50 GMT+01:00 YAN-HONG WANG >: > >> Hi Basanta, >> >> Because

Re: Failed to connect to http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.local

Hi Hong, Here is the detail of the Environment Installed k8s and Jenkins on the one Master server (Linux) and the jobs are running on Master.(with out slave nodes) But when we tried on 1 Master and 2 slave nodes , the jobs are failing with error = Nov 16, 2017 6:22:51 AM

Re: Failed to connect to http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.local

Hi Hong, We are using Linux machine But i think the issue reported on this thread is nothing to do with Operating System. Regards, Basanta On Monday, November 20, 2017 at 9:13:08 PM UTC+5:30, YAN-HONG WANG wrote: > > Hello, > > Do you use Ubuntu machine to be your base? > > Hong > > Am Montag,

Re: Failed to connect to http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/: jenkins.build-env.svc.cluster.local

Hi Hong, We are hitting the Same error as mentioned above .. Can you please share the steps followed to resolve this error. = Nov 16, 2017 6:22:51 AM hudson.remoting.jnlp.Main$CuiListener error SEVERE: Failed to connect to http://slc13pef.us.oracle.com:8080/tcpSlaveAgentListener/: