date:20120404


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ulli Hafner resolved JENKINS-13340.
---

Resolution: Not A Defect

That is the intended behavior. The link to the details page is only shown if 
there are warnings found. What would you like to show on that page?

 Compiler Warnings menu item gone when no compiler warnings
 --

 Key: JENKINS-13340
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13340
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Affects Versions: current
 Environment: compiler warnings version 3.28
 jenkins version 1.458
Reporter: Markus Hjerto
Assignee: Ulli Hafner
Priority: Minor

 When we've finally been able to remove all the compiler warnings in a 
 project, then the compiler warnings menu item in the left menu column 
 disappear. It is also not present in the new hover menus introduced in 
 Jenkins not that long ago. I can access it from clicking on the build. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13340) Compiler Warnings menu item gone when no compiler warnings

2012-04-04 Thread m...@nordicsemi.no (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161215#comment-161215
]

Markus Hjerto commented on JENKINS-13340:
-

I would expect a list as normal where the Fixed warnings field contains the
number of warnings that was fixed. I could click that number and get more
information about the warnings. This is still relevant even if we have no
warnings anymore. Today I can access that page by simply adding /warningsResult
to the URL, even if the menu is not there. I think the main problem is that it
confused me that the menu was gone. I was afraid that the warning had stopped
working or something.

In the end this is probably a preference decision, so I'll leave it up to you
to decide. You may know much more about a user-friendly UIs than I do.

Great plugin, by the way!

Compiler Warnings menu item gone when no compiler warnings
--

Key: JENKINS-13340
URL: https://issues.jenkins-ci.org/browse/JENKINS-13340
Project: Jenkins
Issue Type: Bug
Components: warnings
Affects Versions: current
Environment: compiler warnings version 3.28
jenkins version 1.458
Reporter: Markus Hjerto
Assignee: Ulli Hafner
Priority: Minor

When we've finally been able to remove all the compiler warnings in a
project, then the compiler warnings menu item in the left menu column
disappear. It is also not present in the new hover menus introduced in
Jenkins not that long ago. I can access it from clicking on the build.

[JIRA] (JENKINS-13340) Compiler Warnings menu item gone when no compiler warnings

[
https://issues.jenkins-ci.org/browse/JENKINS-13340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161216#comment-161216
]

Ulli Hafner commented on JENKINS-13340:
---

Actually, we are talking about two links. The project (job) link, and the build
link. The semantics of both links are similar: if the project has no warnings
in the latest build, then the job link (/warnings) is not shown. If a build
has no warnings, then the build link (build#/warningsResult) is not shown. If
you don't have warnings, then there would be no fixed warnings (only one build
would have fixed warnings).

Compiler Warnings menu item gone when no compiler warnings
--

[JIRA] (JENKINS-13007) Git plugin cannot find revision to build on Windows

2012-04-04 Thread ritzm...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161217#comment-161217
 ] 

ritzmann commented on JENKINS-13007:


I can confirm that setting the executable to git.exe instead of git.cmd works 
for us.

 Git plugin cannot find revision to build on Windows
 ---

 Key: JENKINS-13007
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13007
 Project: Jenkins
  Issue Type: Bug
  Components: git
 Environment: Windows 2008 Server 64 Bit
 NTFS
Reporter: ritzmann
Assignee: Nicolas De Loof
Priority: Critical

 After we upgraded the Git plugin from 1.1.14 to 1.1.16, all our builds on 
 Windows build slaves started failing like this:
 Started by user anonymous
 Building remotely on win-slave1 in workspace d:\hudson\workspace\my-app
 Checkout:my-app / d:\hudson\workspace\my-app - 
 hudson.remoting.Channel@95ff886:win-slave1
 Using strategy: Default
 Last Built Revision: Revision e00e2c1328a011ca99980e0ffd90f7534b34 
 (origin/master)
 Checkout:my-app / d:\hudson\workspace\my-app - 
 hudson.remoting.LocalChannel@470a4b80
 Fetching changes from 1 remote Git repository
 Fetching upstream changes from d:\hudson\shared\repo.git
 ERROR: Couldn't find any revision to build. Verify the repository and branch 
 configuration for this job.
 The builds on our Linux slaves are not affected. Wiping the workspaces on the 
 Windows slaves did not help. Both clones and checkouts/updates seem to fail 
 with the same error. Downgrading back to 1.1.14 made the Windows builds work 
 again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13312) Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue

2012-04-04 Thread thomasmfie...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161218#comment-161218
 ] 

Thomas Fields commented on JENKINS-13312:
-

Just had this happen again. Process explorer didn't give any clues and Handle 
-u pathToDir reporting no locks. Is it possible to add some debugging code to 
the Perforce plugin to help get to the bottom of this?

 Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue
 

 Key: JENKINS-13312
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13312
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: Jenkins 1.455
 Perforce plugin 1.38
Reporter: Thomas Fields
Assignee: Rob Petti

 Hi there,
 Occasionally some of my projects fail with the following callstack:
 {code}12:19:33  Started by an SCM change
 12:19:33  Building remotely on BuildSlave1 in workspace 
 c:\JCI\workspace\UnitTestsToolWin32-Release
 12:20:29  hudson.util.IOException2: remote file operation failed: 
 c:\JCI\workspace\UnitTestsToolWin32-Release\CONFIG at 
 hudson.remoting.Channel@586ca3ef:PhyreBuild1
 12:20:29  at hudson.FilePath.act(FilePath.java:784)
 12:20:29  at hudson.FilePath.act(FilePath.java:770)
 12:20:29  at hudson.FilePath.deleteRecursive(FilePath.java:854)
 12:20:29  at 
 hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:597)
 12:20:29  at 
 hudson.model.AbstractProject.checkout(AbstractProject.java:1197)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
 12:20:29  at hudson.model.Run.run(Run.java:1410)
 12:20:29  at hudson.matrix.MatrixBuild.run(MatrixBuild.java:253)
 12:20:29  at 
 hudson.model.ResourceController.execute(ResourceController.java:88)
 12:20:29  at hudson.model.Executor.run(Executor.java:238)
 12:20:29  at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
 12:20:29  Caused by: java.io.IOException: There are no more files
 12:20:29  at java.io.WinNTFileSystem.canonicalize0(Native Method)
 12:20:29  at java.io.Win32FileSystem.canonicalize(Unknown Source)
 12:20:29  at java.io.File.getCanonicalPath(Unknown Source)
 12:20:29  at java.io.File.getCanonicalFile(Unknown Source)
 12:20:29  at hudson.Util.isSymlink(Util.java:322)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:277)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:856)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:854)
 12:20:29  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2099)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 12:20:29  at hudson.remoting.Request$2.run(Request.java:287)
 12:20:29  at 
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 12:20:29  at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 12:20:29  at java.util.concurrent.FutureTask.run(Unknown Source)
 12:20:29  at

[JIRA] (JENKINS-13267) Wrong working dir used on Windows if executed command is in a subfolder

2012-04-04 Thread hsku...@gmail.com (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Henrik Skupin resolved JENKINS-13267.
-

Resolution: Not A Defect

As it has been turned out it was really an issue on our side. Sorry for the
false alarm.

Wrong working dir used on Windows if executed command is in a subfolder
---

Key: JENKINS-13267
URL: https://issues.jenkins-ci.org/browse/JENKINS-13267
Project: Jenkins
Issue Type: Bug
Components: xshell
Affects Versions: current
Environment: Any Windows platform
Reporter: Henrik Skupin

If a build step with XShell calls a command which is not in the current
working dir but in a sub folder, the sub folder is used as current working
dir. This issue only persists on Windows and cannot be seen on Linux or Mac.
Just take a command (which is a wrapper script) like:
scripts/run hg clone https://hg.mozilla.org/qa/mozmill-automation
It should clone the given repository into the nodes working dir, but right
now it will end up as 'scripts/mozmill-automation'. So the wrapper scripts
working dir is used.
Calling the wrapper script from outside Jenkins it works fine, so it has to
be a XShell bug.
As reference of a problematic job see:
https://github.com/whimboo/mozmill-ci/blob/master/jenkins-master/jobs/functional-test/config.xml#L78
Steps to reproduce:
1. Clone https://github.com/whimboo/mozmill-ci/
2. Follow the readme and setup the system
3. Add a node for Windows
4. Run 'Build Now' on the functional testrun (Branch: mozilla-central,
Platform: win32, Locale: en-US, BuildId: 20120328115525, Nodes: win_xp,
Env-Platform: Windows)
5. Check the working dir of the project and notice that the hg clone is not
ending up in the root working dir
There is also no difference with executeFromWorkingDir enabled or disabled.
5.

[JIRA] (JENKINS-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail

2012-04-04 Thread r...@java.net (JIRA)

ravn created JENKINS-13341:
--

 Summary: Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK 
cause Maven build to fail
 Key: JENKINS-13341
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13341
 Project: Jenkins
  Issue Type: Bug
  Components: maven
Reporter: ravn


After upgrading Ubuntu packaged Jenkins to 1.458 (using OpenJDK as installed by 
apt-get) I receive the following failures:



 Failed to load native POSIX impl; falling back on Java impl. Stacktrace 
follows.
13:19:30  java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': 
com.sun.jna.Native.open(Ljava/lang/String;)J
13:19:30at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166)
13:19:30at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239)
13:19:30at com.sun.jna.Library$Handler.init(Library.java:140)
13:19:30at com.sun.jna.Native.loadLibrary(Native.java:366)
13:19:30at 
org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96)
13:19:30at 
org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65)
13:19:30at 
org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24)
13:19:30at hudson.os.PosixAPI.clinit(PosixAPI.java:40)
13:19:30at hudson.Util.resolveSymlink(Util.java:1067)
13:19:30at hudson.Util.resolveSymlink(Util.java:1030)
13:19:30at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
13:19:30at hudson.FilePath.writeToTar(FilePath.java:1781)
13:19:30at hudson.FilePath.copyRecursiveTo(FilePath.java:1708)
13:19:30at hudson.FilePath.copyRecursiveTo(FilePath.java:1637)
13:19:30at 
hudson.maven.reporters.AbstractMavenJavadocArchiver.postExecute(AbstractMavenJavadocArchiver.java:98)
13:19:30at 
hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:478)
13:19:30at 
hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:459)
13:19:30at 
org.jfrog.build.extractor.maven.BuildInfoRecorder.mojoSucceeded(BuildInfoRecorder.java:241)
13:19:30at 
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
13:19:30at 
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
13:19:30at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
13:19:30at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
13:19:30at 
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
13:19:30at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
13:19:30at 
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
13:19:30at 
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
13:19:30at 
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
13:19:30at 
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
13:19:30at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
13:19:30at 
org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
13:19:30at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
13:19:30at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
13:19:30at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
13:19:30at java.lang.reflect.Method.invoke(Method.java:616)
13:19:30at 
org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
13:19:30at 
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
13:19:30at 
org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
13:19:30at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
13:19:30at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
13:19:30at hudson.remoting.UserRequest.perform(UserRequest.java:118)
13:19:30at hudson.remoting.UserRequest.perform(UserRequest.java:48)
13:19:30at hudson.remoting.Request$2.run(Request.java:287)
13:19:30at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
13:19:30at 
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
13:19:30at java.util.concurrent.FutureTask.run(FutureTask.java:166)
13:19:30at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
13:19:30at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
13:19:30

[JIRA] (JENKINS-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail

2012-04-04 Thread r...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161221#comment-161221
 ] 

ravn commented on JENKINS-13341:


It appears to happen when I use javadoc:aggregate, but not without in my 
maven invocation line.

 Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to 
 fail
 

 Key: JENKINS-13341
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13341
 Project: Jenkins
  Issue Type: Bug
  Components: maven
