[JIRA] [jenkins-multijob-plugin] (JENKINS-21649) High CPU Usage on master while slaves working (multijob)
Patrik Schalin commented on JENKINS-21649 High CPU Usage on master while slaves working (multijob) Seeing the same on Jenkins 1.532.1 with MultiJob PLugin 1.12. Typically its the pool threads that are heavy on CPU... "pool-26-thread-1" prio=5 RUNNABLE java.util.Hashtable.get(Unknown Source) java.text.NumberFormat.getInstance(Unknown Source) java.text.NumberFormat.getInstance(Unknown Source) java.text.MessageFormat.subformat(Unknown Source) java.text.MessageFormat.format(Unknown Source) java.text.Format.format(Unknown Source) java.text.MessageFormat.format(Unknown Source) org.jvnet.localizer.ResourceBundleHolder.format(ResourceBundleHolder.java:139) hudson.Messages.Util_second(Messages.java:405) hudson.Util.getTimeSpanString(Util.java:682) hudson.model.Run.getDurationString(Run.java:697) com.tikal.jenkins.plugins.multijob.MultiJobBuilder.updateSubBuild(MultiJobBuilder.java:292) com.tikal.jenkins.plugins.multijob.MultiJobBuilder.access$000(MultiJobBuilder.java:60) com.tikal.jenkins.plugins.multijob.MultiJobBuilder$SubJobWorker.run(MultiJobBuilder.java:200) java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) "pool-26-thread-2" prio=5 WAITING hudson.remoting.AsyncFutureImpl.isCancelled(AsyncFutureImpl.java:64) com.tikal.jenkins.plugins.multijob.MultiJobBuilder$SubJobWorker.run(MultiJobBuilder.java:194) java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) java.lang.Thread.run(Unknown Source) 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] [integrity-plugin] (JENKINS-21826) Integrity Plugin does not work with parameterized builds
Thorsten Liepert
created JENKINS-21826
Integrity Plugin does not work with parameterized builds
Issue Type:
Bug
Affects Versions:
current
Assignee:
Cletus DSouza
Components:
integrity-plugin
Created:
17/Feb/14 8:33 AM
Description:
A parameterized build where the checkpoint is given as a text parameter
the follwoing exception is thrown:
FATAL: No such property: Release_Checkpoint for class: Script1
groovy.lang.MissingPropertyException: No such property: Release_Checkpoint for class: Script1
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:50)
at org.codehaus.groovy.runtime.callsite.PogoGetPropertySite.getProperty(PogoGetPropertySite.java:49)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callGroovyObjectGetProperty(AbstractCallSite.java:231)
at Script1.run(Script1.groovy:1)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:580)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:618)
at groovy.lang.GroovyShell.evaluate(GroovyShell.java:589)
at hudson.scm.IntegrityCheckpointAction.evalGroovyExpression(IntegrityCheckpointAction.java:86)
at hudson.scm.IntegritySCM.buildEnvVars(IntegritySCM.java:536)
at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:918)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:90)
at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66)
at org.jenkinsci.plugins.preSCMbuildstep.PreSCMBuildStepsWrapper.preCheckout(PreSCMBuildStepsWrapper.java:122)
at jenkins.scm.SCMCheckoutStrategy.preCheckout(SCMCheckoutStrategy.java:78)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:559)
at hudson.model.Run.execute(Run.java:1670)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:231)
The Project is configured as followed:
#/_Projects/XYZ#ABC/ABCD/EFGH/CDE/UVW#$Release_Checkpoint
where $Release_Checkpoint is the given paramter. Also the format ${Release_Checkpoint} does throw the exception.
The only LogEntry is
Feb 17, 2014 9:30:57 AM DEBUG IntegritySCM - buildEnvVars() invoked...!
Environment:
Ubuntu 12.04 LTS
Project:
Jenkins
Priority:
Major
Reporter:
Thorsten Liepert
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-8765) Notify job configuration editor when someone else is editing it at the same time, or make it read only for the other person
Oleg Nenashev updated JENKINS-8765 Notify job configuration editor when someone else is editing it at the same time, or make it read only for the other person Change By: Oleg Nenashev (17/Feb/14 8:38 AM) Labels: configuration Component/s: core 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] [groovy] (JENKINS-10974) Using a Groovy Command build step with the pre-scm-buildstep plugin returns a 500 server error
Oleg Nenashev updated JENKINS-10974 Using a Groovy Command build step with the pre-scm-buildstep plugin returns a 500 server error Added component definitions to the issue's description. Change By: Oleg Nenashev (17/Feb/14 8:40 AM) Component/s: groovy Component/s: prescmbuildstep 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-11446) Environment variable replacement issue on WINDOWS
Oleg Nenashev updated JENKINS-11446 Environment variable replacement issue on WINDOWS Added component definitions to the issue's description. Change By: Oleg Nenashev (17/Feb/14 8:42 AM) Labels: variables Component/s: core 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] [ant] (JENKINS-11437) Custom Ant location for running using either Windows or Linux Shell
Oleg Nenashev updated JENKINS-11437 Custom Ant location for running using either Windows or Linux Shell Added component definitions to the issue's description. Change By: Oleg Nenashev (17/Feb/14 8:44 AM) Component/s: ant 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] [scm-sync-configuration] (JENKINS-21827) Error with SCM-syn-configuration
Andrea Panattoni created JENKINS-21827 Error with SCM-syn-configuration Issue Type: Bug Affects Versions: current Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 17/Feb/14 8:45 AM Description: I installed the plugin and it worked a few days. Then it stopped to work and when I try to disable and enabled the plugin configuration I get the following error javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:52) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at
[JIRA] [copyartifact] (JENKINS-11385) Build selector for Copy Artifact generates invalid command line
Oleg Nenashev updated JENKINS-11385 Build selector for Copy Artifact generates invalid command line Added component definitions to the issue's description. Change By: Oleg Nenashev (17/Feb/14 8:45 AM) Component/s: copyartifact 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-10107) Files uploaded via Fileparameter is not available in matrix jobs and throws NPE
Oleg Nenashev updated JENKINS-10107 Files uploaded via Fileparameter is not available in matrix jobs and throws NPE Assigned the issue to the core. BTW, seems it has been already resolved... Change By: Oleg Nenashev (17/Feb/14 8:50 AM) Assignee: kokawa Component/s: core 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:391)
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?ownerId=oleg_nenashevavatarId=11787;
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=oleg_nenashev
id=email_oleg_nenashev
href=https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=oleg_nenashev;
style=color:#355564;Oleg Nenashev/a
resolved img src=https://issues.jenkins-ci.org/images/icons/bug.gif;
height=16 width=16 border=0 align=absmiddle alt=Bug a
style='color:#355564;text-decoration:none;'
[JIRA] [groovy-postbuild] (JENKINS-9992) Execute Groovy script after the launch of the downstream jobs
Oleg Nenashev updated JENKINS-9992 Execute Groovy script after the launch of the downstream jobs Assigned the issue to the proper component. Change By: Oleg Nenashev (17/Feb/14 8:52 AM) Component/s: groovy-postbuild 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] [groovy-postbuild] (JENKINS-10041) Excute the Groovy post build script as the last post build step
Oleg Nenashev updated JENKINS-10041 Excute the Groovy post build script as the last post build step Assigned the issue to the proper component. Change By: Oleg Nenashev (17/Feb/14 8:51 AM) Component/s: groovy-postbuild 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] [perforce] (JENKINS-9893) $JOB_NAME doesn't work with matrix projects due to illegal character '/' in workspace name
Oleg Nenashev updated JENKINS-9893 $JOB_NAME doesnt work with matrix projects due to illegal character / in workspace name Assigned the issue to the proper component. BTW, seems that the issue has been already solved Change By: Oleg Nenashev (17/Feb/14 8:55 AM) Labels: matrixperforce Assignee: RobPetti Component/s: perforce 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] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin
Alex Earl commented on JENKINS-21760 Unable to attach pdf as an attachment in email-ext plugin Please attach a screenshot of the job configuration showing the attachment pattern field. 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-10091) Concurrent fingerprint corruption
Oleg Nenashev updated JENKINS-10091 Concurrent fingerprint corruption Assigned the issue to the core. BTW, most probably the issue has been resolved Change By: Oleg Nenashev (17/Feb/14 8:56 AM) Labels: fingerprints Component/s: core 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-9775) Generic URL to access latest log for job
Oleg Nenashev updated JENKINS-9775 Generic URL to access latest log for job Assigned the issue to the core. Change By: Oleg Nenashev (17/Feb/14 8:57 AM) Component/s: core 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] [platformlabeler] (JENKINS-9586) Sometimes after Jenkins restart platform labels are not available
Oleg Nenashev updated JENKINS-9586 Sometimes after Jenkins restart platform labels are not available Assigned the issue to the proper component. Change By: Oleg Nenashev (17/Feb/14 8:58 AM) Component/s: platformlabeler 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-9561) Add a Save button to the top of config pages
Oleg Nenashev updated JENKINS-9561 Add a Save button to the top of config pages Assigned the issue to the core. Change By: Oleg Nenashev (17/Feb/14 8:59 AM) Labels: configuration Component/s: core 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] [configurationslicing] (JENKINS-9478) NullPointerException while submitting config slicer logrotationbuilds or logrotationdays
Oleg Nenashev updated JENKINS-9478 NullPointerException while submitting config slicer logrotationbuilds or logrotationdays Assigned the issue to the proper component. Change By: Oleg Nenashev (17/Feb/14 9:01 AM) Component/s: configurationslicing 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] [ldap] (JENKINS-9543) uppercase ldap groupnames appear to work but don't
Oleg Nenashev updated JENKINS-9543 uppercase ldap groupnames appear to work but dont Assigned the issue to the proper component. Change By: Oleg Nenashev (17/Feb/14 9:00 AM) Component/s: ldap 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] [ldap] (JENKINS-9543) uppercase ldap groupnames appear to work but don't
Oleg Nenashev updated JENKINS-9543 uppercase ldap groupnames appear to work but dont Change By: Oleg Nenashev (17/Feb/14 9:01 AM) Assignee: KohsukeKawaguchi 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] [integrity-plugin] (JENKINS-9477) [integrity-plugin] MKS plugin consumes 1 file descriptor on MKS server per file in project to check-out
Oleg Nenashev updated JENKINS-9477 [integrity-plugin] MKS plugin consumes 1 file descriptor on MKS server per file in project to check-out Assigned the issue to the proper component. Change By: Oleg Nenashev (17/Feb/14 9:02 AM) Component/s: integrity-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 -- 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] [parameterized-trigger] (JENKINS-9332) parameterized-trigger with multiple triggers only fires first one
Oleg Nenashev updated JENKINS-9332 parameterized-trigger with multiple triggers only fires first one Assigned the issue to the proper component. Change By: Oleg Nenashev (17/Feb/14 9:03 AM) Component/s: parameterized-trigger 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] [parameterized-trigger] (JENKINS-9332) parameterized-trigger with multiple triggers only fires first one
Oleg Nenashev resolved JENKINS-9332 as Fixed parameterized-trigger with multiple triggers only fires first one Seems that the issue has been solved in 2.9 (Jul 10, 2011) Change By: Oleg Nenashev (17/Feb/14 9:06 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 -- 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] [scm-sync-configuration] (JENKINS-21827) Error with SCM-syn-configuration
Frédéric Camblor closed JENKINS-21827 as Wont Fix Error with SCM-syn-configuration I can't support every jenkins version in the wild. Will only support LTS versions. Could you try with latest (1.532.2) and see if you can reproduce your problem ? Change By: Frédéric Camblor (17/Feb/14 9:12 AM) Status: Open Closed Resolution: WontFix 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-11434) Check for Java on install
Oleg Nenashev updated JENKINS-11434 Check for Java on install Assigned the issue to the core. BTW, it's hard to check Java due to huge number of possible installations. AFAIK, the current version of /etc/init.d/jenkins checks several locations. Change By: Oleg Nenashev (17/Feb/14 9:13 AM) Labels: installationrpm Component/s: core 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-21822) java.lang.OutOfMemoryError out of nothing
vjuranek commented on JENKINS-21822 java.lang.OutOfMemoryError out of nothing Hi, does it happen repeatedly? Did you check https://wiki.jenkins-ci.org/display/JENKINS/I'm+getting+OutOfMemoryError ? 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/groups/opt_out.
[JIRA] [core] (JENKINS-21822) java.lang.OutOfMemoryError out of nothing
Michael Mosmann commented on JENKINS-21822 java.lang.OutOfMemoryError out of nothing No, only once. Than i did increase the jvm memory. I thought, the stack trace would help somehow. It felt like a endless recursion which where stopped by OOM-Exception. 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] [nodelabelparameter] (JENKINS-21828) java.lang.IllegalArgumentException: Malformed \uxxxx encoding.
Sven Appenrodt created JENKINS-21828 java.lang.IllegalArgumentException: Malformed \u encoding. Issue Type: Bug Affects Versions: current Assignee: Dominik Bartholdi Components: nodelabelparameter Created: 17/Feb/14 11:02 AM Description: Message for locale de contains "ü" See: file:/...Jenkins/plugins/nodelabelparameter/WEB-INF/lib/nodelabelparameter.jar!/org/jvnet/jenkins/plugins/nodelabelparameter/Messages_de.properties Property: NodeListBuildParameterFactory.skippOfflineNode This causes any donwnstream project triggered on any slave/master to fail with an exception: FATAL: Malformed \u encoding. java.lang.IllegalArgumentException: Malformed \u encoding. at java.util.Properties.loadConvert(Properties.java:552) at java.util.Properties.load0(Properties.java:375) at java.util.Properties.load(Properties.java:325) at java.util.PropertyResourceBundle.init(PropertyResourceBundle.java:111) at org.jvnet.localizer.ResourceBundleHolder$ResourceBundleImpl.init(ResourceBundleHolder.java:114) at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:88) at org.jvnet.localizer.ResourceBundleHolder.get(ResourceBundleHolder.java:102) at org.jvnet.localizer.ResourceBundleHolder.format(ResourceBundleHolder.java:139) at org.jvnet.jenkins.plugins.nodelabelparameter.Messages.LabelBadgeAction_label_tooltip_node(Messages.java:101) at org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterValue.addBadgeToBuild(LabelParameterValue.java:253) at org.jvnet.jenkins.plugins.nodelabelparameter.LabelParameterValue.createBuildWrapper(LabelParameterValue.java:205) at hudson.model.ParametersAction.createBuildWrappers(ParametersAction.java:78) at hudson.model.Build$BuildExecution.doRun(Build.java:151) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Please replace the "ü" with the correspondung \uxxx code. Thx Environment: Jenkins version: 1.550 nodelabel parameter plugin version: 1.5.0 Project: Jenkins Priority: Critical Reporter: Sven Appenrodt 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] [parameterized-trigger] (JENKINS-21829) Console output should print build number when adding a build to the queue
Hallvard Nygård created JENKINS-21829 Console output should print build number when adding a build to the queue Issue Type: Improvement Assignee: huybrechts Attachments: jenkins-pending.PNG Components: parameterized-trigger Created: 17/Feb/14 11:53 AM Description: I'm using this plugin in two scenarios. In both I would like to get the build number at the time that the job is added to the build queue. The executed jobs are long running and I want to open up the console while they are running. When the job enters the queue, a build number is created. See screenshot. The two different running modes: With "Block until the triggered projects finish their builds" Without "Block until the triggered projects finish their builds" With "Block until the triggered projects finish their builds": Line 1: Waiting for the completion of Job name - long running tests Line 2: Job name - long running tests #1040 completed. Result was FAILURE Line 3: Finished: FAILURE Line 1 appears when the job enter the queue. Line 2 and 3 appears after the job has finished. Should be: Line 1: Waiting for the completion of Job name - long running tests #1040 Line 2: Job name - long running tests #1040 completed. Result was FAILURE Line 3: Finished: FAILURE Without "Block until the triggered projects finish their builds" Line 1: Triggering projects: Job name - long running tests Line 2: Finished: SUCCESS Line 1 appears when the job enter the queue. Line 2 appears after the job has finished. Should be: Line 1: Triggering projects: Job name - long running tests #1040 Line 2: Finished: SUCCESS Project: Jenkins Priority: Major Reporter: Hallvard Nygård 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-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked
Mark Waite updated JENKINS-21622 Build creates new workspace@2 (and so on) when option concurrent builds NOT checked Change By: Mark Waite (17/Feb/14 11:58 AM) Component/s: core Component/s: git 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] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
Branz Frandwein commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials I'm facing the same problem, this is very frustrating. Any workarounds? 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] [git-client] (JENKINS-21032) git executable should be determined by node, not by the host
Mark Waite resolved JENKINS-21032 as Not A Defect git executable should be determined by node, not by the host The user has configured the Jenkins master incorrectly. This is not a bug, but rather an incorrect configuration. Change By: Mark Waite (17/Feb/14 12:10 PM) Status: Open Resolved Resolution: NotADefect 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] [git-client] (JENKINS-21032) git executable should be determined by node, not by the host
Mark Waite closed JENKINS-21032 as Not A Defect git executable should be determined by node, not by the host Change By: Mark Waite (17/Feb/14 12:10 PM) Status: Resolved Closed 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails http://stackoverflow.com/questions/5343068/is-there-a-way-to-skip-password-typing-when-using-https-github describes alternatives based on the version of git you are running. 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-21822) java.lang.OutOfMemoryError out of nothing
vjuranek commented on JENKINS-21822 java.lang.OutOfMemoryError out of nothing hm, stacktrace IMHO doesn't suggest any infinite recursion. Moreover in such case, I would expect StackOverflowError rather than OOM. 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] [git-client] (JENKINS-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Mark Waite closed JENKINS-21745 as Fixed [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL Change By: Mark Waite (17/Feb/14 12:15 PM) Status: Resolved Closed 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-21822) java.lang.OutOfMemoryError out of nothing
vjuranek resolved JENKINS-21822 as Not A Defect java.lang.OutOfMemoryError out of nothing as mention in previous comment, it seems to me, that you just have too low heap limit, so closing. Of course I can be wrong, so feel free to re-open, especially if you experience it again with increased heap limit. And thanks for reporting. Change By: vjuranek (17/Feb/14 12:16 PM) Status: Open Resolved Resolution: NotADefect 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] [git-client] (JENKINS-21745) [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL
Mark Waite resolved JENKINS-21745 as Fixed [git-client] NoClassDefFoundException: ...GitClient when trying to paste a repository URL Marking this issue as resolved, since the submitter noted that it was a configuration error, not a bug in the git-client plugin. Change By: Mark Waite (17/Feb/14 12:14 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 -- 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] [git-client] (JENKINS-21520) NoClassDefFoundError in git client 1.6.1
Mark Waite commented on JENKINS-21520 NoClassDefFoundError in git client 1.6.1 The related bug report has been closed as a configuration error. Have you found a configuration related solution to this problem as well? If not, can you provide more details about the configuration you're running? Have you installed the latest version of the plugins (including credentials)? Are any of your plugins disabled? Are any of your plugins pinned to older versions? 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] [throttle-concurrents] (JENKINS-21830) Throttle-concurrents -plugin do not recognise new slave nodes generated after build are on queue
Samu Wikstedt created JENKINS-21830 Throttle-concurrents -plugin do not recognise new slave nodes generated after build are on queue Issue Type: Bug Affects Versions: current Assignee: abayer Components: throttle-concurrents Created: 17/Feb/14 12:18 PM Description: Situation: Jenkins project uses matrix build (dynamic axis) to create massive job load Jobs are put on the queue since there is not enough executors on master and slave nodes separate load balancer starts new slave nodes from cloud-cluster, which are connected to master with help of swarm-plugin. throttle-plugin allows jobs from queue to be run only on slaves that were existing before jobs were launched. If throttle plugin is removed, all new slave nodes are utilized immediately. On situation described, throttle plugin also seems to stuck jenkins GUI. (After removal of throttle, GUI doesn't get stuck ). I have no idea what kind of logs/trace I should focus on, so feel free to ask those if needed. Environment: Linux (RHEL)/64 bit jenkins: 1.532.1 (LTS) throttle: 1.8.1 Project: Jenkins Labels: plugin jenkins Priority: Major Reporter: Samu Wikstedt 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] [git-client] (JENKINS-19921) Git clone fails with JGit and SSH Credentials
Mark Waite commented on JENKINS-19921 Git clone fails with JGit and SSH Credentials Could you check to see if this problem still exists in git-client-plugin 1.6.2 and in git-plugin 2.0.1? A number of other authentication issues have been resolved since this bug was reported, and this one may have been resolved as well. 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] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing
x29a reopened JENKINS-18443 SkipNoTestFiles flag ignored. Build still set to failed if test files missing Unfortunately, it still doesnt work. On version 1.82 (jenkins 1.544), i have enabled "Skip if there are no test files" for all configurations and get: Archiving artifacts [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing CppUnit-1.12.1 (default) [xUnit] [INFO] - [CppUnit-1.12.1 (default)] - No test report file(s) were found with the pattern '*UnitTestU.log' relative to 'e:\jenkins\workspace\job' for the testing framework 'CppUnit-1.12.1 (default)'. Did you enter a pattern relative to the correct directory? Did you generate the result report(s) for 'CppUnit-1.12.1 (default)'? [xUnit] [WARNING] - No test reports found for the metric 'CppUnit' with the resolved pattern '*UnitTestU.log'. [xUnit] [INFO] - Failing BUILD because 'set build failed if errors' option is activated. [xUnit] [INFO] - There are errors when processing test results. [xUnit] [INFO] - Skipping tests recording. [xUnit] [INFO] - Stop build. Build step 'Publish xUnit test result report' changed build result to FAILURE Finished: FAILURE Change By: x29a (17/Feb/14 12:24 PM) Resolution: Fixed 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 -- 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] [git] (JENKINS-20446) Git Plugin 2.0 has changed contents of GIT_BRANCH
Mark Waite updated JENKINS-20446 Git Plugin 2.0 has changed contents of GIT_BRANCH Removed git-client and git-parameter since the definition of the GIT_BRANCH environment variable is in git-plugin Change By: Mark Waite (17/Feb/14 12:26 PM) Labels: git git-client Component/s: git-client Component/s: git-parameter 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] [nodelabelparameter] (JENKINS-21828) java.lang.IllegalArgumentException: Malformed \uxxxx encoding.
Sven Appenrodt updated JENKINS-21828 java.lang.IllegalArgumentException: Malformed \u encoding. There are 2 additional problems in this file, so please diff and/or use this one. Change By: Sven Appenrodt (17/Feb/14 12:25 PM) Attachment: Messages_de.properties 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] [git] (JENKINS-21298) Git polling not ignoring excluded users
Mark Waite updated JENKINS-21298 Git polling not ignoring excluded users Assigned to git component, since exclusion processing is handled in git-plugin rather than in git-client-plugin. Change By: Mark Waite (17/Feb/14 12:28 PM) Labels: git git-clientgitplugin Component/s: git Component/s: git-client 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] [git-client] (JENKINS-20196) Failed to connect to URL (status = 404)
Mark Waite commented on JENKINS-20196 Failed to connect to URL (status = 404) Is this still an issue with git-plugin 2.0.1 and git-client-plugin 1.6.2? I'm able to insert the bitbucket user name and password into my https URL and it works as expected. I used https://markewaite:mypassw...@bitbucket.org/markewaite/git-client-plugin.git to check that works. 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] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower Won't the reference repository option available in "Advanced clone options" give you most of the same performance benefits? 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] [git-client] (JENKINS-21032) git executable should be determined by node, not by the host
Orgad Shaneh commented on JENKINS-21032 git executable should be determined by node, not by the host Right. Sorry for the noise. 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] [git-client] (JENKINS-20614) Git client discards the exception message on error case in HttpClient
Mark Waite resolved JENKINS-20614 as Fixed Git client discards the exception message on error case in HttpClient The method has been replaced in the current implementation and now includes the generated exception in the GitException which is thrown from the checkCredentials() method. Change By: Mark Waite (17/Feb/14 12:48 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 -- 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] [git-client] (JENKINS-20614) Git client discards the exception message on error case in HttpClient
Mark Waite closed JENKINS-20614 as Fixed Git client discards the exception message on error case in HttpClient Change By: Mark Waite (17/Feb/14 12:48 PM) Status: Resolved Closed 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Juergen Klasen commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails I'd like to update the info here with two things ... 1st: (about the latest remarks on the GIT version) : YES, you need a GIT that understands the '--local' option. But even then ... (see 2nd) 2nd: I got everything running okay with plugins 'credential-helper' 1.9.4, 'git plugin' 2.0.1 and 'GIT client plugin' 1.6.4 on a LINUX system. However using the same combination of plugins on WINDOWS, I still can't get it to work - although I'm using identical Jenkins configurations there !? P.S.: The Jenkins version was in both cases 1.549 Obviously Jenkins is behaving differently on Windows and on Linux !?? ... possibly an issue with the used Java version? On Linux I right now use Java7U45. On Windows the system is running Jenkins with J7U25. Can't upgrade the Java here now ... Maybe try this as next when the use of the machine allows "downtime". Can't test further on the Windows system this week, as this in produciton use ... 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Is the Windows machine running the Jenkins process (master or slave) as a service? JENKINS-20356 reports that credentials don't work as expected on Windows when the Jenkins process is running as a service. Jenkins behaves differently on Windows and Linux in many cases, most often due to platform differences (symbolic links are handled quite differently between the two platforms, open files are handled quite differently between the two platforms, etc.). 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] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Marek Sieradzki commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower How does this "reference repository" work? Is specifying both main setting and reference repository to the same mirror that I'm using enough for fast clone to take place? 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-21822) java.lang.OutOfMemoryError out of nothing
Michael Mosmann commented on JENKINS-21822 java.lang.OutOfMemoryError out of nothing ok 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 -- 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] [jenkins-jira-issue-updater] (JENKINS-21514) Add fixed version support to jira issue updater plugin
Hua Zhang resolved JENKINS-21514 as Fixed Add fixed version support to jira issue updater plugin PR merged and released with version 1.7. Change By: Hua Zhang (17/Feb/14 1:51 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 -- 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] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower I believe that should be sufficient. The --reference argument is not precisely the same as the --local argument, but I've seen significantly faster and smaller clones of large repositories since I've been using the --reference argument to refer to a bare repository copy which is kept on each of the slaves. 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] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Marek Sieradzki commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower Option that you recommended works but I find it a bit unintuitive. When one does git clone from command line, it automatically detects that repository is located on the same drive. This is also how it worked in earlier version of git plugin. I'd prefer to avoid adding slightly duplicate setting to our ~350 jobs. I measured time required to run basic "echo world" job that checks out git repository we're using internally: no reference path, deep clone: ~4 minutes reference path, deep clone: ~1 minute reference path, shallow clone: 15 seconds 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] [git] (JENKINS-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Mark Waite closed JENKINS-21057 as Fixed Cannot checkout git repository with submodules: FATAL: No remotes found! Change By: Mark Waite (17/Feb/14 2:03 PM) Status: Resolved Closed 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] [git] (JENKINS-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Mark Waite resolved JENKINS-21057 as Fixed Cannot checkout git repository with submodules: FATAL: No remotes found! git-plugin 2.0.1 and git-client-plugin 1.6.2 include the fix for this. Future versions of git-client-plugin (after 1.6.2) will have the further refinement that the plugin consistently assigns a remote when cloning, whether using JGit or command line git, and whether the internal implementation is a clone or an init and fetch. Change By: Mark Waite (17/Feb/14 2:03 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 -- 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] [gerrit-trigger] (JENKINS-19951) Build to be kept in the queue until replication is complete to gerrit slave(s)
Hugo Ares updated JENKINS-19951 Build to be kept in the queue until replication is complete to gerrit slave(s) Change By: Hugo Ares (17/Feb/14 2:05 PM) Summary: Buildtobekeptinthequeueuntilreplicationiscompletetogerrit mirror slave (s) Description: Thisfeaturewillallowanadministratortoconfiguregerrit-triggertowaitforthereplicationtooneormoregerrit mirror( slave (mirror )tobecompletedbeforethebuildgetassignedtoanexecutor.Problematic:Ifgerrit-triggerisusedinasetupwherethereisaGerritmasterandmirror(s),gerrit-triggerislisteningforGerriteventonthemasterandtriggeringthebuildaccordinglybut,mostofthetime,thebuildwillbeexecutedandwilltrytopullthechangefromthemirrorbeforeGerritisdonereplicatingthechangetothemirrorwhichiscausingthebuildtofail.Solution:Ifgerrit-triggerisconfiguredtowaitforoneormore mirror slave ,thegerriteventwillcreatethebuildanditwillgetqueuedbutgerrit-triggerwillalsovetoifthebuildcanrundependingifthereplicationisdonetothat mirror slave .Theuserwouldseethatthebuildisinqueueandamessagelike:waitingforreplicationto mirror_name slave_name .Notalltypesofgerriteventneedtobereplicatedtomirror,hereisthelistofeventthatdoneedtowaitreplication:patchsetcreate,changemergerandrefupdated.GerritcurrentlydoesnotpublishreplicationeventbutIamworkingonaddingthisfeaturetogerrit. 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-5065) Installing Hudson as a windows service on Vista 64 Bit
Mark Waite resolved JENKINS-5065 as Fixed Installing Hudson as a windows service on Vista 64 Bit Resolving this bug because Windows Vista is no longer a relevant operating system Windows 7 installs and runs as a service with 1.532.2 (and earlier) Other Windows operating systems are expected to work just as reliably Change By: Mark Waite (17/Feb/14 2:07 PM) Status: Reopened 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 -- 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-5065) Installing Hudson as a windows service on Vista 64 Bit
Mark Waite closed JENKINS-5065 as Fixed Installing Hudson as a windows service on Vista 64 Bit Change By: Mark Waite (17/Feb/14 2:07 PM) Status: Resolved Closed 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] [analysis-collector] (JENKINS-21831) optional dependencies are not optional anymore
Andreas Pakulat created JENKINS-21831 optional dependencies are not optional anymore Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-collector Created: 17/Feb/14 2:09 PM Description: It seems like some change between 1.36 and 1.39 causes the originally optional dependencies on the dry, warnings, pmd and possibly other plugins to be hard requirements. We have an installation where at least the dry plugin is missing and accessing the main page of jobs that use the 'publish combined analysis' post build task is not possible. Chrome indicates the following error when visiting jenkins/job/jobname/: The webpage at http://jenkins/job/jobname/ might be temporarily down or it may have moved permanently to a new web address. Error code: ERR_CONTENT_DECODING_FAILED Firefox behaves the same way. Fetching the URL through wget retrieves an unfinished html file. Either removing the post-build task or disabling the plugin fixes the problem. In the jenkins log each time the url is visited this error occurs: javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1 .532.2.jar!/hudson/model/AbstractProject/main.jelly:76:66: st:include hudson/plugins/dry/DryProjectAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) 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:96) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) 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.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [parameterized-trigger] (JENKINS-12479) Add checkbox to add an executor when blocking
Dominic cleal commented on JENKINS-12479 Add checkbox to add an executor when blocking I was thinking this could use a flyweight task to execute the job that's being blocked on. This way the lifecycle of the executor is directly tied to the blocked job, no worries that the new executor might start running a really long job. If the job being blocked on can be run on the same node, then launch it as a flyweight. If it can't, don't and then execute + block normally. 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] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower I'm of the opposite opinion. I think the "--local" option is unintuitive in a Jenkins context, since it seems it will only work if the repository URL is a path to a repository on the same file system as the Jenkins workspace. I rarely have a Jenkins environment with no slaves, and when I add the slaves, that "same file system" requirement is no longer a workable requirement. The reference option allows me to use the same configuration on the job whether it executes on the master or the slave, and I get the benefit of the reference repository if the referenced bare repository is available. 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Juergen Klasen commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Typically a Jenkins runs on a Windows box as service (so it does on a UNIX/LINUX env) ... and in my case it is like that However: The service is NOT started under the system account but runs under an own account (again: same as under UNIX the service doesn't run as 'root' user but under an own account) Why should one run a Jenkins service manually - unless it's for testing purposes? I can see a reason why it makes a difference if a procees runs under the system account, or under a user account. This is pretty evident. But I can not see a reason why it should make a difference whether a process is started during system startup, or later by a user - unless they would get a differently set up environment. But when starting a process under a user account, it should inherit all corresponding setting of the user, no matter if the service control manager is starting it, or not - 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 -- 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] [git-client] (JENKINS-21469) Change from git clone to init+fetch makes clone from local GIT mirror a lot slower
Mark Waite commented on JENKINS-21469 Change from git clone to init+fetch makes clone from local GIT mirror a lot slower If that's not workable for you, you could submit a pull request with unit tests and the code change to implement the --local option to meet 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 -- 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] [gerrit-trigger] (JENKINS-19951) Build to be kept in the queue until replication is complete to gerrit slave(s)
Hugo Ares commented on JENKINS-19951 Build to be kept in the queue until replication is complete to gerrit slave(s) Replication events are published in Gerrit 2.9. For Gerrit-Trigger, I submited a pull request which add this feature: https://github.com/jenkinsci/gerrit-trigger-plugin/pull/133. 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski updated JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Attached are the method traces for before and after the hot Fix. The hot fix eliminated 4 seconds of time on the getPrivateMacros method. Change By: Walter Kacynski (17/Feb/14 2:20 PM) Attachment: preHotFixMethods.png Attachment: hotFixMethods.png 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails I rarely run Jenkins as a service on any of the Windows machines I configure. Most of the products which I need to build and test are working from the assumption that if they are running on Windows they have access to the Windows Desktop. Access to the Windows Desktop is most directly available by running the Jenkins master and Jenkins slaves from a command prompt on the Windows Desktop. I realize that there is a setting which allows a service to interact with the Desktop, but that is not the typical environment where my programs run. They are more likely to run on a real desktop, as real desktop programs. There have been several bugs reported which have been related to Jenkins running as a service on Windows. I prefer to avoid those bugs by running on the Desktop. I don't know why the git-client-plugin has this difference when running from a service or not. If I find a way to write automated tests of credentials in the git-client-plugin, that will probably also lead to a solution to JENKINS-20356. Until then, it will probably remain open as a bug. 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] [artifactory] (JENKINS-21832) Can't fetch remote repositories nor deploy
Henri Gomez created JENKINS-21832 Cant fetch remote repositories nor deploy Issue Type: Bug Affects Versions: current Assignee: yossis Components: artifactory Created: 17/Feb/14 2:26 PM Description: Since we updated our Artifactory Plugin from 2.1.8 to 2.2.1 on our Jenkins (LTS 1.532.1) we can't : Browse remote repositories in job Artifactory Deploy section We cannot deploy artifacts anymore We had to revert to 2.1.8 to get both works again Environment: Jenkins 1.532.1 LTS, Artifactory Plugin 2.2.1 Project: Jenkins Priority: Major Reporter: Henri Gomez 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) So, the next question, how do I dig down into the methods calls to compromise Scriptcontent|evaluate 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Juergen Klasen commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Hmmmh, no sysadmin background ... I suppose ? (no offense here !) BUT: Why should one run a program that is supposed to provide a service function (this is where the name is coming from ) under the expectation that it has access to the Desktop? Jenkins is not meant to be run as a desktop program !!! Obviously you seem to have got the idea fundamentally wrong !? And: If there should be plugins for a service(and this is, what Jenkins is all about: a service!) which behave differently under such conditions they are implemented faulty. No discussion about that ... Maybe you're mixing things like "running under system account vs. running under a user account" ? 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] [maven2] (JENKINS-21833) Problem accessing static files bundled inside a plugin using the latest Jenkins releases (1.548+)
Guglielmo Iozzia created JENKINS-21833 Problem accessing static files bundled inside a plugin using the latest Jenkins releases (1.548+) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: maven2 Created: 17/Feb/14 2:39 PM Description: Trying to access a static resource in the the src/main/resources folder (or any of its subfolders) of any plugin generated through Maven 3 like in the following example: URL url = "" + xmlFile); File xmlFile = new File(url.getPath()); The following exception is thrown: Caused by: java.io.FileNotFoundException: C:\Guglielmo\Software\Jenkins\1.551\fi le:\C:\Users\Administrator\.jenkins\plugins\lc-plugin\WEB-INF\lib\classes. jar!\ServerList.xml (The filename, directory name, or volume lab el syntax is incorrect.) at java.io.FileInputStream.init(FileInputStream.java:137) at java.io.FileInputStream.init(FileInputStream.java:96) at sun.net.www.protocol.file.FileURLConnection.connect(FileURLConnection .java:82) at sun.net.www.protocol.file.FileURLConnection.getInputStream(FileURLCon nection.java:173) But the ServerList.xml file is bundled in the classes.jar of this plugin (and the other custom plugins of ours) and it is loaded in the classpath (we are able to get its InputStream from there at runtime). The code above works fine with Jenkins releases up to 1.547. It isn't working with the latest one 1.551 too. Project: Jenkins Priority: Major Reporter: Guglielmo Iozzia 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Your assertion that Jenkins is supposed to provide a service function solely within the context of a Windows service does not match my use model, nor does it match the use model of many Jenkins users. Jenkins provides the capability to build, test, and report results. Many test contexts require desktop access. As an example, Selenium tests need access to a desktop so that they can drive the web browser. Desktop applications often assume desktop access even when running in test mode. 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] [artifactory] (JENKINS-21832) Can't fetch remote repositories nor deploy
Henri Gomez updated JENKINS-21832 Cant fetch remote repositories nor deploy Change By: Henri Gomez (17/Feb/14 2:50 PM) Environment: Jenkins1.532.1LTS,ArtifactoryPlugin2.2.1 ,Java1.6.0u45,Tocmat7.0.50 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] [artifactory] (JENKINS-21832) Can't fetch remote repositories nor deploy
Henri Gomez updated JENKINS-21832 Cant fetch remote repositories nor deploy Change By: Henri Gomez (17/Feb/14 2:50 PM) Environment: Jenkins1.532.1LTS,ArtifactoryPlugin2.2.1,Java1.6.0u45, Tocmat Tomcat 7.0.50 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] [git] (JENKINS-20818) git plugin 2.0 started giving error to connect git over https
Mark Waite commented on JENKINS-20818 git plugin 2.0 started giving error to connect git over https Could you check again with git-plugin 2.0.1 and git-client-plugin 1.6.2? The git-client-plugin credentials implementation is more mature now and has been confirmed to work over https with or without credentials to GitHub and to bitbucket. There is a known bug ( JENKINS-20356 ) that the cloning with credentials does not work when Jenkins is running as a Windows service. There may also be issues with self-signed certificates on https servers, though I don't have access to a server with a self-signed certificate for testing. 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] [git] (JENKINS-20861) git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option
Mark Waite resolved JENKINS-20861 as Fixed git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option Released with git-client-plugin 1.62 or earlier. Change By: Mark Waite (17/Feb/14 2:59 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 -- 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Juergen Klasen commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails Again: No offense - BUT ... If your "use model" is to use Jenkins interactively, and believe that this is the intended way to use Jenkins then you must have got it wrong. JENKINS IS ALL ABOUT USING IT AS A SERVICE. Jenkins is supposed to run on some (if you want to put it this way) "background server", doing tasks like building software in an automated way running unit tests, code coverage and stylecheck test additionally it can deploy the build results to testing environments trigger tests of the deployed software remotely collect the test results display them as report on the jobs dashboard page etc. And it's supposed to do all this with NO INTERACTION required! If you don't get this concept - and do not accept that this is the main usage of Jenkins - then you are definitely on a wrong path ! Sorry ... 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] [git] (JENKINS-20861) git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option
Mark Waite closed JENKINS-20861 as Fixed git plugin 2.0 does not correctly migrate 1.5 configs using reference repo option Change By: Mark Waite (17/Feb/14 3:00 PM) Status: Resolved Closed 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] [jenkins-multijob-plugin] (JENKINS-21798) Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds
Dan Dumont commented on JENKINS-21798 Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds During profiling, we saw a huge amount of calls to this: https://github.com/jenkinsci/tikal-multijob-plugin/blob/master/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuilder.java#L200 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] [jenkins-multijob-plugin] (JENKINS-21649) High CPU Usage on master while slaves working (multijob)
Dan Dumont commented on JENKINS-21649 High CPU Usage on master while slaves working (multijob) There's more information in JENKINS-21798 The thread trace is misleading, as the threads round-robin the work. 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] [jenkins-multijob-plugin] (JENKINS-21798) Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds
Dan Dumont commented on JENKINS-21798 Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds Note: a manual downgrade to 1.10 fixed the issue for us. 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Alex Earl commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) ScriptContent.evaluate will use GroovyShell to evaluate the template. Not sure if you are currently looking at hudson.plugins.emailext.plugins.content in your traces. 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Mark Waite commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails This exchange seems to be no longer useful. It seems you will continue to insist that I'm on the wrong path if I require desktop access for tests. I've invested many years contributing to Jenkins, using Jenkins, and administering continuous integration servers. I'm comfortable that mine is not the only use model, but am just as comfortable that the use model you're proposing is also not the only use model. The Selenium test users (including Jenkins' own testing with Selenium) would likely disagree with you, as would all those users who use the Xvnc plugin on Linux. I'll resume trying to contribute to Jenkins, without worrying about your perceptions of how I use Jenkins. 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] [jenkins-multijob-plugin] (JENKINS-21798) Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds
Dan Dumont commented on JENKINS-21798 Multi Job Plugin causes CPU to max out due to updateSubBuild executing millions of times in a few seconds Related: JENKINS-21649 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] [git] (JENKINS-20533) Git2 plugin and HTTP-authentication fails
Juergen Klasen commented on JENKINS-20533 Git2 plugin and HTTP-authentication fails quoteThis exchange seems to be no longer useful./quote Full ACK - This exchange really seems to be no longer useful. -- BTW - About running Selenium Tests: The typical way is to deploy the built software package to a (mostly remote) testing environment (along with the Selenium scripts), then trigger the script execution on this environment, collect the test result data and display it in the report on Jenkins. We have done lot's of this, and all work without trouble and don't require any desktop/user-interface interaction at all. 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] [warnings] (JENKINS-21569) Expose current input line in groovy script
James Howe reopened JENKINS-21569 Expose current input line in groovy script Upgraded to 4.39, and get this error on the "Configure System" page when testing the script you added to the tests. An exception occurred during evaluation of the Groovy script: No such property: lineNumber for class: Script1 Change By: James Howe (17/Feb/14 3:33 PM) Resolution: Fixed 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 -- 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) I did a more detailed trace and the most time is spent in ScriptContent.renderTemplate for all my test, I'm using the same groovy based transfer template. In plugin version 2.36 render time is about 1.1 seconds In plugin version 2.37.2.1 render time is about 2.2 seconds for script / managed script based 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] [antisamy-markup-formatter] (JENKINS-21834) Permit user-configurable policies
Jesse Glick created JENKINS-21834 Permit user-configurable policies Issue Type: New Feature Assignee: Jesse Glick Components: antisamy-markup-formatter Created: 17/Feb/14 3:47 PM Description: Let the user configure RawHtmlMarkupFormatter using a textarea containing a definition compliant with antisamy.xsd, with buttons to load predefined profiles like that for MySpace. Project: Jenkins 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 -- 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) I'm not familiar at all with Groovy and how it works within the JVM. I could try switching to Java 6 to see if there is any performance change. 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)
Walter Kacynski commented on JENKINS-20078 email-ext plugin takes a huge amount of time to send out final status emails (30min) Overall, I think that the latest caching changes can be pushed up, and I can investigate the rending performance as a separate item. 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] [antisamy-markup-formatter] (JENKINS-21834) Permit user-configurable policies
Jesse Glick commented on JENKINS-21834 Permit user-configurable policies Should probably deprecate all the classes currently in the hudson.markup package, creating a fresh formatter (with a more appropriate name and description), and having RawHtmlMarkupFormatter.readResolve switch to it. 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] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
John Long commented on JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials I am also having this issue and I have not found a workaround. 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] [subversion] (JENKINS-21797) Subversion-Tagging Plugin can't create tag because of missing credentials
John Long updated JENKINS-21797 Subversion-Tagging Plugin cant create tag because of missing credentials Change By: John Long (17/Feb/14 3:51 PM) Component/s: svn-tag 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] [jobgenerator] (JENKINS-21238) Ability to run the generated job immediately after generation
Sylvain Benner edited a comment on JENKINS-21238 Ability to run the generated job immediately after generation Hi François, I added a check box in the job generator configuration page, it will be available shortly in the 1.21. Tell me if it does the 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 -- 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] [antisamy-markup-formatter] (JENKINS-21834) Permit user-configurable policies
Jesse Glick commented on JENKINS-21834 Permit user-configurable policies May be better to see https://code.google.com/p/owasp-java-html-sanitizer/wiki/Maven rather than using the current https://github.com/kohsuke/owasp-java-html-sanitizer wrapper. Seems that the OWASP Java HTML Sanitizer does not load AntiSamy XML definitions, so maybe this issue is moot, unless AntiSamy can also be bundled to allow configurable policies. 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] [cloudbees-folder] (JENKINS-20523) Implement ModelObjectWithChildren
SCM/JIRA link daemon commented on JENKINS-20523 Implement ModelObjectWithChildren Code changed in jenkins User: Jesse Glick Path: src/main/java/com/cloudbees/hudson/plugins/folder/Folder.java http://jenkins-ci.org/commit/cloudbees-folder-plugin/ac59f5238b0807041d6d60b1a9419db25d7b4173 Log: Merge pull request #6 from daniel-beck/JENKINS-20523 FIXED JENKINS-20523 Provide views list in breadcrumb bar Compare: https://github.com/jenkinsci/cloudbees-folder-plugin/compare/2bbf9ee189f6...ac59f5238b08 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.
