[JIRA] (JENKINS-15860) Mail body for two simultaneous mails get mixed
Xavier Nodet resolved JENKINS-15860 as Cannot Reproduce Mail body for two simultaneous mails get mixed The issue didn't show again. I'll reopen the issue if I reproduce it. Thanks! Change By: Xavier Nodet (10/Dec/12 8:11 AM) Status: Open Resolved Resolution: CannotReproduce 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-15918) RunParameter environment variabes contain . character
Geoff Cummings
updated JENKINS-15918
RunParameter environment variabes contain . character
Change By:
Geoff Cummings
(10/Dec/12 9:09 AM)
Description:
TheRunParametercreates2environmentvariableswhichcontaina.character.Icannotreferencetheseenvironmentvariablesfromabashscriptduetothischaracter.envPARAMETER_X=http://xxx/jenkins/job/ASE_CI/2072/PARAMETER_X.number=2072PARAMETER_X.jobName=ASE_CIecho${
PARAMETER_NAME
PARAMETER_X
.number}${
PARAMETER_NAME
PARAMETER_X
.number}:badsubstitutionCanyoualsocreateenvironmentvariableswhichuseanunderscore?PARAMETER_XPARAMETER_X_NUMBERPARAMETER_X_JOBNAME
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-15860) Mail body for two simultaneous mails get mixed
Xavier Nodet edited a comment on JENKINS-15860 Mail body for two simultaneous mails get mixed Actually, this happened again tonight! The same two builds as last time failed at exactly the same time again. I received two mails, with two different (correct) subjects, but the same body in each (correct for only one of the mails). 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-15860) Mail body for two simultaneous mails get mixed
Xavier Nodet reopened JENKINS-15860 Mail body for two simultaneous mails get mixed Actually, this happened again tonigh! The same two builds as last time failed at exactly the same time again. I received two mails, with two different (correct) subjects, but the same body in each (correct for only one of the mails). Change By: Xavier Nodet (10/Dec/12 9:32 AM) Resolution: CannotReproduce Status: Resolved Reopened 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-15415) Anonymous users can browse source code through coverage report
Jes Struck commented on JENKINS-15415 Anonymous users can browse source code through coverage report this has been solved in the tip of the repos, so we are just waiting for the next release of 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-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild
Murray Cumming commented on JENKINS-15977 java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild Yes, upgrading Jenkins seems to have fixed this. After upgrading to the jenkins.org .deb packages (1.493), there is no "Maven 2 Project plugin" available or installed, but the "Maven Integration plugin" seems to be installed by default. And my "Copy artifacts from another project" build step now works. 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-16085) Mail Commander Plugin not working.
Deepal Neema created JENKINS-16085 Mail Commander Plugin not working. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: mailcommander Created: 10/Dec/12 10:54 AM Description: I am new to the jenkins, and i want to use the functionality of Mail Commander Plugin, I set the configuration on my Jenkins Configuration setup for the Email Notification. In Add Build Step Mail Commander I configured POP3 mail server address, POP3 mail server port,POP3 User Name,POP3 Password. And Mail Commander Pooling is Checked and set scheduling */1 * * * * After this i send the command mail with the subject build JOB_NAME to the jenkins configured mail id jenkins@__.com from the configured user mail id. I have checked that mail is received on the jenkins@__.com but my job not build and in the Mail Command Action the logger shows that Polling has not run yet. Please suggest me on this. Due Date: 11/Dec/12 12:00 AM Fix Versions: current Project: Jenkins Labels: jenkins Priority: Critical Reporter: Deepal Neema 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
lukerobertson commented on JENKINS-15587 Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: 39 Have you recently tried running Jenkins under Java 7 and then switched back to Java 6 or less? I experienced this issue where after a trial period under Java 7, switching back caused the build number shortcut folders to cause this exception. I managed to workaround this by just removing the shortcut folders which didnt impact the load up of the jobs. 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-16072) Missing baselines issue with latest plugin
Ronan Mulvaney commented on JENKINS-16072 Missing baselines issue with latest plugin If I don't pass the baseline in and just try to use the latest on the stream I get: CCUCM ClearCase UCM Plugin version 1.3.0 CCUCM Allow for slave polling: true CCUCM Poll for posted deliveries: false CCUCM Forcing deliver: false CCUCM Polling streams: self CCUCM Getting baselines for : CCUCM * Stream: n2o_ref_int@\N2O-PVOB CCUCM * Component: N2O-VOB@\N2O-PVOB CCUCM * Promotion level: null CCUCM No Baselines found CCUCM Pre build steps done CCUCM Finished processing; the baseline is null, this could pose as a problem! As the Promotion level: null appeared here I have tried setting and unsetting this from "any" but this doesn't seem to effect this 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-16083) HTML Publisher v1.1 regression
Kerstin Klein commented on JENKINS-16083 HTML Publisher v1.1 regression Similar issue: Configuration has not changed, after upgrade to version 1.1 of plugin I get this error message: Archiving artifacts htmlpublisher Archiving HTML reports... ERROR: directory does not exist no matter what I enter the error occurs. 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-16083) HTML Publisher v1.1 regression
Kerstin Klein edited a comment on JENKINS-16083 HTML Publisher v1.1 regression Similar issue: Configuration has not changed, after upgrade to version 1.1 of plugin I get this error message: Archiving artifacts htmlpublisher Archiving HTML reports... ERROR: directory does not exist no matter what I enter the error occurs. Environment: Centos 6.3 master. Downgrading to 1.0 failed. 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-16086) Always tags at end, despite changing position
Piotr Jasiulewicz created JENKINS-16086 Always tags at end, despite changing position Issue Type: Bug Assignee: k2nakamura Components: svn-tag Created: 10/Dec/12 1:23 PM Description: The task always executes as the last thing in the list post-build even though its first in the list. Having problems tagging and updating remote afterwards. Environment: Amazon Linux Project: Jenkins Priority: Major Reporter: Piotr Jasiulewicz 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-15860) Mail body for two simultaneous mails get mixed
Slide-O-Mix commented on JENKINS-15860 Mail body for two simultaneous mails get mixed It looks like you are using a global content template, can you post the text of that, sanitized? 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-16085) Mail Commander Plugin not working.
Deepal Neema commented on JENKINS-16085 Mail Commander Plugin not working. Please provide help on 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-3230) Parameter usable as value for SCM fields
Martin Ba
commented on JENKINS-3230
Parameter usable as value for SCM fields
Adding info: This works in Jenkins 1.420 (which is what I am running) - Not sure which is the first version that implements it.
The syntax to include a parameter is ${PARAM_NAME} (note the curly brackets) I was confused for a bit because I was used the %NAME% or the $(NAME) syntax.
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-16072) Missing baselines issue with latest plugin
Mads Nielsen commented on JENKINS-16072 Missing baselines issue with latest plugin Hey Ronan, We have an internal release candidate with a possible fix for your issue ready at our office. If you wish to download this version send a mail to m...@praqma.net, and i will reply you with a direct download link for the .hpi file. Regards, Mads 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-15808) CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration
Francois Valdy commented on JENKINS-15808 CVS plugin 2.0-2.7 breaks Gerrit Trigger (v2.5.2 and 2.6.0) configuration I confirm I'm affected by this issue as well (with latest greatest jenkins 1.492), and downgrading to CVS 1.6 fixes it. The 'Apply' workaround doesn't work for me. 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-16076) No email is sent to anyone if there is an invalid email address contained within the email list
rejesi commented on JENKINS-16076 No email is sent to anyone if there is an invalid email address contained within the email list Great - this fix has corrected the email html problem. The "unkn...@xxx.xx.com" user is still being sent email even though the log indicates "Error sending to the following INVALID addresses: unkn...@xxx.xx.com" - but this is so much better than no email going out at all. The other misleading line in the log has been removed as well. Thank you very much for the expedient manner in which you took care of this issue. 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-15322) NOTESTS in TAP response gives parse error and stack trace from plugin
Alex Newnham commented on JENKINS-15322 NOTESTS in TAP response gives parse error and stack trace from plugin http://testanything.org has been down for A Very Long Time, it seems. There's a crawled version of the site here: http://web.archive.org/web/20100124210854/http://testanything.org/wiki/index.php/Main_Page Browsing from there, I noticed here that Every test set as defined in this document should contain a version definition. A test set without a version definition is assumed to be written in TAP version 12, which is not covered by this document. Unfortunately I haven't yet found a definition for TAP version 12, but at least http://web.archive.org has a definition of TAP 13. It might be safe to assume that the Perl Tap::Harness module is writing valid TAP 12 - also that without a version specifier 12 the TAP plugin for Jenkins should parse TAP as TAP 12. Maybe I can coerce my perl harness to output TAP 13 which would probably be a fix to my problem, but in the meantime some of the above may be useful to you? 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-16076) No email is sent to anyone if there is an invalid email address contained within the email list
Slide-O-Mix commented on JENKINS-16076 No email is sent to anyone if there is an invalid email address contained within the email list Why do you say the user is still being send the email? Even if it shows up in the "To:" of the email when you receive it, doesn't mean that the email was actually sent to that address. It just means the header of the email lists that user in the To header. There really isn't a way around 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-16083) HTML Publisher v1.1 regression
Larry Shatzer, Jr. commented on JENKINS-16083 HTML Publisher v1.1 regression My regression is slightly different. Here is the output in my build: [htmlpublisher] Archiving HTML reports... ERROR: more than one path matched the pattern: ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/index.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/ivy-report.css ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-build.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-build.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-compile.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-compile.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-provided.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-provided.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-runtime.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-runtime.html ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-test.graphml ERROR: - /home/jenkins/workspace/projectName/target/dependency-report/org.grails.internal-AppName-test.html Build step 'Publish HTML reports' changed build result to 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-16076) No email is sent to anyone if there is an invalid email address contained within the email list
rejesi commented on JENKINS-16076 No email is sent to anyone if there is an invalid email address contained within the email list Hmmm, Just so you know - when valid email addresses and an invalid email address with a bad domain are entered in the "Project Recipient List" to be used as the recipient list for the triggers, it is considered an empty list (per the log message) and no email gets sent to anyone as shown in the log below. There is clearly a red error message on the job config page about the bad domain name - which means that the user just ignored the message. Email was triggered for: Success Sending email for trigger: Success Failed to create e-mail address for sw@xxx..xx.com An attempt to send an e-mail to empty list of recipients, ignored. Finished: SUCCESS The "Project Recipient List" has been used in the trigger emails before if the user wanted the same people to be notified for the respective trigger and didn't put the same names in the respective trigger's "Recipient List" But if the bad domain name is in the trigger recipient list it is handled as expected as per the log messages below: Email was triggered for: Success Sending email for trigger: Success Failed to create e-mail address for sw.t...@xxx..xx.com Sending email to: sw@xxx.xx.com unkn...@xxx.xx.com Successfully sent to the following addresses: sw@xx.com Error sending to the following INVALID addresses: unkn...@xx.xx.com Finished: SUCCESS 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-16076) No email is sent to anyone if there is an invalid email address contained within the email list
rejesi commented on JENKINS-16076 No email is sent to anyone if there is an invalid email address contained within the email list Sorry, didn't see your remarks. Agreed. I was not implying that it was wrong, as I have no way of knowing what really happens to the email, just that it showed up in the header. And as you indicate, there is no way around it and I am fine with 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-16083) HTML Publisher v1.1 regression
SCM/JIRA link daemon commented on JENKINS-16083 HTML Publisher v1.1 regression Code changed in jenkins User: Michael Rooney Path: src/main/java/htmlpublisher/HtmlPublisher.java src/main/resources/htmlpublisher/HtmlPublisher/config.jelly http://jenkins-ci.org/commit/htmlpublisher-plugin/7dbff2b015d5eead296e73d697dd31e720039224 Log: revert 'Resolve ant pattern in archive directory' as it is perhaps causing JENKINS-16083 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-16083) HTML Publisher v1.1 regression
Bob Ballantyne commented on JENKINS-16083 HTML Publisher v1.1 regression the exact output I found was dependent on the path specification in the "HTML directory to archive" setting. I got the same output in the build when I tried either \ in place of / or /** 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-16083) HTML Publisher v1.1 regression
mcrooney commented on JENKINS-16083 HTML Publisher v1.1 regression Okay, sorry about this everyone! There were unreleased commits when I went to release other commits, so I've reverted the likely culprit and released as 1.2. Please let me know if that resolves the issue or not. I'm able to successfully archive HTML reports in a test setup with this version. 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-13835) E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request
Leon Moctezuma commented on JENKINS-13835 E175002 in org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request Issue #1 I'm having this problem on a Mac OS 10.8 Jenkins version 1.493 Subversion Plugin 1.43 FAILED: svn: E175002: OPTIONS /vc/repos failed org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /vc/repos failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:304) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:289) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:277) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:696) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:619) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1018) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.postCredential(SubversionSCM.java:1978) at hudson.scm.SubversionSCM$DescriptorImpl.doPostCredential(SubversionSCM.java:1923) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215) at
[JIRA] (JENKINS-16087) Number of successful release builds to keep option does not work
Yevgen Galchenko created JENKINS-16087 Number of successful release builds to keep option does not work Issue Type: Bug Affects Versions: current Assignee: teilo Attachments: M2ReleaseBuildWrapper.java Components: m2release Created: 10/Dec/12 7:36 PM Description: "Number of successful release builds to keep" cannot be modified due to name mismatch in M2ReleaseBuildWrapper for field numberOfReleaseBuildsToKeep. Working version attached. Project: Jenkins Priority: Minor Reporter: Yevgen Galchenko 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-15829) hg share always recreating working copy on slave (on master it's working fine)
Jesse Glick commented on JENKINS-15829 hg share always recreating working copy on slave (on master its working fine) It is true that when caching is enabled, slave repos have no paths.default: changeset bundles are transferred over the Jenkins remoting channel instead. 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-16087) Number of successful release builds to keep option does not work
Yevgen Galchenko commented on JENKINS-16087 Number of successful release builds to keep option does not work Also buildsKept is not incremented keeping old releases marked with "keep forever" 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-5949) Trim JUnit stack traces logs to reasonable length before mailing
Slide-O-Mix commented on JENKINS-5949 Trim JUnit stack traces logs to reasonable length before mailing The way I have implemented this is with a new parameter (maxLength) which can be used to specify the max KB of data to print as part of the FAILED_TESTS token. If the output would exceed the amount specified, then it truncates the output and adds "...output truncated" to the output. The default value of the parameter imposes no limit to maintain current functionality by default. Will this meet the request? 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-15309) NPE (isEmpty) from main.groovy
David Ishee commented on JENKINS-15309 NPE (isEmpty) from main.groovy I updated to Jenkins 1.480.1, and set the security realm to Active Directory, and Authorization = "Anyone can do anything". It didn't change the error message. I changed the Authorization to "logged in users can do anything", but the error message is still there. The Anonymous View works OK. 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-15309) NPE (isEmpty) from main.groovy
David Ishee commented on JENKINS-15309 NPE (isEmpty) from main.groovy A lot of other problems are showing up. I think I'm going to give up on trying to upgrade a Hudson installation and start with a clean Jenkins install and re-do all my jobs. It looks like that is the only workable solution. 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-16088) JClouds Plugin creates too many instances and fails to launch Jenkins slaves
Jonathan Harker
created JENKINS-16088
JClouds Plugin creates too many instances and fails to launch Jenkins slaves
Issue Type:
Bug
Assignee:
abayer
Components:
jclouds
Created:
10/Dec/12 10:42 PM
Description:
A simple job which creates a single jclouds instance then runs `echo` on that instance fails creating several nova instances on the account, none of which are listed in jenkins as nodes.
The instance template uses a base ubuntu precise image, with Allow Sudo on and the following init script defined:
#!/bin/bash
apt-add-repository -y ppa:saltstack/salt
apt-get -y update
apt-get install -y build-essential
apt-get install -y git
apt-get install -y python-dev
apt-get install -y python-novaclient
apt-get install -y python-jinja2
apt-get install -y salt-master
The console output is:
Started by user anonymous
EnvInject - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/jobs/create-salt-slave-az1/workspace
Queuing cloud instance: #0 1, HPCS salt-az1
ERROR: Exception creating a node: org.jclouds.compute.RunNodesException: error running 1 node group(salt-az1) location(az-1.region-a.geo-1) image(8419) size(101) options({scriptPresent=true, userMetadata={Name=salt-az1}, generateKeyPair=true})
Execution failures:
1) ExecutionException on salt-az1-348:
java.util.concurrent.ExecutionException: java.util.NoSuchElementException
at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)
at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:134)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.util.NoSuchElementException
at com.google.common.collect.Iterables.getLast(Iterables.java:797)
at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:100)
at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:55)
at com.google.common.util.concurrent.Futures$3.apply(Futures.java:380)
at com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:522)
... 3 more
1 errors
Node failures:
0 errors
ERROR: Exception creating a node: org.jclouds.compute.RunNodesException: error running 1 node group(salt-az1) location(az-1.region-a.geo-1) image(8419) size(101) options({scriptPresent=true, userMetadata={Name=salt-az1}, generateKeyPair=true})
Execution failures:
1) ExecutionException on salt-az1-768:
java.util.concurrent.ExecutionException: java.util.NoSuchElementException
at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:289)
at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:276)
at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:111)
at org.jclouds.concurrent.FutureIterables$1.run(FutureIterables.java:134)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.util.NoSuchElementException
at com.google.common.collect.Iterables.getLast(Iterables.java:797)
at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:100)
at org.jclouds.openstack.nova.v2_0.compute.functions.AllocateAndAddFloatingIpToNode.apply(AllocateAndAddFloatingIpToNode.java:55)
at com.google.common.util.concurrent.Futures$3.apply(Futures.java:380)
at com.google.common.util.concurrent.Futures$ChainingListenableFuture.run(Futures.java:522)
... 3 more
1 errors
Node failures:
0 errors
ERROR: Exception creating a node:
[JIRA] (JENKINS-16088) JClouds Plugin creates too many instances and fails to launch Jenkins slaves
abayer commented on JENKINS-16088 JClouds Plugin creates too many instances and fails to launch Jenkins slaves Looks like jclouds isn't able to allocate an IP to your instances? 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-15885) Not able to any configutation changes for existing jobs and new jobs
viral shah commented on JENKINS-15885 Not able to any configutation changes for existing jobs and new jobs Hi Andrew, I tried to look into IE 8 but it is still not working for me.DO you know what is the estimated time to fix this one? or is there any alternative solution for this issue . As this is really a blocker for me to create new job and update the existing Job. 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-15120) Minimize round trips for slave class loading
Jesse Glick started work on JENKINS-15120 Minimize round trips for slave class loading Change By: Jesse Glick (10/Dec/12 11:50 PM) Status: Open InProgress 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-16089) Standard view columns interact force builds to be eagerly loaded
Jesse Glick created JENKINS-16089 Standard view columns interact force builds to be eagerly loaded Issue Type: Bug Assignee: Jesse Glick Components: core Created: 10/Dec/12 11:58 PM Description: LastFailureColumn, shown by default in AllView, is calling Job.getLastFailedBuild which then keeps on loading builds until it finds a failed build, with no cutoff. The fix for that would be to either impose a maximum number of builds to search back from (10? 20?); or do the search asynchronously after the page loads, which might still put some load on the server but would at least not stop you from browsing. The same would apply to the last success column if all your recent builds failed, etc. Project: Jenkins Labels: performance Priority: Major Reporter: Jesse Glick 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-5949) Trim JUnit stack traces logs to reasonable length before mailing
Jesse Glick commented on JENKINS-5949 Trim JUnit stack traces logs to reasonable length before mailing Makes sense I think. 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-16090) Cannot access published results page via links in prior builds
John Mills created JENKINS-16090 Cannot access published results page via links in prior builds Issue Type: Bug Assignee: mcrooney Components: htmlpublisher Created: 11/Dec/12 1:40 AM Description: Exception thrown accessing published results page via links in prior builds on jobs that have the "Keep past HTML reports" option set. Note: Using v1.1 is not an option as it does not work properly for me (a different issue). Status Code: 500 Exception: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/webapps/jenkins/WEB-INF/lib/jenkins-core-1.492.jar!/hudson/model/DirectoryBrowserSupport/dir.jelly:29:58: st:include No page found 'sidepanel.jelly' for class htmlpublisher.HtmlPublisherTarget$HTMLBuildAction Stacktrace: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files/Apache%20Software%20Foundation/Tomcat%207.0/webapps/jenkins/WEB-INF/lib/jenkins-core-1.492.jar!/hudson/model/DirectoryBrowserSupport/dir.jelly:29:58: st:include No page found 'sidepanel.jelly' for class htmlpublisher.HtmlPublisherTarget$HTMLBuildAction at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:60) at hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:247) at hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:108) at htmlpublisher.HtmlPublisherTarget$BaseHTMLAction.doDynamic(HtmlPublisherTarget.java:134) at htmlpublisher.HtmlPublisherTarget$HTMLBuildAction.doDynamic(HtmlPublisherTarget.java:174) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:363) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at
[JIRA] (JENKINS-3324) Ability to configure Reply-To header for broken build mail
Slide-O-Mix started work on JENKINS-3324 Ability to configure Reply-To header for broken build mail Change By: Slide-O-Mix (11/Dec/12 3:46 AM) Status: Open InProgress 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-3324) Ability to configure Reply-To header for broken build mail
Slide-O-Mix resolved JENKINS-3324 as Fixed Ability to configure Reply-To header for broken build mail Change By: Slide-O-Mix (11/Dec/12 4:16 AM) Status: InProgress 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-5949) Trim JUnit stack traces logs to reasonable length before mailing
Slide-O-Mix resolved JENKINS-5949 as Fixed Trim JUnit stack traces logs to reasonable length before mailing Change By: Slide-O-Mix (11/Dec/12 4:16 AM) 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-16085) Mail Commander Plugin not working.
Deepal Neema updated JENKINS-16085 Mail Commander Plugin not working. Change By: Deepal Neema (11/Dec/12 4:22 AM) Due Date: 11/Dec/12 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-16085) Mail Commander Plugin not working.
Deepal Neema updated JENKINS-16085 Mail Commander Plugin not working. Change By: Deepal Neema (11/Dec/12 4:23 AM) Description: Iamnewtothejenkins,andiwanttousethefunctionalityofMailCommanderPlugin,IsettheconfigurationonmyJenkinsConfigurationsetupfortheEmailNotification. InAddBuildStepMailCommanderIconfiguredPOP3mailserveraddress,POP3mailserverport,POP3UserName,POP3Password. AndMailCommanderPoolingisCheckedandsetscheduling*/1 AfterthisisendthecommandmailwiththesubjectbuildJOB_NAMEtothejenkinsconfiguredmailidjenkins@__.comfromtheconfiguredusermailid.Ihavecheckedthatmailisreceivedonthejenkins@__.combutmyjobnotbuildandintheMailCommandActiontheloggershowsthatPollinghasnotrunyet.Pleasesuggestmeonthis. 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-15976) Provided maven settings.xml in maven builder is lost
domi commented on JENKINS-15976 Provided maven settings.xml in maven builder is lost It seems that a dropdown in a dropdown is an issue 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-15976) Provided maven settings.xml in maven builder is lost
domi edited a comment on JENKINS-15976 Provided maven settings.xml in maven builder is lost It seems that a dropdown in a dropdown is an issue for an advanced section 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-13697) ArrayIndexOutOfBounds Exception when I try to setup a second IRC channel in Jenkins configuration
SCM/JIRA link daemon resolved JENKINS-13697 as Fixed ArrayIndexOutOfBounds Exception when I try to setup a second IRC channel in Jenkins configuration Change By: SCM/JIRA link daemon (11/Dec/12 7:29 AM) Status: InProgress 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-13697) ArrayIndexOutOfBounds Exception when I try to setup a second IRC channel in Jenkins configuration
SCM/JIRA link daemon commented on JENKINS-13697 ArrayIndexOutOfBounds Exception when I try to setup a second IRC channel in Jenkins configuration Code changed in jenkins User: syl20bnr Path: src/main/java/hudson/plugins/ircbot/IrcPublisher.java http://jenkins-ci.org/commit/ircbot-plugin/ffbda2c14adc98c995674ea7225518edd5390375 Log: FIXED JENKINS-13697: retrieve notificationOnly value via JSON representation 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