Reporter: ravn

 After upgrading Ubuntu packaged Jenkins to 1.458 (using OpenJDK as installed 
 by apt-get) I receive the following failures:
 
  Failed to load native POSIX impl; falling back on Java impl. Stacktrace 
 follows.
 13:19:30  java.lang.UnsatisfiedLinkError: Unable to load library 'libc.so.6': 
 com.sun.jna.Native.open(Ljava/lang/String;)J
 13:19:30  at com.sun.jna.NativeLibrary.loadLibrary(NativeLibrary.java:166)
 13:19:30  at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:239)
 13:19:30  at com.sun.jna.Library$Handler.init(Library.java:140)
 13:19:30  at com.sun.jna.Native.loadLibrary(Native.java:366)
 13:19:30  at 
 org.jruby.ext.posix.POSIXFactory.loadLibC(POSIXFactory.java:96)
 13:19:30  at 
 org.jruby.ext.posix.POSIXFactory.loadLinuxPOSIX(POSIXFactory.java:65)
 13:19:30  at 
 org.jruby.ext.posix.POSIXFactory.getPOSIX(POSIXFactory.java:24)
 13:19:30  at hudson.os.PosixAPI.clinit(PosixAPI.java:40)
 13:19:30  at hudson.Util.resolveSymlink(Util.java:1067)
 13:19:30  at hudson.Util.resolveSymlink(Util.java:1030)
 13:19:30  at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
 13:19:30  at hudson.FilePath.writeToTar(FilePath.java:1781)
 13:19:30  at hudson.FilePath.copyRecursiveTo(FilePath.java:1708)
 13:19:30  at hudson.FilePath.copyRecursiveTo(FilePath.java:1637)
 13:19:30  at 
 hudson.maven.reporters.AbstractMavenJavadocArchiver.postExecute(AbstractMavenJavadocArchiver.java:98)
 13:19:30  at 
 hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoSucceeded(Maven3Builder.java:478)
 13:19:30  at 
 hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:459)
 13:19:30  at 
 org.jfrog.build.extractor.maven.BuildInfoRecorder.mojoSucceeded(BuildInfoRecorder.java:241)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
 13:19:30  at 
 org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
 13:19:30  at 
 org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
 13:19:30  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
 13:19:30  at 
 org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
 13:19:30  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 13:19:30  at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
 13:19:30  at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 13:19:30  at java.lang.reflect.Method.invoke(Method.java:616)
 13:19:30  at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
 13:19:30  at 
 org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
 13:19:30  at 
 org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
 13:19:30  at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
 13:19:30  at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
 13:19:30  at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 13:19:30  at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 13:19:30  at hudson.remoting.Request$2.run(Request.java:287)
 13:19:30  at 
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 13:19:30  at

[JIRA] (JENKINS-13124) Missing New warnings


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ulli Hafner updated JENKINS-13124:
--

Priority: Minor  (was: Major)

Seems that your links are expired. Do you mind providing the details as 
attachments?

 Missing New warnings 
 ---

 Key: JENKINS-13124
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13124
 Project: Jenkins
  Issue Type: Bug
  Components: warnings
Reporter: Roland Schulz
Assignee: Ulli Hafner
Priority: Minor

 I noticed a case in which the warnings surrounding a modified line are not 
 shown as new warnings. But according to: 
 https://issues.jenkins-ci.org/browse/JENKINS-6675 they should be shown 
 because the warnings are within +/-3 line of the modified line. I assume that 
 the warnings plugin is taken the modified lines from the SCM.
 The file was changed in line 77 (see 4) but the surrounding warnings (see 1) 
 are not shown in the New warnings (see 2).
 1) The warnings: 
 http://jenkins.gromacs.org/view/Gerrit%20Docu/job/Doxygen_Gerrit_master/65/warningsResult/package.689474037/file.-1578484055/
 2) 0 new warngins: 
 http://jenkins.gromacs.org/view/Gerrit%20Docu/job/Doxygen_Gerrit_master/65/warningsResult/new/
 3) Showing that the file was changed: 
 http://jenkins.gromacs.org/view/Gerrit%20Docu/job/Doxygen_Gerrit_master/65/changes#detail0
 4) Showing the diff for the file: 
 https://gerrit.gromacs.org/#/c/517/13/src/gromacs/trajectoryanalysis/runnercommon.h
 Maybe interesting the new warning detection did work correctly with an 
 earlier reference build.
 For that build, the new warnings were detected correctly: 
 http://jenkins.gromacs.org/view/Gerrit%20Docu/job/Doxygen_Gerrit_master/59/warningsResult/new/package.689474037.
 The file changed exactly the same  for build 59 and build 65. 
 The plugins and Jenkins is the latest version.
 Please let me know if I can provide any further information. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13214) Tests with the same name are no longer reported in the test results

[
https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161223#comment-161223
]

Ruslan Strazhnyk commented on JENKINS-13214:

Got the same problem. It is broken from 1.455

Tests with the same name are no longer reported in the test results
---

Key: JENKINS-13214
URL: https://issues.jenkins-ci.org/browse/JENKINS-13214
Project: Jenkins
Issue Type: Bug
Components: maven2
Affects Versions: current
Reporter: ajbanck

After updating from 1.425 to 1.456 test results will only show one test for
tests having the same name.
Test set having tests executed with parameters:
...
..Executing TestMyTest#testDefault(true)
..Executing TestMyTest#testDefault(false)
.Finished test set [Unit Tests] on Fri Mar 23 12:26:08 CET 2012. Executed
[132] tests.
Resulting test results: xml
...
testcase time=0.047 classname=TestMyTest name=testDefault/
testcase time=0.043 classname=TestMyTest name=testDefault/
/testsuite
In version 1.425 the 132 test results where correctly displayed.
In version 1.456 the test results page is only having one entry for these
tests, total amount of tests reported is no longer valid and is the count per
test method and not the count of tests actually executed.

[JIRA] (JENKINS-13101) Analysis Collector Plugin prevents other plugins from loading when the Dashboard View Plugin is not installed


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161224#comment-161224
 ] 

Ulli Hafner commented on JENKINS-13101:
---

Ok, I can reproduce the problem with 1.458.

 Analysis Collector Plugin prevents other plugins from loading when the 
 Dashboard View Plugin is not installed
 -

 Key: JENKINS-13101
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13101
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector
Affects Versions: current
 Environment: Jenkins ver. 1.455
 Analysis Collector 1.20
 Tomcat 6 
Reporter: Martin Ziel
Assignee: Ulli Hafner
  Labels: exception, plugin
 Attachments: jenkins.log


 The Analysis Collector Plugin prevents other plugins from loading when the 
 Dashboard View Plugin is not installed and activated. In my case, this 
 effectively disables the SCM Plugins and thus prevents Jenkins from fetching 
 SCM changes. Log attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13214) Tests with the same name are no longer reported in the test results

[
https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161223#comment-161223
]

Ruslan Strazhnyk edited comment on JENKINS-13214 at 4/4/12 12:51 PM:
-

Got the same problem. It is broken from 1.453
Still works good on 1.452 - I discovered it afer series of downgrades

was (Author: desperado):
Got the same problem. It is broken from 1.455

Tests with the same name are no longer reported in the test results
---

Key: JENKINS-13214
URL: https://issues.jenkins-ci.org/browse/JENKINS-13214
Project: Jenkins
Issue Type: Bug
Components: maven2
Affects Versions: current
Reporter: ajbanck

[JIRA] (JENKINS-13343) Plugins included in base distributions are not updating

2012-04-04 Thread h...@filez.com (JIRA)

Radim Kolar created JENKINS-13343:
-

 Summary: Plugins included in base distributions are not updating
 Key: JENKINS-13343
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13343
 Project: Jenkins
  Issue Type: Bug
  Components: plugin
 Environment: Freebsd 8.2 / 64 bit
Reporter: Radim Kolar


http://groups.google.com/group/jenkinsci-users/browse_thread/thread/8bdcccbac4bf0c63#

in /jenkins/pluginManager i see that 3 bundled plugins are updated -
subversion, cvs, translation plugin.

when i click on update new plugins are downloaded but when i check
them by looking inside - they are exactly same versions as my old, not
announced versions.

Subversion Plugin - installed 1.34
CVS Plugin - installed 1.6
Translation Assistance Plugin - installed 1.8

update site:
http://jenkins.mirror.isppower.de/updates/stable/update-center.json

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruslan Strazhnyk reopened JENKINS-12457:



 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12457) 'Age' column on 'Test Result' tab may show incorrect value when a test suite divided into multiple junit files


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161226#comment-161226
 ] 

Ruslan Strazhnyk commented on JENKINS-12457:


Seems like fix is defective - See JENKINS-13214

 'Age' column on 'Test Result' tab may show incorrect value when a test suite 
 divided into multiple junit files
 --

 Key: JENKINS-12457
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12457
 Project: Jenkins
  Issue Type: Improvement
  Components: junit
Affects Versions: current
Reporter: Greg Temchenko
Assignee: kutzi

 Somebody described the problem a year ago here:
 http://jenkins.361315.n4.nabble.com/Problem-with-Age-column-on-Test-Results-tab-td3172208.html
 {quote}
 I have a problem with 'Age' column on 'Test Results' tab. For couple of my 
 tests, all the time this column has value equals '1', despite the fact that 
 those tests start failing earlier than one build ago. When I switch to 
 'History' tab, in 'Test Result' column there is a 'Regression' value for all 
 builds, and it should be 'Regression' value only for the first build and 
 'Failed' for next builds.
 {quote}
 For me this happens because I have many junit xmls that containing the same 
 test suite name.
 In this case hudson.tasks.junit.CaseResult.getPreviousResult() gets the only 
 last junit xml result and if it's not failed then the Age column won't be 
 calculated properly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13214) Tests with the same name are no longer reported in the test results

2012-04-04 Thread ku...@gmx.de (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

kutzi reassigned JENKINS-13214:
---

Assignee: kutzi

Tests with the same name are no longer reported in the test results
---

Key: JENKINS-13214
URL: https://issues.jenkins-ci.org/browse/JENKINS-13214
Project: Jenkins
Issue Type: Bug
Components: maven2
Affects Versions: current
Reporter: ajbanck
Assignee: kutzi

[JIRA] (JENKINS-13241) Artifact archiving from remote slave fails

2012-04-04 Thread adam.wal...@detica.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161227#comment-161227
 ] 

Adam Walker commented on JENKINS-13241:
---

I have just upgraded to 1.458 and I'm getting the same problem. In my case a 
single file was archived but is unreadable (red no-entry icon with size 0). 
I've examined the filesystem and it's a symlink pointing at a file that doesn't 
exist locally, but does exist on the slave it was compiled on. 

Our previous builds do not contain any symlinks, only copies of the file 
content. I've had a look through the changes affecting 1.456 and I think that 
JENKINS-9118 is the cause of the problem. Before this bug was fixed, the 
workspace on the slave would be copied by content (i.e. no symlinks) to the 
archive. With the bug fix, the symlinks are copied instead, but these point to 
a location that doesn't necessarily exist on master (e.g. 
/var/lib/hudson/workspace/project on slave vs /var/lib/hudson/jobs/project 
on master). This causes the archiving process to fail as the file descriptor is 
invalid on files that only exist on the slave.

 Artifact archiving from remote slave fails
 --

 Key: JENKINS-13241
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13241
 Project: Jenkins
  Issue Type: Bug
  Components: core
