Re: How to prevent Jenkins from adding single quotes to parameterized vlaues

2020-01-20 Thread Aaron G
It IS adding the single quotes to build parameters!

On Friday, December 18, 2015 at 7:58:04 PM UTC-5, Daniel Beck wrote:
>
> I answered this on IRC. Here's basically the same answer again: 
> http://stackoverflow.com/a/34364786 
>
> On 18.12.2015, at 22:57, no...@gmx.com  wrote: 
>
> > I've also tried doing this: 
> > Name: OPTS 
> > Default Value: -o tmp -e "arg1=${VAR1} arg2=${VAR2} arg3=${VAR3}" 
> > 
> > Execute shell command: 
> > ARGS=$(echo $OPTS) 
> > ./build_app $ARGS 
> > 
> > Console Output: 
> > 
> > ++ echo -o tmp -e '"arg1=value1' arg2=value2 'arg3=value3"' 
> > + ARGS='-o tmp -e "arg1=${VAR1} arg2=${VAR2} arg3={VAR3}"' 
> > 
> > + ./build_app  -o tmp -e '"arg1=value1' arg2=value2 'arg3=value3"' 
> > 
> > So it seems the parameter variable itself doesn't contain the single 
> quotes, just when it's being referenced. And the single quotes only appear 
> around wherever there's double quotes in the string. 
> > 
> > On Friday, December 18, 2015 at 4:21:20 PM UTC-5, no...@gmx.com wrote: 
> > I basically have a string parameter that contains values from other 
> parameter fields, which I then use again in the Execute shell command. 
> > However, Jenkins adds single quotes in erroneous places within that 
> string, which makes the executing application unable to parse the 
> arguments. 
> > 
> > Example: 
> > 
> > Name: OPTS 
> > Default Value: -e "arg1=${VAR1} arg2=${VAR2} arg3={VAR3}" 
> >  
> > Execute shell 
> > Command: ./build_app $OPTS 
> > 
> > 
> > Console Output: 
> > ./build_app -e '"arg1=value1' arg2=value2 'arg3=value3"' 
> > 
> > 
> > Notice the placement of the single quotes preceding the opening double 
> quote and after value1, and before arg3 and after the closing double quote. 
> These were not added by me. 
> > 
> > I have also tried: 
> > Command: ./build_app $(echo $OPTS) 
> > 
> > but it renders the same results. 
> > 
> > I am trying to figure out if this is expected behavior or if this is an 
> actual bug. 
> > The only other mention of this issue was found here (which went 
> unanswered): 
> http://stackoverflow.com/questions/28260083/how-do-i-prevent-jenkins-from-single-quoting-the-parameterized-value
>  
> > 
> > I am currently running Jenkins 1.642. 
> > 
> > 
> > Thanks! 
> > 
> > -- 
> > 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 jenkins...@googlegroups.com . 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/ae6da2f1-0391-4f15-97e8-e114734dc1a2%40googlegroups.com.
>  
>
> > For more options, visit https://groups.google.com/d/optout. 
>
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/3d35cd9a-0dd6-407a-8ccf-a88c6b156452%40googlegroups.com.


Jenkins Integration with LDAP -- Issue

2020-01-20 Thread gaurav gundal
 

Hi Everyone,


I am trying to configure Jenkins with the  ldap,but I am getting error as 
mentioned below . Please let me know if you know about below error


 

*Ldap Integration with the Jenkins *

 

Below are the Jenkins Setup details

Jenkins Version - Jenkins ver. 2.204.1 

Jenkins Ldap plugin – 1.21

 

*LdapSearch from the Jenkins Master *

ldapsearch -x -h xxx -p 389 -D "CN=xx,OU=bb,OU=aa,DC=qq,DC=pp,DC=com"  -b  
"OU= aa,DC= qq,DC=pp,DC=com" "(sAMAccountName=xx)"

*Result stripped out -- Succesful*

Search: 2

Result: 0 Success

# numResponses: 2

# numEntries: 1

 

 

So I configured the Ldap through Jenkins UI

With below details

*Test 1* : 

Server : xxx:389

rootDn: DC= qq,DC=pp,DC=com

ManagerDn: CN=xx,OU=bb,OU=aa,DC=qq,DC=pp,DC=com

Manager Password : x

