Re: Windows 7 Agents (slaves) via SSH

2019-07-29 Thread Steve K
Thanks again Mark.

So, what does the master think the launch method is for the slave? 

-- 
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/690225b1-271b-45dc-88b0-d15b06c15135%40googlegroups.com.


Re: Windows 7 Agents (slaves) via SSH

2019-07-29 Thread Mark Waite
On Mon, Jul 29, 2019 at 12:26 PM Steve K 
wrote:

> Thanks Mark,
> Web articles, such as this "Installing OpenSSH on Windows 7
> " gave me hope
> of finding a workable solution.
> I had also considered trying to use Cygwin, as described by Kohsuke
> Kawaguci in the Wiki page "SSH slaves and Cygwin
> ", but
> that seemed like too much overhead when several slaves/agents need to be
> configured.
>
> Launching an agent with a batch file seems like a good alternative. Have
> you been able to auto-start such a script (for example, to run at boot
> time)?
>

I have a batch file on the Desktop of the computer with a link to that
Desktop batch file in the Startup folder for the specific user.  The
specific user is configured to auto-login.  Thus, those machines run the
agent automatically when they boot.

Running from a running Desktop account also assures that desktop access is
available (for things like Selenium tests).


> Thanks again.
>
> --
> 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/d7a41896-cfd6-4dc6-8007-649097fa0304%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/CAO49JtHnCTnEbJ4eiJxkyNGaVRY%2BLvZCbVrcFyCDSk%2B3%2BZFj%3DQ%40mail.gmail.com.


Re: Windows 7 Agents (slaves) via SSH

2019-07-29 Thread Steve K
Thanks Mark,
Web articles, such as this "Installing OpenSSH on Windows 7 
" gave me hope of 
finding a workable solution.
I had also considered trying to use Cygwin, as described by Kohsuke 
Kawaguci in the Wiki page "SSH slaves and Cygwin 
", but that 
seemed like too much overhead when several slaves/agents need to be 
configured.

Launching an agent with a batch file seems like a good alternative. Have 
you been able to auto-start such a script (for example, to run at boot 
time)?

Thanks again.

-- 
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/d7a41896-cfd6-4dc6-8007-649097fa0304%40googlegroups.com.


Re: Converting to pipeline questions

2019-07-29 Thread jeremy mordkoff
My personal advice is to pick declarative or scripted pipelines and stick 
to that everywhere. Switching back and forth always leads to mistakes.  And 
so keeping the Jenkinsfiles in source control is huge plus and I would 
never go back to putting any logic inside my jenkins job config. Why are 
you averse to the repository fetch? 

I found that there were just enough things that I could not do in 
declarative so I needed to use scripted. 

Finally, I try to keep the nitty gritty details of my build process in 
scripts in source control. For instance, I don't call make from Jenkins. I 
call a bash script which calls make (among other things). I found that the 
serialization restrictions in Jenkins make writing serious scripts for it 
pretty difficult and frustrating since what looks like a perfectly valid 
script will throw unintelligible errors when run inside Jenkins. 

I believe serialization is also important for executing code inside of 
containers or on other nodes, but I do not know that for a fact. 