Reporter: Vyacheslav Karpukhin

 Since 1.456 jenkins stopped archiving artifacts from remote slave. This 
 affects both 1.456 and 1.457, works correctly with 1.455.
 ERROR: Failed to archive artifacts: build/Release/*.app/**/*
 hudson.util.IOException2: hudson.util.IOException2: Failed to extract 
 /var/jenkins/workspace/NGB_Queues/build/Release/*.app/**/*
   at hudson.FilePath.readFromTar(FilePath.java:1817)
   at hudson.FilePath.copyRecursiveTo(FilePath.java:1729)
   at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
   at hudson.model.Build$RunnerImpl.post2(Build.java:162)
   at 
 hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625)
   at hudson.model.Run.run(Run.java:1435)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)
 Caused by: java.io.IOException: Failed to chmod 
 /mnt/storage/.jenkins/jobs/NGB_Queues/builds/2012-03-27_03-11-27/archive/build/Release/NGB
  
 Queues.app/Contents/Frameworks/BWToolkitFramework.framework/BWToolkitFramework
  : No such file or directory
   at hudson.FilePath._chmod(FilePath.java:1248)
   at hudson.FilePath.readFromTar(FilePath.java:1813)
   ... 12 more
   at hudson.FilePath.copyRecursiveTo(FilePath.java:1736)
   at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
   at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
   at 
 hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678)
   at 
 hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656)
   at hudson.model.Build$RunnerImpl.post2(Build.java:162)
   at 
 hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625)
   at hudson.model.Run.run(Run.java:1435)
   at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
   at hudson.model.ResourceController.execute(ResourceController.java:88)
   at hudson.model.Executor.run(Executor.java:238)
 Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Pipe 
 is already closed
   at hudson.remoting.Channel$2.adapt(Channel.java:714)
   at hudson.remoting.Channel$2.adapt(Channel.java:709)
   at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)
   at hudson.FilePath.copyRecursiveTo(FilePath.java:1732)
   ... 11 more
 Caused by: java.io.IOException: Pipe is already closed
   at hudson.remoting.PipeWindow.checkDeath(PipeWindow.java:83)
   at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:171)
   at hudson.remoting.ProxyOutputStream._write(ProxyOutputStream.java:118)
   at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:103)
   at 
 java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65)
   at java.io.BufferedOutputStream.write(BufferedOutputStream.java:109)
   at

[JIRA] (JENKINS-13344) Build publishing on multiple instances

2012-04-04 Thread vjura...@java.net (JIRA)

vjuranek created JENKINS-13344:
--

 Summary: Build publishing on multiple instances
 Key: JENKINS-13344
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13344
 Project: Jenkins
  Issue Type: New Feature
  Components: build-publisher
Reporter: vjuranek
Assignee: vjuranek


Implement option to publish the build on more then one instance if there are 
more instances configured.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12466) Jobs using repo plugin do not persist

2012-04-04 Thread aherit...@apache.org (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Héritier reassigned JENKINS-12466:
-

Assignee: Arnaud Héritier

 Jobs using repo plugin do not persist
 -

 Key: JENKINS-12466
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12466
 Project: Jenkins
  Issue Type: Bug
  Components: repo
Affects Versions: current
 Environment: Ubuntu 10.04, Jenkins 1.448, repo plugin 1.2
Reporter: Senthil Natarajan
Assignee: Arnaud Héritier
Priority: Minor

 I lost a job that used the repo plugin, after restarting Jenkins.  I checked 
 the jenkins log, and this is the error shown in the log:
 Jan 18, 2012 4:43:28 PM jenkins.InitReactorRunner$1 onTaskFailed
 SEVERE: Failed Loading job Manifest_Monitor
 java.lang.NullPointerException
 at hudson.plugins.repo.RevisionState.hashCode(RevisionState.java:139)
 at java.lang.Object.toString(Object.java:219)
 at java.lang.String.valueOf(String.java:2826)
 at java.util.Arrays.toString(Arrays.java:4071)
 at 
 java.util.concurrent.CopyOnWriteArrayList.toString(CopyOnWriteArrayList.java:860)
 at java.lang.String.valueOf(String.java:2826)
 at java.lang.StringBuilder.append(StringBuilder.java:115)
 at 
 org.jvnet.hudson.plugins.DownStreamProjectActionFactory.createFor(DownStreamProjectActionFactory.java:69)
 at 
 hudson.model.AbstractProject.createTransientActions(AbstractProject.java:612)
 at hudson.model.Project.createTransientActions(Project.java:203)
 at 
 hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:602)
 at hudson.model.AbstractProject.onLoad(AbstractProject.java:272)
 at hudson.model.Project.onLoad(Project.java:88)
 at hudson.model.Items.load(Items.java:115)
 at jenkins.model.Jenkins$14.run(Jenkins.java:2372)
 at 
 org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
 at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
 at jenkins.model.Jenkins$5.runTask(Jenkins.java:812)
 at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
 at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Jan 18, 2012 4:43:28 PM
 org.jvnet.hudson.plugins.DownStreamProjectActionFactory createFor 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12466) Jobs using repo plugin do not persist

2012-04-04 Thread aherit...@apache.org (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161229#comment-161229
 ] 

Arnaud Héritier commented on JENKINS-12466:
---

pull request merged.
Please ask on the dev list if the plugin maintainer wants to release it. 
Otherwise I'll do it.

 Jobs using repo plugin do not persist
 -

 Key: JENKINS-12466
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12466
 Project: Jenkins
  Issue Type: Bug
  Components: repo
Affects Versions: current
 Environment: Ubuntu 10.04, Jenkins 1.448, repo plugin 1.2
Reporter: Senthil Natarajan
Assignee: Arnaud Héritier
Priority: Minor

 I lost a job that used the repo plugin, after restarting Jenkins.  I checked 
 the jenkins log, and this is the error shown in the log:
 Jan 18, 2012 4:43:28 PM jenkins.InitReactorRunner$1 onTaskFailed
 SEVERE: Failed Loading job Manifest_Monitor
 java.lang.NullPointerException
 at hudson.plugins.repo.RevisionState.hashCode(RevisionState.java:139)
 at java.lang.Object.toString(Object.java:219)
 at java.lang.String.valueOf(String.java:2826)
 at java.util.Arrays.toString(Arrays.java:4071)
 at 
 java.util.concurrent.CopyOnWriteArrayList.toString(CopyOnWriteArrayList.java:860)
 at java.lang.String.valueOf(String.java:2826)
 at java.lang.StringBuilder.append(StringBuilder.java:115)
 at 
 org.jvnet.hudson.plugins.DownStreamProjectActionFactory.createFor(DownStreamProjectActionFactory.java:69)
 at 
 hudson.model.AbstractProject.createTransientActions(AbstractProject.java:612)
 at hudson.model.Project.createTransientActions(Project.java:203)
 at 
 hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:602)
 at hudson.model.AbstractProject.onLoad(AbstractProject.java:272)
 at hudson.model.Project.onLoad(Project.java:88)
 at hudson.model.Items.load(Items.java:115)
 at jenkins.model.Jenkins$14.run(Jenkins.java:2372)
 at 
 org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
 at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
 at jenkins.model.Jenkins$5.runTask(Jenkins.java:812)
 at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
 at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Jan 18, 2012 4:43:28 PM
 org.jvnet.hudson.plugins.DownStreamProjectActionFactory createFor 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12466) Jobs using repo plugin do not persist


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161230#comment-161230
 ] 

SCM/JIRA link daemon commented on JENKINS-12466:


Code changed in jenkins
User: Arnaud Heritier
Path:
 pom.xml
http://jenkins-ci.org/commit/repo-plugin/d48ea50ab88f37a30c084cc3fd3868b2a29b824c
Log:
  RElease a bugfix for JENKINS-12466




 Jobs using repo plugin do not persist
 -

 Key: JENKINS-12466
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12466
 Project: Jenkins
  Issue Type: Bug
  Components: repo
Affects Versions: current
 Environment: Ubuntu 10.04, Jenkins 1.448, repo plugin 1.2
Reporter: Senthil Natarajan
Assignee: Arnaud Héritier
Priority: Minor

 I lost a job that used the repo plugin, after restarting Jenkins.  I checked 
 the jenkins log, and this is the error shown in the log:
 Jan 18, 2012 4:43:28 PM jenkins.InitReactorRunner$1 onTaskFailed
 SEVERE: Failed Loading job Manifest_Monitor
 java.lang.NullPointerException
 at hudson.plugins.repo.RevisionState.hashCode(RevisionState.java:139)
 at java.lang.Object.toString(Object.java:219)
 at java.lang.String.valueOf(String.java:2826)
 at java.util.Arrays.toString(Arrays.java:4071)
 at 
 java.util.concurrent.CopyOnWriteArrayList.toString(CopyOnWriteArrayList.java:860)
 at java.lang.String.valueOf(String.java:2826)
 at java.lang.StringBuilder.append(StringBuilder.java:115)
 at 
 org.jvnet.hudson.plugins.DownStreamProjectActionFactory.createFor(DownStreamProjectActionFactory.java:69)
 at 
 hudson.model.AbstractProject.createTransientActions(AbstractProject.java:612)
 at hudson.model.Project.createTransientActions(Project.java:203)
 at 
 hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:602)
 at hudson.model.AbstractProject.onLoad(AbstractProject.java:272)
 at hudson.model.Project.onLoad(Project.java:88)
 at hudson.model.Items.load(Items.java:115)
 at jenkins.model.Jenkins$14.run(Jenkins.java:2372)
 at 
 org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
 at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
 at jenkins.model.Jenkins$5.runTask(Jenkins.java:812)
 at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
 at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Jan 18, 2012 4:43:28 PM
 org.jvnet.hudson.plugins.DownStreamProjectActionFactory createFor 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12466) Jobs using repo plugin do not persist

2012-04-04 Thread aherit...@apache.org (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-12466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Arnaud Héritier resolved JENKINS-12466.
---

Resolution: Fixed

Will be fixed in 1.2.1

 Jobs using repo plugin do not persist
 -

 Key: JENKINS-12466
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12466
 Project: Jenkins
  Issue Type: Bug
  Components: repo
Affects Versions: current
 Environment: Ubuntu 10.04, Jenkins 1.448, repo plugin 1.2
Reporter: Senthil Natarajan
Assignee: Arnaud Héritier
Priority: Minor

 I lost a job that used the repo plugin, after restarting Jenkins.  I checked 
 the jenkins log, and this is the error shown in the log:
 Jan 18, 2012 4:43:28 PM jenkins.InitReactorRunner$1 onTaskFailed
 SEVERE: Failed Loading job Manifest_Monitor
 java.lang.NullPointerException
 at hudson.plugins.repo.RevisionState.hashCode(RevisionState.java:139)
 at java.lang.Object.toString(Object.java:219)
 at java.lang.String.valueOf(String.java:2826)
 at java.util.Arrays.toString(Arrays.java:4071)
 at 
 java.util.concurrent.CopyOnWriteArrayList.toString(CopyOnWriteArrayList.java:860)
 at java.lang.String.valueOf(String.java:2826)
 at java.lang.StringBuilder.append(StringBuilder.java:115)
 at 
 org.jvnet.hudson.plugins.DownStreamProjectActionFactory.createFor(DownStreamProjectActionFactory.java:69)
 at 
 hudson.model.AbstractProject.createTransientActions(AbstractProject.java:612)
 at hudson.model.Project.createTransientActions(Project.java:203)
 at 
 hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:602)
 at hudson.model.AbstractProject.onLoad(AbstractProject.java:272)
 at hudson.model.Project.onLoad(Project.java:88)
 at hudson.model.Items.load(Items.java:115)
 at jenkins.model.Jenkins$14.run(Jenkins.java:2372)
 at 
 org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
 at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
 at jenkins.model.Jenkins$5.runTask(Jenkins.java:812)
 at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
 at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
 at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:662)
 Jan 18, 2012 4:43:28 PM
 org.jvnet.hudson.plugins.DownStreamProjectActionFactory createFor 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13324) Perforce mail address resolver should fall back to other resolvers if mail address is invalid

[
https://issues.jenkins-ci.org/browse/JENKINS-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161232#comment-161232
]

Rob Petti commented on JENKINS-13324:
-

Alright, let's go for a string for now then. Is 'n/a' actually accepted as a
valid email by perforce?

Perforce mail address resolver should fall back to other resolvers if mail
address is invalid
-

Key: JENKINS-13324
URL: https://issues.jenkins-ci.org/browse/JENKINS-13324
Project: Jenkins
Issue Type: Bug
Components: perforce
Environment: Perforce 2011.1
perforce-plugin 1.3.12
Reporter: Mikko Tapaninen

Perforce mail address resolver is always returning a string, no matter what
the actual email address is. I don't know what is the order how Jenkins loops
through the various MailAddressResolver instances but if some instance
returns an actual string (i.e. non-null), it will stick with that. I don't
think it's feasible to really check whether the email address provided by
Perforce is valid, but PerforceMailResolver could check for some value (e.g.
n/a) and return null if it matches. At least with Perforce 2011.1 you can't
have an empty value for an email address.
There could be an UI element for configuring which email address would be
thought as invalid, but I'm fine with hardcoding n/a there and documenting
it somewhere. Would this be ok?

