[JIRA] (JENKINS-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
[ https://issues.jenkins-ci.org/browse/JENKINS-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Ldap connection failed - jenkins loosing FQDN of ldap server > > > Key: JENKINS-13265 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13265 > Project: Jenkins > Issue Type: Bug > Components: active-directory >Affects Versions: current > Environment: Jenkins in all 1.4xx versions, Linux X86, SLES 10, > Apache Tomcat 7.0.14 >Reporter: Joern Muehlencord > Labels: ConnectExcetion, ldap, plugin > Attachments: exception.txt > > > Jenkins is configured to use LDAP login which works perfectly. After some > time - some times directly after restarting tomcat - the login fails. When > checking catalina.out the attached exception is thrown. The reason for the > failed login is clear - Jenkins is configured to connect to ldap.my.domain - > but when this happens Jenkins forgets "ldap" and tries to connect to > my.domain only - for sure this does not work as this is no valid host name. > To fix this, we need to restart Tomcat until it failes 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-13265) Ldap connection failed - jenkins loosing FQDN of ldap server
[ https://issues.jenkins-ci.org/browse/JENKINS-13265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13265 stopped by Joern Muehlencord. > Ldap connection failed - jenkins loosing FQDN of ldap server > > > Key: JENKINS-13265 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13265 > Project: Jenkins > Issue Type: Bug > Components: active-directory >Affects Versions: current > Environment: Jenkins in all 1.4xx versions, Linux X86, SLES 10, > Apache Tomcat 7.0.14 >Reporter: Joern Muehlencord > Labels: ConnectExcetion, ldap, plugin > Attachments: exception.txt > > > Jenkins is configured to use LDAP login which works perfectly. After some > time - some times directly after restarting tomcat - the login fails. When > checking catalina.out the attached exception is thrown. The reason for the > failed login is clear - Jenkins is configured to connect to ldap.my.domain - > but when this happens Jenkins forgets "ldap" and tries to connect to > my.domain only - for sure this does not work as this is no valid host name. > To fix this, we need to restart Tomcat until it failes 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-2295) Jenkins cannot handle modules added by profiles - if profile is not activated via '-P' (was: Assertion in MavenModuleSetBuild for aggregator POM with modules provided by profile)
[
https://issues.jenkins-ci.org/browse/JENKINS-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161457#comment-161457
]
Alon Barlev commented on JENKINS-2295:
--
Not sure if related or separate issue:
As a "maven2/3 project", if I have "-U clean deploy -P profile1,profile2" as my
goals and options, everything works fine.
If I replace that with "-U clean deploy -P ${profs}" and send down
"profile1,profile2" as a string parameter called "profs", I get a NPE (stack
trace below). If I run this as a free-style job, it works fine with the
parameter as well.
Some log output:
Executing Maven: -B -f d:\jenkins\workspace\sandbox\sandbox\pom.xml -U clean
deploy -P profile1,profile2 -Dprofs=profile1,profile2
...
mavenExecutionResult exceptions not empty
message : Internal error: java.lang.NullPointerException
cause : null
Stack trace :
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at
org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at
org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
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.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
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:619)
Caused by: java.lang.NullPointerException
at
hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted(Maven3Builder.java:286)
at
hudson.maven.Maven3Builder$MavenExecutionListener.projectStarted(Maven3Builder.java:276)
at
org.jfrog.build.extractor.maven.BuildInfoRecorder.projectStarted(BuildInfoRecorder.java:149)
at
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:71)
at
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:78)
... 24 more
> Jenkins cannot handle modules added by profiles - if profile is not activated
> via '-P' (was: Assertion in MavenModuleSetBuild for aggregator POM with
> modules provided by profile)
> --
>
> Key: JENKINS-2295
> URL: https://issues.jenkins-ci.org/browse/JENKINS-2295
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
>Affects Versions: current
> Environment: Platform: All, OS: All
>Reporter: tjuerge
> Attachments: testcase-build.log, testcase.tgz
>
>
> The root POM of one of our Maven2 projects aggregates sub-modules which are
> defined in a set of profiles. So within this POM there's no defined
> outside of a profile.
> Building this project from the commandline via "mvn -P,
> clean install" is working like a charme. But using the same commandline from
> within a H
[JIRA] (JENKINS-2295) Jenkins cannot handle modules added by profiles - if profile is not activated via '-P' (was: Assertion in MavenModuleSetBuild for aggregator POM with modules provided by profile)
[
https://issues.jenkins-ci.org/browse/JENKINS-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161457#comment-161457
]
Alon Barlev edited comment on JENKINS-2295 at 4/11/12 7:11 AM:
---
Not sure if related or separate issue:
As a "maven2/3 project", if I have "-U clean deploy -P profile1,profile2" as my
goals and options, everything works fine.
If I replace that with "-U clean deploy -P ${profs}" and send down
"profile1,profile2" as a string parameter called "profs", I get a NPE (stack
trace below). If I run this as a free-style job, it works fine with the
parameter as well.
Jenkins 1.459
Maven 3.0.4
JDK 1.6
Some log output:
Executing Maven: -B -f d:\jenkins\workspace\sandbox\sandbox\pom.xml -U clean
deploy -P profile1,profile2 -Dprofs=profile1,profile2
...
mavenExecutionResult exceptions not empty
message : Internal error: java.lang.NullPointerException
cause : null
Stack trace :
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at
org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:95)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at
org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79)
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.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239)
at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:104)
at hudson.maven.Maven3Builder.call(Maven3Builder.java:70)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
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:619)
Caused by: java.lang.NullPointerException
at
hudson.maven.Maven3Builder$MavenExecutionListener.recordProjectStarted(Maven3Builder.java:286)
at
hudson.maven.Maven3Builder$MavenExecutionListener.projectStarted(Maven3Builder.java:276)
at
org.jfrog.build.extractor.maven.BuildInfoRecorder.projectStarted(BuildInfoRecorder.java:149)
at
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:71)
at
org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:78)
... 24 more
was (Author: barlevalon):
Not sure if related or separate issue:
As a "maven2/3 project", if I have "-U clean deploy -P profile1,profile2" as my
goals and options, everything works fine.
If I replace that with "-U clean deploy -P ${profs}" and send down
"profile1,profile2" as a string parameter called "profs", I get a NPE (stack
trace below). If I run this as a free-style job, it works fine with the
parameter as well.
Some log output:
Executing Maven: -B -f d:\jenkins\workspace\sandbox\sandbox\pom.xml -U clean
deploy -P profile1,profile2 -Dprofs=profile1,profile2
...
mavenExecutionResult exceptions not empty
message : Internal error: java.lang.NullPointerException
cause : null
Stack trace :
org.apache.maven.InternalErrorException: Internal error:
java.lang.NullPointerException
at
org.apache.maven.lifecycle.internal.BuilderCommon.handleBuildError(BuilderCommon.java:128)
at
org.apache.maven.lifecycle.internal.LifecycleMo
[JIRA] (JENKINS-13150) 'FATAL: null' while looking for test results in JUnit classes
[
https://issues.jenkins-ci.org/browse/JENKINS-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161458#comment-161458
]
Jaroslavas D. commented on JENKINS-13150:
-
Hi, Bruno.
Everything works fine with new job! Thank You.
I think ticket can be closed :)
> 'FATAL: null' while looking for test results in JUnit classes
> -
>
> Key: JENKINS-13150
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13150
> Project: Jenkins
> Issue Type: Bug
> Components: testlink
>Reporter: Jaroslavas D.
>Assignee: Bruno P. Kinoshita
> Labels: junit, plugin, plugins
> Attachments: full-log.txt, jenkins.jpg, logg.txt, noStrategy.png,
> TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml,
> testlink.jpg, withStrategy.png
>
>
> h3.Testlink configuration:
> !testlink.jpg|thumbnail!
> h3.Jenkins configuration:
> !jenkins.jpg|thumbnail!
> h3.Jenkins job {color:red}*FAILS*{color}:
> {code}
> 08:23:20 Looking for the test results of TestLink test cases.
> 08:23:20
> 08:23:20 Looking for test results in JUnit classes.
> 08:23:20
> 08:23:21 FATAL: null
> 08:23:21 java.lang.NullPointerException
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138)
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99)
> 08:23:21 at
> hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159)
> 08:23:21 at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
> 08:23:21 at hudson.model.Build$RunnerImpl.build(Build.java:178)
> 08:23:21 at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
> 08:23:21 at hudson.model.Run.run(Run.java:1408)
> 08:23:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> 08:23:21 at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> 08:23:21 at hudson.model.Executor.run(Executor.java:238)
> {code}
> Full console out can be found [^full-log.txt]
> Also JUnit report is attached -
> [^TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml]
--
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-13150) 'FATAL: null' while looking for test results in JUnit classes
[
https://issues.jenkins-ci.org/browse/JENKINS-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JENKINS-13150 stopped by Bruno P. Kinoshita.
> 'FATAL: null' while looking for test results in JUnit classes
> -
>
> Key: JENKINS-13150
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13150
> Project: Jenkins
> Issue Type: Bug
> Components: testlink
>Reporter: Jaroslavas D.
>Assignee: Bruno P. Kinoshita
> Labels: junit, plugin, plugins
> Attachments: full-log.txt, jenkins.jpg, logg.txt, noStrategy.png,
> TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml,
> testlink.jpg, withStrategy.png
>
>
> h3.Testlink configuration:
> !testlink.jpg|thumbnail!
> h3.Jenkins configuration:
> !jenkins.jpg|thumbnail!
> h3.Jenkins job {color:red}*FAILS*{color}:
> {code}
> 08:23:20 Looking for the test results of TestLink test cases.
> 08:23:20
> 08:23:20 Looking for test results in JUnit classes.
> 08:23:20
> 08:23:21 FATAL: null
> 08:23:21 java.lang.NullPointerException
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138)
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99)
> 08:23:21 at
> hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159)
> 08:23:21 at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
> 08:23:21 at hudson.model.Build$RunnerImpl.build(Build.java:178)
> 08:23:21 at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
> 08:23:21 at hudson.model.Run.run(Run.java:1408)
> 08:23:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> 08:23:21 at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> 08:23:21 at hudson.model.Executor.run(Executor.java:238)
> {code}
> Full console out can be found [^full-log.txt]
> Also JUnit report is attached -
> [^TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml]
--
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-13150) 'FATAL: null' while looking for test results in JUnit classes
[
https://issues.jenkins-ci.org/browse/JENKINS-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno P. Kinoshita resolved JENKINS-13150.
--
Resolution: Fixed
Thanks for reporting Jaroslavas!
I will read more about XStream to see ways to maintain the backward
compatibility in new version (though I'm aware sometimes it's not possible :)
Have a good day!
> 'FATAL: null' while looking for test results in JUnit classes
> -
>
> Key: JENKINS-13150
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13150
> Project: Jenkins
> Issue Type: Bug
> Components: testlink
>Reporter: Jaroslavas D.
>Assignee: Bruno P. Kinoshita
> Labels: junit, plugin, plugins
> Attachments: full-log.txt, jenkins.jpg, logg.txt, noStrategy.png,
> TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml,
> testlink.jpg, withStrategy.png
>
>
> h3.Testlink configuration:
> !testlink.jpg|thumbnail!
> h3.Jenkins configuration:
> !jenkins.jpg|thumbnail!
> h3.Jenkins job {color:red}*FAILS*{color}:
> {code}
> 08:23:20 Looking for the test results of TestLink test cases.
> 08:23:20
> 08:23:20 Looking for test results in JUnit classes.
> 08:23:20
> 08:23:21 FATAL: null
> 08:23:21 java.lang.NullPointerException
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138)
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99)
> 08:23:21 at
> hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159)
> 08:23:21 at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
> 08:23:21 at hudson.model.Build$RunnerImpl.build(Build.java:178)
> 08:23:21 at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
> 08:23:21 at hudson.model.Run.run(Run.java:1408)
> 08:23:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> 08:23:21 at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> 08:23:21 at hudson.model.Executor.run(Executor.java:238)
> {code}
> Full console out can be found [^full-log.txt]
> Also JUnit report is attached -
> [^TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml]
--
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-13150) 'FATAL: null' while looking for test results in JUnit classes
[
https://issues.jenkins-ci.org/browse/JENKINS-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161459#comment-161459
]
Jaroslavas D. commented on JENKINS-13150:
-
Bruno, please, one more time ask someone to delete attachments: *full-log.txt*
and *TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml*
Thank You!
> 'FATAL: null' while looking for test results in JUnit classes
> -
>
> Key: JENKINS-13150
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13150
> Project: Jenkins
> Issue Type: Bug
> Components: testlink
>Reporter: Jaroslavas D.
>Assignee: Bruno P. Kinoshita
> Labels: junit, plugin, plugins
> Attachments: full-log.txt, jenkins.jpg, logg.txt, noStrategy.png,
> TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml,
> testlink.jpg, withStrategy.png
>
>
> h3.Testlink configuration:
> !testlink.jpg|thumbnail!
> h3.Jenkins configuration:
> !jenkins.jpg|thumbnail!
> h3.Jenkins job {color:red}*FAILS*{color}:
> {code}
> 08:23:20 Looking for the test results of TestLink test cases.
> 08:23:20
> 08:23:20 Looking for test results in JUnit classes.
> 08:23:20
> 08:23:21 FATAL: null
> 08:23:21 java.lang.NullPointerException
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138)
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99)
> 08:23:21 at
> hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159)
> 08:23:21 at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
> 08:23:21 at hudson.model.Build$RunnerImpl.build(Build.java:178)
> 08:23:21 at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
> 08:23:21 at hudson.model.Run.run(Run.java:1408)
> 08:23:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> 08:23:21 at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> 08:23:21 at hudson.model.Executor.run(Executor.java:238)
> {code}
> Full console out can be found [^full-log.txt]
> Also JUnit report is attached -
> [^TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml]
--
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-13408) Defects filter in plugin is not enough, e.g. the file filter is required.
[ https://issues.jenkins-ci.org/browse/JENKINS-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13408 stopped by Allen Xu. > Defects filter in plugin is not enough, e.g. the file filter is required. > - > > Key: JENKINS-13408 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13408 > Project: Jenkins > Issue Type: Improvement > Components: coverity >Reporter: Allen Xu > -- 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-13408) Defects filter in plugin is not enough, e.g. the file filter is required.
[ https://issues.jenkins-ci.org/browse/JENKINS-13408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Defects filter in plugin is not enough, e.g. the file filter is required. > - > > Key: JENKINS-13408 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13408 > Project: Jenkins > Issue Type: Improvement > Components: coverity >Reporter: Allen Xu > -- 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-13409) 404 when clicking on "more" in Builds-List
Robert Lachner created JENKINS-13409: Summary: 404 when clicking on "more" in Builds-List Key: JENKINS-13409 URL: https://issues.jenkins-ci.org/browse/JENKINS-13409 Project: Jenkins Issue Type: Bug Components: gui Affects Versions: current Environment: Windows Server 2008 R2 - Apache Tomcat 7.0.16 Reporter: Robert Lachner Priority: Minor Hi, since the last few Versions of Jenkins we are getting 404 Error Messages when there are more build in the builds-list and you click on the more Link. So noone is able to see the older builds in the list anymore and that is a problem for some users. Regards, Robert -- 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-13150) 'FATAL: null' while looking for test results in JUnit classes
[
https://issues.jenkins-ci.org/browse/JENKINS-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161461#comment-161461
]
Bruno P. Kinoshita commented on JENKINS-13150:
--
I asked to remove the attachments again on IRC :-) hopefully someone with admin
karma will remove them. Sorry.
> 'FATAL: null' while looking for test results in JUnit classes
> -
>
> Key: JENKINS-13150
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13150
> Project: Jenkins
> Issue Type: Bug
> Components: testlink
>Reporter: Jaroslavas D.
>Assignee: Bruno P. Kinoshita
> Labels: junit, plugin, plugins
> Attachments: full-log.txt, jenkins.jpg, logg.txt, noStrategy.png,
> TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml,
> testlink.jpg, withStrategy.png
>
>
> h3.Testlink configuration:
> !testlink.jpg|thumbnail!
> h3.Jenkins configuration:
> !jenkins.jpg|thumbnail!
> h3.Jenkins job {color:red}*FAILS*{color}:
> {code}
> 08:23:20 Looking for the test results of TestLink test cases.
> 08:23:20
> 08:23:20 Looking for test results in JUnit classes.
> 08:23:20
> 08:23:21 FATAL: null
> 08:23:21 java.lang.NullPointerException
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138)
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99)
> 08:23:21 at
> hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159)
> 08:23:21 at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
> 08:23:21 at hudson.model.Build$RunnerImpl.build(Build.java:178)
> 08:23:21 at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
> 08:23:21 at hudson.model.Run.run(Run.java:1408)
> 08:23:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> 08:23:21 at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> 08:23:21 at hudson.model.Executor.run(Executor.java:238)
> {code}
> Full console out can be found [^full-log.txt]
> Also JUnit report is attached -
> [^TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml]
--
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-13055) checkout error for org.tmatesoft.svn.core.SVNException: svn: REPORT /svn/hit71/!svn/vcc/default failed
[
https://issues.jenkins-ci.org/browse/JENKINS-13055?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161462#comment-161462
]
Yoshitaro Makise commented on JENKINS-13055:
In my environment similar stack trace got.
Using Jenkins 1.458 and Subversion plugin 1.39.
In my environment, error should be come from the svn server's instability,
but at least retry should occur.
I think the same fix as JENKINS-12201 should be applied to CheckoutUpdater.java
as well as UpdateUpdater.java.
{code}
Checking out
https://x.xxx..com:8001/xxx/xx//x/x
ERROR: Failed to check out
https://x.xxx..com:8001/xxx/xx//x/x
org.tmatesoft.svn.core.SVNException: svn: OPTIONS
/xxx/xx//x/x failed
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:298)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:283)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:271)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:533)
at
org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:98)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1011)
at
org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision(DAVRepository.java:180)
at
org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber(SVNBasicClient.java:482)
at
org.tmatesoft.svn.core.wc.SVNBasicClient.getLocations(SVNBasicClient.java:876)
at
org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:534)
at
org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:901)
at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:84)
at
hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:136)
at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:787)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:768)
at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:752)
at hudson.FilePath.act(FilePath.java:783)
at hudson.FilePath.act(FilePath.java:765)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:742)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:684)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:568)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:457)
at hudson.model.Run.run(Run.java:1404)
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: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS
/xxx/xx//x/x failed
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146)
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89)
... 27 more
Caused by: org.tmatesoft.svn.core.SVNException: svn: OPTIONS request failed on
'/xxx/xx//x/x'
svn: connection refused by the server
at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:662)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:292)
... 26 more
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: OPTIONS request failed
on '/xxx/xx//x/x'
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:660)
... 27 more
Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: connection refused by
the server
at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
at
org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection._request(HTTPConnection.java:418)
... 27 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(Unknown Source)
at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at com.sun.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source)
at
org.tmatesoft.svn.core.internal.util.SVNSocketConnection.run(SVNSocketConnection.java:57)
at java.lang.Thread.run(Unknown Source)
FATAL: null
java.lang.NullPoint
[JIRA] (JENKINS-13150) 'FATAL: null' while looking for test results in JUnit classes
[
https://issues.jenkins-ci.org/browse/JENKINS-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161463#comment-161463
]
Jaroslavas D. commented on JENKINS-13150:
-
*Everything works just fine now!* (y)
Thank You for your work!
> 'FATAL: null' while looking for test results in JUnit classes
> -
>
> Key: JENKINS-13150
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13150
> Project: Jenkins
> Issue Type: Bug
> Components: testlink
>Reporter: Jaroslavas D.
>Assignee: Bruno P. Kinoshita
> Labels: junit, plugin, plugins
> Attachments: full-log.txt, jenkins.jpg, logg.txt, noStrategy.png,
> TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml,
> testlink.jpg, withStrategy.png
>
>
> h3.Testlink configuration:
> !testlink.jpg|thumbnail!
> h3.Jenkins configuration:
> !jenkins.jpg|thumbnail!
> h3.Jenkins job {color:red}*FAILS*{color}:
> {code}
> 08:23:20 Looking for the test results of TestLink test cases.
> 08:23:20
> 08:23:20 Looking for test results in JUnit classes.
> 08:23:20
> 08:23:21 FATAL: null
> 08:23:21 java.lang.NullPointerException
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138)
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99)
> 08:23:21 at
> hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159)
> 08:23:21 at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
> 08:23:21 at hudson.model.Build$RunnerImpl.build(Build.java:178)
> 08:23:21 at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
> 08:23:21 at hudson.model.Run.run(Run.java:1408)
> 08:23:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> 08:23:21 at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> 08:23:21 at hudson.model.Executor.run(Executor.java:238)
> {code}
> Full console out can be found [^full-log.txt]
> Also JUnit report is attached -
> [^TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml]
--
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-10674) Publish over CIFS performance is slow
[ https://issues.jenkins-ci.org/browse/JENKINS-10674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161464#comment-161464 ] Edwin Renner commented on JENKINS-10674: Actually we are facing the same problems with slow write speed to a remote share. if i am using the windows native client (just by copying a 40MB file) from buildserver (windows server 2008 R2) to the remote server (windows server 2008 R2) i reach transfer speeds at around 150KByte/sec which is quite OK, as it is a WAN connection via VPN to a branch office. If i am using the Publish over CIFS plugin which is using the jcifs implementation is it rather slow. I think this is related to SMB2.0 and Windows Server 2008 in general. Also a netmon capture trace file shows me, that jcifs is not able to send packets bigger than 4096KB when sending to a Windows 7 oder Windows Server 2008 host. Is it possible to provide the plugin by using the jcifs implementation with the Large Read/Write Patch mentioned in this article: http://thread.gmane.org/gmane.network.samba.java/8878/focus=8884 thanks! > Publish over CIFS performance is slow > - > > Key: JENKINS-10674 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10674 > Project: Jenkins > Issue Type: Bug > Components: publish-over-cifs >Affects Versions: current > Environment: Windows XP, via Slave agent >Reporter: Ioannis Mavroukakis >Assignee: Slide-O-Mix > > Copying to a CIFS share is painfully slow. It takes (consistently) 7 minutes > to copy a 12MiB file to the windows share. I have tested manually copying > files to exclude other workstation issues, and the same file is copied in a > couple of seconds. -- 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-10674) Publish over CIFS performance is slow
[ https://issues.jenkins-ci.org/browse/JENKINS-10674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161464#comment-161464 ] Edwin Renner edited comment on JENKINS-10674 at 4/11/12 8:24 AM: - Actually we are facing the same problems with slow write speed to a remote share. if i am using the windows native client (just by copying a 40MB file) from buildserver (windows server 2008 R2) to the remote server (windows server 2008 R2) i reach transfer speeds at around 150KByte/sec which is quite OK, as it is a WAN connection via VPN to a branch office. If i am using the Publish over CIFS plugin which is using the jcifs implementation it performs rather slow. I think this is related to SMB2.0 and Windows Server 2008 in general. Also a netmon capture trace file shows me, that jcifs is not able to send packets bigger than 4096KB when sending to a Windows 7 oder Windows Server 2008 host. Is it possible to provide the plugin by using the jcifs implementation with the Large Read/Write Patch mentioned in this article: http://thread.gmane.org/gmane.network.samba.java/8878/focus=8884 thanks! was (Author: erenner): Actually we are facing the same problems with slow write speed to a remote share. if i am using the windows native client (just by copying a 40MB file) from buildserver (windows server 2008 R2) to the remote server (windows server 2008 R2) i reach transfer speeds at around 150KByte/sec which is quite OK, as it is a WAN connection via VPN to a branch office. If i am using the Publish over CIFS plugin which is using the jcifs implementation is it rather slow. I think this is related to SMB2.0 and Windows Server 2008 in general. Also a netmon capture trace file shows me, that jcifs is not able to send packets bigger than 4096KB when sending to a Windows 7 oder Windows Server 2008 host. Is it possible to provide the plugin by using the jcifs implementation with the Large Read/Write Patch mentioned in this article: http://thread.gmane.org/gmane.network.samba.java/8878/focus=8884 thanks! > Publish over CIFS performance is slow > - > > Key: JENKINS-10674 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10674 > Project: Jenkins > Issue Type: Bug > Components: publish-over-cifs >Affects Versions: current > Environment: Windows XP, via Slave agent >Reporter: Ioannis Mavroukakis >Assignee: Slide-O-Mix > > Copying to a CIFS share is painfully slow. It takes (consistently) 7 minutes > to copy a 12MiB file to the windows share. I have tested manually copying > files to exclude other workstation issues, and the same file is copied in a > couple of seconds. -- 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-12903) cloudbees-deployer could have on option for application environnement
[ https://issues.jenkins-ci.org/browse/JENKINS-12903?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161465#comment-161465 ] Steve Mactaggart commented on JENKINS-12903: I would really like this feature also. > cloudbees-deployer could have on option for application environnement > - > > Key: JENKINS-12903 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12903 > Project: Jenkins > Issue Type: Improvement > Components: cloudbees-deployer >Affects Versions: current >Reporter: Brice Laurencin >Assignee: olamy >Priority: Minor > > It would be nice if the deployer-plugin could have an option where we would > be able to select which environnement we want to use for this deployment, as > define in the cloudbees-web.xml. > Thanks! -- 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-12521) java.lang.IllegalArgumentException with TMP Cleaner Plugin after Jenkins update to version 1.449
[
https://issues.jenkins-ci.org/browse/JENKINS-12521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161466#comment-161466
]
torbent commented on JENKINS-12521:
---
Rene Snajder is right. The -D options must be given to "java", not
"jenkins.war". I've verified that on my setup: With a -Dhudson.footerURL (nice
and visible for debug!) option given like this:
{code}java -jar jenkins.war -Dhudson.footerURL=http://localhost{code}
there's no effect - the option is completely ignored. If I change it to this:
{code}java -Dhudson.footerURL=http://localhost -jar jenkins.war{code}
the footer URL changes as expected.
So we need to give our -D's in the right place, which will vary with method of
deployment. Rene apparently needs to set JENKINS_JAVA_OPTIONS. I'm running one
Jenkins on a Ubuntu server and need to change JAVA_ARGS in /etc/default/jenkins.
On another instance running on SuSE with an RPM I found "somewhere" the
variable is JENKINS_JAVA_OPTIONS and is set in /etc/sysconfig/jenkins.
So this is very likely not a bug in the code, rather in the documentation (and
may be obvious for those who actually code in Java, which I don't).
> java.lang.IllegalArgumentException with TMP Cleaner Plugin after Jenkins
> update to version 1.449
>
>
> Key: JENKINS-12521
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12521
> Project: Jenkins
> Issue Type: Bug
> Components: plugin
>Affects Versions: current
> Environment: Jenkins 1.449, Tmp Cleaner Plugin 1.1
>Reporter: Jürgen Prechtl
> Labels: jenkins, plugin
>
> After Jenkins update to version 1.449 Jenkins throws
> java.lang.IllegalArgumentException and does not start.
> The problem does not exist until version 1.448.
> The issue affects Tmp Cleaner Plugin 1.0 and 1.1 (i've tested those two
> versions).
> Here is the complete logfile entry:
> Exception in thread "main" java.lang.reflect.InvocationTargetException
> 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 Main._main(Main.java:273)
> at Main.main(Main.java:98)
> Caused by: java.lang.IllegalArgumentException: Multiple command line argument
> specified:
> -Dhudson.plugins.tmpcleaner.TmpCleanWork.extraDirectories=/home/hudson1t/tmp
> If i remove this startup option, Jenkins throws the same exception with the
> parameter hudson.plugins.tmpcleaner.TmpCleanWork.days.
--
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-13410) Git notifyCommit doesn't trigger if the configured repository url has a user/password, but the trigger one doesn't
Łukasz Pater created JENKINS-13410: -- Summary: Git notifyCommit doesn't trigger if the configured repository url has a user/password, but the trigger one doesn't Key: JENKINS-13410 URL: https://issues.jenkins-ci.org/browse/JENKINS-13410 Project: Jenkins Issue Type: Bug Components: git Environment: Windows Server 2008 R2, SCM Manager Reporter: Łukasz Pater Assignee: Nicolas De Loof Priority: Minor When notifying about a repo update we use the url: http://jenkins/git/notifyCommit?url=http://repo/url This doesn't trigger polling for builds that have a http user/password defined in the repository url (http://user:pass@repo/url). Calling the trigger url with the user/password works correctly. Would be nice if they could be omitted though. -- 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-13150) 'FATAL: null' while looking for test results in JUnit classes
[
https://issues.jenkins-ci.org/browse/JENKINS-13150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruno P. Kinoshita closed JENKINS-13150.
> 'FATAL: null' while looking for test results in JUnit classes
> -
>
> Key: JENKINS-13150
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13150
> Project: Jenkins
> Issue Type: Bug
> Components: testlink
>Reporter: Jaroslavas D.
>Assignee: Bruno P. Kinoshita
> Labels: junit, plugin, plugins
> Attachments: full-log.txt, jenkins.jpg, logg.txt, noStrategy.png,
> TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml,
> testlink.jpg, withStrategy.png
>
>
> h3.Testlink configuration:
> !testlink.jpg|thumbnail!
> h3.Jenkins configuration:
> !jenkins.jpg|thumbnail!
> h3.Jenkins job {color:red}*FAILS*{color}:
> {code}
> 08:23:20 Looking for the test results of TestLink test cases.
> 08:23:20
> 08:23:20 Looking for test results in JUnit classes.
> 08:23:20
> 08:23:21 FATAL: null
> 08:23:21 java.lang.NullPointerException
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.getJUnitNotes(JUnitCaseClassNameResultSeeker.java:138)
> 08:23:21 at
> hudson.plugins.testlink.result.JUnitCaseClassNameResultSeeker.seek(JUnitCaseClassNameResultSeeker.java:99)
> 08:23:21 at
> hudson.plugins.testlink.TestLinkBuilder.perform(TestLinkBuilder.java:159)
> 08:23:21 at
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703)
> 08:23:21 at hudson.model.Build$RunnerImpl.build(Build.java:178)
> 08:23:21 at hudson.model.Build$RunnerImpl.doRun(Build.java:139)
> 08:23:21 at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:473)
> 08:23:21 at hudson.model.Run.run(Run.java:1408)
> 08:23:21 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
> 08:23:21 at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> 08:23:21 at hudson.model.Executor.run(Executor.java:238)
> {code}
> Full console out can be found [^full-log.txt]
> Also JUnit report is attached -
> [^TEST-com.exigen.ipb.product.ProductPropertiesUiConfWebTests.xml]
--
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-11918) To support authenticating into SMTP server with Auth and TLS turned on please update to javax.mail version 1.4.4
[ https://issues.jenkins-ci.org/browse/JENKINS-11918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161467#comment-161467 ] Christoph Moser commented on JENKINS-11918: --- Solved since jenkins-version 1.455 > To support authenticating into SMTP server with Auth and TLS turned on please > update to javax.mail version 1.4.4 > > > Key: JENKINS-11918 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11918 > Project: Jenkins > Issue Type: Improvement > Components: mail, plugin >Affects Versions: current >Reporter: Christoph Moser > > To support authenticating into SMTP server with Auth and TLS turned on please > update to javax.mail version 1.4.4 -- 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-11918) To support authenticating into SMTP server with Auth and TLS turned on please update to javax.mail version 1.4.4
[ https://issues.jenkins-ci.org/browse/JENKINS-11918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christoph Moser closed JENKINS-11918. - Fix Version/s: current Resolution: Fixed This issue is solved with jenkins-version 1.455 > To support authenticating into SMTP server with Auth and TLS turned on please > update to javax.mail version 1.4.4 > > > Key: JENKINS-11918 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11918 > Project: Jenkins > Issue Type: Improvement > Components: mail, plugin >Affects Versions: current >Reporter: Christoph Moser > Fix For: current > > > To support authenticating into SMTP server with Auth and TLS turned on please > update to javax.mail version 1.4.4 -- 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-12316) git plugin should NOT tag every build by default
[ https://issues.jenkins-ci.org/browse/JENKINS-12316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161469#comment-161469 ] Steffen Sledz commented on JENKINS-12316: - Can't find this checkbox in Jenkins 1.459. :( Where did it went to? > git plugin should NOT tag every build by default > > > Key: JENKINS-12316 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12316 > Project: Jenkins > Issue Type: Bug > Components: git >Reporter: Alexey Java >Assignee: abayer > Attachments: jenkins git plugin fail.txt > > > Git plugin automatically tries to add tags to my Git repository for every > build (every 15 minutes or so!). that's very weird it does it automatically > by default without me configuring this. > I don't need hundreds of tags in Git repo... I suggest turning this OFF by > default and allowing to configure it in Jenkins UI per build job. -- 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-13381) Jenkins stopped after updating plugins
[ https://issues.jenkins-ci.org/browse/JENKINS-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161470#comment-161470 ] Kasper Garnæs commented on JENKINS-13381: - I've experienced the same problem. Downgrading analysis collector did not solve the problem here. Disabling analysis-collector did. > Jenkins stopped after updating plugins > -- > > Key: JENKINS-13381 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13381 > Project: Jenkins > Issue Type: Bug > Components: analysis-collector, core, git >Affects Versions: current > Environment: Ubuntu Server 64 bits >Reporter: Rafael Tavares >Assignee: Nicolas De Loof > Labels: git, jenkins, plugins > > Hi, > I was updating my plugins then after update I can't access anymore my > jenkins. I get the following error: > > [!] Erro > org.jvnet.hudson.reactor.ReactorException: java.lang.Error: > java.lang.reflect.InvocationTargetException > at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:246) > at jenkins.InitReactorRunner.run(InitReactorRunner.java:43) > at jenkins.model.Jenkins.executeReactor(Jenkins.java:849) > at jenkins.model.Jenkins.(Jenkins.java:761) > at hudson.model.Hudson.(Hudson.java:81) > at hudson.model.Hudson.(Hudson.java:77) > at hudson.WebAppMain$2.run(WebAppMain.java:217) > Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException > at hudson.init.InitializerFinder.invoke(InitializerFinder.java:124) > at > hudson.init.InitializerFinder$TaskImpl.run(InitializerFinder.java:184) > at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259) > at jenkins.model.Jenkins$6.runTask(Jenkins.java:838) > 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.runWorker(ThreadPoolExecutor.java:1110) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > Caused by: java.lang.reflect.InvocationTargetException > 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 hudson.init.InitializerFinder.invoke(InitializerFinder.java:120) > ... 8 more > Caused by: java.lang.NullPointerException > at hudson.plugins.git.GitTool.onLoaded(GitTool.java:74) > ... 13 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-12521) java.lang.IllegalArgumentException with TMP Cleaner Plugin after Jenkins update to version 1.449
[ https://issues.jenkins-ci.org/browse/JENKINS-12521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jürgen Prechtl resolved JENKINS-12521. -- Resolution: Not A Defect The Problem is not the softver version itself. The java arguments has to be positioned in the right order (as described in the last entry in this issue) > java.lang.IllegalArgumentException with TMP Cleaner Plugin after Jenkins > update to version 1.449 > > > Key: JENKINS-12521 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12521 > Project: Jenkins > Issue Type: Bug > Components: plugin >Affects Versions: current > Environment: Jenkins 1.449, Tmp Cleaner Plugin 1.1 >Reporter: Jürgen Prechtl > Labels: jenkins, plugin > > After Jenkins update to version 1.449 Jenkins throws > java.lang.IllegalArgumentException and does not start. > The problem does not exist until version 1.448. > The issue affects Tmp Cleaner Plugin 1.0 and 1.1 (i've tested those two > versions). > Here is the complete logfile entry: > Exception in thread "main" java.lang.reflect.InvocationTargetException > 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 Main._main(Main.java:273) > at Main.main(Main.java:98) > Caused by: java.lang.IllegalArgumentException: Multiple command line argument > specified: > -Dhudson.plugins.tmpcleaner.TmpCleanWork.extraDirectories=/home/hudson1t/tmp > If i remove this startup option, Jenkins throws the same exception with the > parameter hudson.plugins.tmpcleaner.TmpCleanWork.days. -- 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-12521) java.lang.IllegalArgumentException with TMP Cleaner Plugin after Jenkins update to version 1.449
[ https://issues.jenkins-ci.org/browse/JENKINS-12521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161471#comment-161471 ] Jürgen Prechtl edited comment on JENKINS-12521 at 4/11/12 11:01 AM: The Problem is not the software version itself. The java arguments has to be positioned in the right order (as described in the last entry in this issue) was (Author: juprecht): The Problem is not the softver version itself. The java arguments has to be positioned in the right order (as described in the last entry in this issue) > java.lang.IllegalArgumentException with TMP Cleaner Plugin after Jenkins > update to version 1.449 > > > Key: JENKINS-12521 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12521 > Project: Jenkins > Issue Type: Bug > Components: plugin >Affects Versions: current > Environment: Jenkins 1.449, Tmp Cleaner Plugin 1.1 >Reporter: Jürgen Prechtl > Labels: jenkins, plugin > > After Jenkins update to version 1.449 Jenkins throws > java.lang.IllegalArgumentException and does not start. > The problem does not exist until version 1.448. > The issue affects Tmp Cleaner Plugin 1.0 and 1.1 (i've tested those two > versions). > Here is the complete logfile entry: > Exception in thread "main" java.lang.reflect.InvocationTargetException > 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 Main._main(Main.java:273) > at Main.main(Main.java:98) > Caused by: java.lang.IllegalArgumentException: Multiple command line argument > specified: > -Dhudson.plugins.tmpcleaner.TmpCleanWork.extraDirectories=/home/hudson1t/tmp > If i remove this startup option, Jenkins throws the same exception with the > parameter hudson.plugins.tmpcleaner.TmpCleanWork.days. -- 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-13409) 404 when clicking on "more" in Builds-List
[ https://issues.jenkins-ci.org/browse/JENKINS-13409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13409. --- Resolution: Duplicate > 404 when clicking on "more" in Builds-List > -- > > Key: JENKINS-13409 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13409 > Project: Jenkins > Issue Type: Bug > Components: gui >Affects Versions: current > Environment: Windows Server 2008 R2 - Apache Tomcat 7.0.16 >Reporter: Robert Lachner >Priority: Minor > > Hi, > since the last few Versions of Jenkins we are getting 404 Error Messages when > there are more build in the builds-list and you click on the more Link. > So noone is able to see the older builds in the list anymore and that is a > problem for some users. > Regards, > Robert -- 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-13356) Git fast remote polling always triggers build when missing locale
[
https://issues.jenkins-ci.org/browse/JENKINS-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
OHTAKE Tomohiro resolved JENKINS-13356.
---
Resolution: Fixed
> Git fast remote polling always triggers build when missing locale
> -
>
> Key: JENKINS-13356
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13356
> Project: Jenkins
> Issue Type: Bug
> Components: git
>Reporter: Marc Günther
>Assignee: Nicolas De Loof
>Priority: Minor
>
> Symptom:
> All jobs which had fast remote polling enabled triggered on every change in
> their repository, even if it was on an unrelated branch.
> Cause:
> Fast remote polling issues a {{git ls-remote -h }} command.
> The output of this command is supposed to be the sha hash of the last commit,
> but in our case it was:
> {{bash: warning: setlocale: LC_ALL: cannot}}
> Explanation:
> We have some slaves that use a german locale. This locale does not exist on
> the Git repository server nor on the Jenkins server. Installing it on the
> Jenkins server had no effect, as the above warning comes from the Git
> repository server.
> Quick fix:
> Install the missing locale on the both servers.
> Solution:
> Installing locales on some server should not be required. Either ignore
> stderr when issuing the {{git ls-remote}} command, or manipulate the passed
> in environment to something that does not cause side effects like this.
> Question:
> Why is the environment from the slave used on the server when doing the
> polling? {{LC_ALL}} is not set on our Jenkins server, so this definitely
> comes from a slave. I also notice that variables like HOME, USER, DISPLAY are
> set to values which make no sense on the server, and can lead to more
> problems like this.
--
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-13371) Wrong URL on WIKI for perfformance-plugin bug list.
[ https://issues.jenkins-ci.org/browse/JENKINS-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cjo9900 reassigned JENKINS-13371: - Assignee: cjo9900 (was: Manuel Carrasco) > Wrong URL on WIKI for perfformance-plugin bug list. > --- > > Key: JENKINS-13371 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13371 > Project: Jenkins > Issue Type: Bug > Components: performance-plugin >Reporter: Piotr Czachur >Assignee: cjo9900 > > On Performance Plugin WIKI page > (https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin) where is URL > for Open Issues: > http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance%27 > but should be: > https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance-plugin%27 > Please update WIKI page. > Cheers! -- 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-13371) Wrong URL on WIKI for perfformance-plugin bug list.
[
https://issues.jenkins-ci.org/browse/JENKINS-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161472#comment-161472
]
cjo9900 commented on JENKINS-13371:
---
Changed
{hudson-plugin-info:pluginId=performance}
to
{hudson-plugin-info:pluginId=performance|jiraComponent=performance-plugin}
so allow the jira issues link to be correctly generated.
Link for table generating code
https://github.com/jenkinsci/backend-jenkins-plugin-info-plugin/blob/master/src/main/java/org/jenkinsci/confluence/plugins/JenkinsPluginInfoMacro.java#L86
> Wrong URL on WIKI for perfformance-plugin bug list.
> ---
>
> Key: JENKINS-13371
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13371
> Project: Jenkins
> Issue Type: Bug
> Components: performance-plugin
>Reporter: Piotr Czachur
>Assignee: cjo9900
>
> On Performance Plugin WIKI page
> (https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin) where is URL
> for Open Issues:
> http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance%27
> but should be:
> https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance-plugin%27
> Please update WIKI page.
> Cheers!
--
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-13371) Wrong URL on WIKI for perfformance-plugin bug list.
[ https://issues.jenkins-ci.org/browse/JENKINS-13371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] cjo9900 resolved JENKINS-13371. --- Resolution: Fixed > Wrong URL on WIKI for perfformance-plugin bug list. > --- > > Key: JENKINS-13371 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13371 > Project: Jenkins > Issue Type: Bug > Components: performance-plugin >Reporter: Piotr Czachur >Assignee: cjo9900 > > On Performance Plugin WIKI page > (https://wiki.jenkins-ci.org/display/JENKINS/Performance+Plugin) where is URL > for Open Issues: > http://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance%27 > but should be: > https://issues.jenkins-ci.org/secure/IssueNavigator.jspa?mode=hide&reset=true&jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%29+AND+component+%3D+%27performance-plugin%27 > Please update WIKI page. > Cheers! -- 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-13356) Git fast remote polling always triggers build when missing locale
[
https://issues.jenkins-ci.org/browse/JENKINS-13356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161473#comment-161473
]
Marc Günther commented on JENKINS-13356:
Still wondering why the complete environment from the slave is used to run a
process on the server. This screams for potential problems, doesn't it?
> Git fast remote polling always triggers build when missing locale
> -
>
> Key: JENKINS-13356
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13356
> Project: Jenkins
> Issue Type: Bug
> Components: git
>Reporter: Marc Günther
>Assignee: Nicolas De Loof
>Priority: Minor
>
> Symptom:
> All jobs which had fast remote polling enabled triggered on every change in
> their repository, even if it was on an unrelated branch.
> Cause:
> Fast remote polling issues a {{git ls-remote -h }} command.
> The output of this command is supposed to be the sha hash of the last commit,
> but in our case it was:
> {{bash: warning: setlocale: LC_ALL: cannot}}
> Explanation:
> We have some slaves that use a german locale. This locale does not exist on
> the Git repository server nor on the Jenkins server. Installing it on the
> Jenkins server had no effect, as the above warning comes from the Git
> repository server.
> Quick fix:
> Install the missing locale on the both servers.
> Solution:
> Installing locales on some server should not be required. Either ignore
> stderr when issuing the {{git ls-remote}} command, or manipulate the passed
> in environment to something that does not cause side effects like this.
> Question:
> Why is the environment from the slave used on the server when doing the
> polling? {{LC_ALL}} is not set on our Jenkins server, so this definitely
> comes from a slave. I also notice that variables like HOME, USER, DISPLAY are
> set to values which make no sense on the server, and can lead to more
> problems like this.
--
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-13352) Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found" when trying to download artifacts >2GB
[
https://issues.jenkins-ci.org/browse/JENKINS-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161474#comment-161474
]
OHTAKE Tomohiro commented on JENKINS-13352:
---
Reproduced in Ubuntu 11.04 64bit, Jenkins 1.459, Winstone.
In Winstone case, it seems that Winstone fails to parse Content-Length header.
{code}
java.lang.NumberFormatException: For input string: "2147484672"
at
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:484)
at java.lang.Integer.parseInt(Integer.java:514)
at winstone.WinstoneOutputStream.write(WinstoneOutputStream.java:106)
at org.kohsuke.stapler.Stapler.serveStaticResource(Stapler.java:418)
at org.kohsuke.stapler.ResponseImpl.serveFile(ResponseImpl.java:150)
{code}
[Which servlet
container|https://wiki.jenkins-ci.org/display/JENKINS/Containers] do you use
for Jenkins?
> Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory
> could not be found" when trying to download artifacts >2GB
>
>
> Key: JENKINS-13352
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13352
> Project: Jenkins
> Issue Type: Bug
> Components: core
>Affects Versions: current
> Environment: Server Win2k8 - Jenkins ver. 1.455 and 1.457 (server has
> zero executors)
> Slave Win2k8 R2 - Slave ver. 2.12 (21 slaves)
> WebBrowser - Firefox 11.0 and Chrome 18.0.1025.142 m
> The build which is failing to archive artifacts is tied to a single slave.
>Reporter: Richard Taylor
>
> *** This issues appears to be that artifacts larger than 2GB can not be
> downloaded from Jenkins server ***
> We have started getting bad links to artifacts from some runs of our package
> build job.
> * The build completes with out error.
> * The artifacts are sucesfully copied back to the server.
> * The artifacts can be copied and verified ok using SMB drive share.
> * Any artifacts which are larger than 2GB will fail to download from the
> jenkins server.
> This web page has not been found
> Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found.
> As a work around we are looking to split up the artifacts into multiple files
> but this is a less than ideal workflow.
> Thanks
> Richard.
--
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-13352) Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found" when trying to download artifacts >2GB
[ https://issues.jenkins-ci.org/browse/JENKINS-13352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161475#comment-161475 ] Richard Taylor commented on JENKINS-13352: -- Yes we are running jenkins as a service on the win2k machine with the default container. >From the docs that makes it the Winstone container. Server is win2k 64bit and we are running 64bit JRE. > Jenkins returns "Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory > could not be found" when trying to download artifacts >2GB > > > Key: JENKINS-13352 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13352 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Server Win2k8 - Jenkins ver. 1.455 and 1.457 (server has > zero executors) > Slave Win2k8 R2 - Slave ver. 2.12 (21 slaves) > WebBrowser - Firefox 11.0 and Chrome 18.0.1025.142 m > The build which is failing to archive artifacts is tied to a single slave. >Reporter: Richard Taylor > > *** This issues appears to be that artifacts larger than 2GB can not be > downloaded from Jenkins server *** > We have started getting bad links to artifacts from some runs of our package > build job. > * The build completes with out error. > * The artifacts are sucesfully copied back to the server. > * The artifacts can be copied and verified ok using SMB drive share. > * Any artifacts which are larger than 2GB will fail to download from the > jenkins server. > This web page has not been found > Error 6 (net::ERR_FILE_NOT_FOUND): The file or directory could not be found. > As a work around we are looking to split up the artifacts into multiple files > but this is a less than ideal workflow. > Thanks > Richard. -- 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-10880) Git plugin fails on remote Poll
[ https://issues.jenkins-ci.org/browse/JENKINS-10880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161476#comment-161476 ] Marc Günther commented on JENKINS-10880: fix available here: https://github.com/jenkinsci/git-plugin/pull/65 > 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-10674) Publish over CIFS performance is slow
[ https://issues.jenkins-ci.org/browse/JENKINS-10674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161477#comment-161477 ] Slide-O-Mix commented on JENKINS-10674: --- I will try and build a test version of the plugin with the large read/write patch. > Publish over CIFS performance is slow > - > > Key: JENKINS-10674 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10674 > Project: Jenkins > Issue Type: Bug > Components: publish-over-cifs >Affects Versions: current > Environment: Windows XP, via Slave agent >Reporter: Ioannis Mavroukakis >Assignee: Slide-O-Mix > > Copying to a CIFS share is painfully slow. It takes (consistently) 7 minutes > to copy a 12MiB file to the windows share. I have tested manually copying > files to exclude other workstation issues, and the same file is copied in a > couple of seconds. -- 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-10674) Publish over CIFS performance is slow
[ https://issues.jenkins-ci.org/browse/JENKINS-10674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161478#comment-161478 ] Edwin Renner commented on JENKINS-10674: thanks a lot for your efforts, that's really awesome news! > Publish over CIFS performance is slow > - > > Key: JENKINS-10674 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10674 > Project: Jenkins > Issue Type: Bug > Components: publish-over-cifs >Affects Versions: current > Environment: Windows XP, via Slave agent >Reporter: Ioannis Mavroukakis >Assignee: Slide-O-Mix > > Copying to a CIFS share is painfully slow. It takes (consistently) 7 minutes > to copy a 12MiB file to the windows share. I have tested manually copying > files to exclude other workstation issues, and the same file is copied in a > couple of seconds. -- 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-13411) Klocwork XML output is deprecated
Krzysztof Malinowski created JENKINS-13411: -- Summary: Klocwork XML output is deprecated Key: JENKINS-13411 URL: https://issues.jenkins-ci.org/browse/JENKINS-13411 Project: Jenkins Issue Type: New Feature Components: klocwork Reporter: Krzysztof Malinowski Assignee: gbois As http://www.klocwork.com/products/documentation/current/Kwinspectreport states: XML report is deprecated in KW 9.5 and will no longer be available. I recommend that plugin uses some other parser for the issues (csv maybe) or use web api to get the issues. -- 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
[
https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161479#comment-161479
]
Marc Sanfacon commented on JENKINS-13325:
-
They are indeed environment variables on the linux server. They are set in the
.bash_profile file.
They are defined like this:
export DEVHOME=/usr/local/jenkins
export SRC_SHARED=${DEVHOME}/Projects/Shared
export NEWSCP=${DEVHOME}/Projects/DevTools/newscp
# Python scripts
export PYTHONPATH=${PYTHONPATH}:${DEVHOME}/Projects/DevTools/newscp
export
PATH=${PATH}:${DEVHOME}/Projects/DevTools/newscp:${DEVHOME}/Projects/DevTools/redhat
Does that help?
I'm not sure I understand what you mean by: these variables can't resolve each
other.
> 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.
--
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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
Daniel Beck created JENKINS-13412:
-
Summary: Gradle plugin fails to quote parameters without
whitespace when containing input/output redirection symbols, e.g. in XML strings
Key: JENKINS-13412
URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
Project: Jenkins
Issue Type: Bug
Components: gradle
Affects Versions: current
Environment: Windows Server 2008 R2
Jenkins 1.424.6
Jenkins Gradle Plugin 1.12
Reporter: Daniel Beck
Assignee: gbois
Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
call.
If one of these arguments looks like XML, but does not contain whitespace, it
is not quoted. This leads to problems with input/output redirection symbols
(less-than, greater-than)
Example String Parameter value:
{code}
{code}
Results in the following build output:
{code}
[workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
%%ERRORLEVEL%%
The system cannot find the file specified.
Build step 'Invoke Gradle script' changed build result to FAILURE
Build step 'Invoke Gradle script' marked build as failure
Notifying upstream projects of job completion
{code}
Real world example:
Copy artifacts plugin's "Latest successful build" has the value:
{code}
{code}
This results in "File not found" errors on Windows Server. Not tested on Linux.
--
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-13413) Git icon(git-48x48.png) missing in job page.
[ https://issues.jenkins-ci.org/browse/JENKINS-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe updated JENKINS-13413: - Priority: Minor (was: Major) > Git icon(git-48x48.png) missing in job page. > - > > Key: JENKINS-13413 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13413 > Project: Jenkins > Issue Type: Bug > Components: git > Environment: Git Plugin 1.1.17 >Reporter: sogabe >Assignee: Nicolas De Loof >Priority: Minor > Attachments: git-icon_missing.png > > > After updating to Git Plugin 1.1.17, Git icon is missing in job page. -- 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-13413) Git icon(git-48x48.png) missing in job page.
sogabe created JENKINS-13413: Summary: Git icon(git-48x48.png) missing in job page. Key: JENKINS-13413 URL: https://issues.jenkins-ci.org/browse/JENKINS-13413 Project: Jenkins Issue Type: Bug Components: git Environment: Git Plugin 1.1.17 Reporter: sogabe Assignee: Nicolas De Loof Attachments: git-icon_missing.png After updating to Git Plugin 1.1.17, Git icon is missing in job page. -- 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-13414) Issue while building jenkinsci-pmd-plugin-a16ba49 source code
karthikeya karthi created JENKINS-13414:
---
Summary: Issue while building jenkinsci-pmd-plugin-a16ba49 source
code
Key: JENKINS-13414
URL: https://issues.jenkins-ci.org/browse/JENKINS-13414
Project: Jenkins
Issue Type: Bug
Components: pmd
Reporter: karthikeya karthi
Assignee: Ulli Hafner
Priority: Blocker
I've customized PMD, so to point my pmd jar I've edit pom.xml of jenkins pmd
plugin sourcode and while building getting following error report.
Problem encountered during annotation processing;
see stacktrace below for more information.
java.lang.AssertionError
at com.sun.tools.apt.mirror.type.TypeMaker.getType(TypeMaker.java:76)
at
com.sun.tools.apt.mirror.declaration.ClassDeclarationImpl.getSuperclass(ClassDeclarationImpl.java:64)
at
org.jvnet.hudson.maven.plugins.hpi.AnnotationProcessorFactoryImpl$1.process(AnnotationProcessorFactoryImpl.ja
va:50)
at
com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.process(AnnotationProcessors.java:60)
at
com.sun.mirror.apt.AnnotationProcessors$CompositeAnnotationProcessor.process(AnnotationProcessors.java:60)
at com.sun.tools.apt.comp.Apt.main(Apt.java:454)
at com.sun.tools.apt.main.JavaCompiler.compile(JavaCompiler.java:258)
at com.sun.tools.apt.main.Main.compile(Main.java:1102)
at com.sun.tools.apt.main.Main.compile(Main.java:964)
at com.sun.tools.apt.Main.processing(Main.java:95)
at com.sun.tools.apt.Main.process(Main.java:85)
at
org.jvnet.hudson.maven.plugins.hpi.AptCompiler.compileInProcess(AptCompiler.java:63)
at
org.jvnet.hudson.maven.plugins.hpi.AptCompiler.compile(AptCompiler.java:50)
at
org.jvnet.hudson.maven.plugins.hpi.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:486)
at
org.jvnet.hudson.maven.plugins.hpi.CompilerMojo.execute(CompilerMojo.java:111)
at org.jvnet.hudson.maven.plugins.hpi.AptMojo.execute(AptMojo.java:24)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:55
6)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
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.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
C:\Documents and
Settings\ET33783\Desktop\jenkinsci-pmd-plugin-a16ba49\src\main\java\hudson\plugins\pmd\tokens\PmdResult
TokenMacro.java:4: package hudson.plugins.analysis.tokens does not exist
import hudson.plugins.analysis.tokens.AbstractResultTokenMacro;
^
C:\Documents and
Settings\ET33783\Desktop\jenkinsci-pmd-plugin-a16ba49\src\main\java\hudson\plugins\pmd\tokens\PmdResult
TokenMacro.java:14: cannot find symbol
symbol: class AbstractResultTokenMacro
public class PmdResultTokenMacro extends AbstractResultTokenMacro {
^
C:\Documents and
Settings\ET33783\Desktop\jenkinsci-pmd-plugin-a16ba49\src\main\java\hudson\plugins\pmd\dashboard\Warnin
gsPriorityGraphPortlet.java:11: package hudson.plugins.view.dashboard does not
exist
import hudson.plugins.view.dashboard.DashboardPortlet;
^
C:\Documents and
Settings\ET33783\Desktop\jenkinsci-pmd-plugin-a16ba49\src\main\java\hudson\plugins\pmd\dashboard\Warnin
gsPriorityGraphPortlet.java:20: cannot access
hudson.plugins.view.dashboard.DashboardPortlet
class file for hudson.plugin
[JIRA] (JENKINS-7767) Performance report JMeter not possible to set threshold >0% but <1%
[ https://issues.jenkins-ci.org/browse/JENKINS-7767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manuel Carrasco resolved JENKINS-7767. -- Fix Version/s: current Resolution: Fixed > Performance report JMeter not possible to set threshold >0% but <1% > --- > > Key: JENKINS-7767 > URL: https://issues.jenkins-ci.org/browse/JENKINS-7767 > Project: Jenkins > Issue Type: Bug > Components: performance-plugin >Affects Versions: current > Environment: WINDOWS XP HUDSON >Reporter: zillakilla >Assignee: Manuel Carrasco > Fix For: current > > > When executing jmeter tests within Hudson, Some of the tests fail with an > Error% of 0.4% > Is it possible to set the thresholds of the Performance Report to a value of > less than 1% but greater than 0% ? > When entering a value of say 0.1 and saving, the value changes to 0 -- 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-13416) On demand slave provisioning is starting all available slaves
Bruno Meneguello created JENKINS-13416: -- Summary: On demand slave provisioning is starting all available slaves Key: JENKINS-13416 URL: https://issues.jenkins-ci.org/browse/JENKINS-13416 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Reporter: Bruno Meneguello Assignee: Kohsuke Kawaguchi Priority: Minor I'm using on demand slaves (on amazon) started by a shell script. When starting a job with all slaves disconnected, all my slaves are started together. When in debug, I'd noticed that "RetentionStrategy" "Demand" is testing "Computer.getDemandStartMilliseconds()" to connect the slave, but all slaves (that 'll take some time to wake up) pass in test. Shouldn't this strategy take in account if there are executor enough and nodes starting? -- 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-12619) "Failed to test the validity of the user name" on all security matrices since upgrade
[ https://issues.jenkins-ci.org/browse/JENKINS-12619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161480#comment-161480 ] Alex Trevino commented on JENKINS-12619: Same issue on CentOS 6.2, with Jenkins 1.454 and AD plugin 1.26. We downgraded to AD plugin 1.23 (previously installed version), and the problem seems to be fixed. > "Failed to test the validity of the user name" on all security matrices since > upgrade > - > > Key: JENKINS-12619 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12619 > Project: Jenkins > Issue Type: Bug > Components: active-directory > Environment: Jenkins 1.450, plugin version 1.26 > Windows Server 2003, non-domain server > Installed as local user > Our Windows domain name specified in configuration as ourdomain.co.uk >Reporter: Tom Fanning >Priority: Minor > Labels: jenkins, plugin, windows > > Upgraded plugin to version 1.26 just after upgrading Jenkins to 1.450 > Now get message "Failed to test the validity of the user name x" wherever > there is a security checkbox matrix. > Everything seems to work alright still as far as I can tell. > Stack trace: > org.acegisecurity.BadCredentialsException: Failed to retrieve user > information for x; nested exception is javax.naming.NamingException: [LDAP: > error code 1 - 04DC: LdapErr: DSID-0C0906E8, comment: In order to perform > this operation a successful bind must be completed on the connection., data > 0, v1db1]; remaining name 'DC=ourdomain,DC=co,DC=uk' > at > hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:231) > at > hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:130) > at > hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:95) > at > hudson.plugins.active_directory.AbstractActiveDirectoryAuthenticationProvider.loadUserByUsername(AbstractActiveDirectoryAuthenticationProvider.java:27) > at > hudson.plugins.active_directory.ActiveDirectorySecurityRealm.loadUserByUsername(ActiveDirectorySecurityRealm.java:551) > at > hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName_(GlobalMatrixAuthorizationStrategy.java:304) > at > hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:288) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > 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: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.MetaClass$6.doDispatch(MetaClass.java:241) > 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 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 >
[JIRA] (JENKINS-13417) git-plugin: rev-parse dereferencing tags breaks on Windows
Jay Berkenbilt created JENKINS-13417:
Summary: git-plugin: rev-parse dereferencing tags breaks on Windows
Key: JENKINS-13417
URL: https://issues.jenkins-ci.org/browse/JENKINS-13417
Project: Jenkins
Issue Type: Bug
Components: git
Environment: Windows 2008 R2 slave launched with cygwin ssh, cygwin git
Reporter: Jay Berkenbilt
Assignee: Nicolas De Loof
The change to GitAPI.java in commit 13f6038acc4fa5b5a62413155da6fc8cfcad3fe0
seems to break the git plugin for Windows, at least in some circumstances. The
syntax rev^{commit} gets mangled by cmd because ^ is a quote character. This
means that cmd passes rev{commit} to git, which as a cygwin executable being
run from Windows, further tries to do wildcard expansion and maps this to
revcommit. Putting "" around rev^{commit} empirically seems to work, though I
haven't tried it in the git plugin itself.
This C fragment:
{code}
#include
int main(int argc, char* argv[])
{
int i;
for (i = 0; i < argc; ++i)
{
printf("%s\n", argv[i]);
}
return 0;
}
{code}
when compiled with mingw to a native Windows application (a.exe) and invoked
from cmd as a.exe a^{b} prints a{b}. When the same fragment is compiled with
cygwin gcc to cygwin executable a.exe and is invoked the same way from cmd, it
prints ab. Both print a^{b} when invoked from cmd as a.exe "a^{b}".
I'm not sure what the fix is here other than perhaps detecting that this is
windows and putting quotes around the argument in Windows.
On another note, I left the Affects Version/s field blank. My Jenkins
installation claims that it is using version 1.1.6. Looking at the git repo
for the plugin, it appears that 1.1.6 should not have the ^{commit} fix, yet
running strings on plugins/git/WEB-INF/classes/hudson/plugins/git/GitAPI.class
clearly shows that my git plugin has that change in it.
--
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-13418) PostBuildScript plugin does not load its configuration properly
Nate Jones created JENKINS-13418:
Summary: PostBuildScript plugin does not load its configuration
properly
Key: JENKINS-13418
URL: https://issues.jenkins-ci.org/browse/JENKINS-13418
Project: Jenkins
Issue Type: Bug
Components: postbuildscript
Environment: Jenkins: v. 1.458 (but also 1.419)
OS: Debian Lenny/Squeeze
Reporter: Nate Jones
Assignee: gbois
Priority: Minor
Attachments: screenshot1.png, screenshot2.png
The PostBuildScript plugin works great.
However, I've noticed that when I load up the configuration page for my job in
jenkins, the PBS information is missing. The config in screenshot1.png doesn't
show up when the configuration is loaded again in screenshot2.png. If the
config.xml is examined, the data is there:
{noformat}
/usr/bin/send_post_build_message.sh
false
{noformat}
I've made some customizations to the PBS plugin (as seen here
https://github.com/mediatemple/postbuildscript-plugin in the build_info_as_env
branch), but after looking at the code for a while, I think this is a little
above my ken.
--
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-13418) PostBuildScript plugin does not load its configuration properly
[
https://issues.jenkins-ci.org/browse/JENKINS-13418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nate Jones updated JENKINS-13418:
-
Description:
The PostBuildScript plugin works great.
However, I've noticed that when I load up the configuration page for my job in
jenkins, the PBS information is missing. The config in screenshot1.png doesn't
show up when the configuration is loaded again in screenshot2.png. If the
config.xml is examined, the data is there:
{noformat}
/usr/bin/send_post_build_message.sh
false
{noformat}
And after saving the second time (as in screenshot2.png), the script is missing
from config.xml:
{noformat}
false
{noformat}
I've made some customizations to the PBS plugin (as seen here
https://github.com/mediatemple/postbuildscript-plugin in the build_info_as_env
branch), but after looking at the code for a while, I think this is a little
above my ken.
was:
The PostBuildScript plugin works great.
However, I've noticed that when I load up the configuration page for my job in
jenkins, the PBS information is missing. The config in screenshot1.png doesn't
show up when the configuration is loaded again in screenshot2.png. If the
config.xml is examined, the data is there:
{noformat}
/usr/bin/send_post_build_message.sh
false
{noformat}
I've made some customizations to the PBS plugin (as seen here
https://github.com/mediatemple/postbuildscript-plugin in the build_info_as_env
branch), but after looking at the code for a while, I think this is a little
above my ken.
> PostBuildScript plugin does not load its configuration properly
> ---
>
> Key: JENKINS-13418
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13418
> Project: Jenkins
> Issue Type: Bug
> Components: postbuildscript
> Environment: Jenkins: v. 1.458 (but also 1.419)
> OS: Debian Lenny/Squeeze
>Reporter: Nate Jones
>Assignee: gbois
>Priority: Minor
> Attachments: screenshot1.png, screenshot2.png
>
>
> The PostBuildScript plugin works great.
> However, I've noticed that when I load up the configuration page for my job
> in jenkins, the PBS information is missing. The config in screenshot1.png
> doesn't show up when the configuration is loaded again in screenshot2.png.
> If the config.xml is examined, the data is there:
> {noformat}
>
>
>
> /usr/bin/send_post_build_message.sh
>
>
> false
>
> {noformat}
> And after saving the second time (as in screenshot2.png), the script is
> missing from config.xml:
> {noformat}
>
> false
>
> {noformat}
> I've made some customizations to the PBS plugin (as seen here
> https://github.com/mediatemple/postbuildscript-plugin in the
> build_info_as_env branch), but after looking at the code for a while, I think
> this is a little above my ken.
--
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-13419) Add PostBuildScript global configuration
Nate Jones created JENKINS-13419: Summary: Add PostBuildScript global configuration Key: JENKINS-13419 URL: https://issues.jenkins-ci.org/browse/JENKINS-13419 Project: Jenkins Issue Type: New Feature Components: postbuildscript Environment: All Reporter: Nate Jones Assignee: gbois Priority: Minor We have many jobs in Jenkins (currently over 4K). Creating new build jobs is done programmatically. We are planning on using the PostBuildScript plugin soon and we have updated our job creation code to insert the appropriate configuration into each job. However, if we every want to change any PBS settings (like adding another script or changing the path of a script), we would have to go update all existing jobs. It would be very convenient to have a single global configuration that we can set up and then just make sure the plugin is enabled for all jobs. -- 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:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-10319. Resolution: Fixed > 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-tabpanel&focusedCommentId=161482#comment-161482 ] SCM/JIRA link daemon commented on JENKINS-10319: Code changed in jenkins User: Ulli Hafner Path: go.sh src/main/java/hudson/plugins/warnings/WarningsDescriptor.java src/main/java/hudson/plugins/warnings/WarningsProjectAction.java src/main/resources/hudson/plugins/warnings/WarningsPublisher/config.jelly src/main/resources/hudson/plugins/warnings/WarningsPublisher/config.properties src/main/resources/hudson/plugins/warnings/WarningsPublisher/config_de.properties http://jenkins-ci.org/commit/warnings-plugin/fb9ebbdc5d97f584ebd32a77fe4924fb213b9e85 Log: [FIXED JENKINS-10319] Moved trend configuration to descriptor. Compare: https://github.com/jenkinsci/warnings-plugin/compare/2dcbd87...fb9ebbd > 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-tabpanel&focusedCommentId=161481#comment-161481 ] SCM/JIRA link daemon commented on JENKINS-10319: Code changed in jenkins User: Ulli Hafner Path: src/main/java/hudson/plugins/analysis/core/AbstractProjectAction.java src/main/java/hudson/plugins/analysis/core/BuildHistory.java src/main/java/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet.java src/main/java/hudson/plugins/analysis/graph/BuildResultGraph.java src/main/java/hudson/plugins/analysis/graph/DefaultGraphConfigurationView.java src/main/java/hudson/plugins/analysis/graph/DifferenceGraph.java src/main/java/hudson/plugins/analysis/graph/GraphConfigurationView.java src/main/java/hudson/plugins/analysis/graph/UserGraphConfigurationView.java src/main/java/hudson/plugins/analysis/util/CategoryUrlBuilder.java http://jenkins-ci.org/commit/analysis-core-plugin/0f72aa2df9e3f352ceeea90cfdb5b0cce56aca20 Log: [FIXED JENKINS-10319] Moved trend configuration to descriptor. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/98210b4...0f72aa2 > 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-13420) Unable to serialize hudson.plugins.android_emulator.SdkInstaller
Juraci P. Kroehling created JENKINS-13420:
-
Summary: Unable to serialize
hudson.plugins.android_emulator.SdkInstaller
Key: JENKINS-13420
URL: https://issues.jenkins-ci.org/browse/JENKINS-13420
Project: Jenkins
Issue Type: Bug
Components: android-emulator
Affects Versions: current
Environment: Job running on a slave started via Java Web Start. Server
running on the cloud, slave running inside our office.
Reporter: Juraci P. Kroehling
Assignee: Christopher Orr
When starting a job which requires an Android SDK, we see the exception below.
This happens if we use ANDROID_HOME pointing to an existing installation (in
this case, the download of the SDK is not performed) as well as with automatic
download of the needed "tools".
{code}
Started by user dashboard
Building remotely on dashboard in workspace
/tmp/jenkins/workspace/CI-emulatortest
[android] No Android SDK found; let's install it automatically...
Downloading and installing Android SDK from
http://dl.google.com/android/android-sdk_r16-linux.tgz
[android] Base SDK installed successfully
[android] Going to install required Android SDK components...
[android] Installing the 'platform-tool,tool' SDK component(s)...
$ /tmp/jenkins/tools/android-sdk/tools/android update sdk -o -u -t
platform-tool,tool
Refresh Sources:
Fetching https://dl-ssl.google.com/android/repository/addons_list-1.xml
Validate XML
Parse XML
Fetched Add-ons List successfully
Refresh Sources
Fetching URL: https://dl-ssl.google.com/android/repository/repository-5.xml
Validate XML: https://dl-ssl.google.com/android/repository/repository-5.xml
Parse XML:https://dl-ssl.google.com/android/repository/repository-5.xml
Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
Fetching URL: http://dl.htcdev.com/sdk/addon.xml
Validate XML: http://dl.htcdev.com/sdk/addon.xml
Parse XML:http://dl.htcdev.com/sdk/addon.xml
Fetching URL: http://software.intel.com/sites/landingpage/android/addon.xml
Validate XML: http://software.intel.com/sites/landingpage/android/addon.xml
Parse XML:http://software.intel.com/sites/landingpage/android/addon.xml
Fetching URL: http://www.echobykyocera.com/download/echo_repository.xml
Validate XML: http://www.echobykyocera.com/download/echo_repository.xml
Parse XML:http://www.echobykyocera.com/download/echo_repository.xml
Fetching URL: http://developer.lgmobile.com/sdk/android/repository.xml
Validate XML: http://developer.lgmobile.com/sdk/android/repository.xml
Parse XML:http://developer.lgmobile.com/sdk/android/repository.xml
Fetching URL: http://android-sdk-addons.motodevupdate.com/addons.xml
Validate XML: http://android-sdk-addons.motodevupdate.com/addons.xml
Parse XML:http://android-sdk-addons.motodevupdate.com/addons.xml
Fetching URL:
http://innovator.samsungmobile.com/android/repository/repository.xml
Validate XML:
http://innovator.samsungmobile.com/android/repository/repository.xml
Parse XML:
http://innovator.samsungmobile.com/android/repository/repository.xml
Fetching URL: http://developer.sonyericsson.com/edk/android/repository.xml
Validate XML: http://developer.sonyericsson.com/edk/android/repository.xml
Parse XML:http://developer.sonyericsson.com/edk/android/repository.xml
Refresh Sources:
Fetching URL: https://dl-ssl.google.com/android/repository/addon.xml
Validate XML: https://dl-ssl.google.com/android/repository/addon.xml
Installing Archives:
Preparing to install archives
Downloading Android SDK Platform-tools, revision 11
(22%, 1087 KiB/s, 7 seconds left)
(41%, 1354 KiB/s, 4 seconds left)
(59%, 1468 KiB/s, 2 seconds left)
(77%, 1537 KiB/s, 1 seconds left)
(94%, 1565 KiB/s, 0 seconds left)
Installing Android SDK Platform-tools, revision 11
Stopping ADB server failed (code -1).
Unzipping Android SDK Platform-tools, revision 11 (4%)
Unzipping Android SDK Platform-tools, revision 11 (5%)
Unzipping Android SDK Platform-tools, revision 11 (6%)
Unzipping Android SDK Platform-tools, revision 11 (9%)
Unzipping Android SDK Platform-tools, revision 11 (18%)
Unzipping Android SDK Platform-tools, revision 11 (19%)
Unzipping Android SDK Platform-tools, revision 11 (99%)
Installed Android SDK Platform-tools, revision 11
Downloading Android SDK Tools, revision 18
(11%, 1605 KiB/s, 16 seconds left)
(17%, 1664 KiB/s, 14 seconds left)
(23%, 1689 KiB/s, 13 seconds left)
(29%, 1711 KiB/s, 11 seconds left)
(35%, 1727 KiB/s, 10 seconds left)
(41%, 1739 KiB/s, 9 seconds left)
(48%, 1748 KiB/s, 8 seconds left)
(54%, 1752 KiB/s, 7 seconds left)
(60%, 1758 KiB/s, 6 seconds left)
(66%, 1764 KiB/s, 5 seconds left)
(72%, 1768 KiB/s, 4 sec
[JIRA] (JENKINS-13417) git-plugin: rev-parse dereferencing tags breaks on Windows
[
https://issues.jenkins-ci.org/browse/JENKINS-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161483#comment-161483
]
Jay Berkenbilt commented on JENKINS-13417:
--
In case anyone is searching for this, I should mention that this problem
manifests itself as this error message in the build output:
ERROR: Couldn't find any revision to build. Verify the repository and branch
configuration for this job.
This is because the command "git rev-parse mastercommit" (in the case of the
default, which is to use the master branch) is failing.
> git-plugin: rev-parse dereferencing tags breaks on Windows
> --
>
> Key: JENKINS-13417
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13417
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Environment: Windows 2008 R2 slave launched with cygwin ssh, cygwin
> git
>Reporter: Jay Berkenbilt
>Assignee: Nicolas De Loof
>
> The change to GitAPI.java in commit 13f6038acc4fa5b5a62413155da6fc8cfcad3fe0
> seems to break the git plugin for Windows, at least in some circumstances.
> The syntax rev^{commit} gets mangled by cmd because ^ is a quote character.
> This means that cmd passes rev{commit} to git, which as a cygwin executable
> being run from Windows, further tries to do wildcard expansion and maps this
> to revcommit. Putting "" around rev^{commit} empirically seems to work,
> though I haven't tried it in the git plugin itself.
> This C fragment:
> {code}
> #include
> int main(int argc, char* argv[])
> {
> int i;
> for (i = 0; i < argc; ++i)
> {
> printf("%s\n", argv[i]);
> }
> return 0;
> }
> {code}
> when compiled with mingw to a native Windows application (a.exe) and invoked
> from cmd as a.exe a^{b} prints a{b}. When the same fragment is compiled with
> cygwin gcc to cygwin executable a.exe and is invoked the same way from cmd,
> it prints ab. Both print a^{b} when invoked from cmd as a.exe "a^{b}".
> I'm not sure what the fix is here other than perhaps detecting that this is
> windows and putting quotes around the argument in Windows.
> On another note, I left the Affects Version/s field blank. My Jenkins
> installation claims that it is using version 1.1.6. Looking at the git repo
> for the plugin, it appears that 1.1.6 should not have the ^{commit} fix, yet
> running strings on
> plugins/git/WEB-INF/classes/hudson/plugins/git/GitAPI.class clearly shows
> that my git plugin has that change in it.
--
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-tabpanel&focusedCommentId=161484#comment-161484 ] Ulli Hafner commented on JENKINS-10319: --- Integrated in !http://faktorzehn.org:8081/images/16x16/blue.png! [Jenkins Analysis Plug-ins (Compile) #459|http://faktorzehn.org:8081/job/Jenkins%20Analysis%20Plug-ins%20(Compile)/459/] [FIXED JENKINS-10319] Moved trend configuration to descriptor. (Revision 0f72aa2df9e3f352ceeea90cfdb5b0cce56aca20) Result = SUCCESS > 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-tabpanel&focusedCommentId=161485#comment-161485 ] dogfood commented on JENKINS-10319: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_analysis-core #10435|http://ci.jenkins-ci.org/job/plugins_analysis-core/10435/] [FIXED JENKINS-10319] Moved trend configuration to descriptor. (Revision 0f72aa2df9e3f352ceeea90cfdb5b0cce56aca20) Result = SUCCESS Ulli Hafner : Files : * src/main/java/hudson/plugins/analysis/graph/UserGraphConfigurationView.java * src/main/java/hudson/plugins/analysis/graph/GraphConfigurationView.java * src/main/java/hudson/plugins/analysis/core/AbstractProjectAction.java * src/main/java/hudson/plugins/analysis/graph/DifferenceGraph.java * src/main/java/hudson/plugins/analysis/graph/BuildResultGraph.java * src/main/java/hudson/plugins/analysis/core/BuildHistory.java * src/main/java/hudson/plugins/analysis/dashboard/AbstractWarningsTablePortlet.java * src/main/java/hudson/plugins/analysis/util/CategoryUrlBuilder.java * src/main/java/hudson/plugins/analysis/graph/DefaultGraphConfigurationView.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-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-tabpanel&focusedCommentId=161486#comment-161486 ] dogfood commented on JENKINS-10319: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_warnings #388|http://ci.jenkins-ci.org/job/plugins_warnings/388/] Result = SUCCESS > 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-13421) Windows Installer with old Plugins and without upgrade possibility
Sebo Stone created JENKINS-13421: Summary: Windows Installer with old Plugins and without upgrade possibility Key: JENKINS-13421 URL: https://issues.jenkins-ci.org/browse/JENKINS-13421 Project: Jenkins Issue Type: Bug Components: subversion Environment: Windows 7 64bit Reporter: Sebo Stone Priority: Blocker The Jenkins 1.459 Windows Installer includes the Subversion version 1.34, but the current version is 1.39! An Update to this version is not possible, neither with "install without restart" or with "Download now and install after restart". I also tried to install the version 1.39 by hand. Once I start the Jenkins service again, the version 1.34 will be installed again. The same problem exists with the plugins "Translation Assistance Plugin" (1.8 instead 1.9) and "CVS Plugin" (1.6 instead 2.2). -- 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-7104) Clearcase Plug-in 1.3 polling broken
[ https://issues.jenkins-ci.org/browse/JENKINS-7104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161487#comment-161487 ] Jordan Bentley commented on JENKINS-7104: - On my instance it doesn't even try to run lshistory: Started on Apr 11, 2012 2:16:16 PM [jenkins_psd48_Inspect_and_Analyze_jenkins] $ cleartool pwv -root [Inspect_and_Analyze] $ cleartool lsview jenkins_psd48_Inspect_and_Analyze_jenkins Done. Took 0.14 sec No changes Is this plugin still being actively developed? This is a large issue and hasn't been updated in a while. > Clearcase Plug-in 1.3 polling broken > > > Key: JENKINS-7104 > URL: https://issues.jenkins-ci.org/browse/JENKINS-7104 > Project: Jenkins > Issue Type: Bug > Components: clearcase >Affects Versions: current > Environment: RedHat Linux >Reporter: javakrieg >Assignee: Vincent Latombe > Attachments: build.xml > > > I was using Hudson 1.366. After I installed the new Clearcase 1.3 plug-in, I > noticed that polling no longer detected changes in my Clearcase vobs. > Polling would generate a normal report, but report no issues found. > I just updated to Hudson 1.368 and the same thing is still happening. -- 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-13421) Windows Installer with old Plugins and without upgrade possibility
[ https://issues.jenkins-ci.org/browse/JENKINS-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161488#comment-161488 ] Andrew Kujtan edited comment on JENKINS-13421 at 4/11/12 6:53 PM: -- It's a known issue, you can just create a "subversion.jpi.pinned" file with the plugin and it will update it. Super annoying though. @see [https://wiki.jenkins-ci.org/display/JENKINS/Pinned+Plugins] was (Author: andrewk): It's a known issue, you can just create a "subversion.jpi.pinned" file with the plugin and it will update it. Super annoying though. > Windows Installer with old Plugins and without upgrade possibility > -- > > Key: JENKINS-13421 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13421 > Project: Jenkins > Issue Type: Bug > Components: subversion > Environment: Windows 7 64bit >Reporter: Sebo Stone >Priority: Blocker > > The Jenkins 1.459 Windows Installer includes the Subversion version 1.34, but > the current version is 1.39! An Update to this version is not possible, > neither with "install without restart" or with "Download now and install > after restart". I also tried to install the version 1.39 by hand. Once I > start the Jenkins service again, the version 1.34 will be installed again. > The same problem exists with the plugins "Translation Assistance Plugin" (1.8 > instead 1.9) and "CVS Plugin" (1.6 instead 2.2). -- 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-13421) Windows Installer with old Plugins and without upgrade possibility
[ https://issues.jenkins-ci.org/browse/JENKINS-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161488#comment-161488 ] Andrew Kujtan commented on JENKINS-13421: - It's a known issue, you can just create a "subversion.jpi.pinned" file with the plugin and it will update it. Super annoying though. > Windows Installer with old Plugins and without upgrade possibility > -- > > Key: JENKINS-13421 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13421 > Project: Jenkins > Issue Type: Bug > Components: subversion > Environment: Windows 7 64bit >Reporter: Sebo Stone >Priority: Blocker > > The Jenkins 1.459 Windows Installer includes the Subversion version 1.34, but > the current version is 1.39! An Update to this version is not possible, > neither with "install without restart" or with "Download now and install > after restart". I also tried to install the version 1.39 by hand. Once I > start the Jenkins service again, the version 1.34 will be installed again. > The same problem exists with the plugins "Translation Assistance Plugin" (1.8 > instead 1.9) and "CVS Plugin" (1.6 instead 2.2). -- 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-13422) Release button column
[ https://issues.jenkins-ci.org/browse/JENKINS-13422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] wernight updated JENKINS-13422: --- Description: Like the existing build button column, a Build Release custom column would be nice. It just would show a build button like the release one. This would allow quickly making a release. I'm talking of course about a custom column that can be used in any Jenkins view. (was: Like the existing build button column, a Build Release custom column would be nice. It just would show a build button like the release one. This would allow quickly making a release.) > Release button column > - > > Key: JENKINS-13422 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13422 > Project: Jenkins > Issue Type: New Feature > Components: release >Reporter: wernight >Assignee: Peter Hayes > > Like the existing build button column, a Build Release custom column would be > nice. It just would show a build button like the release one. This would > allow quickly making a release. I'm talking of course about a custom column > that can be used in any Jenkins view. -- 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-13422) Release button column
wernight created JENKINS-13422: -- Summary: Release button column Key: JENKINS-13422 URL: https://issues.jenkins-ci.org/browse/JENKINS-13422 Project: Jenkins Issue Type: New Feature Components: release Reporter: wernight Assignee: Peter Hayes Like the existing build button column, a Build Release custom column would be nice. It just would show a build button like the release one. This would allow quickly making a release. -- 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-13348) EnvInject overriding WORKSPACE variable
[ https://issues.jenkins-ci.org/browse/JENKINS-13348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161489#comment-161489 ] gbois commented on JENKINS-13348: - Did you have time to test it? Thanks in advance. > 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-13325) PYTHONPATH gets undefined with latest 1.44 version of EnvInject
[
https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161490#comment-161490
]
gbois commented on JENKINS-13325:
-
I think these variables are not loaded by the Jenkins process.
Could you check if Jenkins process reads the .bash_profile file?
Jenkins expects to have all these variables resolved.
For example:
DEVHOME=/usr/local/jenkins
SRC_SHARED=${DEVHOME}/Projects/Shared
is OK because the SRC_SHARED variable can be resolved with DEVHOME value but
only if DEVHOME is take into account (loaded by the Jenkins process).
Please check 'Manage Jenkins > System Information' and check if each variable
can be resolved.
> 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.
--
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-13296) Changelists that include excluded files and files outside of the client view will trigger a build.
[ https://issues.jenkins-ci.org/browse/JENKINS-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161491#comment-161491 ] Patrick McKeown commented on JENKINS-13296: --- Just confirmed this is working. In the p4 polling log the file that was outside the view mapping did not appear in the Exclude file(s) found: message. Thanks again! > Changelists that include excluded files and files outside of the client view > will trigger a build. > -- > > Key: JENKINS-13296 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13296 > Project: Jenkins > Issue Type: Improvement > Components: perforce >Reporter: Patrick McKeown >Assignee: Rob Petti >Priority: Minor > > If there is already a way to handle this I apologize, looked around but > didn't find anything. > Given a client spec > //depot/test/... //client/test/... > with an exclude list such as > //depot/test/exclude/... > and polling turned on- > if someone submits a changelist with an excluded file and a file outside the > client spec such as > changelist 1234 > //depot/test/exclude/example.txt#1 > //depot/test2/example2.txt#1 > then //depot/test2/example2.txt#1 will trigger the build as it does not match > anything in the exclude list. > I would like a way to consider any files outside of the client spec as > excluded files without actually having to specify them. Thanks! -- 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-13296) Changelists that include excluded files and files outside of the client view will trigger a build.
[ https://issues.jenkins-ci.org/browse/JENKINS-13296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti resolved JENKINS-13296. - Resolution: Fixed > Changelists that include excluded files and files outside of the client view > will trigger a build. > -- > > Key: JENKINS-13296 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13296 > Project: Jenkins > Issue Type: Improvement > Components: perforce >Reporter: Patrick McKeown >Assignee: Rob Petti >Priority: Minor > > If there is already a way to handle this I apologize, looked around but > didn't find anything. > Given a client spec > //depot/test/... //client/test/... > with an exclude list such as > //depot/test/exclude/... > and polling turned on- > if someone submits a changelist with an excluded file and a file outside the > client spec such as > changelist 1234 > //depot/test/exclude/example.txt#1 > //depot/test2/example2.txt#1 > then //depot/test2/example2.txt#1 will trigger the build as it does not match > anything in the exclude list. > I would like a way to consider any files outside of the client spec as > excluded files without actually having to specify them. Thanks! -- 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-13423) Environment Variables documentation missing GIT_COMMIT and GIT_BRANCH
dserodio created JENKINS-13423: -- Summary: Environment Variables documentation missing GIT_COMMIT and GIT_BRANCH Key: JENKINS-13423 URL: https://issues.jenkins-ci.org/browse/JENKINS-13423 Project: Jenkins Issue Type: Improvement Components: core Affects Versions: current Reporter: dserodio Priority: Minor The documentation about Environment Variables included with Jenkins doesn't mention the GIT_COMMIT and GIT_BRANCH variables (the Jenkins website does mention these). -- 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-13424) Need option to run "accurev replica sync" before populating the stream
pickgr1 created JENKINS-13424: - Summary: Need option to run "accurev replica sync" before populating the stream Key: JENKINS-13424 URL: https://issues.jenkins-ci.org/browse/JENKINS-13424 Project: Jenkins Issue Type: Bug Components: accurev Environment: plugin version is 0.6.18 Reporter: pickgr1 Assignee: Scott Tatum This needs to either be an option or the default behavior. Ideally, this is the default behavior or a global setting so we don't have to re-configure all of our projects. -- 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-13396) EnvInject plug-in does not read ${WORKSPACE} property
[
https://issues.jenkins-ci.org/browse/JENKINS-13396?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161493#comment-161493
]
John Bayley commented on JENKINS-13396:
---
Thanks for the speedy reply. I didn't look for the existence of the "Inject
environment variables to the build process" check-box after selecting the
preceding "Prepare an environment for the run" check-box. Now I know!
> EnvInject plug-in does not read ${WORKSPACE} property
> -
>
> Key: JENKINS-13396
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13396
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
>Affects Versions: current
> Environment: Jenkins v1.458 on Linux (CentOS v5.6)
> EnvInject v1.45
>Reporter: John Bayley
>Assignee: gbois
>
> In the EnvInject plug-in configuration for a job, both the "Keep Jenkins
> Environment Variables" and "Keep Jenkins Build Variables" check-boxes are
> selected.
> The "Properties Content" section sets the following property:
> M2_REPO = ${WORKSPACE}/.repository
> However, when a build runs, the log reports:
> [EnvInject] - Loading node environment variables.
> [EnvInject] - Preparing an environment for the build.
> [EnvInject] - Keep Jenkins system variables.
> [EnvInject] - Keep Jenkins build variables.
> [EnvInject] - Injecting as environment variables the properties content
> M2_REPO=${WORKSPACE}/.repository
> [EnvInject] - Variables injected successfully.
> [EnvInject] - Unset unresolved 'M2_REPO' variable.
> and the build operates as if the environment variable is unset. The
> ${WORKSPACE} property appears to be ignored.
--
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-13423) Environment Variables documentation missing GIT_COMMIT and GIT_BRANCH
[ https://issues.jenkins-ci.org/browse/JENKINS-13423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > Environment Variables documentation missing GIT_COMMIT and GIT_BRANCH > - > > Key: JENKINS-13423 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13423 > Project: Jenkins > Issue Type: Improvement > Components: core >Affects Versions: current >Reporter: dserodio >Priority: Minor > > The documentation about Environment Variables included with Jenkins doesn't > mention the GIT_COMMIT and GIT_BRANCH variables (the Jenkins website does > mention these). -- 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-13423) Environment Variables documentation missing GIT_COMMIT and GIT_BRANCH
[ https://issues.jenkins-ci.org/browse/JENKINS-13423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161494#comment-161494 ] gbois commented on JENKINS-13423: - You're right. At the moment, the environment page is static. GIT variables are provided by the GIT plugin. > Environment Variables documentation missing GIT_COMMIT and GIT_BRANCH > - > > Key: JENKINS-13423 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13423 > Project: Jenkins > Issue Type: Improvement > Components: core >Affects Versions: current >Reporter: dserodio >Priority: Minor > > The documentation about Environment Variables included with Jenkins doesn't > mention the GIT_COMMIT and GIT_BRANCH variables (the Jenkins website does > mention these). -- 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-13423) Environment Variables documentation missing GIT_COMMIT and GIT_BRANCH
[ https://issues.jenkins-ci.org/browse/JENKINS-13423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161495#comment-161495 ] dserodio commented on JENKINS-13423: https://github.com/jenkinsci/jenkins/pull/434 > Environment Variables documentation missing GIT_COMMIT and GIT_BRANCH > - > > Key: JENKINS-13423 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13423 > Project: Jenkins > Issue Type: Improvement > Components: core >Affects Versions: current >Reporter: dserodio >Priority: Minor > > The documentation about Environment Variables included with Jenkins doesn't > mention the GIT_COMMIT and GIT_BRANCH variables (the Jenkins website does > mention these). -- 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-13418) PostBuildScript plugin does not load its configuration properly
[
https://issues.jenkins-ci.org/browse/JENKINS-13418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161496#comment-161496
]
SCM/JIRA link daemon commented on JENKINS-13418:
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/resources/org/jenkinsci/plugins/postbuildscript/PostBuildScript/config.jelly
http://jenkins-ci.org/commit/postbuildscript-plugin/8fb91fbb3112fb540977b9e13411ffd9e64d4f04
Log:
Fix JENKINS-13418
> PostBuildScript plugin does not load its configuration properly
> ---
>
> Key: JENKINS-13418
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13418
> Project: Jenkins
> Issue Type: Bug
> Components: postbuildscript
> Environment: Jenkins: v. 1.458 (but also 1.419)
> OS: Debian Lenny/Squeeze
>Reporter: Nate Jones
>Assignee: gbois
>Priority: Minor
> Attachments: screenshot1.png, screenshot2.png
>
>
> The PostBuildScript plugin works great.
> However, I've noticed that when I load up the configuration page for my job
> in jenkins, the PBS information is missing. The config in screenshot1.png
> doesn't show up when the configuration is loaded again in screenshot2.png.
> If the config.xml is examined, the data is there:
> {noformat}
>
>
>
> /usr/bin/send_post_build_message.sh
>
>
> false
>
> {noformat}
> And after saving the second time (as in screenshot2.png), the script is
> missing from config.xml:
> {noformat}
>
> false
>
> {noformat}
> I've made some customizations to the PBS plugin (as seen here
> https://github.com/mediatemple/postbuildscript-plugin in the
> build_info_as_env branch), but after looking at the code for a while, I think
> this is a little above my ken.
--
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-13418) PostBuildScript plugin does not load its configuration properly
[
https://issues.jenkins-ci.org/browse/JENKINS-13418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161497#comment-161497
]
gbois commented on JENKINS-13418:
-
It was an issue in the UI.
I fixed it.
For your customizations on your fork, do not hesitate to provide a pull request.
Thanks
> PostBuildScript plugin does not load its configuration properly
> ---
>
> Key: JENKINS-13418
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13418
> Project: Jenkins
> Issue Type: Bug
> Components: postbuildscript
> Environment: Jenkins: v. 1.458 (but also 1.419)
> OS: Debian Lenny/Squeeze
>Reporter: Nate Jones
>Assignee: gbois
>Priority: Minor
> Attachments: screenshot1.png, screenshot2.png
>
>
> The PostBuildScript plugin works great.
> However, I've noticed that when I load up the configuration page for my job
> in jenkins, the PBS information is missing. The config in screenshot1.png
> doesn't show up when the configuration is loaded again in screenshot2.png.
> If the config.xml is examined, the data is there:
> {noformat}
>
>
>
> /usr/bin/send_post_build_message.sh
>
>
> false
>
> {noformat}
> And after saving the second time (as in screenshot2.png), the script is
> missing from config.xml:
> {noformat}
>
> false
>
> {noformat}
> I've made some customizations to the PBS plugin (as seen here
> https://github.com/mediatemple/postbuildscript-plugin in the
> build_info_as_env branch), but after looking at the code for a while, I think
> this is a little above my ken.
--
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-13418) PostBuildScript plugin does not load its configuration properly
[
https://issues.jenkins-ci.org/browse/JENKINS-13418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-13418.
-
Resolution: Fixed
> PostBuildScript plugin does not load its configuration properly
> ---
>
> Key: JENKINS-13418
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13418
> Project: Jenkins
> Issue Type: Bug
> Components: postbuildscript
> Environment: Jenkins: v. 1.458 (but also 1.419)
> OS: Debian Lenny/Squeeze
>Reporter: Nate Jones
>Assignee: gbois
>Priority: Minor
> Attachments: screenshot1.png, screenshot2.png
>
>
> The PostBuildScript plugin works great.
> However, I've noticed that when I load up the configuration page for my job
> in jenkins, the PBS information is missing. The config in screenshot1.png
> doesn't show up when the configuration is loaded again in screenshot2.png.
> If the config.xml is examined, the data is there:
> {noformat}
>
>
>
> /usr/bin/send_post_build_message.sh
>
>
> false
>
> {noformat}
> And after saving the second time (as in screenshot2.png), the script is
> missing from config.xml:
> {noformat}
>
> false
>
> {noformat}
> I've made some customizations to the PBS plugin (as seen here
> https://github.com/mediatemple/postbuildscript-plugin in the
> build_info_as_env branch), but after looking at the code for a while, I think
> this is a little above my ken.
--
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-13425) Upgraded to 1.459 - Promotions now fail
Andrew Knapp created JENKINS-13425: -- Summary: Upgraded to 1.459 - Promotions now fail Key: JENKINS-13425 URL: https://issues.jenkins-ci.org/browse/JENKINS-13425 Project: Jenkins Issue Type: Bug Components: promoted-builds Affects Versions: current Reporter: Andrew Knapp Priority: Blocker Just upgrading to jenkins 1.459, and now none of my promotions run, with this error message: 14:28:23 Started by upstream project "lanai-master/promotion/tapp-sandbox-rollout" build number 2169 14:28:23 FATAL: null 14:28:23 java.lang.NullPointerException 14:28:23at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:85) 14:28:23at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:46) 14:28:23at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188) 14:28:23at hudson.model.Run.run(Run.java:1408) 14:28:23at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 14:28:23at hudson.model.ResourceController.execute(ResourceController.java:88) 14:28:23at hudson.model.Executor.run(Executor.java:238) Let me know if you need anything else. -- 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-12520) Post Build Shell Script initiates irrespective of Maven2 build status
[ https://issues.jenkins-ci.org/browse/JENKINS-12520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-12520. --- Resolution: Won't Fix I'm closing due to a lack of inputs > Post Build Shell Script initiates irrespective of Maven2 build status > - > > Key: JENKINS-12520 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12520 > Project: Jenkins > Issue Type: Bug > Components: core, maven2, postbuild-task, postbuildscript >Reporter: Jayakrishnan Nair >Assignee: gbois > Labels: maven > > Post Build Shell Script initiates irrespective of Maven2 build status > The maven2 build fails and shows a BUILD ERROR in the console output of the > build. ( added -Dmaven.test.failure.ignore=false ) > According to the configuration the shell scripts will only initiate if build > is successful. > But still the scripts get executed !!! -- 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-12492) Manage SSH keys for Git in web GUI
[ https://issues.jenkins-ci.org/browse/JENKINS-12492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161499#comment-161499 ] Steven Cole commented on JENKINS-12492: --- Heartily agree. I'm still trying to figure out how to get the git plugin to use the keys I've assigned to Jenkins. > Manage SSH keys for Git in web GUI > -- > > Key: JENKINS-12492 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12492 > Project: Jenkins > Issue Type: Improvement > Components: git >Affects Versions: current >Reporter: henrik242 >Assignee: abayer > > Right now I have to manage SSH keys on the filesystem in order to use the Git > plugin. If I could manage (add/delete/edit) the SSH keys in the web GUI, it > would make the Git hookup process much simpler and intuitive. In my > experience this is the number one hurdle for new Jenkins users as they try to > connect to a GitHub repo. -- 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-13425) Upgraded to 1.459 - Promotions now fail
[ https://issues.jenkins-ci.org/browse/JENKINS-13425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161500#comment-161500 ] Andrew Knapp commented on JENKINS-13425: Actually, it looks like the promotion runs fine, but then the actual build spits this out. The problem is that when I run the build manually (with the required parameters) it runs fine. Only out of promotions is this happening. > Upgraded to 1.459 - Promotions now fail > --- > > Key: JENKINS-13425 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13425 > Project: Jenkins > Issue Type: Bug > Components: promoted-builds >Affects Versions: current >Reporter: Andrew Knapp >Priority: Blocker > > Just upgrading to jenkins 1.459, and now none of my promotions run, with this > error message: > 14:28:23 Started by upstream project > "lanai-master/promotion/tapp-sandbox-rollout" build number 2169 > 14:28:23 FATAL: null > 14:28:23 java.lang.NullPointerException > 14:28:23 at > org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:85) > 14:28:23 at > org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:46) > 14:28:23 at > hudson.model.listeners.RunListener.fireStarted(RunListener.java:188) > 14:28:23 at hudson.model.Run.run(Run.java:1408) > 14:28:23 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > 14:28:23 at > hudson.model.ResourceController.execute(ResourceController.java:88) > 14:28:23 at hudson.model.Executor.run(Executor.java:238) > Let me know if you need anything else. -- 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-13419) Add PostBuildScript global configuration
[ https://issues.jenkins-ci.org/browse/JENKINS-13419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13419 started by gbois. > Add PostBuildScript global configuration > > > Key: JENKINS-13419 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13419 > Project: Jenkins > Issue Type: New Feature > Components: postbuildscript > Environment: All >Reporter: Nate Jones >Assignee: gbois >Priority: Minor > > We have many jobs in Jenkins (currently over 4K). Creating new build jobs is > done programmatically. We are planning on using the PostBuildScript plugin > soon and we have updated our job creation code to insert the appropriate > configuration into each job. > However, if we every want to change any PBS settings (like adding another > script or changing the path of a script), we would have to go update all > existing jobs. It would be very convenient to have a single global > configuration that we can set up and then just make sure the plugin is > enabled for all jobs. -- 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-13419) Add PostBuildScript global configuration
[ https://issues.jenkins-ci.org/browse/JENKINS-13419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161501#comment-161501 ] gbois commented on JENKINS-13419: - Good idea. I'll look at it. Waiting a solution, could you check SharedObjects plugin, maybe the future solution can use it. > Add PostBuildScript global configuration > > > Key: JENKINS-13419 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13419 > Project: Jenkins > Issue Type: New Feature > Components: postbuildscript > Environment: All >Reporter: Nate Jones >Assignee: gbois >Priority: Minor > > We have many jobs in Jenkins (currently over 4K). Creating new build jobs is > done programmatically. We are planning on using the PostBuildScript plugin > soon and we have updated our job creation code to insert the appropriate > configuration into each job. > However, if we every want to change any PBS settings (like adding another > script or changing the path of a script), we would have to go update all > existing jobs. It would be very convenient to have a single global > configuration that we can set up and then just make sure the plugin is > enabled for all jobs. -- 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-9538) hudson.model.FreeStyleBuild & GradleInstallation not serializable => Gradle build not working anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-9538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161502#comment-161502 ] SCM/JIRA link daemon commented on JENKINS-9538: --- Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/gradle/GradleInstallation.java http://jenkins-ci.org/commit/gradle-plugin/cdf64a127aad602b99fda0321fec61a892e156d8 Log: Fix JENKINS-9538 Compare: https://github.com/jenkinsci/gradle-plugin/compare/c76c4bc...cdf64a1 > hudson.model.FreeStyleBuild & GradleInstallation not serializable => Gradle > build not working anymore > - > > Key: JENKINS-9538 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9538 > Project: Jenkins > Issue Type: Bug > Components: gradle >Affects Versions: current > Environment: Jenkins ver. 1.409 >Reporter: Joern Huxhorn >Assignee: gbois > > I switched build back to "Use Gradle Wrapper" in "Invoke Gradle script" > configuration from a previously manually defined Gradle. > This may be related to master/slave configuration, i.e. I think that the > problem exists because the changed Gradle plugin configuration can't be > synced to the slave. > FATAL: Unable to serialize hudson.plugins.gradle.GradleInstallation$2@100e3d5 > java.io.IOException: Unable to serialize > hudson.plugins.gradle.GradleInstallation$2@100e3d5 > at hudson.remoting.UserRequest.serialize(UserRequest.java:166) > at hudson.remoting.UserRequest.(UserRequest.java:62) > at hudson.remoting.Channel.call(Channel.java:642) > at > hudson.plugins.gradle.GradleInstallation.getWrapperExecutable(GradleInstallation.java:72) > at hudson.plugins.gradle.Gradle.perform(Gradle.java:154) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:649) > at hudson.model.Build$RunnerImpl.build(Build.java:177) > at hudson.model.Build$RunnerImpl.doRun(Build.java:139) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:423) > at hudson.model.Run.run(Run.java:1362) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:145) > Caused by: java.io.NotSerializableException: hudson.model.FreeStyleBuild > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) > at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) > at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) > at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) > at hudson.remoting.UserRequest._serialize(UserRequest.java:155) > at hudson.remoting.UserRequest.serialize(UserRequest.java:164) > ... 13 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-9538) hudson.model.FreeStyleBuild & GradleInstallation not serializable => Gradle build not working anymore
[ https://issues.jenkins-ci.org/browse/JENKINS-9538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-9538. Resolution: Fixed > hudson.model.FreeStyleBuild & GradleInstallation not serializable => Gradle > build not working anymore > - > > Key: JENKINS-9538 > URL: https://issues.jenkins-ci.org/browse/JENKINS-9538 > Project: Jenkins > Issue Type: Bug > Components: gradle >Affects Versions: current > Environment: Jenkins ver. 1.409 >Reporter: Joern Huxhorn >Assignee: gbois > > I switched build back to "Use Gradle Wrapper" in "Invoke Gradle script" > configuration from a previously manually defined Gradle. > This may be related to master/slave configuration, i.e. I think that the > problem exists because the changed Gradle plugin configuration can't be > synced to the slave. > FATAL: Unable to serialize hudson.plugins.gradle.GradleInstallation$2@100e3d5 > java.io.IOException: Unable to serialize > hudson.plugins.gradle.GradleInstallation$2@100e3d5 > at hudson.remoting.UserRequest.serialize(UserRequest.java:166) > at hudson.remoting.UserRequest.(UserRequest.java:62) > at hudson.remoting.Channel.call(Channel.java:642) > at > hudson.plugins.gradle.GradleInstallation.getWrapperExecutable(GradleInstallation.java:72) > at hudson.plugins.gradle.Gradle.perform(Gradle.java:154) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:649) > at hudson.model.Build$RunnerImpl.build(Build.java:177) > at hudson.model.Build$RunnerImpl.doRun(Build.java:139) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:423) > at hudson.model.Run.run(Run.java:1362) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:145) > Caused by: java.io.NotSerializableException: hudson.model.FreeStyleBuild > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156) > at > java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509) > at > java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474) > at > java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326) > at hudson.remoting.UserRequest._serialize(UserRequest.java:155) > at hudson.remoting.UserRequest.serialize(UserRequest.java:164) > ... 13 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-11147) Build SUCCESSFUL but still I get Finished: FAILURE
[ https://issues.jenkins-ci.org/browse/JENKINS-11147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-11147. - Resolution: Fixed It is due to your init script > Build SUCCESSFUL but still I get Finished: FAILURE > -- > > Key: JENKINS-11147 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11147 > Project: Jenkins > Issue Type: Bug > Components: gradle >Affects Versions: current > Environment: Windows XP >Reporter: Pranav Varshney >Assignee: gbois > Attachments: config.xml > > > I am using Jenkins with Gradle plugin. I am able to build my module but I get > the following error - "Error occurred while writing Gradle Init Script: null" > This is the console output > Started by user anonymous > Error occurred while writing Gradle Init Script: null > [workspace] $ cmd.exe /C D:\gradle-1.0-milestone-3\bin\gradle.bat build && > exit %%ERRORLEVEL%% > :compileJava UP-TO-DATE > :processResources UP-TO-DATE > :classes UP-TO-DATE > :jar UP-TO-DATE > :assemble UP-TO-DATE > :compileTestJava UP-TO-DATE > :processTestResources UP-TO-DATE > :testClasses UP-TO-DATE > :test UP-TO-DATE > :check UP-TO-DATE > :build UP-TO-DATE > BUILD SUCCESSFUL > Total time: 1.812 secs > Sending e-mails to: pranavv@*.com > Finished: FAILURE > > I am attaching configuration file. > Regards, > Pranav -- 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
[ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161504#comment-161504 ] Marc Sanfacon commented on JENKINS-13325: - The variables were not defined in the Jenkins process, only in the .bash_profile. Looks like the ssh command does not run the .bash_profile. I modified the launch script and they are now defined. I upgraded to the latest build of EnvInject (1.44) and it fixes the problem. 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. -- 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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
[
https://issues.jenkins-ci.org/browse/JENKINS-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161505#comment-161505
]
SCM/JIRA link daemon commented on JENKINS-13412:
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/hudson/plugins/gradle/Gradle.java
http://jenkins-ci.org/commit/gradle-plugin/ff6465b3681cf2dab7f5eb8dcb0eb7a3193df547
Log:
Fix JENKINS-13412
> Gradle plugin fails to quote parameters without whitespace when containing
> input/output redirection symbols, e.g. in XML strings
>
>
> Key: JENKINS-13412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
> Project: Jenkins
> Issue Type: Bug
> Components: gradle
>Affects Versions: current
> Environment: Windows Server 2008 R2
> Jenkins 1.424.6
> Jenkins Gradle Plugin 1.12
>Reporter: Daniel Beck
>Assignee: gbois
>
> Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
> call.
> If one of these arguments looks like XML, but does not contain whitespace, it
> is not quoted. This leads to problems with input/output redirection symbols
> (less-than, greater-than)
> Example String Parameter value:
> {code}
>
> {code}
> Results in the following build output:
> {code}
> [workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
> %%ERRORLEVEL%%
> The system cannot find the file specified.
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Notifying upstream projects of job completion
> {code}
> Real world example:
> Copy artifacts plugin's "Latest successful build" has the value:
> {code}
>
> {code}
> This results in "File not found" errors on Windows Server. Not tested on
> Linux.
--
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
[ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161506#comment-161506 ] gbois commented on JENKINS-13325: - I'm happy to read that > 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. -- 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
[ https://issues.jenkins-ci.org/browse/JENKINS-13325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois resolved JENKINS-13325. - Resolution: Fixed > 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. -- 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-13412) Gradle plugin fails to quote parameters without whitespace when containing input/output redirection symbols, e.g. in XML strings
[
https://issues.jenkins-ci.org/browse/JENKINS-13412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-13412.
-
Resolution: Fixed
> Gradle plugin fails to quote parameters without whitespace when containing
> input/output redirection symbols, e.g. in XML strings
>
>
> Key: JENKINS-13412
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13412
> Project: Jenkins
> Issue Type: Bug
> Components: gradle
>Affects Versions: current
> Environment: Windows Server 2008 R2
> Jenkins 1.424.6
> Jenkins Gradle Plugin 1.12
>Reporter: Daniel Beck
>Assignee: gbois
>
> Gradle plugin explicitly passes job parameters to the "cmd.exe /c gradle.bat"
> call.
> If one of these arguments looks like XML, but does not contain whitespace, it
> is not quoted. This leads to problems with input/output redirection symbols
> (less-than, greater-than)
> Example String Parameter value:
> {code}
>
> {code}
> Results in the following build output:
> {code}
> [workspace] $ cmd.exe /C C:\path\to\gradle.bat -Dfoo= -i && exit
> %%ERRORLEVEL%%
> The system cannot find the file specified.
> Build step 'Invoke Gradle script' changed build result to FAILURE
> Build step 'Invoke Gradle script' marked build as failure
> Notifying upstream projects of job completion
> {code}
> Real world example:
> Copy artifacts plugin's "Latest successful build" has the value:
> {code}
>
> {code}
> This results in "File not found" errors on Windows Server. Not tested on
> Linux.
--
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-13317) Mail not sent: NullPointerException in plugins.ContentBuilder.transformText(ContentBuilder.java:68)
[ https://issues.jenkins-ci.org/browse/JENKINS-13317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161508#comment-161508 ] SCM/JIRA link daemon commented on JENKINS-13317: Code changed in jenkins User: slide Path: src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java src/test/java/hudson/plugins/emailext/plugins/ContentBuilderTest.java http://jenkins-ci.org/commit/email-ext-plugin/a75006ea9298eaaf66183ca283fb14016ed90840 Log: Merge pull request #38 from hajush/master Fix JENKINS-13317 - prevent null String derefences from the default Subject, Body, Recipient lists. Compare: https://github.com/jenkinsci/email-ext-plugin/compare/8e08512...a75006e > Mail not sent: NullPointerException in > plugins.ContentBuilder.transformText(ContentBuilder.java:68) > --- > > Key: JENKINS-13317 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13317 > Project: Jenkins > Issue Type: Bug > Components: email-ext >Affects Versions: current > Environment: jdk1.6.0_29 Linux >Reporter: Chris J >Assignee: shinsato >Priority: Blocker > Labels: email-ext, exception, plugin > Attachments: email-ext.hpi > > > email-ext fails with a NullPointerException when sending some emails (not > all). > I am not a java developer but if someone could send me a version of email-ext > having this line (ContentBuilder.java:68) devided in several lines, next time > it fails we could locate more precisely the error. > Here is the stack I have: > -- > Build step 'Execute shell' marked build as failure > Email was triggered for: Failure > Sending email for trigger: Failure > ERROR: Could not send email as a part of the post-build publishers. > java.lang.NullPointerException > at java.util.regex.Matcher.quoteReplacement(Matcher.java:598) > at > hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:68) > at > hudson.plugins.emailext.ExtendedEmailPublisher.setSubject(ExtendedEmailPublisher.java:463) > at > hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:311) > at > hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:259) > at > hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:251) > at > hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:211) > at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) > 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.cleanUp(Build.java:171) > at hudson.model.Run.run(Run.java:1454) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:238) > Finished: FAILURE -- 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-12577) Email notification hangs due to NullPointerException
[ https://issues.jenkins-ci.org/browse/JENKINS-12577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161507#comment-161507 ] SCM/JIRA link daemon commented on JENKINS-12577: Code changed in jenkins User: Harold Shinsato Path: src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java src/test/java/hudson/plugins/emailext/plugins/ContentBuilderTest.java http://jenkins-ci.org/commit/email-ext-plugin/90376763efcf7cd00c795d9e9c07c184bc0a7f56 Log: Fix for JENKINS-12577- prevent dereferencing null default subject and body fields + plus unit test > Email notification hangs due to NullPointerException > > > Key: JENKINS-12577 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12577 > Project: Jenkins > Issue Type: Bug > Components: email-ext >Affects Versions: current > Environment: Windows 2008 Server x64, Java 1.6.0_25 >Reporter: Costin Caraivan >Priority: Blocker > Attachments: template.jelly > > > We have an email notification which uses a Jelly template. So far it worked > ok, but recently we started getting these: > Jan 25, 2012 2:11:23 PM hudson.plugins.emailext.ExtendedEmailPublisher > sendMail > WARNING: Could not send email. > java.lang.NullPointerException > at hudson.model.Slave.createLauncher(Slave.java:311) > at > hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:60) > at > hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:100) > at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:488) > at > hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:331) > at > hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:251) > at > hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:243) > at > hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:203) > at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:694) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:669) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:647) > at hudson.model.Build$RunnerImpl.cleanUp(Build.java:171) > at hudson.model.Run.run(Run.java:1448) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) -- 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-13421) Windows Installer with old Plugins and without upgrade possibility
[ https://issues.jenkins-ci.org/browse/JENKINS-13421?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161509#comment-161509 ] Sebo Stone commented on JENKINS-13421: -- All right, thank you! > Windows Installer with old Plugins and without upgrade possibility > -- > > Key: JENKINS-13421 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13421 > Project: Jenkins > Issue Type: Bug > Components: subversion > Environment: Windows 7 64bit >Reporter: Sebo Stone >Priority: Blocker > > The Jenkins 1.459 Windows Installer includes the Subversion version 1.34, but > the current version is 1.39! An Update to this version is not possible, > neither with "install without restart" or with "Download now and install > after restart". I also tried to install the version 1.39 by hand. Once I > start the Jenkins service again, the version 1.34 will be installed again. > The same problem exists with the plugins "Translation Assistance Plugin" (1.8 > instead 1.9) and "CVS Plugin" (1.6 instead 2.2). -- 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-13411) Klocwork XML output is deprecated
[ https://issues.jenkins-ci.org/browse/JENKINS-13411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161510#comment-161510 ] gbois commented on JENKINS-13411: - Thanks so much for reporting that. This is a bad news. Unfortunately, the Klocwork strategy is to not expose its reports. I think they want to privilege their internal dashboard. > Klocwork XML output is deprecated > - > > Key: JENKINS-13411 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13411 > Project: Jenkins > Issue Type: New Feature > Components: klocwork >Reporter: Krzysztof Malinowski >Assignee: gbois > > As http://www.klocwork.com/products/documentation/current/Kwinspectreport > states: XML report is deprecated in KW 9.5 and will no longer be available. I > recommend that plugin uses some other parser for the issues (csv maybe) or > use web api to get the issues. -- 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-13413) Git icon(git-48x48.png) missing in job page.
[ https://issues.jenkins-ci.org/browse/JENKINS-13413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] sogabe updated JENKINS-13413: - Environment: Git Plugin 1.1.17 Tomcat 7 was:Git Plugin 1.1.17 > Git icon(git-48x48.png) missing in job page. > - > > Key: JENKINS-13413 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13413 > Project: Jenkins > Issue Type: Bug > Components: git > Environment: Git Plugin 1.1.17 > Tomcat 7 >Reporter: sogabe >Assignee: Nicolas De Loof >Priority: Minor > Attachments: git-icon_missing.png > > > After updating to Git Plugin 1.1.17, Git icon is missing in job page. -- 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-13405) JDK Automatic install fails on Debian
[
https://issues.jenkins-ci.org/browse/JENKINS-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161511#comment-161511
]
Kean Lau commented on JENKINS-13405:
I'm getting this problem as well. It looks like Oracle has changed the Java
website to now require authentication for downloads. This is the error webpage
that gets written into {{jdk.sh}}:
{quote}
Sorry!
In order to download products from Oracle Technology Network you must agree to
the OTN license terms.
Be sure that...
Your browser has "cookies" and JavaScript enabled.
You clicked on "Accept License" for the product you wish to download.
You attempt the download within 30 minutes of accepting the license.
{quote}
This problem affects all SSH based slaves.
> JDK Automatic install fails on Debian
> -
>
> Key: JENKINS-13405
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13405
> Project: Jenkins
> Issue Type: Bug
> Components: javanet
>Reporter: Jesse Bowes
> Attachments: jdk.sh.html
>
>
> I have my Jenkins system set up to automatically install Java 7. When I add
> a new project and try to build, I see errors saying:
> Started by an SCM change
> Building in workspace /var/lib/jenkins/jobs/FeedWatcher/workspace
> Installing /var/lib/jenkins/tools/Java_SE_7/jdk.sh
> [Java_SE_7] $ /var/lib/jenkins/tools/Java_SE_7/jdk.sh -noregister
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 1: cannot open html: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 2: cannot open head: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 3: cannot open title: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 3: Request: not found
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 4: cannot open META: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 5: cannot open link: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 6: cannot open link: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 7:
> : not found
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 8: cannot open body: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 9: cannot open div: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 10: cannot open table: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 11: cannot open tr: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 12: Syntax error: redirection
> unexpected
> ERROR: Failed to install JDK. Exit code=2
> Finished: FAILURE
> Looking at /var/lib/jenkins/tools/Java_SE_7/jdk.sh, I see it's HTML generated
> from an Oracle site.
--
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-13405) JDK Automatic install fails on Debian
[
https://issues.jenkins-ci.org/browse/JENKINS-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kean Lau updated JENKINS-13405:
---
Attachment: jdk.sh.html
Attaching a copy of {{jdk.sh}}
> JDK Automatic install fails on Debian
> -
>
> Key: JENKINS-13405
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13405
> Project: Jenkins
> Issue Type: Bug
> Components: javanet
>Reporter: Jesse Bowes
> Attachments: jdk.sh.html
>
>
> I have my Jenkins system set up to automatically install Java 7. When I add
> a new project and try to build, I see errors saying:
> Started by an SCM change
> Building in workspace /var/lib/jenkins/jobs/FeedWatcher/workspace
> Installing /var/lib/jenkins/tools/Java_SE_7/jdk.sh
> [Java_SE_7] $ /var/lib/jenkins/tools/Java_SE_7/jdk.sh -noregister
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 1: cannot open html: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 2: cannot open head: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 3: cannot open title: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 3: Request: not found
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 4: cannot open META: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 5: cannot open link: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 6: cannot open link: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 7:
> : not found
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 8: cannot open body: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 9: cannot open div: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 10: cannot open table: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 11: cannot open tr: No such file
> /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 12: Syntax error: redirection
> unexpected
> ERROR: Failed to install JDK. Exit code=2
> Finished: FAILURE
> Looking at /var/lib/jenkins/tools/Java_SE_7/jdk.sh, I see it's HTML generated
> from an Oracle site.
--
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-13417) git-plugin: rev-parse dereferencing tags breaks on Windows
[
https://issues.jenkins-ci.org/browse/JENKINS-13417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161513#comment-161513
]
Dan Savilonis commented on JENKINS-13417:
-
I can confirm I see this problem with git plugin 1.1.6 as well. I had to revert
to 1.1.5 to unbreak our installation.
> git-plugin: rev-parse dereferencing tags breaks on Windows
> --
>
> Key: JENKINS-13417
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13417
> Project: Jenkins
> Issue Type: Bug
> Components: git
> Environment: Windows 2008 R2 slave launched with cygwin ssh, cygwin
> git
>Reporter: Jay Berkenbilt
>Assignee: Nicolas De Loof
>
> The change to GitAPI.java in commit 13f6038acc4fa5b5a62413155da6fc8cfcad3fe0
> seems to break the git plugin for Windows, at least in some circumstances.
> The syntax rev^{commit} gets mangled by cmd because ^ is a quote character.
> This means that cmd passes rev{commit} to git, which as a cygwin executable
> being run from Windows, further tries to do wildcard expansion and maps this
> to revcommit. Putting "" around rev^{commit} empirically seems to work,
> though I haven't tried it in the git plugin itself.
> This C fragment:
> {code}
> #include
> int main(int argc, char* argv[])
> {
> int i;
> for (i = 0; i < argc; ++i)
> {
> printf("%s\n", argv[i]);
> }
> return 0;
> }
> {code}
> when compiled with mingw to a native Windows application (a.exe) and invoked
> from cmd as a.exe a^{b} prints a{b}. When the same fragment is compiled with
> cygwin gcc to cygwin executable a.exe and is invoked the same way from cmd,
> it prints ab. Both print a^{b} when invoked from cmd as a.exe "a^{b}".
> I'm not sure what the fix is here other than perhaps detecting that this is
> windows and putting quotes around the argument in Windows.
> On another note, I left the Affects Version/s field blank. My Jenkins
> installation claims that it is using version 1.1.6. Looking at the git repo
> for the plugin, it appears that 1.1.6 should not have the ^{commit} fix, yet
> running strings on
> plugins/git/WEB-INF/classes/hudson/plugins/git/GitAPI.class clearly shows
> that my git plugin has that change in it.
--
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-13405) JDK Automatic install fails on Debian
[ https://issues.jenkins-ci.org/browse/JENKINS-13405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161514#comment-161514 ] Kean Lau edited comment on JENKINS-13405 at 4/12/12 2:27 AM: - The priority needs to be blocker. Everyone who has any SSH based slaves cannot build since the problem causes the slave to be offline. was (Author: kean_lau): The priority needs to be blocker. Everyone who has any SSH based slaves cannot build since the problem sets the slave status to offline. > JDK Automatic install fails on Debian > - > > Key: JENKINS-13405 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13405 > Project: Jenkins > Issue Type: Bug > Components: javanet, ssh-slaves >Reporter: Jesse Bowes >Priority: Blocker > Attachments: jdk.sh.html > > > I have my Jenkins system set up to automatically install Java 7. When I add > a new project and try to build, I see errors saying: > Started by an SCM change > Building in workspace /var/lib/jenkins/jobs/FeedWatcher/workspace > Installing /var/lib/jenkins/tools/Java_SE_7/jdk.sh > [Java_SE_7] $ /var/lib/jenkins/tools/Java_SE_7/jdk.sh -noregister > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 1: cannot open html: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 2: cannot open head: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 3: cannot open title: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 3: Request: not found > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 4: cannot open META: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 5: cannot open link: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 6: cannot open link: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 7: > : not found > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 8: cannot open body: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 9: cannot open div: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 10: cannot open table: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 11: cannot open tr: No such file > /var/lib/jenkins/tools/Java_SE_7/jdk.sh: 12: Syntax error: redirection > unexpected > ERROR: Failed to install JDK. Exit code=2 > Finished: FAILURE > Looking at /var/lib/jenkins/tools/Java_SE_7/jdk.sh, I see it's HTML generated > from an Oracle site. -- 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