Error : 

LdapCallback;LDAP response read timed out, timeout used:6ms.; nested 
exception is javax.naming.NamingException: LDAP response read timed out, 
timeout used:6ms.; remaining name 

User lookup: failed for user "xx"

 

*Test 2* : 

Server : xxx:389

rootDn: DC= qq,DC=pp,DC=com

ManagerDn: CN=xx,OU=bb,OU=aa,DC=qq,DC=pp,DC=com

Manager Password : x

Environment Properties: com.sun.jndi.ldap.connect.pool - 
false

 

*Error*: 

LdapCallback;LDAP response read timed out, timeout used:6ms.; nested 
exception is javax.naming.NamingException: LDAP response read timed out, 
timeout used:6ms.; remaining name 

User lookup: failed for user "xx"

 

*Test 3*

Server : xxx:389

rootDn: DC= qq,DC=pp,DC=com

ManagerDn: CN=xx,OU=bb,OU=aa,DC=qq,DC=pp,DC=com

Manager Password : x

Environment Properties: com.sun.jndi.ldap.connect.pool - 
false

   Group membership : Parser user attribute for list of LDAP 
groups

 

*Error*: Same error

 


-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/d9d4dfa4-29a4-4bdd-8517-1f4905618533%40googlegroups.com.


job-dsl: Dynamic DSL - gitscmsource - includes

2020-01-20 Thread Alex

pipeline {
   agent any
   stages {
   stage('test') {
   steps {
   jobDsl scriptText: 
"""multibranchPipelineJob("job-features") {
branchSources {
branchSource {
 source {
   git {
  
id('123456789')
remote("gir-
url.git")
  includes("
feature/*")
  }
  }
  strategy {
 
defaultBranchPropertyStrategy 
{
props {

noTriggerBranchProperty()
  }
  }
  }
  }
   }
   configure { 
  def traits = it / sources / data 
/ 'jenkins.branch.BranchSource' / source / traits
 traits << 
'jenkins.plugins.git.traits.BranchDiscoveryTrait' {}
 }
   triggers {
   periodic(5)
   }
orphanedItemStrategy {
   discardOldItems {
   daysToKeep(3)
   numToKeep(3)
   }
   }
   }"""
   }
   }
   }
}

I am trying to create a job using job-dsl to seed a multibranch job that 
includes auto discovery of branches and the supress scm strategy. For some 
reason in this format the includes option is not working. Any ideas?

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/c0499942-f07f-4077-ac93-ccfaa1f55a1c%40googlegroups.com.


JAVA_HOME on Windows?

2020-01-20 Thread David Aldrich
Hi

When running a Visual Studio job from a declarative script on a Windows
agent I see:

E:\jenkins\workspace\CMake_tests_1_Windows_trunk>call "C:\Program
Files (x86)\Microsoft Visual
Studio\2017\BuildTools\VC\Auxiliary\Build\vcvars64.bat"
\Java\jre1.8.0_241\bin"" was unexpected at this time.


I want to check the value of JAVA_HOME. Where is that set for a Windows agent?


Best regards

David

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/CAJK_iegQXheUok%3DpY8DV25GtjKK0D_a5fr6WD56JXPbpzs9DgQ%40mail.gmail.com.


Re: Perform actual hardware tests using jenkins pipeline and kubernetes

2020-01-20 Thread Andrey Babushkin

Hi,
As far as I understood you're using Jenkins Kubernetes plugin and you have 
your own Kubernetes cluster with a few physical nodes connected to it.
In that case you should label your Kubernetes nodes like this (assuming you 
have working kubectl setup):
kubectl label node node1.example.com hw_type=type1

kubectl label node node2.example.com hw_type=type2

