[JIRA] [custom-tools] (JENKINS-18774) Add setup of label-specific variables after installation
Oleg Nenashev updated JENKINS-18774 Add setup of label-specific variables after installation Change By: Oleg Nenashev (27/Jul/13 8:03 AM) Summary: Add setup of additional label-specific variables after installation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17680) Upgrade to new Copy Artifacts version erases all job names to copy from
ikedam commented on JENKINS-17680 Upgrade to new Copy Artifacts version erases all job names to copy from Send a pull request: https://github.com/jenkinsci/copyartifact-plugin/pull/23 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-18962) rework disk-usage plugin
Kanstantsin Shautsou
updated JENKINS-18962
rework disk-usage plugin
Change By:
Kanstantsin Shautsou
(27/Jul/13 9:33 AM)
Description:
I think this plugin should change it's logic/architecture.* If we need disk size calculation feature for specific job, then we accept performance/time degradation in job.* when background thread could affect other building job (correct if i mistaken)So i think that plugin should: 1. have ability enable/disable disk calculation feature per jobs (for example if i do chrooted build calculation will fail, btw because of thread calculator errors i got offline slave).2.
it should
run calculation as a build step (optionally probably background thread could be kept like ("calculate later").3.
create
have
ability to disable background thread.4. In future this could be base for some configurable quotas for job sizes (linux specific).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-18962) rework disk-usage plugin
Kanstantsin Shautsou
created JENKINS-18962
rework disk-usage plugin
Issue Type:
Improvement
Assignee:
vjuranek
Components:
disk-usage
Created:
27/Jul/13 9:32 AM
Description:
I think this plugin should change it's logic/architecture.
If we need disk size calculation feature for specific job, then we accept performance/time degradation in job.
when background thread could affect other building job (correct if i mistaken)
So i think that plugin should:
1. have ability enable/disable disk calculation feature per jobs (for example if i do chrooted build calculation will fail, btw because of thread calculator errors i got offline slave).
2. it should run calculation as a build step (optionally probably background thread could be kept like ("calculate later").
3. create ability to disable background thread.
4. In future this could be base for some configurable quotas for job sizes (linux specific).
Project:
Jenkins
Labels:
plugin
Priority:
Major
Reporter:
Kanstantsin Shautsou
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
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/groups/opt_out.
[JIRA] [git] (JENKINS-18963) Add SourceForge Repository Viewer
Chris T created JENKINS-18963 Add SourceForge Repository Viewer Issue Type: Improvement Affects Versions: current Assignee: Nicolas De Loof Components: git, plugin Created: 27/Jul/13 10:57 AM Description: Since the last major Forge upgrade SF (SourceForge.net) stopped using GitWeb and only provides a repository lookup via their built in repository viewer. It would be awesome if this repository viewer could be referenced by the git plugin. Right now I only see an unlinked revision number when Jenkins checks out some changeswhich is not very helpfull at all. Project: Jenkins Labels: git plugin readlink Priority: Minor Reporter: Chris T This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel This happens across all our slaves, windows, redhat, ubuntu. We have a little bit more than 100 jobs, and we keep logs for the last 10 runs of each job. Over the last 10 runs, we've seen this 14 times on Windows, 26 times on the other platforms. Everything runs over SSH (cygwin on windows) with the default settings: TCPKeepAlive: yes ClientAliveCountMax: 3 ClientAliveInterval: 0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn edited a comment on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel This happens across all our slaves, windows, redhat, ubuntu. We have a little bit more than 100 jobs, and we keep logs for the last 10 runs of each job. Over the last 10 runs, we've seen this 14 times on Windows, 26 times on the other platforms. Everything runs over SSH (cygwin on windows) with the default settings: TCPKeepAlive: yes ClientAliveCountMax: 3 ClientAliveInterval: 0 It doesn't look related to the output - this fails randomly in different steps, some with no output for minutes, some with no output for only a few seconds This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-15797) Upgradefrom 1.424 to 1.489 : API incompatibility AbstractHttpClientWagon.getReadTimeout()
Robert Reiz commented on JENKINS-15797 Upgradefrom 1.424 to 1.489 : API incompatibility AbstractHttpClientWagon.getReadTimeout() I got the same Exception with Maven 3.0.3. But after I updated to Maven 3.0.5 this error disappeared. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-17606) Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied
Martin d'Anjou commented on JENKINS-17606 Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied This may not be blocking, but in very large teams, having to explain this does not help me build trust in the Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel I added a print every ten seconds, still happens: ( 2013-29-27 17:29:07 running ) ( 2013-29-27 17:29:17 running ) ( 2013-29-27 17:29:27 running ) ( 2013-29-27 17:29:37 running ) ( 2013-29-27 17:29:47 running ) ( 2013-29-27 17:29:57 running ) ( 2013-30-27 17:30:07 running ) FATAL: Unable to delete script file C:\Users\Administrator\hudson7142602309142296785.py hudson.util.IOException2: remote file operation failed: C:\Users\Administrator\hudson7142602309142296785.py at hudson.remoting.Channel@6e47e0a6:host-ci38 at hudson.FilePath.act(FilePath.java:901) at hudson.FilePath.act(FilePath.java:878) at hudson.FilePath.delete(FilePath.java:1263) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:101) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.plugins.templateproject.ProxyBuilder.perform(ProxyBuilder.java:87) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Caused by: hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:524) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:722) at hudson.FilePath.act(FilePath.java:894) ... 14 more Caused by: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Channel$CloseCommand.execute(Channel.java:900) at hudson.remoting.Channel$2.handle(Channel.java:465) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: Command close created at at hudson.remoting.Command.(Command.java:56) at hudson.remoting.Channel$CloseCommand.(Channel.java:894) at hudson.remoting.Channel$CloseCommand.(Channel.java:892) at hudson.remoting.Channel.close(Channel.java:975) at hudson.remoting.Channel.close(Channel.java:958) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:899) ... 2 more FATAL: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:162) at sun.proxy.$Proxy38.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:915) at hudson.Launcher$ProcStarter.join(Launcher.java:360) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:91) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.plugins.templateproject.ProxyBuilder.perform(ProxyBuilder.java:87) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586) at hudson.model.Run.execute(Run.java:1593) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:242) Caused by: hudson.remoting.RequestAbortedException: hudson.remoting.Channel$OrderlyShutdown at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.Channel$CloseCommand.execute(Channel.java:900) at hudson.remoting.Channel$2.handle(Channel.java:465) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Caused by: hudson.remoting.Channel$OrderlyShutdown ... 3 more Caused by: Command close created at at hudson.remoting.Command.(Command.ja
[JIRA] [copyartifact] (JENKINS-17606) Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied
kutzi commented on JENKINS-17606 Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied I've you think that a change to Jenkins' core Fingerprinter would fix the issue, feel free to create a pull request with a fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Marc Seeger commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We started printing "tweet" every minute or so, still happened. Since we took down the numbers of executors on the master (aws m1.large) to 2 and upsized the slave, I haven't seen another crash. (not that long of a timespan though) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18956) Cache location should be configurable through the GUI
Daniel Beck edited a comment on JENKINS-18956 Cache location should be configurable through the GUI Edit the Suffix Start Slave Command under Advanced and specify e.g. -jar-cache /path/to/jars (with a leading space). Not a convenient button to click, but gets the job done. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-18956) Cache location should be configurable through the GUI
Daniel Beck commented on JENKINS-18956 Cache location should be configurable through the GUI Edit the Suffix Start Slave Command under Advanced and specify e.g. -jar-cache /Users/danielbeck/jars (with a leading space). Not a convenient button to click, but gets the job done. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [msbuild] (JENKINS-18543) Update to newest MSBuild plugin breaks passing of release configurations with spaces in them
SCM/JIRA link daemon resolved JENKINS-18543 as Fixed Update to newest MSBuild plugin breaks passing of release configurations with spaces in them Change By: SCM/JIRA link daemon (27/Jul/13 7:55 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [msbuild] (JENKINS-18543) Update to newest MSBuild plugin breaks passing of release configurations with spaces in them
SCM/JIRA link daemon commented on JENKINS-18543 Update to newest MSBuild plugin breaks passing of release configurations with spaces in them Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java src/test/java/hudson/plugins/msbuild/MsBuildBuilderTest.java http://jenkins-ci.org/commit/msbuild-plugin/07f777ed18603bc8e66c3eb0e3c9523c1a9ed784 Log: Merge pull request #8 from tyrius02/master [FIXED JENKINS-18543] Revert break from commit 11525049ed173f941d6ec6e87... Compare: https://github.com/jenkinsci/msbuild-plugin/compare/6bd00887edd5...07f777ed1860 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [msbuild] (JENKINS-18543) Update to newest MSBuild plugin breaks passing of release configurations with spaces in them
SCM/JIRA link daemon commented on JENKINS-18543 Update to newest MSBuild plugin breaks passing of release configurations with spaces in them Code changed in jenkins User: jzimmerman Path: src/main/java/hudson/plugins/msbuild/MsBuildBuilder.java src/test/java/hudson/plugins/msbuild/MsBuildBuilderTest.java http://jenkins-ci.org/commit/msbuild-plugin/ed6d6d97884a395b7c149d0a773eab6bc76af753 Log: [FIXED JENKINS-18543] Revert break from commit 11525049ed173f941d6ec6e87694269ef40d9920 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-14613) Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository'
evernat commented on JENKINS-14613 Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository' reproduced with Jenkins 1.524 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [maven] (JENKINS-14613) Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository'
evernat updated JENKINS-14613 Maven job config page loses 'invoke top-level maven targets' setting for 'use private repository' Change By: evernat (27/Jul/13 8:44 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [buildresult-trigger] (JENKINS-18931) Build is triggered incorrectly when a triggered build starts running
SCM/JIRA link daemon resolved JENKINS-18931 as Fixed Build is triggered incorrectly when a triggered build starts running Change By: SCM/JIRA link daemon (27/Jul/13 8:49 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [buildresult-trigger] (JENKINS-18931) Build is triggered incorrectly when a triggered build starts running
SCM/JIRA link daemon commented on JENKINS-18931 Build is triggered incorrectly when a triggered build starts running Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger.java http://jenkins-ci.org/commit/buildresult-trigger-plugin/f3f5fab993d404e2b18f32e8af1f2ad35981f771 Log: Merge pull request #6 from jtnord/JENKINS-18931 Fixes Jenkins-18931 Compare: https://github.com/jenkinsci/buildresult-trigger-plugin/compare/12f65d79ac7b...f3f5fab993d4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [buildresult-trigger] (JENKINS-18931) Build is triggered incorrectly when a triggered build starts running
SCM/JIRA link daemon commented on JENKINS-18931 Build is triggered incorrectly when a triggered build starts running Code changed in jenkins User: James Nord Path: src/main/java/org/jenkinsci/plugins/buildresulttrigger/BuildResultTrigger.java http://jenkins-ci.org/commit/buildresult-trigger-plugin/6aac32a245eae1c2800d88a17033ff70c2df2b7a Log: [FIXED JENKINS-18931] Build is triggered incorrectly when a triggered build starts running. Context should be calculated against a completed build not an in progress one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18964) Clone Workspace SCM should be supported by job-dsl
wolfs updated JENKINS-18964 Clone Workspace SCM should be supported by job-dsl Change By: wolfs (27/Jul/13 8:52 PM) Issue Type: Bug New Feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-18964) Clone Workspace SCM should be supported by job-dsl
wolfs created JENKINS-18964 Clone Workspace SCM should be supported by job-dsl Issue Type: Bug Assignee: Justin Ryan Components: job-dsl-plugin Created: 27/Jul/13 8:51 PM Description: The Clone Workspace Publisher is already supported by the dsl. But the corresponding SCM should also be supported. Project: Jenkins Priority: Minor Reporter: wolfs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Although our master node has 10 executors, this happens when there's a single job running all over the jenkins instance, and its running (and failing) on a different slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Guy Rozendorn edited a comment on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel Although our master node has 10 executors (left for tied jobs only), this happens when there's a single job running all over the jenkins instance, and its running (and failing) on a different slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [postbuildscript] (JENKINS-11219) Add the option to run the script after all the sub elements of a matrix project build have finished
Kalps sat commented on JENKINS-11219 Add the option to run the script after all the sub elements of a matrix project build have finished My use case is to run a script from master head(reset/restart the slave) after each axe/node execution completed. Is it possible? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-14144) Build config history getting spammed
SCM/JIRA link daemon commented on JENKINS-14144 Build config history getting spammed Code changed in jenkins User: Nicolas De Loof Path: pom.xml src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java src/main/java/org/jenkinsci/plugins/envinject/service/BuildWrapperService.java http://jenkins-ci.org/commit/envinject-plugin/a9be296cb4a2293b6123addacaeb629b8ba99ae1 Log: JENKINS-14144 use a WorkspaceListener to avoid injecting a temporary BuildWrapper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-14144) Build config history getting spammed
SCM/JIRA link daemon commented on JENKINS-14144 Build config history getting spammed Code changed in jenkins User: Gregory Boissinot Path: pom.xml src/main/java/org/jenkinsci/plugins/envinject/EnvInjectListener.java src/main/java/org/jenkinsci/plugins/envinject/service/BuildWrapperService.java http://jenkins-ci.org/commit/envinject-plugin/dd3834c83ecf6f0c3310ae492893bd63c46d927e Log: Merge pull request #18 from ndeloof/JENKINS-14144-alt [FIXED JENKINS-14144] use a WorkspaceListener to avoid injecting a temporary BuildWrapper Compare: https://github.com/jenkinsci/envinject-plugin/compare/96a526963b53...dd3834c83ecf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [envinject] (JENKINS-14144) Build config history getting spammed
SCM/JIRA link daemon resolved JENKINS-14144 as Fixed Build config history getting spammed Change By: SCM/JIRA link daemon (27/Jul/13 10:01 PM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [git] (JENKINS-18960) Clone of 2.5 GB git repository is dramatically slower with jgit than command line git
Mark Waite updated JENKINS-18960 Clone of 2.5 GB git repository is dramatically slower with jgit than command line git Change By: Mark Waite (27/Jul/13 10:39 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-18965) forgot to give access permission to default user
Mohsin Khan created JENKINS-18965 forgot to give access permission to default user Issue Type: Bug Affects Versions: current Assignee: Mohsin Khan Components: jenkins-tracker Created: 28/Jul/13 3:24 AM Due Date: 29/Jul/13 12:00 AM Environment: Ubuntu 12.04 Fix Versions: current Project: Jenkins Priority: Critical Reporter: Mohsin Khan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-18965) forgot to give access permission to default user
Mohsin Khan commented on JENKINS-18965 forgot to give access permission to default user hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission at hudson.security.ACL.checkPermission(ACL.java:54) at hudson.model.Node.checkPermission(Node.java:412) at jenkins.model.Jenkins.getTarget(Jenkins.java:3655) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:611) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:777) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:586) at org.kohsuke.stapler.Stapler.service(Stapler.java:217) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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/groups/opt_out.