[JIRA] (JENKINS-13312) Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161233#comment-161233
 ] 

Rob Petti commented on JENKINS-13312:
-

It failed with the exact same stack trace? Have you tried following the 
directions on that link I sent earlier?

 Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue
 

 Key: JENKINS-13312
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13312
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: Jenkins 1.455
 Perforce plugin 1.38
Reporter: Thomas Fields
Assignee: Rob Petti

 Hi there,
 Occasionally some of my projects fail with the following callstack:
 {code}12:19:33  Started by an SCM change
 12:19:33  Building remotely on BuildSlave1 in workspace 
 c:\JCI\workspace\UnitTestsToolWin32-Release
 12:20:29  hudson.util.IOException2: remote file operation failed: 
 c:\JCI\workspace\UnitTestsToolWin32-Release\CONFIG at 
 hudson.remoting.Channel@586ca3ef:PhyreBuild1
 12:20:29  at hudson.FilePath.act(FilePath.java:784)
 12:20:29  at hudson.FilePath.act(FilePath.java:770)
 12:20:29  at hudson.FilePath.deleteRecursive(FilePath.java:854)
 12:20:29  at 
 hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:597)
 12:20:29  at 
 hudson.model.AbstractProject.checkout(AbstractProject.java:1197)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
 12:20:29  at hudson.model.Run.run(Run.java:1410)
 12:20:29  at hudson.matrix.MatrixBuild.run(MatrixBuild.java:253)
 12:20:29  at 
 hudson.model.ResourceController.execute(ResourceController.java:88)
 12:20:29  at hudson.model.Executor.run(Executor.java:238)
 12:20:29  at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
 12:20:29  Caused by: java.io.IOException: There are no more files
 12:20:29  at java.io.WinNTFileSystem.canonicalize0(Native Method)
 12:20:29  at java.io.Win32FileSystem.canonicalize(Unknown Source)
 12:20:29  at java.io.File.getCanonicalPath(Unknown Source)
 12:20:29  at java.io.File.getCanonicalFile(Unknown Source)
 12:20:29  at hudson.Util.isSymlink(Util.java:322)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:277)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:856)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:854)
 12:20:29  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2099)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 12:20:29  at hudson.remoting.Request$2.run(Request.java:287)
 12:20:29  at 
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 12:20:29  at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 12:20:29  at java.util.concurrent.FutureTask.run(Unknown Source)
 12:20:29  at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
 12:20:29  at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown 
 Source)

[JIRA] (JENKINS-13345) pre-scm steps runs before workspace is created

2012-04-04 Thread stuff-1-jenkins...@carlini.com (JIRA)

giuliano carlini created JENKINS-13345:
--

 Summary: pre-scm steps runs before workspace is created
 Key: JENKINS-13345
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13345
 Project: Jenkins
  Issue Type: Bug
  Components: prescmbuildstep
Reporter: giuliano carlini
Priority: Critical


1st build for a job always fails when trying to execute prescm build step:
05:45:36  Started by timer
05:45:36  Building on master in workspace 
/build/jenkins/jobs/BuildAllAndTest/workspace
05:45:36  Running Prebuild steps
05:45:36  [workspace] $ /bin/sh -xe /tmp/hudson3985561110537366831.sh
05:45:36  FATAL: command execution failed
05:45:36  java.io.IOException: Cannot run program /bin/sh (in directory
  /build/jenkins/jobs/BuildAllAndTest/workspace): 
java.io.IOException: error=2,
  No such file or directory
Fortunately there is another bug, failures in the prescm build step do not fail 
the build, so the job continues and creates the workspace, so the next build 
succeeds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12048) Wrong option --branch used by change polling

2012-04-04 Thread sgai...@gestour.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161234#comment-161234
 ] 

Samuel Gaiffe commented on JENKINS-12048:
-

Not corrected in 1.458. Could we have a fix version because it's very annoying 
as all our projects are using Mercurial

 Wrong option --branch used by change polling 
 ---

 Key: JENKINS-12048
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12048
 Project: Jenkins
  Issue Type: Bug
  Components: mercurial
Reporter: Christoph Neuroth
Assignee: davidmc24
Priority: Critical

 With Jenkins 1.442, Mercurial Plugin 1.38, the change polling issues a hg 
 log command using \-\-branch foo, which mercurial doesn't know about. 
 Should be \-b or \-\-only-branch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13345) pre-scm steps runs before workspace is created

2012-04-04 Thread stuff-1-jenkins...@carlini.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

giuliano carlini resolved JENKINS-13345.


Resolution: Duplicate

dup of JENKINS-12770

 pre-scm steps runs before workspace is created
 --

 Key: JENKINS-13345
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13345
 Project: Jenkins
  Issue Type: Bug
  Components: prescmbuildstep
Reporter: giuliano carlini
Priority: Critical

 1st build for a job always fails when trying to execute prescm build step:
 05:45:36  Started by timer
 05:45:36  Building on master in workspace 
 /build/jenkins/jobs/BuildAllAndTest/workspace
 05:45:36  Running Prebuild steps
 05:45:36  [workspace] $ /bin/sh -xe /tmp/hudson3985561110537366831.sh
 05:45:36  FATAL: command execution failed
 05:45:36  java.io.IOException: Cannot run program /bin/sh (in directory
   /build/jenkins/jobs/BuildAllAndTest/workspace): 
 java.io.IOException: error=2,
   No such file or directory
 Fortunately there is another bug, failures in the prescm build step do not 
 fail the build, so the job continues and creates the workspace, so the next 
 build succeeds.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13346) Support for QC 10

2012-04-04 Thread msille...@java.net (JIRA)

msillence created JENKINS-13346:
---

 Summary: Support for QC 10
 Key: JENKINS-13346
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13346
 Project: Jenkins
  Issue Type: New Feature
  Components: qc
Affects Versions: current
 Environment: Windows 7
QC 10
QTP 11
Reporter: msillence
Assignee: Daniel Petisme


I would like support for QC 10 and see in the past people have had this working.
When I enter the path to a QC installer/URL/dll it says the path is invalid
I never get to see a QC build option

I'm willing to work on this if someone could provide a few pointers

Thanks,
M

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13312) Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue

2012-04-04 Thread thomasmfie...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161236#comment-161236
 ] 

Thomas Fields commented on JENKINS-13312:
-

Hi Rob,

Yes it was the exact same callstack but this time for a different project. Out 
of about 55 Jenkins projects, we see this issue in 1 or 2 projects per day.

Which link are you talking about? I tried process explorer and couldn't find 
any problems nor did anything have a lock on the directory.

Cheers,
Tom.

 Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue
 

 Key: JENKINS-13312
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13312
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: Jenkins 1.455
 Perforce plugin 1.38
Reporter: Thomas Fields
Assignee: Rob Petti

 Hi there,
 Occasionally some of my projects fail with the following callstack:
 {code}12:19:33  Started by an SCM change
 12:19:33  Building remotely on BuildSlave1 in workspace 
 c:\JCI\workspace\UnitTestsToolWin32-Release
 12:20:29  hudson.util.IOException2: remote file operation failed: 
 c:\JCI\workspace\UnitTestsToolWin32-Release\CONFIG at 
 hudson.remoting.Channel@586ca3ef:PhyreBuild1
 12:20:29  at hudson.FilePath.act(FilePath.java:784)
 12:20:29  at hudson.FilePath.act(FilePath.java:770)
 12:20:29  at hudson.FilePath.deleteRecursive(FilePath.java:854)
 12:20:29  at 
 hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:597)
 12:20:29  at 
 hudson.model.AbstractProject.checkout(AbstractProject.java:1197)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
 12:20:29  at hudson.model.Run.run(Run.java:1410)
 12:20:29  at hudson.matrix.MatrixBuild.run(MatrixBuild.java:253)
 12:20:29  at 
 hudson.model.ResourceController.execute(ResourceController.java:88)
 12:20:29  at hudson.model.Executor.run(Executor.java:238)
 12:20:29  at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
 12:20:29  Caused by: java.io.IOException: There are no more files
 12:20:29  at java.io.WinNTFileSystem.canonicalize0(Native Method)
 12:20:29  at java.io.Win32FileSystem.canonicalize(Unknown Source)
 12:20:29  at java.io.File.getCanonicalPath(Unknown Source)
 12:20:29  at java.io.File.getCanonicalFile(Unknown Source)
 12:20:29  at hudson.Util.isSymlink(Util.java:322)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:277)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:856)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:854)
 12:20:29  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2099)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 12:20:29  at hudson.remoting.Request$2.run(Request.java:287)
 12:20:29  at 
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 12:20:29  at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 12:20:29  at

[JIRA] (JENKINS-13342) After update to 1.458, no more access to localhost:8080, maybe reverse proxy issue

2012-04-04 Thread flateu...@hotmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mahmoud MARNAOUI resolved JENKINS-13342.


  Assignee: Mahmoud MARNAOUI
Resolution: Fixed

Fixed by downgrading jenkins version ..

 After update to 1.458, no more access to localhost:8080, maybe reverse 
 proxy issue
 

 Key: JENKINS-13342
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13342
 Project: Jenkins
  Issue Type: Bug
  Components: update-center
Affects Versions: current
 Environment: WAMP
Reporter: Mahmoud MARNAOUI
Assignee: Mahmoud MARNAOUI
Priority: Blocker
  Labels: jenkins
 Fix For: current

 Attachments: 1.jpg, 2.jpg


 Hi,
 My Jenkins version was 1.454, and today I update it to 1.458 (last release).
 After jenkins restarts, I get this error message :
 Connexion fail
 Firefox cannot get connected with the server at Localhost:8080
 and in my previous jenkins webpage in firefox, I see this message in RED :
 It seems that your configuration reverse proxy is wrong
 I restarted my desktop but the problem persist.
 My jenkins is down, and I cannot access to any feature or link or project !
 Another thing, the windows service for jenkins is stopped, and I cannot 
 restart it due to windows service issue # 1067 (windows cannor start this 
 service in local machine
 Need your help please

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12048) Wrong option --branch used by change polling

2012-04-04 Thread sgai...@gestour.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161238#comment-161238
 ] 

Samuel Gaiffe commented on JENKINS-12048:
-

Sorry but where can I find those snapshots ? I tried to build from git repo but 
I have a problem with the parent pom

 Wrong option --branch used by change polling 
 ---

 Key: JENKINS-12048
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12048
 Project: Jenkins
  Issue Type: Bug
  Components: mercurial
Reporter: Christoph Neuroth
Assignee: davidmc24
Priority: Critical

 With Jenkins 1.442, Mercurial Plugin 1.38, the change polling issues a hg 
 log command using \-\-branch foo, which mercurial doesn't know about. 
 Should be \-b or \-\-only-branch.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13347) Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'

2012-04-04 Thread ro...@jouchet.fr (JIRA)

Ronan Jouchet created JENKINS-13347:
---

 Summary: Using ${SVN_REVISION} in build-name-setter Build Name 
returns error: Unrecognized macro 'SVN_REVISION'
 Key: JENKINS-13347
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13347
 Project: Jenkins
  Issue Type: Bug
  Components: build-name-setter
 Environment: Windows 2008 R2 SP1
Java 1.6.0_31 x64
Tomcat 6.0.35
Jenkins 1.458
SVN
Reporter: Ronan Jouchet
Assignee: Kohsuke Kawaguchi


My Jenkins instance/project are working just fine and builds work as expected.
Now I try to use the build-name-setter plugin. My goal is to have build names 
like svn123build9879.

I installed the plugin via the plugin manager, and set the new Build Name 
field to svn${SVN_REVISION}build${BUILD_NUMBER} (without quotes). It looks 
like the expected syntax, and I can see ${SVN_REVISION} in my env-vars.html
However, this leads to the following error in the console log:
Unrecognized macro 'SVN_REVISION' in 'svn${SVN_REVISION}build${BUILD_NUMBER}'

