[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Reinhold Füreder commented on JENKINS-58684 Re: Linux max task resource exhaustion after excessive timer thread creation Olivier Lamy Sorry for my delayed feedback: AFAIK (no user complaints in my company – at least none that I know of...) the snapshot build of sse-gateway worked fine; and on Jenkins server neither remaining "EventDispatcher.retryProcessor" threads, nor thousands of them at the same time. => Looks good 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.2452.1567057680422%40Atlassian.JIRA.
[JIRA] (JENKINS-59104) Custom tags are not published after upgrade of plugin Influx DB 2.0
Title: Message Title Aleksi Simell updated JENKINS-59104 Jenkins / JENKINS-59104 Custom tags are not published after upgrade of plugin Influx DB 2.0 Change By: Aleksi Simell Status: Fixed but Unreleased Resolved Released As: 2.0.1 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201526.1566916831000.2449.1567057620246%40Atlassian.JIRA.
[JIRA] (JENKINS-59113) Unable to create Job by copying config in 2.176.2
Title: Message Title
Vishnu Potti updated an issue
Jenkins / JENKINS-59113
Unable to create Job by copying config in 2.176.2
Change By:
Vishnu Potti
I upgraded from [ 2.176.1|https://jenkins.io/] version and started observing this issue.I downgraded to [ 2.176.1|https://jenkins.io/] to dooublecheck doublecheck and this issue doesnot does not exist. So this bug is specific to [ 2.176.2|https://jenkins.io/]*Steps* 1) Clicked on Create New job2) Entered Job name3) Entered an existing job name in Copy From section. Jenkins errored out with below exception in UI*PS :*Still the server has around 20% disk space left.I am able to create new jobs, only when I mention Copy from, I am getting this error. h2. {code:java}Stack tracejava.lang.NoClassDefFoundError: Could not initialize class sun.nio.fs.LinuxNativeDispatcher at sun.nio.fs.LinuxUserDefinedFileAttributeView.copyExtendedAttributes(LinuxUserDefinedFileAttributeView.java:291) at sun.nio.fs.LinuxFileSystem.copyNonPosixAttributes(LinuxFileSystem.java:72) at sun.nio.fs.UnixCopyFile.copyFile(UnixCopyFile.java:267) at sun.nio.fs.UnixCopyFile.copy(UnixCopyFile.java:581) at sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:253) at java.nio.file.Files.copy(Files.java:1274) at hudson.model.ItemGroupMixIn.copy(ItemGroupMixIn.java:244) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:188) at com.cloudbees.hudson.plugins.folder.Folder.doCreateItem(Folder.java:231) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Roy Lu assigned an issue to Daniel Gront Jenkins / JENKINS-59090 Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing Change By: Roy Lu Assignee: Roy Lu Daniel Gront 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.2442.1567046160258%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Roy Lu assigned an issue to Roy Lu Jenkins / JENKINS-59090 Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing Change By: Roy Lu Assignee: Maria Narcisa Galan Roy Lu 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.2439.1567046100157%40Atlassian.JIRA.
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Roy Lu assigned an issue to Maria Narcisa Galan Jenkins / JENKINS-59090 Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing Change By: Roy Lu Assignee: Roy Lu Maria Narcisa Galan 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.2436.1567046040365%40Atlassian.JIRA.
[JIRA] (JENKINS-59136) Deprecate plugins and provide suggestions to user
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user Change By: Joseph Petersen Much like security warnings it would be awesome to have a way to deprecate plugins and provide recommendations such as * Auto uninstall upstream service dependency is gone and plugin is useless. * Auto uninstall based on versions of other plugins (you have moved logic from area to another area of plugins) ** configuration-as-code-plugin is a good example of this. JCasC had a support-plugin that has been deprecated/tombstoned since 1.18 as long as you used newer role-strategy-plugin & credentials plugin So a user could have installed role-strategy v2.11 and credential v2.2.0 but still be using JCasC's support plugin v1.16, here it would be nice to uninstall the JCasC support plugin * Auto uninstall tombstone plugins * Auto uninstall due to security reasons * Suggest uninstall for security reasons * Suggest uninstall for any reason * Recommend using another plugin ** URL pointing to documentation for the recommendation ** In the case of something like users using a plugin hosted outside of the org but a newer plugin provides superior capabilities a good example of this is gitlab-branch-source-plugin see: [https://github.com/Argelbargel/gitlab-branch-source-plugin] [https://github.com/jenkinsci/gitlab-branch-source-plugin] * Suggest upgrading due to changes upstream services * Auto upgrade due to changes to upstream service * Implied suggested upgrade depending on matrix of plugins and their version with some conditions ? ** Let's say I updated JCasC to v1.28 where Vault secret source was moved from JCasC to the Hashicorp Vault plugin It would be nice to suggest user to upgrade if some condition is true, [see here for example|https://github.com/jenkinsci/configuration-as-code-plugin/blob/94a2a73095a290ed2cb92b7ace5bf3afbd64b1ba/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationAsCode.java#L677-L685] * Feel free to add bullets or comments with suggestions. Add Comment
[JIRA] (JENKINS-59136) Deprecate plugins and provide suggestions to user
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user Change By: Joseph Petersen Much like security warnings it would be awesome to have a way to deprecate plugins and provide recommendations such as * Auto uninstall upstream service dependency is gone and plugin is useless. * Auto uninstall based on versions of other plugins (you have moved logic from area to another area of plugins) ** configuration-as-code-plugin is a good example of this.JCasC had a support-plugin that has been deprecated/tombstoned since 1.18 as long as you used newer role-strategy-plugin & credentials pluginSo a user could have installed role-strategy v2.11 and credential v2.2.0 but still be using JCasC's support plugin v1.16, here it would be nice to uninstall the JCasC support plugin * Auto uninstall tombstone plugins * Auto uninstall due to security reasons * Suggest uninstall for security reasons * Suggest uninstall for any reason * Recommend using another plugin ** URL pointing to documentation for the recommendation ** In the case of something like users using a plugin hosted outside of the org but a newer plugin provides superior capabilities a good example of this is gitlab-branch-source-plugin see: [https://github.com/Argelbargel/gitlab-branch-source-plugin] [https://github.com/jenkinsci/gitlab-branch-source-plugin] * Suggest upgrading due to changes upstream services * Auto upgrade due to changes to upstream service * Implied suggested upgrade depending on matrix of plugins and their version? ** Let's say I updated JCasC to v1.28 where Vault secret source was moved from JCasC to the Hashicorp Vault pluginIt would be nice to suggest user to upgrade if some condition is true, [see here for example|https://github.com/jenkinsci/configuration-as-code-plugin/blob/94a2a73095a290ed2cb92b7ace5bf3afbd64b1ba/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationAsCode.java#L677-L685] * Feel free to add bullets or comments with suggestions. Add Comment
[JIRA] (JENKINS-59136) Deprecate plugins and provide suggestions to user
Title: Message Title Joseph Petersen updated an issue Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user Change By: Joseph Petersen Much like security warnings it would be awesome to have a way to deprecate plugins and provide recommendations such as * Auto uninstall upstream service dependency is gone and plugin is useless. * Auto uninstall based on version versions of another plugin other plugins (you have moved logic from one area to another area of plugins ) * * configuration-as-code-plugin is a good example of this.JCasC had a support-plugin that has been deprecated/tombstoned since 1.18 as long as you used newer role-strategy-plugin & credentials pluginSo a user could have installed role-strategy v2.11 and credential v2.2.0 but still be using JCasC's support plugin v1.16, here it would be nice to uninstall the JCasC support plugin * Auto uninstall tombstone plugins * Auto uninstall due to security reasons * Suggest uninstall for security reasons * Suggest uninstall for any reason * Recommend using another plugin ** URL pointing to documentation for the recommendation ** In the case of something like users using a plugin hosted outside of the org but a newer plugin provides superior capabilities a good example of this is gitlab-branch-source-plugin see:[https://github.com/Argelbargel/gitlab-branch-source-plugin][https://github.com/jenkinsci/gitlab-branch-source-plugin] * Suggest upgrading due to changes upstream services * Auto upgrade due to changes to upstream service * Implied suggested upgrade depending on matrix of plugins and their version? ** Let's say I updated JCasC to v1.28 where Vault secret source was moved from JCasC to the Hashicorp Vault pluginIt would be nice to suggest user to upgrade if some condition is true, [see here for example|https://github.com/jenkinsci/configuration-as-code-plugin/blob/94a2a73095a290ed2cb92b7ace5bf3afbd64b1ba/plugin/src/main/java/io/jenkins/plugins/casc/ConfigurationAsCode.java#L677-L685] * Feel free to add bullets or comments with suggestions. Add Comment
[JIRA] (JENKINS-59136) Deprecate plugins and provide suggestions to user
Title: Message Title Joseph Petersen created an issue Jenkins / JENKINS-59136 Deprecate plugins and provide suggestions to user Issue Type: Epic Assignee: Joseph Petersen Components: core Created: 2019-08-29 01:29 Priority: Minor Reporter: Joseph Petersen Much like security warnings it would be awesome to have a way to deprecate plugins and provide recommendations such as Auto uninstall upstream service dependency is gone and plugin is useless. Auto uninstall based on version of another plugin (you have moved logic from one to another) Auto uninstall tombstone plugins Auto uninstall due to security reasons Suggest uninstall for security reasons Suggest uninstall for any reason Recommend using another plugin URL pointing to documentation for the recommendation In the case of something like users using a plugin hosted outside of the org but a newer plugin provides superior capabilities a good example of this is gitlab-branch-source-plugin see: https://github.com/Argelbargel/gitlab-branch-source-plugin https://github.com/jenkinsci/gitlab-branch-source-plugin Suggest upgrading due to changes upstream services
[JIRA] (JENKINS-59113) Unable to create Job by copying config in 2.176.2
Title: Message Title Vishnu Potti updated an issue Jenkins / JENKINS-59113 Unable to create Job by copying config in 2.176.2 Change By: Vishnu Potti Priority: Major Critical 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201538.156695862.2429.1567039920102%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Olivier Lamy resolved as Fixed 1.20 version has been released Jenkins / JENKINS-58684 Linux max task resource exhaustion after excessive timer thread creation Change By: Olivier Lamy Status: Open Resolved Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.2427.1567039141426%40Atlassian.JIRA.
[JIRA] (JENKINS-59113) Unable to create Job by copying config in 2.176.2
Title: Message Title
Vishnu Potti updated an issue
Jenkins / JENKINS-59113
Unable to create Job by copying config in 2.176.2
Change By:
Vishnu Potti
I upgraded from [ 2.176.1|https://jenkins.io/] version and started observing this issue.I downgraded to [ 2.176.1|https://jenkins.io/] to dooublecheck and this issue doesnot exist. So this bug is specific to [ 2.176.2|https://jenkins.io/]* Steps * 1) Clicked on Create New job2) Entered Job name3) Entered an existing job name in Copy From section. Jenkins errored out with below exception in UI*PS :*Still the server has around 20% disk space left.I am able to create new jobs, only when I mention Copy from, I am getting this error. h2. {code:java}Stack tracejava.lang.NoClassDefFoundError: Could not initialize class sun.nio.fs.LinuxNativeDispatcher at sun.nio.fs.LinuxUserDefinedFileAttributeView.copyExtendedAttributes(LinuxUserDefinedFileAttributeView.java:291) at sun.nio.fs.LinuxFileSystem.copyNonPosixAttributes(LinuxFileSystem.java:72) at sun.nio.fs.UnixCopyFile.copyFile(UnixCopyFile.java:267) at sun.nio.fs.UnixCopyFile.copy(UnixCopyFile.java:581) at sun.nio.fs.UnixFileSystemProvider.copy(UnixFileSystemProvider.java:253) at java.nio.file.Files.copy(Files.java:1274) at hudson.model.ItemGroupMixIn.copy(ItemGroupMixIn.java:244) at hudson.model.ItemGroupMixIn.createTopLevelItem(ItemGroupMixIn.java:188) at com.cloudbees.hudson.plugins.folder.Folder.doCreateItem(Folder.java:231) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:49) at
[JIRA] (JENKINS-34886) Jenkins Git Error Invalid ID
Title: Message Title Mark Waite updated JENKINS-34886 Jenkins / JENKINS-34886 Jenkins Git Error Invalid ID Change By: Mark Waite Status: Reopened Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170551.1463497414000.2412.1567038000238%40Atlassian.JIRA.
[JIRA] (JENKINS-11547) Jobs trigger continually even though there are no changes due to git repository being "corrupt"
Title: Message Title Mark Waite updated JENKINS-11547 Jenkins / JENKINS-11547 Jobs trigger continually even though there are no changes due to git repository being "corrupt" Change By: Mark Waite Status: Reopened Open 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141773.1319796032000.2409.1567037882510%40Atlassian.JIRA.
[JIRA] (JENKINS-58981) Successful build marked as failed
Title: Message Title
Lukas Behal updated an issue
Jenkins / JENKINS-58981
Successful build marked as failed
Change By:
Lukas Behal
Successfully finished builds are marked as Failed. The build is using Performance Plugin. Console output:{code:java}...13:36:22 Archiving artifacts13:36:22 Recording fingerprints13:36:22 Creating parser with percentiles:'0,50,90,100,' filterRegex:null13:36:22 Performance: Recording JMeterCsv reports '_test_results\jmeter_tests\*.jtl'13:36:22 Performance: JMeterCsv copying reports to master, files '[E:\x.jtl]'13:36:22 Performance: JMeterCsv parsing local reports '[C:\x.jtl]'13:36:22 Performance: Parsing report file 'C:\x.jtl' with filterRegex 'null'.13:36:22 Performance: Percentage of errors greater or equal than 1% sets the build as unstable13:36:22 Performance: Percentage of errors greater or equal than 2% sets the build as failure13:36:22 Performance: File JMeterTestsResults.jtl reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS13:36:22 Disk usage plugin fails during calculation disk usage of this build.13:36:22 Notifying upstream projects of job completion13:36:22 Finished: SUCCESS{code}This build is displayed in Jenkins as:!image-2019-08-19-14-44-52-341.png!I tried to search where the build status is stored on file system and found following record in _all_builds.mr_ in the jobs folder.{code:java}...67,1566178385513,197137,SUCCESS{code}This issue is intermittent. I would really appreciate any help. Update:I did notice that all build.xml files of the jobs with this intermittent issue are missing xml tag as opposed to others. These jobs are being run on remote agent. Could this be relevant to this issue?
Add Comment
[JIRA] (JENKINS-59132) Perforce Workspace spec file root skipped
Title: Message Title
Joel Brown commented on JENKINS-59132
Re: Perforce Workspace spec file root skipped
Check out jenkins.model.Jenkins.workspacesDir - e.g., start your jenkins (including slaves) with -Djenkins.model.Jenkins.workspacesDir=d:\${ITEM_FULL_NAME} Note the comments for this property: https://wiki.jenkins.io/display/JENKINS/Features+controlled+by+system+properties If you do a plain "d:\" then make sure all the workspace View field, right-hand sides, don't overlap. Otherwise you can use a Perforce form-in client trigger to alter the root. Just make sure you only change the root for jenkins clients.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201564.1567024301000.2377.1567037640161%40Atlassian.JIRA.
[JIRA] (JENKINS-58981) Successful build marked as failed
Title: Message Title
Lukas Behal updated an issue
Jenkins / JENKINS-58981
Successful build marked as failed
Change By:
Lukas Behal
Successfully finished builds are marked as Failed. The build is using Performance Plugin. Console output:{code:java}...13:36:22 Archiving artifacts13:36:22 Recording fingerprints13:36:22 Creating parser with percentiles:'0,50,90,100,' filterRegex:null13:36:22 Performance: Recording JMeterCsv reports '_test_results\jmeter_tests\*.jtl'13:36:22 Performance: JMeterCsv copying reports to master, files '[E:\x.jtl]'13:36:22 Performance: JMeterCsv parsing local reports '[C:\x.jtl]'13:36:22 Performance: Parsing report file 'C:\x.jtl' with filterRegex 'null'.13:36:22 Performance: Percentage of errors greater or equal than 1% sets the build as unstable13:36:22 Performance: Percentage of errors greater or equal than 2% sets the build as failure13:36:22 Performance: File JMeterTestsResults.jtl reported 0.0% of errors [SUCCESS]. Build status is: SUCCESS13:36:22 Disk usage plugin fails during calculation disk usage of this build.13:36:22 Notifying upstream projects of job completion13:36:22 Finished: SUCCESS{code}This build is displayed in Jenkins as:!image-2019-08-19-14-44-52-341.png!I tried to search where the build status is stored on file system and found following record in _all_builds.mr_ in the jobs folder.{code:java}...67,1566178385513,197137,SUCCESS{code}This issue is intermittent. I would really appreciate any help. Update:I did notice that
Add Comment
This message was sent by
[JIRA] (JENKINS-57757) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject
Title: Message Title Rick updated JENKINS-57757 Jenkins / JENKINS-57757 java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject Change By: Rick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 1.4 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199703.1559198718000.2373.1567036680185%40Atlassian.JIRA.
[JIRA] (JENKINS-57757) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject
Title: Message Title Rick updated JENKINS-57757 Jenkins / JENKINS-57757 java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject Change By: Rick Status: Fixed but Unreleased Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199703.1559198718000.2374.1567036680215%40Atlassian.JIRA.
[JIRA] (JENKINS-57757) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject
Title: Message Title Rick started work on JENKINS-57757 Change By: Rick Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199703.1559198718000.2371.1567036500192%40Atlassian.JIRA.
[JIRA] (JENKINS-57757) java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject
Title: Message Title Rick updated JENKINS-57757 Jenkins / JENKINS-57757 java.lang.ClassCastException: org.jenkinsci.plugins.workflow.job.WorkflowJob cannot be cast to hudson.model.AbstractProject Change By: Rick Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199703.1559198718000.2372.1567036500220%40Atlassian.JIRA.
[JIRA] (JENKINS-48525) Perforce plugin doesn't sync
Title: Message Title Kurt Routley commented on JENKINS-48525 Re: Perforce plugin doesn't sync One of our teammates is seeing this again, although their automation stack is on an older version of the p4 plugin and p4d, but based on the p4java release notes it should have sufficient parallel sync support. They hit the issue where sync would run and report success in automation, however the files were not actually sync'd, and it wasn't resolved until they explicitly set the sync configuration to have parallel sync enabled, but with threads, minimum files, and minimum bytes all set to 0. Environment information: Running Jenkins 2.164.2 with P4 Plugin 1.7.4 (uses p4java 2017.2.1535715) and SCM API Plugin 2.6.3. Client VMs (Jenkins agents) are syncing from a P4D Commit server on 2017.2.1650199. P4V is not installed on the client VMs Client VMs are an assortment of Windows Server 2016 (8-core, 32GB RAM) and Mac Mojave (4-core, 16GB RAM) VMs Let me know if you need any more information 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187142.1513120856000.2370.1567036440690%40Atlassian.JIRA.
[JIRA] (JENKINS-55134) InputAction No page found 'sidepanel.jelly' for class
Title: Message Title Bryce McHugh commented on JENKINS-55134 Re: InputAction No page found 'sidepanel.jelly' for class Andrew Bayer Thank you for the comment. We had run into this several times before this was originally posted, but have not run into it since upgrading Jenkins. We just had this happen on one job where an input link in the job resulted in an error page with this stack trace. The parameters page on the same job did not have any issues. The version of Jenkins running the job was 2.150.1. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196198.1544577686000.2354.1567035420291%40Atlassian.JIRA.
[JIRA] (JENKINS-59135) Make monitor.gif transparent
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59135 Make monitor.gif transparent Issue Type: Improvement Assignee: Josh Soref Components: core Created: 2019-08-28 22:43 Priority: Minor Reporter: Josh Soref The underlying svg is transparent Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Agent tunnel connection issues after ugrading Jenkins to 2.191 I updated the title to something that I think is a little clearer and more accurate. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.2348.1567031220422%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson updated an issue Jenkins / JENKINS-59094 Agent tunnel connection issues after ugrading Jenkins to 2.191 Change By: Jeff Thompson Summary: Windows Agent tunnel connection issues after ugrading Jenkins to 2.191 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.2346.1567031220390%40Atlassian.JIRA.
[JIRA] (JENKINS-59134) Make save.png transparent
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59134 Make save.png transparent Issue Type: Improvement Assignee: Josh Soref Attachments: image-2019-08-28-18-03-52-970.png Components: core Created: 2019-08-28 22:15 Priority: Minor Reporter: Josh Soref Most objects in Jenkins properly apply transparency. The only one that is clearly wrong is the save button: Notably, the original file has transparency: https://github.com/jenkinsci/jenkins/blob/master/war/images/save.svg Fwiw, Git's logo is officially transparent (i.e. a single color for the diamond and transparency for the graph and the background). Add Comment
[JIRA] (JENKINS-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title Mike commented on JENKINS-38046 Re: Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline Austin Phillips thanks for your solution! It's not multi-branch but it is working well for me. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174194.1473291533000.2292.1567030561304%40Atlassian.JIRA.
[JIRA] (JENKINS-59094) Windows Agent connection issues after ugrading Jenkins to 2.191
Title: Message Title Jeff Thompson commented on JENKINS-59094 Re: Windows Agent connection issues after ugrading Jenkins to 2.191 PR uploaded at https://github.com/jenkinsci/remoting/pull/345 . This PR restores the parsing behavior for empty port and for empty host. The separator character is still required. I haven't been able to reproduce or test these other scenarios. It would be great if someone else with those setups could give it a try. If we can get some more reviews or testing, I should be able to get a new version out quickly. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.2287.1567030080192%40Atlassian.JIRA.
[JIRA] (JENKINS-59123) Make none.gif transparent
Title: Message Title Josh Soref assigned an issue to Josh Soref Jenkins / JENKINS-59123 Make none.gif transparent Change By: Josh Soref Assignee: Josh Soref 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201554.156700477.2285.1567029840071%40Atlassian.JIRA.
[JIRA] (JENKINS-59133) Primeiro Projeto
Title: Message Title João Marques created an issue Jenkins / JENKINS-59133 Primeiro Projeto Issue Type: Task Assignee: Unassigned Components: _unsorted Created: 2019-08-28 21:52 Priority: Minor Reporter: João Marques 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201565.1567029129000.2284.1567029180112%40Atlassian.JIRA.
[JIRA] (JENKINS-59127) Blue Ocean should have a page for individual branches (folders), as classic Jenkins does
Title: Message Title Larry West closed an issue as Not A Defect I just realized there is this: > https://build.example.com/java-org/blue/organizations/jenkins/java-proj/activity/?branch=develop ...which is close enough for my purposes, so I'm closing this. Jenkins / JENKINS-59127 Blue Ocean should have a page for individual branches (folders), as classic Jenkins does Change By: Larry West Status: Open Closed Resolution: Not A Defect 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201559.1567014366000.2281.1567026600250%40Atlassian.JIRA.
[JIRA] (JENKINS-59131) TypeError: null is not an object (evaluating 'run.causes.length')
Title: Message Title Kevin Ushey commented on JENKINS-59131 Re: TypeError: null is not an object (evaluating 'run.causes.length') Candidate PR at https://github.com/jenkinsci/blueocean-plugin/pull/2020. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201563.1567024188000.2277.1567024500055%40Atlassian.JIRA.
[JIRA] (JENKINS-59132) Perforce Workspace spec file root skipped
Title: Message Title
Alena Volarevic created an issue
Jenkins / JENKINS-59132
Perforce Workspace spec file root skipped
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2019-08-28 20:31
Labels:
p4plugin p4 workspace workspace-root
Priority:
Minor
Reporter:
Alena Volarevic
I have a drive letter (lets say D) that is being used as a root for all the perforce workspaces that we have on our system. I am trying to use the p4 plugin in Jenkins to sync the code before running the unittest or running any script, and no matter what kind of workspace behavior I use (besides the Static one), It is always syncing the code to the {Jenkins workspace}/{JOB_NAME} and I would like to keep it on the D drive as all the perforce workspaces we have are set right now like that. I managed to get this with the Static workspace behavior, but in that case I have to remote to the slave machines to create the workspace by hand and then use it, which then defeats the purpose of Jenkins... I tried using the Spec workspace behavior, cause I though if I specify the root in that file, the perforce workspace should use that folder as a root, but whenever it starts the sync part, it again syncs to the jenkins workspace location and sets the workspace root to use that location for root... It woudl be really nice if we can control where do we want the root to be, if we want to copy the files to the new jenkins workspace or use the root folder that we already had setup before implementing Jenkins. If I'm missing something I apologize for creating this ticket. I am using Jenkins ver 2.190 P4 Plugin 1.10.3 Thanks.
[JIRA] (JENKINS-59131) TypeError: null is not an object (evaluating 'run.causes.length')
Title: Message Title Kevin Ushey created an issue Jenkins / JENKINS-59131 TypeError: null is not an object (evaluating 'run.causes.length') Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2019-08-28 20:29 Priority: Minor Reporter: Kevin Ushey I'm seeing the following _javascript_ exception when I attempt to navigate to the blue ocean pipeline. Copied from Safari: [Log] There has been an error while trying to get the run data. (blueocean-core-js.js, line 57459) TypeError: null is not an object (evaluating 'run.causes.length') cause — jenkins-js-extension.js:93976 render — jenkins-js-extension.js:94037 _renderValidatedComponentWithoutOwnerOrContext — jenkins-design-language.js:69002 _renderValidatedComponent — jenkins-design-language.js:69025:95 performInitialMount — jenkins-design-language.js:68560 mountComponent — jenkins-design-language.js:68456 mountComponent — jenkins-design-language.js:75122 mountChildren — jenkins-design-language.js:74035 _createInitialChildren — jenkins-design-language.js:69925 mountComponent — jenkins-design-language.js:69744 mountComponent — jenkins-design-language.js:75122 performInitialMount — jenkins-design-language.js:68569 mountComponent — jenkins-design-language.js:68456 mountComponent — jenkins-design-language.js:75122 mountChildren — jenkins-design-language.js:74035 _createInitialChildren — jenkins-design-language.js:69925 mountComponent — jenkins-design-language.js:69744 mountComponent — jenkins-design-language.js:75122 performInitialMount — jenkins-design-language.js:68569 mountComponent — jenkins-design-language.js:68456 mountComponent — jenkins-design-language.js:75122 performInitialMount — jenkins-design-language.js:68569 mountComponent — jenkins-design-language.js:68456 mountComponent —
[JIRA] (JENKINS-59011) Log web hook exception in the folder events log
Title: Message Title Parichay Barpanda resolved as Fixed Jenkins / JENKINS-59011 Log web hook exception in the folder events log Change By: Parichay Barpanda Status: Open Resolved Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201364.1566310227000.2274.1567021200369%40Atlassian.JIRA.
[JIRA] (JENKINS-59130) toko obat bius asli
Title: Message Title fitriyani beauty created an issue Jenkins / JENKINS-59130 toko obat bius asli Issue Type: Task Assignee: Technical Support Components: absint-a3-plugin Created: 2019-08-28 19:26 Priority: Major Reporter: fitriyani beauty 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201562.1567020415000.2272.1567020420295%40Atlassian.JIRA.
[JIRA] (JENKINS-59129) "Build step 'Execute shell' marked build as failure" happens, would the remaining process be going?
Title: Message Title chun ji created an issue Jenkins / JENKINS-59129 "Build step 'Execute shell' marked build as failure" happens, would the remaining process be going? Issue Type: New Feature Assignee: Unassigned Components: _unsorted Created: 2019-08-28 19:10 Environment: Ubuntu 16.0.4 Priority: Minor Reporter: chun ji I have created a "freestyle" job in my Jenkins which is running on Ubuntu server. The commands of that job is as such: "... pip install behave pip install selenium pip install -r features/requirements.txt behave ./features/group1/*.feature behave ./features/group2/*.feature ... ", In details, it is trying to execute BDD test cases from both group1 and group2 direction. Dring the regular runtime, sometimes, some test case may hit an intermittent failure, and one test case fails. In the Console Output, I am see this type of message: " 0 features passed, 1 failed, 0 skipped 0 scenarios passed, 1 failed, 0 skipped 3 steps passed, 1 failed, 1 skipped, 0 undefined Took 2m48.770s Build step 'Execute shell' marked build as failure ". As it tells me that "the current test case takes 2m48.770s to process, 3 passed and 1 fails". And because of that, the remaining unexecuted tests are skipped as well. But since all test test cases are independent of each other, Is there a way I can have the rest still running ? Thanks, Jack
[JIRA] (JENKINS-58242) Look into Failed Junit Test on Ubuntu
Title: Message Title Kristin Whetstone commented on JENKINS-58242 Re: Look into Failed Junit Test on Ubuntu The tests with `buildPlugin` should cover this as it tests on linux and windows. I think this is safe to close. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200305.1561669084000.2266.1567018500613%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Marcello Ribeiro commented on JENKINS-59092 Re: Blue Ocean does not allow us to list Bitbucket repositories 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2263.1567017840133%40Atlassian.JIRA.
[JIRA] (JENKINS-59128) hudson.model.UpdateCenter.never = true not working
Title: Message Title Jeroen Wolff created an issue Jenkins / JENKINS-59128 hudson.model.UpdateCenter.never = true not working Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-08-28 18:34 Priority: Minor Reporter: Jeroen Wolff When is start Jenkins there is alway a connection made to the UpdateCentre. Even when i set hudson.model.UpdateCenter.never to true I have no internet so there is always a timeout in the log. Looks like a scheduled action which i cannot stop. INFO: The attempt #1 to do the action check updates server failed with an allowed exception: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:666) at sun.net.NetworkClient.doConnect(NetworkClient.java:175) at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1162) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1056) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1570) at
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Gavin Mogan commented on JENKINS-59092 Re: Blue Ocean does not allow us to list Bitbucket repositories oh I didn't read the message fully, I thought you said it would only break on the second time doing it, was fine after restart. No work around sorry. I think you'll have better luck with the classic UI 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2260.1567016700140%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Marcello Ribeiro commented on JENKINS-59092 Re: Blue Ocean does not allow us to list Bitbucket repositories Gavin Mogan thanks for you suggestion and i´ll try it as you said. Its is no clear about what you mean with a "crappy work around". Can you please clear that? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2257.1567016520176%40Atlassian.JIRA.
[JIRA] (JENKINS-59011) Log web hook exception in the folder events log
Title: Message Title Joseph Petersen commented on JENKINS-59011 Re: Log web hook exception in the folder events log This is done by throwing exception 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201364.1566310227000.2254.1567016160634%40Atlassian.JIRA.
[JIRA] (JENKINS-58212) VaultTokenCredentialBinding is not working in pipeline
Title: Message Title Joseph Petersen commented on JENKINS-58212 Re: VaultTokenCredentialBinding is not working in pipeline Nicolas Drufin is this issue present in 2.5.0? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200272.1561559302000.2251.1567015680171%40Atlassian.JIRA.
[JIRA] (JENKINS-59127) Blue Ocean should have a page for individual branches (folders), as classic Jenkins does
Title: Message Title Larry West created an issue Jenkins / JENKINS-59127 Blue Ocean should have a page for individual branches (folders), as classic Jenkins does Issue Type: Improvement Assignee: Ivan Meredith Components: blueocean-display-url-plugin, blueocean-plugin Created: 2019-08-28 17:46 Environment: 2.176.2 with 1.18.1 of these plug-ins: Bitbucket Pipeline for BO, BO, BO Core JS, BO Executor Info, BO Pipeline Editor, i18n for BO, Personalization for BO, Pipeline implementation for BO, REST API for BO, REST Implementation for BO, Web for BO; also: Display URL for BO 2.3.0 Labels: Folders folders UI blueocean blueocean-ui Priority: Minor Reporter: Larry West Background In classic Jenkins, I can provide users a stable link from, say, a GitHub readme to the folder/list of build jobs for a particular branch. E.g.: > https://build.example.com/java-org/job/java-project/job/master/ > https://build.example.com/java-org/job/java-project/job/develop/ And those will always take the user to a page with the most recent build job on "master" or "develop" listed at the top. The issue But in Blue Ocean, all we have is "branches": > https://build.example.com/java-org/blue/organizations/jenkins/java-project/branches/ Some of our projects have over a hundred branches recently active (for automated testing), and it can be a chore to click to find a specific branch (there's no search here, either). When we click on the "develop" or "master" branch there, we are directly taken to the most recent build, which is often useful, but that link becomes stale on the next commit to
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Marcello Ribeiro edited a comment on JENKINS-59092 Re: Blue Ocean does not allow us to list Bitbucket repositories [~jhartley], I don´t know if you could reopen that issue, once i have a detailled video with the issue evidence and its behaviour...It only happens after second time we try listing the repos. (Exception is thrown every times, but the eternal "loading..." message happens only when you navigate any other Jenkins screens, you come back to pipeline creation screen and try it again) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2245.1567013040260%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Marcello Ribeiro commented on JENKINS-59092 Re: Blue Ocean does not allow us to list Bitbucket repositories Jeremy Hartley, I know if you could reopen that issue, once i have a detailled video with the issue evidence and its behaviour... It only happens after second time we try listing the repos. (Exception is thrown every times, but the eternal "loading..." message happens only when you navigate any other Jenkins screens, you come back to pipeline creation screen and try it again) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2243.1567013040230%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Gavin Mogan edited a comment on JENKINS-59092 Re: Blue Ocean does not allow us to list Bitbucket repositories [~marcello_ribeiro] so I'm kinda at the limit I can do as an OSS contributor since I can't reproduce it. Also you have a kinda crappy work around so its not highest priority. My suggestion is to try to get as much information as you can prepareted, then try out the 30 minutes free cloudbees support and see if they can raise a ticket internally to get more traction on it - [ https://www.cloudbees.com/go/jenkins-support-ama ] 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2240.1567012320142%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Gavin Mogan commented on JENKINS-59092 Re: Blue Ocean does not allow us to list Bitbucket repositories Marcello Ribeiro so I'm kinda at the limit I can do as an OSS contributor since I can't reproduce it. Also you have a kinda crappy work around so its not highest priority. My suggestion is to try out the 30 minutes free cloudbees support and see if they can raise a ticket internally to get more traction on it - https://www.cloudbees.com/go/jenkins-support-ama 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2237.1567012260137%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Gavin Mogan reopened an issue Jenkins / JENKINS-59092 Blue Ocean does not allow us to list Bitbucket repositories Change By: Gavin Mogan Resolution: Cannot Reproduce Status: Closed Reopened 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2234.1567012200428%40Atlassian.JIRA.
[JIRA] (JENKINS-42502) blueocean dependencies do not seem to be optional - causing the whole UI to break
Title: Message Title James Nord commented on JENKINS-42502 Re: blueocean dependencies do not seem to be optional - causing the whole UI to break I believe (not validated) that certain blueocean plugins can now be uninstalled. You should not need the blueOcean aggregator and from then on you can uninstall the blueocean-Jira plugin. Note you will have to maintain all of the blueocean plugins at the same version manually from then on. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179429.1488815363000.2231.1567010220171%40Atlassian.JIRA.
[JIRA] (JENKINS-42502) blueocean dependencies do not seem to be optional - causing the whole UI to break
Title: Message Title Antoine Musso commented on JENKINS-42502 Re: blueocean dependencies do not seem to be optional - causing the whole UI to break I have a use case. Blue Ocean depends on a lot of plugins which would get security updates from time to time. Whenever one of those plugins is hit by a security update, we have to update our Jenkins installations even though we have no use for the plugins. Though I get the intent that if one installs the Jira plugin, the Blue Ocean integration should be installed as well. In our case we do not use Jira at all and would thus happily dispose of both Jira and the related integration plugins. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179429.1488815363000.2227.1567009920201%40Atlassian.JIRA.
[JIRA] (JENKINS-48096) EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance
Title: Message Title Raihaan Shouhell commented on JENKINS-48096 Re: EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance This shouldn't be too hard to backport. https://github.com/jenkinsci/ec2-plugin/pull/378 is the current implementation of checking if creds are ok and refreshing them 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186661.1511004471000.2219.1567008720262%40Atlassian.JIRA.
[JIRA] (JENKINS-59092) Blue Ocean does not allow us to list Bitbucket repositories
Title: Message Title Marcello Ribeiro commented on JENKINS-59092 Re: Blue Ocean does not allow us to list Bitbucket repositories Gavin Mogan, as i said i´ve spent some time tested the issue, once it is intermitent and yesterday it seemed to be ok, but today it raised up again. Same enviroment, same Bitbucket username/password. One new information is: If i restart Jenkins process it runs ok by the first time. I am recording a video with issue. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201512.1566860104000.2215.1567008660189%40Atlassian.JIRA.
[JIRA] (JENKINS-48096) EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance
Title: Message Title rsandell commented on JENKINS-48096 Re: EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance Any insight into what was fixed in 1.44 that fixed this issue? I'm investigating if it is possible to backport the fix into the 1.42 line. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186661.1511004471000.2207.1567008540338%40Atlassian.JIRA.
[JIRA] (JENKINS-59108) Artifactory plugin can't publish build info for Gradle builds
Title: Message Title Yahav Itzhak assigned an issue to Yahav Itzhak Jenkins / JENKINS-59108 Artifactory plugin can't publish build info for Gradle builds Change By: Yahav Itzhak Assignee: Eyal Ben Moshe Yahav Itzhak 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201532.1566935841000.2204.1567008240188%40Atlassian.JIRA.
[JIRA] (JENKINS-59108) Artifactory plugin can't publish build info for Gradle builds
Title: Message Title Yahav Itzhak commented on JENKINS-59108 Re: Artifactory plugin can't publish build info for Gradle builds Kevin Phillips, this warning introduced in the Groovy Plugin v 2.7.1 at this commit. More information can be found in JENKINS-58643. There is an open pull request that resolves it. You're welcome to vote up. At the meanwhile, you can ignore the meaningless warning. However, I didn't managed to understand. Does the artifacts been published to Artifactory or not? Do you see 'uploading' messages at the build log? Do you see them at the build-info page at Artifactory? Thanks. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201532.1566935841000.2201.1567008180932%40Atlassian.JIRA.
[JIRA] (JENKINS-59126) Add compatibility test with JCasC
Title: Message Title Francisco Fernández updated JENKINS-59126 Jenkins / JENKINS-59126 Add compatibility test with JCasC Change By: Francisco Fernández Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201558.1567006548000.2191.1567007400134%40Atlassian.JIRA.
[JIRA] (JENKINS-59126) Add compatibility test with JCasC
Title: Message Title Francisco Fernández started work on JENKINS-59126 Change By: Francisco Fernández Status: Open In Progress 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201558.1567006548000.2190.1567006560392%40Atlassian.JIRA.
[JIRA] (JENKINS-59125) test
Title: Message Title Sai Test created an issue Jenkins / JENKINS-59125 test Issue Type: Task Assignee: Varun Menon Components: test-results-analyzer-plugin Created: 2019-08-28 15:35 Priority: Minor Reporter: Sai Test 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201557.1567006519000.2188.1567006560363%40Atlassian.JIRA.
[JIRA] (JENKINS-59126) Add compatibility test with JCasC
Title: Message Title Francisco Fernández created an issue Jenkins / JENKINS-59126 Add compatibility test with JCasC Issue Type: Improvement Assignee: Francisco Fernández Components: saml-plugin Created: 2019-08-28 15:35 Labels: jcasc-compatibility Priority: Minor Reporter: Francisco Fernández So far, saml-plugin is compatible with JCasC and can be both exported and configured using that plugin. It would be great to have a compatibility test so any future incompatibility can be detected in advance in such way as other plugins: ant-plugin git-plugin antisamy-markup-formatter-plugin Add Comment
[JIRA] (JENKINS-54571) Problem with jcasc compatibility plugin and job priority in Jenkins
Title: Message Title Cuong Tran commented on JENKINS-54571 Re: Problem with jcasc compatibility plugin and job priority in Jenkins Yeah, I was afraid you were going to say that. That's a shame jcasc can't handle everything. Thanks for the reply. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195354.1542018406000.2179.1567006440172%40Atlassian.JIRA.
[JIRA] (JENKINS-59124) I am trying to take screenshot for IE browser through takeSnapshot() java code but always getting black image as output, same code runs fine with local setup(through eclipse).
Title: Message Title Akshay Shukla created an issue Jenkins / JENKINS-59124 I am trying to take screenshot for IE browser through takeSnapshot() java code but always getting black image as output, same code runs fine with local setup(through eclipse). Issue Type: Task Assignee: Akshay Shukla Attachments: Capture.PNG Components: core Created: 2019-08-28 15:28 Environment: Windows operating system internet Explorer browser Java 8 Labels: snapshot Priority: Critical Reporter: Akshay Shukla When using Internet Explorer driver and automating testing through selenium and jenkins, getting black screen output screenshot and same thing works for chrome. But i am dependent to use Internet Explorer. Kindly assist regarding taking screenshot in Internet Explorer in Server. Jenkins installed and testing done in Windows Server. Language used is Java
[JIRA] (JENKINS-59123) Make none.gif transparent
Title: Message Title
Josh Soref updated an issue
Jenkins / JENKINS-59123
Make none.gif transparent
Change By:
Josh Soref
Various random places end up w/ 1px wide or 16px wide white elements on gray backgrounds for no particular reason. It looks ugly.Unless there's a specific reason for {{none.gif}} to be white instead of transparent, it seems like transparent would be a better choice. This image is used, e.g. by the github-branch-source-plugin – it appears to the left of "User..." below:!image-2019-08-28-11-08-46-763.png!
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201554.156700477.2150.1567005000129%40Atlassian.JIRA.
[JIRA] (JENKINS-59123) Make none.gif transparent
Title: Message Title Josh Soref updated an issue Jenkins / JENKINS-59123 Make none.gif transparent Change By: Josh Soref Attachment: image-2019-08-28-11-08-46-763.png 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201554.156700477.2149.1567004940077%40Atlassian.JIRA.
[JIRA] (JENKINS-59123) Make none.gif transparent
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59123 Make none.gif transparent Issue Type: Improvement Assignee: Unassigned Components: core Created: 2019-08-28 15:06 Priority: Trivial Reporter: Josh Soref Various random places end up w/ 1px wide or 16px wide white elements on gray backgrounds for no particular reason. It looks ugly. Unless there's a specific reason for none.gif to be white instead of transparent, it seems like transparent would be a better choice. Add Comment
[JIRA] (JENKINS-57561) Ant plugin exports empty home and then crashes with NPE
Title: Message Title Francisco Fernández updated JENKINS-57561 Jenkins / JENKINS-57561 Ant plugin exports empty home and then crashes with NPE Change By: Francisco Fernández Status: In Review Resolved Resolution: Fixed Released As: ant-1.10 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199472.1558359982000.2147.1567004700253%40Atlassian.JIRA.
[JIRA] (JENKINS-56277) Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3.
Title: Message Title Gregg Dameron commented on JENKINS-56277 Re: Parameter separator (containing HTML tags) is not working after upgrading jenkins to 2.150.3. We ran into this problem too after 1.596.2 --> 2.150.1 upgrade. (Coincidentally, HTML tag support was also lost for parameter types "Node" and "Extended Choice".) Would really like to see HTML tag support restored. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197855.155115906.2135.1567004100434%40Atlassian.JIRA.
[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Jeff Thompson closed an issue as Incomplete Jenkins / JENKINS-55689 Not able to connect to jenkins master from windows slave Change By: Jeff Thompson Status: Reopened Closed Resolution: Incomplete 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196875.1547848244000.2129.1567003980919%40Atlassian.JIRA.
[JIRA] (JENKINS-55689) Not able to connect to jenkins master from windows slave
Title: Message Title Jeff Thompson commented on JENKINS-55689 Re: Not able to connect to jenkins master from windows slave Have you asked on the Jenkins users email list as suggested? Or the gitter channel? This looks like a usage or configuration question and not a specific defect. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196875.1547848244000.2124.1567003980800%40Atlassian.JIRA.
[JIRA] (JENKINS-59122) Need to schedule the Jenkins job dynamically.
Title: Message Title Prasanna Rengarajan created an issue Jenkins / JENKINS-59122 Need to schedule the Jenkins job dynamically. Issue Type: New Feature Assignee: Martin Spielmann Components: schedule-build-plugin Created: 2019-08-28 14:42 Priority: Major Reporter: Prasanna Rengarajan Hi Team, We would like to have a parameter plugin which will schedule the jenkins job dynamically by passing value to the parameter Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title Harish Kumar edited a comment on JENKINS-59105 Re: Accessing Jenkins using API token does not work in group memberships Yes as far I can tell the set up seems valid.Its is the crumb request which is failing : "https://jenkinsurl/crumbIssuer/api/json" Error : someuser is missing the Overall/Read permission 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201528.1566922172000.2084.1567002000163%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title Harish Kumar edited a comment on JENKINS-59105 Re: Accessing Jenkins using API token does not work in group memberships It fails in Yes as far I can tell the very first request made and it set up seems valid.Its is the crumb request which is failing : "https://jenkinsurl/crumbIssuer/api/json" 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201528.1566922172000.2082.1567001880126%40Atlassian.JIRA.
[JIRA] (JENKINS-42844) Slave to Agent Renaming: Upstart Slave Installer Module
Title: Message Title Bryan Choate assigned an issue to Bryan Choate Jenkins / JENKINS-42844 Slave to Agent Renaming: Upstart Slave Installer Module Change By: Bryan Choate Assignee: Bryan Choate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179846.1489679281000.2069.1567000980277%40Atlassian.JIRA.
[JIRA] (JENKINS-42842) Slave to Agent Renaming: Launchd Slave Installer Module
Title: Message Title Bryan Choate assigned an issue to Bryan Choate Jenkins / JENKINS-42842 Slave to Agent Renaming: Launchd Slave Installer Module Change By: Bryan Choate Assignee: Bryan Choate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179844.1489679153000.2073.1567000980326%40Atlassian.JIRA.
[JIRA] (JENKINS-42843) Slave to Agent Renaming: Systemd Slave Installer Module
Title: Message Title Bryan Choate assigned an issue to Bryan Choate Jenkins / JENKINS-42843 Slave to Agent Renaming: Systemd Slave Installer Module Change By: Bryan Choate Assignee: Bryan Choate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179845.1489679177000.2071.1567000980304%40Atlassian.JIRA.
[JIRA] (JENKINS-58493) Add NodeProperty to skip-clean-on-this-node
Title: Message Title pjdarton resolved as Fixed Fixed in version 1.0.6, which was released today. Jenkins / JENKINS-58493 Add NodeProperty to skip-clean-on-this-node Change By: pjdarton Status: In Progress Resolved Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200632.1563189253000.2032.1566997440135%40Atlassian.JIRA.
[JIRA] (JENKINS-58492) Improve robustness w.r.t. bad slave nodes
Title: Message Title pjdarton resolved as Fixed Fixed in version 1.0.6, which was released today. Jenkins / JENKINS-58492 Improve robustness w.r.t. bad slave nodes Change By: pjdarton Status: In Progress Resolved Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200631.1563187768000.2033.1566997500854%40Atlassian.JIRA.
[JIRA] (JENKINS-43269) workspace cleanup removes workspaces for running job
Title: Message Title pjdarton resolved as Fixed Fixed in version 1.0.6, which was released today. Jenkins / JENKINS-43269 workspace cleanup removes workspaces for running job Change By: pjdarton Status: In Progress Resolved Resolution: Fixed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180392.1490961803000.2028.1566997380611%40Atlassian.JIRA.
[JIRA] (JENKINS-59121) Multibranch build strategy extension plugin throws BitbucketSCMSource cannot be cast to AbstractGitSCMSource
Title: Message Title Benjamin Federau created an issue Jenkins / JENKINS-59121 Multibranch build strategy extension plugin throws BitbucketSCMSource cannot be cast to AbstractGitSCMSource Issue Type: Bug Assignee: Igal Gluh Components: multibranch-build-strategy-extension-plugin Created: 2019-08-28 13:00 Environment: Ubuntu 18.04, Jenkins 2.191, Bitbucket Branch Source Plugin 2.4.6, SCM API Plugin 2.6.3, Git plugin 3.12.0, Priority: Critical Reporter: Benjamin Federau I'm using a Multibranch Pipeline Project with the Bitbucket Branch Sources Plugin. Currently I get an exception when setting a included or excluded build strategy. In the Jenkins log file the output is: 2019-08-28 08:43:18.576+ [id=13442] INFOc.i.j.p.m.b.IncludeRegionBranchBuildStrategy#isAutomaticBuild: Included regions: [hub/azuredeploy.json, hub/azuredeploy.parameters.json, hub/Jenkinsfile] 2019-08-28 08:43:18.577+ [id=13442] SEVERE c.i.j.p.m.b.IncludeRegionBranchBuildStrategy#isAutomaticBuild: Unecpected exception java.lang.ClassCastException: com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource cannot be cast to jenkins.plugins.git.AbstractGitSCMSource at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:378) at com.igalg.jenkins.plugins.multibranch.buildstrategy.BranchBuildStrategyExtension.buildSCMFileSystem(BranchBuildStrategyExtension.java:55) at com.igalg.jenkins.plugins.multibranch.buildstrategy.IncludeRegionBranchBuildStrategy.isAutomaticBuild(IncludeRegionBranchBuildStrategy.java:96) at
[JIRA] (JENKINS-29353) Configurable number of builds for trends generation
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-29353 Configurable number of builds for trends generation Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163820.1436555899000.2019.1566996963362%40Atlassian.JIRA.
[JIRA] (JENKINS-28338) IO Exception: Truncated TAR archive during copy step in robot-plugin
Title: Message Title Aleksi Simell closed an issue as Duplicate Jenkins / JENKINS-28338 IO Exception: Truncated TAR archive during copy step in robot-plugin Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162772.1431352521000.2015.1566996963294%40Atlassian.JIRA.
[JIRA] (JENKINS-9386) Links to local screenshots in Robot plugin don't work if I view logs from "Original report files"
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-9386 Links to local screenshots in Robot plugin don't work if I view logs from "Original report files" Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.139553.1302863494000.2024.1566996963426%40Atlassian.JIRA.
[JIRA] (JENKINS-27141) Option to show only critical tests in graphs
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-27141 Option to show only critical tests in graphs Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160934.1424941909000.2007.1566996963156%40Atlassian.JIRA.
[JIRA] (JENKINS-29178) Robot Framework 2.9 output parsing is broken
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-29178 Robot Framework 2.9 output parsing is broken Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163639.1435821752000.2017.1566996963334%40Atlassian.JIRA.
[JIRA] (JENKINS-26980) Enable configuration of "Robot Results" column in the default job list view
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-26980 Enable configuration of "Robot Results" column in the default job list view Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.160766.1424121248000.2012.1566996963249%40Atlassian.JIRA.
[JIRA] (JENKINS-24916) Link to robot log from individual tests and suites
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-24916 Link to robot log from individual tests and suites Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.158412.1412014919000.1999.1566996901280%40Atlassian.JIRA.
[JIRA] (JENKINS-21644) Aggregated results in a multimodule maven project displays only values of the last submodule
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-21644 Aggregated results in a multimodule maven project displays only values of the last submodule Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153342.1391529597000.1997.1566996901243%40Atlassian.JIRA.
[JIRA] (JENKINS-24792) Cleanup graph zooming
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-24792 Cleanup graph zooming Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157620.1411373135000.2001.1566996901302%40Atlassian.JIRA.
[JIRA] (JENKINS-24868) Add the ability for robot plugin graph to show only failed tests
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-24868 Add the ability for robot plugin graph to show only failed tests Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157710.1411665447000.2004.1566996901342%40Atlassian.JIRA.
[JIRA] (JENKINS-22406) Show tags for test cases
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-22406 Show tags for test cases Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154207.1396010395000.1994.1566996843787%40Atlassian.JIRA.
[JIRA] (JENKINS-22060) Plugin does not count suite setup times into duration
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-22060 Plugin does not count suite setup times into duration Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153839.1394104304000.1989.1566996843235%40Atlassian.JIRA.
[JIRA] (JENKINS-24531) There should be high resolution versions of graphs available
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-24531 There should be high resolution versions of graphs available Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.157116.1409587319000.1991.1566996843540%40Atlassian.JIRA.
[JIRA] (JENKINS-20240) Build is incorrectly marked as successful
Title: Message Title Aleksi Simell closed an issue as Duplicate Jenkins / JENKINS-20240 Build is incorrectly marked as successful Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.151760.1382647936000.1978.1566996841969%40Atlassian.JIRA.
[JIRA] (JENKINS-19484) Robot Framework plugin shows result as "Failed!" on individual test case result page
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-19484 Robot Framework plugin shows result as "Failed!" on individual test case result page Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.150936.1378448872000.1985.1566996842828%40Atlassian.JIRA.
[JIRA] (JENKINS-21736) Make the archiving of output.xml optional
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-21736 Make the archiving of output.xml optional Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.153436.1392024021000.1981.1566996842101%40Atlassian.JIRA.
[JIRA] (JENKINS-15188) Human readable duration values for test summaries and trend graphs
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-15188 Human readable duration values for test summaries and trend graphs Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.145910.1347880751000.1959.1566996782023%40Atlassian.JIRA.
[JIRA] (JENKINS-10630) Robot Framework Plugin should copy Selenium screenshots, too
Title: Message Title Aleksi Simell closed an issue as Fixed Jenkins / JENKINS-10630 Robot Framework Plugin should copy Selenium screenshots, too Change By: Aleksi Simell Status: Resolved Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140824.1312862483000.1962.1566996782066%40Atlassian.JIRA.
