[JIRA] (JENKINS-15780) Plugin says provided key doesn't exist in file
vimil resolved JENKINS-15780 as Fixed Plugin says provided key doesn't exist in file all errors are converted to warnings. it is now also possible to specify an http url for the properties file instead of directory path Change By: vimil (08/Jan/13 6:33 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15780) Plugin says provided key doesn't exist in file
vimil started work on JENKINS-15780 Plugin says provided key doesn't exist in file Change By: vimil (08/Jan/13 6:33 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11852) Provide a field to specify the size of selection box
vimil updated JENKINS-11852 Provide a field to specify the size of selection box new field 'number of visible items' added new 'checkbox' and 'radio button' types added Change By: vimil (08/Jan/13 6:32 AM) Attachment: screenshot.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11852) Provide a field to specify the size of selection box
vimil resolved JENKINS-11852 as Fixed Provide a field to specify the size of selection box fixed in version 0.20 of plugin Change By: vimil (08/Jan/13 6:29 AM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11852) Provide a field to specify the size of selection box
vimil assigned JENKINS-11852 to vimil Provide a field to specify the size of selection box Change By: vimil (08/Jan/13 6:28 AM) Assignee: vimil This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-11852) Provide a field to specify the size of selection box
vimil started work on JENKINS-11852 Provide a field to specify the size of selection box Change By: vimil (08/Jan/13 6:29 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16001) display username who kicked off the batch task
Sud Ramasamy updated JENKINS-16001 display username who kicked off the batch task Change By: Sud Ramasamy (08/Jan/13 6:01 AM) Summary: display username who kicked off the batch - task This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16145) add confirmation page to "reload from disk" management link
Stewart Smith resolved JENKINS-16145 as Duplicate add confirmation page to "reload from disk" management link Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-15340 Change By: Stewart Smith (08/Jan/13 5:06 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13623) Over-the-Air Ad Hoc deployment of iOS applications
Jesly Varghese commented on JENKINS-13623 Over-the-Air Ad Hoc deployment of iOS applications The plugin is now available in jenkins github repo https://github.com/jenkinsci/ios-otabuilder-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16274) SFTP/SCP support
Kohsuke Kawaguchi commented on JENKINS-16274 SFTP/SCP support Yet another approach is to use "ProxyCommand=ssh -p %p jenkins.acme.com diagnose-tunnel JOBNAME" or something. This first creates an SSH connection to jenkins.acme.com and runs the diagnose-tunnel command with arguments. This can set up the relevant context, then pass on the stream to another SSH server session. The only downside is that it does double encryption. But the ProxyCommand option can be in ~/.ssh/config, and with the wildcard support in it, the end user experience can be something like: ssh JOBNAME.jenkins.acme.com This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Christopher Orr edited a comment on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" I believe I saw this too in the logs while debugging an issue a few weeks ago. But it doesn't actually cause any problems, does it? All the builds are still visible in Jenkins, right? Edit: Apparently I failed at fully reading the original post. But I'm sure I saw this on OS X, but didn't see any problems. Just that Jenkins was parsing the symlinked target directory names (i.e. the build number) as a date, then failing; the symlinks themselves (i.e. the datetime) seemed to be parsed and the builds appeared as normal. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
Christopher Orr commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39" I believe I saw this too in the logs while debugging an issue a few weeks ago. But it doesn't actually cause any problems, does it? All the builds are still visible in Jenkins, right? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Pei-Tang Huang updated JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 Stop the Jenkins slave service. Pasting the jnlp url ( http://192.168.30.95/jenkins/login?from=%2Fjenkins%2Fcomputer%2FFortify%25201%2Fslave-agent.jnlp ) in my browser and input my credential, the Jenkins slave agent starts. But after I click the File / Install as a service, the attached error message showed up to me. Change By: Pei-Tang Huang (08/Jan/13 2:31 AM) Attachment: jenkins-slave-error.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16274) SFTP/SCP support
Kohsuke Kawaguchi
commented on JENKINS-16274
SFTP/SCP support
Another possibility is to send environment variable via -oSendEnv=CONTEXT. A wrapper script needs to be provided to actually invoke it with "export CONTEXT=diagnose JOBNAME".
Yet another hack is to use remote-to-local port forwarding as the information carrying mechanism in the host name portion ("-oRemoteForward= ThisCanBeArbitraryText:1234", except ThisCanBeArbitraryText can't really be an arbitrary text because it needs to look like a host name.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16273) Slaves cannot connect to master through JNLP after upgrading to 1.498
Pei-Tang Huang updated JENKINS-16273 Slaves cannot connect to master through JNLP after upgrading to 1.498 Change By: Pei-Tang Huang (08/Jan/13 2:22 AM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16274) SFTP/SCP support
Kohsuke Kawaguchi commented on JENKINS-16274 SFTP/SCP support SFTP bootstraps itself by using the subsystem request, and there's the "-s" option in the client to send in different subsystem name. So we should be able to support something like -s "sftp diagnose JOBNAME" to let the server understand the right context. SCP doesn't use this mechanism, and the only hook is the "-S program" option to specify the path to ssh. Unfortunately, scp invokes ssh with something like "-x -o... -o... -o... – host scp -t ..." and so there's no one liner to convert this to "... – host diagnose JOBNAME scp" In both cases, these cannot be described in ~/.ssh/config, which makes this painful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16274) SFTP/SCP support
Kohsuke Kawaguchi edited a comment on JENKINS-16274 SFTP/SCP support SFTP bootstraps itself by using the subsystem request, and there's the "-s" option in the client to send in different subsystem name. So we should be able to support something like -s "sftp diagnose JOBNAME" to let the server understand the right context. SCP doesn't use this mechanism, and the only hook is the "-S program" option to specify the path to ssh. Unfortunately, scp invokes ssh with something like "-x -o... -o... -o... – host scp -t ..." and so there's no one liner to convert this to "... – host diagnose JOBNAME scp" In both cases, these cannot be described in ~/.ssh/config, which makes this painful. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16274) SFTP/SCP support
Kohsuke Kawaguchi
created JENKINS-16274
SFTP/SCP support
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
remote-terminal-access
Created:
08/Jan/13 2:02 AM
Description:
Because this plugin requires several argument ("diagnose JOBNAME") before accepting users commands, we need some more gimic to make it work with SCP and SFTP.
Project:
Jenkins
Priority:
Major
Reporter:
Kohsuke Kawaguchi
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used Change By: Johno Crawford (08/Jan/13 12:57 AM) Attachment: ivy.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used To get a better understanding of what is going on I have created a snapshot with verbose logging enabled ( https://issues.jenkins-ci.org/secure/attachment/23032/ivy.hpi ). Would you please try it out and look for log messages which differ from master and slave? Log messages starting with the following might be interesting.. Configured Ivy using custom settings Configured Ivy using default 2.1 settings Error while reading the default Ivy 2.1 settings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford updated JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used To get a better understanding of what is going on I have created a snapshot with verbose logging enabled. Would you please try it out and look for log messages which differ from master and slave? Log messages starting with the following might be interesting.. Configured Ivy using custom settings Configured Ivy using default 2.1 settings Error while reading the default Ivy 2.1 settings Change By: Johno Crawford (08/Jan/13 12:25 AM) Attachment: ivy.hpi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
Johno Crawford edited a comment on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used To get a better understanding of what is going on I have created a snapshot with verbose logging enabled ( https://issues.jenkins-ci.org/secure/attachment/23031/ivy.hpi ). Would you please try it out and look for log messages which differ from master and slave? Log messages starting with the following might be interesting.. Configured Ivy using custom settings Configured Ivy using default 2.1 settings Error while reading the default Ivy 2.1 settings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-14002) Make the git plugin support login credentials
Thomas Suckow updated JENKINS-14002 Make the git plugin support login credentials Change By: Thomas Suckow (08/Jan/13 12:00 AM) Summary: Make the git pluing plugin support login credentials This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted That's the one...couldn't remember what its labeled as. Please see the wiki page (https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin) for more information on the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted I'm not seeing the email-ext plugin, only "Editable Email Notification". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted There should be a drop-down for post-build actions. You select the email-ext plugin (Extended Email Publisher) from there and then configure for your needs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Ok, so how do I enable it for the project? I see no checkbox or anything related to email-ext on the project configure page, other than the Email Notification section, which only has a field for recipients and checkboxes for when to send emails. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Yes, they both can be installed, but unless you have it configured on the PROJECT page, it won't be used. Your config shows email-ext is not being used. The hudson.plugins.emailext.ExtendedEmailPublisher.xml file is for the GLOBAL configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted And yet it shows up under the Manage Plugins page as being installed, not to mention it shows up on the config page. Also, the hudson.plugins.emailext.ExtendedEmailPublisher.xml file gets updated whenever I change any of the email extension settings. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12563) Build multiple configuration
Daniel Brooks edited a comment on JENKINS-12563 Build multiple configuration From what I can tell it looks like the params are not getting passed from Jenkins as the changed variables. Unless there is something fancy that needs to be done to grab the right env variables. Does anyone know of documentation anywhere? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Ok, it looks like you don't have email-ext configured at all. So, I don't think the issue you are seeing has anything to do with email-ext. email-ext doesn't show up under your list of publishers (only Mailer@1.4). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Here's the xml (can't fit everything in a screenshot): - Continuous build for Dummy project false - - - https://server.domain.net:8443/svn/TheCode/trunk/G9 . false true false false false - - #check every hour and launch the build if there was a change. 0 * * * * false false - - del Build\Dummy\DEBUG_VS2008\FV*.f* codebuild.bat -P Dummy --UDRIVE - C:\Jenkins\Test_Scripts\Dummy_Test_Script.bat - - Build\Dummy\DEBUG_VS2008\FV*.full, Build\Dummy\DEBUG_VS2008\FV*.flash false - richard.merr...@hp.com false false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12563) Build multiple configuration
Daniel Brooks commented on JENKINS-12563 Build multiple configuration From what I can tell it looks like the params are not getting passed from Jenkins as the changed variables. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Can you take a screenshot of the project config (fuzz anything the world shouldn't see). I'm especially interested in the Post-Build Actions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted It looks to me like the email extensions plugin isn't being run at all. The boxes are checked and the xml file has values of true for both overrideGlobalSettings and debugMode. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Then debug mode is not enabled, there is much more output from the plugin before it tries to actually send the email. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Nothing related to email, just why the job build crashed. This particular build was expected to fail, so that I could test the email extension. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74 commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used the offer was increased to $200 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16251) HtmlPublisher 1.2 doesn't load from disk under Jenkins 1.492
mcrooney resolved JENKINS-16251 as Won't Fix HtmlPublisher 1.2 doesn't load from disk under Jenkins 1.492 Great, thanks Cedd, I'll close it for now but if someone else is finding this to be a serious problem, please do comment / re-open. Change By: mcrooney (07/Jan/13 7:38 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15774) Add ability to specify custom ivy settings file in global configuration for ivy job type
eguess74 commented on JENKINS-15774 Add ability to specify custom ivy settings file in global configuration for ivy job type This offer was increased to $150.00! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford commented on JENKINS-13726 Github plugin should work with Github enterprise by allowing for overriding the github URL github-plugin and github-api-plugin (1.34) dependencies now support connecting to an enterprise server. Once there is feedback on my snapshot I will see about merging the changes into the plugin and creating a new release. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13726) Github plugin should work with Github enterprise by allowing for overriding the github URL
Johno Crawford updated JENKINS-13726 Github plugin should work with Github enterprise by allowing for overriding the github URL Change By: Johno Crawford (07/Jan/13 7:23 PM) Summary: Github plugin should work with Guthub Github enterprise by allowing for overriding the github URL This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Can you please give more of the output? With debug mode enabled there should be a bunch more information before this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Sending e-mails to: richard.myn...@mycompany.com ERROR: Could not connect to SMTP host: localhost, port: 25 javax.mail.MessagingException: Could not connect to SMTP host: localhost, port: 25; nested exception is: java.net.SocketException: Permission denied: connect at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1934) at com.sun.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:638) at javax.mail.Service.connect(Service.java:295) at javax.mail.Service.connect(Service.java:176) at javax.mail.Service.connect(Service.java:125) at javax.mail.Transport.send0(Transport.java:194) at javax.mail.Transport.send(Transport.java:124) at hudson.tasks.MailSender.execute(MailSender.java:116) at hudson.tasks.Mailer.perform(Mailer.java:117) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732) at hudson.model.Run.execute(Run.java:1568) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.net.SocketException: Permission denied: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.sun.mail.util.SocketFetcher.createSocket(SocketFetcher.java:286) at com.sun.mail.util.SocketFetcher.getSocket(SocketFetcher.java:231) at com.sun.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:1900) ... 17 more Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74 commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used May be there is a simple race condition or something like that? The fact is that the ivy settings file is specified in the job configuration. When the build starts on the master the variables contained in build.xml are already read by the time the ivy descriptors parsing step starts. On slave though it is not working that way, so the variables are not yet initialized, so the parsing step fails. Does it make any sense? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15779) Parsing ivy descriptors step fails on a slave when custom ivy settings file is used
eguess74 commented on JENKINS-15779 Parsing ivy descriptors step fails on a slave when custom ivy settings file is used @Johno Currently, unfortunately, I have no way to reproduce the bug, as all our stuff is in the closed network. I will try to come up with something, but it is not guaranteed. I.e. the bug is easily reproducible on our setup, but it is not easy to reproduce the set up. My wild guess is that the variables initialization or usage is working a bit differently when build executed on slave vs master. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15964) All configuration screens are stuck "LOADING"
kurt stam commented on JENKINS-15964 All configuration screens are stuck "LOADING" In my case this was somehow caused by a rewrite in apache from /hudson to /jenkins which I had added to make old bookmarks work. All is working fine for me now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Can you enable debug mode for the email-ext plugin and then post the build log? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config
Kamil Kisiel commented on JENKINS-12436 Log parser plugin should not store the absolute path to the parsing file in each job config I should add, in order to fix the job configurations it was sufficient to go to each job and click the "save" button. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Just for fun, I disabled the Mailer plugin and got NullPointerException. When I have the Mailer enabled and the SMTP server field under Mailer blank, it tries to use localhost instead of the SMTP server specified under Email Extenstion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12436) Log parser plugin should not store the absolute path to the parsing file in each job config
Kamil Kisiel commented on JENKINS-12436 Log parser plugin should not store the absolute path to the parsing file in each job config I just got bit by this rather badly. We moved our console log parsing file on the filesystem and updated the global jenkins configuration. I assumed since the rules are chosen by name in the job config they would all be updated automatically (after all, isn't that the point of a global config?). Of course it didn't and even worse the error is not reported anywhere in the job console and doesn't cause the job to fail in any way. The only way to discover the problem was the browse to a job and check its parsed console log output which displayed the message: ERROR:Failed to parse console log : log-parser plugin ERROR: Cannot parse log: Can't read parsing rules file: This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12563) Build multiple configuration
Daniel Brooks commented on JENKINS-12563 Build multiple configuration +1 for a fix here. I'm going to look at the code here. I am using this for the CFBundleShortString and that param gets passed right. There must be something we are missing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill edited a comment on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Yup. Here's the contents of hudson.plugins.emailext.ExtendedEmailPublisher.xml: http://myservername:8080/ richard.myn...@mycompany.com smtp.mycompany.com false text/plain $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS! $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS: Check console output at $BUILD_URL to view the results. -1 true false true false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Yup. Here's the contents of hudson.plugins.emailext.ExtendedEmailPublisher.xml: http://myservername:8080/ richard.myn...@mycomopany.com smtp.mycompany.com false text/plain $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS! $PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS: Check console output at $BUILD_URL to view the results. -1 true false true false This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted You have override global settings checked in the extended email configuration and have filled in all the server info? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted Good to know. However, when I run my build it still fails to connect when trying to send the email notification. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Slide-O-Mix commented on JENKINS-16163 NullPointerException when sending post build emails - all triggers appear to be impacted The test configuration by sending test-email is part of the Mailer plugin, not email-ext. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16269) Provide a default string for BUILD_LOG_REGEX if match is not found
Slide-O-Mix resolved JENKINS-16269 as Fixed Provide a default string for BUILD_LOG_REGEX if match is not found Added defaultValue parameter which will be used if there is no match found. Change By: Slide-O-Mix (07/Jan/13 3:42 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16269) Provide a default string for BUILD_LOG_REGEX if match is not found
SCM/JIRA link daemon commented on JENKINS-16269 Provide a default string for BUILD_LOG_REGEX if match is not found Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/plugins/content/BuildLogRegexContent.java src/test/java/hudson/plugins/emailext/plugins/content/BuildLogRegexContentTest.java http://jenkins-ci.org/commit/email-ext-plugin/7bdb213ce94430654ae158377ba1ee3ea6ce102d Log: Fix JENKINS-16269 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16163) NullPointerException when sending post build emails - all triggers appear to be impacted
Richard Merrill
commented on JENKINS-16163
NullPointerException when sending post build emails - all triggers appear to be impacted
I have been using the "Test configuration by sending test e-mail" feature. With Jenkins version 1.493 it sends test emails successfully, but with the same settings in versions 1.494 and up (including 1.497) it fails to connect to the smtp host ("java.net.SocketException: Permission denied: connect"). Mailer Plugin 1.4 and Email Extension Plugin 2.25 are both installed and enabled.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15606) CloverPHP : error during configuration of cloverPHP in job
sogabe commented on JENKINS-15606 CloverPHP : error during configuration of cloverPHP in job The plugin does not verify the existence of xml files. It only check whether the value is entered or not. Accrodin to 404 error, the plugin is trying to check it with ajax, but ajax seems to be broken. I'll look into it in the near future. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15606) CloverPHP : error during configuration of cloverPHP in job
Jurgen Van Bouchaute commented on JENKINS-15606 CloverPHP : error during configuration of cloverPHP in job The main reason for this error is that the plugin does not support multiple jenkins nodes (machines). It tries to verify the existence of certain files on the main host, whereas the job workspace is located on the executor remote host. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16165) Configure screen stuck in "LOADING" state
Jesse Glick
commented on JENKINS-16165
Configure screen stuck in "LOADING" state
You can ignore the CSS warnings. The JS errors seem to be
TypeError: 'Event.observe' is not a function
Error thrown at line 1, column 0 in /adjuncts/cdaa3bea/lib/form/breadcrumb-config-outline/init.js:
Event.observe(window, "load", function () {
TypeError: 'YAHOO.util.XHRDataSource' is not a constructor
Error thrown at line 1605, column 4 in createSearchBox(searchURL) in /static/cdaa3bea/scripts/hudson-behavior.js:
var ds = new YAHOO.util.XHRDataSource(searchURL+"suggest");
ReferenceError: Undefined variable: $
Error thrown at line 1511, column 4 in updateBuildHistory(ajaxUrl, nBuild) in /static/cdaa3bea/scripts/hudson-behavior.js:
$('buildHistory').headers = ["n",nBuild];
TypeError: 'storage._each' is not a function
Error thrown at line 93, column 8 in function: applySubtree>(startNode, includeSelf) in /static/cdaa3bea/scripts/behavior.js:
storage._each(function (registration) {
and perhaps others. Not sure if these are due to incompatibilities with Opera. Can you please try
1. Running with a different browser, say Chrome or Firefox.
2. Running a clean Jenkins installation (i.e. fresh $JENKINS_HOME) on the same machine, with your regular browser, in case the problems are triggered by plugins.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach commented on JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp Maybe this is of importance: Coming from 1.480.1 I just exchanged the jenkins.war with 1.480.2 Anonymous read access is granted. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16272) LTS 1.480.2 breaks launching slaves via jnlp
Steffen Breitbach created JENKINS-16272 LTS 1.480.2 breaks launching slaves via jnlp Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: slave-prerequisites Created: 07/Jan/13 2:28 PM Description: Jenkins is running within a Tomcat 6.0.36 / Java 7u9 1.480.1 works as expected with 1.480.2, if trying to start a slave via JNLP, I get an error 403 from the server. http://$JENKINS/computer/$SLAVE/slave-agent.jnlp => HTTP request sent, awaiting response... 403 Forbidden 2013-01-07 15:17:43 ERROR 403: Forbidden. Environment: Linux/Tomcat Project: Jenkins Labels: jenkins slave Priority: Major Reporter: Steffen Breitbach This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8435) Tests that finish with a result of Timeout with MSTest get a passing result in Hudson
Arash Shafiee commented on JENKINS-8435 Tests that finish with a result of Timeout with MSTest get a passing result in Hudson Is there any further updates on this issue ? This issue is raised against XP but also applies to Win 7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13972) Concurrent matrix builds abort
Miro Vnuk updated JENKINS-13972 Concurrent matrix builds abort Change By: Miro Vnuk (07/Jan/13 2:08 PM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16271) The list of changed files should be shown in a table format
Mads Nielsen created JENKINS-16271 The list of changed files should be shown in a table format Issue Type: Improvement Affects Versions: current Assignee: Praqma Support Components: clearcase-ucm Created: 07/Jan/13 1:45 PM Description: The list of changed files should be shown in a table format. So that version, filename and user are shown in 3 seperate columns. Fix Versions: current Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16104) Build Failure Analyzer: Ugly output from plugin
stevengbrown updated JENKINS-16104 Build Failure Analyzer: Ugly output from plugin Not a Timestamper bug. Removed "timestamper" from the Components field. This bug appears to be caused by the way the Build Failure Analyzer plugin handles console notes. The Timestamper plugin (prior to version 1.4 only) inserted console notes, but so do other plugins and Jenkins itself. I was able to reproduce this with Jenkins 1.495 and only the Build Failure Analyzer plugin installed: Install Build Failure Analyzer 1.3.0 and dependencies. Create a new free-style build. Add an Execute Script build step (I was running Linux): There are 42 checkstyle errors. exit 1 Add the Checkstyle Error cause as described on the Build Failure Analyser wiki page. Run the build and inspect the console log. Change By: stevengbrown (07/Jan/13 1:45 PM) Component/s: timestamper This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16270) Build metrics icon filename incorrect
Jamie Penman-Smithson created JENKINS-16270 Build metrics icon filename incorrect Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: plugin Created: 07/Jan/13 1:32 PM Description: The build metrics icon is called icons/build-metrics.PNG, however the link used in the management page references icons/build-metrics.png. This works on Windows where filenames are case insensitive, but will not work on Unix. There doesn't seem to be a build-metrics component in JIRA, so I've set it to plugin instead, I hope this is okay. Project: Jenkins Labels: plugin Priority: Trivial Reporter: Jamie Penman-Smithson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16269) Provide a default string for BUILD_LOG_REGEX if match is not found
Dave Hunt
created JENKINS-16269
Provide a default string for BUILD_LOG_REGEX if match is not found
Issue Type:
Bug
Assignee:
Slide-O-Mix
Components:
email-ext
Created:
07/Jan/13 12:16 PM
Description:
If no match is found the value returned by BUILD_LOG_REGEX is empty, which makes the resulting emails difficult to read. It would be great if we could provide a suitable default value. An example is given below:
${BUILD_LOG_REGEX, regex="^*{3} Application: (.*)$", maxMatches=1, showTruncatedLines=false, substText="$1", addNewline=false, noMatchText="UNKNOWN"}
Project:
Jenkins
Priority:
Minor
Reporter:
Dave Hunt
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16268) Total disk usage counts shared workspaces more than once
David Riley created JENKINS-16268 Total disk usage counts shared workspaces more than once Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: disk-usage Created: 07/Jan/13 11:38 AM Description: I am using multiple shared workspaces in my jenkins instance so the total disk usage is useless because it is counting each of them separately. Should be able to create a set of absolute workspaces from all jobs then add them up rather than (presumably) a list created from the workspace for each job? Project: Jenkins Priority: Minor Reporter: David Riley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16267) Support multiple report directories
Norman Seidel created JENKINS-16267 Support multiple report directories Issue Type: Improvement Affects Versions: current Assignee: Vaclav Tunka Components: tattletale Created: 07/Jan/13 11:28 AM Description: Unfortunately, maven tattletale plugin doesn't support a aggregation of its reports. So in a multi-module project you get a tattletale report for each module. But the tattletale-plugin for jenkins only looks in one directory and so in our case the tattletale link point to nowhere. So please either look recursive for the configured directory or make it possible to configure more than one report directory. Environment: Tattletale plugin 0.3 Project: Jenkins Priority: Major Reporter: Norman Seidel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16053) Timestamper conflict with AnsiColor plugin
stevengbrown commented on JENKINS-16053 Timestamper conflict with AnsiColor plugin Great, thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16165) Configure screen stuck in "LOADING" state
Matti Linnanvuori updated JENKINS-16165 Configure screen stuck in "LOADING" state Opera error console file attached. Change By: Matti Linnanvuori (07/Jan/13 10:37 AM) Attachment: opera.error This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13644) Rebuild plugin can't rebuild when using parameters specified by copyartifact
Rino assigned JENKINS-13644 to Rino Rebuild plugin can't rebuild when using parameters specified by copyartifact Change By: Rino (07/Jan/13 10:26 AM) Assignee: ragesh_nair Rino This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16266) Direct link to console output (without first cliking on job) creates a 404
cedd burge created JENKINS-16266 Direct link to console output (without first cliking on job) creates a 404 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 07/Jan/13 10:06 AM Description: I have configured Jenkins to send emails with links to the console output for a specific build when a build fails, the links are like the one below. http://kl-vts-003:8081/job/Altahullion2%20ION/20/console When I first click on this link I get a 404. Clicking on http://kl-vts-003:8081/job/Altahullion2%20ION/20/ also produces a 404. Clicking on http://kl-vts-003:8081/job/Altahullion2%20ION/ works perfectly, and having done this the original link works fine from then on. Environment: Windows Project: Jenkins Priority: Major Reporter: cedd burge This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16251) HtmlPublisher 1.2 doesn't load from disk under Jenkins 1.492
cedd burge commented on JENKINS-16251 HtmlPublisher 1.2 doesn't load from disk under Jenkins 1.492 Hi! I have no idea, but I can work round the problem now and other people will be able to read up on it here if they come across it so feel free to close it if you want. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15119) Duration sorting is incorrect in TestNG report
Hua Zhang commented on JENKINS-15119 Duration sorting is incorrect in TestNG report The sorting is now correct. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
