[JIRA] [email-ext] (JENKINS-24417) email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times
m_broida commented on JENKINS-24417 email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times And Token Macro 1.10 does not require a Jenkins newer than we use. We'll install it during our next maintenance window. Thanks, everyone! 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24417) email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times
m_broida commented on JENKINS-24417 email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times Ah! We have Token Macro plugin 1.8.1. I will try to update and see if that helps. Thanks! (I say 'try to update' because I don't know what other dependencies we'll need.) 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24417) email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times
m_broida commented on JENKINS-24417 email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times e-mail-ext changelog suggests a similar problem may have been fixed in version 2.28. But this is present in version 2.36, and nothing in changelog since then (or in open issues) seems to match. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-24417) email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times
m_broida created JENKINS-24417 email-ext Content Token Reference help info: after first list, it repeats each item hundreds of times Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 25/Aug/14 4:11 PM Description: Click the ? to open the email-ext Content Token Reference. Wait 15 seconds for help info to load. Scroll the list of tokens. After the header "Token Macro Plugin Tokens", each item is repeated hundreds of times. Then a few final items are listed. Environment: Jenkins 1.542, email-ext 2.36 Project: Jenkins Priority: Major Reporter: m_broida 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
m_broida commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? This is not fixed in 1.542. We're waiting for this fix before we upgrade. Changelog does not show this issue (or any of the duplicated/related issues) have ever been incorporated/released. When will this fix be incorporated? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-16376) BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE?
m_broida commented on JENKINS-16376 BuildStepMonitor.BUILD makes concurrent builds wait, could be changed to BuildStepMonitor.NONE? Sorry. I reached this issue from a different issue and thought it was still against Jenkins itself. I meant Jenkins version 1.542. I see from the email-ext changelog that version 2.37 has this fix in it. We're using 2.36, so an update should fix this for us. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
m_broida commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session OK, same thing today: first login did not save the ACEGI... cookie. Logged out and back in, and got that cookie. AND it has not logged me out all day. So, sounds like "cookie is not accepted" is actually the cause of logouts for me. Now, how do I figure out WHY the cookie is not being accepted? (or not being sent) Jenkins 1.542 on Windows, using local login authentication (no AD). 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
m_broida edited a comment on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session I had to close the browser/reboot, so expected the cookie to be deleted. It was, so I was logged out. Logged into Jenkins again: new cookie good for 14 days from today. We'll see how it goes this time... LATER: No problem the rest of that day. I'll repost the next time Jenkins logs me out WITHOUT closing the browser. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
m_broida commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session I apologize for not reading the earlier posts in more detail. I added the LogRecorder and the logger as described above. When I logout and back in, this (among other detail) shows in the log: Mar 17, 2014 3:49:09 PM FINE org.acegisecurity.ui.rememberme.TokenBasedRememberMeServices loginSuccess Added remember-me cookie for user 'michael.broida', expiry: 'Mon Mar 31 15:49:09 GMT 2014' So its set to expire in two weeks: Mar 31 - Mar 17 = 14 days. My system time was about 10:49AM (US CDT) and the Jenkins Master node time was: 3:49:09PM (UTC). So those line up correctly: US CDT = UTC-5. I see log entries like this one cleansed, apparently every time I click a Jenkins link: Mar 17, 2014 3:49:09 PM FINE org.acegisecurity.ui.rememberme.RememberMeProcessingFilter doFilter SecurityContextHolder not populated with remember-me token, as it already contained: 'org.acegisecurity.providers.UsernamePasswordAuthenticationToken@f05122ff: Username: org.acegisecurity.userdetails.User@0: Username: michael.broida; Password: PROTECTED; Enabled: true; AccountNonExpired: true; credentialsNonExpired: true; AccountNonLocked: true; Granted Authorities: authenticated, USER, admin; Password: PROTECTED; Authenticated: true; Details: org.acegisecurity.ui.WebAuthenticationDetails@957e: RemoteIpAddress: nn.nn.nn.nn; SessionId: 178z3b1pbslvm1hyjg8qchd6wo; Granted Authorities: authenticated, USER, admin' Chrome shows an ACEGI_SECURITY_HASHED_REMEMBER_ME_COOKIE cookie with same Mar 31 expiration as above. We'll see if Jenkins logs me out in the next couple of hours 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
m_broida commented on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session On 30/Jul/13, he said he still has to login 10 times a day. That doesn't sound "resolved" to me. I'm using Jenkins 1.542, and several times a day Jenkins forgets that I'm logged in. Browser (Chrome) stays open, but refreshed page is suddenly logged out. We do not use ActiveDirectory, so this is not related to JENKINS-9258. We use a local script for authentication. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
m_broida edited a comment on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session His last comment (30/Jul/13) says he still has to login 10 times a day. That doesn't sound "resolved" to me. I'm using Jenkins 1.542, and several times a day Jenkins forgets that I'm logged in. Browser (Chrome) stays open, but refreshed page is suddenly logged out. We do not use ActiveDirectory, so this is not related to JENKINS-9258. We use a local script for authentication. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-16278) Remember me on this computer does not work, cookie is not accepted in new session
m_broida edited a comment on JENKINS-16278 Remember me on this computer does not work, cookie is not accepted in new session His last comment (30/Jul/13) says he still has to login 10 times a day. That doesn't sound "resolved" to me. I'm using Jenkins 1.542, and several times a day Jenkins forgets that I'm logged in. Browser (Chrome) stays open, but refreshed page is suddenly logged out. We do not use ActiveDirectory, so this is not related to JENKINS-9258. We use a local script for authentication. Oh, _)% While typing this entry, Jenkins logged me out AGAIN. Why? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-9258) Remember me doesn't work with Active Directory plugin
m_broida commented on JENKINS-9258 Remember me doesnt work with Active Directory plugin The workaround also won't work if you're not using AD. We don't use AD, we use a local script for login. Yet Jenkins keeps logging me out, several times each day. Why? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
m_broida commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours What about setups where we do NOT use AD at all? We validate logins via a local script, and have no AD use. Yet Jenkins still logs me out several times/day. Jenkins 1.542 on Windows. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
m_broida edited a comment on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours What about setups where we do NOT use AD at all? We don't even have the ActiveDirectory plugin. We validate logins via a local script. Yet Jenkins still logs me out several times/day. Jenkins 1.542 on Windows. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
m_broida commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Linux is not an option. And we do -NOT- use ActiveDirectory. We authenticate with a Ruby script. AD is not involved at all. Yet Jenkins logs me out after some period of time. Usually a couple of hours, whether inactive or not. Note: =I= am the only user of our buildserver that is experiencing the periodic logouts. (Or no-one else is complaining.) At least one other user NEVER gets logged out. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
m_broida commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours This is becoming VERY annoying. Our Jenkins master is a WinServer2008R2 box, several Windows slaves (WinServer2003 + WinServer2008R2 + a couple Linux boxes). We "authenticate via custom script". Logins work fine. I'm using Chrome to view Jenkins. I do NOT close the browser; I don't even close the Jenkins tab. Every few hours, a page refresh shows I'm no longer logged in. Any suggestions? Polite ones, please. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
m_broida edited a comment on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours This is becoming VERY annoying. Our Jenkins master (1.542) is a WinServer2008R2 box, has several Windows slaves (WinServer2003 + WinServer2008R2 + a couple Linux boxes). We "authenticate via custom script". Logins work fine. I'm using Chrome to view Jenkins. I do NOT close the browser; I don't even close all of the Jenkins tabs (only some of them). Every few hours, a page refresh shows I'm no longer logged in. Any suggestions? Polite ones, please. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodenamecolumn] (JENKINS-12207) get warnings in log
m_broida commented on JENKINS-12207 get warnings in log This started hitting us today in Jenkins 1.509.2. The jobs are not Multijob; they are normal FreeStyleProjects. 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nodenamecolumn] (JENKINS-6286) Caught exception evaluating: it.getNodeName(job). Reason: java.lang.NullPointerException
m_broida commented on JENKINS-6286 Caught exception evaluating: it.getNodeName(job). Reason: java.lang.NullPointerException Hit this today several times on Jenkins 1.509.2. Seems duplicated at a later date in JENKINS-12207 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18439) Ability to modify the login page
m_broida created JENKINS-18439 Ability to modify the login page Issue Type: New Feature Assignee: Unassigned Components: core Created: 20/Jun/13 10:46 PM Description: We need to display a bit of information (which set of credentials to use, who to contact for site/job support, etc). We currently display that on the "Default View", but it must be visible BEFORE the user is logged in. NOW we want to set Jenkins so any access requires a logged-in user. In that case, first access jumps to login page showing only Username, Password, and "remember me" boxes. We want to modify the login page (login.jelly file?) without worry of our mods being wiped out by a Jenkins upgrade (and without mucking in .jar files). Perhaps just a way to specify a blob of HTML that login.jelly will display above the "Username" input box?? Project: Jenkins Labels: login Priority: Minor Reporter: m_broida 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18439) Ability to modify the login page
m_broida updated JENKINS-18439 Ability to modify the login page Change By: m_broida (20/Jun/13 10:55 PM) Description: Weneedtodisplayabitofinformation(whichsetofcredentialstouse,whotocontactforsite/jobsupport,etc).WecurrentlydisplaythatontheDefaultView,butitmustbevisibleBEFOREtheuserisloggedin.NOWwewanttosetJenkinssoanyaccessrequiresalogged-inuser.Inthatcase,firstaccessjumpstologinpageshowingonlyUsername,Password,andremembermeboxes.Wewanttomodifytheloginpage (login.jellyfile?) withoutworryofourmodsbeingwipedoutbyaJenkinsupgrade(andwithoutmuckingin.jarfiles).PerhapsjustawaytospecifyablobofHTMLthatlogin.jellywilldisplayabovetheUsernameinputbox?? 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 -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
---
org.apache.velocity.exception.MethodInvocationException:
Invocation of method #39;next#39; in class java.util.AbstractList$Itr
threw exception class java.util.NoSuchElementException : null
at
org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:251)
at
org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:175)
at
org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:220)
at
org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:230)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:300)
at
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:202)
at
com.atlassian.velocity.DefaultVelocityManager.getEncodedBodyForContent(DefaultVelocityManager.java:143)
at
com.atlassian.jira.mail.MailingListCompiler$1.processRecipient(MailingListCompiler.java:295)
at
com.atlassian.jira.mail.NotificationRecipientProcessor.process(NotificationRecipientProcessor.java:39)
at
com.atlassian.jira.mail.MailingListCompiler.addMailsToQueue(MailingListCompiler.java:318)
at
com.atlassian.jira.mail.MailingListCompiler.access$400(MailingListCompiler.java:42)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:463)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:433)
at
com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendForEvent(MailingListCompiler.java:386)
at
com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:135)
at
com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:145)
at
com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:66)
at
com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:28)
at
com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:61)
at
com.atlassian.jira.service.ServiceRunner.execute(ServiceRunner.java:47)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at
com.atlassian.multitenant.quartz.MultiTenantThreadPool$MultiTenantRunnable.run(MultiTenantThreadPool.java:72)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
MIME-Version: 1.0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 3c0fae591c90ba70494f35b895fc4b8f
style
/* Changing the layout to use less space for mobiles */
@media screen and (max-device-width: 480px), screen and
(-webkit-min-device-pixel-ratio: 2) {
#email-body { min-width: 30em !important; }
#email-page { padding: 8px !important; }
#email-banner { padding: 8px 8px 0 8px !important; }
#email-avatar { margin: 1px 8px 8px 0 !important; padding: 0 !important; }
#email-fields { padding: 0 8px 8px 8px !important; }
#email-gutter { width: 0 !important; }
}
/style
div id=email-body
table id=email-wrap align=center border=0 cellpadding=0
cellspacing=0 style=background-color:#f0f0f0;color:#00;width:100%;
tr valign=top
td id=email-page style=padding:16px !important;
table align=center border=0 cellpadding=0 cellspacing=0
style=background-color:#ff;border:1px solid
#bb;color:#00;width:100%;
tr valign=top
td bgcolor=#33
style=background-color:#33;color:#ff;font-family:Arial,FreeSans,Helvetica,sans-serif;font-size:12px;line-height:1;img
src=https://issues.jenkins-ci.org/s/en_US-jh6o7l/733/41/_/jira-logo-scaled.png;
alt= style=vertical-align:top; //td
/trtr valign=top
td id=email-banner style=padding:32px 32px 0 32px;
table align=left border=0 cellpadding=0 cellspacing=0
width=100% style=width:100%;
tr valign=top
td
style=color:#505050;font-family:Arial,FreeSans,Helvetica,sans-serif;padding:0;
img id=email-avatar
src=https://issues.jenkins-ci.org/secure/useravatar?avatarId=10292; alt=
height=48 width=48 border=0 align=left style=padding:0;margin: 0 16px
16px 0; /
div id=email-action style=padding: 0 0 8px
0;font-size:12px;line-height:18px;
a class=user-hover rel=m_broida
id=email_m_broida
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=m_broida;
style=color:#355564;m_broida/a
commented on img
src=https://issues.jenkins-ci.org/images/icons/improvement.gif; height=16
width=16 border=0 align=absmiddle alt=Improvement a
style='color:#355564;text-decoration:none;'
href='https://issues.jenkins-ci.org/browse/JENKINS-10841'JENKINS-10841/a
/div
[JIRA] (JENKINS-14030) renaming a job does not preserve history
m_broida commented on JENKINS-14030 renaming a job does not preserve history Similarly: renaming (or deleting) a node causes job history entries for jobs built on that node to say they were built on the "master" node 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-3105) Configuration UI to disable process tree killer selectively
[ https://issues.jenkins-ci.org/browse/JENKINS-3105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=158732#comment-158732 ] m_broida edited comment on JENKINS-3105 at 2/7/12 5:43 PM: --- Details on this workaround work, please? Does it prevent intentionally killing/aborting a build? Can a build step in the job just set a BUILD_ID envvar? Is the specific value dontKillMe required, or will any value work? Adding a parameter to every one of our many jobs (and new ones) would be a hassle, even if users could accept a default value. Can the BUILD_ID envvar be set in the overall Jenkins configuration to affect all Jenkins jobs? Can the BUILD_ID envvar be set at the OS level to affect all Jenkins jobs? We have had to restrict many of our jobs to run on nodes with only a single executor to ensure that the situation doesn't arise. A real fix would be most helpful. was (Author: m_broida): Details on this workaround work, please? Can a build step in the job just set a BUILD_ID envvar? Is the specific value dontKillMe required, or will any value work? Adding a parameter to every one of our many jobs (and new ones) would be a hassle, even if users could accept a default value. Can the BUILD_ID envvar be set in the overall Jenkins configuration to affect all Jenkins jobs? Can the BUILD_ID envvar be set at the OS level to affect all Jenkins jobs? We have had to restrict many of our jobs to run on nodes with only a single executor to ensure that the situation doesn't arise. A real fix would be most helpful. Configuration UI to disable process tree killer selectively --- Key: JENKINS-3105 URL: https://issues.jenkins-ci.org/browse/JENKINS-3105 Project: Jenkins Issue Type: Improvement Components: other Affects Versions: current Environment: Platform: Sun, OS: Solaris Reporter: olamy Priority: Trivial Due to fix https://hudson.dev.java.net/issues/show_bug.cgi?id=2729, I can't restart my tomcat instance with using a script which worked fine before 1.283. My script called fastRestart.sh is : PWD=`pwd` cd $PWD #BUILD_ID=dontKillMe catalina.sh start #BUILD_ID=dontKillMe ./startup.sh echo $BUILD_ID kill -9 `cat ./tomcat.pid` ./startup.sh My hudson job do : BUILD_ID=dontKillMe startup.sh cd /local/dotw/tomcat-dev-ota-ah/apache-tomcat-6.0.14/bin ./fastRestart.sh job console output : started [workspace] $ /bin/sh -xe /local/dotw/tmp/hudson-tmp/hudson3776950102996593394.sh BUILD_ID=dontKillMe startup.sh + cd /local/dotw/tomcat-dev-ota-ah/apache-tomcat-6.0.14/bin + ./fastRestart.sh + pwd PWD=/local/dotw/tomcat-dev-ota-ah/apache-tomcat-6.0.14/bin + cd /local/dotw/tomcat-dev-ota-ah/apache-tomcat-6.0.14/bin + echo dontKillMe startup.sh dontKillMe startup.sh + cat ./tomcat.pid + kill -9 9822 + ./startup.sh finished: SUCCESS Here the tomcat has been killed and restarted but immediatly stop due to fix for 2729. Is there any other workaround ? IMHO we should have a flag when running a script which don't kill child processes (to preserve a minimum of backward compatibility and a minimum of some jobs/scripts rewriting) Thanks -- Olivier -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