Then you should specify label you need in podTemplate section of your 
Jenkins pipeline (I slightly changed code from examples folder in 
Kubernetes plugin repo - 
https://github.com/jenkinsci/kubernetes-plugin/blob/master/examples/maven.groovy)

podTemplate(nodeSelector: 'hw_type=type1', containers: [
containerTemplate(name: 'maven', image: 'maven:3.3.9-jdk-8-alpine',
  ttyEnabled: true, command: 'cat',

)
  ]) {

  node(POD_LABEL) {
stage('Tests on hardware type 1') {
  git 'https://github.com/jenkinsci/kubernetes-plugin.git'
  container('maven') {
  sh 'mvn -B clean package'
  }
}
  }
}


On Monday, January 20, 2020 at 9:19:00 AM UTC+3, touseef wrote:
>
> Can anyone point me in right direction,
>
> I have a use case as follow:
>
> Kubernetes master running the jenkins and i have n number of physical 
> machine connected with different hardwares,So what i want to achieve is 
> when a specific job is triggered in jenkins to execute a test on hardware , 
> k8's(kubernetes master) should route and connect to that machine in a pool 
> which has requiste hardware and execute the tests.
>
> Any pointer how to achieve is appreciated
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/e8069c44-fab0-44b0-8708-d453d31724ad%40googlegroups.com.


Re: Windows JNLP agent doesn't see PATH

2020-01-20 Thread Vitaly Karasik
Simon, thank you,
but as far as I see it's not the case - 'C:\Windows\system32' was part of 
the PATH from the start, I didn't add it.

On Monday, January 20, 2020 at 4:22:57 PM UTC+2, Simon Richter wrote:
>
> Hi, 
>
> On Mon, Jan 20, 2020 at 04:55:40AM -0800, Vitaly Karasik wrote: 
>
> > I see really weird behaviour on my Windows (Windows Server 2019) Jenkins 
> > agent (launched by JNLP). 
>
> I can't claim to have understood Windows agents' environment handling yet, 
> but it seems that the entire environment is frozen in the state the agent 
> had when it was first connected (i.e. saved then, and restored from the 
> master whenever the client reconnects). 
>
> Deleting and readding the agent seemed to help for me (use the same agent 
> name so it generates the same secret), this will refresh the environment 
> variables from the client. 
>
>Simon 
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/23dae2d7-dfd5-4011-825c-a9ef020c5fa6%40googlegroups.com.


Re: About Jenkins slowness for version 2.138 in multi branch pipeline project

2020-01-20 Thread Mark Waite
You might install the Jenkins Health Advisor by CloudBees and see if it has
suggestions for your instance.  It will check for conditions that have been
found to cause problems in other installations and report them to you in a
daily e-mail message.

https://jenkins.io/blog/2019/11/22/jenkins-health-advisor-by-cloudbees/

On Mon, Jan 20, 2020 at 6:49 AM Mahesh Wabale  wrote:

> We are using following JAVA_OPTS CONFIG in Jenkins deployment .
>
> "name": "JAVA_OPTS",
> "value": "-XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent
> -XX:+ParallelRefProcEnabled -XX:+UseStringDeduplication
> -XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20
> -XX:+UnlockDiagnosticVMOptions -XX:NativeMemoryTracking=summary
> -XX:G1SummarizeRSetStatsPeriod=1 -Xms2048m -Xmx8192m"   , and 48 GB ram
> allocated for master Jenkins pod as per initial observation GC is working
> correctly its not going beyond 8 gb . But observing RAM USAGE of master pod
> is continusly increasing day by day . Some time it reaches to memory 48 GB
> seems like it taking memory for cache .How can we control ram memory size ,
> or is it possible to free cache memory from Jenkins Docker image which can
> solve my problem .
>
> On Mon, Jan 20, 2020, 3:45 PM Mahesh Wabale  wrote:
>
>> Thanks Marc ,
>>
>> We will check if it helps , Currently we have "maximum durability"
>> settings configured now , we are planning to make it to "
>> performance-optimized"  .  We have observed couple of time disc IO is
>> very high sometimes .
>>
>> On Monday, January 20, 2020 at 5:54:38 AM UTC+5:30, Mark Waite wrote:
>>>
>>> I'm not aware of an open bug in Jenkins related to being slow over NFS,
>>> though Jenkins is quite disc intensive and runs best with local disc drives.
>>>
>>> You might refer to the following articles for more information:
>>>
>>>- Jenkins pipeline durability settings documentation
>>>
>>> 
>>>("Will Higher-Performance Durability Settings Help Me? Yes, if your 
>>> Jenkins
>>>instance uses NFS, magnetic storage, runs many Pipelines at once, or 
>>> shows
>>>high iowait.")
>>>- CloudBees NFS guide
>>> 
>>> (multiple
>>>pages of tuning recommendations)
>>>
>>>
>>>
>>> On Fri, Jan 17, 2020 at 5:42 AM Mahesh Wabale 
>>> wrote:
>>>
 Hi Team ,

 We are using observing Jenkins slowness issues for jenkins version
 2.138 in multi branch pipeline project .
 We have also used NFS 4.1 .

 After Jenkins restart it works for few days but at some stage it stuck
 and becomes unresponsive . As per observation only restart will solve this
 issue for next few days . We require frequent restart due to this issue .
 Have anyone observed similar issues , or  this is open bug in Jenkins ?


 --
 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 jenkins...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/jenkinsci-users/319f90ff-5410-4495-bb46-51d61745b3e8%40googlegroups.com
 
 .

>>>
>>>
>>> --
>>> Thanks!
>>> Mark Waite
>>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "Jenkins Users" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/jenkinsci-users/8MnTICGxQ-o/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/8a711ba9-4433-4e62-9170-50e7f5c82bdd%40googlegroups.com
>> 
>> .
>>
> --
> 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
> https://groups.google.com/d/msgid/jenkinsci-users/CABOY2ebxtXCGqDXKcfk7kzh0CgjvajTmyiOSni4EPF516gy9iA%40mail.gmail.com
> 
> .
>


-- 
Thanks!
Mark Waite

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe 

Re: Windows JNLP agent doesn't see PATH

2020-01-20 Thread Simon Richter
Hi,

On Mon, Jan 20, 2020 at 04:55:40AM -0800, Vitaly Karasik wrote:

> I see really weird behaviour on my Windows (Windows Server 2019) Jenkins 
> agent (launched by JNLP).

I can't claim to have understood Windows agents' environment handling yet,
but it seems that the entire environment is frozen in the state the agent
had when it was first connected (i.e. saved then, and restored from the
master whenever the client reconnects).

Deleting and readding the agent seemed to help for me (use the same agent
name so it generates the same secret), this will refresh the environment
variables from the client.

   Simon

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/20200120142245.GA12625%40psi5.com.


Re: About Jenkins slowness for version 2.138 in multi branch pipeline project

2020-01-20 Thread Mahesh Wabale
We are using following JAVA_OPTS CONFIG in Jenkins deployment .

"name": "JAVA_OPTS",
"value": "-XX:+UseG1GC -XX:+ExplicitGCInvokesConcurrent
-XX:+ParallelRefProcEnabled -XX:+UseStringDeduplication
-XX:+UnlockExperimentalVMOptions -XX:G1NewSizePercent=20
-XX:+UnlockDiagnosticVMOptions -XX:NativeMemoryTracking=summary
-XX:G1SummarizeRSetStatsPeriod=1 -Xms2048m -Xmx8192m"   , and 48 GB ram
allocated for master Jenkins pod as per initial observation GC is working
correctly its not going beyond 8 gb . But observing RAM USAGE of master pod
is continusly increasing day by day . Some time it reaches to memory 48 GB
seems like it taking memory for cache .How can we control ram memory size ,
or is it possible to free cache memory from Jenkins Docker image which can
solve my problem .

On Mon, Jan 20, 2020, 3:45 PM Mahesh Wabale  wrote:

> Thanks Marc ,
>
> We will check if it helps , Currently we have "maximum durability"
> settings configured now , we are planning to make it to "
> performance-optimized"  .  We have observed couple of time disc IO is
> very high sometimes .
>
> On Monday, January 20, 2020 at 5:54:38 AM UTC+5:30, Mark Waite wrote:
>>
>> I'm not aware of an open bug in Jenkins related to being slow over NFS,
>> though Jenkins is quite disc intensive and runs best with local disc drives.
>>
>> You might refer to the following articles for more information:
>>
>>- Jenkins pipeline durability settings documentation
>>
>> 
>>("Will Higher-Performance Durability Settings Help Me? Yes, if your 
>> Jenkins
>>instance uses NFS, magnetic storage, runs many Pipelines at once, or shows
>>high iowait.")
>>- CloudBees NFS guide
>> 
>> (multiple
>>pages of tuning recommendations)
>>
>>
>>
>> On Fri, Jan 17, 2020 at 5:42 AM Mahesh Wabale  wrote:
>>
>>> Hi Team ,
>>>
>>> We are using observing Jenkins slowness issues for jenkins version 2.138
>>> in multi branch pipeline project .
>>> We have also used NFS 4.1 .
>>>
>>> After Jenkins restart it works for few days but at some stage it stuck
>>> and becomes unresponsive . As per observation only restart will solve this
>>> issue for next few days . We require frequent restart due to this issue .
>>> Have anyone observed similar issues , or  this is open bug in Jenkins ?
>>>
>>>
>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/319f90ff-5410-4495-bb46-51d61745b3e8%40googlegroups.com
>>> 
>>> .
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/jenkinsci-users/8MnTICGxQ-o/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/8a711ba9-4433-4e62-9170-50e7f5c82bdd%40googlegroups.com
> 
> .
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/CABOY2ebxtXCGqDXKcfk7kzh0CgjvajTmyiOSni4EPF516gy9iA%40mail.gmail.com.


Windows JNLP agent doesn't see PATH

2020-01-20 Thread Vitaly Karasik
I see really weird behaviour on my Windows (Windows Server 2019) Jenkins 
agent (launched by JNLP).
Jenkins user has C:\Windows\system32 into its PATH (as well as other 
relevant paths).
But 

  bat '''
any-command
  '''

fails with 

  'cmd' is not recognized as an internal or external command, 
  operable program or batch file.

unless I'm using PATH = "%Path%;C:\\WINDOWS\\SYSTEM32" into this step 
'environment'.

So should I re-define the whole user's environment into my job or I'm 
missing something?

TIA,
Vitaly


-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/dd328de1-0f93-48ad-92af-e2d0a30fbffc%40googlegroups.com.


Missing jenkin jobs.

2020-01-20 Thread Charles Ong
Hello,
So recently i fixed a bug and push my code up to github. Then jenkin was 
running fine and it actually push to the AWS but it did not deploy 
accordingly. During which, i thought of restarting the AWS and it changes 
the ip address for the server. Upon the ip address change, my previous 
information on the jobs i previously did on jenkin disappear. I tried to 
look it up through cmd and was able to find it in the file but it just not 
shown on the jenkin page. I tried to create another project and it was 
shown in the same path as the missing projects. Any suggestion on how to 
get back my projects to be shown on the Jenkins webpage?

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/a59a66f8-3f76-4782-b687-9709874238b3%40googlegroups.com.


Re: About Jenkins slowness for version 2.138 in multi branch pipeline project

2020-01-20 Thread Mahesh Wabale
Thanks Marc , 

We will check if it helps , Currently we have "maximum durability" settings 
configured now , we are planning to make it to "performance-optimized"  .  
We have observed couple of time disc IO is very high sometimes . 

On Monday, January 20, 2020 at 5:54:38 AM UTC+5:30, Mark Waite wrote:
>
> I'm not aware of an open bug in Jenkins related to being slow over NFS, 
> though Jenkins is quite disc intensive and runs best with local disc drives.
>
> You might refer to the following articles for more information:
>
>- Jenkins pipeline durability settings documentation 
>
> 
>  
>("Will Higher-Performance Durability Settings Help Me? Yes, if your 
> Jenkins 
>instance uses NFS, magnetic storage, runs many Pipelines at once, or shows 
>high iowait.")
>- CloudBees NFS guide 
> 
> (multiple 
>pages of tuning recommendations)
>
>
>
> On Fri, Jan 17, 2020 at 5:42 AM Mahesh Wabale  > wrote:
>
>> Hi Team , 
>>
>> We are using observing Jenkins slowness issues for jenkins version 2.138 
>> in multi branch pipeline project . 
>> We have also used NFS 4.1 . 
>>
>> After Jenkins restart it works for few days but at some stage it stuck 
>> and becomes unresponsive . As per observation only restart will solve this 
>> issue for next few days . We require frequent restart due to this issue . 
>> Have anyone observed similar issues , or  this is open bug in Jenkins ?
>>
>>
>> -- 
>> 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 jenkins...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/319f90ff-5410-4495-bb46-51d61745b3e8%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Thanks!
> Mark Waite
>

-- 
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 
https://groups.google.com/d/msgid/jenkinsci-users/8a711ba9-4433-4e62-9170-50e7f5c82bdd%40googlegroups.com.