I'm available for more info. I searched for similar bugs, sorry if that's not a 
but but just a misconfiguration, please point me to what you think might be 
wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13347) Using ${SVN_REVISION} in build-name-setter Build Name returns error: Unrecognized macro 'SVN_REVISION'

2012-04-04 Thread ro...@jouchet.fr (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ronan Jouchet updated JENKINS-13347:


Environment: 
Windows 2008 R2 SP1 x64
Java 1.6.0_31 x64 from Oracle
Tomcat 6.0.35
Jenkins 1.458, freshly installed and never upgraded
SVN

  was:
Windows 2008 R2 SP1
Java 1.6.0_31 x64
Tomcat 6.0.35
Jenkins 1.458
SVN


 Using ${SVN_REVISION} in build-name-setter Build Name returns error: 
 Unrecognized macro 'SVN_REVISION'
 --

 Key: JENKINS-13347
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13347
 Project: Jenkins
  Issue Type: Bug
  Components: build-name-setter
 Environment: Windows 2008 R2 SP1 x64
 Java 1.6.0_31 x64 from Oracle
 Tomcat 6.0.35
 Jenkins 1.458, freshly installed and never upgraded
 SVN
Reporter: Ronan Jouchet
Assignee: Kohsuke Kawaguchi
  Labels: plugin

 My Jenkins instance/project are working just fine and builds work as expected.
 Now I try to use the build-name-setter plugin. My goal is to have build 
 names like svn123build9879.
 I installed the plugin via the plugin manager, and set the new Build Name 
 field to svn${SVN_REVISION}build${BUILD_NUMBER} (without quotes). It looks 
 like the expected syntax, and I can see ${SVN_REVISION} in my env-vars.html
 However, this leads to the following error in the console log:
 Unrecognized macro 'SVN_REVISION' in 'svn${SVN_REVISION}build${BUILD_NUMBER}'
 I'm available for more info. I searched for similar bugs, sorry if that's not 
 a but but just a misconfiguration, please point me to what you think might be 
 wrong.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13312) Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161239#comment-161239
 ] 

Rob Petti commented on JENKINS-13312:
-

https://wiki.jenkins-ci.org/display/JENKINS/I'm+getting+OutOfMemoryError

The operation being performed during the failure has very low memory 
requirements, so I doubt this is actually being caused by the perforce plugin.

 Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue
 

 Key: JENKINS-13312
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13312
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: Jenkins 1.455
 Perforce plugin 1.38
Reporter: Thomas Fields
Assignee: Rob Petti

 Hi there,
 Occasionally some of my projects fail with the following callstack:
 {code}12:19:33  Started by an SCM change
 12:19:33  Building remotely on BuildSlave1 in workspace 
 c:\JCI\workspace\UnitTestsToolWin32-Release
 12:20:29  hudson.util.IOException2: remote file operation failed: 
 c:\JCI\workspace\UnitTestsToolWin32-Release\CONFIG at 
 hudson.remoting.Channel@586ca3ef:PhyreBuild1
 12:20:29  at hudson.FilePath.act(FilePath.java:784)
 12:20:29  at hudson.FilePath.act(FilePath.java:770)
 12:20:29  at hudson.FilePath.deleteRecursive(FilePath.java:854)
 12:20:29  at 
 hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:597)
 12:20:29  at 
 hudson.model.AbstractProject.checkout(AbstractProject.java:1197)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
 12:20:29  at hudson.model.Run.run(Run.java:1410)
 12:20:29  at hudson.matrix.MatrixBuild.run(MatrixBuild.java:253)
 12:20:29  at 
 hudson.model.ResourceController.execute(ResourceController.java:88)
 12:20:29  at hudson.model.Executor.run(Executor.java:238)
 12:20:29  at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
 12:20:29  Caused by: java.io.IOException: There are no more files
 12:20:29  at java.io.WinNTFileSystem.canonicalize0(Native Method)
 12:20:29  at java.io.Win32FileSystem.canonicalize(Unknown Source)
 12:20:29  at java.io.File.getCanonicalPath(Unknown Source)
 12:20:29  at java.io.File.getCanonicalFile(Unknown Source)
 12:20:29  at hudson.Util.isSymlink(Util.java:322)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:277)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:856)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:854)
 12:20:29  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2099)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 12:20:29  at hudson.remoting.Request$2.run(Request.java:287)
 12:20:29  at 
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 12:20:29  at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 12:20:29  at java.util.concurrent.FutureTask.run(Unknown Source)
 12:20:29  at

[JIRA] (JENKINS-10880) Git plugin fails on remote Poll

2012-04-04 Thread y...@schli.ch (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161240#comment-161240
 ] 

Marc Günther commented on JENKINS-10880:


This only happens when you manually edit the config.xml files.

If you want to enable Fast Remote Polling, you can have only one branch, one 
repository, and you can not use any excluded regions, excluded users or 
submodules. Of course this is not documented anywhere.

Furthermore, if you DO enable it, and these requirements are not met, Jenkins 
silently disables it again, without telling you anything about it.

BUT, if you enable it manually by editing the config.xml, then Jenkins will NOT 
disable it. And then if you have more than one branch, the config will be in an 
inconsistent state, which Jenkins is not able to handle.

 Git plugin fails on remote Poll
 ---

 Key: JENKINS-10880
 URL: https://issues.jenkins-ci.org/browse/JENKINS-10880
 Project: Jenkins
  Issue Type: Bug
  Components: git
Affects Versions: current
Reporter: robertdw
Assignee: Kohsuke Kawaguchi
Priority: Minor

 If you enable remote polling in the Git Plugin, the project will never poll 
 successfully, and stops other projects polling as well.
 In GitSCM, requiresWorkspaceForPolling() returns false if remotePoll is 
 enabled.
 https://github.com/jenkinsci/git-plugin/blob/git-1.1.12/src/main/java/hudson/plugins/git/GitSCM.java#L582
 This mean that in the jenkins-core AbstractProject (at least on the LTS 
 branch), a null value is passed in for the workspace parameter to SCM.poll()
 https://github.com/jenkinsci/jenkins/blob/jenkins-1.409.1/core/src/main/java/hudson/model/AbstractProject.java#L1305
 This ends up in 'compareRemoteRevisionWith' back in GitSCM. At line 651, the 
 call to 'workingDirectory(workspace)' returns null - because null was passed 
 in as a param from AbstractProject. This means that at line 657, the call to 
 !!workingDirectory.exists() results in a null pointer.
 Suggested fix: remove the remotePoll, or make it require a workspace to do 
 the polling. 
 Stacktrace:
 Sep 2, 2011 2:41:50 PM hudson.triggers.SCMTrigger$Runner runPolling
 SEVERE: Failed to record SCM polling
 java.lang.NullPointerException
   at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:657)
   at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:354)
   at hudson.scm.SCM.poll(SCM.java:371)
   at hudson.model.AbstractProject.poll(AbstractProject.java:1305)
   at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
   at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
   at hudson.triggers.SCMTrigger.run(SCMTrigger.java:103)
   at hudson.triggers.SCMTrigger.run(SCMTrigger.java:83)
   at hudson.triggers.Trigger$1.run(Trigger.java:229)
   at hudson.DependencyRunner.run(DependencyRunner.java:73)
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
   at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
   at java.util.concurrent.FutureTask.run(FutureTask.java:138)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
   at java.lang.Thread.run(Thread.java:662)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13312) Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161242#comment-161242
 ] 

Rob Petti commented on JENKINS-13312:
-

Wait, sorry, I got my issues mixed up. Disregard that last comment.

Adding logging won't really help, since it's failing in core jenkins code. Do 
you really need to clear the workspace every time you build?

 Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue
 

 Key: JENKINS-13312
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13312
 Project: Jenkins
  Issue Type: Bug
  Components: perforce
 Environment: Jenkins 1.455
 Perforce plugin 1.38
Reporter: Thomas Fields
Assignee: Rob Petti

 Hi there,
 Occasionally some of my projects fail with the following callstack:
 {code}12:19:33  Started by an SCM change
 12:19:33  Building remotely on BuildSlave1 in workspace 
 c:\JCI\workspace\UnitTestsToolWin32-Release
 12:20:29  hudson.util.IOException2: remote file operation failed: 
 c:\JCI\workspace\UnitTestsToolWin32-Release\CONFIG at 
 hudson.remoting.Channel@586ca3ef:PhyreBuild1
 12:20:29  at hudson.FilePath.act(FilePath.java:784)
 12:20:29  at hudson.FilePath.act(FilePath.java:770)
 12:20:29  at hudson.FilePath.deleteRecursive(FilePath.java:854)
 12:20:29  at 
 hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:597)
 12:20:29  at 
 hudson.model.AbstractProject.checkout(AbstractProject.java:1197)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
 12:20:29  at 
 hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
 12:20:29  at hudson.model.Run.run(Run.java:1410)
 12:20:29  at hudson.matrix.MatrixBuild.run(MatrixBuild.java:253)
 12:20:29  at 
 hudson.model.ResourceController.execute(ResourceController.java:88)
 12:20:29  at hudson.model.Executor.run(Executor.java:238)
 12:20:29  at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
 12:20:29  Caused by: java.io.IOException: There are no more files
 12:20:29  at java.io.WinNTFileSystem.canonicalize0(Native Method)
 12:20:29  at java.io.Win32FileSystem.canonicalize(Unknown Source)
 12:20:29  at java.io.File.getCanonicalPath(Unknown Source)
 12:20:29  at java.io.File.getCanonicalFile(Unknown Source)
 12:20:29  at hudson.Util.isSymlink(Util.java:322)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:277)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.Util.deleteContentsRecursive(Util.java:198)
 12:20:29  at hudson.Util.deleteRecursive(Util.java:278)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:856)
 12:20:29  at hudson.FilePath$9.invoke(FilePath.java:854)
 12:20:29  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2099)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:118)
 12:20:29  at hudson.remoting.UserRequest.perform(UserRequest.java:48)
 12:20:29  at hudson.remoting.Request$2.run(Request.java:287)
 12:20:29  at 
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
 12:20:29  at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
 12:20:29  at java.util.concurrent.FutureTask.run(Unknown Source)
 12:20:29  at 
 java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown

[JIRA] (JENKINS-11749) Included regions feature for GitSCM plugin

2012-04-04 Thread blatinvill...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161243#comment-161243
 ] 

Bertrand Latinville commented on JENKINS-11749:
---

I'm very interested in the Included regions feature for GitSCM plugin and have 
been testing it
via SCM polling and Git hook.

I could see that in some cases the jobs were not triggered whereas some changes 
have been made in the included regions.

After some more testing I discovered that if several commits are made, only the 
last commit seems to be taken into account.

Spying the gitcommand the plugin is using I could see : 

{code:xml}
git rev-parse --verify HEAD
git command : fetch -t https://url.git +refs/heads/*:refs/remotes/origin/* 
git tag -l master
git command : rev-parse origin/master^{commit} 
  - Gives the new SHA1
git command : show --no-abbrev --format=raw -M --raw 'new sha1' 
{code}
The last command shows only diff from latest sha1, should't it be something 
like : 
{code:xml}
git show --no-abbrev --format=raw -M --raw 'old sha1'..'new sha1' 
{code}
'old sha1' beeing the sha1 of the latest build.

Can you confirm there is a bug or have I something wrong in my setup ?

Thanks, 

Bertrand

 Included regions feature for GitSCM plugin
 --

 Key: JENKINS-11749
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11749
 Project: Jenkins
  Issue Type: New Feature
  Components: git
Affects Versions: current
Reporter: Juerg Haefliger
Assignee: Juerg Haefliger
Priority: Minor

 For having several regions to be excluded from build its better to filter the 
 building process only for some included regions.
 [Description copied from http://issues.hudson-ci.org/browse/HUDSON-7294]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-8326) Support for ratcheting

2012-04-04 Thread robertjhun...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-8326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161244#comment-161244
 ] 

Rob Hunter commented on JENKINS-8326:
-

I'd also like to have support for failing the build when the coverage gets 
worse than it was.

I've been looking at different options like:
 * post-build script to re-configure thresholds with Groovy
 * post-build script to re-configure thresholds with HTTP API
 * thresholds use variables ${COBERTURA_MIN_METHOD_COVERAGE} or something

