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.
