[JIRA] (JENKINS-49102) Add quote character to role pattern to avoid white spaces
Title: Message Title Alec Matschiner edited a comment on JENKINS-49102 Re: Add quote character to role pattern to avoid white spaces I just hit the following issue with v2.10 of the Role-based Auth plugin. I created a top level folder (e.g. Top-Foo) and I was unable to create a pattern that matched to this top level folder. I tried the following patterns: .*, Top-Foo.* , T.* and nothing was able to recognize that top level folder. I ended up downgrading to version 2.9 and I was able to get my normal method of Top-Foo.* to work. Is this change only looking jobs within folders and not top level folders themselves or is my regex incorrect with the new version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49102) Add quote character to role pattern to avoid white spaces
Title: Message Title Alec Matschiner edited a comment on JENKINS-49102 Re: Add quote character to role pattern to avoid white spaces I just hit the following issue with v2.10 of the Role-based Auth plugin. I created a top level folder (e.g. Top-Foo) and I was unable to create a pattern that matched to this top level folder. I tried the following patterns: " .* " , " Top-Foo.* " , " T.* " and nothing was able to recognize that top level folder. I ended up downgrading to version 2.9 and I was able to get my normal method of " Top-Foo.* " to work. Is this change only looking jobs within folders and not top level folders themselves or is my regex incorrect with the new version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49102) Add quote character to role pattern to avoid white spaces
Title: Message Title Alec Matschiner edited a comment on JENKINS-49102 Re: Add quote character to role pattern to avoid white spaces I just hit the following issue with v2.10 of the Role-based Auth plugin. I created a top level folder (e.g. Top-Foo) and I was unable to create a pattern that matched to this top level folder. I tried the following patterns: ".*", "Top-Foo.*", "T.*" and nothing was able to recognize that top level folder. I ended up downgrading to version 2.9 and I was able to get my normal method of "Top-Foo.*" to work. Is this change only looking jobs within folders and not top level folders themselves or is my regex incorrect with the new version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49102) Add quote character to role pattern to avoid white spaces
Title: Message Title Alec Matschiner commented on JENKINS-49102 Re: Add quote character to role pattern to avoid white spaces I just hit the following issue with v2.10 of the Role-based Auth plugin. I created a top level folder (e.g. Top-Foo) and I was unable to create a pattern that matched to this top level folder. I tried the following patterns: ".", "Top-Foo.", "T." and nothing was able to recognize that top level folder. I ended up downgrading to version 2.9 and I was able to get my normal method of "Top-Foo." to work. Is this change only looking jobs within folders and not top level folders themselves or is my regex incorrect with the new version? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41182) Nodes disappear if "# of executors" is set to 0
Title: Message Title Alec Matschiner commented on JENKINS-41182 Re: Nodes disappear if "# of executors" is set to 0 When I had set the node executor to 0 I observed all of the same issues described in the description here. I then tried to just create a new node with the same name, that didn't work since its still in the file system. As noob alot (nice name) mentioned you can edit the config and change the # of executors. I also noticed deleting that node's directory, restarting Jenkins, and then I'm able to create a new node with that name but then you'll have to reconfigure it. I'd like to suggest maybe adding more of a warning when when someone is trying to change the executors to 0 in the node config page. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41385) Setting number of executors to 0 on a slave removes the slave from view
Title: Message Title Alec Matschiner commented on JENKINS-41385 Re: Setting number of executors to 0 on a slave removes the slave from view Yep, I agree. Thanks for the update! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42113) Unable to download plugins
Title: Message Title Alec Matschiner commented on JENKINS-42113 Re: Unable to download plugins Ah ok, thanks! Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42113) Unable to download plugins
Title: Message Title Alec Matschiner edited a comment on JENKINS-42113 Re: Unable to download plugins Dropping this to minor. Something must have been resolve resolved as I'm now able to download plugins. Still not quite sure what went on.. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42113) Unable to download plugins
Title: Message Title Alec Matschiner commented on JENKINS-42113 Re: Unable to download plugins Dropping this to minor. Something must have been resolve as I'm now able to download plugins. Still not quite sure what went on.. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42113) Unable to download plugins
Title: Message Title Alec Matschiner updated an issue Jenkins / JENKINS-42113 Unable to download plugins Change By: Alec Matschiner Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42113) Unable to download plugins
Title: Message Title Alec Matschiner created an issue Jenkins / JENKINS-42113 Unable to download plugins Issue Type: Bug Assignee: Oleg Nenashev Components: _unsorted Created: 2017/Feb/16 5:01 PM Environment: Jenkins ver. 2.32.1 Jenkins ver. 2.36 Priority: Critical Reporter: Alec Matschiner This morning I was testing out some plugins and wanted to download the Pipeline Plugin on my local test Jenkins instance. I received a socket timeout and tried to troubleshoot it for a bit thinking it was something on my local machine. Eventually I tried to update a plugin on a different Jenkins instance not on my local machine and got the same socket timeout error. Is http://updates.jenkins-ci.org down? Stacktrace: hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/docker-plugin/0.16.2/docker-plugin.hpi (redirected to: http://archives.jenkins-ci.org/plugins/docker-plugin/0.16.2/docker-plugin.hpi) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:1172) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1678) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1876) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1652) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.SocketTimeoutException: connect timed out at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at
[JIRA] (JENKINS-41385) Setting number of executors to 0 on a slave removes the slave from view
Title: Message Title Alec Matschiner created an issue Jenkins / JENKINS-41385 Setting number of executors to 0 on a slave removes the slave from view Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Jan/24 7:00 PM Environment: Jenkins 2.32.1 and 2.36 Labels: slave node executor Priority: Minor Reporter: Alec Matschiner When I set any slave node besides the master to have 0 executors the slave vanishes from the Build Executor Status list, I cannot view it anywhere on Jenkins, and I cannot create a new node with the same name. It must still exist in Jenkins but it becomes inaccessible. When I manually type in the slave's URL I get a 404 Error. While I am setting the number of executors to 0 I get the warning: "Not a positive number" but that's all the warning I get. Is this the desired function behind this? If possible it would be nice to at least be able to see the node and configure it back to have a positive number of executors. The only way I see to get that node back is to use the CLI to delete it and then create a new one.
[JIRA] (JENKINS-23073) Jobs stop polling for file changes after 1-2 builds
Title: Message Title Alec Matschiner commented on JENKINS-23073 Re: Jobs stop polling for file changes after 1-2 builds Is there any update on this issue? I'm having an issue with a job that uses a script to trigger a build, and it was working fop a while, then all of a sudden seems to stop polling. There is no information in the Script Trigger log other than "Polling has not run yet." Is there a fix for this, a work around, or even a way to produce more log info to help debug? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32118) Opening Robot Framework log failed
Title: Message Title Alec Matschiner updated an issue Jenkins / JENKINS-32118 Opening Robot Framework log failed Change By: Alec Matschiner Attachment: Selection_243.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32118) Opening Robot Framework log failed
Title: Message Title Alec Matschiner commented on JENKINS-32118 Re: Opening Robot Framework log failed I've been using SCP plugin to publish the resulting log.html out to a directory I can grab it from. Sort of a way of dealing with this. However it would be extremely nice to be able to have this working without a work around. Is there any update on this? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