It'd be super-nice if the Cobertura plugin supported ratcheting limits like 
this but I'd be happy if it were obvious how to source the thresholds from 
anywhere other than a fixed value in the Web interface.


(FWIW, I don't think this is a duplicate of JENKINS-11025 -- that only covers 
static thresholds, this ticket covers dynamic thresholds)

 Support for ratcheting
 --

 Key: JENKINS-8326
 URL: https://issues.jenkins-ci.org/browse/JENKINS-8326
 Project: Jenkins
  Issue Type: New Feature
  Components: cobertura
Reporter: johnsmart
Assignee: stephenconnolly

 It would be very useful to add support for ratcheting. This would involve 
 making the build job fail or become unstable if the code coverage for a build 
 drops below the code coverage of the previous build. The plugin could keep 
 track of the highest code coverage metrics values from previous builds, and 
 check against this. If the current results are lower, the build fails. If 
 not, the latest values are stored as the new reference values.
 This is very useful for legacy projects, where you want to adopt a Continuous 
 Improvement strategy rather than just imposing a minimum required level of 
 test coverage.
 Thoughts?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13114) dropdown views taskbar: error when saving jenkins config page


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161245#comment-161245
 ] 

Jim Searle commented on JENKINS-13114:
--

Same problem with Jenkins 1.458.  It works in IE 7.0, FF 3.6.  Fails in FF 11.0 
and Chrome 18.0.


 dropdown views taskbar: error when saving jenkins config page
 -

 Key: JENKINS-13114
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13114
 Project: Jenkins
  Issue Type: Bug
  Components: dropdown-viewstabbar
Affects Versions: current
Reporter: Steve Roth
Assignee: jieryn

 I have the dropdown views tabbar enabled, and am usign Jenkins 1.455   When I 
 go to save the main Jenkins config page, I see this CNF exception in the 
 browser:
 exception
 javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to 
 instantiate class hudson.views.ViewsTabBar from 
 {showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
   org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:605)
   org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
   org.kohsuke.stapler.Stapler.service(Stapler.java:159)
   javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
   hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
   net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
   net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
   
 net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
   
 org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
   hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   
 hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
   hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   
 oracle.boulderlabs.jenkins.validatorkiller.ValidatorKiller.doFilter(ValidatorKiller.java:63)
   hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
   hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
   
 hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   
 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   
 org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   
 org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   
 org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   
 org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:61)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   
 org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
   
 hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:66)
   
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   
 hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
   hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
   
 hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
 root cause
 java.lang.IllegalArgumentException: Failed to instantiate class 
 hudson.views.ViewsTabBar from 
 {showJobCount:false,stapler-class:[hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
   
 org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
   org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
   org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)

[JIRA] (JENKINS-13198) Saving jenkins config with dropdown views plugin causes json error


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161246#comment-161246
 ] 

Jim Searle commented on JENKINS-13198:
--

Should this be closed as a duplicate to 
https://issues.jenkins-ci.org/browse/JENKINS-13114 ?


 Saving jenkins config with dropdown views plugin causes json error
 --

 Key: JENKINS-13198
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13198
 Project: Jenkins
  Issue Type: Bug
  Components: core, dropdown-viewstabbar
 Environment: jenkins 1.456
 dropdown views tabbar plugin  (latest)
Reporter: Marc Robinson
Assignee: jieryn

 Status Code: 500
 Exception: 
 Stacktrace:
 java.lang.IllegalArgumentException: Failed to instantiate class 
 hudson.views.ViewsTabBar from 
 {showJobCount:false,stapler-class:[ws.albors.CountJobsViewsTabBar,hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
   at 
 org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
   at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
   at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
   at 
 hudson.views.ViewsTabBar$GlobalConfigurationImpl.configure(ViewsTabBar.java:84)
   at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2620)
   at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2583)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
   at 
 org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
   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:95)
   at 
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
   at 
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
   at 
 net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
   at 
 org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at 
 hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at 
 hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at 
 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at 
 org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at

[JIRA] (JENKINS-13198) Saving jenkins config with dropdown views plugin causes json error

2012-04-04 Thread jie...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161247#comment-161247
 ] 

jieryn commented on JENKINS-13198:
--

Yah, but JIRA is taking an error when trying to close the issue... so we're 
stuck.

 Saving jenkins config with dropdown views plugin causes json error
 --

 Key: JENKINS-13198
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13198
 Project: Jenkins
  Issue Type: Bug
  Components: core, dropdown-viewstabbar
 Environment: jenkins 1.456
 dropdown views tabbar plugin  (latest)
Reporter: Marc Robinson
Assignee: jieryn

 Status Code: 500
 Exception: 
 Stacktrace:
 java.lang.IllegalArgumentException: Failed to instantiate class 
 hudson.views.ViewsTabBar from 
 {showJobCount:false,stapler-class:[ws.albors.CountJobsViewsTabBar,hudson.views.DefaultViewsTabBar,hudson.views.tabbar.DropDownViewsTabBar]}
   at 
 org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:633)
   at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:377)
   at org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:373)
   at 
 hudson.views.ViewsTabBar$GlobalConfigurationImpl.configure(ViewsTabBar.java:84)
   at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2620)
   at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2583)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
   at java.lang.reflect.Method.invoke(Method.java:597)
   at 
 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
   at 
 org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:563)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
   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:95)
   at 
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:185)
   at 
 net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:159)
   at 
 net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
   at 
 org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at 
 hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:74)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at 
 hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at 
 org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at 
 org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
   at

[JIRA] (JENKINS-13348) EnvInject overriding WORKSPACE variable

Jim Searle created JENKINS-13348:


 Summary: EnvInject overriding WORKSPACE variable
 Key: JENKINS-13348
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13348
 Project: Jenkins
  Issue Type: Bug
  Components: envinject
Affects Versions: current
Reporter: Jim Searle
Assignee: gbois
Priority: Blocker


I upgraded Jenkins to 1.458 and envinject from 1.36 to 1.44.  After the upgrade 
all my jobs that did not use envinject were getting their WORKSPACE variable 
set to another jobs that did use envinject WORKSPACE.  Downgraded envinject to 
1.36 and the problem went away.

Here's an edited log that shows initially the workspace is correct, even after 
EnvInject line, but when the shell script runs, it is wrong.

Also, I don't know why EnvInject is even being run for this job since it is not 
enabled anywhere...

[EnvInject] - Preparing an environment for the build.
Building on master in workspace --correct-workspace--
Updating http://svn
At revision 36652
no change for http://svn since the previous build
No emails were triggered.
[bronze-bin] $ /bin/sh -xe /tmp/hudson6983282044770433158.sh
+ echo --some-other-jobs-workspace--


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-12514) .hpi versus .jpi causes inability to upgrade Subversion Plugin

2012-04-04 Thread reynald.bo...@gmail.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-12514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161248#comment-161248
 ] 

Reynald Borer commented on JENKINS-12514:
-

Still happening with Jenkins 1.458 running under debian squeeze (with the 
debian package).

 .hpi versus .jpi causes inability to upgrade Subversion Plugin
 --

 Key: JENKINS-12514
 URL: https://issues.jenkins-ci.org/browse/JENKINS-12514
 Project: Jenkins
  Issue Type: Bug
  Components: update-center
 Environment: Ubuntu 11.10, OpenJDK 1.6.0_23, Tomcat 7.0.21, Jenkins 
 1.448  1.449
 Jenkins 1.456 on Windows Server 2003 64-bit, Sun JDK 6.0.260.3
Reporter: Charlie Huggard
Assignee: Kohsuke Kawaguchi
Priority: Blocker

 Reproduction:
 $JENKINS_HOME/plugins: subversion (directory), subversion.hpi
 1) Open http://root/pluginManager. Update Subversion plugin from 1.34 - 
 1.37 using download now and install after restart button.
 $JENKINS_HOME/plugins: subversion (directory), subversion.bak (1.34), 
 subversion.hpi.pinned, subversion.jpi (1.37)
 2) Restart Tomcat/Jenkins
 $JENKINS_HOME/plugins: subversion (directory), subversion.bak (1.34), 
 subversion.hpi (1.34) subversion.hpi.pinned, subversion.jpi (1.37)
 3) PluginManager still reports old version 
 Should note that the logs report:
 INFO: Ignoring /ci/jenkins-home/plugins/subversion.jpi because 
 /ci/jenkins-home/plugins/subversion.hpi is already loaded
 Also the plugin is broken at this point with a NoClassDefFound on 
 org/tmatesoft/svn/core/SVNException 
 Clean State: 
 1) /etc/init.d/tomcat7 stop
 2) cd $JENKINS_HOME/plugins
 3) rm subversion*
 4) /etc/init.d/tomcat7 start
 Workaround:
 1) Restore clean state
 2) Update plugin
 3) Stop tomcat/jenkins
 4) cd $JENKINS_HOME/plugins
 5) mv subversion.jpi subversion.hpi
 6) Start tomcat/jenkins

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13349) Time out clock refresh after output

2012-04-04 Thread nickbmar...@gmail.com (JIRA)

nicholas blasingame created JENKINS-13349:
-

 Summary: Time out clock refresh after output
 Key: JENKINS-13349
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13349
 Project: Jenkins
  Issue Type: New Feature
  Components: build-timeout
 Environment: windows 7, msvc 9.0 build system.
Reporter: nicholas blasingame
Assignee: kohsuke_agent
Priority: Minor


It would be a nice feature to have a clock refresh every time there is output. 

This is useful since our code grows and builds take longer and longer each day. 
Thus it would require tests' time out time to be adjusted frequently.

Rather it would be nice for the time out counter to refresh every time output 
is displayed. 

So, if a test were to time out after 20 minutes it would be 20 minutes AFTER 
last std output.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13349) Time out clock refresh after output

2012-04-04 Thread nickbmar...@gmail.com (JIRA)


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

nicholas blasingame updated JENKINS-13349:
--

Assignee: Kohsuke Kawaguchi  (was: kohsuke_agent)

 Time out clock refresh after output
 ---

 Key: JENKINS-13349
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13349
 Project: Jenkins
  Issue Type: New Feature
  Components: build-timeout
 Environment: windows 7, msvc 9.0 build system.
Reporter: nicholas blasingame
Assignee: Kohsuke Kawaguchi
Priority: Minor

 It would be a nice feature to have a clock refresh every time there is 
 output. 
 This is useful since our code grows and builds take longer and longer each 
 day. 
 Thus it would require tests' time out time to be adjusted frequently.
 Rather it would be nice for the time out counter to refresh every time output 
 is displayed. 
 So, if a test were to time out after 20 minutes it would be 20 minutes AFTER 
 last std output.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13322) Configure tab freezes when using both the HTML5 notifier plugin and the Android Emulator Plugin


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161249#comment-161249
 ] 

Christopher Orr commented on JENKINS-13322:
---

The HTML5 Notifier Plugin is including prototype-1.7.js into the 
configuration page which appears to prevent the Form.findMatchingInput method 
in hudson-behavior.js to stop working, which breaks the Android Emulator Plugin.

When I removed prototype-1.7.js, the job configuration page loaded properly 
again.

This is related, in some way, to JENKINS-11618.

 Configure tab freezes when using both the HTML5 notifier plugin and the 
 Android Emulator Plugin
 ---

 Key: JENKINS-13322
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13322
 Project: Jenkins
  Issue Type: Bug
  Components: android-emulator, html5-notifier
 Environment: Mac OS X
Reporter: Johannes Pelto-Piri
Assignee: Christopher Orr

 When trying to configure a job with both the HTML5 notifier plugin and the 
 Android Emulator plugin the job configuration wont load. I tried again in a 
 fresh installation and installed the plugins separately and the issue 
 remained. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13214) Tests with the same name are no longer reported in the test results

2012-04-04 Thread ku...@gmx.de (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161250#comment-161250
]

kutzi commented on JENKINS-13214:
-

Do you have a 'real-world' example of a testresult.xml?

Tests with the same name are no longer reported in the test results
---