On Monday, July 29, 2019 at 11:40:56 AM UTC-4, Louis Elston wrote:
>
> 07/17/19 – wrote this…
>
> We are currently using Windows \ Jenkins 2.107.1 (no pipeline), and I am 
> researching going to pipeline. We have a nightly build job, that fetches 
> from repositories, and submits and waits on other jobs. I see 9 jobs 
> running on the same Master node (we only have a master), at the same time. 
> I am not clear on if we should have one Jenkinsfile or multiple 
> Jenkinsfiles. It will not be a multibranch pipeline, as we do not create 
> test branches and then merge back to a master. In the repository we have 
> product1.0 branch, product2.0 branch etc., and build only one branch (the 
> latest one). While I do like the Blue Ocean editor, it is only for 
> MultiBranch pipelines.
>
> Looking for directions and\or examples on how to convert existing Jenkins 
> non-pipeline systems, to pipeline.  I did find this…
> https://wiki.jenkins.io/display/JENKINS/Convert+To+Pipeline+Plugin. It 
> does help a little in that it gives you some converted steps, but cannot 
> convert all the steps, and will give comments in the pipeline script 
> "//Unable to convert a build step referring to...please verify and convert 
> manually if required." There is an option "Recursively convert downstream 
> jobs if any" and if you select that, it appears to add all the downstream 
> jobs to the same pipeline script, and really confuses the job parameters. 
> There is also an option to "Commit JenkinsFile" (if doing declarative). I 
> will play with this some more, but it is not the be all and end all of 
> converting to pipeline, and I still am not sure of whether I should be have 
> one or more scripts.
>
> Added 07/26/19 - Let’s see if I have my research to date correct…
>
> A Declarative pipeline (Pipeline Script from SCM), is stored in a 
> Jenkinsfile in the repository. Every time that this Jenkins job is 
> executed, a fetch from the repository is done (to get the latest version of 
> the Jenkinsfile).
>
> A Pipeline script is stored as part of the config.xml file in the 
> Jenkins\Jobs folder (it is not stored in the repository, or in a separate 
> Jenkinsfile in the jobs folder). There is a fetch from the repository only 
> if you put it in (you do not need to do a repository fetch to get the 
> Pipeline script).
>
> Besides our nightly product build, we also have other jobs. I could create 
> a separate Declarative Jenkinsfile for each of them (JenkinsfileA, 
> JenkinsfileB, etc.) for each of the other jobs and store then in the 
> repository also (in the same branch as the main Jenkinsfile), but that 
> would mean that every one of those additional jobs, to get the particular 
> Jenkinsfile for that job, would also need to do a repository fetch 
> (basically fetching\cloning the repository branch for each job, and have 
> multiple versions of the repository branch unnecessarily downloaded to the 
> workspace of each job).
>
> That does not make sense to me (unless my understanding of things to date 
> is incorrect). Because the main product build does require a fetch every 
> time it is run (to get any possible developer check-ins), I do not see a 
> problem doing Declarative Jenkinsfile for that job. For the other jobs (if 
> we do not leave then for the time being in the classic (non-pipeline) 
> format)), they will be Pipeline scripts.
>
> Is there any way of (or plans for), being able to do Declarative pipeline 
> without having to store in the repository and doing a fetch every time 
> (lessening the need to become a Groovy developer)? The Blue Ocean script 
> editor appears to be an easier tool to use to create pipeline scripts, but 
> it is only for MultiBranch pipelines (which we don’t do).
>
> Serialization (restarting a job), is that only for when a node goes down, 
> or can you restart a pipeline job (Declarative or Scripted), from any point 
> if it fails?
>
> I see that there are places to look to see 

Re: Jenkins Agents getting disconnected

2019-07-29 Thread Ivan Fernandez Calvo
check the Cloudbees links, I've helped to write those KB when I was on 
CloudBees :), I'm pretty sure that the NFS is your pain and the root cause 
of all your problems if you can rid of it better.

El lunes, 29 de julio de 2019, 18:03:59 (UTC+2), slide escribió:
>
> CloudBees (not my employer) has some resources on using NFS (generally the 
> recommendation is to NOT use NFS for JENKINS_HOME). 
>
>
> https://support.cloudbees.com/hc/en-us/articles/115000486312-CJP-Performance-Best-Practices-for-Linux#nfs
>  
> and
> https://support.cloudbees.com/hc/en-us/articles/217479948-NFS-Guide 
>
> On Mon, Jul 29, 2019 at 8:51 AM Sverre Moe  > wrote:
>
>> Yes, we are using NFS for JENKINS_HOME.
>>
>> mandag 29. juli 2019 15.41.00 UTC+2 skrev Ivan Fernandez Calvo følgende:
>>>
>>> you have 83 threads in state:IN_NATIVE, probably stuck in IO 
>>> operations, those 83 threads are blocking the other 382 threads, if you use 
>>> an NFS or similar device for you Jenkins HOME this is probably your 
>>> bottleneck, if not check the IO stats on the OS to see where you have the 
>>> bottleneck.
>>>
>>> El lunes, 29 de julio de 2019, 11:20:50 (UTC+2), Sverre Moe escribió:

 I was unable to determine something from the stack output
 Here is the result: 
 https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjkvLS1qc3RhY2sudHh0LS05LTE2LTI3

 torsdag 18. juli 2019 11.28.06 UTC+2 skrev Sverre Moe følgende:
>
> There is no such reference in my jstack output.
> The output says no deadlock detected.
> I will try that site for analyzing the jstack.
>
> Even a normal running Jenkins has many BLOCKED threads. If that is 
> normal I don't know.
>
> We have a test Jenkins instance running on Java 11. That one does not 
> have any BLOCKED threads.
> Our production Jenkins is running Java 8u181.
>
> torsdag 18. juli 2019 11.04.16 UTC+2 skrev Ivan Fernandez Calvo 
> følgende:
>>
>> In that dump I can not see which thread is blocking the others, the 
>> jstack output has a reference on each thread that said what thread is 
>> the 
>> blocker on each thread (- locked <0x> a java.lang.Object), 
>> you can try to analyze those thread dump with 
>> https://fastthread.io/index.jsp or other online tools to see if you 
>> see something relevant, it looks like there is a deadlock.
>>
>> https://dzone.com/articles/how-to-read-a-thread-dump
>>
> -- 
>> 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/cc2d0bdb-b15f-4bec-a0a3-0562ea8c7df7%40googlegroups.com
>>  
>> 
>> .
>>
>
>
> -- 
> Website: http://earl-of-code.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/9976bba2-c9da-4975-b00a-138786d7f7d1%40googlegroups.com.


Re: Jenkins Agents getting disconnected

2019-07-29 Thread Slide
CloudBees (not my employer) has some resources on using NFS (generally the
recommendation is to NOT use NFS for JENKINS_HOME).

https://support.cloudbees.com/hc/en-us/articles/115000486312-CJP-Performance-Best-Practices-for-Linux#nfs

and
https://support.cloudbees.com/hc/en-us/articles/217479948-NFS-Guide

On Mon, Jul 29, 2019 at 8:51 AM Sverre Moe  wrote:

> Yes, we are using NFS for JENKINS_HOME.
>
> mandag 29. juli 2019 15.41.00 UTC+2 skrev Ivan Fernandez Calvo følgende:
>>
>> you have 83 threads in state:IN_NATIVE, probably stuck in IO operations,
>> those 83 threads are blocking the other 382 threads, if you use an NFS or
>> similar device for you Jenkins HOME this is probably your bottleneck, if
>> not check the IO stats on the OS to see where you have the bottleneck.
>>
>> El lunes, 29 de julio de 2019, 11:20:50 (UTC+2), Sverre Moe escribió:
>>>
>>> I was unable to determine something from the stack output
>>> Here is the result:
>>> https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjkvLS1qc3RhY2sudHh0LS05LTE2LTI3
>>>
>>> torsdag 18. juli 2019 11.28.06 UTC+2 skrev Sverre Moe følgende:

 There is no such reference in my jstack output.
 The output says no deadlock detected.
 I will try that site for analyzing the jstack.

 Even a normal running Jenkins has many BLOCKED threads. If that is
 normal I don't know.

 We have a test Jenkins instance running on Java 11. That one does not
 have any BLOCKED threads.
 Our production Jenkins is running Java 8u181.

 torsdag 18. juli 2019 11.04.16 UTC+2 skrev Ivan Fernandez Calvo
 følgende:
>
> In that dump I can not see which thread is blocking the others, the
> jstack output has a reference on each thread that said what thread is the
> blocker on each thread (- locked <0x> a java.lang.Object),
> you can try to analyze those thread dump with
> https://fastthread.io/index.jsp or other online tools to see if you
> see something relevant, it looks like there is a deadlock.
>
> https://dzone.com/articles/how-to-read-a-thread-dump
>
 --
