Re: Jenkins: user is missing the Overall/Read permission - Issue
Just to clarify, I have checked that the Overall/Read Permission is set. We are using Matrix-based security with Jenkins version 2.138.2. Please see attached screenshots. On Saturday, 3 March 2018 14:07:07 UTC, Poovaraj Thangamariappan wrote: > > Hello, > > I have created *manual* user in Manger User and I have configured in > Matrix-based > security. It is showing Manual user is missing the Overall/Read > permission'while login into jenkins. > > Pleaes find thebelow screenshot and config.xml file. Please help me to fix > this issue. > > > > > > > > > > > > Regards, > Poovaraj > > > -- 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/1bad5fe0-fe38-4280-a8d4-c126599a9364%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins: user is missing the Overall/Read permission - Issue
I get this issue too. Users who have previously managed to log in (including myself) find themselves effectively locked out and I have to create a new login to work round the issue. I just tried to follow Ram's suggestion but that did not help. On Saturday, 3 March 2018 14:07:07 UTC, Poovaraj Thangamariappan wrote: > > Hello, > > I have created *manual* user in Manger User and I have configured in > Matrix-based > security. It is showing Manual user is missing the Overall/Read > permission'while login into jenkins. > > Pleaes find thebelow screenshot and config.xml file. Please help me to fix > this issue. > > > > > > > > > > > > Regards, > Poovaraj > > > -- 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/3564e1bd-d62f-4c84-9988-19948640b722%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: threadExecutorNumber must be at least 1 error with JIRA plugin v3.04 and Jenkins v2.138.2
Apologies, plugin version should read JIRA plugin v3.0.4 On Friday, 2 November 2018 16:30:49 UTC, David Brown wrote: > > Hello. I'm facing an issue with the JIRA plugin. Associated cases are > correctly getting updated but the JIRA Issue links in build Changelog are > not rendering correctly as hyplerlinks. As a first step in trying to debug > this I have tried "Validate Settings" in the JIRA section of Manage Jenkins > > Configure System but this fails with an error message > "threadExecutorNumber must be at least 1". It seems there is a new > parameter "Thread Executor Size" (defaults to 10, I have tried a few other > values but these make no difference to my error message) but I can see no > option to specify the Thread Executor Number. Can anyone help please? > 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/69f7916d-66b6-42b8-9d54-ea91b7abff38%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
threadExecutorNumber must be at least 1 error with JIRA plugin v3.04 and Jenkins v2.138.2
Hello. I'm facing an issue with the JIRA plugin. Associated cases are correctly getting updated but the JIRA Issue links in build Changelog are not rendering correctly as hyplerlinks. As a first step in trying to debug this I have tried "Validate Settings" in the JIRA section of Manage Jenkins > Configure System but this fails with an error message "threadExecutorNumber must be at least 1". It seems there is a new parameter "Thread Executor Size" (defaults to 10, I have tried a few other values but these make no difference to my error message) but I can see no option to specify the Thread Executor Number. Can anyone help please? 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/26d39012-0fde-4420-bcca-fce48fcae730%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Build change history not shown.
I seem to have fixed my own issue here. I discovered that the Mercurial Installation had not been declared in the System Config. In the newer version of Jenkins this has been moved into a new section: "Global Tool Configuration". Once I set this up and ran another build I found that the changelog mechanism appears to start working again. On Wednesday, 8 March 2017 15:41:35 UTC, David Brown wrote: > > I'm trying to pilot Jenkins 2.32.2 before upgrading our production system > which is running v 1.651.3. > > Most of our jobs pull in from multiple Mercurial repositories, thus we are > heavily reliant upon the Multiple SCMs Plugin. > > I'm facing an issue in Jenkins 2.32.2 in that the build change history is > not shown, it just displays "No changes". This is with version 0.6 of the > Multiple SCMs Plugin. > > I have seen the banner on the Multple SCMs Plugin page which advises that > this plugin has been deprecated and "Users should migrate to Pipeline > Plugin". Having taken a quick look at the overview page and "How do I start > with Pipeline" topic, I am concerned that this is not something that can be > achieved without spending some considerable time learning (Pipeline Syntax, > stages, steps, agents, etc., etc.), so I would prefer to keep using the > Multiple SCMs plugin if at all possible. > > Has anyone else in the community experienced this issue or can anyone > suggest a solution please? > -- 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/040f420a-59ba-4d1e-bbd5-8ec23b692ca1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Build change history not shown.
I'm trying to pilot Jenkins 2.32.2 before upgrading our production system which is running v 1.651.3. Most of our jobs pull in from multiple Mercurial repositories, thus we are heavily reliant upon the Multiple SCMs Plugin. I'm facing an issue in Jenkins 2.32.2 in that the build change history is not shown, it just displays "No changes". This is with version 0.6 of the Multiple SCMs Plugin. I have seen the banner on the Multple SCMs Plugin page which advises that this plugin has been deprecated and "Users should migrate to Pipeline Plugin". Having taken a quick look at the overview page and "How do I start with Pipeline" topic, I am concerned that this is not something that can be achieved without spending some considerable time learning (Pipeline Syntax, stages, steps, agents, etc., etc.), so I would prefer to keep using the Multiple SCMs plugin if at all possible. Has anyone else in the community experienced this issue or can anyone suggest a solution please? -- 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/4c1ce683-a8ab-45d6-b6df-18114422fd9e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins crash - ci-game reference
Hi All,
Our Jenkins server crashed this afternoon for the first time in about 6
weeks. This is the first crash we've experienced since installing the
Support Core Plugin, which we installed partly in the hope that it would
assist us in debugging server crash issues. Now we have a number of files
and folders in the Hudson\Support folder and I have no idea where to start
my investigation.
I'm curious about the reference to "ci-game" in the following log whose
contents are copied below.
jenkins.metrics.api.Metrics$HealthChecker.log
Starting health checks at Thu Apr 07 14:23:41 BST 2016
Health check results at Thu Apr 07 14:23:41 BST 2016:
* disk-space: Result{isHealthy=true}
* plugins: Result{isHealthy=false, message=There are 1 failed plugins:
ci-game}
* temporary-space: Result{isHealthy=true}
* thread-deadlock: Result{isHealthy=true}
I am aware of the "Continuous Integration Game" plugin but to my knowledge
this has never been installed on our Jenkins instance.
Is the above log file trying to tell me that I need to install this plugin?
--
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/aa4999a4-2fac-401f-a2fa-e1bc5330a4f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: How to get Jobs Start/stop timestamp information in the main log UI of Jenkins
Are you aware of the Timestamper plugin (https://wiki.jenkins-ci.org/display/JENKINS/Timestamper)? We implemented this to see where the pinch points are in some of our longer running jobs and find it very useful. On Thursday, 13 August 2015 22:41:54 UTC+1, Frederic Meyrou wrote: *Dear mates,* *I maintain a huge Jenkins Master server with more than 8000 jobs and 450 Slaves. * *One of this Jobs it giving a hard time to the Master and consume all RAM available in JVM until GC fail, and I need to restart the server... * *Because the number of Jobs, I can't find the faulty one, so I need to add either a logger or anything that would centralize a timestamp like : * *Job Name #nnn started at HH:MM:SS. * *And the same at the end of Job eventually with status.* *Tks for your feedback,* *./Fred* -- 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/415c9349-87fc-4c62-be72-c41eed4f4480%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: How to get Jobs Start/stop timestamp information in the main log UI of Jenkins
Your understanding is correct, this plugin adds timestamp details to the individual job console output logs. So, I guess it doesn't give you exactly what you're after. You want some indication about which of the many jobs that were running when the server crashed was the one which caused the failure. Sorry, I can't help further with that. On Friday, 14 August 2015 10:40:21 UTC+1, Frederic Meyrou wrote: Well yes, but correct me if I'm wrong this plug-in add information to the Job console, no? It's not very clear in the Plugin description... Tks for your answer David! :) ./Fred Le vendredi 14 août 2015 11:36:29 UTC+2, David Brown a écrit : Are you aware of the Timestamper plugin ( https://wiki.jenkins-ci.org/display/JENKINS/Timestamper)? We implemented this to see where the pinch points are in some of our longer running jobs and find it very useful. On Thursday, 13 August 2015 22:41:54 UTC+1, Frederic Meyrou wrote: *Dear mates,* *I maintain a huge Jenkins Master server with more than 8000 jobs and 450 Slaves. * *One of this Jobs it giving a hard time to the Master and consume all RAM available in JVM until GC fail, and I need to restart the server... * *Because the number of Jobs, I can't find the faulty one, so I need to add either a logger or anything that would centralize a timestamp like : * *Job Name #nnn started at HH:MM:SS. * *And the same at the end of Job eventually with status.* *Tks for your feedback,* *./Fred* -- 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/03274840-668f-4872-b843-026f153f8ebf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Use Repository Sharing - advice please
Thank you for the replies. It seems that Use Repository Sharing is not for me! I shall reconsider my approach to my problem and investigate your suggestions. Thank you again. On Tuesday, 28 July 2015 21:51:52 UTC+1, David Brown wrote: Here is my scenario. I have a number of Jenkins projects which build from the same set of Mercurial repositories, compile source code and generate executable files, etc. I’m used to being able to run any combination of these jobs in parallel. Each build runs for at least 3+ hours, but the first third of the build time is spent cloning the repositories and preparing an individual workspace. I have restricted disc space so the jobs are setup to delete their workspace at completion. I am looking to reduce my build times. When I discovered the “Use Repository Sharing” option I was hoping it would enable me to shave the repository cloning time off the start of each build. However I have not been able to find much in the way of documentation or advice on the use of this feature, perhaps I’ve not been looking in the right places or else I’ve not looked hard enough. Here’s what I’ve discovered so far, partly through trial and error: - Need to also assign a specific Directory in the “Use custom workspace” option within Advanced Project Options (a per Project setting) - I set the same shared workspace folder against two jobs - When I attempted to run both jobs in parallel one job failed with message “The process cannot access the file because it is being used by another process.”, suggesting that I have to wait for the build of Project A to finish before I can start a build of Project B Am I naive in expecting this feature to allow jobs to be run in parallel? If I can’t do this then I don’t think this feature will be of any benefit to me. Any tips, guidance or advice would be gratefully received. -- Confidentiality notice: This message may contain confidential information. It is intended only for the person to whom it is addressed. If you are not that person, you should not use this message. We request that you notify us by replying to this message, and then delete all copies including any contained in your reply. Thank you. -- 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/05d15568-1698-4b73-bfe7-d8a735406dd9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