Key: JENKINS-13214
URL: https://issues.jenkins-ci.org/browse/JENKINS-13214
Project: Jenkins
Issue Type: Bug
Components: maven2
Affects Versions: current
Reporter: ajbanck
Assignee: kutzi

[JIRA] (JENKINS-13322) Configure tab freezes when using both the HTML5 notifier plugin and the Android Emulator Plugin


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161249#comment-161249
 ] 

Christopher Orr edited comment on JENKINS-13322 at 4/4/12 6:02 PM:
---

The HTML5 Notifier Plugin is including prototype-1.7.js into the 
configuration page which appears to prevent the Form.findMatchingInput method 
in hudson-behavior.js from working properly, which breaks the Android Emulator 
Plugin.

When I removed prototype-1.7.js, the job configuration page loaded properly 
again.

This is related, in some way, to JENKINS-11618.

  was (Author: orrc):
The HTML5 Notifier Plugin is including prototype-1.7.js into the 
configuration page which appears to prevent the Form.findMatchingInput method 
in hudson-behavior.js to stop working, which breaks the Android Emulator Plugin.

When I removed prototype-1.7.js, the job configuration page loaded properly 
again.

This is related, in some way, to JENKINS-11618.
  
 Configure tab freezes when using both the HTML5 notifier plugin and the 
 Android Emulator Plugin
 ---

 Key: JENKINS-13322
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13322
 Project: Jenkins
  Issue Type: Bug
  Components: android-emulator, html5-notifier
 Environment: Mac OS X
Reporter: Johannes Pelto-Piri
Assignee: Christopher Orr

 When trying to configure a job with both the HTML5 notifier plugin and the 
 Android Emulator plugin the job configuration wont load. I tried again in a 
 fresh installation and installed the plugins separately and the issue 
 remained. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-11618) Prototype 1.7 is missing the instance 'toJSON' method


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11618?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161251#comment-161251
 ] 

Christopher Orr commented on JENKINS-11618:
---

JENKINS-13322 seems to relate to the use of prototype-1.7.js in this plugin.

Any ideas?  I tested on Jenkins 1.458.

 Prototype 1.7 is missing the instance 'toJSON' method
 -

 Key: JENKINS-11618
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11618
 Project: Jenkins
  Issue Type: Bug
  Components: html5-notifier
Affects Versions: current
 Environment: n/a
Reporter: Dan Savilonis
Assignee: jieryn
Priority: Blocker

 When the html5-notifier plugin is enabled, you cannot save a job with more 
 than one build step. To reproduce, install the plugin and add a new job with 
 two windows batch file or shell script build steps. If only one is created, 
 it will save, but if two are created, you will see an error like the 
 following:
 Failed to parse form data. Please report this problem as a bug
 JSON={:,builder:\[{\command\:\bar\,\stapler-class\:\hudson.tasks.Shell\,\kind\:\hudson.tasks.Shell\},
  {\command\:\cd 
 foo\,\stapler-class\:\hudson.tasks.Shell\,\kind\:\hudson.tasks.Shell\}]\,description:,hasSlaveAffinity:{assignedLabelString:windowsexpander},name:debug_job2,properties:{hudson-model-ParametersDefinitionProperty:{},hudson-plugins-batch_task-BatchTaskProperty:{},stapler-class-bag:true},scm:{value:3}}
 net.sf.json.JSONException: A JSONArray text must start with '[' at character 
 1 of [{command:cd 
 bar,stapler-class:hudson.tasks.Shell,kind:hudson.tasks.Shell}, 
 {command:cd 
 foo,stapler-class:hudson.tasks.Shell,kind:hudson.tasks.Shell}]
   at net.sf.json.util.JSONTokener.syntaxError(JSONTokener.java:512)
   at net.sf.json.JSONArray._fromJSONTokener(JSONArray.java:903)
   at net.sf.json.JSONArray._fromString(JSONArray.java:983)
   at net.sf.json.JSONArray.fromObject(JSONArray.java:141)
   at net.sf.json.JSONArray.fromObject(JSONArray.java:120)
   at 
 hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:863)
   at 
 hudson.model.Descriptor.newInstancesFromHeteroList(Descriptor.java:853)
   at hudson.util.DescribableList.rebuildHetero(DescribableList.java:185)
   at hudson.model.Project.submit(Project.java:197)
   at hudson.model.Job.doConfigSubmit(Job.java:966)
   at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:643)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282)
   at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:149)
   at 
 org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:88)
   at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:104)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
   at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:234)
   at 
 org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
   at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:561)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:646)
   at org.kohsuke.stapler.Stapler.invoke(Stapler.java:477)
   at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
   at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
   at winstone.ServletConfiguration.execute(ServletConfiguration.java:249)
   at winstone.RequestDispatcher.forward(RequestDispatcher.java:335)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378)
   at 
 hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
   at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
   at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
   at winstone.FilterConfiguration.execute(FilterConfiguration.java:195)
   at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368)
   at 
 hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
   at 
 hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
   at

[JIRA] (JENKINS-13322) Configure tab freezes when using both the HTML5 notifier plugin and the Android Emulator Plugin


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161252#comment-161252
 ] 

Christopher Orr commented on JENKINS-13322:
---

In Jenkins 1.458, the Chrome JS console reports the following error and the 
Loading overlay remains in place:

{noformat}
Uncaught TypeError: Object #Object has no method 'findMatchingInput'
  (anonymous function)
  e.targetUrl   hudson-behavior.js:339
  registerValidator hudson-behavior.js:344
  apply behavior.js:73
  (anonymous function)  behavior.js:79
  Behaviour.applySubtreebehavior.js:68
  Behaviour.apply   behavior.js:54
  (anonymous function)  behavior.js:49
  window.onload behavior.js:92
{noformat}

 Configure tab freezes when using both the HTML5 notifier plugin and the 
 Android Emulator Plugin
 ---

 Key: JENKINS-13322
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13322
 Project: Jenkins
  Issue Type: Bug
  Components: android-emulator, html5-notifier
 Environment: Mac OS X
Reporter: Johannes Pelto-Piri
Assignee: Christopher Orr

 When trying to configure a job with both the HTML5 notifier plugin and the 
 Android Emulator plugin the job configuration wont load. I tried again in a 
 fresh installation and installed the plugins separately and the issue 
 remained. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13350) Static Code Analysis Plug-ins: Failed to install

2012-04-04 Thread ta...@addlabs.uff.br (JIRA)

Tácio Diogo created JENKINS-13350:
-

 Summary: Static Code Analysis Plug-ins: Failed to install
 Key: JENKINS-13350
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13350
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-core
 Environment: Windows XP x86
Reporter: Tácio Diogo
Assignee: Tácio Diogo


When trying to install DRY Plugin, the installation of its dependency Static 
Code Analysis Plug-ins failed.
This is the error message:

hudson.util.IOException2: Failed to dynamically deploy this plugin
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1138)
at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:956)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown 
Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: hudson.util.IOException2: Failed to expand C:\Documents and 
Settings\ADDLabs\.jenkins\plugins\analysis-core.jpi
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:399)
at 
hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:113)
at hudson.PluginManager.dynamicLoad(PluginManager.java:352)
at 
hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1134)
... 7 more
Caused by: Error while expanding C:\Documents and 
Settings\ADDLabs\.jenkins\plugins\analysis-core.jpi
java.util.zip.ZipException: archive is not a ZIP archive
at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:192)
at org.apache.tools.ant.taskdefs.Expand.execute(Expand.java:132)
at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:397)
... 10 more
Caused by: java.util.zip.ZipException: archive is not a ZIP archive
at 
org.apache.tools.zip.ZipFile.positionAtCentralDirectory(ZipFile.java:481)
at 
org.apache.tools.zip.ZipFile.populateFromCentralDirectory(ZipFile.java:320)
at org.apache.tools.zip.ZipFile.init(ZipFile.java:186)
at org.apache.tools.ant.taskdefs.Expand.expandFile(Expand.java:170)
... 12 more

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays


[ 
https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161253#comment-161253
 ] 

SCM/JIRA link daemon commented on JENKINS-10319:


Code changed in jenkins
User: Ulli Hafner
Path:
 
src/main/java/hudson/plugins/analysis/dashboard/AbstractWarningsGraphPortlet.java
 
src/main/java/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet.java
 
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/config.jelly
 
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/config_de.properties
 
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/config_ja.properties
http://jenkins-ci.org/commit/analysis-core-plugin/f019f54ffd0fc42e26121bd15b294519b0ff9b4e
Log:
  [JENKINS-10319] Make parser a parameter of each warning portlet.


Compare: 
https://github.com/jenkinsci/analysis-core-plugin/compare/efc06e4...f019f54



 Ability to change the name Compiler as seen in a lot of the displays
 --

 Key: JENKINS-10319
 URL: https://issues.jenkins-ci.org/browse/JENKINS-10319
 Project: Jenkins
  Issue Type: New Feature
  Components: warnings
Reporter: Nigel Robbins
Assignee: Ulli Hafner
Priority: Minor
 Attachments: compilerWarningsBuild.png, compilerWarningsIcon.png, 
 compilerWarningsList.png, compilerWarningsTrend.png


 Hi,
 Would it be possible to configure the label Compiler Warnings.
 I am using the Warnings plugin to show FlawFinder issues.
 Seeing text like FlawFinder Warnings or maybe FlawFinder Issues would 
 enhance my display.
 Can the parser name (e.g. FlawFinder in my case) be used instead of the text 
 Compiler ?
 Or, maybe the ability to change the label Compiler Warnings to something 
 else ?
 I can see the text Compiler Warnings in a number of places which I've 
 attached screenshots of. The Compiler Warnings text may also appear 
 elsewhere. 
 Great plugin by the way !
 Many thanks,
 Nigel

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays


[ 
https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161254#comment-161254
 ] 

SCM/JIRA link daemon commented on JENKINS-10319:


Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/warnings/WarningsProjectAction.java
 src/main/java/hudson/plugins/warnings/dashboard/AbstractTrendPortlet.java
 src/main/java/hudson/plugins/warnings/dashboard/ActionSelector.java
 
src/main/java/hudson/plugins/warnings/dashboard/WarningsNewVersusFixedGraphPortlet.java
 
src/main/java/hudson/plugins/warnings/dashboard/WarningsPriorityGraphPortlet.java
 src/main/java/hudson/plugins/warnings/dashboard/WarningsTablePortlet.java
 
src/main/resources/hudson/plugins/warnings/dashboard/WarningsNewVersusFixedGraphPortlet/WarningsGraphDescriptor/local-config.jelly
 
src/main/resources/hudson/plugins/warnings/dashboard/WarningsPriorityGraphPortlet/WarningsGraphDescriptor/local-config.jelly
 
src/main/resources/hudson/plugins/warnings/dashboard/WarningsTablePortlet/WarningsPerJobDescriptor/local-config.jelly
 src/main/resources/parser/parser.jelly
 src/main/resources/parser/parser.properties
 src/main/resources/parser/parser_de.properties
 src/main/resources/parser/taglib
http://jenkins-ci.org/commit/warnings-plugin/6ae185bca666f96fa34a925df75c16ce9052cb28
Log:
  [JENKINS-10319] Make parser a parameter of each warning portlet.






 Ability to change the name Compiler as seen in a lot of the displays
 --

 Key: JENKINS-10319
 URL: https://issues.jenkins-ci.org/browse/JENKINS-10319
 Project: Jenkins
  Issue Type: New Feature
  Components: warnings
Reporter: Nigel Robbins
Assignee: Ulli Hafner
Priority: Minor
 Attachments: compilerWarningsBuild.png, compilerWarningsIcon.png, 
 compilerWarningsList.png, compilerWarningsTrend.png


 Hi,
 Would it be possible to configure the label Compiler Warnings.
 I am using the Warnings plugin to show FlawFinder issues.
 Seeing text like FlawFinder Warnings or maybe FlawFinder Issues would 
 enhance my display.
 Can the parser name (e.g. FlawFinder in my case) be used instead of the text 
 Compiler ?
 Or, maybe the ability to change the label Compiler Warnings to something 
 else ?
 I can see the text Compiler Warnings in a number of places which I've 
 attached screenshots of. The Compiler Warnings text may also appear 
 elsewhere. 
 Great plugin by the way !
 Many thanks,
 Nigel

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13101) Analysis Collector Plugin prevents other plugins from loading when the Dashboard View Plugin is not installed