> 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/cc2d0bdb-b15f-4bec-a0a3-0562ea8c7df7%40googlegroups.com
> 
> .
>


-- 
Website: http://earl-of-code.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/CAPiUgVcY3HW1qCfGrMO2gCm9e-%2BvxzQJEk1E61xc1DDGk7ngQQ%40mail.gmail.com.


Re: Jenkins Agents getting disconnected

2019-07-29 Thread Sverre Moe
Yes, we are using NFS for JENKINS_HOME.

mandag 29. juli 2019 15.41.00 UTC+2 skrev Ivan Fernandez Calvo følgende:
>
> you have 83 threads in state:IN_NATIVE, probably stuck in IO operations, 
> those 83 threads are blocking the other 382 threads, if you use an NFS or 
> similar device for you Jenkins HOME this is probably your bottleneck, if 
> not check the IO stats on the OS to see where you have the bottleneck.
>
> El lunes, 29 de julio de 2019, 11:20:50 (UTC+2), Sverre Moe escribió:
>>
>> I was unable to determine something from the stack output
>> Here is the result: 
>> https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjkvLS1qc3RhY2sudHh0LS05LTE2LTI3
>>
>> torsdag 18. juli 2019 11.28.06 UTC+2 skrev Sverre Moe følgende:
>>>
>>> There is no such reference in my jstack output.
>>> The output says no deadlock detected.
>>> I will try that site for analyzing the jstack.
>>>
>>> Even a normal running Jenkins has many BLOCKED threads. If that is 
>>> normal I don't know.
>>>
>>> We have a test Jenkins instance running on Java 11. That one does not 
>>> have any BLOCKED threads.
>>> Our production Jenkins is running Java 8u181.
>>>
>>> torsdag 18. juli 2019 11.04.16 UTC+2 skrev Ivan Fernandez Calvo følgende:

 In that dump I can not see which thread is blocking the others, the 
 jstack output has a reference on each thread that said what thread is the 
 blocker on each thread (- locked <0x> a java.lang.Object), you 
 can try to analyze those thread dump with 
 https://fastthread.io/index.jsp or other online tools to see if you 
 see something relevant, it looks like there is a deadlock.

 https://dzone.com/articles/how-to-read-a-thread-dump

>>>

-- 
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/cc2d0bdb-b15f-4bec-a0a3-0562ea8c7df7%40googlegroups.com.


Converting to pipeline questions

2019-07-29 Thread Louis Elston


07/17/19 – wrote this…

We are currently using Windows \ Jenkins 2.107.1 (no pipeline), and I am 
researching going to pipeline. We have a nightly build job, that fetches 
from repositories, and submits and waits on other jobs. I see 9 jobs 
running on the same Master node (we only have a master), at the same time. 
I am not clear on if we should have one Jenkinsfile or multiple 
Jenkinsfiles. It will not be a multibranch pipeline, as we do not create 
test branches and then merge back to a master. In the repository we have 
product1.0 branch, product2.0 branch etc., and build only one branch (the 
latest one). While I do like the Blue Ocean editor, it is only for 
MultiBranch pipelines.

Looking for directions and\or examples on how to convert existing Jenkins 
non-pipeline systems, to pipeline.  I did find this…
https://wiki.jenkins.io/display/JENKINS/Convert+To+Pipeline+Plugin. It does 
help a little in that it gives you some converted steps, but cannot convert 
all the steps, and will give comments in the pipeline script "//Unable to 
convert a build step referring to...please verify and convert manually if 
required." There is an option "Recursively convert downstream jobs if any" 
and if you select that, it appears to add all the downstream jobs to the 
same pipeline script, and really confuses the job parameters. There is also 
an option to "Commit JenkinsFile" (if doing declarative). I will play with 
this some more, but it is not the be all and end all of converting to 
pipeline, and I still am not sure of whether I should be have one or more 
scripts.

Added 07/26/19 - Let’s see if I have my research to date correct…

A Declarative pipeline (Pipeline Script from SCM), is stored in a 
Jenkinsfile in the repository. Every time that this Jenkins job is 
executed, a fetch from the repository is done (to get the latest version of 
the Jenkinsfile).

