[JIRA] [copyartifact-plugin] (JENKINS-30655) Copy artifact hangs the job when the slave disconnects during copy
Title: Message Title JY Hsu commented on JENKINS-30655 Re: Copy artifact hangs the job when the slave disconnects during copy soft restarting means go https://jenkins-url/restart. This restart will never end when the problem happens. It appears that the whole Jenkins process is messed up when this happens. Only rebooting the host machine can resolve this. But this is a Jenkins server with several product team using it, so having to reboot every couple days is really a big problem. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-30655) Copy artifact hangs the job when the slave disconnects during copy
Title: Message Title ikedam updated an issue Jenkins / JENKINS-30655 Copy artifact hangs the job when the slave disconnects during copy It is rather considered an issue of Jenkins core as copyartifact depends on the function of Jenkins core for file copying from remotes. Would you get thread dumps (of both the master and the slave) when the problem occurs? Please see following pages for instructions to get thread dumps: https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump Would you let me know more details about "soft restarting the Jenkins process will also hang during the restart"? What exactly happens? I highly recommend you to use Jenkins LTS versions, as non-LTS versions are often unstable. Could you see whether the problem reproduces when you use the latest LTS version?: https://jenkins-ci.org/#stable Change By: ikedam Component/s: core Add Comment
[JIRA] [copyartifact-plugin] (JENKINS-30655) Copy artifact hangs the job when the slave disconnects during copy
Title: Message Title JY Hsu assigned an issue to ikedam Jenkins / JENKINS-30655 Copy artifact hangs the job when the slave disconnects during copy Change By: JY Hsu Assignee: ikedam Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-30655) Copy artifact hangs the job when the slave disconnects during copy
Title: Message Title JY Hsu created an issue Jenkins / JENKINS-30655 Copy artifact hangs the job when the slave disconnects during copy Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 26/Sep/15 2:00 AM Environment: Jenkins 1.599, Copy artifact 1.35 Priority: Blocker Reporter: JY Hsu We are copying a big file from another job to the test job. That takes 4~5 minutes. The problem is, if the slave disconnects during this 4~5 minutes, the copy artifact doesn't know and doesn't stop. As a result, this job will run forever. Cancelling the job doesn't cancel it at this moment. Even disconnecting the slave doesn't stop the job. The only way out of this is restart the master, and I mean reboot the master machine, because soft restarting the Jenkins process will also hang during the restart. This is really ugly when it happens, so the priority is blocker.
[JIRA] [core] (JENKINS-29068) Split Groovy out of core
Title: Message Title Kohsuke Kawaguchi updated an issue Jenkins / JENKINS-29068 Split Groovy out of core Change By: Kohsuke Kawaguchi Labels: 2.0 groovy split-plugins-from-core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-29093) POM location is deleted when changing Maven top-level target
Title: Message Title mdonohue resolved as Fixed Released in the 1.44 version of configurationslicing Jenkins / JENKINS-29093 POM location is deleted when changing Maven top-level target Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-29941) Using Configuration Slicer unsets the "Ignore post-commit hooks" checkbox for polled builds
Title: Message Title mdonohue resolved as Fixed Released in the 1.44 version of configurationslicing Jenkins / JENKINS-29941 Using Configuration Slicer unsets the "Ignore post-commit hooks" checkbox for polled builds Change By: mdonohue Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-19651) Config Slicing "Gradle version per project" yields stack trace output
Title: Message Title mdonohue resolved as Fixed Jenkins / JENKINS-19651 Config Slicing "Gradle version per project" yields stack trace output Change By: mdonohue Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [configurationslicing-plugin] (JENKINS-19651) Config Slicing "Gradle version per project" yields stack trace output
Title: Message Title mdonohue commented on JENKINS-19651 Re: Config Slicing "Gradle version per project" yields stack trace output Fixed in configurationslicing-1.41-2-g6c6f04b Code appears in the 1.44 release of the plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Daniel Beck resolved as Fixed This fix was merged into 1.609.2 and 1.617. That's why this issue is labeled '1.609.2-fixed'. Experiments using 1.609.1 are irrelevant. (Not sure why the LTS changelog didn't pick this up, but Kohsuke uses some weird generator for that, so I cannot even modify it to report the truth afterwards at the moment – this is being tracked as INFRA-264.) Jenkins / JENKINS-27739 Changes to slave environment variables are ignored by master Change By: Daniel Beck Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [run-condition-plugin] (JENKINS-30654) Several run conditional steps causes long configuration load times
Title: Message Title Steven Christou created an issue Jenkins / JENKINS-30654 Several run conditional steps causes long configuration load times Issue Type: Bug Assignee: bap Attachments: screenshot.png Components: run-condition-plugin Created: 26/Sep/15 12:12 AM Priority: Minor Reporter: Steven Christou For each run conditional that is added to the configuration page the load time almost comes at an n^2 cost. The reason for this is because for each run conditional that is added to the list in the job configuration screen is re-drawn in order to properly handle the spacing of each element on the screen. With a run conditional of 40 the job configuration page takes about 20 minutes to load! Screenshot.png is an example where I added multiple run conditionals and it took over 20 minutes to load because of the number of re-draws that needed to be executed.
[JIRA] [perforce-plugin] (JENKINS-30653) java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence when "-" is in Perforce stream name
Title: Message Title Rob Petti commented on JENKINS-30653 Re: java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence when "-" is in Perforce stream name Looks more like it's having problems with character sequences in your workspace view. "-" in the stream name might just be a red-herring, since there's no reason that should cause it to fail. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-30653) java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence when "-" is in Perforce stream name
Title: Message Title Rob Petti assigned an issue to Unassigned Jenkins / JENKINS-30653 java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence when "-" is in Perforce stream name Change By: Rob Petti Assignee: Rob Petti Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30055) Simple script with "long" loop created unloadable flow
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-30055 Simple script with "long" loop created unloadable flow Change By: Jesse Glick Labels: random performance robustness Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30055) Simple script with "long" loop created unloadable flow
Title: Message Title Jesse Glick commented on JENKINS-30055 Re: Simple script with "long" loop created unloadable flow Rather a file descriptor leak; the listener in DefaultStepContext gets notified asynchronously, so not fast enough to close the log files from completed steps. Also a failure to ever remove the listener results in a quadratic slowdown. With that fixed, the insertion of sleep unit: 'MILLISECONDS', time: 1 inside the loop lets it work, but without that extra pause the notifications just pile up undelivered and the error occurs. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-30653) java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence when "-" is in Perforce stream name
Title: Message Title Michael Graessle created an issue Jenkins / JENKINS-30653 java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence when "-" is in Perforce stream name Issue Type: Bug Assignee: Rob Petti Components: perforce-plugin Created: 25/Sep/15 9:57 PM Priority: Minor Reporter: Michael Graessle Currently getting an error when a stream name has a dash in the name of such as "my-stream": java.util.regex.PatternSyntaxException: Illegal/unsupported escape sequence at java.util.regex.Pattern.error(Pattern.java:1924) at java.util.regex.Pattern.escape(Pattern.java:2416) at java.util.regex.Pattern.atom(Pattern.java:2164) at java.util.regex.Pattern.sequence(Pattern.java:2046) at java.util.regex.Pattern.expr(Pattern.java:1964) at java.util.regex.Pattern.compile(Pattern.java:1665) at java.util.regex.Pattern.(Pattern.java:1337) at java.util.regex.Pattern.compile(Pattern.java:1022) at hudson.plugins.perforce.PerforceSCMHelper.getTokenPattern(PerforceSCMHelper.java:220) at hudson.plugins.perforce.PerforceSCMHelper.doesPathMatchView(PerforceSCMHelper.java:196) at hudson.plugins.perforce.PerforceSCMHelper.mapToWorkspace(PerforceSCMHelper.java:182) at com.tek42.perforce.parse.Changes.getWorkspacePathForFile(Changes.java:96) at com.tek42.perforce.parse.Changes.calculateWorkspacePaths(Changes.java:90) at com.tek42.perforce.parse.Changes.getChangelist(Changes.java:72) at com.tek42.perforce.parse.Changes.getChangelistsFromNumbers(Changes.java:431) at hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:1073) at hudson.model.AbstractProject.checkout(AbstractProject.java:1277) at hudson.model.AbstractBuil
[JIRA] [workflow-plugin] (JENKINS-30651) File descriptor leak when invoking for-loop
Title: Message Title Jesse Glick resolved as Duplicate Marking as a duplicate of the older issue, though this one seems to add the critical information that a file handle leak (in DefaultStepContext) is responsible. Jenkins / JENKINS-30651 File descriptor leak when invoking for-loop Change By: Jesse Glick Status: In Progress Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30055) Simple script with "long" loop created unloadable flow
Title: Message Title Jesse Glick started work on JENKINS-30055 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-30651) File descriptor leak when invoking for-loop
Title: Message Title Jesse Glick started work on JENKINS-30651 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-29851) global instance cap not respected for spot instances
Title: Message Title Archie Brentano commented on JENKINS-29851 Re: global instance cap not respected for spot instances I think this is major, since it causes money to be spent. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ec2-plugin] (JENKINS-29851) global instance cap not respected for spot instances
Title: Message Title Archie Brentano updated an issue Jenkins / JENKINS-29851 global instance cap not respected for spot instances Change By: Archie Brentano Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cli] (JENKINS-30652) jenkins-cli does not handle quoted argument containing dashes
Title: Message Title dgam dgam created an issue Jenkins / JENKINS-30652 jenkins-cli does not handle quoted argument containing dashes Issue Type: Bug Assignee: Unassigned Components: cli Created: 25/Sep/15 7:50 PM Environment: Version: 1.630 Priority: Critical Reporter: dgam dgam java -jar /usr/share/jenkins/jenkins-cli.jar -version Version: 1.630 java -jar /usr/share/jenkins/jenkins-cli.jar -s "http://127.0.0.1:8080" get-node "---" "---" is not a valid option java -jar jenkins-cli.jar get-node NODE Dumps the node definition XML to stdout. NODE : Name of the node java -jar /usr/share/jenkins/jenkins-cli.jar -s "http://127.0.0.1:8080" get-node "---aaa--" "---aaa--" is not a valid option java -jar jenkins-cli.jar get-node NODE Dumps the node definition XML
[JIRA] [core] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException
Title: Message Title
jmmckinnon edited a comment on JENKINS-26257
Re: ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException
We are seeing this issue as well. Jenkins 1.596-1 (LTS), Maven 3.2.2. Windows 7 Jenkins master, Windows (Webstart) slaves. I am not sure how long it's been going on but someone reported it to me last week, and I found this and enabled -XX:-OmitStackTraceInFastThrow and here's what our stack trace looks like:Important part seems to be:{noformat}java.util.concurrent.ExecutionException: java.lang.ClassCastException: hudson.model.Fingerprint$RangeSet cannot be cast to hudson.model.Fingerprint{noformat}It prints I'm guessing one or more times per artifact in the build. Here's one complete stacktrace which is the first following build success (there are probably 40-50 in our build, pages and pages, before it logs the artifact archiving){noformat}[INFO] BUILD SUCCESS[INFO] [INFO] Total time: 28:15 min[INFO] Finished at: 2015-09-25T12:31:20-04:00[INFO] Final Memory: 156M/1139M[INFO] ERROR: Asynchronous execution failurejava.util.concurrent.ExecutionException: java.lang.ClassCastException: hudson.model.Fingerprint$RangeSet cannot be cast to hudson.model.Fingerprint at hudson.remoting.Channel$3.adapt(Channel.java:784) at hudson.remoting.Channel$3.adapt(Channel.java:779) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186) at hudson.maven.Maven3Builder.call(Maven3Builder.java:143) at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Caused by: java.lang.ClassCastException: hudson.model.Fingerprint$RangeSet cannot be cast to hudson.model.Fingerprint at hudson.model.Fingerprint.load(Fingerprint.java:1250) at hudson.model.Fingerprint.load(Fingerprint.java:1238) at hudson.model.FingerprintMap.load(FingerprintMap.java:94) at hudson.model.FingerprintMap.load(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.get(KeyedDataStorage.java:154) at hudson.model.FingerprintMap.get(FingerprintMap.java:79) at hudson.model.FingerprintMap.get(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108) at hudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65) at hudson.maven.reporters.MavenFingerprinter$1.call(MavenFingerprinter.java:125) at hudson.maven.reporters.MavenFingerprinter$1.call(MavenFingerprinter.java:112) at hudson.maven.MavenBuild$ProxyImpl.execute(MavenBuild.java:423) at hudson.maven.MavenBuild$ProxyImpl2.execute(MavenBuild.java:551) at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at hudson.model.Executor$1.call(Executor.java:579) at hudson.util.InterceptingProxy$1.invoke(InterceptingProxy.java:23) at $Proxy54.execute(Unknown Source) at hudson.maven.MavenBuildProxy$Filter$AsyncInvoker.call(MavenBuildProxy.java:294) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.c
[JIRA] [core] (JENKINS-26257) ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException
Title: Message Title jmmckinnon commented on JENKINS-26257 Re: ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException We are seeing this issue as well. Jenkins 1.596-1 (LTS), Maven 3.2.2. Windows 7 Jenkins master, Windows (Webstart) slaves. I am not sure how long it's been going on but someone reported it to me last week, and I found this and enabled -XX:-OmitStackTraceInFastThrow and here's what our stack trace looks like: Important part seems to be: java.util.concurrent.ExecutionException: java.lang.ClassCastException: hudson.model.Fingerprint$RangeSet cannot be cast to hudson.model.Fingerprint It prints I'm guessing one or more times per artifact in the build. Here's one complete stacktrace which is the first following build success (there are probably 40-50 in our build, pages and pages, before it logs the artifact archiving) [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 28:15 min [INFO] Finished at: 2015-09-25T12:31:20-04:00 [INFO] Final Memory: 156M/1139M [INFO] ERROR: Asynchronous execution failure java.util.concurrent.ExecutionException: java.lang.ClassCastException: hudson.model.Fingerprint$RangeSet cannot be cast to hudson.model.Fingerprint at hudson.remoting.Channel$3.adapt(Channel.java:784) at hudson.remoting.Channel$3.adapt(Channel.java:779) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.maven.AbstractMavenBuilder.waitForAsynchronousExecutions(AbstractMavenBuilder.java:186) at hudson.maven.Maven3Builder.call(Maven3Builder.java:143) at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassCastException: hudson.model.Fingerprint$RangeSet cannot be cast to hudson.model.Fingerprint at hudson.model.Fingerprint.load(Fingerprint.java:1250) at hudson.model.Fingerprint.load(Fingerprint.java:1238) at hudson.model.FingerprintMap.load(FingerprintMap.java:94) at hudson.model.FingerprintMap.load(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.get(KeyedDataStorage.java:154) at hudson.model.FingerprintMap.get(FingerprintMap.java:79) at hudson.model.FingerprintMap.get(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108) at hudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65) at hudson.maven.reporters.MavenFingerprinter$1.call(MavenFingerprinter.java:125) at hudson.maven.reporters.MavenFingerprinter$1.call(MavenFingerprinter.java:112) at hudson.maven.MavenBuild$ProxyImpl.execute(MavenBuild.java:423) at hudson.maven.MavenBuild$ProxyImpl2.execute(MavenBuild.java:551) at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
[JIRA] [workflow-plugin] (JENKINS-30651) File descriptor leak when invoking for-loop
Title: Message Title
Steven Christou created an issue
Jenkins / JENKINS-30651
File descriptor leak when invoking for-loop
Issue Type:
Bug
Assignee:
Jesse Glick
Attachments:
fd.txt
Components:
workflow-plugin
Created:
25/Sep/15 6:19 PM
Priority:
Minor
Reporter:
Steven Christou
Steps to reproduce:
Create a workflow job with the following:
stage 'all'
for (int i = 0; i < ; i++) {
echo "running #${i}"
}
Expected output: "running #0" to "running #9998"
Actual output: After 7940 the build will freeze, and the System.out will show:
After upgrading to 1.7 I see the exception earlier on:
Aug 14, 2015 9:03:37 PM org.jenkinsci.plugins.workflow.graph.FlowNode$1 persist
WARNING: failed to save actions for FlowNode id=7945
java.io.IOException: Failed to create a temporary file in /space/tmp/160911/jobs/folder/jobs/wf/builds/4/work
[JIRA] [gerrit-trigger-plugin] (JENKINS-27873) Gerrit trigger to support custom labels
Title: Message Title Sam Van Oort commented on JENKINS-27873 Re: Gerrit trigger to support custom labels When this is taken on, I'd like to see Verified removed as a default label for new installs if we can, since it introduces issues with post 2.6 Gerrit As noted in the wiki and while this is Gerrit's fault for introducing a breaking change, it offers bad user experience for new Gerrit Trigger users. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Zilvinas Saltys commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module Same problem on Jenkins ver. 1.609.3 java.lang.IllegalStateException: Invalid object ID 65341 iota=65342 at hudson.remoting.ExportTable.diagnoseInvalidId(ExportTable.java:386) at hudson.remoting.ExportTable.get(ExportTable.java:330) at hudson.remoting.Channel.getExportedObject(Channel.java:630) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:599) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:583) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:542) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) at ..remote call to Mega Slave2(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1413) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:778) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:250) at com.sun.proxy.$Proxy70.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:979) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.build(Build.java:203) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1738) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:381) Caused by: java.lang.Exception: Object was recently deallocated #65341 (ref.0) : object=null type=hudson.Launcher$RemoteLaunchCallable$1 interfaces=[hudson.Launcher$RemoteProcess] Created at Fri Sep 25 13:09:11 UTC 2015 at hudson.remoting.ExportTable$Entry.(ExportTable.java:99) at hudson.remoting.ExportTable.export(ExportTable.java:305) at hudson.remoting.Channel.internalExport(Channel.java:626) at hudson.remoting.Channel.export(Channel.java:617) at hudson.remoting.Channel.export(Channel.java:587) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1138) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:1101) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Released at Fri Sep 25 13:09:11 UTC 2015 at hudson.remoting.ExportTable$Entry.release(ExportTable.java:131) at hudson.remoting.ExportTable.unexportByOid(ExportTable.java:414) at hudson.remoting.Channel.unexport(Channel.java:638) at hudson.r
[JIRA] [mstestrunner-plugin] (JENKINS-30650) testcontainer support non new line delimiter for environment variables
Title: Message Title
Jerome Godbout created an issue
Jenkins / JENKINS-30650
testcontainer support non new line delimiter for environment variables
Issue Type:
Improvement
Assignee:
Unassigned
Components:
mstestrunner-plugin
Created:
25/Sep/15 4:31 PM
Environment:
Windows 7 64 bits
Labels:
mstest environment-variables mstest-runner
Priority:
Major
Reporter:
Jerome Godbout
The inputs for /testcontainer: require new lines which is bad to set it from environment variables. Support for ; delimited string would be a nice addition.
$ {myEnvVarContainingListOfTestDLL}
=mypath1\mytest.dll;mypath2\mytest2.dll
If we could input this into the MSTest runner plugin, this could also be used in conjecture of Inject environment variables from files if you already have those available.
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Jonathan Winch commented on JENKINS-27739 Re: Changes to slave environment variables are ignored by master I have a simple job that reports the slave’s environment variable, I have run this on our production server and can confirm that the environment variable never changes unless the slave is deleted and then re added. This is being seen on LTS 1.609.1 – we know this was working in LTS 1.565.1, when we upgraded directly to 1.609.1 this issue started occurring. Using the test system I have confirmed that the issue is still reproducible in the same manner as on the live system. On the test system I have upgraded the EnvInject plugin from 1.91.3 to the latest version 1.92.1 and that did not fix it. On the test system I upgraded to the latest LTS version 1.609.3, that did not fix it. On the test system I removed the EnvInject plugin and that did not fix it. On the test system I have rolled back to 1.596.3 by replacing the Jenkins.war file, at this point the environment variable is still not being picked up correctly. On the test system I have upgraded to the latest LTS release 1.609.3 with the EnvInject plugin removed and that did not fix it. On the test system I have upgraded to the latest release 1.630 with the EnjInject plugin removed and that did not fix it. The master is an Ubuntu 12.04 64 bit vm, Jenkins has been installed from the Ubuntu package via apt, the slave used in this test is a Windows 7 x64 VM, I am configuring the slave and master + starting the builds via the latest version of Firefox. I have installed the Support Core Plugin and the support zip from this is attached. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/opt
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Jonathan Winch reopened an issue I have a simple job that reports the slave’s environment variable, I have run this on our production server and can confirm that the environment variable never changes unless the slave is deleted and then re added. This is being seen on LTS 1.609.1 – we know this was working in LTS 1.565.1, when we upgraded directly to 1.609.1 this issue started occurring. Using the test system I have confirmed that the issue is still reproducible in the same manner as on the live system. On the test system I have upgraded the EnvInject plugin from 1.91.3 to the latest version 1.92.1 and that did not fix it. On the test system I upgraded to the latest LTS version 1.609.3, that did not fix it. On the test system I removed the EnvInject plugin and that did not fix it. On the test system I have rolled back to 1.596.3 by replacing the Jenkins.war file, at this point the environment variable is still not being picked up correctly. On the test system I have upgraded to the latest LTS release 1.609.3 with the EnvInject plugin removed and that did not fix it. On the test system I have upgraded to the latest release 1.630 with the EnjInject plugin removed and that did not fix it. The master is an Ubuntu 12.04 64 bit vm, Jenkins has been installed from the Ubuntu package via apt, the slave used in this test is a Windows 7 x64 VM, I am configuring the slave and master + starting the builds via the latest version of Firefox. I have installed the Support Core Plugin and the support zip from this is attached. Jenkins / JENKINS-27739 Changes to slave environment variables are ignored by master Change By: Jonathan Winch Resolution: Fixed Status: Resolved Reopened Add Comment
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Jonathan Winch updated an issue Jenkins / JENKINS-27739 Changes to slave environment variables are ignored by master Change By: Jonathan Winch Comment: I have a simple job that reports the slave’s environment variable, I have run this on our production server and can confirm that the environment variable never changes unless the slave is deleted and then re added.This is being seen on LTS 1.609.1 – we know this was working in LTS 1.565.1, when we upgraded directly to 1.609.1 this issue started occurring.Using the test system I have confirmed that the issue is still reproducible in the same manner as on the live system. On the test system I have upgraded the EnvInject plugin from 1.91.3 to the latest version 1.92.1 and that did not fix it. On the test system I upgraded to the latest LTS version 1.609.3, that did not fix it. On the test system I removed the EnvInject plugin and that did not fix it.On the test system I have rolled back to 1.596.3 by replacing the Jenkins.war file, at this point the environment variable is still not being picked up correctly.On the test system I have upgraded to the latest LTS release 1.609.3 with the EnvInject plugin removed and that did not fix it.On the test system I have upgraded to the latest release 1.630 with the EnjInject plugin removed and that did not fix it.The master is an Ubuntu 12.04 64 bit vm, Jenkins has been installed from the Ubuntu package via apt, the slave used in this test is a Windows 7 x64 VM, I am configuring the slave and master + starting the builds via the latest version of Firefox.I have installed the Support Core Plugin and the support zip from this is attached. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master
Title: Message Title Jonathan Winch updated an issue Jenkins / JENKINS-27739 Changes to slave environment variables are ignored by master Change By: Jonathan Winch Attachment: support.zip Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title Kanstantsin Shautsou started work on JENKINS-29876 Change By: Kanstantsin Shautsou Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-setup-plugin] (JENKINS-29120) Slave Machine not reachable and offline
Title: Message Title Raju Bvs edited a comment on JENKINS-29120 Re: Slave Machine not reachable and offline I am also getting the same problem.Is there any solution for this issue??<===[JENKINS REMOTING CAPACITY]===>channel started hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running? at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:953) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Remote call on Linux - appsrv2 failed at hudson.remoting.Channel.call(Channel.java:761) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:498) at hudson.slaves.SlaveComputer.setChannel(SlaveComputer.java:371) at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:945) ... 8 more Caused by: java.lang.ClassFormatError: Failed to load hudson.slaves.SlaveComputer$SlaveVersion at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:325) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:237) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:249) at hudson.remoting.MultiClassLoaderSerializer$Input.resolveClass(MultiClassLoaderSerializer.java:113) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1589) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1494) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1748) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1327) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:349) at hudson.remoting.UserRequest.deserialize(UserRequest.java:185) at hudson.remoting.UserRequest.perform(UserRequest.java:99) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:325) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.con Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [slave-setup-plugin] (JENKINS-29120) Slave Machine not reachable and offline
Title: Message Title Raju Bvs edited a comment on JENKINS-29120 Re: Slave Machine not reachable and offline I am also getting the same problem.Is there no any solution for this issue??<===[JENKINS REMOTING CAPACITY]===>channel started hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running? at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:953) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Remote call on Linux - appsrv2 failed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-setup-plugin] (JENKINS-29120) Slave Machine not reachable and offline
Title: Message Title Raju Bvs commented on JENKINS-29120 Re: Slave Machine not reachable and offline I am also getting the same problem. Is there no solution for this issue?? <===[JENKINS REMOTING CAPACITY]===>channel started hudson.util.IOException2: Slave JVM has not reported exit code. Is it still running? at hudson.plugins.sshslaves.SSHLauncher.startSlave(SSHLauncher.java:953) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:133) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:711) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.io.IOException: Remote call on Linux - appsrv2 failed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title Kanstantsin Shautsou commented on JENKINS-29876 Re: NPE when triggering downstream job (again) As i see no, silly trigger API. Bad logic starts here https://github.com/jenkinsci/jenkins/blob/44d1d2b75fd4df1ab93ee33648ba645a0d4a3680/core/src/main/java/jenkins/triggers/ReverseBuildTrigger.java#L234-L236 i will try produce PR with test case tomorrow if nobody ban me before. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title Kanstantsin Shautsou assigned an issue to Kanstantsin Shautsou Jenkins / JENKINS-29876 NPE when triggering downstream job (again) Change By: Kanstantsin Shautsou Assignee: Kanstantsin Shautsou Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29876) NPE when triggering downstream job (again)
Title: Message Title julian Mata commented on JENKINS-29876 Re: NPE when triggering downstream job (again) Does anyone know if this issue has been resolved in 1.630? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-search-view-plugin] (JENKINS-27613) dynamic search view could not be restarted.
Title: Message Title Oleg Nenashev started work on JENKINS-27613 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-search-view-plugin] (JENKINS-27613) dynamic search view could not be restarted.
Title: Message Title Oleg Nenashev commented on JENKINS-27613 Re: dynamic search view could not be restarted. Sorry for missing the issue. Adjusted the priority. Hopefully I'll handle it on this weekend Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dynamic-search-view-plugin] (JENKINS-27613) dynamic search view could not be restarted.
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-27613 dynamic search view could not be restarted. Change By: Oleg Nenashev Priority: Major Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repo-plugin] (JENKINS-30618) Add support for repo sync --no-tags
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30618 Re: Add support for repo sync --no-tags Code changed in jenkins User: Mika Kaukoranta Path: pom.xml src/main/java/hudson/plugins/repo/TagAction.java http://jenkins-ci.org/commit/repo-plugin/2844357593257e7015aaa87af36983f4d87c595d Log: Update parent to 1.580.1 This enables @DataBoundSetter. JENKINS-30618 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repo-plugin] (JENKINS-30618) Add support for repo sync --no-tags
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30618 Add support for repo sync --no-tags Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repo-plugin] (JENKINS-30618) Add support for repo sync --no-tags
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30618 Re: Add support for repo sync --no-tags Code changed in jenkins User: Mika Kaukoranta Path: checkstyle.xml src/main/java/hudson/plugins/repo/RepoScm.java src/main/resources/hudson/plugins/repo/RepoScm/config.jelly src/main/webapp/help-noTags.html http://jenkins-ci.org/commit/repo-plugin/5bb7bd9bec9986d5e0079ca5b7c787fa910cecf8 Log: Add --no-tags repo sync option [FIXED JENKINS-30618] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [zaproxy-plugin] (JENKINS-30035) Fail the build if alerts are discovered
Title: Message Title Dave Hunt commented on JENKINS-30035 Re: Fail the build if alerts are discovered The Context Alert Filters add-on should allow for per job configuration, however the Jenkins plugin would need to be enhanced to support automatic installation of add-ons. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-plugin] (JENKINS-30642) GitHub Enterprise private mode push hooks don't trigger a build
Title: Message Title Tyler Smith commented on JENKINS-30642 Re: GitHub Enterprise private mode push hooks don't trigger a build Thanks for the help. I don't control the Jenkins master server so I requested the upgrade. Thanks for being willing to point me in the right direction. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-30525) P4 plugin doesn't detect failure and can then cause other plugins to fail
Title: Message Title Morne Joubert commented on JENKINS-30525 Re: P4 plugin doesn't detect failure and can then cause other plugins to fail maybe we should first get the info for a change and then unshelve it. if we can't get the info then we don't unshelve ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-30525) P4 plugin doesn't detect failure and can then cause other plugins to fail
Title: Message Title Paul Allen commented on JENKINS-30525 Re: P4 plugin doesn't detect failure and can then cause other plugins to fail The recent fix should abort if there are any issues during the unshelve process (i.e. shelf is submitted or on a different stream). What was puzzling is why can a build unshelve ok then at a later step fail to access the change. The only thing I can think of is the change was submitted or deleted part way through the build. That is why I need to add the extra checks. There is a 'p4 change -O' which looks up old changes (using the original number), that could work for the submit case, but not delete. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-29595) Build-flow project not sending mail notification
Title: Message Title Lucie Votypkova commented on JENKINS-29595 Re: Build-flow project not sending mail notification I agree with Oliver. After update, jobs with post build steps stopped working and it took some time to realize it - because build did not fail. User should be at least warned because there is no sense to have post-build steps without "Flow run needs a workspace". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emma-plugin] (JENKINS-30648) Disabling Emma Code Coverage plugin
Title: Message Title Karnajit Sen assigned an issue to Unassigned Jenkins / JENKINS-30648 Disabling Emma Code Coverage plugin Change By: Karnajit Sen Assignee: Karnajit Sen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-30649) Test Result trend view is getting truncated
Title: Message Title Karnajit Sen closed an issue as Fixed Sorry wrong observation. Closing this Jenkins / JENKINS-30649 Test Result trend view is getting truncated Change By: Karnajit Sen Status: Open Closed Assignee: Varun Menon Karnajit Sen Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emma-plugin] (JENKINS-30648) Disabling Emma Code Coverage plugin
Title: Message Title Karnajit Sen assigned an issue to Karnajit Sen Jenkins / JENKINS-30648 Disabling Emma Code Coverage plugin Change By: Karnajit Sen Assignee: Kohsuke Kawaguchi Karnajit Sen Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-30548) Post build step not removed from generated Maven job
Title: Message Title
Yoann Dubreuil commented on JENKINS-30548
Re: Post build step not removed from generated Maven job
I found another workaround which seems to work all time. Instead of using a empty postBuildSteps, you can force Job DSL to generate the empty XML node with
configure { it / 'postbuilders' }
Not really nice, but it works!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-30649) Test Result trend view is getting truncated
Title: Message Title Karnajit Sen created an issue Jenkins / JENKINS-30649 Test Result trend view is getting truncated Issue Type: Improvement Assignee: Varun Menon Components: test-results-analyzer-plugin Created: 25/Sep/15 12:58 PM Priority: Minor Reporter: Karnajit Sen Hi, My Test result trend view is getting truncated in the top if the number of test cases is high e.g, 40. Please suggest. Thanks! Add Comment
[JIRA] [build-failure-analyzer-plugin] (JENKINS-30643) Checkbox "Enable statistics logging of successful build" won't get applied when "Enable Statistics logging" doesn't change
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30643 Re: Checkbox "Enable statistics logging of successful build" won't get applied when "Enable Statistics logging" doesn't change Code changed in jenkins User: Robert Sandell Path: src/main/java/com/sonyericsson/jenkins/plugins/bfa/db/MongoDBKnowledgeBase.java http://jenkins-ci.org/commit/build-failure-analyzer-plugin/3295e3e6a49e3616944509fcd9827c9bfa15bff9 Log: Merge pull request #38 from Jochen-A-Fuerbacher/hotfixEqualsInMongoDbKnowledgeBase JENKINS-30643 Hotfix for MongoDB statistics configuration. Compare: https://github.com/jenkinsci/build-failure-analyzer-plugin/compare/ef95fae3d54c...3295e3e6a49e Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [emma-plugin] (JENKINS-30648) Disabling Emma Code Coverage plugin
Title: Message Title Karnajit Sen created an issue Jenkins / JENKINS-30648 Disabling Emma Code Coverage plugin Issue Type: Task Assignee: Kohsuke Kawaguchi Components: emma-plugin, mstest-plugin Created: 25/Sep/15 12:54 PM Priority: Blocker Reporter: Karnajit Sen Hi, Emma plugin is prerequisite for MStest plug in. But I do not need a code coverage trend. How can I disable code coverage trend view even though the emma plugin is installed. Thanks Add Comment
[JIRA] [p4-plugin] (JENKINS-30525) P4 plugin doesn't detect failure and can then cause other plugins to fail
Title: Message Title Morne Joubert commented on JENKINS-30525 Re: P4 plugin doesn't detect failure and can then cause other plugins to fail something that might be relevant is that you cannot unshelve any cl on any stream. e.g. if i shelve on a dev stream then i cannot unshelve on a main (i need a branchspec for this) So we need to check that the CL is a valid CL for the stream as well Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30644) Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin
Title: Message Title Daniel Beck commented on JENKINS-30644 Re: Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin Related PR: https://github.com/jenkinsci/jenkins/pull/1573 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-30647) Support expanding environment variables
Title: Message Title Bartosz Kaczorek updated an issue Jenkins / JENKINS-30647 Support expanding environment variables Change By: Bartosz Kaczorek Summary: Expand Support expanding environment variables Issue Type: New Feature Improvement Add support for expanding of environment variables - when injecting variables to build process using "inject environment variables to build process" option I'd like to be able to use them in "Cobertura xml report pattern" field i.e.: $PROJECT_HOME/target/cobertura-coverage.xml. This feature is supported by most of other report plugins (i.e. JUnit reporter plugin). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-30647) Support expanding environment variables
Title: Message Title Bartosz Kaczorek updated an issue Jenkins / JENKINS-30647 Support expanding environment variables Change By: Bartosz Kaczorek Labels: cobertura jenkins Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-30647) Expand environment variables
Title: Message Title Bartosz Kaczorek created an issue Jenkins / JENKINS-30647 Expand environment variables Issue Type: New Feature Assignee: stephenconnolly Components: cobertura-plugin Created: 25/Sep/15 11:37 AM Environment: Jenkins ver. 1.613 Jenkins Cobertura Plugin 1.9.7 Priority: Minor Reporter: Bartosz Kaczorek Add expanding of environment variables - when injecting variables to build process using "inject environment variables to build process" option I'd like to be able to use them in "Cobertura xml report pattern" field i.e.: $PROJECT_HOME/target/cobertura-coverage.xml. This feature is supported by most of other report plugins (i.e. JUnit reporter plugin). Add Comment
[JIRA] [core] (JENKINS-30644) Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin
Title: Message Title Daniel Beck resolved as Duplicate Duplicates JENKINS-23150, JENKINS-21486, JENKINS-21485. Please search for existing reports before filing obvious long-standing bugs. Jenkins / JENKINS-30644 Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin Change By: Daniel Beck Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-30525) P4 plugin doesn't detect failure and can then cause other plugins to fail
Title: Message Title Paul Allen commented on JENKINS-30525 Re: P4 plugin doesn't detect failure and can then cause other plugins to fail Looks like I need to expand the checking to other commands Seems interesting that the change exists at the unshelve stage... P4 Task: unshelve review: 144856 ... p4 unshelve -f -s144856 -cdefault but then is missing at the post build stage... P4 Task: saving built changes. ... p4 client -o __atf_int_mlb_0_jenkins_p4_2_mlb-TEST-gb-mlb-dt-019 + ... p4 change -o 144856 + Unable to get changes: com.perforce.p4java.exception.RequestException: Change 144856 unknown. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-30646) Bad handling of relative paths
Title: Message Title
Bartosz Kaczorek updated an issue
Jenkins / JENKINS-30646
Bad handling of relative paths
Change By:
Bartosz Kaczorek
The issue happens when trying to publish cobertura-coverage.xml report with relative paths i.e.:{code:xml}... C:\Users\myUser\.jenkins\workspace\SomeWorkspaceName\SomeProject\aaa\bbb\ccc\ddd.{code}It's causing below errors:{code:java}16:33:58 ERROR: ERROR: Failure to paint C:\Users\myUser\.jenkins\workspace\SomeWorkspaceName\SomeProject\aaa\bbb\ccc\ddd\..\..\..\..\..\SomeProject\xxx\yyy\SomeFile.js to C:\Users\myUser\.jenkins\jobs\SomeWorkspaceName\cobertura16:33:58 java.io.IOException: Failed to mkdirs: C:\Users\SomeProject\xxx\yyy16:33:58 at hudson.FilePath.mkdirs(FilePath.java:1164)16:33:58 at hudson.plugins.cobertura.renderers.SourceCodePainter.paintSourceCode(SourceCodePainter.java:62)16:33:58 at hudson.plugins.cobertura.renderers.SourceCodePainter.invoke(SourceCodePainter.java:135)16:33:58 at hudson.plugins.cobertura.renderers.SourceCodePainter.invoke(SourceCodePainter.java:30)16:33:58 at hudson.FilePath.act(FilePath.java:991)16:33:58 at hudson.FilePath.act(FilePath.java:969)16:33:58 at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:403)16:33:58 at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)16:33:58 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)16:33:58 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:726)16:33:58 at hudson.model.Build$BuildExecution.post2(Build.java:185)16:33:58 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:671)16:33:58 at hudson.model.Run.execute(Run.java:1769)16:33:58 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)16:33:58 at hudson.model.ResourceController.execute(ResourceController.java:98)16:33:58 at hudson.model.Executor.run(Executor.java:374){code} See also related issue on intern github page: [https://github.com/theintern/intern/issues/504]
Add Comment
[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-21785 Re: Check for changes in folders linked via svn:externals fails due to missing credentials dan russell If you have ideas to improve this, it would be helpful if you send an email (dev mailing list) with your proposal. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cobertura-plugin] (JENKINS-30646) Bad handling of relative paths
Title: Message Title Bartosz Kaczorek created an issue Jenkins / JENKINS-30646 Bad handling of relative paths Issue Type: Bug Assignee: stephenconnolly Components: cobertura-plugin Created: 25/Sep/15 10:55 AM Environment: Windows 7 64 bit Jenkins ver. 1.613 Jenkins Cobertura Plugin 1.9.7 Java 1.8.0_45-b15 Priority: Major Reporter: Bartosz Kaczorek The issue happens when trying to publish cobertura-coverage.xml report with relative paths i.e.: ... C:\Users\myUser\.jenkins\workspace\SomeWorkspaceName\SomeProject\aaa\bbb\ccc\ddd ... ... "SomeFile.js" filename="..\..\..\..\..\SomeProject\xxx\yyy\SomeFile.js /> ... It's causing below errors: 16:33:58 ERROR: ERROR: Failure to paint C:\Users\myUser\.jenkins\workspace\SomeWorkspaceName\SomeProject\aaa\bbb\ccc\ddd\..\..\..\..\..\SomeProject\xxx\yyy\SomeFile.js to C:\Users\myUser\.jenkins\jobs\SomeWorkspaceName\cobertura 16:33:58 java.io.IOException: Failed to mkdirs: C:\Users\SomeProject\xxx\yyy 16:33:58
[JIRA] [cobertura-plugin] (JENKINS-30646) Bad handling of relative paths
Title: Message Title Bartosz Kaczorek updated an issue Jenkins / JENKINS-30646 Bad handling of relative paths Change By: Bartosz Kaczorek Labels: cobertura jenkins Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Title: Message Title dan russell edited a comment on JENKINS-21785 Re: Check for changes in folders linked via svn:externals fails due to missing credentials Seems a pretty clunky fix to have to put credentials in for each job that requires externals, shouldn't the plugin at least try the given credentials before failing? Also does anybody know why this is only an intermittent failure? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials
Title: Message Title dan russell commented on JENKINS-21785 Re: Check for changes in folders linked via svn:externals fails due to missing credentials Seems a pretty clunky fix to have to put credentials in for each job that requires externals, shouldn't the plugin at least try the given credentials before failing? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rtc-plugin] (JENKINS-30645) Version 1.1.9.5 of rtc-plugins does not use previously configured "Build Definition"
Title: Message Title Lucas Martins do Amaral created an issue Jenkins / JENKINS-30645 Version 1.1.9.5 of rtc-plugins does not use previously configured "Build Definition" Issue Type: Bug Assignee: Deluan Quintão Components: rtc-plugin Created: 25/Sep/15 10:14 AM Environment: Jenkins 1.628 rtc-plugin 1.1.9.5 Labels: plugin Priority: Critical Reporter: Lucas Martins do Amaral Version 1.1.9.5 of rtc-plugin disconsider selected "Use a build definition for better RTC integration" of jobs already configured, causing the following error: RTC : checkout... FATAL: RTC : checkout failure: More than 1 repository workspace has the name "null" FATAL: RTC : checkout failure: RTC : checkout failure: More than 1 repository workspace has the name "null" hudson.AbortException: RTC : checkout failure: More than 1 repository workspace has the name "null" at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:198) at com.ibm.team.build.internal.hjplugin.RTCCheckoutTask.invoke(RTCCheckoutTask.java:31)
[JIRA] [p4-plugin] (JENKINS-30525) P4 plugin doesn't detect failure and can then cause other plugins to fail
Title: Message Title Morne Joubert commented on JENKINS-30525 Re: P4 plugin doesn't detect failure and can then cause other plugins to fail Problem is still there. P4 Task: unshelve review: 144856 ... p4 unshelve -f -s144856 -cdefault + ... p4 revert -k c:\jenkins\workspace__atf_int_mlb_0/... + ... duration: (29ms) P4 Task: saving built changes. ... p4 client -o __atf_int_mlb_0_jenkins_p4_2_mlb-TEST-gb-mlb-dt-019 + ... p4 change -o 144856 + Unable to get changes: com.perforce.p4java.exception.RequestException: Change 144856 unknown. ... p4 client -o __atf_int_mlb_0_jenkins_p4_2_mlb-TEST-gb-mlb-dt-019 + ... p4 change -o 144856 + Unable to get changes: com.perforce.p4java.exception.RequestException: Change 144856 unknown. ... done if p4 change fails then it needs to fail the job Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30644) Jenkins should manage better the plugin dependencies when disable/uninstall a plugin
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-30644 Jenkins should manage better the plugin dependencies when disable/uninstall a plugin Issue Type: Bug Assignee: Unassigned Components: core Created: 25/Sep/15 8:47 AM Priority: Major Reporter: Félix Belzunce Arcos If you disable a plugin which has a hard dependency with another plugin, Jenkins doesn't report anything or suggest you to disable/delete the dependencies. At the end, you can end up with stacktraces like: WARNING: Failed to scout com.cloudbees.opscenter.client.plugin.ClusterSessionClientExtensionHandler java.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/plugins/openid/OpenIdExtension at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:354) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.iterator(ExtensionList.java:143) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.size(ExtensionList.java:162) at java.util.AbstractCollection.toArray(AbstractCollection.java:136) at java.util.ArrayList.addAll(ArrayList.java:559) at
[JIRA] [core] (JENKINS-30644) Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-30644 Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin Change By: Félix Belzunce Arcos Summary: Jenkins should manage better the plugin dependencies when disable disabling / uninstall uninstalling a plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-30644) Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin
Title: Message Title
Félix Belzunce Arcos updated an issue
Jenkins / JENKINS-30644
Jenkins should manage better the plugin dependencies when disabling/uninstalling a plugin
Change By:
Félix Belzunce Arcos
If you disable a plugin which has a hard dependency with another plugin, Jenkins doesn't report anything or suggest you to disable/delete the dependencies. At the end, you can end up with stacktraces like:{code:java}WARNING: Failed to scout com.cloudbees.opscenter.client.plugin.ClusterSessionClientExtensionHandler java.lang.InstantiationException: java.lang.NoClassDefFoundError: hudson/plugins/openid/OpenIdExtension at net.java.sezpoz.IndexItem.element(IndexItem.java:146) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:666) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:354) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.iterator(ExtensionList.java:143) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:353) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.size(ExtensionList.java:162) at java.util.AbstractCollection.toArray(AbstractCollection.java:136) at java.util.ArrayList.addAll(ArrayList.java:559) at {code}Jenkins should not allow you to disable a plugin when there is such kind of dependency. It should instead maybe give you also the tree of dependencies so you can uninstall all of them if you want.A Warning can be also an option saying that it is not possible to remove/disable because there is a dependency with another plugin. I don ; ' t like too much this option because you end up with a lot of manual work.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [doxygen-plugin] (JENKINS-29938) Unable to serialize is reported when publishing doxygen generate html files
Title: Message Title Sebastian Troy commented on JENKINS-29938 Re: Unable to serialize is reported when publishing doxygen generate html files It would seem that Gregory Boissinot has about 40 bugs assigned to him, all marked as Open and Unresolved (none in progress) his Git account also suggests that he hasn't contributed to a Jenkins branch since last year, correct me if I'm wrong, but it doesn't look like a fix is coming any time soon from him! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-30643) Checkbox "Enable statistics logging of successful build" won't get applied when "Enable Statistics logging" doesn't change
Title: Message Title Jochen A. Fürbacher updated an issue Jenkins / JENKINS-30643 Checkbox "Enable statistics logging of successful build" won't get applied when "Enable Statistics logging" doesn't change Change By: Jochen A. Fürbacher In global configuration when using Mongo DB as storage type, the checkbox "Enable statistics logging of successful builds" only gets saved, when the status of "Enable Statistics logging" gets also changed.E.g.:Enable Statistics logging: trueEnable statistics logging of successful build: falseWhen you check "Enable statistics logging of successful build" and apply it, it won't get saved. It's still disabled.But when you uncheck "Enable Statistics logging" AND check "Enable statistics logging of successful build", then both get saved correctly.I created a pull reguest with a hotfix for this: https://github.com/jenkinsci/build-failure-analyzer-plugin/pull/38 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-30643) Checkbox "Enable statistics logging of successful build" won't get applied when "Enable Statistics logging" doesn't change
Title: Message Title Jochen A. Fürbacher created an issue Jenkins / JENKINS-30643 Checkbox "Enable statistics logging of successful build" won't get applied when "Enable Statistics logging" doesn't change Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 25/Sep/15 8:17 AM Priority: Major Reporter: Jochen A. Fürbacher In global configuration when using Mongo DB as storage type, the checkbox "Enable statistics logging of successful builds" only gets saved, when the status of "Enable Statistics logging" gets also changed. E.g.: Enable Statistics logging: true Enable statistics logging of successful build: false When you check "Enable statistics logging of successful build" and apply it, it won't get saved. It's still disabled. But when you uncheck "Enable Statistics logging" AND check "Enable statistics logging of successful build", then both get saved correctly. I created a pull reguest with a hotfix for this:
[JIRA] [xfpanel-plugin] (JENKINS-14873) NPE after upgrade
Title: Message Title Tomasz Bech closed an issue as Won't Fix That was issue with upgrade for an old version of plugin - in release not it was even stated that after ugrade you have to reconfigure jobs. Closing with won't fix. Jenkins / JENKINS-14873 NPE after upgrade Change By: Tomasz Bech Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Daniel Spilker commented on JENKINS-21750 Re: Promoted Builds Plugin Dennis Schulte OK, but no one objected to add Groovy code in your last dev list thread (https://groups.google.com/forum/#!msg/jenkinsci-dev/IZ3kBFhIYYg/amywuitlHAAJ). I suggest to open a pull request. If no one replied after 2 weeks, ask for commit access on the jenkins-dev list. If you get commit access, integrate your Groovy code into the Promoted Builds Plugin and release the plugin. If not, we need to discuss a viable solution with the maintainer. IMHO, releasing a plugin outside of the Update Center is only a short-term solution. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Dennis Schulte commented on JENKINS-21750 Re: Promoted Builds Plugin Steve Jansen We are actually testing the Extension in a big Jenkins setup with version 1.630. If this works, I'll create a release of it... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Dennis Schulte commented on JENKINS-21750 Re: Promoted Builds Plugin Daniel Spilker Yes, I created a ticket, but no response: https://issues.jenkins-ci.org/browse/JENKINS-29776 The problem with option #3 is that we have to add Groovy to the codebase of the plugin, which will maybe not accepted by the maintainers of the Promoted Builds plugin... Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-21750) Promoted Builds Plugin
Title: Message Title Daniel Spilker commented on JENKINS-21750 Re: Promoted Builds Plugin What about option #3, integrating the extension into the Promoted Builds Plugin? Dennis Schulte have you contacted the Promoted Build Plugin maintainer(s)? If you get no answer, ask for commit access on the jenkins-dev list and just do it. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