[ 
https://issues.jenkins-ci.org/browse/JENKINS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161255#comment-161255
 ] 

SCM/JIRA link daemon commented on JENKINS-13101:


Code changed in jenkins
User: Ulli Hafner
Path:
 
src/main/java/hudson/plugins/analysis/collector/dashboard/AnalysisGraphDescriptor.java
 
src/main/java/hudson/plugins/analysis/collector/dashboard/WarningsOriginGraphPortlet.java
 
src/main/java/hudson/plugins/analysis/collector/dashboard/WarningsTablePortlet.java
 src/main/resources/hudson/plugins/analysis/collector/Messages_fr.properties
http://jenkins-ci.org/commit/analysis-collector-plugin/9b7918907bf37ed25b4ba7e57ad825978df41e2e
Log:
  [FIXED JENKINS-13101] Don't use dashboard classes in abstract base
classes that do not define an extension.






 Analysis Collector Plugin prevents other plugins from loading when the 
 Dashboard View Plugin is not installed
 -

 Key: JENKINS-13101
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13101
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector
Affects Versions: current
 Environment: Jenkins ver. 1.455
 Analysis Collector 1.20
 Tomcat 6 
Reporter: Martin Ziel
Assignee: Ulli Hafner
  Labels: exception, plugin
 Attachments: jenkins.log


 The Analysis Collector Plugin prevents other plugins from loading when the 
 Dashboard View Plugin is not installed and activated. In my case, this 
 effectively disables the SCM Plugins and thus prevents Jenkins from fetching 
 SCM changes. Log attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13101) Analysis Collector Plugin prevents other plugins from loading when the Dashboard View Plugin is not installed


 [ 
https://issues.jenkins-ci.org/browse/JENKINS-13101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

SCM/JIRA link daemon resolved JENKINS-13101.


Resolution: Fixed

 Analysis Collector Plugin prevents other plugins from loading when the 
 Dashboard View Plugin is not installed
 -

 Key: JENKINS-13101
 URL: https://issues.jenkins-ci.org/browse/JENKINS-13101
 Project: Jenkins
  Issue Type: Bug
  Components: analysis-collector
Affects Versions: current
 Environment: Jenkins ver. 1.455
 Analysis Collector 1.20
 Tomcat 6 
Reporter: Martin Ziel
Assignee: Ulli Hafner
  Labels: exception, plugin
 Attachments: jenkins.log


 The Analysis Collector Plugin prevents other plugins from loading when the 
 Dashboard View Plugin is not installed and activated. In my case, this 
 effectively disables the SCM Plugins and thus prevents Jenkins from fetching 
 SCM changes. Log attached.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-10319) Ability to change the name Compiler as seen in a lot of the displays

2012-04-04 Thread dogf...@java.net (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-10319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161256#comment-161256
 ] 

dogfood commented on JENKINS-10319:
---

Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! 
[plugins_analysis-core 
#10432|http://ci.jenkins-ci.org/job/plugins_analysis-core/10432/]
 [JENKINS-10319] Make parser a parameter of each warning portlet. (Revision 
f019f54ffd0fc42e26121bd15b294519b0ff9b4e)

 Result = SUCCESS
Ulli Hafner : 
Files : 
* 
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/config_de.properties
* 
src/main/java/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet.java
* 
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/config_ja.properties
* 
src/main/resources/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet/config.jelly
* 
src/main/java/hudson/plugins/analysis/dashboard/AbstractWarningsGraphPortlet.java


 Ability to change the name Compiler as seen in a lot of the displays
 --

 Key: JENKINS-10319
 URL: https://issues.jenkins-ci.org/browse/JENKINS-10319
 Project: Jenkins
  Issue Type: New Feature
  Components: warnings
Reporter: Nigel Robbins
Assignee: Ulli Hafner
Priority: Minor
 Attachments: compilerWarningsBuild.png, compilerWarningsIcon.png, 
 compilerWarningsList.png, compilerWarningsTrend.png


 Hi,
 Would it be possible to configure the label Compiler Warnings.
 I am using the Warnings plugin to show FlawFinder issues.
 Seeing text like FlawFinder Warnings or maybe FlawFinder Issues would 
 enhance my display.
 Can the parser name (e.g. FlawFinder in my case) be used instead of the text 
 Compiler ?
 Or, maybe the ability to change the label Compiler Warnings to something 
 else ?
 I can see the text Compiler Warnings in a number of places which I've 
 attached screenshots of. The Compiler Warnings text may also appear 
 elsewhere. 
 Great plugin by the way !
 Many thanks,
 Nigel

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

[JIRA] (JENKINS-13325) PYTHONPATH gets undefined with latest 1.44 version of EnvInject

2012-04-04 Thread gb...@java.net (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161260#comment-161260
]

gbois commented on JENKINS-13325:
-

Could you try to reproduce it in on an isolated environment?
I tested in my context and it is OK.
Thanks

PYTHONPATH gets undefined with latest 1.44 version of EnvInject
---

Key: JENKINS-13325
URL: https://issues.jenkins-ci.org/browse/JENKINS-13325
Project: Jenkins
Issue Type: Bug
Components: envinject
Environment: Jenkins 1.457, Windows master, Linux slave
Reporter: Marc Sanfacon
Assignee: gbois
Attachments: BuildFingerprint.txt, config.xml

We are using envinject on our Linux slave. With version 1.36, we get the
following behavior:
08:51:39 [EnvInject] - Injecting environment variables from a build step.
08:51:39 [EnvInject] - Injecting as environment variables the properties
file path 'BuildFingerprint.txt'
08:51:39 [EnvInject] - Variables injected successfully.
08:51:39 [EnvInject] - Unset unresolved 'SRC_SHARED' variable.
08:51:39 [EnvInject] - Unset unresolved 'PATH' variable.
08:51:39 [EnvInject] - Unset unresolved 'NEWSCP' variable.
08:51:39 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
08:51:39 [EnvInject] - Unset unresolved 'TEMP' variable.
But somehow, the variable PYTHONPATH is still set afterwards since we call a
script found in the path and it works.
With version 1.44, we get this:
08:49:16 [EnvInject] - Injecting environment variables from a build step.
08:49:16 [EnvInject] - Injecting as environment variables the properties
file path 'BuildFingerprint.txt'
08:49:16 [EnvInject] - Variables injected successfully.
08:49:16 [EnvInject] - Unset unresolved 'PYTHONPATH' variable.
Only PYTHONPATH gets undefined, but it really is. The next build step fails
when calling the script because it is not found in the path.
I don't know what changed between the builds, but reverting the plugin fixed
it.
Also, why does EnvInject undefines other variables? All I want is for it to
inject the variables I asked. The ini files does not contain PYTHONPATH.

[JIRA] (JENKINS-13348) EnvInject overriding WORKSPACE variable

2012-04-04 Thread gb...@java.net (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Work on JENKINS-13348 started by gbois.

EnvInject overriding WORKSPACE variable
---

Key: JENKINS-13348
URL: https://issues.jenkins-ci.org/browse/JENKINS-13348
Project: Jenkins
Issue Type: Bug
Components: envinject
Affects Versions: current
Reporter: Jim Searle
Assignee: gbois
Priority: Blocker

I upgraded Jenkins to 1.458 and envinject from 1.36 to 1.44. After the
upgrade all my jobs that did not use envinject were getting their WORKSPACE
variable set to another jobs that did use envinject WORKSPACE. Downgraded
envinject to 1.36 and the problem went away.
Here's an edited log that shows initially the workspace is correct, even
after EnvInject line, but when the shell script runs, it is wrong.
Also, I don't know why EnvInject is even being run for this job since it is
not enabled anywhere...
[EnvInject] - Preparing an environment for the build.
Building on master in workspace --correct-workspace--
Updating http://svn
At revision 36652
no change for http://svn since the previous build
No emails were triggered.
[bronze-bin] $ /bin/sh -xe /tmp/hudson6983282044770433158.sh
+ echo --some-other-jobs-workspace--

[JIRA] (JENKINS-13348) EnvInject overriding WORKSPACE variable

2012-04-04 Thread gb...@java.net (JIRA)

[
https://issues.jenkins-ci.org/browse/JENKINS-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161261#comment-161261
]

gbois commented on JENKINS-13348:
-

Strange behavior.
I don't know where it is from and I can't reproduce it.
Could you try to isolate it?
Are your sure?

EnvInject overriding WORKSPACE variable
---

[JIRA] (JENKINS-13348) EnvInject overriding WORKSPACE variable

[
https://issues.jenkins-ci.org/browse/JENKINS-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161262#comment-161262
]

Jim Searle commented on JENKINS-13348:
--

Thanks. I am sure... I will try something on our test server and get back to
you.

EnvInject overriding WORKSPACE variable
---

[JIRA] (JENKINS-11945) Invalid combination filter groovy script in matrix project build handled badly

2012-04-04 Thread doug.b...@integware.com (JIRA)


[ 
https://issues.jenkins-ci.org/browse/JENKINS-11945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=161263#comment-161263
 ] 

Doug Borg commented on JENKINS-11945:
-

The other thing that is not clear about defining the filters is how you specify 
multiple filters. Are you supposed to put them all in one line in one big 
expression? Can they be whitespace separated, etc.? It might be good to allow 
multiple line entry and possibly have some configurable way to AND or OR the 
filters together.

 Invalid combination filter groovy script in matrix project build handled badly
 --

 Key: JENKINS-11945
 URL: https://issues.jenkins-ci.org/browse/JENKINS-11945
 Project: Jenkins
  Issue Type: Bug
  Components: matrix
Affects Versions: current
 Environment: Jenkins 1.441 Ubuntu 10.04
Reporter: Richard Mortimer

 I inadvertantly set an invalid combination filter script for a Matrix based 
 job. When I clicked save on the configuration I got a 500 error code 
 informing me of the error but a back/reload seemed to show that the 
 configuration was ok (I assumed it had not been saved).
 At this stage I restarted jenkins and after the restart the Matrix job was no 
 longer listed in the Job list. The Manage Jenkins screen did have any 
 warnings of error in configuration. I was able to restore the job be manually 
 editing the config.xml and restarting Jenkins but this is clearly not ideal 
 behaviour.
 I don't have a minimal configuration file as an example but the configuration 
 is fairly simple.
 I had a user defined axis for  screenres with values WVGA, WXGA and WYGA. 
 The combination filter had a typo in the name of screen res and included  
 (screemres==WYGA) not the 'm' instead lf 'n' in screenres,
 A failure to evaluate/parse the combination filter will likely need handling 
 gracefully in:
 * save/display of the configuration
 * load of configuration at startup time
 * build of a project with a broken combination filter.
 Initial configuration save 500 error stack trace below. Also included is the 
 configuration load error in the jenkins.log from the restart.
 {code}
 Status Code: 500
 Exception:
 Stacktrace:
 groovy.lang.MissingPropertyException: No such property: screemres for class: 
 Script1
   at 
 org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)
   at 
 org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49)
   at 
 org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231)
   at Script1$_run_closure1.doCall(Script1.groovy:1)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
   at 
 org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
   at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
   at 
 org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.callCurrent(PogoMetaClassSite.java:66)
   at 
 org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46)
   at 
 org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:133)
   at 
 org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:141)
   at Script1$_run_closure1.doCall(Script1.groovy)
   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
   at 
 sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
   at 
 sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
   at java.lang.reflect.Method.invoke(Method.java:616)
   at 
 org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
   at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
   at 
 org.codehaus.groovy.runtime.metaclass.ClosureMetaClass.invokeMethod(ClosureMetaClass.java:272)
   at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:884)
   at groovy.lang.Closure.call(Closure.java:410)
   at groovy.lang.Closure.call(Closure.java:404)
   at 
 org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:106)
   at

[JIRA] (JENKINS-13057) Support for integrated changelists in Changes view