A Pipeline script is stored as part of the config.xml file in the 
Jenkins\Jobs folder (it is not stored in the repository, or in a separate 
Jenkinsfile in the jobs folder). There is a fetch from the repository only 
if you put it in (you do not need to do a repository fetch to get the 
Pipeline script).

Besides our nightly product build, we also have other jobs. I could create 
a separate Declarative Jenkinsfile for each of them (JenkinsfileA, 
JenkinsfileB, etc.) for each of the other jobs and store then in the 
repository also (in the same branch as the main Jenkinsfile), but that 
would mean that every one of those additional jobs, to get the particular 
Jenkinsfile for that job, would also need to do a repository fetch 
(basically fetching\cloning the repository branch for each job, and have 
multiple versions of the repository branch unnecessarily downloaded to the 
workspace of each job).

That does not make sense to me (unless my understanding of things to date 
is incorrect). Because the main product build does require a fetch every 
time it is run (to get any possible developer check-ins), I do not see a 
problem doing Declarative Jenkinsfile for that job. For the other jobs (if 
we do not leave then for the time being in the classic (non-pipeline) 
format)), they will be Pipeline scripts.

Is there any way of (or plans for), being able to do Declarative pipeline 
without having to store in the repository and doing a fetch every time 
(lessening the need to become a Groovy developer)? The Blue Ocean script 
editor appears to be an easier tool to use to create pipeline scripts, but 
it is only for MultiBranch pipelines (which we don’t do).

Serialization (restarting a job), is that only for when a node goes down, 
or can you restart a pipeline job (Declarative or Scripted), from any point 
if it fails?

I see that there are places to look to see what Jenkins plugin’s have been 
ported to pipeline, but is there anything that can be run to look at the 
classic jobs that you have, to determine up front which jobs are going to 
have problems being converted to pipeline (non supported plugins)?

-- 
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/0df1dd25-df1e-4649-bc0e-d0c1b394062d%40googlegroups.com.


Re: Jenkins Agents getting disconnected

2019-07-29 Thread Ivan Fernandez Calvo
you have 83 threads in state:IN_NATIVE, probably stuck in IO operations, 
those 83 threads are blocking the other 382 threads, if you use an NFS or 
similar device for you Jenkins HOME this is probably your bottleneck, if 
not check the IO stats on the OS to see where you have the bottleneck.

El lunes, 29 de julio de 2019, 11:20:50 (UTC+2), Sverre Moe escribió:
>
> I was unable to determine something from the stack output
> Here is the result: 
> https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjkvLS1qc3RhY2sudHh0LS05LTE2LTI3
>
> torsdag 18. juli 2019 11.28.06 UTC+2 skrev Sverre Moe følgende:
>>
>> There is no such reference in my jstack output.
>> The output says no deadlock detected.
>> I will try that site for analyzing the jstack.
>>
>> Even a normal running Jenkins has many BLOCKED threads. If that is normal 
>> I don't know.
>>
>> We have a test Jenkins instance running on Java 11. That one does not 
>> have any BLOCKED threads.
>> Our production Jenkins is running Java 8u181.
>>
>> torsdag 18. juli 2019 11.04.16 UTC+2 skrev Ivan Fernandez Calvo følgende:
>>>
>>> In that dump I can not see which thread is blocking the others, the 
>>> jstack output has a reference on each thread that said what thread is the 
>>> blocker on each thread (- locked <0x> a java.lang.Object), you 
>>> can try to analyze those thread dump with 
>>> https://fastthread.io/index.jsp or other online tools to see if you see 
>>> something relevant, it looks like there is a deadlock.
>>>
>>> https://dzone.com/articles/how-to-read-a-thread-dump
>>>
>>

-- 
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/1d477738-f36f-4464-82ea-6411884c6a31%40googlegroups.com.


Re: Create new item - Item name error 'Only alphanumerical characters allowed'

