[JIRA] (JENKINS-13319) Change icon for repeatableDeleteButton and show tooltip on it
[ https://issues.jenkins-ci.org/browse/JENKINS-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-13319 started by OHTAKE Tomohiro. > Change icon for repeatableDeleteButton and show tooltip on it > - > > Key: JENKINS-13319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13319 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro >Priority: Minor > > Currently icon for repeatableDeleteButton is "edit-delete.png". [1] > Change it to "user-trash.png". [3] > Discussions: (written in Japanese) > [1] https://twitter.com/#!/ohtaket/status/186631033582657538 > [2] https://twitter.com/#!/kohsukekawa/status/186913466391597056 > [3] https://twitter.com/#!/ohtaket/status/186977316025540609 > [4] https://twitter.com/#!/kohsukekawa/status/186978692772278272 > [5] https://twitter.com/#!/ohtaket/status/186983488975679488 > [6] https://twitter.com/#!/kohsukekawa/status/186983938441494529 -- 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-13318) "Display Name" can be misread as an optional block of "Use custom workspace"
[
https://issues.jenkins-ci.org/browse/JENKINS-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
> "Display Name" can be misread as an optional block of "Use custom workspace"
>
>
> Key: JENKINS-13318
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13318
> Project: Jenkins
> Issue Type: Improvement
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Priority: Trivial
>
> {code:title="Use custom workspace" is not checked}
> [unchecked] Use custom workspace
> Display Name [ ]
> {code}
> {code:title="Use custom workspace" is checked}
> [checked] Use custom workspace
> Directory [ ]
> Display Name [ ]
> {code}
> "Display Name" can be misread as an optional block of "Use custom workspace".
> Better to change the location.
--
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-13321) Fitnesse tests with no result doesn't fail the build
Simon Westcott created JENKINS-13321:
Summary: Fitnesse tests with no result doesn't fail the build
Key: JENKINS-13321
URL: https://issues.jenkins-ci.org/browse/JENKINS-13321
Project: Jenkins
Issue Type: Bug
Components: fitnesse
Reporter: Simon Westcott
Fitnesse plugin 1.6
When Fitnesse returns the following result (no tests executed), Jenkins should
probably mark the build as failed/unstable.
{noformat}
v20110104
StagingRegression
0
0
0
0
0
{noformat}
--
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-13266) In fluid layout, side-panel may overflow into main-panel
[ https://issues.jenkins-ci.org/browse/JENKINS-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161125#comment-161125 ] SCM/JIRA link daemon commented on JENKINS-13266: Code changed in jenkins User: Tom Bevers Path: war/src/main/webapp/less/jenkins.less http://jenkins-ci.org/commit/jenkins/c6586ab682ccb1ec721be5174651f15e4e361a0c Log: [Fixed JENKINS-13266] Fixed fluid layout > In fluid layout, side-panel may overflow into main-panel > > > Key: JENKINS-13266 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13266 > Project: Jenkins > Issue Type: Bug > Components: ui-changes > Environment: ui-changes branch >Reporter: OHTAKE Tomohiro > Attachments: Untitled.png > > > If side-panel contains a wide table, it may overflow into main-panel. -- 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-13266) In fluid layout, side-panel may overflow into main-panel
[ https://issues.jenkins-ci.org/browse/JENKINS-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] > In fluid layout, side-panel may overflow into main-panel > > > Key: JENKINS-13266 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13266 > Project: Jenkins > Issue Type: Bug > Components: ui-changes > Environment: ui-changes branch >Reporter: OHTAKE Tomohiro > Attachments: Untitled.png > > > If side-panel contains a wide table, it may overflow into main-panel. -- 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-13266) In fluid layout, side-panel may overflow into main-panel
[ https://issues.jenkins-ci.org/browse/JENKINS-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161126#comment-161126 ] dogfood commented on JENKINS-13266: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_ui-changes_branch #18|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/18/] [Fixed JENKINS-13266] Fixed fluid layout (Revision c6586ab682ccb1ec721be5174651f15e4e361a0c) Result = SUCCESS t.bevers : [c6586ab682ccb1ec721be5174651f15e4e361a0c|https://github.com/jenkinsci/jenkins/commit/c6586ab682ccb1ec721be5174651f15e4e361a0c] Files : * war/src/main/webapp/less/jenkins.less > In fluid layout, side-panel may overflow into main-panel > > > Key: JENKINS-13266 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13266 > Project: Jenkins > Issue Type: Bug > Components: ui-changes > Environment: ui-changes branch >Reporter: OHTAKE Tomohiro > Attachments: Untitled.png > > > If side-panel contains a wide table, it may overflow into main-panel. -- 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-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[
https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161127#comment-161127
]
OHTAKE Tomohiro commented on JENKINS-13284:
---
I have moved all less/bootstrap/\*.less files to less/\*.less,
but the issue still exists.
{code:title=IE 9}
Unable to get value of the property 'charAt': object is null or undefined
in http://localhost:8080/less/jenkins.less
{code}
{code:title=Chrome 18}
Cannot call method 'charAt' of undefined
in http://localhost:8080/less/jenkins.less
{code}
> ui-changes: Cannot load stylesheets during hudson-dev:run
> -
>
> Key: JENKINS-13284
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13284
> Project: Jenkins
> Issue Type: Bug
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Priority: Critical
>
> See
> https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432
> Approaches:
> - Modify
> [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin]
> - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running
> in developement mode
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13322) Configure tab freezes when using both the HTML5 notifier plugin and the Android Emulator Plugin
Johannes Pelto-Piri created JENKINS-13322: - Summary: Configure tab freezes when using both the HTML5 notifier plugin and the Android Emulator Plugin Key: JENKINS-13322 URL: https://issues.jenkins-ci.org/browse/JENKINS-13322 Project: Jenkins Issue Type: Bug Components: android-emulator, html5-notifier Environment: Mac OS X Reporter: Johannes Pelto-Piri Assignee: Christopher Orr When trying to configure a job with both the HTML5 notifier plugin and the Android Emulator plugin the job configuration wont load. I tried again in a fresh installation and installed the plugins separately and the issue remained. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[ https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161128#comment-161128 ] OHTAKE Tomohiro commented on JENKINS-13284: --- The internal error was "No matching definition was found for `.spanX()`". Commenting out 3 lines below will make less.js work. * grid.less:2 #grid > .core(@gridColumnWidth, @gridGutterWidth); * grid.less:5 #grid > .fluid(@fluidGridColumnWidth, @fluidGridGutterWidth); * forms.less:256 #grid > .input (@gridColumnWidth, @gridGutterWidth); > ui-changes: Cannot load stylesheets during hudson-dev:run > - > > Key: JENKINS-13284 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13284 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: OHTAKE Tomohiro >Priority: Critical > > See > https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432 > Approaches: > - Modify > [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin] > - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running > in developement mode -- 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-9247) NPE when saving tool installation config
[
https://issues.jenkins-ci.org/browse/JENKINS-9247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
evernat updated JENKINS-9247:
-
Assignee: Josh Kennedy
Component/s: clang-scanbuild
(was: plugin)
> NPE when saving tool installation config
>
>
> Key: JENKINS-9247
> URL: https://issues.jenkins-ci.org/browse/JENKINS-9247
> Project: Jenkins
> Issue Type: Bug
> Components: clang-scanbuild
> Environment: Jenkins 1.405, clang-scanbuild 1.1
>Reporter: Marcus Better
>Assignee: Josh Kennedy
>
> The clang-scanbuild plugin throws an NPE when saving the Hudson configuration
> page, after adding a clang tool installation. It was set to install
> automatically by downloading clang from
> [http://clang-analyzer.llvm.org/checker/checker-255.tar.bz2]
> {code}
> java.lang.NullPointerException
>
> jenkins.plugins.clangscanbuild.ClangScanBuildToolInstallation.removeTrailingSlashes(ClangScanBuildToolInstallation.java:39)
>
> jenkins.plugins.clangscanbuild.ClangScanBuildToolInstallation.(ClangScanBuildToolInstallation.java:33)
> sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
>
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> java.lang.reflect.Constructor.newInstance(Constructor.java:532)
> org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:449)
> org.kohsuke.stapler.RequestImpl.bindJSON(RequestImpl.java:395)
> org.kohsuke.stapler.RequestImpl.bindJSONToList(RequestImpl.java:432)
> hudson.tools.ToolDescriptor.configure(ToolDescriptor.java:102)
> hudson.model.Hudson.configureDescriptor(Hudson.java:2565)
> hudson.model.Hudson.doConfigSubmit(Hudson.java:2518)
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> java.lang.reflect.Method.invoke(Method.java:616)
> {code}
--
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-13063) Test report does not include all matching result xml files
[ https://issues.jenkins-ci.org/browse/JENKINS-13063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161129#comment-161129 ] ganesh vattamwar commented on JENKINS-13063: I do have the same issue. In my *.xml file there are 2 testsuite and the trend is showing only the first testsuite and skipping the second one in the display. Is there any possibility to get this fixed within next weeks? > Test report does not include all matching result xml files > -- > > Key: JENKINS-13063 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13063 > Project: Jenkins > Issue Type: Bug > Components: junit >Reporter: Philip Corlatan > > We are using the option "Publish test results" for all our build jobs > and are specifiying the following pattern for "Test results in XML format:" > "\_test/results/TEST\_*.xml" > When our ant build script is completed, there are the following files > available matching this pattern: > _test/results/TEST_hmm.xml > _test/results/TEST_mssql2008.xml > _test/results/TEST_oracle11g.xml > _test/results/TESTS-TestSuites > Since we updated to Jenkins 1.454, the file > "_test/results/TEST_oracle11g.xml" will not be included anymore in the > resulting test report (JOB/builds/TIMESTAMP/junitResult.xml) for all our > builds. > Only "TEST_hmm.xml" and "TEST_mssql2008.xml" are considered. > Symptoms: > - The build succeeds even if some of our Oracle tests fail > - The test result trend graph shows the wrong number of test > The listed files are all available in the specified directory and the HTML > test report, which we create additionally, includes all test results. > An update to Jenkins 1.455 did not help. > Please let me know if you need any further information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-10771) hudson.util.IOException2: remote file operation failed
[ https://issues.jenkins-ci.org/browse/JENKINS-10771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161130#comment-161130 ] Deepti K commented on JENKINS-10771: I have jenkins 1.456 installed on my machine hosting Ubuntu 11.04(Natty) with openjdk-6-jre. The jobs are executed on the ec2 slaves which are configured for provisioning Ubuntu 12.04 (precise, beta) images and openjdk-6-jre. My builds failed constantly with the following error when more than one build executed on the slave simultaneously: Caused by: java.lang.LinkageError: loader (instance of hudson/remoting/RemoteClassLoader): attempted duplicate class definition for name: "hudson/model/AbstractProject" at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at java.lang.ClassLoader.defineClass(ClassLoader.java:480) at hudson.remoting.RemoteClassLoader.loadClassFile(RemoteClassLoader.java:152) at hudson.remoting.RemoteClassLoader.findClass(RemoteClassLoader.java:131) at java.lang.ClassLoader.loadClass(ClassLoader.java:321) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2444) at java.lang.Class.getDeclaredMethod(Class.java:1952) at java.io.ObjectStreamClass.getPrivateMethod(ObjectStreamClass.java:1396) at java.io.ObjectStreamClass.access$1700(ObjectStreamClass.java:69) at java.io.ObjectStreamClass$2.run(ObjectStreamClass.java:455) at java.security.AccessController.doPrivileged(Native Method) at java.io.ObjectStreamClass.(ObjectStreamClass.java:430) at java.io.ObjectStreamClass.lookup(ObjectStreamClass.java:327) at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:564) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1600) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1513) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1749) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1963) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1887) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1770) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1346) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:287) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) 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) Relaunching the slave and executing the builds did not help. As a workaround I restricted only 1 build executor on the slave and it seem to build the jobs successfully. But this inturn leads to poor utilisation of the slaves. I would request to fix the bug at the earliest. > hudson.util.IOException2: remote file operation failed > -- > > Key: JENKINS-10771 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10771 > Project: Jenkins > Issue Type: Bug > Components: master-slave >Affects Versions: current > Environment: node: Windows Server 2008 R2, amd64 - Intel64 Family 6 > Model 15 Stepping 1, GenuineIntel, jvm 1.6.0_25-b06 > master: AIX >Reporter: Thorsten Löber > > After upgrading jenkins from 1.415 to 1.426 we cannot build anymore any > project on our windows node. We get the exception: > Building remotely on WSJENKINSDEV01 > hudson.util.IOException2: remote file operation failed: d:\Program > Files\jenkins_slave\workspace\TASC Workbench at > hudson.remoting.Channel@4f854f85:WSJENKINSDEV01 > at hudson.FilePath.act(FilePath.ja
[JIRA] (JENKINS-13059) Backup userContent folder too
[ https://issues.jenkins-ci.org/browse/JENKINS-13059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161131#comment-161131 ] Thomas Fields commented on JENKINS-13059: - I see that progress has started on this issue. Is there an ETA for when the work will be complete? Thanks, Tom. > Backup userContent folder too > - > > Key: JENKINS-13059 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13059 > Project: Jenkins > Issue Type: Improvement > Components: thinBackup > Environment: Jenkins 1.454 >Reporter: Thomas Fields >Assignee: Thomas Fürer > > Hi there, > First off, thinBackup is a super plugin. Just what I need. > I'd like to request that you add support for backing up the "userContent" > folder as well. If you don't want to hard code this path then could you at > least give me a new option such as "Additional files included in backup > (regular expression)" where I can specify the folder myself? > Regards, > Tom. -- 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-13241) Artifact archiving from remote slave fails
[ https://issues.jenkins-ci.org/browse/JENKINS-13241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161132#comment-161132 ] Poulet Fabrice commented on JENKINS-13241: -- Same issue, but only on AIX, it work on SunOS & Windows without any errors downgrade to 1.455 did not solve the issue > Artifact archiving from remote slave fails > -- > > Key: JENKINS-13241 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13241 > Project: Jenkins > Issue Type: Bug > Components: core >Reporter: Vyacheslav Karpukhin > > Since 1.456 jenkins stopped archiving artifacts from remote slave. This > affects both 1.456 and 1.457, works correctly with 1.455. > ERROR: Failed to archive artifacts: build/Release/*.app/**/* > hudson.util.IOException2: hudson.util.IOException2: Failed to extract > /var/jenkins/workspace/NGB_Queues/build/Release/*.app/**/* > at hudson.FilePath.readFromTar(FilePath.java:1817) > at hudson.FilePath.copyRecursiveTo(FilePath.java:1729) > at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656) > at hudson.model.Build$RunnerImpl.post2(Build.java:162) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) > at hudson.model.Run.run(Run.java:1435) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:238) > Caused by: java.io.IOException: Failed to chmod > /mnt/storage/.jenkins/jobs/NGB_Queues/builds/2012-03-27_03-11-27/archive/build/Release/NGB > > Queues.app/Contents/Frameworks/BWToolkitFramework.framework/BWToolkitFramework > : No such file or directory > at hudson.FilePath._chmod(FilePath.java:1248) > at hudson.FilePath.readFromTar(FilePath.java:1813) > ... 12 more > at hudson.FilePath.copyRecursiveTo(FilePath.java:1736) > at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:703) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:678) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:656) > at hudson.model.Build$RunnerImpl.post2(Build.java:162) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:625) > at hudson.model.Run.run(Run.java:1435) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:238) > Caused by: java.util.concurrent.ExecutionException: java.io.IOException: Pipe > is already closed > at hudson.remoting.Channel$2.adapt(Channel.java:714) > at hudson.remoting.Channel$2.adapt(Channel.java:709) > at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) > at hudson.FilePath.copyRecursiveTo(FilePath.java:1732) > ... 11 more > Caused by: java.io.IOException: Pipe is already closed > at hudson.remoting.PipeWindow.checkDeath(PipeWindow.java:83) > at hudson.remoting.PipeWindow$Real.get(PipeWindow.java:171) > at hudson.remoting.ProxyOutputStream._write(ProxyOutputStream.java:118) > at hudson.remoting.ProxyOutputStream.write(ProxyOutputStream.java:103) > at > java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.write(BufferedOutputStream.java:109) > at > java.util.zip.DeflaterOutputStream.deflate(DeflaterOutputStream.java:161) > at > java.util.zip.DeflaterOutputStream.write(DeflaterOutputStream.java:118) > at java.util.zip.GZIPOutputStream.write(GZIPOutputStream.java:72) > at java.io.BufferedOutputStream.write(BufferedOutputStream.java:105) > at org.apache.tools.tar.TarBuffer.writeBlock(TarBuffer.java:410) > at org.apache.tools.tar.TarBuffer.writeRecord(TarBuffer.java:351) > at > hudson.org.apache.tools.tar.TarOutputStream.writeEOFRecord(TarOutputStream.java:356) > at > hudson.org.apache.tools.tar.TarOutputStream.finish(TarOutputStream.java:137) > at > hudson.org.apache.tools.tar.TarOutputStream.close(TarOutputStream.java:149) > at hudson.util.io.TarArchiver.
Process leaked file descriptors, even though I'm not spawing any proces
1) I'm running a job on a Windows 7 Virtualbox slave, using the VirtualBox Plugin 0.5-SNAPSHOT 2) I execute a windows batch command: java -DTestSuite="My Regression Test" -cp test.jar org.testng.TestNG -d "testng-results" MyTest.xml 3) After about 9 minutes, Jenkins stops the execution of the TestNG test with: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information So, as I understand this can happen if you spawn a process, but thats not what I'm doing here. I'm running a TestNG test that continuously talks on STDOUT to Jenkins... What's happening here?
[JIRA] (JENKINS-13323) Renaming a node does not update associated projects
David Riley created JENKINS-13323: - Summary: Renaming a node does not update associated projects Key: JENKINS-13323 URL: https://issues.jenkins-ci.org/browse/JENKINS-13323 Project: Jenkins Issue Type: Bug Components: core Reporter: David Riley Priority: Minor v1.448 This is a painful bug, if I ever need to move a bunch of projects from one node to another, instead of just reconfiguring the existing node to run in a different place with a different name, I have to manually change every project which uses the node to point at the new name. I like to include the server name in the node name, which I'm sure is not an uncommon practise! Thank you -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13324) Perforce mail address resolver should fall back to other resolvers if mail address is invalid
Mikko Tapaninen created JENKINS-13324: - Summary: Perforce mail address resolver should fall back to other resolvers if mail address is invalid Key: JENKINS-13324 URL: https://issues.jenkins-ci.org/browse/JENKINS-13324 Project: Jenkins Issue Type: Bug Components: perforce Environment: Perforce 2011.1 perforce-plugin 1.3.12 Reporter: Mikko Tapaninen Perforce mail address resolver is always returning a string, no matter what the actual email address is. I don't know what is the order how Jenkins loops through the various MailAddressResolver instances but if some instance returns an actual string (i.e. non-null), it will stick with that. I don't think it's feasible to really check whether the email address provided by Perforce is valid, but PerforceMailResolver could check for some value (e.g. "n/a") and return null if it matches. At least with Perforce 2011.1 you can't have an empty value for an email address. There could be an UI element for configuring which email address would be thought as invalid, but I'm fine with hardcoding "n/a" there and documenting it somewhere. Would this be ok? -- 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-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[ https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13284. Resolution: Fixed > ui-changes: Cannot load stylesheets during hudson-dev:run > - > > Key: JENKINS-13284 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13284 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: OHTAKE Tomohiro >Priority: Critical > > See > https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432 > Approaches: > - Modify > [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin] > - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running > in developement mode -- 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-13319) Change icon for repeatableDeleteButton and show tooltip on it
[ https://issues.jenkins-ci.org/browse/JENKINS-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161134#comment-161134 ] SCM/JIRA link daemon commented on JENKINS-13319: Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/main/resources/lib/form/repeatableDeleteButton.jelly war/src/main/webapp/images/16x16/user-trash.png http://jenkins-ci.org/commit/jenkins/1511f7eb33b984d8226b5f3823cc40adfc4ed79e Log: [FIXED JENKINS-13319] repeatableDeleteButton's icon is now user-trash.png > Change icon for repeatableDeleteButton and show tooltip on it > - > > Key: JENKINS-13319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13319 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro >Priority: Minor > > Currently icon for repeatableDeleteButton is "edit-delete.png". [1] > Change it to "user-trash.png". [3] > Discussions: (written in Japanese) > [1] https://twitter.com/#!/ohtaket/status/186631033582657538 > [2] https://twitter.com/#!/kohsukekawa/status/186913466391597056 > [3] https://twitter.com/#!/ohtaket/status/186977316025540609 > [4] https://twitter.com/#!/kohsukekawa/status/186978692772278272 > [5] https://twitter.com/#!/ohtaket/status/186983488975679488 > [6] https://twitter.com/#!/kohsukekawa/status/186983938441494529 -- 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-13318) "Display Name" can be misread as an optional block of "Use custom workspace"
[
https://issues.jenkins-ci.org/browse/JENKINS-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161135#comment-161135
]
SCM/JIRA link daemon commented on JENKINS-13318:
Code changed in jenkins
User: OHTAKE Tomohiro
Path:
core/src/main/resources/hudson/matrix/MatrixProject/configure-entries.jelly
core/src/main/resources/hudson/model/AbstractItem/configure-common.jelly
http://jenkins-ci.org/commit/jenkins/a91de10c687cc671c3ba651a92a65f6f1572c683
Log:
[FIXED JENKINS-13318] Move "Display Name" entry to the top
Compare: https://github.com/jenkinsci/jenkins/compare/c6586ab...a91de10
> "Display Name" can be misread as an optional block of "Use custom workspace"
>
>
> Key: JENKINS-13318
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13318
> Project: Jenkins
> Issue Type: Improvement
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Priority: Trivial
>
> {code:title="Use custom workspace" is not checked}
> [unchecked] Use custom workspace
> Display Name [ ]
> {code}
> {code:title="Use custom workspace" is checked}
> [checked] Use custom workspace
> Directory [ ]
> Display Name [ ]
> {code}
> "Display Name" can be misread as an optional block of "Use custom workspace".
> Better to change the location.
--
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-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[ https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161133#comment-161133 ] SCM/JIRA link daemon commented on JENKINS-13284: Code changed in jenkins User: OHTAKE Tomohiro Path: core/src/main/resources/lib/layout/layout.jelly http://jenkins-ci.org/commit/jenkins/7e721850dbf1f1f3ff41bdf42b285ad2f082bf84 Log: [FIXED JENKINS-13284] Load jenkins.less and less.js first > ui-changes: Cannot load stylesheets during hudson-dev:run > - > > Key: JENKINS-13284 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13284 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: OHTAKE Tomohiro >Priority: Critical > > See > https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432 > Approaches: > - Modify > [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin] > - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running > in developement mode -- 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-13319) Change icon for repeatableDeleteButton and show tooltip on it
[ https://issues.jenkins-ci.org/browse/JENKINS-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13319. Resolution: Fixed > Change icon for repeatableDeleteButton and show tooltip on it > - > > Key: JENKINS-13319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13319 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro >Priority: Minor > > Currently icon for repeatableDeleteButton is "edit-delete.png". [1] > Change it to "user-trash.png". [3] > Discussions: (written in Japanese) > [1] https://twitter.com/#!/ohtaket/status/186631033582657538 > [2] https://twitter.com/#!/kohsukekawa/status/186913466391597056 > [3] https://twitter.com/#!/ohtaket/status/186977316025540609 > [4] https://twitter.com/#!/kohsukekawa/status/186978692772278272 > [5] https://twitter.com/#!/ohtaket/status/186983488975679488 > [6] https://twitter.com/#!/kohsukekawa/status/186983938441494529 -- 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-13318) "Display Name" can be misread as an optional block of "Use custom workspace"
[
https://issues.jenkins-ci.org/browse/JENKINS-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
SCM/JIRA link daemon resolved JENKINS-13318.
Resolution: Fixed
> "Display Name" can be misread as an optional block of "Use custom workspace"
>
>
> Key: JENKINS-13318
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13318
> Project: Jenkins
> Issue Type: Improvement
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Priority: Trivial
>
> {code:title="Use custom workspace" is not checked}
> [unchecked] Use custom workspace
> Display Name [ ]
> {code}
> {code:title="Use custom workspace" is checked}
> [checked] Use custom workspace
> Directory [ ]
> Display Name [ ]
> {code}
> "Display Name" can be misread as an optional block of "Use custom workspace".
> Better to change the location.
--
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-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[ https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161136#comment-161136 ] OHTAKE Tomohiro commented on JENKINS-13284: --- Some says that LESS 1.3.0 fixes "#grid > .core" issue, and others says that 1.3.0 does not. https://github.com/twitter/bootstrap/issues/2528 In my environment, changing order of loading JS resolved the issue. Could you try if less.js works correctly? > ui-changes: Cannot load stylesheets during hudson-dev:run > - > > Key: JENKINS-13284 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13284 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: OHTAKE Tomohiro >Priority: Critical > > See > https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432 > Approaches: > - Modify > [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin] > - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running > in developement mode -- 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-13318) "Display Name" can be misread as an optional block of "Use custom workspace"
[
https://issues.jenkins-ci.org/browse/JENKINS-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161137#comment-161137
]
dogfood commented on JENKINS-13318:
---
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[jenkins_ui-changes_branch
#19|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/19/]
[FIXED JENKINS-13318] Move "Display Name" entry to the top (Revision
a91de10c687cc671c3ba651a92a65f6f1572c683)
Result = SUCCESS
ohtake.tomohiro :
[a91de10c687cc671c3ba651a92a65f6f1572c683|https://github.com/jenkinsci/jenkins/commit/a91de10c687cc671c3ba651a92a65f6f1572c683]
Files :
* core/src/main/resources/hudson/model/AbstractItem/configure-common.jelly
* core/src/main/resources/hudson/matrix/MatrixProject/configure-entries.jelly
> "Display Name" can be misread as an optional block of "Use custom workspace"
>
>
> Key: JENKINS-13318
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13318
> Project: Jenkins
> Issue Type: Improvement
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Priority: Trivial
>
> {code:title="Use custom workspace" is not checked}
> [unchecked] Use custom workspace
> Display Name [ ]
> {code}
> {code:title="Use custom workspace" is checked}
> [checked] Use custom workspace
> Directory [ ]
> Display Name [ ]
> {code}
> "Display Name" can be misread as an optional block of "Use custom workspace".
> Better to change the location.
--
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-13319) Change icon for repeatableDeleteButton and show tooltip on it
[ https://issues.jenkins-ci.org/browse/JENKINS-13319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161138#comment-161138 ] dogfood commented on JENKINS-13319: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_ui-changes_branch #19|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/19/] [FIXED JENKINS-13319] repeatableDeleteButton's icon is now user-trash.png (Revision 1511f7eb33b984d8226b5f3823cc40adfc4ed79e) Result = SUCCESS ohtake.tomohiro : [1511f7eb33b984d8226b5f3823cc40adfc4ed79e|https://github.com/jenkinsci/jenkins/commit/1511f7eb33b984d8226b5f3823cc40adfc4ed79e] Files : * core/src/main/resources/lib/form/repeatableDeleteButton.jelly * war/src/main/webapp/images/16x16/user-trash.png > Change icon for repeatableDeleteButton and show tooltip on it > - > > Key: JENKINS-13319 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13319 > Project: Jenkins > Issue Type: Improvement > Components: ui-changes >Reporter: OHTAKE Tomohiro >Assignee: OHTAKE Tomohiro >Priority: Minor > > Currently icon for repeatableDeleteButton is "edit-delete.png". [1] > Change it to "user-trash.png". [3] > Discussions: (written in Japanese) > [1] https://twitter.com/#!/ohtaket/status/186631033582657538 > [2] https://twitter.com/#!/kohsukekawa/status/186913466391597056 > [3] https://twitter.com/#!/ohtaket/status/186977316025540609 > [4] https://twitter.com/#!/kohsukekawa/status/186978692772278272 > [5] https://twitter.com/#!/ohtaket/status/186983488975679488 > [6] https://twitter.com/#!/kohsukekawa/status/186983938441494529 -- 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-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[ https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161139#comment-161139 ] dogfood commented on JENKINS-13284: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_ui-changes_branch #19|http://ci.jenkins-ci.org/job/jenkins_ui-changes_branch/19/] [FIXED JENKINS-13284] Load jenkins.less and less.js first (Revision 7e721850dbf1f1f3ff41bdf42b285ad2f082bf84) Result = SUCCESS ohtake.tomohiro : [7e721850dbf1f1f3ff41bdf42b285ad2f082bf84|https://github.com/jenkinsci/jenkins/commit/7e721850dbf1f1f3ff41bdf42b285ad2f082bf84] Files : * core/src/main/resources/lib/layout/layout.jelly > ui-changes: Cannot load stylesheets during hudson-dev:run > - > > Key: JENKINS-13284 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13284 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: OHTAKE Tomohiro >Priority: Critical > > See > https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432 > Approaches: > - Modify > [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin] > - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running > in developement mode -- 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-13266) In fluid layout, side-panel may overflow into main-panel
[ https://issues.jenkins-ci.org/browse/JENKINS-13266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161140#comment-161140 ] OHTAKE Tomohiro commented on JENKINS-13266: --- If width of Build History table is 300px, required min-width for ".container-fluid" would be 1200px and more. Setting min-width for ".navbar" prevents navbar from wrapping. Since width of Build History table varies, I don't think that setting min-width will resolve the issue. > In fluid layout, side-panel may overflow into main-panel > > > Key: JENKINS-13266 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13266 > Project: Jenkins > Issue Type: Bug > Components: ui-changes > Environment: ui-changes branch >Reporter: OHTAKE Tomohiro > Attachments: Untitled.png > > > If side-panel contains a wide table, it may overflow into main-panel. -- 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-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161141#comment-161141 ] lestin commented on JENKINS-13270: -- HiRob， It's not because the next time it's still using the ticket to authorize the user. Also our ticket system is configured to last for a relatively long period. I did have issues originally when using the account/passwd method and that's why i changed to use tickets. But i need to confess that I didn't try that for a long long while, i.e. since 2010. Thanks. Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudso
[JIRA] (JENKINS-13318) "Display Name" can be misread as an optional block of "Use custom workspace"
[
https://issues.jenkins-ci.org/browse/JENKINS-13318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161142#comment-161142
]
domi commented on JENKINS-13318:
perfect! I was thinking about this too :)
> "Display Name" can be misread as an optional block of "Use custom workspace"
>
>
> Key: JENKINS-13318
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13318
> Project: Jenkins
> Issue Type: Improvement
> Components: ui-changes
>Reporter: OHTAKE Tomohiro
>Priority: Trivial
>
> {code:title="Use custom workspace" is not checked}
> [unchecked] Use custom workspace
> Display Name [ ]
> {code}
> {code:title="Use custom workspace" is checked}
> [checked] Use custom workspace
> Directory [ ]
> Display Name [ ]
> {code}
> "Display Name" can be misread as an optional block of "Use custom workspace".
> Better to change the location.
--
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
Marc Sanfacon created JENKINS-13325: --- Summary: 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 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-13238) Loading All Build History Fails
[ https://issues.jenkins-ci.org/browse/JENKINS-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jakub Czaplicki reopened JENKINS-13238: --- The issue is still present 1.458 > Loading All Build History Fails > --- > > Key: JENKINS-13238 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13238 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: linux, jenkins 1.456 >Reporter: Spencer Oliver >Assignee: sogabe > > seems after the update from 1.455 to 1.456 causes an issue where pressing > 'More' to expand the job Build History now fails with a 404. > Calling the build history directly also causes the 404, eg. > http://openocd.zylin.com/jenkins/job/openocd/buildHistory/all/ > For info rolling back to 1.455 cures the problem. > tested 1.457 and issue still present. > jenkins own server also shows the issue: > http://ci.jenkins-ci.org/view/All/job/jenkins_main_trunk/buildHistory/all/ -- 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-13284) ui-changes: Cannot load stylesheets during hudson-dev:run
[ https://issues.jenkins-ci.org/browse/JENKINS-13284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161144#comment-161144 ] domi commented on JENKINS-13284: yep, seems to work for me now - thanks! > ui-changes: Cannot load stylesheets during hudson-dev:run > - > > Key: JENKINS-13284 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13284 > Project: Jenkins > Issue Type: Bug > Components: ui-changes >Reporter: OHTAKE Tomohiro >Priority: Critical > > See > https://github.com/jenkinsci/jenkins/commit/c4ab05d80fd2e2fb633143421517522c42538f7b#L1R432 > Approaches: > - Modify > [maven-hudson-dev-plugin|https://github.com/jenkinsci/maven-hudson-dev-plugin] > - Use [less.js|http://lesscss.org/#-client-side-usage] if Jenkins is running > in developement mode -- 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-13326) Grinder plugin: Mean Response Length in graph is incorrect
Kees Hink created JENKINS-13326: --- Summary: Grinder plugin: Mean Response Length in graph is incorrect Key: JENKINS-13326 URL: https://issues.jenkins-ci.org/browse/JENKINS-13326 Project: Jenkins Issue Type: Bug Components: plugin Environment: Ubuntu Server 9.04 Reporter: Kees Hink Priority: Trivial Attachments: jenkins-grinder-screenshot.png In the graph that is generated from a Grinder plugin report, Mean Response Lengths appear to be ordered incorrectly: The MRL value for a given test number does not always match the MRL value from the table. See attached screenshot. Here you can see that for "Test 2", the graph shows an MRL of 0, but the table shows it to bo 227k. The table's value is correct here. -- 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-11938) Jenkins loses builds when restarted
[
https://issues.jenkins-ci.org/browse/JENKINS-11938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161145#comment-161145
]
Asher Aber commented on JENKINS-11938:
--
That is correct!
The build.xml should not have the this type of reference:
/tmp/upload__1efd5df3_13659557023__8000_0056.tmp
It should be:
/var/lib/jenkins/jobs/My_Project/builds/12/fileParameters/uploadedFile
The question is who can correct this?
> Jenkins loses builds when restarted
> ---
>
> Key: JENKINS-11938
> URL: https://issues.jenkins-ci.org/browse/JENKINS-11938
> Project: Jenkins
> Issue Type: Bug
> Components: other, versionnumber
>Affects Versions: current
> Environment: tomcat 7.0.22
> windows server 2008 r2
>Reporter: Ben Dean
>
> Jenkins version 1.437
> If I stop the Apache Tomcat windows service, a bunch of my builds disappear
> from the history of the jobs. The missing builds are still on disk in the
> build folder, it just doesn't "find" them when making the history list.
> The jobs that lose history use the version number plugin and I had recently
> changed the version format from "4.3.${BUILDS_ALL_TIME}" to
> "4.4.${BUILDS_ALL_TIME}". The builds that disappear are all those after I
> changed this format. Also affects jobs that are downstream from those with
> version number changes.
> I could not find any Component related to the build history for a job. If
> someone knows what that should be feel free to change this. Also, sorry if
> there's not enough (or to much) information, this is the first Jenkins bug I
> have filed.
--
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-13238) Loading All Build History Fails
[ https://issues.jenkins-ci.org/browse/JENKINS-13238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-13238. --- Resolution: Fixed The fix will be available in 1.459. See http://jenkins-ci.org/changelog and click "Upcoming changes". Or, you can use an RC http://jenkins-ci.org/rc > Loading All Build History Fails > --- > > Key: JENKINS-13238 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13238 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: linux, jenkins 1.456 >Reporter: Spencer Oliver >Assignee: sogabe > > seems after the update from 1.455 to 1.456 causes an issue where pressing > 'More' to expand the job Build History now fails with a 404. > Calling the build history directly also causes the 404, eg. > http://openocd.zylin.com/jenkins/job/openocd/buildHistory/all/ > For info rolling back to 1.455 cures the problem. > tested 1.457 and issue still present. > jenkins own server also shows the issue: > http://ci.jenkins-ci.org/view/All/job/jenkins_main_trunk/buildHistory/all/ -- 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-13327) JENKINS_AGENT_HOME environment variable required
Eugene Gligalov created JENKINS-13327:
-
Summary: JENKINS_AGENT_HOME environment variable required
Key: JENKINS-13327
URL: https://issues.jenkins-ci.org/browse/JENKINS-13327
Project: Jenkins
Issue Type: New Feature
Components: core
Reporter: Eugene Gligalov
Jenkins has variable called JENKINS_HOME but it doesn't have variable something
like JENKINS_AGENT_HOME which will point to place where agent was extracted,
for now I'm using workaround to get this folder like ${WORKSPACE}/../..
Would be nice if Jenkins has some variable which point on this location.
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-13312) Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue
[
https://issues.jenkins-ci.org/browse/JENKINS-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161147#comment-161147
]
Rob Petti commented on JENKINS-13312:
-
Try process explorer, or try deleting it from the machine manually. It's also
possible that there are simple too many files in that directory for java to
handle at once.
> Help diagnosing a hudson.plugins.perforce.PerforceSCM.checkout issue
>
>
> Key: JENKINS-13312
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13312
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Environment: Jenkins 1.455
> Perforce plugin 1.38
>Reporter: Thomas Fields
>Assignee: Rob Petti
>
> Hi there,
> Occasionally some of my projects fail with the following callstack:
> {code}12:19:33 Started by an SCM change
> 12:19:33 Building remotely on BuildSlave1 in workspace
> c:\JCI\workspace\UnitTestsToolWin32-Release
> 12:20:29 hudson.util.IOException2: remote file operation failed:
> c:\JCI\workspace\UnitTestsToolWin32-Release\CONFIG at
> hudson.remoting.Channel@586ca3ef:PhyreBuild1
> 12:20:29 at hudson.FilePath.act(FilePath.java:784)
> 12:20:29 at hudson.FilePath.act(FilePath.java:770)
> 12:20:29 at hudson.FilePath.deleteRecursive(FilePath.java:854)
> 12:20:29 at
> hudson.plugins.perforce.PerforceSCM.checkout(PerforceSCM.java:597)
> 12:20:29 at
> hudson.model.AbstractProject.checkout(AbstractProject.java:1197)
> 12:20:29 at
> hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:579)
> 12:20:29 at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:468)
> 12:20:29 at hudson.model.Run.run(Run.java:1410)
> 12:20:29 at hudson.matrix.MatrixBuild.run(MatrixBuild.java:253)
> 12:20:29 at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> 12:20:29 at hudson.model.Executor.run(Executor.java:238)
> 12:20:29 at hudson.model.OneOffExecutor.run(OneOffExecutor.java:66)
> 12:20:29 Caused by: java.io.IOException: There are no more files
> 12:20:29 at java.io.WinNTFileSystem.canonicalize0(Native Method)
> 12:20:29 at java.io.Win32FileSystem.canonicalize(Unknown Source)
> 12:20:29 at java.io.File.getCanonicalPath(Unknown Source)
> 12:20:29 at java.io.File.getCanonicalFile(Unknown Source)
> 12:20:29 at hudson.Util.isSymlink(Util.java:322)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:277)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.Util.deleteContentsRecursive(Util.java:198)
> 12:20:29 at hudson.Util.deleteRecursive(Util.java:278)
> 12:20:29 at hudson.FilePath$9.invoke(FilePath.java:856)
> 12:20:29 at hudson.FilePath$9.invoke(FilePath.java:854)
> 12:20:29 at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2099)
> 12:20:29 at hudson.remoting.UserRequest.perform(UserRequest.java:118)
> 12:20:29 at hudson.remoting.UserRequest.perform(UserRequest.java:48)
> 12:20:29 at hudson.remoting.Request$2.run(Request.java:287)
> 12:20:29 at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> 12:20:29 at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
> 12:20:29 at java.util.concurrent.FutureTask.run(Unknown Source)
> 12:20:29 at
> java.util.concurrent
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161148#comment-161148 ] Rob Petti commented on JENKINS-13270: - Define a 'long period'? You haven't used passwords since 2010, so I'm guessing that this period is longer than 2 years? > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused by: jav
[JIRA] (JENKINS-12005) Broken configuration page as referenced in tutorials
[ https://issues.jenkins-ci.org/browse/JENKINS-12005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] OHTAKE Tomohiro resolved JENKINS-12005. --- Resolution: Fixed Fixed in Stapler 1.181. https://github.com/stapler/stapler/commit/9604f1e4c796bfd24175a8fff44caaec0cdfe065 Jenkins 1.456 starts to use Stapler 1.181. https://github.com/jenkinsci/jenkins/commit/63529f0f3e7ef7d2422d6b2d52e02d03e9003820 > Broken configuration page as referenced in tutorials > > > Key: JENKINS-12005 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12005 > Project: Jenkins > Issue Type: Bug > Components: core >Reporter: John Haugeland > Labels: embarrassment > > So, if you follow the main site's tutorials on how to turn on authentication, > which SHOULD BE ON BY DEFAULT, they send you to the erroneous configuration > address http://install/configure/ . > This is awesome for several reasons. > 1) The correct URL does not have a trailing slash > 2) The form will in fact respond from the wrong URL, with no apparent problem > 3) The form gets the target *completely* wrong, but the stack trace is empty > and the container 404s with no mention of what's wrong, and there's no > documentation of what's correct, so you either have to source dive or hold > your nose and spend three days being abused by the IRC channel to find out > what's wrong. > What's wrong? > Well, if you put that trailing slash on there, which by the Java > specification is supposed to be the same as without (even though that in turn > is a violation of the URI RFC,) then suddenly instead of using > %/configureSubmit like it's supposed to, it uses %/config/configSubmit (wrong > path, wrong target.) > So, if you follow the site instructions on getting user accounts working, you > spend several days with builds exposed to the internet while you look for > someone with enough trivia knowledge to get basic authentication instructions > to work. > Hooray! > Thankfully, the bug tracker refuses to take anonymous bugs, and takes 20 > minutes for a credential to start working, guaranteeing that 95% of the > people who would have already reported this went away and did something else > instead. > Because why shouldn't we make the barriers to finding out what's broken > higher? > Next, let's get stuck choosing from several hundred components, even though > this doesn't really apply to a component in any sensible way. > TL;DR: your app responds to URLs it shouldn't, and your tutorials on getting > accounts working point at the wrong URLs, and when you go to the wrong URL > for configuration it breaks in a spectacularly inobvious way. -- 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-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161150#comment-161150 ] Rob Petti commented on JENKINS-13270: - Actually, all of those "Login" lines are logins that are being performed using the password, not the ticket. It never explicitly tries to login using a ticket, and will only try to log in using the password when perforce requests authorization when running other commands. The Warning is telling the user that a new ticket has been obtained and saved in the environment, not that it's using it for login. Make sure your password is configured correctly on all of your jobs. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) >
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Petti resolved JENKINS-13270. - Resolution: Not A Defect > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused by: java.io.IOException: java.io.IOException: error=2, No such file or > directory > at java.lang.UNIXProcess.(UNIXProcess.java:148) > at java.lang.P
[JIRA] (JENKINS-13109) Huge changelogs eat all the Java memory
[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161151#comment-161151
]
SCM/JIRA link daemon commented on JENKINS-13109:
Code changed in jenkins
User: Rob Petti
Path:
src/main/java/com/tek42/perforce/parse/ChangelistBuilder.java
src/main/java/com/tek42/perforce/parse/Changes.java
src/main/java/hudson/plugins/perforce/PerforceSCM.java
src/main/resources/hudson/plugins/perforce/PerforceSCM/config.jelly
src/main/webapp/help/fileLimit.html
src/test/java/hudson/plugins/perforce/PerforceSCMTest.java
http://jenkins-ci.org/commit/perforce-plugin/a2523100d02ca360fd23b382af4e531c4dc6ac59
Log:
Merge pull request #18 from miktap/master
[JENKINS-13109] Huge changelogs eat all the Java memory
Compare: https://github.com/jenkinsci/perforce-plugin/compare/11249ca...a252310
> Huge changelogs eat all the Java memory
> ---
>
> Key: JENKINS-13109
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Environment: Windows Server 2008 HPC Edition
> 64-bit JVM 1.6.0_29
> Running Jenkins service with "-Xrs -Xmx2048m
> -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar
> "%BASE%\jenkins.war" --httpPort=8080"
>Reporter: Mikko Tapaninen
>
> With really huge changelists the p4 plugin can run out of java heap space. At
> least it looks like the reason for memory problems would be huge
> changelog.xml files. An example case:
> - a changelist with > 40 files
> - results in a changelog.xml size > 110MB
> - Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
> Maybe there should be an option to limit the amount of files that p4 plugin
> reads to from changelists?
--
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-13328) CLI parameter submission is not supported for the class com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition type.
Zeev Tavor created JENKINS-13328: Summary: CLI parameter submission is not supported for the class com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition type. Key: JENKINS-13328 URL: https://issues.jenkins-ci.org/browse/JENKINS-13328 Project: Jenkins Issue Type: Bug Components: clearcase-ucm-baseline, cli, jenkins-plugin-runtime, parameters Affects Versions: current Environment: Windows 7, Jenkins 1.457, ClearCase UCM Baseline Plugin 1.7.4 Reporter: Zeev Tavor Assignee: Daniel Petisme Priority: Blocker When trying to run job in CLI and need to provide baseline name parameter, got the following error: "CLI parameter submission is not supported for the class com.michelin.cio.hudson.plugins.clearcaseucmbaseline.ClearCaseUcmBaselineParameterDefinition type. Please file a bug report for this." Command I use: c:\Jenkins>java -jar jenkins-cli.jar -s http://builder:8080/ build "Test_Job" -p "ClearCase UCM baseline=TestBL_03_04_12" -- 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-13326) Grinder plugin: Mean Response Length in graph is incorrect
[ https://issues.jenkins-ci.org/browse/JENKINS-13326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161152#comment-161152 ] Kees Hink commented on JENKINS-13326: - Looks like the graph adds values in the order of "ID". Clicking the ID collumn header in the table to sort the rows on ID (ascending) yields the order "1, 10, 11, ...", and the MLR values are displayed in the graph in that order. Renaming my test ID's by adding 100 (so 1 -> 101, 10 -> 110, 22 -> 122 etc.) fixes the problem. > Grinder plugin: Mean Response Length in graph is incorrect > --- > > Key: JENKINS-13326 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13326 > Project: Jenkins > Issue Type: Bug > Components: plugin > Environment: Ubuntu Server 9.04 >Reporter: Kees Hink >Priority: Trivial > Labels: plugin > Attachments: jenkins-grinder-screenshot.png > > > In the graph that is generated from a Grinder plugin report, Mean Response > Lengths appear to be ordered incorrectly: The MRL value for a given test > number does not always match the MRL value from the table. > See attached screenshot. Here you can see that for "Test 2", the graph shows > an MRL of 0, but the table shows it to bo 227k. The table's value is correct > here. -- 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-13109) Huge changelogs eat all the Java memory
[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161153#comment-161153
]
Tim Drury commented on JENKINS-13109:
-
I noticed the same error today on 1.450 w/ perforce plugin 1.3.7. In my case,
it isn't caused by huge changelogs - at least that I can tell. We don't have
huge changelogs. We do have 2 slaves and all polling is done on the master.
Here is the stack trace:
Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling
SEVERE: Failed to record SCM polling
java.lang.OutOfMemoryError: Java heap space
at
hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:78)
at
hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:66)
at
hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321)
at
com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54)
at
hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208)
at
hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903)
at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
at hudson.scm.SCM.poll(SCM.java:373)
at hudson.model.AbstractProject.poll(AbstractProject.java:1323)
at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
at
hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
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)
We do keep Jenkins running without period reboots so I'm thinking there may be
a memory leak somewhere as well. If anyone can give me hints how to get more
information, I'll try to provide it.
-tim
> Huge changelogs eat all the Java memory
> ---
>
> Key: JENKINS-13109
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Environment: Windows Server 2008 HPC Edition
> 64-bit JVM 1.6.0_29
> Running Jenkins service with "-Xrs -Xmx2048m
> -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar
> "%BASE%\jenkins.war" --httpPort=8080"
>Reporter: Mikko Tapaninen
>
> With really huge changelists the p4 plugin can run out of java heap space. At
> least it looks like the reason for memory problems would be huge
> changelog.xml files. An example case:
> - a changelist with > 40 files
> - results in a changelog.xml size > 110MB
> - Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
> Maybe there should be an option to limit the amount of files that p4 plugin
> reads to from changelists?
--
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-13109) Huge changelogs eat all the Java memory
[ https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161153#comment-161153 ] Tim Drury edited comment on JENKINS-13109 at 4/3/12 2:41 PM: - I noticed the same error today on 1.450 w/ perforce plugin 1.3.7. In my case, it isn't caused by huge changelogs - at least that I can tell. We don't have huge changelogs. We do have 2 slaves and all polling is done on the master. Here is the stack trace: Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:78) at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:66) at hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1323) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) 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) We do keep Jenkins running without periodic reboots so I'm thinking there may be a memory leak somewhere as well. If anyone can give me hints how to get more information, I'll try to provide it. -tim was (Author: timdrury): I noticed the same error today on 1.450 w/ perforce plugin 1.3.7. In my case, it isn't caused by huge changelogs - at least that I can tell. We don't have huge changelogs. We do have 2 slaves and all polling is done on the master. Here is the stack trace: Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:78) at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:66) at hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1323) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) 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) We do keep Jenkins running without period reboots so I'm thinking there may be a memory leak somewhere as well. If anyone can give me hints how to get more information, I'll try to provide it. -tim > Huge changelogs eat all the Java memory > --- > >
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161154#comment-161154 ] lestin commented on JENKINS-13270: -- Hi Rob, I don't want to admit that but yes, it's configured to be valid for more than 2 years. And i just tried to put a random value into my password value, it still passed the p4 login stage and checked out the file for me. And to make sure that i did the right thing, i put a random value to the user ID field, it actually failed! And to actually verify the login failure, i asked my colleague to put in his info (which is not in the p4.ticket). We ran twice and double checked that the passwd is correct, it failed both trials. So my conclusion is, it is using the ticket system to validate user as a prority over passwd checks. And the old school passwd login doesn't work for my instance. --- Any hints to root cause it? Thanks. Lestin First tria;: [/tmp] $ /tools/perforce/2010.1/bin.linux26x86/p4 workspace -o jenkins_playground--1850485244 Last build changeset: 0 [/tmp] $ /bin/sh -xe /tmp/hudson6889247811306965176.sh + echo hello hello + p4 info User name: lestin Client name: jenkins_playground--1850485244 Client host: lc-cam-501 Client root: /tmp <..> + p4 sync -f ... //training/test2/ians-branch/test_subdir/file5#174 - refreshing /tmp/ians-branch/test_subdir/file5 Second trial: [/tmp] $ /tools/perforce/2010.1/bin.linux26x86/p4 -s client -i Caught exception communicating with perforce. User lestin2 doesn't exist. Third trial: + p4 info User name: leho Client name: jenkins_playground--1850485244 Client host: lc-cam-501 Client root: /tmp Current directory: /tmp <..> + p4 sync -f ... Perforce password (P4PASSWD) invalid or unset. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hud
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] lestin reopened JENKINS-13270: -- Hi Rob, My trials didn't appear to be as your described. Can you give more hints how i can look into this? Thanks. Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused by: java.io.IOException: java.io.IOException: error=2, No suc
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161156#comment-161156 ] Rob Petti commented on JENKINS-13270: - They look exactly as I described to me. It ONLY logs in using the password when the ticket fails to authenticate. Notice how there are no login lines in any of the logs you have posted. That's because it's validating correctly using the ticket. Make sure that your password is set correctly on all of your jobs in the event that ticket validation fails. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$Lo
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161157#comment-161157 ] lestin commented on JENKINS-13270: -- Hi Rob, Sorry I didn't make myself clear. I'll summarise them here: 1. Occassionly I saw in the jenkins log, jobs complaining about login attempt failed. However, we have the p4 ticket configured and it's considered as always valid & true. The same job, before & after the login attemp failure, is using "p4 issued ticket". 2. If i setup a job with a valid user/passwd combination, but not registered in p4 ticket, the job will fail to login. I don't have a clue how to look into the plugin hence can not provide more info other than the trials i had but can run more :) Thanks. Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOExcep
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161158#comment-161158 ] Rob Petti commented on JENKINS-13270: - The original log you attached contained several successful p4 login attempts. Logins are only performed using the password, not the ticket. The "WARNING: Using p4 issued ticket." message is informing the user that a new ticket has been saved into the environment after successfully logging in, not that it is using a ticket for login. I hope that clears things up. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.
[JIRA] (JENKINS-13329) Mercurial debug causes clone repository each time Mrather than update
Vladimir Kralik created JENKINS-13329: - Summary: Mercurial debug causes clone repository each time Mrather than update Key: JENKINS-13329 URL: https://issues.jenkins-ci.org/browse/JENKINS-13329 Project: Jenkins Issue Type: Bug Components: mercurial Affects Versions: current Environment: Linux, Jenkis 1.458, mercurial 1.7 Reporter: Vladimir Kralik Assignee: Kohsuke Kawaguchi Priority: Minor JENKINS-4672 gives possibility to setup Marcurial debug flag. When I switch it on, the all mercurial call is done with option "--debug". The first command, during the build, checks if configuration of repository wasn't changed. This check is done by comparision result of commad "hg showconfig paths.default" with jenkins configuration. But there is a different output if the debug option is ON. Without debug option : $ hg showconfig paths.default https://hg/hg/zpis With debug option : hg --debug showconfig paths.default read config from: /etc/mercurial/hgrc read config from: /data/hudson/.hgrc none: https://hg/hg/zpis So with the debug option, the mercurial configuration is always different as jenkins configuration. Result is : --- Building in workspace /data/hudson/jobs/vlk-pokus/workspace [workspace] $ hg --debug showconfig paths.default read config from: /etc/mercurial/hgrc read config from: /data/hudson/.hgrc none: https://hg/hg/zpis which looks different than https://hg/hg/zpis so falling back to fresh clone rather than incremental update Workaround : Switch off the degug option. -- 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-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161159#comment-161159 ] lestin commented on JENKINS-13270: -- Note that the log i put on just now was from the Jenkins job console log, not the jenkins log. Tha't why you didn't see the login information. I'll diable all my jenkins jobs and leave only the trial job running. then i'll send you the jenkins log. Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) >
[JIRA] (JENKINS-13200) 1.455: Block build when downstream project is building doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161160#comment-161160 ] Kay Abendroth commented on JENKINS-13200: - The fix I mentioned doesn't work. The problem is somewhere else. > 1.455: Block build when downstream project is building doesn't work > --- > > Key: JENKINS-13200 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13200 > Project: Jenkins > Issue Type: Bug > Components: build-pipeline > Environment: Jenkins 1.455, CentOS 5.5 >Reporter: Kay Abendroth >Priority: Blocker > Labels: build > > We have a test job chain that runs on a single slave. As this chain can be > triggered serveral times during the day it's very important that it is > blocked from running on that slave, if a downstream job is building. That > doesn't work anymore. -- 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-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161161#comment-161161 ] Rob Petti commented on JENKINS-13270: - How are you setting the ticket in the job config? > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused by: java.io.IOException: java.io.IOException: error=2, No such file or > dire
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161162#comment-161162 ] lestin commented on JENKINS-13270: -- I don't do that per job. The ticket is enabled by default as the jenkins account. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused by: java.io.IOException: java.io.IOException: error
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161163#comment-161163 ] Rob Petti commented on JENKINS-13270: - Can you elaborate on that? The plugin gets the ticket by logging in using the password, but you said that logging in using a password does not work. How did you get this working in the first place? > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExec
[JIRA] (JENKINS-3629) Charset of slave builder should be considered / changeable on slave definition
[
https://issues.jenkins-ci.org/browse/JENKINS-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Kacynski reopened JENKINS-3629:
--
Assignee: (was: Kohsuke Kawaguchi)
I have an IBM mainframe that I can test with and I wish to explore this issue
further.
> Charset of slave builder should be considered / changeable on slave definition
> --
>
> Key: JENKINS-3629
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3629
> Project: Jenkins
> Issue Type: Bug
> Components: other
>Affects Versions: current
> Environment: Platform: All, OS: All
>Reporter: olaf_vkb
>Priority: Critical
>
> Using Hudson build master on Windows XP together with a slave machine (IBM
> mainframe) connected by JNLP.
> Slave machine shows up perfectly in system information, e.g.
> ...
> file.encoding IBM-1047
> file.separator/
> ibm.signalhandling.rs false
> ibm.signalhandling.sigchain false
> ibm.signalhandling.sigint true
> ibm.system.encoding IBM-1047
> invokedviajava
> java.assistiveON
> java.awt.fonts
> java.awt.graphicsenv sun.awt.X11GraphicsEnvironment
> java.awt.printerjob sun.print.PSPrinterJob
> java.class.path slave.jar
> java.class.version49.0
> java.compiler j9jit23
> java.ext.dirs /usr/lpp/java15/J5.0/lib/ext
> java.fullversion J2RE 1.5.0 IBM J9 2.3 z/OS s390-31 j9vmmz3123-20080315
> (JIT
> enabled) J9VM - 20080314_17962_bHdSMr JIT - 20080130_0718ifx2_r8 GC -
> 200802_08
> java.home /usr/lpp/java15/J5.0
> ...
> When running shell command on such a slave, charset (IBM-1047) seems to be
> ignored, so output of shell is unreadable in web interface:
> â£�™£…„@‚¨@¤¢…™@�•–•¨”–¤¢
> Baue auf Slave hosttestu
> [FreeStyle] $ sh -xe /tmp/hudson38047.sh
> N@¢…£@ |~a£”—aˆ¤„¢–•óøðô÷K¢ˆ ÂäÉÓÄmÉÄ~òððù`ðõ`ðõmññ`ðô`ñö
> ÂäÉÓÄmÕäÔÂÅÙ~òö ÂäÉÓÄmãÁÇ~ˆ¤„¢–•`Æ™……⣨“…`òö
> ÃÂÃÔÁÉÕ~a¤¢™a“——aƒ‚ƒ“‰‚a§“ƒ
> ÄâÔÉmÃÖÕÆÉÇ~a¤¢™a“——a㉥–“‰a£¢”aƒ“‰…•£a‚�a‚‰•a„¢”K–—£
> ÄâÔÉmÄÉÙ~a¤¢™a“——a㉥–“‰a£¢”aƒ“‰…•£a‚�a‚‰• ÄâÔÉmÓÖÇ~a¥�™
> ÄâÔmÃÖÕÆÉÇ~a¤¢™a“——a㉥–“‰a£¢”aƒ“‰…•£a‚�a‚‰•a„¢”K–—£
> ÄâÔmÄÉÙ~a¤¢™a“——a㉥–“‰a£¢”aƒ“‰…•£a‚�a‚‰• ÄâÔmÓÖÇ~a¥�™ ÅÙÙÕÖ~ð
> ÅçÅÃäãÖÙmÕäÔÂÅÙ~ð ÈÖÔÅ~a¤aˆ–”…aˆ÷„�…�©
> ÈäÄâÖÕmÃÖÖÒÉÅ~ùƒù„ð…ò…`ø÷öõ`ôöññ`‚‚ƒø`ðùñ‚ñò÷òõööù
> ÈäÄâÖÕmÈÖÔÅ~ÄzààÄ–’¤”…•£…@¤•„@ʼn•¢£…““¤•‡…•ààÈ÷ÄÁÅÁéààKˆ¤„¢–•
> ÈäÄâÖÕmäÙÓ~ˆ££—zaa¨‚£”öðøñôùK¥’‚‰•£™�K„…zøðøða
> ÉÂÔmÑÁåÁmÃÖÔÔÁÕÄmÓÉÕÅ~‘�¥�@`‘�™@¢“�¥…K‘�™@`‘•“—䙓@ˆ££—zaa¨‚£”öðøñôùK¥’‚‰•£™�K„…zøðøðaƒ–”—¤£…™aˆ–¢££…¢£¤a¢“�¥…`�‡…•£K‘•“—
> ÉÆâ~@ Éâmäââ~èÅâ ÉãÄÉÙ~a¤¢™a“–ƒ�“aƒ¥¢”•£aÃåâã…¢£a£––“’‰£
> ÑÖÂmÕÁÔÅ~Æ™……⣨“… ÑâåÕ~a¤aˆ–”…aˆ÷„�…�©a¢¥•’‰£`ñKòKóKõõòñ
> ÑâåÕmÑÁÙâ~a¤aˆ–”…aˆ÷„�…�©a¢¥•’‰£`ñKòKóKõõòña¢¥•’‰£`ƒ“‰K‘�™za¤aˆ–”…aˆ÷„�…�©a¢¥•’‰£`ñKòKóKõõòña¢¥•’‰£K‘�™za¤aˆ–”…aˆ÷„�…�©a¢¥•’‰£`ñKòKóKõõòña‘•�K‘�™
> ÓÁÕÇ~Ã
> ÓÉÂ×ÁãÈ~a¤¢™a“——a‘�¥�ñõaÑõKða‚‰•aƒ“�¢¢‰ƒa“‰‚‘¥”K¢–za¤¢™a“——a‘�¥�ñõaÑõKða‚‰•aƒ“�¢¢‰ƒza¤¢™a“——a‘�¥�ñõaÑõKða‚‰•aza“‰‚za¤¢™a“‰‚za¤¢™a“——a‘�¥�a“‰‚zza¤¢™a“——aÑÇ�£…a‚‰•a”¥¢z
> ÓÉÕÅÕÖ~ñ ÓÓÖ×ã~è ÓÖÇÕÁÔÅ~È÷ÄÁÅÁé ÔÁÉÓ~a¤¢™a”�‰“aÈ÷ÄÁÅÁé
> ÔÁÉÓÃÈÅÃÒ~öðð ÔÁÕ×ÁãÈ~a¤¢™a”�•alÓza¤¢™a“–ƒ�“a”�•
> ÕÓâ×ÁãÈ~a¤¢™a“‰‚a•“¢a”¢‡alÓalÕ ÕÖÄÅ×ÅÕÄ~è Ö×ãÉÕÄ~ñ Öâ~Öâóùð
> ×ÁãÈ~a¤¢™a“——a‘�¥�ñõaÑõKða‚‰•za¤¢™a“–ƒ�“a‚‰•za‚‰•za¤¢™a‚‰•za¤¢™a“——a‘�¥�a‚‰•zza¤¢™a“——aƒ‚ƒ“‰‚a§“ƒa…§…zza¤¢™a“——aƒ‚ƒ“‰‚a§“ƒa‚‰•zKza¤¢™a“–ƒ�“aƒ¥¢”•£aƒ¥¢za¤¢™a“–ƒ�“aƒ¥¢”•£aÃåâã…¢£a£––“’‰£a‚‰•
> ××ÉÄ~øóøøùõó÷ ×âñ~à[@ ×âò~n@ ×âó~{o@ ×âô~N@
> ×æÄ~a¤aˆ–”…aˆ÷„�…�©aˆ¤„¢–•a¦–™’¢—�ƒ…aÆ™……⣨“… ÙÁÕÄÖÔ~òøõðõ âÅÃÖÕÄâ~ð
> âÈÅÓÓ~a‚‰•a¢ˆ âãÅ×ÓÉÂ~âèâñKÃÂÃKâÃÃÕÃÔ× ãÅÙÔ~§£…™”
> ãé~ÔÅé`ñÔÅâékÔóKõKðkÔñðKõKð
> æÖÙÒâ×ÁÃÅ~a¤aˆ–”…aˆ÷„�…�©aˆ¤„¢–•a¦–™’¢—�ƒ…aÆ™……⣨“…
> m~a¤¢™a“——a‘�¥�ñõaÑõKða‚‰•a‘�¥� mÂ×çÒmÁäãÖÃåã~ÖÕ mÃøùmÁÃÃÅ×ãÁÂÓÅmÙÃ~ô
> mÃøùmÃÃÔÖÄÅ~ñ mÃøùmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
> mÃøùmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ“¤„…@a¤¢™a“——a‰–ƒ“‰‚a‰•ƒ“¤„…
> mÃøùmÓÉÂÄÉÙâ~a“‰‚@a¤¢™a“‰‚ mÃøùm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ
> mÃøùmâÓÉÂm×ÙÅÆÉç~âèâñ mÃøùmæÖÙÒmäÕÉã~âèâÄÁ mÃÃmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
> mÃÃmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ“¤„…@a¤¢™a“——a‰–ƒ“‰‚a‰•ƒ“¤„…
> mÃÃmÓÉÂÄÉÙâ~a“‰‚@a¤¢™a“‰‚ mÃÃm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ mÃÃmâÓÉÂm×ÙÅÆÉç~âèâñ
> mÃÃmæÖÙÒmäÕÉã~âèâÄÁ mÃÙÅÁãÅmÓÁèÖäã~è mÃççmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
> mÃççmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ“¤„…@a¤¢™a“——a‰–ƒ“‰‚a‰•ƒ“¤„…
> mÃççmÓÉÂÄÉÙâ~a“‰‚@a¤¢™a“‰‚ mÃççm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ
> mÃççmâÓÉÂm×ÙÅÆÉç~âèâñ mÃççmæÖÙÒmäÕÉã~âèâÄÁ mÅÄÃm×ãÈÙÅÁÄmèÉÅÓÄ~`ò
> Ɖ•‰¢ˆ…„z@âäÃÃÅââ
>
> Last line is output of unix build-in shell command "set", manually converted
> to
> ASCII it looks like this:
> + set
> …@="/tmp/hudson38047.sh"…BUILD_ID="2009-05-05_11-04-16"…BUILD_NUMBER="26"…BUILD_TAG="hudson-FreeStyle-26"…CBCMAIN="/usr/lpp/cbclib/xlc"…DSMI_CONFIG="/usr/lpp/Tivoli/tsm/client/b
> /bin/dsm.opt"…DSMI_DIR="/usr/lpp/Tivoli/tsm/client/b /bin"…DSMI_LOG="/
[JIRA] (JENKINS-3629) Charset of slave builder should be considered / changeable on slave definition
[
https://issues.jenkins-ci.org/browse/JENKINS-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Kacynski updated JENKINS-3629:
-
Description:
Using Hudson build master on Windows XP together with a slave machine (IBM
mainframe) connected by JNLP.
Slave machine shows up perfectly in system information, e.g.
...
file.encoding IBM-1047
file.separator /
ibm.signalhandling.rs false
ibm.signalhandling.sigchain false
ibm.signalhandling.sigint true
ibm.system.encoding IBM-1047
invokedviajava
java.assistive ON
java.awt.fonts
java.awt.graphicsenvsun.awt.X11GraphicsEnvironment
java.awt.printerjob sun.print.PSPrinterJob
java.class.path slave.jar
java.class.version 49.0
java.compiler j9jit23
java.ext.dirs /usr/lpp/java15/J5.0/lib/ext
java.fullversionJ2RE 1.5.0 IBM J9 2.3 z/OS s390-31 j9vmmz3123-20080315
(JIT
enabled) J9VM - 20080314_17962_bHdSMr JIT - 20080130_0718ifx2_r8 GC - 200802_08
java.home /usr/lpp/java15/J5.0
...
When running shell command on such a slave, charset (IBM-1047) seems to be
ignored, so output of shell is unreadable in web interface:
â£�™£...„@‚¨@¤¢...™@�•-•¨"-¤¢
Baue auf Slave hosttestu
[FreeStyle] $ sh -xe /tmp/hudson38047.sh
N@¢...£@ |~a£"—aˆ¤„¢-•óøðô÷K¢ˆ ÂäÉÓÄmÉÄ~òððù`ðõ`ðõmññ`ðô`ñö
ÂäÉÓÄmÕäÔÂÅÙ~òö ÂäÉÓÄmãÁÇ~ˆ¤„¢-•`Æ™..⣨"...`òö
ÃÂÃÔÁÉÕ~a¤¢™a"——aƒ‚ƒ"‰‚a§"ƒ
ÄâÔÉmÃÖÕÆÉÇ~a¤¢™a"——a㉥-"‰a£¢"aƒ"‰...•£a‚�a‚‰•a„¢"K-—£
ÄâÔÉmÄÉÙ~a¤¢™a"——a㉥-"‰a£¢"aƒ"‰...•£a‚�a‚‰• ÄâÔÉmÓÖÇ~a¥�™
ÄâÔmÃÖÕÆÉÇ~a¤¢™a"——a㉥-"‰a£¢"aƒ"‰...•£a‚�a‚‰•a„¢"K-—£
ÄâÔmÄÉÙ~a¤¢™a"——a㉥-"‰a£¢"aƒ"‰...•£a‚�a‚‰• ÄâÔmÓÖÇ~a¥�™ ÅÙÙÕÖ~ð
ÅçÅÃäãÖÙmÕäÔÂÅÙ~ð ÈÖÔÅ~a¤aˆ-"...aˆ÷„�...�©
ÈäÄâÖÕmÃÖÖÒÉÅ~ùƒù„ð...ò...`ø÷öõ`ôöññ`‚‚ƒø`ðùñ‚ñò÷òõööù
ÈäÄâÖÕmÈÖÔÅ~ÄzààÄ-'¤"...•£...@¤•„@ʼn•¢£...""¤•‡...•ààÈ÷ÄÁÅÁéààKˆ¤„¢-•
ÈäÄâÖÕmäÙÓ~ˆ££—zaa¨‚£"öðøñôùK¥'‚‰•£™�K„...zøðøða
ÉÂÔmÑÁåÁmÃÖÔÔÁÕÄmÓÉÕÅ~'�¥�@`'�™@¢"�¥...K'�™@`'•"—ä™"@ˆ££—zaa¨‚£"öðøñôùK¥'‚‰•£™�K„...zøðøðaƒ-"—¤£...™aˆ-¢££...¢£¤a¢"�¥...`�‡...•£K'•"—
ÉÆâ~@ Éâmäââ~èÅâ ÉãÄÉÙ~a¤¢™a"-ƒ�"aƒ¥¢"•£aÃåâã...¢£a£--"'‰£
ÑÖÂmÕÁÔÅ~Æ™..⣨"... ÑâåÕ~a¤aˆ-"...aˆ÷„�...�©a¢¥•'‰£`ñKòKóKõõòñ
ÑâåÕmÑÁÙâ~a¤aˆ-"...aˆ÷„�...�©a¢¥•'‰£`ñKòKóKõõòña¢¥•'‰£`ƒ"‰K'�™za¤aˆ-"...aˆ÷„�...�©a¢¥•'‰£`ñKòKóKõõòña¢¥•'‰£K'�™za¤aˆ-"...aˆ÷„�...�©a¢¥•'‰£`ñKòKóKõõòña'•�K'�™
ÓÁÕÇ~Ã
ÓÉÂ×ÁãÈ~a¤¢™a"——a'�¥�ñõaÑõKða‚‰•aƒ"�¢¢‰ƒa"‰‚'¥"K¢-za¤¢™a"——a'�¥�ñõaÑõKða‚‰•aƒ"�¢¢‰ƒza¤¢™a"——a'�¥�ñõaÑõKða‚‰•aza"‰‚za¤¢™a"‰‚za¤¢™a"——a'�¥�a"‰‚zza¤¢™a"——aÑÇ�£...a‚‰•a"¥¢z
ÓÉÕÅÕÖ~ñ ÓÓÖ×ã~è ÓÖÇÕÁÔÅ~È÷ÄÁÅÁé ÔÁÉÓ~a¤¢™a"�‰"aÈ÷ÄÁÅÁé
ÔÁÉÓÃÈÅÃÒ~öðð ÔÁÕ×ÁãÈ~a¤¢™a"�•alÓza¤¢™a"-ƒ�"a"�•
ÕÓâ×ÁãÈ~a¤¢™a"‰‚a•"¢a"¢‡alÓalÕ ÕÖÄÅ×ÅÕÄ~è Ö×ãÉÕÄ~ñ Öâ~Öâóùð
×ÁãÈ~a¤¢™a"——a'�¥�ñõaÑõKða‚‰•za¤¢™a"-ƒ�"a‚‰•za‚‰•za¤¢™a‚‰•za¤¢™a"——a'�¥�a‚‰•zza¤¢™a"——aƒ‚ƒ"‰‚a§"ƒa...§...zza¤¢™a"——aƒ‚ƒ"‰‚a§"ƒa‚‰•zKza¤¢™a"-ƒ�"aƒ¥¢"•£aƒ¥¢za¤¢™a"-ƒ�"aƒ¥¢"•£aÃåâã...¢£a£--"'‰£a‚‰•
××ÉÄ~øóøøùõó÷ ×âñ~à[@ ×âò~n@ ×âó~{o@ ×âô~N@
×æÄ~a¤aˆ-"...aˆ÷„�...�©aˆ¤„¢-•a¦-™'¢—�ƒ...aÆ™..⣨"... ÙÁÕÄÖÔ~òøõðõ
âÅÃÖÕÄâ~ð âÈÅÓÓ~a‚‰•a¢ˆ âãÅ×ÓÉÂ~âèâñKÃÂÃKâÃÃÕÃÔ× ãÅÙÔ~§£...™"
ãé~ÔÅé`ñÔÅâékÔóKõKðkÔñðKõKð
æÖÙÒâ×ÁÃÅ~a¤aˆ-"...aˆ÷„�...�©aˆ¤„¢-•a¦-™'¢—�ƒ...aÆ™..⣨"...
m~a¤¢™a"——a'�¥�ñõaÑõKða‚‰•a'�¥� mÂ×çÒmÁäãÖÃåã~ÖÕ mÃøùmÁÃÃÅ×ãÁÂÓÅmÙÃ~ô
mÃøùmÃÃÔÖÄÅ~ñ mÃøùmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
mÃøùmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ"¤„...@a¤¢™a"——a‰-ƒ"‰‚a‰•ƒ"¤„...
mÃøùmÓÉÂÄÉÙâ~a"‰‚@a¤¢™a"‰‚ mÃøùm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ
mÃøùmâÓÉÂm×ÙÅÆÉç~âèâñ mÃøùmæÖÙÒmäÕÉã~âèâÄÁ mÃÃmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
mÃÃmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ"¤„...@a¤¢™a"——a‰-ƒ"‰‚a‰•ƒ"¤„...
mÃÃmÓÉÂÄÉÙâ~a"‰‚@a¤¢™a"‰‚ mÃÃm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ mÃÃmâÓÉÂm×ÙÅÆÉç~âèâñ
mÃÃmæÖÙÒmäÕÉã~âèâÄÁ mÃÙÅÁãÅmÓÁèÖäã~è mÃççmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
mÃççmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ"¤„...@a¤¢™a"——a‰-ƒ"‰‚a‰•ƒ"¤„...
mÃççmÓÉÂÄÉÙâ~a"‰‚@a¤¢™a"‰‚ mÃççm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ
mÃççmâÓÉÂm×ÙÅÆÉç~âèâñ mÃççmæÖÙÒmäÕÉã~âèâÄÁ mÅÄÃm×ãÈÙÅÁÄmèÉÅÓÄ~`ò
Ɖ•‰¢ˆ...„z@âäÃÃÅââ
Last line is output of unix build-in shell command "set", manually converted to
ASCII it looks like this:
+ set
...@="/tmp/hudson38047.sh"...BUILD_ID="2009-05-05_11-04-16"...BUILD_NUMBER="26"...BUILD_TAG="hudson-FreeStyle-26"...CBCMAIN="/usr/lpp/cbclib/xlc"...DSMI_CONFIG="/usr/lpp/Tivoli/tsm/client/b
/bin/dsm.opt"...DSMI_DIR="/usr/lpp/Tivoli/tsm/client/b /bin"...DSMI_LOG="/v
r"...DSM_CONFIG="/usr/lpp/Tivoli/tsm/client/b
/bin/dsm.opt"...DSM_DIR="/usr/lpp/Tivoli/tsm/client/b /bin"...DSM_LOG="/v
r"...ERRNO="0"...EXECUTOR_NUMBER="0"...HOME="/u/home/h7d e
z"...HUDSON_COOKIE="9c9d0e2e-8765-4611-bbc8-091b12725669"...HUDSON_HOME="D:\\Dokumente
und
Einstellungen\\H7DAEAZ\\.hudson"...HUDSON_URL="http://ybtm608149.vkbintr
.de:8080/"...IBM_JAVA_COMMAND_LINE="j v
-j r sl ve.j r -jnlpUrl
http://ybtm608149.vkbintr .de:8080/computer/hosttestu/sl ve- gent.jnlp"...IFS="
..."...IS_USS="YES"...ITDIR="/usr/loc
l/cvsmnt/CVSTest/toolkit"...JOB_NAME="FreeStyle"...JSVN="/u/home/h7d e
z/svnkit-1.2.3.5521"...JSVN_JARS="/u/h
[JIRA] (JENKINS-3629) Charset of slave builder should be considered / changeable on slave definition
[
https://issues.jenkins-ci.org/browse/JENKINS-3629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Kacynski updated JENKINS-3629:
-
Component/s: (was: other)
> Charset of slave builder should be considered / changeable on slave definition
> --
>
> Key: JENKINS-3629
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3629
> Project: Jenkins
> Issue Type: Bug
> Components: master-slave, slave-prerequisites, slave-setup
>Affects Versions: current
> Environment: Platform: All, OS: All
>Reporter: olaf_vkb
>Priority: Critical
>
> Using Hudson build master on Windows XP together with a slave machine (IBM
> mainframe) connected by JNLP.
> Slave machine shows up perfectly in system information, e.g.
> ...
> file.encoding IBM-1047
> file.separator/
> ibm.signalhandling.rs false
> ibm.signalhandling.sigchain false
> ibm.signalhandling.sigint true
> ibm.system.encoding IBM-1047
> invokedviajava
> java.assistiveON
> java.awt.fonts
> java.awt.graphicsenv sun.awt.X11GraphicsEnvironment
> java.awt.printerjob sun.print.PSPrinterJob
> java.class.path slave.jar
> java.class.version49.0
> java.compiler j9jit23
> java.ext.dirs /usr/lpp/java15/J5.0/lib/ext
> java.fullversion J2RE 1.5.0 IBM J9 2.3 z/OS s390-31 j9vmmz3123-20080315
> (JIT
> enabled) J9VM - 20080314_17962_bHdSMr JIT - 20080130_0718ifx2_r8 GC -
> 200802_08
> java.home /usr/lpp/java15/J5.0
> ...
> When running shell command on such a slave, charset (IBM-1047) seems to be
> ignored, so output of shell is unreadable in web interface:
> â£�™£...„@‚¨@¤¢...™@�•-•¨"-¤¢
> Baue auf Slave hosttestu
> [FreeStyle] $ sh -xe /tmp/hudson38047.sh
> N@¢...£@ |~a£"—aˆ¤„¢-•óøðô÷K¢ˆ ÂäÉÓÄmÉÄ~òððù`ðõ`ðõmññ`ðô`ñö
> ÂäÉÓÄmÕäÔÂÅÙ~òö ÂäÉÓÄmãÁÇ~ˆ¤„¢-•`Æ™..⣨"...`òö
> ÃÂÃÔÁÉÕ~a¤¢™a"——aƒ‚ƒ"‰‚a§"ƒ
> ÄâÔÉmÃÖÕÆÉÇ~a¤¢™a"——a㉥-"‰a£¢"aƒ"‰...•£a‚�a‚‰•a„¢"K-—£
> ÄâÔÉmÄÉÙ~a¤¢™a"——a㉥-"‰a£¢"aƒ"‰...•£a‚�a‚‰• ÄâÔÉmÓÖÇ~a¥�™
> ÄâÔmÃÖÕÆÉÇ~a¤¢™a"——a㉥-"‰a£¢"aƒ"‰...•£a‚�a‚‰•a„¢"K-—£
> ÄâÔmÄÉÙ~a¤¢™a"——a㉥-"‰a£¢"aƒ"‰...•£a‚�a‚‰• ÄâÔmÓÖÇ~a¥�™ ÅÙÙÕÖ~ð
> ÅçÅÃäãÖÙmÕäÔÂÅÙ~ð ÈÖÔÅ~a¤aˆ-"...aˆ÷„�...�©
> ÈäÄâÖÕmÃÖÖÒÉÅ~ùƒù„ð...ò...`ø÷öõ`ôöññ`‚‚ƒø`ðùñ‚ñò÷òõööù
> ÈäÄâÖÕmÈÖÔÅ~ÄzààÄ-'¤"...•£...@¤•„@ʼn•¢£...""¤•‡...•ààÈ÷ÄÁÅÁéààKˆ¤„¢-•
> ÈäÄâÖÕmäÙÓ~ˆ££—zaa¨‚£"öðøñôùK¥'‚‰•£™�K„...zøðøða
> ÉÂÔmÑÁåÁmÃÖÔÔÁÕÄmÓÉÕÅ~'�¥�@`'�™@¢"�¥...K'�™@`'•"—ä™"@ˆ££—zaa¨‚£"öðøñôùK¥'‚‰•£™�K„...zøðøðaƒ-"—¤£...™aˆ-¢££...¢£¤a¢"�¥...`�‡...•£K'•"—
> ÉÆâ~@ Éâmäââ~èÅâ ÉãÄÉÙ~a¤¢™a"-ƒ�"aƒ¥¢"•£aÃåâã...¢£a£--"'‰£
> ÑÖÂmÕÁÔÅ~Æ™..⣨"... ÑâåÕ~a¤aˆ-"...aˆ÷„�...�©a¢¥•'‰£`ñKòKóKõõòñ
> ÑâåÕmÑÁÙâ~a¤aˆ-"...aˆ÷„�...�©a¢¥•'‰£`ñKòKóKõõòña¢¥•'‰£`ƒ"‰K'�™za¤aˆ-"...aˆ÷„�...�©a¢¥•'‰£`ñKòKóKõõòña¢¥•'‰£K'�™za¤aˆ-"...aˆ÷„�...�©a¢¥•'‰£`ñKòKóKõõòña'•�K'�™
> ÓÁÕÇ~Ã
> ÓÉÂ×ÁãÈ~a¤¢™a"——a'�¥�ñõaÑõKða‚‰•aƒ"�¢¢‰ƒa"‰‚'¥"K¢-za¤¢™a"——a'�¥�ñõaÑõKða‚‰•aƒ"�¢¢‰ƒza¤¢™a"——a'�¥�ñõaÑõKða‚‰•aza"‰‚za¤¢™a"‰‚za¤¢™a"——a'�¥�a"‰‚zza¤¢™a"——aÑÇ�£...a‚‰•a"¥¢z
> ÓÉÕÅÕÖ~ñ ÓÓÖ×ã~è ÓÖÇÕÁÔÅ~È÷ÄÁÅÁé ÔÁÉÓ~a¤¢™a"�‰"aÈ÷ÄÁÅÁé
> ÔÁÉÓÃÈÅÃÒ~öðð ÔÁÕ×ÁãÈ~a¤¢™a"�•alÓza¤¢™a"-ƒ�"a"�•
> ÕÓâ×ÁãÈ~a¤¢™a"‰‚a•"¢a"¢‡alÓalÕ ÕÖÄÅ×ÅÕÄ~è Ö×ãÉÕÄ~ñ Öâ~Öâóùð
> ×ÁãÈ~a¤¢™a"——a'�¥�ñõaÑõKða‚‰•za¤¢™a"-ƒ�"a‚‰•za‚‰•za¤¢™a‚‰•za¤¢™a"——a'�¥�a‚‰•zza¤¢™a"——aƒ‚ƒ"‰‚a§"ƒa...§...zza¤¢™a"——aƒ‚ƒ"‰‚a§"ƒa‚‰•zKza¤¢™a"-ƒ�"aƒ¥¢"•£aƒ¥¢za¤¢™a"-ƒ�"aƒ¥¢"•£aÃåâã...¢£a£--"'‰£a‚‰•
> ××ÉÄ~øóøøùõó÷ ×âñ~à[@ ×âò~n@ ×âó~{o@ ×âô~N@
> ×æÄ~a¤aˆ-"...aˆ÷„�...�©aˆ¤„¢-•a¦-™'¢—�ƒ...aÆ™..⣨"... ÙÁÕÄÖÔ~òøõðõ
> âÅÃÖÕÄâ~ð âÈÅÓÓ~a‚‰•a¢ˆ âãÅ×ÓÉÂ~âèâñKÃÂÃKâÃÃÕÃÔ× ãÅÙÔ~§£...™"
> ãé~ÔÅé`ñÔÅâékÔóKõKðkÔñðKõKð
> æÖÙÒâ×ÁÃÅ~a¤aˆ-"...aˆ÷„�...�©aˆ¤„¢-•a¦-™'¢—�ƒ...aÆ™..⣨"...
> m~a¤¢™a"——a'�¥�ñõaÑõKða‚‰•a'�¥� mÂ×çÒmÁäãÖÃåã~ÖÕ mÃøùmÁÃÃÅ×ãÁÂÓÅmÙÃ~ô
> mÃøùmÃÃÔÖÄÅ~ñ mÃøùmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
> mÃøùmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ"¤„...@a¤¢™a"——a‰-ƒ"‰‚a‰•ƒ"¤„...
> mÃøùmÓÉÂÄÉÙâ~a"‰‚@a¤¢™a"‰‚ mÃøùm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ
> mÃøùmâÓÉÂm×ÙÅÆÉç~âèâñ mÃøùmæÖÙÒmäÕÉã~âèâÄÁ mÃÃmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
> mÃÃmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ"¤„...@a¤¢™a"——a‰-ƒ"‰‚a‰•ƒ"¤„...
> mÃÃmÓÉÂÄÉÙâ~a"‰‚@a¤¢™a"‰‚ mÃÃm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ mÃÃmâÓÉÂm×ÙÅÆÉç~âèâñ
> mÃÃmæÖÙÒmäÕÉã~âèâÄÁ mÃÙÅÁãÅmÓÁèÖäã~è mÃççmÃÓÉÂm×ÙÅÆÉç~âèâñKÃÂÃ
> mÃççmÉÕÃÄÉÙâ~a¤¢™a‰•ƒ"¤„...@a¤¢™a"——a‰-ƒ"‰‚a‰•ƒ"¤„...
> mÃççmÓÉÂÄÉÙâ~a"‰‚@a¤¢™a"‰‚ mÃççm×ÓÉÂm×ÙÅÆÉç~âèâñKÃÅÅ
> mÃççmâÓÉÂm×ÙÅÆÉç~âèâñ mÃççmæÖÙÒmäÕÉã~âèâÄÁ mÅÄÃm×ãÈÙÅÁÄmèÉÅÓÄ~`ò
> Ɖ•‰¢ˆ...„z@âäÃÃÅââ
>
> Last line is output of unix build-in shell command "set", manually converted
> to
> ASCII it looks like this:
> + set
> ...@="/tmp/hudson38047.sh"...BUILD_ID="2009-05-05_11-04-16"...BUILD_NUMBER="26"...BUILD_TAG="hudson-FreeStyle-26"...CBCMAIN="/usr/lpp/cbclib/xlc"...DSMI_CONFIG="/usr/lpp/Tivoli/tsm/client/b
> /bin/dsm.
[JIRA] (JENKINS-13200) 1.455: Block build when downstream project is building doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-13200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161160#comment-161160 ] Kay Abendroth edited comment on JENKINS-13200 at 4/3/12 3:43 PM: - The fix I mentioned doesn't work. The problem is somewhere else, but still present. was (Author: kay_abendroth): The fix I mentioned doesn't work. The problem is somewhere else. > 1.455: Block build when downstream project is building doesn't work > --- > > Key: JENKINS-13200 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13200 > Project: Jenkins > Issue Type: Bug > Components: build-pipeline > Environment: Jenkins 1.455, CentOS 5.5 >Reporter: Kay Abendroth >Priority: Blocker > Labels: build > > We have a test job chain that runs on a single slave. As this chain can be > triggered serveral times during the day it's very important that it is > blocked from running on that slave, if a downstream job is building. That > doesn't work anymore. -- 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-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161165#comment-161165 ] lestin commented on JENKINS-13270: -- Ah, maybe that's where the confusion is. Below description is based on Linux BTW. Perforce can create a p4 ticket file (normally |/.p4ticket) that remembers your login if you use "p4 login -a" Once that's setup (you can setenv P4TICKET to change the default file path), p4 will check the file to see if this user had been id-cleared. In my setup, I configured jenkins_home/.p4ticket and it has registered my success login (p4 login -a with my user id). With this, jenkins can access the perforce database as if it were me (or any one else that has registered himself in jenkins_home/.p4ticket). Now at the job configuration page, i configured it as normal (correct combination of user id, passwd). If this user id has been registered in jenkins_home/.p4ticket, the passwd can be a wrong one, no issue at all. If this user id has not been registered in jenkins_home/.p4ticket, even the correct combination will caused a login error with the line "Perforce password (P4PASSWD) invalid or unset." --- Note that this line is from the web page, not the jenkins.log I tried to set P4PASSWD variable in the environment var field, tick the box in job configuration etc, none of them worked. If i put an invalid user id, the plugin immediately informs me that. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161166#comment-161166 ] lestin commented on JENKINS-13270: -- With a cleaner log, now i noticed that even with a non existing user id, i saw the following log coming out from jenkins.log: === Apr 3, 2012 4:51:18 PM com.tek42.perforce.parse.AbstractPerforceTemplate login WARNING: Using p4 issued ticket. Apr 3, 2012 4:51:18 PM com.tek42.perforce.process.CmdLineExecutor exec INFO: Executing: /tools/perforce/2010.1/bin.linux26x86/p4 -P CA84BE534B260418A89133C914BFE6B2 counter change Apr 3, 2012 4:51:19 PM com.tek42.perforce.process.CmdLineExecutor exec INFO: Executing: /tools/perforce/2010.1/bin.linux26x86/p4 -P CA84BE534B260418A89133C914BFE6B2 workspace -o jenkins_playground Apr 3, 2012 4:51:19 PM com.tek42.perforce.process.CmdLineExecutor exec INFO: Executing: /tools/perforce/2010.1/bin.linux26x86/p4 counter change Apr 3, 2012 4:51:19 PM com.tek42.perforce.process.CmdLineExecutor exec === At the same time, the web GUI told me the following: [/tmp] $ /tools/perforce/2010.1/bin.linux26x86/p4 -s client -i Caught exception communicating with perforce. User lestin2 doesn't exist. For Command: /tools/perforce/2010.1/bin.linux26x86/p4 -s client -i With Data: === Client: jenkins_playground--1850485244 Description: Root: /tmp Options: noallwrite clobber nocompress unlocked nomodtime rmdir LineEnd: local View: //training/test2/... //jenkins_playground--1850485244/... === Any hints so that i can dig further? Thanks. Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.jav
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161167#comment-161167 ] Rob Petti commented on JENKINS-13270: - Ok, so the real issue is that logging in using username and password isn't working... If your tickets are mysteriously getting invalidated by perforce, there's not a whole lot the plugin can do about that if it can't log in properly. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161168#comment-161168 ] Rob Petti commented on JENKINS-13270: - The build log and the jenkins log don't seem like they match in that instance. The jenkins log looks like it's polling on the master, while the build log looks like it's building on a slave. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.ex
[JIRA] (JENKINS-11887) Support Git for "Repository browser" setting
[ https://issues.jenkins-ci.org/browse/JENKINS-11887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161169#comment-161169 ] Bernhard T commented on JENKINS-11887: -- Hi Gerd, I am looking for the identical feature for svn urls. The repository stays the same for one Jenkins job. Hence an additional settings input field for the trac repository name would do perfectly. Bernhard > Support Git for "Repository browser" setting > > > Key: JENKINS-11887 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11887 > Project: Jenkins > Issue Type: Improvement > Components: git, trac > Environment: Jenkins 1.441, Trac Plugin 1.12 >Reporter: Gerd Zanker >Assignee: Gerd Zanker >Priority: Minor > Labels: trac > Fix For: current > > Attachments: trac.hpi > > > In the [Trac Plugin > documentation|https://wiki.jenkins-ci.org/display/jenkins/Trac+Plugin] the > configuration is described as > bq. In the Source Code Management section, choose "Trac" for the "Repository > browser" setting. > This settings "Trac" is not available for when I use git as a SCM. > Can this selection be added? > > The Trac-plugin code supports "TracGit" for the "Repository browser" setting. > The given Trac URL at the top of the job settings will be used to generate > links for git changesets, files and diffs to your Trac "Browse Source" area. -- 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-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161170#comment-161170 ] lestin commented on JENKINS-13270: -- Hi Rob, I don't know but I can disable the slave and give it another go. I also need to confess (again) that i dont know if the ticket-invalid was caused by perforce itself or not. For day to day work, perforce never refused us. --- But from the frequence/percentage of the invalid situation, i can believe it can be perforce's bug. But as you spotted, the reason i used the ticket was i couldn't get the normal username/password login to work. Thanks. Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$L
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161171#comment-161171 ] lestin commented on JENKINS-13270: -- Hi Rob, I've done some more trials with no slaves involved and all other plug-ins disabled and it revealed more details. I was wrong saying that correct combination of username/passwd didn't work --- good news. What i noticed is, those information seemed to be only kept (used) within the p4 plugin. They're not exposed to the job terminal hence you saw the error when i tried the "p4 sync". However it's quite common for the job itself trying to invoke p4, e.g. lable, check-out, pop etc. I believe that it already sets/exports the P4USER into the job terminal. (from the p4 info outputs) Is it possible that the plugin can then export P4PASSWD to the job terminal? Thanks! Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run
[JIRA] (JENKINS-13330) Jenkins slave hangs in post build phase
Clark Wright created JENKINS-13330: -- Summary: Jenkins slave hangs in post build phase Key: JENKINS-13330 URL: https://issues.jenkins-ci.org/browse/JENKINS-13330 Project: Jenkins Issue Type: Bug Components: master-slave, slave-status Environment: RHEL 5, both master and all slaves. Jenkins is running inside of Tomcat Reporter: Clark Wright Priority: Critical Attachments: Screenshot-galleon_allIntegration #1196 Console [Jenkins] - Mozilla Firefox.png We have an intermittent problem with slaves hanging AFTER the job itself is finished. In the post processing step (?) what we see is that the console log has this line: Description set: vap_current_iter-2012_03_29_19_01_03 And then nothing. Usually, it will look like this: Description set: prod_pull-2012_03_28_19_01_03 Notifying upstream build armada_Launch_prod_pull #13 of job completion Project armada_Launch_prod_pull still waiting for 1 builds to complete Notifying upstream projects of job completion Notifying upstream of completion: armada_Launch_prod_pull #13 Finished: SUCCESS I setup a logger for hudson.model.Run, and it currently has this : at java.lang.Thread.run(Thread.java:619) Mar 30, 2012 12:44:00 PM hudson.model.Run run INFO: galleon_allUnit #1134 main build action completed: SUCCESS Mar 30, 2012 12:44:00 PM hudson.model.Run setResult FINE: galleon_allUnit #1134 : result is set to SUCCESS java.lang.Exception at hudson.model.Run.setResult(Run.java:352) at hudson.model.Run.run(Run.java:1410) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) Repeated for every hung slave. The main hudson log doesn't have any additional information. Disconnecting the slave has no effect. Trying to do an orderly shutdown of Jenkins has no effect (jenkins actually appears to hang on shutdown). The only way we have found to recover is to kill -9 the tomcat process. The tread dump for one of the slaves (they are all the same) is: Thread Dump Channel reader thread: channel "Channel reader thread: channel" Id=9 Group=main RUNNABLE (in native) at java.io.FileInputStream.readBytes(Native Method) at java.io.FileInputStream.read(FileInputStream.java:199) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) - locked java.io.BufferedInputStream@1ae615a at java.io.ObjectInputStream$PeekInputStream.peek(ObjectInputStream.java:2249) at java.io.ObjectInputStream$BlockDataInputStream.peek(ObjectInputStream.java:2542) at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2552) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1297) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:351) at hudson.remoting.Channel$ReaderThread.run(Channel.java:1030) main "main" Id=1 Group=main WAITING on hudson.remoting.Channel@e1d5ea at java.lang.Object.wait(Native Method) - waiting on hudson.remoting.Channel@e1d5ea at java.lang.Object.wait(Object.java:485) at hudson.remoting.Channel.join(Channel.java:766) at hudson.remoting.Launcher.main(Launcher.java:420) at hudson.remoting.Launcher.runWithStdinStdout(Launcher.java:366) at hudson.remoting.Launcher.run(Launcher.java:206) at hudson.remoting.Launcher.main(Launcher.java:168) Ping thread for channel hudson.remoting.Channel@e1d5ea:channel "Ping thread for channel hudson.remoting.Channel@e1d5ea:channel" Id=10 Group=main TIMED_WAITING at java.lang.Thread.sleep(Native Method) at hudson.remoting.PingThread.run(PingThread.java:86) Pipe writer thread: channel "Pipe writer thread: channel" Id=12 Group=main WAITING on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@14263ed at sun.misc.Unsafe.park(Native Method) - waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@14263ed at java.util.concurrent.locks.LockSupport.park(LockSupport.java:158) at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:1925) at java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:358) at java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:947) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907) at java.lang.Thread.run(Thread.java:619) pool-1-thread-267 "pool-1-thread-267" Id=285 Group=main RUNNABLE at sun.management.ThreadImpl.dumpThreads0(Native Method) at sun.management.ThreadImpl.dumpAllThreads(ThreadImpl.java:374) at hudson.Functions.getThreadInfos(Functions.java:872) at hudson.util.RemotingDiagnostics$G
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161172#comment-161172 ] Rob Petti commented on JENKINS-13270: - There is an option in the job config to expose P4PASSWD in the build environment. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused by: java.io.IOException: java.io.IOException:
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161173#comment-161173 ] lestin commented on JENKINS-13270: -- Hi Rob, I knew that and that was selected already in my job spec. But doesn't seem to take any effect based on the web GUI log. == + p4 sync -f ... Perforce password (P4PASSWD) invalid or unset. Build step 'Execute shell' marked build as failure Notifying upstream projects of job completion Finished: FAILURE == Could it be because that i had P4TICKET configured? Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$Local
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[
https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161174#comment-161174
]
Rob Petti commented on JENKINS-13270:
-
Your perforce security level probably prevents the P4PASSWD environment
variable from being used for authentication.
I recommend unsetting P4TICKETS to ensure that the same tickets file
(~/.p4tickets) is used by the build process and the perforce plugin login
operation.
Alternatively, you can alter your scripts to explicitly specify the password on
the command line: "p4 -P${P4PASSWD} sync -f ..."
> Occasional login failures using p4 ticket
> -
>
> Key: JENKINS-13270
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13270
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
>Affects Versions: current
> Environment: 1.456 Jenkins with latest perforce plugin
>Reporter: lestin
>Assignee: Rob Petti
>Priority: Minor
>
> Saw the following log whilst nothing has changed during the period:
>
> INFO: job_name_here #4437 main build action completed: SUCCESS
> Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:01:18 AM hudson.model.Run run
> INFO: job_name_here #4438 main build action completed: SUCCESS
> Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login
> attempt failed: Password invalid.
> Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Attempt to workaround p4 executable location failed
> com.tek42.perforce.PerforceException: Could not run perforce command.
> at
> hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
> at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61)
> at
> hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325)
> at
> hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019)
> at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
> at hudson.scm.SCM.poll(SCM.java:373)
> at hudson.model.AbstractProject.poll(AbstractProject.java:1340)
> at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
> at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
> at
> hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
> 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.io.IOException: Cannot run program "/usr/bin/p4" (in
> directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No
> such file or directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
> at hudson.Proc$LocalProc.(Proc.java:244)
> at hudson.Proc$LocalPro
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161175#comment-161175 ] lestin commented on JENKINS-13270: -- Hi Rob, "I recommend unsetting P4TICKETS to ensure that the same tickets file (~/.p4tickets) is used by the build process and the perforce plugin login operation" ^^^It is configured to the same ticket file. However, the use case here is, jenkins is running of one account but the jobs are setup by different engineers. Unless the jenkins .p4ticket contains all the user entries, it won't be able to achieve that. //unless the plugin does a "p4 login -a" to add user entry, which it doesn't seem to be doing now. I think i've found the reason it doesn't work with the P4PASSWD in our server setup when we have the expose box ticked. The variable being set in the environment variable P4PASSWD is the user input whilst it should be the hash passwd like the one you used in the plugin (p4 -P ...). I tried to do an "echo $P4PASSWD" and i got the passwd in plain text instead of the hash ones like "687A2F0323B3C666D6C69E5E2F78B665" Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.con
[JIRA] (JENKINS-13324) Perforce mail address resolver should fall back to other resolvers if mail address is invalid
[ https://issues.jenkins-ci.org/browse/JENKINS-13324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161176#comment-161176 ] Rob Petti commented on JENKINS-13324: - PerforceMailResolver will return null if no email address is found. The problem as you said is that perforce will always have an email set for users, and will invent an email address if none is supplied (usually user@host or user@client). I don't really have a problem with hard coding some value such as 'n/a', assuming that perforce will accept it as a valid email address. Though I question the need for it, since perforce admins will need to forcefully reset all the email addresses to that value anyways. If someone needs to go through all that trouble to set email addresses to 'n/a', why not just set the email addresses correctly instead? > Perforce mail address resolver should fall back to other resolvers if mail > address is invalid > - > > Key: JENKINS-13324 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13324 > Project: Jenkins > Issue Type: Bug > Components: perforce > Environment: Perforce 2011.1 > perforce-plugin 1.3.12 >Reporter: Mikko Tapaninen > > Perforce mail address resolver is always returning a string, no matter what > the actual email address is. I don't know what is the order how Jenkins loops > through the various MailAddressResolver instances but if some instance > returns an actual string (i.e. non-null), it will stick with that. I don't > think it's feasible to really check whether the email address provided by > Perforce is valid, but PerforceMailResolver could check for some value (e.g. > "n/a") and return null if it matches. At least with Perforce 2011.1 you can't > have an empty value for an email address. > There could be an UI element for configuring which email address would be > thought as invalid, but I'm fine with hardcoding "n/a" there and documenting > it somewhere. Would this be ok? -- 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-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161177#comment-161177 ] Rob Petti commented on JENKINS-13270: - What version of the perforce plugin are you using? That looks like a ticket hash, not an encrypted password. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused by: java.io.IOExce
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161178#comment-161178 ] Rob Petti commented on JENKINS-13270: - FYI, P4PASSWD is supposed to be the plain text password. That's why there is a seperate option to enable it in the environment. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused
[JIRA] (JENKINS-13109) Huge changelogs eat all the Java memory
[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161179#comment-161179
]
Rob Petti commented on JENKINS-13109:
-
Tim, the wiki has some information on how to debug memory leaks:
https://wiki.jenkins-ci.org/display/JENKINS/I'm+getting+OutOfMemoryError
I'll also note that you are getting a different error from the one filed in the
ticket, so your cause might be different.
> Huge changelogs eat all the Java memory
> ---
>
> Key: JENKINS-13109
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Environment: Windows Server 2008 HPC Edition
> 64-bit JVM 1.6.0_29
> Running Jenkins service with "-Xrs -Xmx2048m
> -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar
> "%BASE%\jenkins.war" --httpPort=8080"
>Reporter: Mikko Tapaninen
>
> With really huge changelists the p4 plugin can run out of java heap space. At
> least it looks like the reason for memory problems would be huge
> changelog.xml files. An example case:
> - a changelist with > 40 files
> - results in a changelog.xml size > 110MB
> - Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
> Maybe there should be an option to limit the amount of files that p4 plugin
> reads to from changelists?
--
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-13109) Huge changelogs eat all the Java memory
[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161180#comment-161180
]
Tim Drury commented on JENKINS-13109:
-
Ok, I'll move my stack trace to a new issue and I'll update with OOM Error info
when/if it occurs again. Thanks again, Rob.
> Huge changelogs eat all the Java memory
> ---
>
> Key: JENKINS-13109
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Environment: Windows Server 2008 HPC Edition
> 64-bit JVM 1.6.0_29
> Running Jenkins service with "-Xrs -Xmx2048m
> -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar
> "%BASE%\jenkins.war" --httpPort=8080"
>Reporter: Mikko Tapaninen
>
> With really huge changelists the p4 plugin can run out of java heap space. At
> least it looks like the reason for memory problems would be huge
> changelog.xml files. An example case:
> - a changelist with > 40 files
> - results in a changelog.xml size > 110MB
> - Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
> Maybe there should be an option to limit the amount of files that p4 plugin
> reads to from changelists?
--
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-13331) After installing Jenkins from .deb pkg on Ubuntu in AWS, no plugins appears, and strange Java errors in logs.
Samuel Falvo II created JENKINS-13331: - Summary: After installing Jenkins from .deb pkg on Ubuntu in AWS, no plugins appears, and strange Java errors in logs. Key: JENKINS-13331 URL: https://issues.jenkins-ci.org/browse/JENKINS-13331 Project: Jenkins Issue Type: Bug Components: jenkins-plugin-runtime Environment: Ubuntu 11.10, 64-bit, running in an AWS EC2 instance. Reporter: Samuel Falvo II Assignee: Jørgen Tjernø Priority: Blocker 1. Create an AWS EC2 instance with 1.7GB of memory and a single CPU core. Use 64-bit Ubuntu Oneiric Ocelot AMI. Make sure the image has a security group allowing outside access to port 8080. 2. Follow instructions found at http://pkg.jenkins-ci.org/debian/ a) wget -q -O - http://pkg.jenkins-ci.org/debian/jenkins-ci.org.key | sudo apt-key add - b) Edit /etc/apt/sources.list and append: deb http://pkg.jenkins-ci.org/debian binary/ c) sudo apt-get update d) sudo apt-get install jenkins 3. Visit port 8080 of the new instance. Jenkins should come up. 4. Click on "Manage Jenkins" 5. Click on "Manage Plugins" 6. Click on the "Available" tab. Observe that no plugins appears. While researching this, I discovered errors in /var/log/jenkins/jenkins.log, to the effect of: SEVERE: Error while serving http://75.101.228.252:8080/updateCenter/byId/default/postBack 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 org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) 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:571) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485) 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 hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.j
[JIRA] (JENKINS-13333) Clicking test result links in IE8 when you have JavaScript debugging on produces an error.
alexlombardi created JENKINS-1: -- Summary: Clicking test result links in IE8 when you have JavaScript debugging on produces an error. Key: JENKINS-1 URL: https://issues.jenkins-ci.org/browse/JENKINS-1 Project: Jenkins Issue Type: Bug Components: jenkins-plugin-runtime Affects Versions: current Environment: Running Jenkins as a Windows Service on a server. Reporter: alexlombardi Assignee: Jørgen Tjernø Attachments: Error.doc When you dirll down to look at NUnit Test results for builds and JavaScript debugging is enabled in IE8 it produces an object not found error (see attached document). -- 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-13332) OutOfMemoryError from Perforce polling
[ https://issues.jenkins-ci.org/browse/JENKINS-13332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161181#comment-161181 ] Tim Drury commented on JENKINS-13332: - This issue started out here: https://issues.jenkins-ci.org/browse/JENKINS-13109 but Rob identified it as a separate issue so I created this Jira issue. > OutOfMemoryError from Perforce polling > -- > > Key: JENKINS-13332 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13332 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: Windows Server 2008, Jenkins 1.450, Perforce plugin > 1.3.7, Jenkins JVM 1.6.0_26 64-bit -Xmx=1280mb (at time of crash - it's been > increased); 1 master, 2 slaves, all SCM polling on master; See attached > jenkins-info.txt >Reporter: Tim Drury > Labels: outofmemoryerror, perforce, scm > Attachments: jenkins-info.txt > > > Our QA noticed no new builds for 2 days. When I checked the polling log of > one project it was: > Perforce Polling Log > Started on Apr 1, 2012 7:00:38 PM > Looking for changes... > Using master > Using master perforce client: jenkins_me-main > ERROR: Failed to record SCM polling > java.lang.OutOfMemoryError: Java heap space > I did not follow the Jenkins wiki process :(. If this happens again, I'll > use it to get more information. Here is the stack trace: > Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling > SEVERE: Failed to record SCM polling > java.lang.OutOfMemoryError: Java heap space > at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:78) > at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:66) > at > hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1323) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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) > We do keep Jenkins running without periodic reboots so I'm thinking there may > be a memory leak somewhere as well. -- 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-13332) OutOfMemoryError from Perforce polling
Tim Drury created JENKINS-13332: --- Summary: OutOfMemoryError from Perforce polling Key: JENKINS-13332 URL: https://issues.jenkins-ci.org/browse/JENKINS-13332 Project: Jenkins Issue Type: Bug Components: perforce Affects Versions: current Environment: Windows Server 2008, Jenkins 1.450, Perforce plugin 1.3.7, Jenkins JVM 1.6.0_26 64-bit -Xmx=1280mb (at time of crash - it's been increased); 1 master, 2 slaves, all SCM polling on master; See attached jenkins-info.txt Reporter: Tim Drury Attachments: jenkins-info.txt Our QA noticed no new builds for 2 days. When I checked the polling log of one project it was: Perforce Polling Log Started on Apr 1, 2012 7:00:38 PM Looking for changes... Using master Using master perforce client: jenkins_me-main ERROR: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space I did not follow the Jenkins wiki process :(. If this happens again, I'll use it to get more information. Here is the stack trace: Apr 1, 2012 7:48:48 PM hudson.triggers.SCMTrigger$Runner runPolling SEVERE: Failed to record SCM polling java.lang.OutOfMemoryError: Java heap space at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:78) at hudson.remoting.FastPipedInputStream.(FastPipedInputStream.java:66) at hudson.plugins.perforce.HudsonP4RemoteExecutor.exec(HudsonP4RemoteExecutor.java:97) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:321) at com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:54) at hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1208) at hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:903) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.poll(AbstractProject.java:1323) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) 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) We do keep Jenkins running without periodic reboots so I'm thinking there may be a memory leak somewhere as well. -- 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-10771) hudson.util.IOException2: remote file operation failed
[ https://issues.jenkins-ci.org/browse/JENKINS-10771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161182#comment-161182 ] Khai Do commented on JENKINS-10771: --- Hope my experience helps someone out there. I kept getting this same error due to my configuration. My configuration was a centos linux (ver 5.6) machine running jenkins (LTS 1.409) that would connect to a cloud storage service (amazon) to store all of its jobs. Once I removed the cloud storage and just put all of the data on the local machine I stopped getting this error. I believe the problem, never confirmed, was that access to the cloud storage was too slow and kept timing out. > hudson.util.IOException2: remote file operation failed > -- > > Key: JENKINS-10771 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10771 > Project: Jenkins > Issue Type: Bug > Components: master-slave >Affects Versions: current > Environment: node: Windows Server 2008 R2, amd64 - Intel64 Family 6 > Model 15 Stepping 1, GenuineIntel, jvm 1.6.0_25-b06 > master: AIX >Reporter: Thorsten Löber > > After upgrading jenkins from 1.415 to 1.426 we cannot build anymore any > project on our windows node. We get the exception: > Building remotely on WSJENKINSDEV01 > hudson.util.IOException2: remote file operation failed: d:\Program > Files\jenkins_slave\workspace\TASC Workbench at > hudson.remoting.Channel@4f854f85:WSJENKINSDEV01 > at hudson.FilePath.act(FilePath.java:754) > at hudson.FilePath.act(FilePath.java:740) > at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:731) > at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:676) > at hudson.model.AbstractProject.checkout(AbstractProject.java:1193) > at > hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:555) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:443) > at hudson.model.Run.run(Run.java:1376) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:230) > Caused by: java.io.IOException: Remote call on WSJENKINSDEV01 failed > at hudson.remoting.Channel.call(Channel.java:677) > at hudson.FilePath.act(FilePath.java:747) > ... 10 more > Caused by: java.lang.NoClassDefFoundError: Could not initialize class > hudson.model.Hudson > at > hudson.scm.SubversionWorkspaceSelector.syncWorkspaceFormatFromMaster(SubversionWorkspaceSelector.java:85) > at > hudson.scm.SubversionSCM.createSvnClientManager(SubversionSCM.java:808) > at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:751) > at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:738) > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1994) > 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(Unknown Source) > at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) > at java.util.concurrent.FutureTask.run(Unknown Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown > Source) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) > at hudson.remoting.Engine$1$1.run(Engine.java:60) > at java.lang.Thread.run(Unknown Source) > As soon as we rollback, we are able again to build the project. -- 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-13109) Huge changelogs eat all the Java memory
[
https://issues.jenkins-ci.org/browse/JENKINS-13109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161180#comment-161180
]
Tim Drury edited comment on JENKINS-13109 at 4/3/12 6:59 PM:
-
Ok, I'll move my stack trace to a new issue and I'll update with OOM Error info
when/if it occurs again. Thanks again, Rob.
Created this issue: https://issues.jenkins-ci.org/browse/JENKINS-13332
was (Author: timdrury):
Ok, I'll move my stack trace to a new issue and I'll update with OOM Error
info when/if it occurs again. Thanks again, Rob.
> Huge changelogs eat all the Java memory
> ---
>
> Key: JENKINS-13109
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13109
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
> Environment: Windows Server 2008 HPC Edition
> 64-bit JVM 1.6.0_29
> Running Jenkins service with "-Xrs -Xmx2048m
> -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar
> "%BASE%\jenkins.war" --httpPort=8080"
>Reporter: Mikko Tapaninen
>
> With really huge changelists the p4 plugin can run out of java heap space. At
> least it looks like the reason for memory problems would be huge
> changelog.xml files. An example case:
> - a changelist with > 40 files
> - results in a changelog.xml size > 110MB
> - Jenkins runs out of memory: {{java.lang.OutOfMemoryError: Java heap space}}
> Maybe there should be an option to limit the amount of files that p4 plugin
> reads to from changelists?
--
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-13130) Gradle Plugin - Gradle distribution URL has changed
[
https://issues.jenkins-ci.org/browse/JENKINS-13130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161183#comment-161183
]
William Kilian commented on JENKINS-13130:
--
Something updated in the jenkins plugin, but the update was incorrect. Our
jenkins instances were looking at
http://services.gradle.org/distributions/distributions/gradle-1.0-milestone-9-bin.zip
(which doesn't exist).
A search and replace for "distributions/distributions" with "distributions" in
{{updates/hudson.plugins.gradle.GradleInstaller}} resolved things for us.
> Gradle Plugin - Gradle distribution URL has changed
> ---
>
> Key: JENKINS-13130
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13130
> Project: Jenkins
> Issue Type: Task
> Components: gradle
>Affects Versions: current
>Reporter: Glen Conboy
>Assignee: gbois
>Priority: Minor
>
> The lastest Gradle distribution (1.0 milestone 9) cannot be selected in the
> "Install from Gradle.org" drop down list.
>
> I would guess that this is because the Gradle distrubition URL has changed
> from http://repo.gradle.org/gradle/distributions to
> http://services.gradle.org/distributions . See the Gradle release note
> http://wiki.gradle.org/display/GRADLE/Gradle+1.0-milestone-8+Migration+Guide#Gradle1.0-milestone-8MigrationGuide-NewURLfordownloadingGradledistributions
> .
--
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-10771) hudson.util.IOException2: remote file operation failed
[ https://issues.jenkins-ci.org/browse/JENKINS-10771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161184#comment-161184 ] peter_schuetze commented on JENKINS-10771: -- I had a similar issue today. (Windows Master, AIX client) AND we found the solution. The temp folder was full. After cleaning up the temp folder. Everything worked fine again. 07:49:33 Building remotely on devocnswasa 07:50:09 hudson.util.IOException2: remote file operation failed: /jenkins/Hudson/cmicci/workspace/OCNS_Deploy2WAS at hudson.remoting.Channel@6499fc:devocnswasa 07:50:09at hudson.FilePath.act(FilePath.java:779) 07:50:09at hudson.FilePath.act(FilePath.java:765) 07:50:09at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743) 07:50:09at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685) 07:50:09at hudson.model.AbstractProject.checkout(AbstractProject.java:1195) 07:50:09at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:573) 07:50:09at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:462) 07:50:09at hudson.model.Run.run(Run.java:1404) 07:50:09at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) 07:50:09at hudson.model.ResourceController.execute(ResourceController.java:88) 07:50:09at hudson.model.Executor.run(Executor.java:238) 07:50:09 Caused by: java.io.IOException: Remote call on devocnswasa failed 07:50:09at hudson.remoting.Channel.call(Channel.java:690) 07:50:09at hudson.FilePath.act(FilePath.java:772) 07:50:09... 10 more 07:50:09 Caused by: java.lang.Error: Unable to load resource hudson/model/Messages.properties 07:50:09at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:202) 07:50:09at java.lang.ClassLoader.getResource(ClassLoader.java:431) 07:50:09at java.lang.Class.getResource(Class.java:1170) 07:50:09at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:83) 07:50:09at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102) 07:50:09at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102) 07:50:09at org.jvnet.localizer.ResourceBundleHolder.format(ResourceBundleHolder.java:139) 07:50:09at hudson.model.Messages.Node_Mode_NORMAL(Messages.java:1685) 07:50:09at hudson.model.Node$Mode.(Node.java:432) 07:50:09at java.lang.J9VMInternals.initializeImpl(Native Method) 07:50:09at java.lang.J9VMInternals.initialize(J9VMInternals.java:196) 07:50:09at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 07:50:09at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) 07:50:09at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 07:50:09at java.lang.reflect.Method.invoke(Method.java:618) 07:50:09at java.lang.Class.getEnumConstants(Class.java:1755) 07:50:09at jenkins.model.Jenkins.(Jenkins.java:3662) 07:50:09at java.lang.J9VMInternals.initializeImpl(Native Method) 07:50:09at java.lang.J9VMInternals.initialize(J9VMInternals.java:196) 07:50:09at java.lang.J9VMInternals.initialize(J9VMInternals.java:161) 07:50:09at hudson.scm.SubversionWorkspaceSelector.syncWorkspaceFormatFromMaster(SubversionWorkspaceSelector.java:85) 07:50:09at hudson.scm.SubversionSCM.createSvnClientManager(SubversionSCM.java:823) 07:50:09at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:766) 07:50:09at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753) 07:50:09at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2030) 07:50:09at hudson.remoting.UserRequest.perform(UserRequest.java:118) 07:50:09at hudson.remoting.UserRequest.perform(UserRequest.java:48) 07:50:09at hudson.remoting.Request$2.run(Request.java:287) 07:50:09at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:432) 07:50:09at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:284) 07:50:09at java.util.concurrent.FutureTask.run(FutureTask.java:138) 07:50:09at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:678) 07:50:09at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:703) 07:50:09at java.lang.Thread.run(Thread.java:811) 07:50:09 Caused by: java.io.IOException: There is not enough space in the file system. 07:50:09at java.io.FileOutputStream.write(FileOutputStream.java:277) 07:50:09at hudson.remoting.RemoteClassLoader.makeResource(RemoteClassLoader.java:271) 07:50:09at hudson.remoting.RemoteClassLoader.findResource(RemoteClassLoader.java:198) 07:50:09... 33
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161178#comment-161178 ] Rob Petti edited comment on JENKINS-13270 at 4/3/12 7:53 PM: - FYI, P4PASSWD is supposed to be the plain text password. That's why there is a seperate option to enable it in the environment. In recent versions of the perforce plugin. P4TICKET is set to the ticket obtained upon login, so you can use that instead of the plaintext password if you so desire. was (Author: rpetti): FYI, P4PASSWD is supposed to be the plain text password. That's why there is a seperate option to enable it in the environment. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.Process
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161185#comment-161185 ] lestin commented on JENKINS-13270: -- Hi Rob, I'm using 1.3.12 for the perforce plugin with 1.458 Jenkins. I noticed that within the plugin when it's trying to poke perforce, it's using the hash version of P4PASSWD. So if the plugin can give that out, that should solve my problem. How is the new p4ticket supposed to work? Do i need to do special setup? where is the ticket file saved? Thanks Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launche
[JIRA] (JENKINS-13136) Environment Variable Injection injecting (and overriding) unwanted variables (ie JAVA_HOME)
[ https://issues.jenkins-ci.org/browse/JENKINS-13136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] gbois closed JENKINS-13136. --- Resolution: Cannot Reproduce > Environment Variable Injection injecting (and overriding) unwanted variables > (ie JAVA_HOME) > --- > > Key: JENKINS-13136 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13136 > Project: Jenkins > Issue Type: Bug > Components: envinject >Affects Versions: current > Environment: Jenkins Master: 1.432, hosted on a centos5.3, 32-bit > Slave Node: Windows XP > EnvInject: 1.38 >Reporter: Alex Gray >Assignee: gbois > Attachments: EnvInjectData.zip > > > We were using EnvInject 1.35 in various free-style jobs, but after we > upgraded to 1.36 jobs started failing. > This is the reason: > 1) On the slave node (in this case, a windows XP slave node) JAVA_HOME is > pointing to version 1.25. I can verify this by going to Jenkins->Manage > Jenkins->Manage Nodes->MyWinXPNode->"view log", and sure enough the node's > environment variables have JAVA_HOME pointing to 1.25 > 2) After upgraded to EnvInject 1.36, the jobs started failing because > JAVA_HOME has been overwritten to 1.27, which does not exist on the node. In > fact, I don't know where this is being set because the master does not have > java 1.27 either! > The only option that is is present in the job is this: > Inject environment variables to the build process > Properties Content: > TEMP=c:\\windows\\temp > TMP=c:\\windows\\temp > (everything else under "Inject Environment Variables" is blank. > I have not tried the latest version, 1.38, but I will, since all the jobs are > currently broken and I have nothing else to lose... > If it doesn't fix it, then the workaround is to go to EnvInject 1.35, but > that does not work on multiconfiguration jobs. > I'll keep you posted. If this is fixed in 1.38, I will update this Jira. -- 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 ] Work on JENKINS-13325 started by gbois. > 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 > > 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:comment-tabpanel&focusedCommentId=161186#comment-161186 ] gbois commented on JENKINS-13325: - Please attach your job configuration file ($JENKINS_HOME/jobs/config.xml0 and your 'BuildFingerprint.txt' file. I'll look at it. > 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 > > 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-13305) typing within a selector should be for anywhere in the selector item name
[ https://issues.jenkins-ci.org/browse/JENKINS-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161187#comment-161187 ] SCM/JIRA link daemon commented on JENKINS-13305: Code changed in jenkins User: Jesse Farinacci Path: src/main/webapp/js/keyboard-shortcuts.js http://jenkins-ci.org/commit/keyboard-shortcuts-plugin/ce2e4ad3f860b5941abf05952440859ed17a5d69 Log: [FIXED JENKINS-13305] typing within a selector should be for anywhere in the selector item name Compare: https://github.com/jenkinsci/keyboard-shortcuts-plugin/compare/4346a5a...ce2e4ad > typing within a selector should be for anywhere in the selector item name > - > > Key: JENKINS-13305 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13305 > Project: Jenkins > Issue Type: Improvement > Components: keyboard-shortcuts >Reporter: jieryn >Assignee: jieryn >Priority: Minor > -- 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-13305) typing within a selector should be for anywhere in the selector item name
[ https://issues.jenkins-ci.org/browse/JENKINS-13305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-13305. Resolution: Fixed > typing within a selector should be for anywhere in the selector item name > - > > Key: JENKINS-13305 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13305 > Project: Jenkins > Issue Type: Improvement > Components: keyboard-shortcuts >Reporter: jieryn >Assignee: jieryn >Priority: Minor > -- 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-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161188#comment-161188 ] Jay Beeckman commented on JENKINS-11381: Any update on this? It appears that SVNKIT has updated their stuff? An ETA would be great. > Subversion Plugin does not support Subversion 1.7 > - > > Key: JENKINS-11381 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 > Project: Jenkins > Issue Type: Improvement > Components: subversion >Reporter: soundworker >Priority: Blocker > -- 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-11381) Subversion Plugin does not support Subversion 1.7
[ https://issues.jenkins-ci.org/browse/JENKINS-11381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161189#comment-161189 ] Milutin Jovanovic commented on JENKINS-11381: - I am not the maintainer, but interested in this... SVNKit is still in release candidate stage, so I don't think svn plugin will be updated until SVNKit is fully released. > Subversion Plugin does not support Subversion 1.7 > - > > Key: JENKINS-11381 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11381 > Project: Jenkins > Issue Type: Improvement > Components: subversion >Reporter: soundworker >Priority: Blocker > -- 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-13270) Occasional login failures using p4 ticket
[
https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161190#comment-161190
]
Rob Petti commented on JENKINS-13270:
-
It doesn't save a ticket file.
P4TICKETS is the location of the ticket file as used by the perforce client.
P4TICKET is the actual value of the ticket as obtained by the perforce plugin
from perforce on login, and can be used in place of the password, ie "p4
-P${P4TICKET} sync -f ..."
> Occasional login failures using p4 ticket
> -
>
> Key: JENKINS-13270
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13270
> Project: Jenkins
> Issue Type: Bug
> Components: perforce
>Affects Versions: current
> Environment: 1.456 Jenkins with latest perforce plugin
>Reporter: lestin
>Assignee: Rob Petti
>Priority: Minor
>
> Saw the following log whilst nothing has changed during the period:
>
> INFO: job_name_here #4437 main build action completed: SUCCESS
> Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:01:18 AM hudson.model.Run run
> INFO: job_name_here #4438 main build action completed: SUCCESS
> Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Using p4 issued ticket.
> Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login
> attempt failed: Password invalid.
> Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate
> login
> WARNING: Attempt to workaround p4 executable location failed
> com.tek42.perforce.PerforceException: Could not run perforce command.
> at
> hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372)
> at
> com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292)
> at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61)
> at
> hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325)
> at
> hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019)
> at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356)
> at hudson.scm.SCM.poll(SCM.java:373)
> at hudson.model.AbstractProject.poll(AbstractProject.java:1340)
> at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420)
> at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449)
> at
> hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
> 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.io.IOException: Cannot run program "/usr/bin/p4" (in
> directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No
> such file or directory
> at java.lang.ProcessBuilder.start(ProcessBuilder.java:460)
> at hudson.Proc$LocalProc.(Proc.java:244)
> at hudson.Proc$LocalProc.(Proc.java:216)
> at hudson.Launcher$LocalLauncher.launch(Launcher.java:707)
> at hudson.Launcher$ProcS
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161191#comment-161191 ] lestin commented on JENKINS-13270: -- Hi Rob, Thanks for the update, it does feel like that P4TICKET is the P4PASSWD i need to use in my command line. Can you tell me how to export the P4TICKET variable then? I tried to set the environment varialbe as well as echo $P4TICKET, all referered to null variables. Thanks. Lestin > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStart
[JIRA] (JENKINS-13270) Occasional login failures using p4 ticket
[ https://issues.jenkins-ci.org/browse/JENKINS-13270?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161192#comment-161192 ] Rob Petti commented on JENKINS-13270: - It's set automatically by the perforce plugin when you check the 'expose P4PASSWD' option. > Occasional login failures using p4 ticket > - > > Key: JENKINS-13270 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13270 > Project: Jenkins > Issue Type: Bug > Components: perforce >Affects Versions: current > Environment: 1.456 Jenkins with latest perforce plugin >Reporter: lestin >Assignee: Rob Petti >Priority: Minor > > Saw the following log whilst nothing has changed during the period: > > INFO: job_name_here #4437 main build action completed: SUCCESS > Mar 27, 2012 6:11:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:31:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:41:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 6:51:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:01:18 AM hudson.model.Run run > INFO: job_name_here #4438 main build action completed: SUCCESS > Mar 27, 2012 7:11:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:21:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:31:10 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Using p4 issued ticket. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Login with '/tools/perforce/2010.1/bin.linux26x86/p4' failed: Login > attempt failed: Password invalid. > Mar 27, 2012 7:43:09 AM com.tek42.perforce.parse.AbstractPerforceTemplate > login > WARNING: Attempt to workaround p4 executable location failed > com.tek42.perforce.PerforceException: Could not run perforce command. > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:88) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.p4Login(AbstractPerforceTemplate.java:596) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.login(AbstractPerforceTemplate.java:566) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:372) > at > com.tek42.perforce.parse.AbstractPerforceTemplate.getPerforceResponse(AbstractPerforceTemplate.java:292) > at com.tek42.perforce.parse.Workspaces.getWorkspace(Workspaces.java:61) > at > hudson.plugins.perforce.PerforceSCM.getPerforceWorkspace(PerforceSCM.java:1325) > at > hudson.plugins.perforce.PerforceSCM.compareRemoteRevisionWith(PerforceSCM.java:1019) > at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) > at hudson.scm.SCM.poll(SCM.java:373) > at hudson.model.AbstractProject.poll(AbstractProject.java:1340) > at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) > at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) > at > hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) > 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.io.IOException: Cannot run program "/usr/bin/p4" (in > directory "/projects/jenkins/jenkins_home"): java.io.IOException: error=2, No > such file or directory > at java.lang.ProcessBuilder.start(ProcessBuilder.java:460) > at hudson.Proc$LocalProc.(Proc.java:244) > at hudson.Proc$LocalProc.(Proc.java:216) > at hudson.Launcher$LocalLauncher.launch(Launcher.java:707) > at hudson.Launcher$ProcStarter.start(Launcher.java:338) > at > hudson.plugins.perforce.HudsonP4DefaultExecutor.exec(HudsonP4DefaultExecutor.java:79) > ... 19 more > Caused by: java.io.IOException: java.io.IOE
[JIRA] (JENKINS-13051) Setting branch name prevents branch from building
[ https://issues.jenkins-ci.org/browse/JENKINS-13051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161193#comment-161193 ] Steve Kluth commented on JENKINS-13051: --- +1: Server 2008 R2, x64, Git-1.7.9-preview20120201, Jenkins 1.458. Rollback to 1.1.15 fixed for me as well. > Setting branch name prevents branch from building > - > > Key: JENKINS-13051 > URL: https://issues.jenkins-ci.org/browse/JENKINS-13051 > Project: Jenkins > Issue Type: Bug > Components: git > Environment: Windows Server 2008 R2, Jenkins 1.454, Git Plugin > 1.1.16, Git version 1.7.9-preview20120201 >Reporter: Adam Westhusing >Assignee: Nicolas De Loof >Priority: Critical > Labels: git, plugin, windows > > It appears a bug has been introduced in Git plugin 1.1.16: > If I set the branch specifier in the "Branches to Build" section, I always > get the following error. > ERROR: Couldn't find any revision to build. Verify the repository and branch > configuration for this job. > The only way I found to resolve this is to get rid of the branch specifier > and replace it with **. However, I only want to build a specific branch in > our Git repo, so in the meantime I've rolled back to 1.1.15 where this > functionality is working just fine. -- 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
