[JIRA] (JENKINS-12687) Incorrect redirect back to job/project
Dimaq Q created JENKINS-12687: - Summary: Incorrect redirect back to job/project Key: JENKINS-12687 URL: https://issues.jenkins-ci.org/browse/JENKINS-12687 Project: Jenkins Issue Type: Bug Components: htmlpublisher Affects Versions: current Environment: jenkins runs on host dev port 8014, apache mod_proxy frontend forwards traffic from dev/jenkins to dev:8014/jenkins eventually I want to make my jenkins public (perhaps password-protected, accessible from anywhere in the world), where dev.myhost.domain/jenkins traffic would be forwarded to dev:8014/jenkins. Reporter: Dimaq Q Assignee: mcrooney Priority: Minor all links in jenkins work correctly; most links in htmlpublisher work correctly; however back to gives me dev:8014/jenkins/jobs/ instead of dev/jenkins/job/ this breaks public accessibility of jenkins, as port 8014 is not publicly visible. -- 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-12688) Build hangs on Windows 2008 x64 slave
Costin Caraivan created JENKINS-12688: - Summary: Build hangs on Windows 2008 x64 slave Key: JENKINS-12688 URL: https://issues.jenkins-ci.org/browse/JENKINS-12688 Project: Jenkins Issue Type: Bug Components: core Affects Versions: current Environment: Master - Windows 2008 x64, Java 1.6.0_29 Slave - Windows 2008 x64 service (also tried JNLP), Java 1.6.0._29 Reporter: Costin Caraivan Priority: Critical We have some integration tests launched from freestyle jobs. They are MSBuild projects which launch Nunit tests. The main build steps run ok and are over in ~17-18 minutes. However, the build hangs at the end - where the communication with the master is supposed to happen (for example when publishing the reports, or when sending the email notification). I've removed the email notification and the Nunit report publishing, and the build still hangs: "Time Elapsed 00:16:10.09 Build step 'Build a Visual Studio project or solution using MSBuild.' marked build as failure"). We've had build hanging for as much as 11 hours (!). I've tried different connection settings: Windows service, JNLP - nothing helps. I'll attach the server & slave dumps. -- 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-12688) Build hangs on Windows 2008 x64 slave
[ https://issues.jenkins-ci.org/browse/JENKINS-12688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Costin Caraivan updated JENKINS-12688: -- Attachment: huskar-sysinfo.txt Priority: Blocker (was: Critical) > Build hangs on Windows 2008 x64 slave > - > > Key: JENKINS-12688 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12688 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Master - Windows 2008 x64, Java 1.6.0_29 > Slave - Windows 2008 x64 service (also tried JNLP), Java 1.6.0._29 >Reporter: Costin Caraivan >Priority: Blocker > Attachments: huskar-sysinfo.txt > > > We have some integration tests launched from freestyle jobs. They are MSBuild > projects which launch Nunit tests. > The main build steps run ok and are over in ~17-18 minutes. However, the > build hangs at the end - where the communication with the master is supposed > to happen (for example when publishing the reports, or when sending the email > notification). I've removed the email notification and the Nunit report > publishing, and the build still hangs: > "Time Elapsed 00:16:10.09 > Build step 'Build a Visual Studio project or solution using MSBuild.' marked > build as failure"). > We've had build hanging for as much as 11 hours (!). > I've tried different connection settings: Windows service, JNLP - nothing > helps. > I'll attach the server & slave dumps. -- 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-12688) Build hangs on Windows 2008 x64 slave
[ https://issues.jenkins-ci.org/browse/JENKINS-12688?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Costin Caraivan updated JENKINS-12688: -- Environment: Jenkins 1.437 Master - Windows 2008 x64, Java 1.6.0_29 Slave - Windows 2008 x64 service (also tried JNLP), Java 1.6.0._29 was: Master - Windows 2008 x64, Java 1.6.0_29 Slave - Windows 2008 x64 service (also tried JNLP), Java 1.6.0._29 Description: We have some integration tests launched from freestyle jobs. They are MSBuild projects which launch Nunit tests. The main build steps run ok and are over in ~17-18 minutes. However, the build hangs at the end - where the communication with the master is supposed to happen (for example when publishing the reports, or when sending the email notification). I've removed the email notification and the Nunit report publishing, and the build still hangs: "Time Elapsed 00:16:10.09 Build step 'Build a Visual Studio project or solution using MSBuild.' marked build as failure"). We've had build hanging for as much as 11 hours (!). I've tried different connection settings: Windows service, JNLP - nothing helps. I'll attach the server & slave dumps. If there are any fixes for this, that I missed in the recent changelogs, I'll update Jenkins. But I don't see any possible fixes for this problem. was: We have some integration tests launched from freestyle jobs. They are MSBuild projects which launch Nunit tests. The main build steps run ok and are over in ~17-18 minutes. However, the build hangs at the end - where the communication with the master is supposed to happen (for example when publishing the reports, or when sending the email notification). I've removed the email notification and the Nunit report publishing, and the build still hangs: "Time Elapsed 00:16:10.09 Build step 'Build a Visual Studio project or solution using MSBuild.' marked build as failure"). We've had build hanging for as much as 11 hours (!). I've tried different connection settings: Windows service, JNLP - nothing helps. I'll attach the server & slave dumps. > Build hangs on Windows 2008 x64 slave > - > > Key: JENKINS-12688 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12688 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Jenkins 1.437 > Master - Windows 2008 x64, Java 1.6.0_29 > Slave - Windows 2008 x64 service (also tried JNLP), Java 1.6.0._29 >Reporter: Costin Caraivan >Priority: Blocker > Attachments: huskar-sysinfo.txt > > > We have some integration tests launched from freestyle jobs. They are MSBuild > projects which launch Nunit tests. > The main build steps run ok and are over in ~17-18 minutes. However, the > build hangs at the end - where the communication with the master is supposed > to happen (for example when publishing the reports, or when sending the email > notification). I've removed the email notification and the Nunit report > publishing, and the build still hangs: > "Time Elapsed 00:16:10.09 > Build step 'Build a Visual Studio project or solution using MSBuild.' marked > build as failure"). > We've had build hanging for as much as 11 hours (!). > I've tried different connection settings: Windows service, JNLP - nothing > helps. > I'll attach the server & slave dumps. > If there are any fixes for this, that I missed in the recent changelogs, I'll > update Jenkins. But I don't see any possible fixes for this problem. -- 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-12113) Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section
[ https://issues.jenkins-ci.org/browse/JENKINS-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158803#comment-158803 ] kutzi commented on JENKINS-12113: - Still need to write some unit tests and ask other devs if it's okay to do a release now. Hope to have it this weekend or beginning of next week. > Maven - java.io.IOException: error=2, No such file or directory if in SVN > configuration parameters used in Local module directory section > - > > Key: JENKINS-12113 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12113 > Project: Jenkins > Issue Type: Bug > Components: core, maven, maven2, parameters, subversion > Environment: Jenkins 1.448 > Subversion Plugin 1.37 > Maven Integration Plugin 1.448 > Ant 1.1 >Reporter: Oleksandr Popov >Assignee: kutzi > Attachments: subversion.hpi, svn_maven_issue_01.PNG, > svn_maven_issue_02.PNG > > > Maven is unable to work if in Subversion configuration parameters are used in > Local module directory section. > As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in > Local module directory section. And when I run it - Maven failed > (svn_maven_issue_02.PNG) with java.io.IOException. -- 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-12689) There is a problem with the website's security certificate.
Joop van Bussel created JENKINS-12689: - Summary: There is a problem with the website's security certificate. Key: JENKINS-12689 URL: https://issues.jenkins-ci.org/browse/JENKINS-12689 Project: Jenkins Issue Type: Bug Components: update-center Environment: LTS 1.424.2 Reporter: Joop van Bussel The certicate begin https://updates.jenkins-ci.org/stable/update-center.json?version=1.424.2 was expired on februari 2th 2012. Please update the certificate E.g. new installation do not show any available plugins 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-12689) There is a problem with the website's security certificate.
[ https://issues.jenkins-ci.org/browse/JENKINS-12689?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joop van Bussel updated JENKINS-12689: -- Description: The certicate begin https://updates.jenkins-ci.org/stable/update-center.json?version=1.424.2 was expired on februari 2th 2012 and/or the root certificate is not trusted. Please update the certificate E.g. new installation do not show any available plugins anymore. was: The certicate begin https://updates.jenkins-ci.org/stable/update-center.json?version=1.424.2 was expired on februari 2th 2012. Please update the certificate E.g. new installation do not show any available plugins anymore. > There is a problem with the website's security certificate. > --- > > Key: JENKINS-12689 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12689 > Project: Jenkins > Issue Type: Bug > Components: update-center > Environment: LTS 1.424.2 >Reporter: Joop van Bussel > > The certicate begin > https://updates.jenkins-ci.org/stable/update-center.json?version=1.424.2 was > expired on februari 2th 2012 and/or the root certificate is not trusted. > Please update the certificate > E.g. new installation do not show any available plugins 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-12113) Maven - java.io.IOException: error=2, No such file or directory if in SVN configuration parameters used in Local module directory section
[ https://issues.jenkins-ci.org/browse/JENKINS-12113?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158804#comment-158804 ] Oleksandr Popov commented on JENKINS-12113: --- Great news! Hope so ;) > Maven - java.io.IOException: error=2, No such file or directory if in SVN > configuration parameters used in Local module directory section > - > > Key: JENKINS-12113 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12113 > Project: Jenkins > Issue Type: Bug > Components: core, maven, maven2, parameters, subversion > Environment: Jenkins 1.448 > Subversion Plugin 1.37 > Maven Integration Plugin 1.448 > Ant 1.1 >Reporter: Oleksandr Popov >Assignee: kutzi > Attachments: subversion.hpi, svn_maven_issue_01.PNG, > svn_maven_issue_02.PNG > > > Maven is unable to work if in Subversion configuration parameters are used in > Local module directory section. > As you can see in svn_maven_issue_01.PNG Ive specified predefined variable in > Local module directory section. And when I run it - Maven failed > (svn_maven_issue_02.PNG) with java.io.IOException. -- 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-12583) update for cvs plugin to 2.0 doesn't work
[ https://issues.jenkins-ci.org/browse/JENKINS-12583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158805#comment-158805 ] Alex Lehmann commented on JENKINS-12583: Are you sure that you have the plugin pinnned? I have the following files in the jenkins/plugins dir: cvs cvs.jpi cvs.jpi.pinned if that is the case, the main jenkins should update the plugin to the old version anymore in 1.450 it is supposed to be fixed, but I haven't tried that yet. > update for cvs plugin to 2.0 doesn't work > - > > Key: JENKINS-12583 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12583 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: jenkins 1.449, cvs plugin 1.6 >Reporter: Alex Lehmann > Fix For: current > > > I tried to update to the cvs plugin 2.0 today but this doesn't work, I assume > there is a name problem due to the extension *.jpi on the new plugin. > Before update, the file is called cvs.hpi, the update process creates a new > file cvs.jpi that is ignored with the following message: > Jan 30, 2012 5:04:26 PM hudson.PluginManager$1$3$1 isDuplicate > INFO: Ignoring /home/lehmann/.jenkins/plugins/cvs.jpi because > /home/lehmann/.jenkins/plugins/cvs.hpi is already loaded > I assume it may work if it were the other way around. > The version displayed by the plugin page remains 1.6 but there are a few > exceptions in the log about missing classes like this > java.lang.NoClassDefFoundError: org/netbeans/lib/cvsclient/admin/AdminHandler > these classes are included in the cvs.jpi zip but that is not used. > I was able to fix the update manually by copying cvs.jpi to cvs.hpi, which > resulted in a pinned plugin 2.0, but the automatic process has to be fixed > somehow. -- 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-12663) Mantis plugin does not detect change.
[ https://issues.jenkins-ci.org/browse/JENKINS-12663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158806#comment-158806 ] Jan Goyvaerts commented on JENKINS-12663: - That's it indeed. I assumed the # sign was part of %ID% since it wasn't explicitly set in the tutorial. Now I see it's updating the ticket ! :-) However, shouldn't the names of the changed files be listed in the ticket note ? I'm just getting "integrated into :" with a url. Which leads me to the build of Jenkins. > Mantis plugin does not detect change. > - > > Key: JENKINS-12663 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12663 > Project: Jenkins > Issue Type: Bug > Components: mantis >Reporter: Jan Goyvaerts >Assignee: sogabe > Labels: plugin > Attachments: build_console_output.png, mantis_project_config.png, > project_changes.png > > > I've configured Jenkins according to > https://wiki.jenkins-ci.org/display/JENKINS/Mantis+Plugin. But i can't have > the tickets updated. > I'm getting this in the console output: [MANTIS] No issues have been found in > the changelog. > For the very same build I have these changes: "Fix issue #0010038." > The Mantis configuration is set to "[ISSUE %ID%]". As indicated in the > plugin's tutorial. > Is this a known issue ? -- 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-12683) Crowd 2 plugin authenticates, but doesn't allow login
[ https://issues.jenkins-ci.org/browse/JENKINS-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158807#comment-158807 ] Thorsten Heit commented on JENKINS-12683: - Hi, a couple of questions to isolate the problem: - What kind of browser do you use? - Do you have something like a cookie manager installed that accidentally blocks cookies? - Do you have another application from Atlassian such as Confluence, JIRA etc., that uses your Crowd server for user management in combination with SSO? If yes, what happens when you log in in that application and then open up Jenkins in the same browser? - Does the user belong to the user group you have specified in Jenkins >> Manage Jenkins >> Configure System, Security Realm => Crowd 2? - Is the user marked as active in your Crowd server? I'm also using Jenkins 1.450 and Crowd 2.4, but on Solaris 11 as OS. Everything works fine here... Best regards Thorsten > Crowd 2 plugin authenticates, but doesn't allow login > - > > Key: JENKINS-12683 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12683 > Project: Jenkins > Issue Type: Bug > Components: crowd2 >Affects Versions: current > Environment: x64 Windows 7 >Reporter: Dan Busha >Assignee: Thorsten Heit >Priority: Critical > Labels: plugin, windows > > I have an installation of Jenkins 1.450 with the Crowd 2 plugin v1.4 > installed connecting to a Crowd v2.4.0 server which successfully > authenticates users (according to the log). When a user enters their username > and password and clicks 'log in' they are returned to the main Jenkins page > but are not logged in. -- 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-12690) JenkinsTrigger does not understand SSH Key with a password
Tim Baverstock created JENKINS-12690: Summary: JenkinsTrigger does not understand SSH Key with a password Key: JENKINS-12690 URL: https://issues.jenkins-ci.org/browse/JENKINS-12690 Project: Jenkins Issue Type: Bug Components: gerrit-trigger Environment: Linux dt-000886 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Jenkins ver. 1.450 Gerrit Trigger 2.3.1 Reporter: Tim Baverstock Assignee: rsandell Attachments: id_rsa, id_rsa, id_rsa.pub, id_rsa.pub I can only get Jenkins to talk to Gerrit's SSH connection if the key file has no password. 1. Use ssh-keygen to create a key with a password 2. Configure Gerrit Trigger with that key and its password 3. Test Connection > Bad SSH keyfile or password Jenkins.log: > 09-Feb-2012 12:43:18 com.sshtools.j2ssh.transport.publickey.SshPrivateKeyFile > parse > INFO: Parsing private key file > 09-Feb-2012 12:43:18 com.sshtools.j2ssh.transport.publickey.SshPrivateKeyFile > parse > INFO: Private key is not in the default format, attempting parse with other > supported formats 4. Clear the password: ssh-keygen -f .ssh/id_rsa -p -N '' Note that the Proc-Type and DEK-Info headers have gone. 5. Test connection (without clearing the password!) 6. Succeeds. Log still complains about non-default format. 7. Clear the password in Jenkins. 8. Test connection 9. Still succeeds, Log still complains about non-default format. This took me ages to nail down because supplying a password to a no-password key file doesn't fail. -- 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-11029) FATAL: Unable to produce a script file
[ https://issues.jenkins-ci.org/browse/JENKINS-11029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158808#comment-158808 ] Abhijit Shinde commented on JENKINS-11029: -- We get similar error after completion of successful build in Jenkins 1.445 using JDK jdk1.6.0_26. Then we have save output scripts which has below periodic failure. FATAL: null java.lang.NullPointerException at hudson.tasks.CommandInterpreter.createScriptFile(CommandInterpreter.java:104) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) at hudson.model.Build$RunnerImpl.build(Build.java:178) at hudson.model.Build$RunnerImpl.doRun(Build.java:139) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:465) at hudson.model.Run.run(Run.java:1404) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) > FATAL: Unable to produce a script file > -- > > Key: JENKINS-11029 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11029 > Project: Jenkins > Issue Type: Bug > Components: maven2 > Environment: Env #1 > OS : RHEL 5.5 32 bit > Jenkins : 1.429 > Java Used : Sunjdk > Env #2 > OS: Mac OS X 10.6.8 > Jenkins: 1.450 > Java: 1.6.0_29 >Reporter: Pushkaraj P > > We get this failure in our build ( This is just after checkout , so not sure > if checkout and this is related > FATAL: Unable to produce a script file > hudson.util.IOException2: Failed to create a temp file on > /home/hudson/jobs/VMCTrunk/workspace > at hudson.FilePath.createTextTempFile(FilePath.java:966) > at > hudson.tasks.CommandInterpreter.createScriptFile(CommandInterpreter.java:104) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) > at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:58) > at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:693) > at hudson.model.Build$RunnerImpl.build(Build.java:178) > at hudson.model.Build$RunnerImpl.doRun(Build.java:139) > at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:459) > 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: hudson.util.IOException2: Failed to create a temporary directory > in /tmp > at hudson.FilePath$12.invoke(FilePath.java:955) > at hudson.FilePath$12.invoke(FilePath.java:944) > at hudson.FilePath.act(FilePath.java:758) > at hudson.FilePath.act(FilePath.java:740) > at hudson.FilePath.createTextTempFile(FilePath.java:944) > ... 12 more > Caused by: java.io.IOException: No such file or directory > at java.io.UnixFileSystem.createFileExclusively(Native Method) > at java.io.File.checkAndCreate(File.java:1704) > at java.io.File.createTempFile(File.java:1792) > at hudson.FilePath$12.invoke(FilePath.java:953) > ... 16 more -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12691) Property variable not set if using a property file
Bruno L created JENKINS-12691:
-
Summary: Property variable not set if using a property file
Key: JENKINS-12691
URL: https://issues.jenkins-ci.org/browse/JENKINS-12691
Project: Jenkins
Issue Type: Bug
Components: envinject
Affects Versions: current
Environment: Linux (RedHat), Jenkinx 1.446, EnvInject 1.17
Reporter: Bruno L
Assignee: gbois
I am trying to inject environment variables to the build process after SCM
checkout. If I point to a .properties file in the workspace some variables do
not get set properly while others are OK. If I copy/paste the content of the
file into the "Properties Content" box in the Jenkins project configuration
page then it works fine for all variables.
For example
AVARIABLE=/some/path
PATH=/opt/bin:${AVARIABLE}/bin:${PATH}
LD_LIBRARY_PATH=${AVARIABLE}/lib:${LD_LIBRARY_PATH}
where I already have some existing directories in my $PATH. If I save this in a
file and point to it then I get errors :
[EnvInject] - Variables injected successfully.
[EnvInject] - Unset unresolved 'PATH' variable.
[EnvInject] - Unset unresolved 'LD_LIBRARY_PATH' variable.
But the same 3 lines work fine if I enter them directly in the "Properties
Content" dialog box
--
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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
[
https://issues.jenkins-ci.org/browse/JENKINS-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158809#comment-158809
]
Stéphane Van Espen commented on JENKINS-10502:
--
+1. This feature would be very useful.
> Add an option to make archiving the artifacts non-fatal if they don't exist
> ---
>
> Key: JENKINS-10502
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10502
> Project: Jenkins
> Issue Type: Improvement
> Components: core
> Environment: Jenkins 1.421
>Reporter: Thomas Fields
>
> If you tick the box to enable "Archive the artifacts", populate the "Files to
> archive", and your build fails to output those artifacts it will fail with
> something like this:
> {code}
> 12:11:51 Archiving artifacts
> 12:11:51 ERROR: No artifacts found that match the file pattern
> "tfields/Live/Engine/Tools/Layout.*". Configuration error?
> 12:11:57 ERROR: 'tfields/Live/Engine/Tools/Layout.*' doesn't match anything:
> 'tfields' exists but not 'tfields/Live/Engine/Tools/Layout.*'
> 12:11:57 Build step 'Archive the artifacts' changed build result to FAILURE
> {code}
> Depending on what your build actually does, those artifacts might not always
> be created. I'd like to propose that you add an option to make the archiving
> of artifacts non fatal.
> Thanks,
> 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-12690) JenkinsTrigger does not understand SSH Key with a password
[ https://issues.jenkins-ci.org/browse/JENKINS-12690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158810#comment-158810 ] Tim Baverstock commented on JENKINS-12690: -- Oh, the password is 'letmein' for the keys with a passphrase. > JenkinsTrigger does not understand SSH Key with a password > -- > > Key: JENKINS-12690 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12690 > Project: Jenkins > Issue Type: Bug > Components: gerrit-trigger > Environment: Linux dt-000886 3.0.0-15-generic #26-Ubuntu SMP Fri Jan > 20 17:23:00 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux > Jenkins ver. 1.450 > Gerrit Trigger 2.3.1 >Reporter: Tim Baverstock >Assignee: rsandell > Labels: gerrit, plugin > Attachments: id_rsa, id_rsa, id_rsa.pub, id_rsa.pub > > > I can only get Jenkins to talk to Gerrit's SSH connection if the key file has > no password. > 1. Use ssh-keygen to create a key with a password > 2. Configure Gerrit Trigger with that key and its password > 3. Test Connection > > Bad SSH keyfile or password > Jenkins.log: > > 09-Feb-2012 12:43:18 > > com.sshtools.j2ssh.transport.publickey.SshPrivateKeyFile parse > > INFO: Parsing private key file > > 09-Feb-2012 12:43:18 > > com.sshtools.j2ssh.transport.publickey.SshPrivateKeyFile parse > > INFO: Private key is not in the default format, attempting parse with other > > supported formats > 4. Clear the password: ssh-keygen -f .ssh/id_rsa -p -N '' > Note that the Proc-Type and DEK-Info headers have gone. > 5. Test connection (without clearing the password!) > 6. Succeeds. Log still complains about non-default format. > 7. Clear the password in Jenkins. > 8. Test connection > 9. Still succeeds, Log still complains about non-default format. > This took me ages to nail down because supplying a password to a no-password > key file doesn't fail. -- 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-12516) java.io.IOException @ hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80)
[ https://issues.jenkins-ci.org/browse/JENKINS-12516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158811#comment-158811 ] SCM/JIRA link daemon commented on JENKINS-12516: Code changed in jenkins User: Ulli Hafner Path: pom.xml src/main/java/hudson/plugins/dry/parser/cpd/CpdParser.java src/test/java/hudson/plugins/dry/parser/cpd/CpdParserTest.java src/test/resources/hudson/plugins/dry/parser/cpd/issue12516.xml http://jenkins-ci.org/commit/dry-plugin/c26adbd5955801c6080c8ba46d10ceb3b041e595 Log: [FIXED JENKINS-12516] Upgrade to Digester 3.2 which is more robust in parsing CDATA elements. > java.io.IOException @ > hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80) > -- > > Key: JENKINS-12516 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12516 > Project: Jenkins > Issue Type: Bug > Components: dry >Affects Versions: current >Reporter: Greg Moncreaff >Assignee: Ulli Hafner > > CPD is looking at .sh files and DRY's processing of the CPD results blew up. > Looking at CPDs XML Renderer, it attempts to escape anything that would > prematurely end the CDATA > buffer.append(StringUtil.replaceString(codeFragment, "]]>", > "]]>")).append(PMD.EOL + "]]>" + PMD.EOL + "" + PMD. > EOL); > Is it possible that DRY is choking in its attempt to process the contents of > the CDATA block. the codefragments have hundreds of > \ > >> > > > # > && > >& > that could confuse XML if not all escaped! > 21:57:45 java.io.IOException: No parser found for duplicated code results > file cpd-sh.xml > 21:57:45 at > hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:358) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:317) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:266) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) > 21:57:45 at hudson.FilePath.act(FilePath.java:783) > 21:57:45 at hudson.FilePath.act(FilePath.java:765) > 21:57:45 at > hudson.plugins.dry.DryPublisher.perform(DryPublisher.java:171) > 21:57:45 at > hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338) > 21:57:45 at > hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:670) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:648) > 21:57:45 at hudson.model.Build$RunnerImpl.post2(Build.java:162) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:617) > 21:57:45 at hudson.model.Run.run(Run.java:1429) > 21:57:45 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > 21:57:45 at > hudson.model.ResourceController.execute(ResourceController.java:88) > 21:57:45 at hudson.model.Executor.run(Executor.java:238) -- 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-12516) java.io.IOException @ hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80)
[ https://issues.jenkins-ci.org/browse/JENKINS-12516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12516. Resolution: Fixed > java.io.IOException @ > hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80) > -- > > Key: JENKINS-12516 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12516 > Project: Jenkins > Issue Type: Bug > Components: dry >Affects Versions: current >Reporter: Greg Moncreaff >Assignee: Ulli Hafner > > CPD is looking at .sh files and DRY's processing of the CPD results blew up. > Looking at CPDs XML Renderer, it attempts to escape anything that would > prematurely end the CDATA > buffer.append(StringUtil.replaceString(codeFragment, "]]>", > "]]>")).append(PMD.EOL + "]]>" + PMD.EOL + "" + PMD. > EOL); > Is it possible that DRY is choking in its attempt to process the contents of > the CDATA block. the codefragments have hundreds of > \ > >> > > > # > && > >& > that could confuse XML if not all escaped! > 21:57:45 java.io.IOException: No parser found for duplicated code results > file cpd-sh.xml > 21:57:45 at > hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:358) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:317) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:266) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) > 21:57:45 at hudson.FilePath.act(FilePath.java:783) > 21:57:45 at hudson.FilePath.act(FilePath.java:765) > 21:57:45 at > hudson.plugins.dry.DryPublisher.perform(DryPublisher.java:171) > 21:57:45 at > hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338) > 21:57:45 at > hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:670) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:648) > 21:57:45 at hudson.model.Build$RunnerImpl.post2(Build.java:162) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:617) > 21:57:45 at hudson.model.Run.run(Run.java:1429) > 21:57:45 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > 21:57:45 at > hudson.model.ResourceController.execute(ResourceController.java:88) > 21:57:45 at hudson.model.Executor.run(Executor.java:238) -- 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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
[
https://issues.jenkins-ci.org/browse/JENKINS-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158812#comment-158812
]
Thomas Fields commented on JENKINS-10502:
-
If only I knew who to assign this to so it actually gets implemented.
> Add an option to make archiving the artifacts non-fatal if they don't exist
> ---
>
> Key: JENKINS-10502
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10502
> Project: Jenkins
> Issue Type: Improvement
> Components: core
> Environment: Jenkins 1.421
>Reporter: Thomas Fields
>
> If you tick the box to enable "Archive the artifacts", populate the "Files to
> archive", and your build fails to output those artifacts it will fail with
> something like this:
> {code}
> 12:11:51 Archiving artifacts
> 12:11:51 ERROR: No artifacts found that match the file pattern
> "tfields/Live/Engine/Tools/Layout.*". Configuration error?
> 12:11:57 ERROR: 'tfields/Live/Engine/Tools/Layout.*' doesn't match anything:
> 'tfields' exists but not 'tfields/Live/Engine/Tools/Layout.*'
> 12:11:57 Build step 'Archive the artifacts' changed build result to FAILURE
> {code}
> Depending on what your build actually does, those artifacts might not always
> be created. I'd like to propose that you add an option to make the archiving
> of artifacts non fatal.
> Thanks,
> 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-12424) More correct and specific build state change reasons from Warnings
[ https://issues.jenkins-ci.org/browse/JENKINS-12424?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ulli Hafner resolved JENKINS-12424. --- Resolution: Fixed > More correct and specific build state change reasons from Warnings > --- > > Key: JENKINS-12424 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12424 > Project: Jenkins > Issue Type: Improvement > Components: analysis-core, warnings >Reporter: Greg Moncreaff >Assignee: Ulli Hafner >Priority: Minor > > I got this in my jobs console. > [WARNINGS] Setting build status to FAILURE since total number of annotations > exceeds the threshold 200: [HIGH, NORMAL, LOW] > Two issues. > 1. text says total, but this was actually a "compute status since reference > build (new) gate. > 2. text should say which specific criteria was exceeded > 3. it doesn't tell you what the actual number/difference was > E.g. > [WARNINGS] Setting build status to FAILURE since number, 234, of new HIGH > annotations exceeds the threshold of 200 by 34 or 17%. -- 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-12536) NullPointerException in QualityCenterResultArchiver
[ https://issues.jenkins-ci.org/browse/JENKINS-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on JENKINS-12536 started by Romain Seguy. > NullPointerException in QualityCenterResultArchiver > --- > > Key: JENKINS-12536 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12536 > Project: Jenkins > Issue Type: Bug > Components: qc >Affects Versions: current > Environment: Jenkins 1.424 running on Linux; QTP 10.0 and HP QC 9.2 > running on a Windows Jenkins slave >Reporter: Thies Fengler >Assignee: Romain Seguy > > This error occurs if QualityCenter.getTestSetLogFiles() returns null. This > can happen if the tests did not run due to some error (which was my fault > (again, see JENKINS-12389)) on the jenkins slave. > ERROR: Publisher > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver aborted due to > exception > java.lang.NullPointerException > at java.util.ArrayList.addAll(ArrayList.java:472) > at > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver.perform(QualityCenterResultArchiver.java:81) > at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635) > at hudson.model.Build$RunnerImpl.post2(Build.java:161) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604) > at hudson.model.Run.run(Run.java:1400) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:175) -- 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-12692) Plugin destroys configuration of Publishers
Ulli Hafner created JENKINS-12692:
-
Summary: Plugin destroys configuration of Publishers
Key: JENKINS-12692
URL: https://issues.jenkins-ci.org/browse/JENKINS-12692
Project: Jenkins
Issue Type: Bug
Components: flexible-publish
Reporter: Ulli Hafner
Assignee: bap
Priority: Blocker
After installing the flexible-publish plugin, the Publishers of some jobs get
corrupted on save.
E.g. I have a WarningsPublisher in my job with the following serialization:
{code}
[WARNINGS]
false
false
false
true
Java Compiler
{code}
After installing the flexible-publish plug-in, I get the following result when
saving the configuration. Seems that there is an interaction between these
plug-ins.
{code}
low
[WARNINGS]
false
false
false
true
Java Compiler
{code}
I have no idea what is causing that problem. Maybe the reason is something deep
in core or in my analysis plug-ins. I need to attach a debugger to our server...
Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is it
intercepting the publishers somehow?
Interestingly, the problem has been reported with another simpilar plug-ins
too: the template project.
Here some related issues: JENKINS-8185, JENKINS-12812.
--
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-12692) Plugin destroys configuration of Publishers
[
https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulli Hafner updated JENKINS-12692:
--
Description:
After installing the flexible-publish plugin, the Publishers of some jobs get
corrupted on save.
E.g. I have a WarningsPublisher in my job with the following serialization:
{code}
[WARNINGS]
false
false
false
true
Java Compiler
{code}
After installing the flexible-publish plug-in, I get the following result when
saving the configuration. Seems that there is an interaction between these
plug-ins.
{code}
low
[WARNINGS]
false
false
false
true
Java Compiler
{code}
The following tag is removed:
{code}
low
{code}
I have no idea what is causing that problem. Maybe the reason is something deep
in core or in my analysis plug-ins. I need to attach a debugger to our server...
Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is it
intercepting the publishers somehow?
Interestingly, the problem has been reported with another simpilar plug-ins
too: the template project.
Here some related issues: JENKINS-8185, JENKINS-12812.
was:
After installing the flexible-publish plugin, the Publishers of some jobs get
corrupted on save.
E.g. I have a WarningsPublisher in my job with the following serialization:
{code}
[WARNINGS]
false
false
false
true
Java Compiler
{code}
After installing the flexible-publish plug-in, I get the following result when
saving the configuration. Seems that there is an interaction between these
plug-ins.
{code}
low
[WARNINGS]
false
false
false
true
Java Compiler
{code}
I have no idea what is causing that problem. Maybe the reason is something deep
in core or in my analysis plug-ins. I need to attach a debugger to our server...
Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is it
intercepting the publishers somehow?
Interestingly, the problem has been reported with another simpilar plug-ins
too: the template project.
Here some related issues: JENKINS-8185, JENKINS-12812.
> Plugin destroys configuration of Publishers
> ---
>
> Key: JENKINS-12692
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12692
> Project: Jenkins
> Issue Type: Bug
> Components: flexible-publish
>Reporter: Ulli Hafner
>Assignee: bap
>Priority: Blocker
>
> After installing the flexible-publish plugin, the Publishers of some jobs get
> corrupted on save.
> E.g. I have a WarningsPublisher in my job with the following serialization:
> {code}
>
>
>
>
> [WARNINGS]
>
> false
> false
>
>
>
>
>
>
>
>
>
>
> false
> true
>
>
> Java Compiler
>
>
> {code}
> After installing the flexible-publish plug-in, I get the following result
> when saving the configuration. Seems that there is an interaction between
> these plug-ins.
> {code}
>
>
>
>
> low
> [WARNINGS]
>
> false
> false
>
>
>
>
>
>
>
>
>
>
> false
> true
>
>
> Java Compiler
>
>
> {code}
> The following tag is removed:
> {code}
> low
> {code}
> I have no idea what is causing that problem. Maybe the reason is something
> deep in core or in my analysis plug-ins. I need to attach a debugger to our
> server...
> Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is
> it intercepting the publishers somehow?
> Interestingly, the problem has been reported with another simpilar plug-ins
> too: the template project.
> Here some related issues: JENKINS-8185, JENKINS-12812.
--
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-12516) java.io.IOException @ hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80)
[ https://issues.jenkins-ci.org/browse/JENKINS-12516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158813#comment-158813 ] dogfood commented on JENKINS-12516: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_dry #315|http://ci.jenkins-ci.org/job/plugins_dry/315/] [FIXED JENKINS-12516] Upgrade to Digester 3.2 which is more robust in (Revision c26adbd5955801c6080c8ba46d10ceb3b041e595) Result = SUCCESS Ulli Hafner : Files : * src/test/resources/hudson/plugins/dry/parser/cpd/issue12516.xml * src/test/java/hudson/plugins/dry/parser/cpd/CpdParserTest.java * src/main/java/hudson/plugins/dry/parser/cpd/CpdParser.java * pom.xml > java.io.IOException @ > hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80) > -- > > Key: JENKINS-12516 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12516 > Project: Jenkins > Issue Type: Bug > Components: dry >Affects Versions: current >Reporter: Greg Moncreaff >Assignee: Ulli Hafner > > CPD is looking at .sh files and DRY's processing of the CPD results blew up. > Looking at CPDs XML Renderer, it attempts to escape anything that would > prematurely end the CDATA > buffer.append(StringUtil.replaceString(codeFragment, "]]>", > "]]>")).append(PMD.EOL + "]]>" + PMD.EOL + "" + PMD. > EOL); > Is it possible that DRY is choking in its attempt to process the contents of > the CDATA block. the codefragments have hundreds of > \ > >> > > > # > && > >& > that could confuse XML if not all escaped! > 21:57:45 java.io.IOException: No parser found for duplicated code results > file cpd-sh.xml > 21:57:45 at > hudson.plugins.dry.parser.DuplicationParserRegistry.parse(DuplicationParserRegistry.java:80) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:358) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:317) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:266) > 21:57:45 at > hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31) > 21:57:45 at hudson.FilePath.act(FilePath.java:783) > 21:57:45 at hudson.FilePath.act(FilePath.java:765) > 21:57:45 at > hudson.plugins.dry.DryPublisher.perform(DryPublisher.java:171) > 21:57:45 at > hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:338) > 21:57:45 at > hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:695) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:670) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:648) > 21:57:45 at hudson.model.Build$RunnerImpl.post2(Build.java:162) > 21:57:45 at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:617) > 21:57:45 at hudson.model.Run.run(Run.java:1429) > 21:57:45 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > 21:57:45 at > hudson.model.ResourceController.execute(ResourceController.java:88) > 21:57:45 at hudson.model.Executor.run(Executor.java:238) -- 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-12692) Plugin destroys configuration of Publishers
[
https://issues.jenkins-ci.org/browse/JENKINS-12692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ulli Hafner updated JENKINS-12692:
--
Description:
After installing the flexible-publish plugin, the Publishers of some jobs get
corrupted on save.
E.g. I have a WarningsPublisher in my job with the following serialization:
{code}
[WARNINGS]
false
false
false
true
Java Compiler
{code}
After installing the flexible-publish plug-in, I get the following result when
saving the configuration. Seems that there is an interaction between these
plug-ins.
{code}
low
[WARNINGS]
false
false
false
true
Java Compiler
{code}
The following tag is removed:
{code}
low
{code}
I have no idea what is causing that problem. Maybe the reason is something deep
in core or in my analysis plug-ins. I need to attach a debugger to our server...
Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is it
intercepting the publishers somehow?
Interestingly, the problem has been reported with another simpilar plug-ins
too: the template project.
Here some related issues: JENKINS-8185, JENKINS-12182.
was:
After installing the flexible-publish plugin, the Publishers of some jobs get
corrupted on save.
E.g. I have a WarningsPublisher in my job with the following serialization:
{code}
[WARNINGS]
false
false
false
true
Java Compiler
{code}
After installing the flexible-publish plug-in, I get the following result when
saving the configuration. Seems that there is an interaction between these
plug-ins.
{code}
low
[WARNINGS]
false
false
false
true
Java Compiler
{code}
The following tag is removed:
{code}
low
{code}
I have no idea what is causing that problem. Maybe the reason is something deep
in core or in my analysis plug-ins. I need to attach a debugger to our server...
Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is it
intercepting the publishers somehow?
Interestingly, the problem has been reported with another simpilar plug-ins
too: the template project.
Here some related issues: JENKINS-8185, JENKINS-12812.
> Plugin destroys configuration of Publishers
> ---
>
> Key: JENKINS-12692
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12692
> Project: Jenkins
> Issue Type: Bug
> Components: flexible-publish
>Reporter: Ulli Hafner
>Assignee: bap
>Priority: Blocker
>
> After installing the flexible-publish plugin, the Publishers of some jobs get
> corrupted on save.
> E.g. I have a WarningsPublisher in my job with the following serialization:
> {code}
>
>
>
>
> [WARNINGS]
>
> false
> false
>
>
>
>
>
>
>
>
>
>
> false
> true
>
>
> Java Compiler
>
>
> {code}
> After installing the flexible-publish plug-in, I get the following result
> when saving the configuration. Seems that there is an interaction between
> these plug-ins.
> {code}
>
>
>
>
> low
> [WARNINGS]
>
> false
> false
>
>
>
>
>
>
>
>
>
>
> false
> true
>
>
> Java Compiler
>
>
> {code}
> The following tag is removed:
> {code}
> low
> {code}
> I have no idea what is causing that problem. Maybe the reason is something
> deep in core or in my analysis plug-ins. I need to attach a debugger to our
> server...
> Any ideas? What exactly is the flexible publisher doing in Jenkins core? Is
> it intercepting the publishers somehow?
> Interestingly, the problem has been reported with another simpilar plug-ins
> too: the template project.
> Here some related issues: JENKINS-8185, JENKINS-12182.
--
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:
[JIRA] (JENKINS-12536) NullPointerException in QualityCenterResultArchiver
[ https://issues.jenkins-ci.org/browse/JENKINS-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158814#comment-158814 ] Romain Seguy commented on JENKINS-12536: Fixed in the upcoming 1.2.2. > NullPointerException in QualityCenterResultArchiver > --- > > Key: JENKINS-12536 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12536 > Project: Jenkins > Issue Type: Bug > Components: qc >Affects Versions: current > Environment: Jenkins 1.424 running on Linux; QTP 10.0 and HP QC 9.2 > running on a Windows Jenkins slave >Reporter: Thies Fengler >Assignee: Romain Seguy > > This error occurs if QualityCenter.getTestSetLogFiles() returns null. This > can happen if the tests did not run due to some error (which was my fault > (again, see JENKINS-12389)) on the jenkins slave. > ERROR: Publisher > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver aborted due to > exception > java.lang.NullPointerException > at java.util.ArrayList.addAll(ArrayList.java:472) > at > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver.perform(QualityCenterResultArchiver.java:81) > at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635) > at hudson.model.Build$RunnerImpl.post2(Build.java:161) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604) > at hudson.model.Run.run(Run.java:1400) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:175) -- 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-12536) NullPointerException in QualityCenterResultArchiver
[ https://issues.jenkins-ci.org/browse/JENKINS-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy closed JENKINS-12536. -- > NullPointerException in QualityCenterResultArchiver > --- > > Key: JENKINS-12536 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12536 > Project: Jenkins > Issue Type: Bug > Components: qc >Affects Versions: current > Environment: Jenkins 1.424 running on Linux; QTP 10.0 and HP QC 9.2 > running on a Windows Jenkins slave >Reporter: Thies Fengler >Assignee: Romain Seguy > > This error occurs if QualityCenter.getTestSetLogFiles() returns null. This > can happen if the tests did not run due to some error (which was my fault > (again, see JENKINS-12389)) on the jenkins slave. > ERROR: Publisher > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver aborted due to > exception > java.lang.NullPointerException > at java.util.ArrayList.addAll(ArrayList.java:472) > at > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver.perform(QualityCenterResultArchiver.java:81) > at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635) > at hudson.model.Build$RunnerImpl.post2(Build.java:161) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604) > at hudson.model.Run.run(Run.java:1400) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:175) -- 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-12536) NullPointerException in QualityCenterResultArchiver
[ https://issues.jenkins-ci.org/browse/JENKINS-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Seguy resolved JENKINS-12536. Resolution: Fixed > NullPointerException in QualityCenterResultArchiver > --- > > Key: JENKINS-12536 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12536 > Project: Jenkins > Issue Type: Bug > Components: qc >Affects Versions: current > Environment: Jenkins 1.424 running on Linux; QTP 10.0 and HP QC 9.2 > running on a Windows Jenkins slave >Reporter: Thies Fengler >Assignee: Romain Seguy > > This error occurs if QualityCenter.getTestSetLogFiles() returns null. This > can happen if the tests did not run due to some error (which was my fault > (again, see JENKINS-12389)) on the jenkins slave. > ERROR: Publisher > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver aborted due to > exception > java.lang.NullPointerException > at java.util.ArrayList.addAll(ArrayList.java:472) > at > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver.perform(QualityCenterResultArchiver.java:81) > at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635) > at hudson.model.Build$RunnerImpl.post2(Build.java:161) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604) > at hudson.model.Run.run(Run.java:1400) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:175) -- 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-10333) Maven jobs don't report all details of failures
[
https://issues.jenkins-ci.org/browse/JENKINS-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158815#comment-158815
]
Tim Drury commented on JENKINS-10333:
-
I get the same error on Jenkins 1.450 compiling a maven 3.0.4 project. This
_just_ started happening on our Jenkins system and it correlates to our move
from maven 2.2.1 to maven 3.0.4, but I could swear we got good compilation
error messages even with 3.0.4. The compiler plugin is 2.0.2.
> Maven jobs don't report all details of failures
> ---
>
> Key: JENKINS-10333
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10333
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
> Environment: Jenkins 1.420 but I'm almost sure to have see it before
>Reporter: Arnaud Héritier
>Priority: Critical
>
> I have a maven build which is failing because of compilation error.
> My local Maven (3.0.3) build returns this :
> {code}
> [INFO]
>
> [INFO] Building eXo Social Portlet Web App 1.2.1-SNAPSHOT
> [INFO]
>
> Downloading:
> http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
> Downloading:
> http://repository.exoplatform.org/private/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
> Downloaded:
> http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/maven-metadata.xml
> (2 KB at 0.0 KB/sec)
> Downloading:
> http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.pom
> Downloaded:
> http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.pom
> (3 KB at 4.2 KB/sec)
> Downloading:
> http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.jar
> Downloaded:
> http://repository.exoplatform.org/public/org/exoplatform/portal/exo.portal.webui.dashboard/3.2.0-PLF-SNAPSHOT/exo.portal.webui.dashboard-3.2.0-PLF-20110714.101638-143.jar
> (35 KB at 52.6 KB/sec)
> [INFO]
> [INFO] --- maven-clean-plugin:2.3:clean (default-clean) @
> exo.social.webapp.portlet ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-plugin-versions)
> @ exo.social.webapp.portlet ---
> [WARNING] This rule is not compatible with the current version of Maven. The
> rule is not able to perform any checks.
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-java-version) @
> exo.social.webapp.portlet ---
> [INFO]
> [INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-maven-version) @
> exo.social.webapp.portlet ---
> [INFO]
> [INFO] --- maven-resources-plugin:2.4.1:resources (default-resources) @
> exo.social.webapp.portlet ---
> [INFO] Using 'UTF-8' encoding to copy filtered resources.
> [INFO] Copying 0 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @
> exo.social.webapp.portlet ---
> [INFO] Compiling 28 source files to
> /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/target/classes
> [INFO]
>
> [INFO] Reactor Summary:
> [INFO]
> ..
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 3:58.991s
> [INFO] Finished at: Thu Jul 14 14:30:36 CEST 2011
> [INFO] Final Memory: 25M/125M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
> (default-compile) on project exo.social.webapp.portlet: Compilation failure:
> Compilation failure:
> [ERROR]
> /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UIHomeSpacePortlet.java:[64,36]
> [deprecation]
> hasEditPermission(org.exoplatform.social.core.space.model.Space,java.lang.String)
> in org.exoplatform.social.core.space.spi.SpaceService has been deprecated
> [ERROR]
> [ERROR]
> /Users/arnaud/Code/eXo/social-1.2.x.svn/webapp/portlet/src/main/java/org/exoplatform/social/portlet/UISocialLogoPortlet.java:[104,13]
> [deprecation] getOrCreateIdentity(java.lang.String,java.lang.String) in
> org.exoplatform.social.core.manager.IdentityManager h
[JIRA] (JENKINS-12675) Add an option to install specific selenium version on the running nodes
[ https://issues.jenkins-ci.org/browse/JENKINS-12675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Lavoie reassigned JENKINS-12675: Assignee: Richard Lavoie (was: Kohsuke Kawaguchi) > Add an option to install specific selenium version on the running nodes > --- > > Key: JENKINS-12675 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12675 > Project: Jenkins > Issue Type: New Feature > Components: selenium >Reporter: Richard Lavoie >Assignee: Richard Lavoie >Priority: Minor > > People have been asking over email that it would be nice to be able to use > the latest selenium version, so here is the ticket for that. -- 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-12683) Crowd 2 plugin authenticates, but doesn't allow login
[ https://issues.jenkins-ci.org/browse/JENKINS-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Busha resolved JENKINS-12683. - Fix Version/s: current Resolution: Not A Defect My apologies, this was a configuration error. The alias I was using to access Jenkins did not resolve to the fully qualified name, just the machine name. The user authenticated correctly with Crowd, but the cookie (for the domain) didn't match Jenkin's address (machine name). Thanks for the help! > Crowd 2 plugin authenticates, but doesn't allow login > - > > Key: JENKINS-12683 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12683 > Project: Jenkins > Issue Type: Bug > Components: crowd2 >Affects Versions: current > Environment: x64 Windows 7 >Reporter: Dan Busha >Assignee: Thorsten Heit >Priority: Critical > Labels: plugin, windows > Fix For: current > > > I have an installation of Jenkins 1.450 with the Crowd 2 plugin v1.4 > installed connecting to a Crowd v2.4.0 server which successfully > authenticates users (according to the log). When a user enters their username > and password and clicks 'log in' they are returned to the main Jenkins page > but are not logged in. -- 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-12683) Crowd 2 plugin authenticates, but doesn't allow login
[ https://issues.jenkins-ci.org/browse/JENKINS-12683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158817#comment-158817 ] Thorsten Heit commented on JENKINS-12683: - Hi, great to hear you solved it. Regarding your problem and your solution I guess I should add a hint to the plugin's wiki page... Regards Thorsten > Crowd 2 plugin authenticates, but doesn't allow login > - > > Key: JENKINS-12683 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12683 > Project: Jenkins > Issue Type: Bug > Components: crowd2 >Affects Versions: current > Environment: x64 Windows 7 >Reporter: Dan Busha >Assignee: Thorsten Heit >Priority: Critical > Labels: plugin, windows > Fix For: current > > > I have an installation of Jenkins 1.450 with the Crowd 2 plugin v1.4 > installed connecting to a Crowd v2.4.0 server which successfully > authenticates users (according to the log). When a user enters their username > and password and clicks 'log in' they are returned to the main Jenkins page > but are not logged in. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12048) Wrong option "--branch" used by change polling
[ https://issues.jenkins-ci.org/browse/JENKINS-12048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emidio Stani reopened JENKINS-12048: Hi all, I recently experienced this problem with Jenkins 1.450 and Mercurial Plugin 1.38, see log below: Started on Feb 9, 2012 5:24:03 PM [workspace] $ hg pull --rev default pulling from http://jenkinsuforge:***@hg.u-forge.net/hg/drupal/ searching for changes no changes found [workspace] $ hg log --style /usr/app/jenkins/jobs/Drupal/workspace/tmp7553423341421974400style --branch default --no-merges --prune af4057c4b7d19d8ebef92de805e28db93fcb0a2c hg log: option --branch not recognized hg log [OPTION]... [FILE] > Wrong option "--branch" used by change polling > --- > > Key: JENKINS-12048 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12048 > Project: Jenkins > Issue Type: Bug > Components: mercurial >Reporter: Christoph Neuroth >Assignee: davidmc24 >Priority: Critical > > With Jenkins 1.442, Mercurial Plugin 1.38, the change polling issues a "hg > log" command using "\-\-branch foo", which mercurial doesn't know about. > Should be "\-b" or "\-\-only-branch". -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12648) TestNG 0.31 does not show test results when tests failed
[ https://issues.jenkins-ci.org/browse/JENKINS-12648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158819#comment-158819 ] Jeff Weiss commented on JENKINS-12648: -- I installed 0.31 this morning and I don't see this issue either. Peter Lustig, I have seen the message "Not looking for any testNG results" when the previous build step failed (in my case, a shell script). So the build fails at that step and it makes sense for testNG plugin to not bother looking for results. Maybe that is what you are seeing. > TestNG 0.31 does not show test results when tests failed > > > Key: JENKINS-12648 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12648 > Project: Jenkins > Issue Type: Bug > Components: testng >Affects Versions: current >Reporter: Peter Lustig >Assignee: nalin_makar >Priority: Critical > Labels: testng > > Whenever I use the TestNG-Plugin 0.31 it only shows reports if the tests > passed. But if the failey there are no test results. If I downgrade to 0.26 > for example everthing works fine. Both the failed and passed test results are > displayed. Please fix this, would be very important. 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-12648) TestNG 0.31 does not show test results when tests failed
[ https://issues.jenkins-ci.org/browse/JENKINS-12648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158819#comment-158819 ] Jeff Weiss edited comment on JENKINS-12648 at 2/9/12 4:31 PM: -- I installed 0.31 this morning and I don't see this issue either. Peter Lustig, I have seen the message "Not looking for any testNG results" when the previous build step failed (in my case, a shell script step returned nonzero). So the build fails at that step and it makes sense for testNG plugin to not bother looking for results. Maybe that is what you are seeing. I don't know what your config looks like, but you may want to verify that all the build steps complete without error. was (Author: weissjeffm): I installed 0.31 this morning and I don't see this issue either. Peter Lustig, I have seen the message "Not looking for any testNG results" when the previous build step failed (in my case, a shell script). So the build fails at that step and it makes sense for testNG plugin to not bother looking for results. Maybe that is what you are seeing. > TestNG 0.31 does not show test results when tests failed > > > Key: JENKINS-12648 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12648 > Project: Jenkins > Issue Type: Bug > Components: testng >Affects Versions: current >Reporter: Peter Lustig >Assignee: nalin_makar >Priority: Critical > Labels: testng > > Whenever I use the TestNG-Plugin 0.31 it only shows reports if the tests > passed. But if the failey there are no test results. If I downgrade to 0.26 > for example everthing works fine. Both the failed and passed test results are > displayed. Please fix this, would be very important. 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-12693) urltrigger cannot start: claims "bad major version at offset=6"
torbent created JENKINS-12693:
-
Summary: urltrigger cannot start: claims "bad major version at
offset=6"
Key: JENKINS-12693
URL: https://issues.jenkins-ci.org/browse/JENKINS-12693
Project: Jenkins
Issue Type: Bug
Components: urltrigger
Environment: Jenkins 1.445, urltrigger 0.10
Reporter: torbent
Assignee: gbois
Attachments: 2012-02-09-urltrigger-major-version.txt.txt
The urltrigger plugin refuses to start, gives a stacktrace where this seems to
be the interesting part:
{quote}Caused by: java.lang.UnsupportedClassVersionError:
(com/sun/jersey/api/client/config/ClientConfig) bad major version at offset=6
{quote}
Full log attached. I'm not able to test newer releases at the moment, because
Jenkins 1.446 does not work for me and the latest urltrigger is built as a .jpi
which Jenkins doesn't support until 1.448.
--
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-12648) TestNG 0.31 does not show test results when tests failed
[ https://issues.jenkins-ci.org/browse/JENKINS-12648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158820#comment-158820 ] nalin_makar commented on JENKINS-12648: --- I figured the same, but I am not sure now that it's the right behavior. Sometimes testng ant ask itself can be configured to to fail the build if tests fail, but that should not stop us from reporting the tests that were executed. I made a similar change for aborted builds recently based on bug that kutzi filed and now am wondering if I should revert that behavior as well or not. > TestNG 0.31 does not show test results when tests failed > > > Key: JENKINS-12648 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12648 > Project: Jenkins > Issue Type: Bug > Components: testng >Affects Versions: current >Reporter: Peter Lustig >Assignee: nalin_makar >Priority: Critical > Labels: testng > > Whenever I use the TestNG-Plugin 0.31 it only shows reports if the tests > passed. But if the failey there are no test results. If I downgrade to 0.26 > for example everthing works fine. Both the failed and passed test results are > displayed. Please fix this, would be very important. 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-11370) pre-scm-buildstep assumes workspace exists
[ https://issues.jenkins-ci.org/browse/JENKINS-11370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158821#comment-158821 ] sid nancy commented on JENKINS-11370: - Here is the full stacktrace from the console when the pre-scm build plugin tries to reference the non-existent workspace. This will happen any time a new job which has no namespace in the slave filesystem uses the pre-scm plugin. Started by user Building remotely on in workspace /some/path/on/slave Running Prebuild steps [] $ cmd /c call C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\hudson33854237146312.bat The directory name is invalid FATAL: command execution failed java.io.IOException: Cannot run program "cmd" (in directory "/some/path/on/slave"): CreateProcess error=267, The directory name is invalid at java.lang.ProcessBuilder.start(Unknown Source) 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.Launcher$RemoteLaunchCallable.call(Launcher.java:932) at hudson.Launcher$RemoteLaunchCallable.call(Launcher.java:899) 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) Caused by: java.io.IOException: CreateProcess error=267, The directory name is invalid at java.lang.ProcessImpl.create(Native Method) at java.lang.ProcessImpl.(Unknown Source) at java.lang.ProcessImpl.start(Unknown Source) ... 17 more Failed build for hudson.tasks.BatchFile@535c37ae > pre-scm-buildstep assumes workspace exists > -- > > Key: JENKINS-11370 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11370 > Project: Jenkins > Issue Type: Bug > Components: plugin >Affects Versions: current > Environment: OS X >Reporter: Niklas Saers >Priority: Minor > > pre-scm-buildstep assumes that the directory workspace exists when it's > running. However, when setting up a project, it does not exist, and thus this > step will fail unless the admin creates manually. Proper behaviour should be > to check if it exists, and create it if it doesn't. Otherwise, if it does not > exist, the execute shell will fail -- 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-12680) onOffline in ComputerListener not getting called when node is taken offline
[ https://issues.jenkins-ci.org/browse/JENKINS-12680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158822#comment-158822 ] SCM/JIRA link daemon commented on JENKINS-12680: Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/java/hudson/slaves/SlaveComputer.java test/src/test/java/hudson/slaves/JNLPLauncherTest.java http://jenkins-ci.org/commit/jenkins/4378e878ae327a954911ae4ef84679e0060b63e2 Log: [FIXED JENKINS-12680] the onOffline method wasn't called for abrupt client termination Compare: https://github.com/jenkinsci/jenkins/compare/dd0f362...4378e87 > onOffline in ComputerListener not getting called when node is taken offline > --- > > Key: JENKINS-12680 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12680 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: OS: All >Reporter: Jens Christensen > Labels: ComputerListener, jenkins, onOffline, slave > > In ComputerListener, onOffline is only called if a node is taken down with > the disconnect link in jenkins, any other cause for a node to go offline, > makes the call postponed until the master is taken down. -- 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-12680) onOffline in ComputerListener not getting called when node is taken offline
[ https://issues.jenkins-ci.org/browse/JENKINS-12680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12680. Resolution: Fixed > onOffline in ComputerListener not getting called when node is taken offline > --- > > Key: JENKINS-12680 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12680 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: OS: All >Reporter: Jens Christensen > Labels: ComputerListener, jenkins, onOffline, slave > > In ComputerListener, onOffline is only called if a node is taken down with > the disconnect link in jenkins, any other cause for a node to go offline, > makes the call postponed until the master is taken down. -- 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-3681) Hide Empty Tabs (Views) in the GUI
[ https://issues.jenkins-ci.org/browse/JENKINS-3681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158823#comment-158823 ] domi commented on JENKINS-3681: --- just placed a pull request: https://github.com/jenkinsci/jenkins/pull/370 > Hide Empty Tabs (Views) in the GUI > -- > > Key: JENKINS-3681 > URL: https://issues.jenkins-ci.org/browse/JENKINS-3681 > Project: Jenkins > Issue Type: Improvement > Components: gui >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: rnell > > I'd like the ability to hide tabs that have no visible jobs. We use Project > Based Security to limit development access to only their projects. I don't > like > that developers can still see all tabs used by the other groups, even though > they are empty due to the security settings. -- 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-10558) Jenkins mercurial plugin - add support for bookmarks
[
https://issues.jenkins-ci.org/browse/JENKINS-10558?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158824#comment-158824
]
Michael Ekstrand commented on JENKINS-10558:
Looking for this myself — the Git plugin supports branches (watching/building
multiple branches); it seems like using an identical model for the Mercurial
plugin with bookmarks would solve this nicely.
> Jenkins mercurial plugin - add support for bookmarks
>
>
> Key: JENKINS-10558
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10558
> Project: Jenkins
> Issue Type: New Feature
> Components: mercurial
>Affects Versions: current
> Environment: all
>Reporter: wujek srujek
>Assignee: Kohsuke Kawaguchi
>Priority: Critical
>
> Mercurial plugin supports branches, which is nice. However, there are a lot
> of people, especially these coming from git, who think that such named
> branches are no good (they stay for ever, the branch is baked into the
> commit), and prefer using bookmarks* instead. There seems to be a lot of
> momentum around that extension, which culminated in it being incorporated
> into mercurial core since hg 1.8 (which means it is not an extension any
> more; rather, it is a first-class citizen now).
> * http://mercurial.selenic.com/wiki/BookmarksExtension,
> http://www.mronge.com/2009/04/01/a-sample-mercurial-bookmark-workflow,
> http://groups.google.com/group/mercurial_general/browse_thread/thread/5f7d2d7c5cfc109b?fwc=2
> (post #4 by Daniel Carrera is really good)
> Bookmarks is the closest thing that mercurial currently supports that
> resembles git-like branches. This is what we would love to use (as we share
> the view that such long running named branches are no good), but we can't
> since the Jenkins plugin doesn't support this (we would like to create ad-hoc
> Jenkins jobs for our features (topic branches), which are bookmarks, not
> branches, and once the feature is implemented, we drop the Jenkins job).
> A basic bookmarks workflow (in a repository):
> $ hg bookmark feature_x
> ... work work work
> $ hg commit -m 'some feature_x code'
> ... push to some canonical repo for others to see
> $ hg push -B feature_x -f // -f most likely needed as bookmarks are simply
> 'named heads' - but it doesn't matter for Jenkins
> Now some other collaborator:
> $ hg incoming -B // shows that there is a new bookmark, 'feature_x'
> $ hg pull -B feature_x
> and they can now start working on this bookmark ('lightweight branch').
> I tried simply changing the value of the 'branch' field in my project
> configuration, but it doesn't work. But it is very close. What seems not to
> work is the fact that Jenkins doesn't know the '-B' switch, and doesn't know
> that I want to import the bookmark. What Jenkins does is this (shortened a
> little, the template is not used):
> $ hg incoming --quiet --bundle hg.bundle --template "..." --rev feature_x
> $ hg unbundle hg.bundle
> adding changesets
> adding manifests
> adding file changes
> added 1 changesets with 1 changes to 1 files (+1 heads)
> (run 'hg heads' to see heads, 'hg merge' to merge)
> $ hg update --clean --rev feature_x
> abort: unknown revision 'test'!
> This means that the incoming changes were found with the bookmark name and
> were pulled, but the bookmark itself wasn't imported, and doesn't exist
> locally - and update fails. With the '-B' switch, it would work fine (tested
> on the command line):
> $ hg incoming --quiet --bundle hg.bundle --template "..." --rev feature_x
> $ hg unbundle hg.bundle
> adding changesets
> adding manifests
> adding file changes
> added 1 changesets with 1 changes to 1 files (+1 heads)
> (run 'hg heads' to see heads, 'hg merge' to merge)
> $ hg pull -B feature_x // <- that's the missing
> link
> no changes found
> importing bookmark test
> $ hg update --clean --rev feature_x
> 1 files updated, 0 files merged, 0 files removed, 0 files unresolved
> With the single call to pull the bookmark (which effectively imports it)
> makes it work!
> Of course, there could be a mix of branch and bookmark, so the 'incoming'
> should use the branch name, and if and only if a bookmark is specified, a
> 'pull -B ' should be issued, and the update should use the
> bookmark and not the branch. This means there should be some additional field
> for the bookmark, and some additional logic, but not that much, I think?
> I will take a look at the source code on GitHub to see if maybe I could help
> you with that, if you are interested?
> I as setting it as critical, as it has the potential to influence the
> decision whether we can use Jenkins or not for this project. Naturally, you
> are the bosses so feel free to squash it.
> As a side note: wha
[JIRA] (JENKINS-12680) onOffline in ComputerListener not getting called when node is taken offline
[ https://issues.jenkins-ci.org/browse/JENKINS-12680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158825#comment-158825 ] dogfood commented on JENKINS-12680: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [jenkins_main_trunk #1523|http://ci.jenkins-ci.org/job/jenkins_main_trunk/1523/] [FIXED JENKINS-12680] the onOffline method wasn't called for abrupt client termination (Revision 4378e878ae327a954911ae4ef84679e0060b63e2) Result = SUCCESS Kohsuke Kawaguchi : [4378e878ae327a954911ae4ef84679e0060b63e2|https://github.com/jenkinsci/jenkins/commit/4378e878ae327a954911ae4ef84679e0060b63e2] Files : * test/src/test/java/hudson/slaves/JNLPLauncherTest.java * core/src/main/java/hudson/slaves/SlaveComputer.java * changelog.html > onOffline in ComputerListener not getting called when node is taken offline > --- > > Key: JENKINS-12680 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12680 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: OS: All >Reporter: Jens Christensen > Labels: ComputerListener, jenkins, onOffline, slave > > In ComputerListener, onOffline is only called if a node is taken down with > the disconnect link in jenkins, any other cause for a node to go offline, > makes the call postponed until the master is taken down. -- 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-12694) Zentimestamp plugin v3.0 no longer compatible with hudson.
Christopher Stephens created JENKINS-12694: -- Summary: Zentimestamp plugin v3.0 no longer compatible with hudson. Key: JENKINS-12694 URL: https://issues.jenkins-ci.org/browse/JENKINS-12694 Project: Jenkins Issue Type: Bug Components: zentimestamp Reporter: Christopher Stephens Assignee: gbois As of version 3.0 the zen timestamp plugin appears to be no longer compatible with Hudson. I tested it in a stand alone Hudson instance (no additional plugins) against Hudson versions 2.2.0 and 2.1.0 and noticed that the BUILD_ID variable is not getting replaced by the correct pattern. I rolled back to version 2.2 of the plugin which appears to still be compatible with both versions of Hudson above. I did not see any errors in the logs when running projects with the plugin activated, only that the environment variable contained the original timestamp formatting. -- 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-12695) Upload fails when using Fortify 3.30
bbonn created JENKINS-12695: --- Summary: Upload fails when using Fortify 3.30 Key: JENKINS-12695 URL: https://issues.jenkins-ci.org/browse/JENKINS-12695 Project: Jenkins Issue Type: Bug Components: fortify360 Environment: Windows Server 2008 Jenkins ver. 1.409.2 Fortify ver. 3.30 Reporter: bbonn Assignee: samngms Hi, We have been using the Fortify360 plugin for a while, works like a charm. But we have recently upgraded to Fortify 3.30. We noticed that if 3.30 is on the system Path the plugin will look there for the 4 files it needs to do the upload (i.e. wsclient.jar,wsobjects.jar, common.jar,common13.jar). Problem is they are not there (in core/lib/) in 3.30, at least they are not named the same. So, if we leave the Version field blank in the global Jenkins config, or we enter 3.30 we get an error that the plugin can't find the .jars it needs. We can get around it by using 3.30 to do the scans but entering 2.65 for the Jars Path for the upload. But still seems like it should be fixed going forward. Here is an example of the error: Error uploading to F360 Server: http://ourfortifyserver/f360 java.lang.RuntimeException: Invalid JarsPath: N:\Program Files (x86)\Fortify Software\HP Fortify v3.30\Core\lib, can't locate common.jar or common13.jar Let me know if you need any more info or need me to try anything. I am glad to help. Thanks! Bernie Bonn -- 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-12696) Cron thread can get stuck making a connection
[ https://issues.jenkins-ci.org/browse/JENKINS-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158827#comment-158827 ] James Blair commented on JENKINS-12696: --- Here's the thread dump for the whole system (which may be more readable): http://paste.openstack.org/show/4748/ > Cron thread can get stuck making a connection > - > > Key: JENKINS-12696 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12696 > Project: Jenkins > Issue Type: Bug > Components: url-change-trigger > Environment: Jenkins 1.450, url-change-trigger 1.2 >Reporter: James Blair >Assignee: dfabulich > > Polling an HTTPS URL for changes can cause the entire cron thread to get > stuck during a connection attempt. Here is a thread dump of a cron thread > that was stuck for more than 5 hours (and likely to be stuck indefinitely): > "Jenkins cron thread" Id=22 Group=main RUNNABLE (in native) > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:146) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:312) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:424) > at sun.security.ssl.InputRecord.read(InputRecord.java:379) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:850) > - locked java.lang.Object@2213b7b7 > at > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1190) > - locked java.lang.Object@3c8260db > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1217) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1201) > at > sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:440) > at > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) > - locked sun.net.www.protocol.https.DelegateHttpsURLConnection@2fb65e1d > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > - locked sun.net.www.protocol.https.HttpsURLConnectionImpl@43998053 > at java.net.URL.openStream(URL.java:1029) > at com.redfin.hudson.UrlChangeTrigger.run(UrlChangeTrigger.java:63) > at hudson.triggers.Trigger.checkTriggers(Trigger.java:250) > at hudson.triggers.Trigger$Cron.doRun(Trigger.java:198) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.TimerThread.mainLoop(Timer.java:534) > at java.util.TimerThread.run(Timer.java:484) -- 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-12696) Cron thread can get stuck making a connection
James Blair created JENKINS-12696: - Summary: Cron thread can get stuck making a connection Key: JENKINS-12696 URL: https://issues.jenkins-ci.org/browse/JENKINS-12696 Project: Jenkins Issue Type: Bug Components: url-change-trigger Environment: Jenkins 1.450, url-change-trigger 1.2 Reporter: James Blair Assignee: dfabulich Polling an HTTPS URL for changes can cause the entire cron thread to get stuck during a connection attempt. Here is a thread dump of a cron thread that was stuck for more than 5 hours (and likely to be stuck indefinitely): "Jenkins cron thread" Id=22 Group=main RUNNABLE (in native) at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:146) at sun.security.ssl.InputRecord.readFully(InputRecord.java:312) at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:424) at sun.security.ssl.InputRecord.read(InputRecord.java:379) at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:850) - locked java.lang.Object@2213b7b7 at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1190) - locked java.lang.Object@3c8260db at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1217) at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1201) at sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:440) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) - locked sun.net.www.protocol.https.DelegateHttpsURLConnection@2fb65e1d at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) - locked sun.net.www.protocol.https.HttpsURLConnectionImpl@43998053 at java.net.URL.openStream(URL.java:1029) at com.redfin.hudson.UrlChangeTrigger.run(UrlChangeTrigger.java:63) at hudson.triggers.Trigger.checkTriggers(Trigger.java:250) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:198) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.TimerThread.mainLoop(Timer.java:534) at java.util.TimerThread.run(Timer.java:484) -- 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-12696) Cron thread can get stuck making a connection
[ https://issues.jenkins-ci.org/browse/JENKINS-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158828#comment-158828 ] James Blair commented on JENKINS-12696: --- It appears we're using the deprecated url-change-trigger, however it looks like urltrigger would also be susceptible to the same problem. > Cron thread can get stuck making a connection > - > > Key: JENKINS-12696 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12696 > Project: Jenkins > Issue Type: Bug > Components: url-change-trigger > Environment: Jenkins 1.450, url-change-trigger 1.2 >Reporter: James Blair >Assignee: dfabulich > > Polling an HTTPS URL for changes can cause the entire cron thread to get > stuck during a connection attempt. Here is a thread dump of a cron thread > that was stuck for more than 5 hours (and likely to be stuck indefinitely): > "Jenkins cron thread" Id=22 Group=main RUNNABLE (in native) > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:146) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:312) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:424) > at sun.security.ssl.InputRecord.read(InputRecord.java:379) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:850) > - locked java.lang.Object@2213b7b7 > at > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1190) > - locked java.lang.Object@3c8260db > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1217) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1201) > at > sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:440) > at > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) > - locked sun.net.www.protocol.https.DelegateHttpsURLConnection@2fb65e1d > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > - locked sun.net.www.protocol.https.HttpsURLConnectionImpl@43998053 > at java.net.URL.openStream(URL.java:1029) > at com.redfin.hudson.UrlChangeTrigger.run(UrlChangeTrigger.java:63) > at hudson.triggers.Trigger.checkTriggers(Trigger.java:250) > at hudson.triggers.Trigger$Cron.doRun(Trigger.java:198) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.TimerThread.mainLoop(Timer.java:534) > at java.util.TimerThread.run(Timer.java:484) -- 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-12697) Allow links tied to projects to use security
alexlombardi created JENKINS-12697: -- Summary: Allow links tied to projects to use security Key: JENKINS-12697 URL: https://issues.jenkins-ci.org/browse/JENKINS-12697 Project: Jenkins Issue Type: Improvement Components: sidebar-link Affects Versions: current Environment: Any Reporter: alexlombardi Assignee: Alan Harder Fix For: current Allow sidebar links in projects to use project based security to display or not for users. -- 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-12696) Cron thread can get stuck making a connection
[ https://issues.jenkins-ci.org/browse/JENKINS-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] SCM/JIRA link daemon resolved JENKINS-12696. Resolution: Fixed > Cron thread can get stuck making a connection > - > > Key: JENKINS-12696 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12696 > Project: Jenkins > Issue Type: Bug > Components: url-change-trigger > Environment: Jenkins 1.450, url-change-trigger 1.2 >Reporter: James Blair >Assignee: dfabulich > > Polling an HTTPS URL for changes can cause the entire cron thread to get > stuck during a connection attempt. Here is a thread dump of a cron thread > that was stuck for more than 5 hours (and likely to be stuck indefinitely): > "Jenkins cron thread" Id=22 Group=main RUNNABLE (in native) > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:146) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:312) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:424) > at sun.security.ssl.InputRecord.read(InputRecord.java:379) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:850) > - locked java.lang.Object@2213b7b7 > at > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1190) > - locked java.lang.Object@3c8260db > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1217) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1201) > at > sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:440) > at > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) > - locked sun.net.www.protocol.https.DelegateHttpsURLConnection@2fb65e1d > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > - locked sun.net.www.protocol.https.HttpsURLConnectionImpl@43998053 > at java.net.URL.openStream(URL.java:1029) > at com.redfin.hudson.UrlChangeTrigger.run(UrlChangeTrigger.java:63) > at hudson.triggers.Trigger.checkTriggers(Trigger.java:250) > at hudson.triggers.Trigger$Cron.doRun(Trigger.java:198) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.TimerThread.mainLoop(Timer.java:534) > at java.util.TimerThread.run(Timer.java:484) -- 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-12696) Cron thread can get stuck making a connection
[ https://issues.jenkins-ci.org/browse/JENKINS-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158829#comment-158829 ] SCM/JIRA link daemon commented on JENKINS-12696: Code changed in jenkins User: Monty Taylor Path: src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java http://jenkins-ci.org/commit/urltrigger-plugin/d2a447a4ea4aad880493e5efb60f297ec2033f94 Log: Fix JENKINS-12696 Add a timeout to the network activity. > Cron thread can get stuck making a connection > - > > Key: JENKINS-12696 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12696 > Project: Jenkins > Issue Type: Bug > Components: url-change-trigger > Environment: Jenkins 1.450, url-change-trigger 1.2 >Reporter: James Blair >Assignee: dfabulich > > Polling an HTTPS URL for changes can cause the entire cron thread to get > stuck during a connection attempt. Here is a thread dump of a cron thread > that was stuck for more than 5 hours (and likely to be stuck indefinitely): > "Jenkins cron thread" Id=22 Group=main RUNNABLE (in native) > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:146) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:312) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:424) > at sun.security.ssl.InputRecord.read(InputRecord.java:379) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:850) > - locked java.lang.Object@2213b7b7 > at > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1190) > - locked java.lang.Object@3c8260db > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1217) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1201) > at > sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:440) > at > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) > - locked sun.net.www.protocol.https.DelegateHttpsURLConnection@2fb65e1d > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > - locked sun.net.www.protocol.https.HttpsURLConnectionImpl@43998053 > at java.net.URL.openStream(URL.java:1029) > at com.redfin.hudson.UrlChangeTrigger.run(UrlChangeTrigger.java:63) > at hudson.triggers.Trigger.checkTriggers(Trigger.java:250) > at hudson.triggers.Trigger$Cron.doRun(Trigger.java:198) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.TimerThread.mainLoop(Timer.java:534) > at java.util.TimerThread.run(Timer.java:484) -- 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-12696) Cron thread can get stuck making a connection
[ https://issues.jenkins-ci.org/browse/JENKINS-12696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158830#comment-158830 ] SCM/JIRA link daemon commented on JENKINS-12696: Code changed in jenkins User: Kohsuke Kawaguchi Path: src/main/java/org/jenkinsci/plugins/urltrigger/URLTrigger.java http://jenkins-ci.org/commit/urltrigger-plugin/0681284704753132857a7daf476a02a16fc1f4be Log: Merge pull request #1 from emonty/master [FIXED JENKINS-12696] Looks good to me. Compare: https://github.com/jenkinsci/urltrigger-plugin/compare/b862ef3...0681284 > Cron thread can get stuck making a connection > - > > Key: JENKINS-12696 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12696 > Project: Jenkins > Issue Type: Bug > Components: url-change-trigger > Environment: Jenkins 1.450, url-change-trigger 1.2 >Reporter: James Blair >Assignee: dfabulich > > Polling an HTTPS URL for changes can cause the entire cron thread to get > stuck during a connection attempt. Here is a thread dump of a cron thread > that was stuck for more than 5 hours (and likely to be stuck indefinitely): > "Jenkins cron thread" Id=22 Group=main RUNNABLE (in native) > at java.net.SocketInputStream.socketRead0(Native Method) > at java.net.SocketInputStream.read(SocketInputStream.java:146) > at sun.security.ssl.InputRecord.readFully(InputRecord.java:312) > at sun.security.ssl.InputRecord.readV3Record(InputRecord.java:424) > at sun.security.ssl.InputRecord.read(InputRecord.java:379) > at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:850) > - locked java.lang.Object@2213b7b7 > at > sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1190) > - locked java.lang.Object@3c8260db > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1217) > at > sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1201) > at > sun.net.www.protocol.https.HttpsClient.afterConnect(HttpsClient.java:440) > at > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:185) > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1139) > - locked sun.net.www.protocol.https.DelegateHttpsURLConnection@2fb65e1d > at > sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) > - locked sun.net.www.protocol.https.HttpsURLConnectionImpl@43998053 > at java.net.URL.openStream(URL.java:1029) > at com.redfin.hudson.UrlChangeTrigger.run(UrlChangeTrigger.java:63) > at hudson.triggers.Trigger.checkTriggers(Trigger.java:250) > at hudson.triggers.Trigger$Cron.doRun(Trigger.java:198) > at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) > at java.util.TimerThread.mainLoop(Timer.java:534) > at java.util.TimerThread.run(Timer.java:484) -- 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-12648) TestNG 0.31 does not show test results when tests failed
[ https://issues.jenkins-ci.org/browse/JENKINS-12648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158831#comment-158831 ] Jeff Weiss commented on JENKINS-12648: -- nalin, I would think that testng plugin should fail a job that would have otherwise passed, if there is no result file (which it does). And it should mark a job as unstable that otherwise would be success, if the result file is there and contains failed tests (which it also does). But seems like it should always look - even when the job is failed or aborted, the user might want to see the test results, if there are any. > TestNG 0.31 does not show test results when tests failed > > > Key: JENKINS-12648 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12648 > Project: Jenkins > Issue Type: Bug > Components: testng >Affects Versions: current >Reporter: Peter Lustig >Assignee: nalin_makar >Priority: Critical > Labels: testng > > Whenever I use the TestNG-Plugin 0.31 it only shows reports if the tests > passed. But if the failey there are no test results. If I downgrade to 0.26 > for example everthing works fine. Both the failed and passed test results are > displayed. Please fix this, would be very important. 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-12524) Compliance with Multiple SCMs Plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-12524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158833#comment-158833 ] dogfood commented on JENKINS-12524: --- Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png! [plugins_github-plugin #536|http://ci.jenkins-ci.org/job/plugins_github-plugin/536/] [JENKINS-12524] Compliance with Multiple SCMs Plugin (Revision da993ac43749097cccd6f3546d980ccc76786c7f) Result = SUCCESS jcarsique : [da993ac43749097cccd6f3546d980ccc76786c7f|https://github.com/jenkinsci/github-plugin/commit/da993ac43749097cccd6f3546d980ccc76786c7f] Files : * src/main/java/com/cloudbees/jenkins/GitHubPushTrigger.java * pom.xml > Compliance with Multiple SCMs Plugin > > > Key: JENKINS-12524 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12524 > Project: Jenkins > Issue Type: Improvement > Components: github >Reporter: jcarsique > > It would be nice to make the GitHub hook triggering work when using Multiple > SCMs Plugin for making one job retrieve multiple GitHub repositories. -- 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-12487) Global configuration not saved since Jenkins 1.445
[
https://issues.jenkins-ci.org/browse/JENKINS-12487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158832#comment-158832
]
dogfood commented on JENKINS-12487:
---
Integrated in !http://ci.jenkins-ci.org/images/16x16/blue.png!
[plugins_github-plugin
#536|http://ci.jenkins-ci.org/job/plugins_github-plugin/536/]
[FIXED JENKINS-12487] Global configuration not saved since Jenkins 1.445
(Revision 685f5b6f3f8fdd7539778dc66f6ced2345ae6eb6)
Result = SUCCESS
Seiji Sogabe :
[685f5b6f3f8fdd7539778dc66f6ced2345ae6eb6|https://github.com/jenkinsci/github-plugin/commit/685f5b6f3f8fdd7539778dc66f6ced2345ae6eb6]
Files :
* pom.xml
* src/main/java/com/cloudbees/jenkins/GitHubPushTrigger.java
> Global configuration not saved since Jenkins 1.445
> --
>
> Key: JENKINS-12487
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12487
> Project: Jenkins
> Issue Type: Bug
> Components: github
> Environment: Jenkins 1.448
> Github plugin 1.0
>Reporter: sogabe
>Assignee: sogabe
>
> Since Jenkins 1.445, Global configurations of this plugin (hookurl,
> credentials ...) are not saved collectly.
> Json in 1.448, which is sent to server is diffrent from the one in 1.444.
> 1.444:
> {code}
> "com-cloudbees-jenkins-GitHubPushTrigger": {"hookMode": {"value": "auto"},
> "hookUrl": {"url": "http://bacons.ddojp/github-webhook/"}, "credentials":
> {"username": "ssogabe", "password": "XX"}}}
> {code}
> 1.448
> {code}
> "com-cloudbees-jenkins-GitHubPushTrigger": {"hookMode": {"value": "auto",
> "hookUrl": {"url": "http://bacons.ddojp/github-webhook/"}, "credentials":
> {"username": "ssogabe", "password": "X"
> {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-12698) Is it possible to use post build task plugin to trigger the same job back again
Surya NV created JENKINS-12698: -- Summary: Is it possible to use post build task plugin to trigger the same job back again Key: JENKINS-12698 URL: https://issues.jenkins-ci.org/browse/JENKINS-12698 Project: Jenkins Issue Type: Task Components: postbuild-task Environment: Jenkins 1.441 Reporter: Surya NV Is it possible to re-trigger the same job either using the post build task or some other means? Any ideas? Please let me know. -- 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-12699) Temp upload files from file param not removed after transferred to slave
Anthony Wat created JENKINS-12699: - Summary: Temp upload files from file param not removed after transferred to slave Key: JENKINS-12699 URL: https://issues.jenkins-ci.org/browse/JENKINS-12699 Project: Jenkins Issue Type: Bug Components: core Environment: OS: Linux ara02 2.6.9-103.ELsmp #1 SMP Fri Nov 11 14:34:02 EST 2011 i686 i686 i386 GNU/Linux JRE: java version "1.6.0_16" Jenkins: 1.442 Reporter: Anthony Wat I currently have a master-slave configuration on Jenkins 1.442 running on a Linux box. Lately I started using file parameter for one of my jobs, and noticed that disk space was decreasing rather quickly on the master system. Upon examination it turns out that file parameter is creating files under /tmp, with a naming convention upload_*.tmp, when the file parameters are uploaded. I've done some experiment and noticed that: - If the job is running on master, the tmp file is moved into the workspace correctly. - If the job is running on slave, the tmp file is uploaded to the slave workspace correctly, but the upload_*.tmp file remains in /tmp. I am using a file parameter for a 100 MB file, so it is very easy to collect GBs worth of temporary files, until my master runs out of disk space. For now I have added a cron job to delete these upload_*.tmp files, but it's not safe if the script runs at the same time as a user uploading a file param for a job. Let me know what other debugging information I need to provide, if any. Please investigate, 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-10832) make testng reporter-output field viewable from testng-plugin generated reports
[ https://issues.jenkins-ci.org/browse/JENKINS-10832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158834#comment-158834 ] Matthew Walters commented on JENKINS-10832: --- I'd also like to see this functionality implemented, thanks. > make testng reporter-output field viewable from testng-plugin generated > reports > > > Key: JENKINS-10832 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10832 > Project: Jenkins > Issue Type: New Feature > Components: testng >Reporter: Denali Lumma >Assignee: nalin_makar >Priority: Minor > > I would like to see the > values on the testng-plugin reports, especially on the test method result > page view. > Here is a description of the test client code and how it is used: > http://testng.org/doc/documentation-main.html#logging-reporter-api > The testng-results.xml file generates this xml: > > > Important test message which should be recorded! > Another important test message which should be recorded in the test > results! > > ... > Please make this viewable from the Jenkins testng-plugin generated results > pages if it exists in the testng-results.xml file. In my scenario, I need > this only for the method results view, but I could see this as useful for the > groups, class, and package results views as well. > 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-12691) Property variable not set if using a property file
[
https://issues.jenkins-ci.org/browse/JENKINS-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158835#comment-158835
]
gbois commented on JENKINS-12691:
-
I think it's due that ${LD_LIBRARY_PATH} is not already defined.
Could you try LD_LIBRARY_PATH=${AVARIABLE}/lib?
> Property variable not set if using a property file
> --
>
> Key: JENKINS-12691
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12691
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
>Affects Versions: current
> Environment: Linux (RedHat), Jenkinx 1.446, EnvInject 1.17
>Reporter: Bruno L
>Assignee: gbois
>
> I am trying to inject environment variables to the build process after SCM
> checkout. If I point to a .properties file in the workspace some variables do
> not get set properly while others are OK. If I copy/paste the content of the
> file into the "Properties Content" box in the Jenkins project configuration
> page then it works fine for all variables.
> For example
>AVARIABLE=/some/path
>PATH=/opt/bin:${AVARIABLE}/bin:${PATH}
>LD_LIBRARY_PATH=${AVARIABLE}/lib:${LD_LIBRARY_PATH}
> where I already have some existing directories in my $PATH. If I save this in
> a file and point to it then I get errors :
> [EnvInject] - Variables injected successfully.
> [EnvInject] - Unset unresolved 'PATH' variable.
> [EnvInject] - Unset unresolved 'LD_LIBRARY_PATH' variable.
> But the same 3 lines work fine if I enter them directly in the "Properties
> Content" dialog box
--
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-8581) Error when using track svn plugin
[ https://issues.jenkins-ci.org/browse/JENKINS-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat updated JENKINS-8581: - Assignee: gbois Component/s: xunit > Error when using track svn plugin > - > > Key: JENKINS-8581 > URL: https://issues.jenkins-ci.org/browse/JENKINS-8581 > Project: Jenkins > Issue Type: Bug > Components: subversion, xunit >Affects Versions: current > Environment: linux 64 bit > hudson .395 >Reporter: davidkarlsen >Assignee: gbois > > I get: > when under the dialog window where I enter the name of the job which is used > for svn revision tracking. > Status Code: 500 > Exception: > Stacktrace: > java.lang.UnsupportedOperationException: The descriptor registry with the > called getId() method is not used. The descriptor redefines its own > getInputMetric() method. > at > com.thalesgroup.hudson.plugins.xunit.types.CustomType$CustomInputMetricDescriptor.getId(CustomType.java:66) > at hudson.model.Hudson.getDescriptor(Hudson.java:955) > at hudson.model.Hudson.getDescriptorByName(Hudson.java:968) > at hudson.model.AbstractItem.getDescriptorByName(AbstractItem.java:375) > at sun.reflect.GeneratedMethodAccessor348.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:282) > at org.kohsuke.stapler.MetaClass$7.doDispatch(MetaClass.java:242) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640) > at org.kohsuke.stapler.MetaClass$7.doDispatch(MetaClass.java:242) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640) > at org.kohsuke.stapler.MetaClass$7.doDispatch(MetaClass.java:242) > at > org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) > at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:562) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:640) > at org.kohsuke.stapler.Stapler.invoke(Stapler.java:478) > at org.kohsuke.stapler.Stapler.service(Stapler.java:160) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) > at winstone.ServletConfiguration.execute(ServletConfiguration.java:249) > at winstone.RequestDispatcher.forward(RequestDispatcher.java:335) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:378) > at > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:94) > at > hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:52) > at > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) > at > net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:153) > at > net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:131) > at > net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:73) > at > org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:69) > at > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) > at > hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:64) > at > hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:97) > at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:86) > at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) > at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) > at winstone.FilterConfiguration.execute(FilterConfiguration.java:195) > at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:368) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) > at > hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) > at > hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) > at > org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) > at > hudson.security
[JIRA] (JENKINS-12691) Property variable not set if using a property file
[
https://issues.jenkins-ci.org/browse/JENKINS-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Work on JENKINS-12691 started by gbois.
> Property variable not set if using a property file
> --
>
> Key: JENKINS-12691
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12691
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
>Affects Versions: current
> Environment: Linux (RedHat), Jenkinx 1.446, EnvInject 1.17
>Reporter: Bruno L
>Assignee: gbois
>
> I am trying to inject environment variables to the build process after SCM
> checkout. If I point to a .properties file in the workspace some variables do
> not get set properly while others are OK. If I copy/paste the content of the
> file into the "Properties Content" box in the Jenkins project configuration
> page then it works fine for all variables.
> For example
>AVARIABLE=/some/path
>PATH=/opt/bin:${AVARIABLE}/bin:${PATH}
>LD_LIBRARY_PATH=${AVARIABLE}/lib:${LD_LIBRARY_PATH}
> where I already have some existing directories in my $PATH. If I save this in
> a file and point to it then I get errors :
> [EnvInject] - Variables injected successfully.
> [EnvInject] - Unset unresolved 'PATH' variable.
> [EnvInject] - Unset unresolved 'LD_LIBRARY_PATH' variable.
> But the same 3 lines work fine if I enter them directly in the "Properties
> Content" dialog box
--
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-12586) cvs-plugin fails to read old changelog files
[ https://issues.jenkins-ci.org/browse/JENKINS-12586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158836#comment-158836 ] A Geller commented on JENKINS-12586: I'd like to point out, that this issue affects me as well. Jenkins initiates plenty of cvs requests. Unfortunately the number of cvs processes increases steadily, resulting in a non-responding Jenkins server. Env.: Jenkins 1.450 & CVS Plugin 2.0 > cvs-plugin fails to read old changelog files > > > Key: JENKINS-12586 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12586 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: jenkins 1.449, cvs-plugin 2.0 >Reporter: Alex Lehmann >Priority: Minor > > after updating to cvs-plugin 2.0, I get an exception when parsing the old > changelog files that were written by the previous version of the plugin, e.g. > Caused by: java.text.ParseException: Unparseable date: "2011-12-14" > at java.text.DateFormat.parse(DateFormat.java:337) > at > hudson.scm.CVSChangeLogSet$CVSChangeLog.setDate(CVSChangeLogSet.java:232) > ... 34 more > the corresponding changelog entry looks like this > > > 2011-12-14 > 23:26 -- 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-12691) Property variable not set if using a property file
[
https://issues.jenkins-ci.org/browse/JENKINS-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158837#comment-158837
]
SCM/JIRA link daemon commented on JENKINS-12691:
Code changed in jenkins
User: Gregory Boissinot
Path:
src/main/java/org/jenkinsci/plugins/envinject/service/PropertiesLoader.java
src/main/java/org/jenkinsci/plugins/envinject/service/PropertiesVariablesRetriever.java
http://jenkins-ci.org/commit/envinject-plugin/83da03b83af3e0dbf96a5d0a6054e105f408da86
Log:
Fix JENKINS-12691
> Property variable not set if using a property file
> --
>
> Key: JENKINS-12691
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12691
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
>Affects Versions: current
> Environment: Linux (RedHat), Jenkinx 1.446, EnvInject 1.17
>Reporter: Bruno L
>Assignee: gbois
>
> I am trying to inject environment variables to the build process after SCM
> checkout. If I point to a .properties file in the workspace some variables do
> not get set properly while others are OK. If I copy/paste the content of the
> file into the "Properties Content" box in the Jenkins project configuration
> page then it works fine for all variables.
> For example
>AVARIABLE=/some/path
>PATH=/opt/bin:${AVARIABLE}/bin:${PATH}
>LD_LIBRARY_PATH=${AVARIABLE}/lib:${LD_LIBRARY_PATH}
> where I already have some existing directories in my $PATH. If I save this in
> a file and point to it then I get errors :
> [EnvInject] - Variables injected successfully.
> [EnvInject] - Unset unresolved 'PATH' variable.
> [EnvInject] - Unset unresolved 'LD_LIBRARY_PATH' variable.
> But the same 3 lines work fine if I enter them directly in the "Properties
> Content" dialog box
--
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-12691) Property variable not set if using a property file
[
https://issues.jenkins-ci.org/browse/JENKINS-12691?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
gbois resolved JENKINS-12691.
-
Resolution: Fixed
I'm sorry. I fixed it in 1.18
> Property variable not set if using a property file
> --
>
> Key: JENKINS-12691
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12691
> Project: Jenkins
> Issue Type: Bug
> Components: envinject
>Affects Versions: current
> Environment: Linux (RedHat), Jenkinx 1.446, EnvInject 1.17
>Reporter: Bruno L
>Assignee: gbois
>
> I am trying to inject environment variables to the build process after SCM
> checkout. If I point to a .properties file in the workspace some variables do
> not get set properly while others are OK. If I copy/paste the content of the
> file into the "Properties Content" box in the Jenkins project configuration
> page then it works fine for all variables.
> For example
>AVARIABLE=/some/path
>PATH=/opt/bin:${AVARIABLE}/bin:${PATH}
>LD_LIBRARY_PATH=${AVARIABLE}/lib:${LD_LIBRARY_PATH}
> where I already have some existing directories in my $PATH. If I save this in
> a file and point to it then I get errors :
> [EnvInject] - Variables injected successfully.
> [EnvInject] - Unset unresolved 'PATH' variable.
> [EnvInject] - Unset unresolved 'LD_LIBRARY_PATH' variable.
> But the same 3 lines work fine if I enter them directly in the "Properties
> Content" dialog box
--
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-12586) cvs-plugin fails to read old changelog files
[ https://issues.jenkins-ci.org/browse/JENKINS-12586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158836#comment-158836 ] A Geller edited comment on JENKINS-12586 at 2/9/12 9:56 PM: I'd like to point out, that this issue affects me as well. Jenkins initiates plenty of cvs requests. Unfortunately the number of cvs processes increases steadily, resulting in a non-responding Jenkins server. Env.: Jenkins 1.450 & CVS Plugin 2.0 The latter point has been mentioned in #JENKINS-12612 was (Author: agel07): I'd like to point out, that this issue affects me as well. Jenkins initiates plenty of cvs requests. Unfortunately the number of cvs processes increases steadily, resulting in a non-responding Jenkins server. Env.: Jenkins 1.450 & CVS Plugin 2.0 > cvs-plugin fails to read old changelog files > > > Key: JENKINS-12586 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12586 > Project: Jenkins > Issue Type: Bug > Components: cvs >Affects Versions: current > Environment: jenkins 1.449, cvs-plugin 2.0 >Reporter: Alex Lehmann >Priority: Minor > > after updating to cvs-plugin 2.0, I get an exception when parsing the old > changelog files that were written by the previous version of the plugin, e.g. > Caused by: java.text.ParseException: Unparseable date: "2011-12-14" > at java.text.DateFormat.parse(DateFormat.java:337) > at > hudson.scm.CVSChangeLogSet$CVSChangeLog.setDate(CVSChangeLogSet.java:232) > ... 34 more > the corresponding changelog entry looks like this > > > 2011-12-14 > 23:26 -- 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-3768) surefire problem w/o batch task
[ https://issues.jenkins-ci.org/browse/JENKINS-3768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-3768. -- Resolution: Incomplete No response from the reporter, so resolving as incomplete. > surefire problem w/o batch task > --- > > Key: JENKINS-3768 > URL: https://issues.jenkins-ci.org/browse/JENKINS-3768 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Platform: PC, OS: Solaris >Reporter: malachid > > We have a CxxTest report being generated in JUnit format. From the > command-line > or from a batch task the maven-surefire-report-plugin works fine with it. > However, when run with site-deploy directly in Hudson, we get a NPE (but > again, > not from Batch Task): > [INFO] Generating "Surefire Report" report. > [HUDSON] Archiving > /export/home/hudson/jobs/SAI-Trunk/workspace/trunk/sai-pipeline/pump/pom.xml > to > /export/home/hudson/jobs/SAI-Trunk/modules/com.arrisi.sai.pipeline$pump/builds/2009-05-26_11-24-57/archive/com.arrisi.sai.pipeline/pump/1.0.0.4-SNAPSHOT/pom.xml > [HUDSON] Archiving > /export/home/hudson/jobs/SAI-Trunk/workspace/.repository/com/arrisi/sai/pipeline/pump/1.0.0.4-SNAPSHOT/pump-1.0.0.4-SNAPSHOT.pom > to > /export/home/hudson/jobs/SAI-Trunk/modules/com.arrisi.sai.pipeline$pump/builds/2009-05-26_11-24-57/archive/com.arrisi.sai.pipeline/pump/1.0.0.4-20090526.182519-10/pump-1.0.0.4-SNAPSHOT.pom > [INFO] > > [ERROR] FATAL ERROR > [INFO] > > [INFO] null > [INFO] > > [INFO] Trace > java.lang.NullPointerException > at > org.apache.maven.plugins.surefire.report.TestSuiteXmlParser.characters(TestSuiteXmlParser.java:218) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.characters(AbstractSAXParser.java:538) > at > com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:463) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:807) > at > com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) > at > com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:107) > at > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) > at > com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:331) > at > org.apache.maven.plugins.surefire.report.TestSuiteXmlParser.parse(TestSuiteXmlParser.java:65) > at > org.apache.maven.plugins.surefire.report.SurefireReportParser.parseXMLReportFiles(SurefireReportParser.java:87) > at > org.apache.maven.plugins.surefire.report.SurefireReportGenerator.doGenerateReport(SurefireReportGenerator.java:57) > at > org.apache.maven.plugins.surefire.report.SurefireReportMojo.executeReport(SurefireReportMojo.java:180) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98) > at sun.reflect.GeneratedMethodAccessor65.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > hudson.maven.agent.ComponentInterceptor.invoke(ComponentInterceptor.java:47) > at > hudson.maven.agent.PluginManagerInterceptor$3.invoke(PluginManagerInterceptor.java:228) > at $Proxy9.generate(Unknown Source) > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:303) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) > at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) > at > hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) > at > org.apache.maven.lifecycle.Defau
[JIRA] (JENKINS-3820) Master: too many open files / remote file operation failed because already closed
[ https://issues.jenkins-ci.org/browse/JENKINS-3820?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-3820. -- Resolution: Incomplete No response from the reporter, so resolving as incomplete. > Master: too many open files / remote file operation failed because already > closed > - > > Key: JENKINS-3820 > URL: https://issues.jenkins-ci.org/browse/JENKINS-3820 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: nhb > > Hello, > i have the problem that after a couple of days Hudson hangs, only throwing > "too > many open files" exceptions again and again. lsof shows that there are several > thousand tmp-files in > /home/hudson/.hudson/jobs/QIS_HEAD/builds/2009-05-29_07-11-46/workspace-files/7f16be5b.tmp > They contain this stacktrace: > hudson.util.IOException2: remote file operation failed > at hudson.FilePath.act(FilePath.java:631) > at hudson.FilePath.copyTo(FilePath.java:1108) > at > hudson.plugins.tasks.util.HealthAwarePublisher.copyFilesFromSlaveToMaster(HealthAwarePublisher.java:189) > at > hudson.plugins.tasks.util.HealthAwarePublisher.perform(HealthAwarePublisher.java:145) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:372) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildStep(AbstractBuild.java:360) > at hudson.model.Build$RunnerImpl.post2(Build.java:183) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:345) > at hudson.model.Run.run(Run.java:947) > at hudson.model.Build.run(Build.java:112) > at hudson.model.ResourceController.execute(ResourceController.java:93) > at hudson.model.Executor.run(Executor.java:119) > Caused by: java.io.IOException: already closed > at hudson.remoting.Channel.send(Channel.java:370) > at hudson.remoting.Request.call(Request.java:104) > at hudson.remoting.Channel.call(Channel.java:509) > at hudson.FilePath.act(FilePath.java:626) > ... 11 more > Can't copy file from slave to master: > slave=/home/hudson/hudson/workspace/QIS_HEAD/qisserver/WEB-INF/src/generated/de/his/appserver/service/dto/gen/HisbezeichnerDtoFactory.java, > master=/home/hudson/.hudson/jobs/QIS_HEAD/builds/2009-05-29_07-11-46/workspace-files/ff810f24.tmp > Hudson is running as a master withou any executers and one slave with two > executers. -- 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
Xvnc on Mac Server with Jenkins running under tomcat
Has anyone been able to get the xvnc plugin working when running Jenkins from tomcat on a headless mac server? I get the following error FATAL: Cannot run program "vncserver" (in directory "/Library/Jenkins/jobs/flexUnitSampleCIProject/workspace"): error=2, No such file or directory java.io.IOException: Cannot run program "vncserver" (in directory "/Library/Jenkins/jobs/flexUnitSampleCIProject/workspace"): error=2, No such file or directory -- View this message in context: http://jenkins.361315.n4.nabble.com/Xvnc-on-Mac-Server-with-Jenkins-running-under-tomcat-tp4374648p4374648.html Sent from the Jenkins issues mailing list archive at Nabble.com.
[JIRA] (JENKINS-3744) Remoting infrastructure / bug in Java serialization
[ https://issues.jenkins-ci.org/browse/JENKINS-3744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-3744. -- Resolution: Incomplete No response from the reporter, so resolving as incomplete. By the way, it may well be fixed with JENKINS-5048 > Remoting infrastructure / bug in Java serialization > --- > > Key: JENKINS-3744 > URL: https://issues.jenkins-ci.org/browse/JENKINS-3744 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Platform: All, OS: All >Reporter: towler > > I created a plugin that uses the SubversionCredentialProvider extension > point. > I packaged my plug-in and installed and it worked great on the Master but I'm > getting the error below on the slaves. I read about the "Distribution > Architecture of Hudson" on the wiki but I'm not sure how to work it into my > plugin. Some guidance would be greatly appreicated. Thx, Brett > Stacetrace: > java.lang.reflect.UndeclaredThrowableException > at hudson.scm.$Proxy7.getCredential(Unknown Source) > at > hudson.scm.SubversionSCM$DescriptorImpl$SVNAuthenticationProviderImpl.requestCli > entAuthentication(SubversionSCM.java:1214) > at > org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getFirstAuthe > ntication(DefaultSVNAuthenticationManager.java:157) > at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request > (HTTPConnection.java:518) > at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request > (HTTPConnection.java:257) > at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request > (HTTPConnection.java:245) > at > org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities > (DAVConnection.java:454) > at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open > (DAVConnection.java:97) > at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection > (DAVRepository.java:665) > at > org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getLatestRevision > (DAVRepository.java:172) > at org.tmatesoft.svn.core.wc.SVNBasicClient.getRevisionNumber > (SVNBasicClient.java:479) > at org.tmatesoft.svn.core.wc.SVNBasicClient.getLocations > (SVNBasicClient.java:848) > at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository > (SVNBasicClient.java:531) > at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout > (SVNUpdateClient.java:830) > at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout > (SVNUpdateClient.java:728) > at > hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:547) > at > hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:477) > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1583) > at hudson.remoting.UserRequest.perform(UserRequest.java:103) > at hudson.remoting.UserRequest.perform(UserRequest.java:47) > at hudson.remoting.Request$2.run(Request.java:236) > 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:54) > at java.lang.Thread.run(Unknown Source) > Caused by: java.io.IOException: Remote call failed > at hudson.remoting.Channel.call(Channel.java:514) > at hudson.remoting.RemoteInvocationHandler.invoke > (RemoteInvocationHandler.java:148) > ... 28 more > Caused by: java.lang.ClassNotFoundException: > com.imsi.iss.hudson.subversion.PwMatrixSubversionCredentialProvider$PwMatrixCred > ential > at java.net.URLClassLoader$1.run(Unknown Source) > at java.security.AccessController.doPrivileged(Native Method) > at java.net.URLClassLoader.findClass(Unknown Source) > at com.sun.jnlp.JNLPClassLoader.findClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at java.lang.ClassLoader.loadClass(Unknown Source) > at java.lang.ClassLoader.loadClassInternal(Unknown Source) > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Unknown Source) > at java.io.ObjectInputStream.resolveClass(Unknown Source) > at hudson.remoting.ObjectInputStreamEx.resolveClass > (ObjectInputStreamEx.java:52) > at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source) > at java.io.ObjectIn
[JIRA] (JENKINS-3748) builds in queue for long time get rearranged
[ https://issues.jenkins-ci.org/browse/JENKINS-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] evernat resolved JENKINS-3748. -- Resolution: Incomplete No response from the reporter, so resolving as incomplete. > builds in queue for long time get rearranged > > > Key: JENKINS-3748 > URL: https://issues.jenkins-ci.org/browse/JENKINS-3748 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current > Environment: Platform: PC, OS: Windows XP >Reporter: stacia > Attachments: later_build.PNG, new_build.PNG > > > Please check out these screenshots that I'm going to attach. The problem is > that > I have one executor and several builds lined up. In reality, only a few of > those > just get run constantly because of some switching around out of order that > goes > on after builds are marked as "stuck". -- 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-12700) Create a prominent press page on the site
R. Tyler Croy created JENKINS-12700: --- Summary: Create a prominent press page on the site Key: JENKINS-12700 URL: https://issues.jenkins-ci.org/browse/JENKINS-12700 Project: Jenkins Issue Type: Task Components: www Reporter: R. Tyler Croy Assignee: R. Tyler Croy Complete with time-zone based press contacts, high level informations, etc -- 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-12536) NullPointerException in QualityCenterResultArchiver
[ https://issues.jenkins-ci.org/browse/JENKINS-12536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158843#comment-158843 ] SCM/JIRA link daemon commented on JENKINS-12536: Code changed in jenkins User: rseguy Path: src/main/java/com/michelin/cio/hudson/plugins/qc/QualityCenterResultArchiver.java http://jenkins-ci.org/commit/qc-plugin/3a2370e3455c40398af5bde997cd633f676e49b6 Log: [JENKINS-12536] NullPointerException in QualityCenterResultArchiver > NullPointerException in QualityCenterResultArchiver > --- > > Key: JENKINS-12536 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12536 > Project: Jenkins > Issue Type: Bug > Components: qc >Affects Versions: current > Environment: Jenkins 1.424 running on Linux; QTP 10.0 and HP QC 9.2 > running on a Windows Jenkins slave >Reporter: Thies Fengler >Assignee: Romain Seguy > > This error occurs if QualityCenter.getTestSetLogFiles() returns null. This > can happen if the tests did not run due to some error (which was my fault > (again, see JENKINS-12389)) on the jenkins slave. > ERROR: Publisher > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver aborted due to > exception > java.lang.NullPointerException > at java.util.ArrayList.addAll(ArrayList.java:472) > at > com.michelin.cio.hudson.plugins.qc.QualityCenterResultArchiver.perform(QualityCenterResultArchiver.java:81) > at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:682) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:657) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:635) > at hudson.model.Build$RunnerImpl.post2(Build.java:161) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:604) > at hudson.model.Run.run(Run.java:1400) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:175) -- 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-3273) Maven build aborted before execution due to SocketTimeoutException
[
https://issues.jenkins-ci.org/browse/JENKINS-3273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158844#comment-158844
]
David Dossot commented on JENKINS-3273:
---
Same problem here with Jenkins 1.449:
{code}
Started by an SCM change
Building in workspace /home/jenkins/jobs/rsb-public/workspace
Checkout:workspace / /home/jenkins/jobs/rsb-public/workspace -
hudson.remoting.LocalChannel@36b4fec5
Using strategy: Default
Checkout:workspace / /home/jenkins/jobs/rsb-public/workspace -
hudson.remoting.LocalChannel@36b4fec5
Fetching changes from 1 remote Git repository
Fetching upstream changes from *
Seen branch in repository origin/HEAD
Seen branch in repository origin/master
Commencing build of Revision a3e51b8864cba056876bcd2e9144b17232e24885
(origin/HEAD, origin/master)
Checking out Revision a3e51b8864cba056876bcd2e9144b17232e24885 (origin/HEAD,
origin/master)
No change to record in branch origin/HEAD
No change to record in branch origin/master
Parsing POMs
[workspace] $ /home/jenkins/tools/JDK_1.6/bin/java -cp
/home/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-agent-1.2.jar:/home/jenkins/tools/Maven_3/boot/plexus-classworlds-2.4.jar
org.jvnet.hudson.maven3.agent.Maven3Main /home/jenkins/tools/Maven_3
/var/lib/tomcat6/webapps/jenkins/WEB-INF/lib/remoting-2.12.jar
/home/jenkins/plugins/maven-plugin/WEB-INF/lib/maven3-interceptor-1.2.jar 56845
ERROR: Aborted Maven execution for InterruptedIOException
java.net.SocketTimeoutException: Accept timed out
at java.net.PlainSocketImpl.socketAccept(Native Method)
at
java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:375)
at java.net.ServerSocket.implAccept(ServerSocket.java:470)
at java.net.ServerSocket.accept(ServerSocket.java:438)
at
hudson.maven.AbstractMavenProcessFactory$SocketHandler$AcceptorImpl.accept(AbstractMavenProcessFactory.java:171)
at
hudson.maven.AbstractMavenProcessFactory.newProcess(AbstractMavenProcessFactory.java:227)
at hudson.maven.ProcessCache.get(ProcessCache.java:231)
at
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:708)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
at hudson.model.Run.run(Run.java:1404)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:238)
Finished: ABORTED
{code}
> Maven build aborted before execution due to SocketTimeoutException
> --
>
> Key: JENKINS-3273
> URL: https://issues.jenkins-ci.org/browse/JENKINS-3273
> Project: Jenkins
> Issue Type: Bug
> Components: maven2
>Affects Versions: current
> Environment: Platform: All, OS: Linux
>Reporter: peterandersen
>Assignee: ashlux
>
> Hi
> I have a build server that sometime abort the scheduled build with just error
> aborted - else no error messages, see example build log below.
> I have configured a logger for the fine level (logger: hudson, log level:
> fine)
> see catelina log below - no useful errors
> I have just start calling maven with -X for debug output - if maven was the
> course - but have not yet capture the error (if maven is to blame - don't
> think so)
> Any suggestions - please see logs are version data below
> Best regards
> Peter Andersen
>
> Versions:
> Hudson: 1.289
> Tomcat: 6.0.18
> java version "1.6.0_0"
> OpenJDK Runtime Environment (build 1.6.0_0-b11)
> OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)
> Maven: 2.0.9
> OS Debian 5, uname -a:
> Linux hudson 2.6.26-1-amd64 #1 SMP Sat Jan 10 17:57:00 UTC 2009 x86_64
> GNU/Linux
>
> Example aborted build:
> started
> Updating svn://svn.lenio.dk//trunk
> U ...
> A build.xml
> At revision 11963
> Parsing POMs
> [trunk] $ /usr/lib/jvm/java-6-openjdk/bin/java -Xmx768m -XX:MaxPermSize=256m
> -cp
> /home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/maven-agent-1.289.jar:/usr/share/maven2/boot/classworlds.jar
> hudson.maven.agent.Main /usr/share/maven2
> /home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/remoting-1.289.jar
> /home/sysadm/apache-tomcat-6.0.18/webapps/hudson/WEB-INF/lib/maven-interceptor-1.289.jar
> 38194
> ERROR: Aborted
> No emails were triggered.
> finished: ABORTED
> Catalina log snippet
> Mar 11, 2009 1:33:35 AM hudson.model.Queue maintain
> FINE: Queue maintenance started hudson.model.Queue@338f7701
> Mar 11, 2009 1:33:40 AM hudson.model.Queue maintain
> FINE: Queue maintenance started hudson.model.Queue@338f7701
> Mar 11, 2009 1:33:45 AM hudson.model.Queue maintain
> FINE: Queue maintenance started hudson.model.Queue@338f7701
> Mar 11,
[JIRA] (JENKINS-12701) Safe Restart checkbox from Plugin Install/Update page fails first time
apgray created JENKINS-12701: Summary: Safe Restart checkbox from Plugin Install/Update page fails first time Key: JENKINS-12701 URL: https://issues.jenkins-ci.org/browse/JENKINS-12701 Project: Jenkins Issue Type: Bug Components: core, safe-restart Affects Versions: current Environment: Windows 2003 SP2 Firefox 10.0 Reporter: apgray Assignee: jieryn Priority: Minor Fix For: current When you check the "Restart Jenkins when installation is complete and no jobs are running" checkbox on the plugin install/upgrade page it redirects the browser. This URL returns 404 first time. Refreshing the page is successful and add Jenkins restart pending to the list of tasks to work on. This probably shouldn't fail the first time. -- 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-12702) Visual Studio 2008/2010 Jenkins plugin like TFS
apgray created JENKINS-12702: Summary: Visual Studio 2008/2010 Jenkins plugin like TFS Key: JENKINS-12702 URL: https://issues.jenkins-ci.org/browse/JENKINS-12702 Project: Jenkins Issue Type: New Feature Components: core Affects Versions: current Environment: Windows Reporter: apgray Priority: Minor Fix For: current Would be good if I could kick off a Jenkins build from my Visual Studio development environment and inspect test results. this should be packaged as a Visual Studio plugin like ankhsvn (http://www.open.collab.net/downloads/subversion/thankyou_ankh.html?_=d) -- 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-12020) Doxgen Plugin crashes with java.lang.NullPointerException
[ https://issues.jenkins-ci.org/browse/JENKINS-12020?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Roland Schulz resolved JENKINS-12020. - Resolution: Duplicate https://issues.jenkins-ci.org/browse/JENKINS-10372 > Doxgen Plugin crashes with java.lang.NullPointerException > - > > Key: JENKINS-12020 > URL: https://issues.jenkins-ci.org/browse/JENKINS-12020 > Project: Jenkins > Issue Type: Bug > Components: doxygen >Affects Versions: current > Environment: Windows, Jenkins 1.442, Doxygen Plugin 0.9, > Ubuntu 11.04, Jenkins 1.443, Doxygen Plugin 0.9 >Reporter: Markus Franke >Assignee: gbois > Labels: plugin > > Dear all, > when enabling "Publish Doxygen" option in the project settings the Doxygen > Plugin crashes with java.lang.NullPointerException. The following backtrace > is generated: > ---snip--- > Publishing Doxygen HTML results. > FATAL: error > java.lang.NullPointerException > at > hudson.plugins.doxygen.DoxygenDirectoryParser$2.invoke(DoxygenDirectoryParser.java:154) > at > hudson.plugins.doxygen.DoxygenDirectoryParser$2.invoke(DoxygenDirectoryParser.java:152) > at hudson.FilePath.act(FilePath.java:783) > at hudson.FilePath.act(FilePath.java:765) > at > hudson.plugins.doxygen.DoxygenDirectoryParser.getDoxygenGeneratedDir(DoxygenDirectoryParser.java:152) > at > hudson.plugins.doxygen.DoxygenDirectoryParser.retrieveDoxygenDirectoryFromDoxyfile(DoxygenDirectoryParser.java:325) > at > hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:54) > at > hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:14) > at hudson.FilePath.act(FilePath.java:783) > at hudson.FilePath.act(FilePath.java:765) > at > hudson.plugins.doxygen.DoxygenArchiver._perform(DoxygenArchiver.java:219) > at > hudson.plugins.doxygen.DoxygenArchiver.perform(DoxygenArchiver.java:176) > at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27) > at > hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:692) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:667) > at > hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:645) > at hudson.model.Build$RunnerImpl.post2(Build.java:162) > at > hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:614) > at hudson.model.Run.run(Run.java:1429) > at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) > at hudson.model.ResourceController.execute(ResourceController.java:88) > at hudson.model.Executor.run(Executor.java:238) > Build step 'Publish Doxygen' changed build result to FAILURE > ---snap--- > It seems to me that the DoxygenDirectoryParser is fairly broken as there have > been reported quiet a lot of NullPointerExceptions in the past. However, I > think this is a new problem. > Please do not hesitate to contact me in case any further information > regarding this issue is required. -- 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-10372) Doxygen plugin NPE issue in matrix job
[ https://issues.jenkins-ci.org/browse/JENKINS-10372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158846#comment-158846 ] Roland Schulz commented on JENKINS-10372: - Do you need further Doxyfile files which cause this problem? We are experiencing the same issue and it was also reported at https://issues.jenkins-ci.org/browse/JENKINS-12020 (I just marked that as duplicate). > Doxygen plugin NPE issue in matrix job > -- > > Key: JENKINS-10372 > URL: https://issues.jenkins-ci.org/browse/JENKINS-10372 > Project: Jenkins > Issue Type: Bug > Components: doxygen > Environment: Jenkins 1.417 > doxygen plugin 0.9 >Reporter: kevincai >Assignee: gbois >Priority: Critical > > Publishing Doxygen HTML results. > FATAL: error > java.lang.NullPointerException > at > hudson.plugins.doxygen.DoxygenDirectoryParser$2.invoke(DoxygenDirectoryParser.java:154) > at > hudson.plugins.doxygen.DoxygenDirectoryParser$2.invoke(DoxygenDirectoryParser.java:152) > at hudson.FilePath.act(FilePath.java:758) > at hudson.FilePath.act(FilePath.java:740) > at > hudson.plugins.doxygen.DoxygenDirectoryParser.getDoxygenGeneratedDir(DoxygenDirectoryParser.java:152) > at > hudson.plugins.doxygen.DoxygenDirectoryParser.retrieveDoxygenDirectoryFromDoxyfile(DoxygenDirectoryParser.java:325) > at > hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:54) > at > hudson.plugins.doxygen.DoxygenDirectoryParser.invoke(DoxygenDirectoryParser.java:14) > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:1980) > at hudson.remoting.UserRequest.perform(UserRequest.java:118) > at hudson.remoting.UserRequest.perform(UserRequest.java:48) > at hudson.remoting.Request$2.run(Request.java:283) > at > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at > 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:636) > Finished: FAILURE -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11716) Renaming a job does not rename the build record root dir, for a Jenkins instance configured with this feature
[ https://issues.jenkins-ci.org/browse/JENKINS-11716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158847#comment-158847 ] Steve Roth commented on JENKINS-11716: -- This is still an issue in Jenkins 1.450 > Renaming a job does not rename the build record root dir, for a Jenkins > instance configured with this feature > - > > Key: JENKINS-11716 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11716 > Project: Jenkins > Issue Type: Bug > Components: core >Affects Versions: current >Reporter: Steve Roth > > We have a Jenkins instance (1.438) using the 'Build Record Root Directory' > feature, so we can specify an alternate directory for storing build artifacts > outside of the JENKINS HOME directory. > This generally works fine. However, I noticed that when I rename a job, I > lose the previous build records. > I see a new build record directory is created, beneath the specified 'Build > Record Root Directory'. However, the old build directory also exists, > containing the previous records. They are not moved over to the new > directory. > In other words, when the 'Build Record Root Directory' feature is enabled, > renaming a project causes the project's build records to be lost. > Current workaround is to move the build record files over and use sed to > replace the project name in them, then restart Jenkins. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12267) Failure to load many builds when Jenkins start
[
https://issues.jenkins-ci.org/browse/JENKINS-12267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158848#comment-158848
]
typek_pb commented on JENKINS-12267:
could someone provide steps for workaround? where is the 1.1.14 version
available for download?
> Failure to load many builds when Jenkins start
> --
>
> Key: JENKINS-12267
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12267
> Project: Jenkins
> Issue Type: Bug
> Components: core, git
> Environment: Debian Squeeze, amd64, Jenkins installed using the
> Debian package from pkg.jenkins-ci.org.
>Reporter: Jean-Sébastien Pédron
>Assignee: abayer
>
> When Jenkins is restarted, it fails to load most of the builds. The
> {{jenkins.log}} file contains many exceptions like this one:
> {code}hudson.util.IOException2: Unable to read
> /var/lib/jenkins/jobs/bones/builds/2011-12-30_16-42-43/build.xml
> at hudson.XmlFile.unmarshal(XmlFile.java:160)
> at hudson.model.Run.reload(Run.java:283)
> at hudson.model.Run.(Run.java:272)
> at hudson.model.AbstractBuild.(AbstractBuild.java:162)
> at hudson.model.Build.(Build.java:100)
> at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
> Method)
> at
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
> at hudson.model.AbstractProject.loadBuild(AbstractProject.java:949)
> at hudson.model.AbstractProject$1.create(AbstractProject.java:256)
> at hudson.model.AbstractProject$1.create(AbstractProject.java:254)
> at hudson.model.RunMap.load(RunMap.java:221)
> at hudson.model.AbstractProject.onLoad(AbstractProject.java:254)
> at hudson.model.Project.onLoad(Project.java:88)
> at hudson.model.Items.load(Items.java:115)
> at jenkins.model.Jenkins$14.run(Jenkins.java:2360)
> at
> org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:146)
> at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:259)
> at jenkins.model.Jenkins$5.runTask(Jenkins.java:800)
> at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:187)
> at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:94)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: com.thoughtworks.xstream.converters.ConversionException: Cannot
> deserialize object with new readObject()/writeObject() methods
> Debugging information
> class : hudson.model.FreeStyleBuild
> required-type : org.eclipse.jgit.lib.ObjectId
> path:
> /build/actions/hudson.plugins.git.util.BuildData/buildsByBranchName/entry/hudson.plugins.git.util.Build/revision/sha1
> line number : 18
> ---
> at
> com.thoughtworks.xstream.converters.reflection.SerializableConverter.doUnmarshal(SerializableConverter.java:281)
> at
> com.thoughtworks.xstream.converters.reflection.AbstractReflectionConverter.unmarshal(AbstractReflectionConverter.java:162)
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82)
> at
> com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63)
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76)
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60)
> at
> hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverter.java:290)
> at
> hudson.util.RobustReflectionConverter.doUnmarshal(RobustReflectionConverter.java:233)
> at
> hudson.util.RobustReflectionConverter.unmarshal(RobustReflectionConverter.java:180)
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:82)
> at
> com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:63)
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:76)
> at
> com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:60)
> at
> hudson.util.RobustReflectionConverter.unmarshalField(RobustReflectionConverte
[JIRA] (JENKINS-12703) jenkins and git over windows7 permission denied
adrien ruffie created JENKINS-12703: --- Summary: jenkins and git over windows7 permission denied Key: JENKINS-12703 URL: https://issues.jenkins-ci.org/browse/JENKINS-12703 Project: Jenkins Issue Type: Bug Components: git Environment: Jenkins ver. 1.450 Windows 7 Tomcat 6.0.33 ant 1.1 javadoc 1.0 Jenkins build timeout plugin 1.8 CVS Plugin 1.6 Maven Integration plugin 1.450 Subversion Plugin 1.34 Jenkins GIT plugin 1.1.15 Git Parameter Plug-In 0.1 github-api 1.16 Github Authentication plugin 0.9 GitHub plugin 1.0 Jenkins SSH Slaves plugin 0.21 Jenkins Translation Assistance plugin Reporter: adrien ruffie Assignee: abayer Hello all, I try to checkout a git project in one Jenkins build, but the following error occurs: Any one have an idea ? I think the problem is linked to my RSA public key, but I have copy/ paste in "ssh public keys" into github.com and my account I have use the id_rsa.pub into my C:\Users\a.ruffie\.jenkins Thank for reading Best regards Adrien Démarré par l'utilisateur anonymous Building in workspace C:\Users\a.ruffie\.jenkins\workspace\game-of- life-default Checkout:game-of-life-default / C:\Users\a.ruffie\.jenkins\workspace \game-of-life-default - hudson.remoting.LocalChannel@4c032069 Using strategy: Default Checkout:game-of-life-default / C:\Users\a.ruffie\.jenkins\workspace \game-of-life-default - hudson.remoting.LocalChannel@4c032069 Cloning the remote Git repository Cloning repository origin ERROR: Error cloning remote repo 'origin' : Could not clone g...@github.com:adryen31/game-of-life.git hudson.plugins.git.GitException: Could not clone g...@github.com:adryen31/game-of-life.git at hudson.plugins.git.GitAPI.clone(GitAPI.java:245) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1029) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:970) at hudson.FilePath.act(FilePath.java:788) at hudson.FilePath.act(FilePath.java:770) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:970) at hudson.model.AbstractProject.checkout(AbstractProject.java: 1195) at hudson.model.AbstractBuild $AbstractRunner.checkout(AbstractBuild.java:576) at hudson.model.AbstractBuild $AbstractRunner.run(AbstractBuild.java:465) at hudson.model.Run.run(Run.java:1409) 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: hudson.plugins.git.GitException: Error performing command: C:\Java\Git\bin\git.exe clone --progress -o origin g...@github.com:adryen31/game-of-life.git C:\Users\a.ruffie\.jenkins \workspace\game-of-life-default Command "C:\Java\Git\bin\git.exe clone --progress -o origin g...@github.com:adryen31/game-of-life.git C:\Users\a.ruffie\.jenkins \workspace\game-of-life-default" returned status code 128: Cloning into 'C:\Users\a.ruffie\.jenkins\workspace\game-of-life-default'... Permission denied (publickey). fatal: The remote end hung up unexpectedly at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:776) at hudson.plugins.git.GitAPI.access$000(GitAPI.java:38) at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:241) at hudson.plugins.git.GitAPI$1.invoke(GitAPI.java:221) at hudson.FilePath.act(FilePath.java:788) at hudson.FilePath.act(FilePath.java:770) at hudson.plugins.git.GitAPI.clone(GitAPI.java:221) ... 12 more Caused by: hudson.plugins.git.GitException: Command "C:\Java\Git\bin \git.exe clone --progress -o origin g...@github.com:adryen31/game-of- life.git C:\Users\a.ruffie\.jenkins\workspace\game-of-life-default" returned status code 128: Cloning into 'C:\Users\a.ruffie\.jenkins \workspace\game-of-life-default'... Permission denied (publickey). fatal: The remote end hung up unexpectedly at hudson.plugins.git.GitAPI.launchCommandIn(GitAPI.java:771) ... 18 more Trying next repository ERROR: Could not clone repository FATAL: Could not clone hudson.plugins.git.GitException: Could not clone at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:1041) at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:970) at hudson.FilePath.act(FilePath.java:788) at hudson.FilePath.act(FilePath.java:770) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:970) at hudson.model.AbstractProject.checkout(AbstractProject.java: 1195) at hudson.model.AbstractBuild $AbstractRunner.checkout(AbstractBuild.java:576) at hudson.model.AbstractBuild $AbstractRunner.run(AbstractBuild.java:465) at hudson.model.Run.run(Run.java:1409) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:238) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact y