2019-07-29 Thread Slide
Can you give a list of plugins and their versions that you have installed?
Did you restart Jenkins after the upgrade of plugins?

On Mon, Jul 29, 2019, 05:58 Laura López Senderos 
wrote:

> Our current Jenkins version is 2.176.2. We're not sure when it has started
> happening, because we've made some updates on plugins and Jenkins instance
> since the last job creation.
>
> It's really strange because we've been able to create jobs with spaces,
> hyphens, underscores, lowercase, uppercase and without problems.
>
> But now, we only type a letter, any letter, and the error message is
> shown. We've tried to follow the javascript code in browser developer
> console when typping a letter, but finally there's an ajax request and we
> can't see anything more.
>
> I'm thinking on installing Jenkins CLI to try creating a Job from commands
> and if the error persists. This isn't the solution I would like to use but
> if it works we'll have to use it meanwhile.
>
> Thanks.
>
>
> El viernes, 26 de julio de 2019, 17:01:05 (UTC+2), Mark Waite escribió:
>>
>> I've not seen any report of that issue from anyone other than you.
>>
>> When I asked if a folder containing the job included an unexpected
>> character, I was thinking of a Jenkins folder more than a directory on the
>> file system.  The directory on the file system which represents that
>> Jenkins folder would be inside a subdirectory or series of subdirectories
>> of /var/lib/jenkins/jobs/.
>>
>> If you don't use Jenkins folders to organize your jobs, then that is not
>> the issue.
>>
>> What version of Jenkins are you running that is broken?  What version of
>> Jenkins were you running when it was working?
>>
>>
>>
>> On Fri, Jul 26, 2019 at 7:05 AM Laura López Senderos 
>> wrote:
>>
>>> Hi Mark,
>>>
>>> The folder where every jobs are created is '/var/lib/jenkins/jobs'. This
>>> is the default folder and we've been able to create items on it since now.
>>>
>>> Maybe some plugin update, or the jenkins instance update has broken
>>> something... We can't rename the jobs neither :/ It's like the regex that
>>> checks the name of the job is not working well.
>>>
>>> Is there anyone having the same issue?
>>>
>>> Thanks.
>>>
>>>
>>> El viernes, 26 de julio de 2019, 14:43:42 (UTC+2), Mark Waite escribió:

 Possibly the folder where you're creating those items has a character
 in its name that is outside the allowed set of characters?

 On Fri, Jul 26, 2019 at 5:55 AM Laura López Senderos <
 laurap...@gmail.com> wrote:

> Hi everyone,
>
> Since the lastest releases of Jenkins we're having a problem when
> creating new items. We always get the 'Only alphanumerical characters
> allowed' error when trying to create a new item.
>
> We've tried from multiple browsers, changing our system language and
> the error persists. We don't know why this is happening suddenly and we
> can't find out a solutions :(
>
> We've 14 projects created without problems, but for a month or so
> we're unable to create new ones.
>
> Any help will be appreciated.
>
> Thanks in advance.
>
> --
> 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/7920a84b-3706-447d-8b71-d3d54036c6e0%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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/4649dca6-d02d-495c-bf96-45a0120bdaf0%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/47d910c8-ed0d-483d-aae3-90d344eab4f6%40googlegroups.com
> 
> .
>

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

Re: Create new item - Item name error 'Only alphanumerical characters allowed'

2019-07-29 Thread Laura López Senderos
Our current Jenkins version is 2.176.2. We're not sure when it has started 
happening, because we've made some updates on plugins and Jenkins instance 
since the last job creation.

It's really strange because we've been able to create jobs with spaces, 
hyphens, underscores, lowercase, uppercase and without problems.

But now, we only type a letter, any letter, and the error message is shown. 
We've tried to follow the javascript code in browser developer console when 
typping a letter, but finally there's an ajax request and we can't see 
anything more.

I'm thinking on installing Jenkins CLI to try creating a Job from commands 
and if the error persists. This isn't the solution I would like to use but 
if it works we'll have to use it meanwhile.

Thanks.


El viernes, 26 de julio de 2019, 17:01:05 (UTC+2), Mark Waite escribió:
>
> I've not seen any report of that issue from anyone other than you.
>
> When I asked if a folder containing the job included an unexpected 
> character, I was thinking of a Jenkins folder more than a directory on the 
> file system.  The directory on the file system which represents that 
> Jenkins folder would be inside a subdirectory or series of subdirectories 
> of /var/lib/jenkins/jobs/.
>
> If you don't use Jenkins folders to organize your jobs, then that is not 
> the issue.
>
> What version of Jenkins are you running that is broken?  What version of 
> Jenkins were you running when it was working?  
>
>
>
> On Fri, Jul 26, 2019 at 7:05 AM Laura López Senderos  > wrote:
>
>> Hi Mark,
>>
>> The folder where every jobs are created is '/var/lib/jenkins/jobs'. This 
>> is the default folder and we've been able to create items on it since now.
>>
>> Maybe some plugin update, or the jenkins instance update has broken 
>> something... We can't rename the jobs neither :/ It's like the regex that 
>> checks the name of the job is not working well.
>>
>> Is there anyone having the same issue?
>>
>> Thanks.
>>
>>
>> El viernes, 26 de julio de 2019, 14:43:42 (UTC+2), Mark Waite escribió:
>>>
>>> Possibly the folder where you're creating those items has a character in 
>>> its name that is outside the allowed set of characters?
>>>
>>> On Fri, Jul 26, 2019 at 5:55 AM Laura López Senderos <
>>> laurap...@gmail.com> wrote:
>>>
 Hi everyone,

 Since the lastest releases of Jenkins we're having a problem when 
 creating new items. We always get the 'Only alphanumerical characters 
 allowed' error when trying to create a new item.

 We've tried from multiple browsers, changing our system language and 
 the error persists. We don't know why this is happening suddenly and we 
 can't find out a solutions :(

 We've 14 projects created without problems, but for a month or so we're 
 unable to create new ones.

 Any help will be appreciated.

 Thanks in advance.

 -- 
 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/7920a84b-3706-447d-8b71-d3d54036c6e0%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 jenkins...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/4649dca6-d02d-495c-bf96-45a0120bdaf0%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/47d910c8-ed0d-483d-aae3-90d344eab4f6%40googlegroups.com.


Increasingly slow build and test run times over time

2019-07-29 Thread ABostonGal ABostonGal
 note that if I reboot all the automation machines (Unix master, Windows 
slave, Windows agent on which automation tests run  compiles and text 
executions are very fast. I have six to twelve Jenkins jobs running every 
night. 

However, over a period of a few days, performance will bog down and slow up 
to the point that the longest running job (optimally at 8 hours) will take 
up to 20 hours or so!

So, I reboot again and things speed up for a while and then bog down.

Last Friday, I noted the hang ups again and this time I noticed on the 
Jenkins dashboard that it is during compiles there is a hideous slowdown. I 
don't know this is always true and I will look at prior builds today to see 
if there is a pattern.

Before running the tests, there are jobs that compile the code and clean 
out "gunk" from output directories. 

Any general guidance as to debugging this? I lack the experience and 
knowledge still to be able to organize and target my debugging efforts as 
well as I should. 

I don't think I should have to depend on random reboots to maximize Jenkins 
performance.

Oh, here's the other big problem and this may a very large part of the 
problem. I 'm working in a changing environment where I have been limited 
in what I can do to update software as I should because of upper level 
decisions. I should be running the latest stable build of Jenkins and all 
software but I am not. That should be my first effort in solving the 
performance issue, right? I am just going to try to update all software 
myself at this point. 


Thanks for listening.


-- 
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/1ded4fac-ced5-410a-8f9b-a88a079e5aed%40googlegroups.com.


Re: Memory issues with Jenkins

2019-07-29 Thread Sverre Moe
I have analyzed the GC log

https://www.gceasy.io/my-gc-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjgvLS1nYy0yMDE5LTA3LTI2XzE3LTMxLTIyLmxvZy4wLmN1cnJlbnQtLTE1LTI0LTQy=WEB

This may be related to another issue I am having when build agents are 
getting disconnected.
https://groups.google.com/forum/#!topic/jenkinsci-users/UDyaH-kfqqA

I also have an jstack output analyzed:
https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjkvLS1qc3RhY2sudHh0LS05LTE2LTI3

søndag 14. juli 2019 13.48.57 UTC+2 skrev Sverre Moe følgende:
>
> I checked out that link
>
> Tried the ulimit settings
>
> https://support.cloudbees.com/hc/en-us/articles/222446987-Prepare-Jenkins-for-Support#bulimitsettingsjustforlinuxos
>
> Will try the additional JVM flags suggested in
>
> https://support.cloudbees.com/hc/en-us/articles/222446987-Prepare-Jenkins-for-Support#ajavaparameters
>
> søndag 14. juli 2019 13.29.22 UTC+2 skrev Sverre Moe følgende:
>>
>> jenkins@meoscorebs12:~> ulimit -a 
>> core file size  (blocks, -c) unlimited 
>> data seg size   (kbytes, -d) unlimited 
>> scheduling priority (-e) 0 
>> file size   (blocks, -f) unlimited 
>> pending signals (-i) 80229 
>> max locked memory   (kbytes, -l) 64 
>> max memory size (kbytes, -m) unlimited 
>> open files  (-n) 1024 
>> pipe size(512 bytes, -p) 8 
>> POSIX message queues (bytes, -q) 819200 
>> real-time priority  (-r) 0 
>> stack size  (kbytes, -s) 8192 
>> cpu time   (seconds, -t) unlimited 
>> max user processes  (-u) 80229 
>> virtual memory  (kbytes, -v) unlimited 
>> file locks  (-x) unlimited
>>
>>
>> I have check the number of processes, with "ps aux", but not the number 
>> of threads.
>> Right now, (Jenkins was restarted 2 day ago and few builds have run), 
>> there are 264 threads for Jenkins currently.
>> Is there any way I can find out what each thread is for?
>>
>> lørdag 13. juli 2019 13.02.15 UTC+2 skrev Ivan Fernandez Calvo følgende:
>>>
>>> Hi,
>>>
>>> When the issue happens, Did you check the number of threads that Jenkins 
>>> has open? How many file descriptors can your process open (run ulimit 
>>> -a with the user jenkins)? here you have a good KB about memory and 
>>> user limit on Jenkins Prepare Jenkins for Support 
>>> 
>>>
>>

-- 
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/1465add4-191b-46c3-bd08-31816f0cc82b%40googlegroups.com.


Re: Jenkins Agents getting disconnected

2019-07-29 Thread Sverre Moe
I was unable to determine something from the stack output
Here is the 
result: 
https://fastthread.io/my-thread-report.jsp?p=c2hhcmVkLzIwMTkvMDcvMjkvLS1qc3RhY2sudHh0LS05LTE2LTI3

torsdag 18. juli 2019 11.28.06 UTC+2 skrev Sverre Moe følgende:
>
> There is no such reference in my jstack output.
> The output says no deadlock detected.
> I will try that site for analyzing the jstack.
>
> Even a normal running Jenkins has many BLOCKED threads. If that is normal 
> I don't know.
>
> We have a test Jenkins instance running on Java 11. That one does not have 
> any BLOCKED threads.
> Our production Jenkins is running Java 8u181.
>
> torsdag 18. juli 2019 11.04.16 UTC+2 skrev Ivan Fernandez Calvo følgende:
>>
>> In that dump I can not see which thread is blocking the others, the 
>> jstack output has a reference on each thread that said what thread is the 
>> blocker on each thread (- locked <0x> a java.lang.Object), you 
>> can try to analyze those thread dump with https://fastthread.io/index.jsp or 
>> other online tools to see if you see something relevant, it looks like 
>> there is a deadlock.
>>
>> https://dzone.com/articles/how-to-read-a-thread-dump
>>
>

-- 
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/9ae17af0-1ed6-4365-8050-aef2b025d6cf%40googlegroups.com.