[JIRA] (JENKINS-16960) Status Code: 500/ NullPointerException when running command in slave script console
cforce created JENKINS-16960 Status Code: 500/ NullPointerException when running command in slave script console Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: vsphere-cloud Created: 26/Feb/13 8:53 AM Description: Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:203) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:306) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:36) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:32) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:244) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) 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
[JIRA] (JENKINS-16303) Console link missing in pop-up dialog on dashboard
Dirk Heinrichs commented on JENKINS-16303 Console link missing in pop-up dialog on dashboard Same here. It's missing only for some jobs while it's there for others. Jenkins version is 1.501. 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-16910) Email Ext-Plugin doesn't work with Jenkins 1.502
Alex Earl commented on JENKINS-16910 Email Ext-Plugin doesnt work with Jenkins 1.502 Do you have the Mailer plugin installed and enabled? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16946) Ratio percentgraph is wrong, bad alignment, length random
Ognjen Bubalo commented on JENKINS-16946 Ratio percentgraph is wrong, bad alignment, length random Hi Marcel, The bar is completely red because Missed Covered, of course we can change this, but as far as I know it was a request too. Please post a question about this in the mailing list: http://groups.google.com/group/jenkins-jacoco-plugin-mailing-list The aligment is broken for sure. I'll fix it ASAP. Thanks, Ogi 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-16910) Email Ext-Plugin doesn't work with Jenkins 1.502
Claudia Drabetz commented on JENKINS-16910 Email Ext-Plugin doesnt work with Jenkins 1.502 It's installed but not enabled (v1.4) and I cannot deinstall 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] (JENKINS-16962) Linux slave on different timezone - immediate ping timeout exception
Dominique Ledit created JENKINS-16962 Linux slave on different timezone - immediate ping timeout exception Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: build-timeout Created: 26/Feb/13 2:04 PM Description: The Jenkins server version is 1.480.1 The Jenkins master doesn't belong to the same timezone as the slave (The slave is 8 Hours behind) Slave Launch method: Launch slave agents on Unix machines via SSH A job run on this slave immediately failed. The corresponding output is: Started by user Dominique Ledit Building remotely on vm-hou-bldrh53cFATAL: channel is already closed hudson.remoting.ChannelClosedException: channel is already closed at hudson.remoting.Channel.send(Channel.java:493) at hudson.remoting.Request.call(Request.java:129) at hudson.remoting.Channel.call(Channel.java:664) at hudson.EnvVars.getRemote(EnvVars.java:202) at hudson.model.Computer.getEnvironment(Computer.java:844) at jenkins.model.CoreEnvironmentContributor.buildEnvironmentFor(CoreEnvironmentContributor.java:28) at hudson.model.Run.getEnvironment(Run.java:1952) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:843) at hudson.model.AbstractBuild$AbstractBuildExecution.decideWorkspace(AbstractBuild.java:462) at hudson.model.AbstractBuild$AbstractBuildExecution.run (AbstractBuild.java:482) at hudson.model.Run.execute(Run.java:1502) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Caused by: java.io.IOException at hudson.remoting.Channel.close(Channel.java:902) at hudson.slaves.ChannelPinger$1.onDead(ChannelPinger.java:110) at hudson.remoting.PingThread.ping(PingThread.java:120) at hudson.remoting.PingThread.run(PingThread.java:81) Caused by: java.util.concurrent.TimeoutException: Ping started on 1361148569659 hasn't completed at 1361148809659 ... 2 more Environment: Server: Red Hat Enterprise Linux Workstation release 6.2 (Santiago) Slave: Red Hat Enterprise Linux Server release 5.3 (Tikanga) Project: Jenkins Priority: Blocker Reporter: Dominique Ledit 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-16963) Job filter for
Thorsten Roemer created JENKINS-16963 Job filter for Issue Type: Improvement Affects Versions: current Assignee: Tomas Westling Components: build-failure-analyzer Created: 26/Feb/13 2:04 PM Description: What about a job filter, e.g. matching jobs with a cause found/not found? Project: Jenkins Priority: Minor Reporter: Thorsten Roemer 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-16963) job filter
Thorsten Roemer updated JENKINS-16963 job filter Change By: Thorsten Roemer (26/Feb/13 2:05 PM) Summary: Job job filter for 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-16962) Linux slave on different timezone - immediate ping timeout exception
Dominique Ledit commented on JENKINS-16962 Linux slave on different timezone - immediate ping timeout exception Is there any 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] (JENKINS-16963) Job filter
Thorsten Roemer updated JENKINS-16963 Job filter Change By: Thorsten Roemer (26/Feb/13 2:06 PM) Summary: job Job filter 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-16910) Email Ext-Plugin doesn't work with Jenkins 1.502
Alex Earl commented on JENKINS-16910 Email Ext-Plugin doesnt work with Jenkins 1.502 Please enable it and things should work. Changes in core version 1.494 split Mailer out if core. Email-ext is built against the LTS version (1.480), so you must have Mailer installed and enabled for anything 1.494 and above. 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-16910) Email Ext-Plugin doesn't work with Jenkins 1.502
Alex Earl resolved JENKINS-16910 as Not A Defect Email Ext-Plugin doesnt work with Jenkins 1.502 Please see my previous comment Change By: Alex Earl (26/Feb/13 2:18 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] (JENKINS-16964) TAP Plug-in does not fail builds with old reports
Bruno P. Kinoshita created JENKINS-16964 TAP Plug-in does not fail builds with old reports Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap Created: 26/Feb/13 2:35 PM Description: If you select the options "Fail the build if no test results are present" and "Discard old reports", the plug-in first checks if there are test results (this includes old reports) and then discard the old reports. It means that if you have old reports, you'll never fail a build due to no test results are present. This bug was reported via e-mail by Felipe Knorr Kuhn. Thanks mate! Project: Jenkins Priority: Minor Reporter: Bruno P. Kinoshita 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-16966) f:optionalBlock not indented correctly
Randy Coulman created JENKINS-16966 f:optionalBlock not indented correctly Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: optionalBlockLayout.png Components: core Created: 26/Feb/13 3:44 PM Description: When using an f:optionalBlock in a config.jelly file, the optional block is not indented like the other entries on the form. See the attachment for an example. See the URL for a config.jelly that exhibits this problem. In that code, I've worked around the problem with an explicit margin-left: 2em on the enclosing table. The layout issue might be related to the enclosing f:block and table elements, but if I leave those out, then the optionalBlock is always expanded when first opening the form, even if the checkbox is not checked. Project: Jenkins Labels: jenkins configuration jelly Priority: Minor Reporter: Randy Coulman 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-16662) Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds
cjo9900 resolved JENKINS-16662 as Fixed Add TRIGGERED_BUILD_RESULT_ to environment variables for Blocking Builds Included in 2.17 Change By: cjo9900 (26/Feb/13 4:02 PM) Status: Open Resolved Assignee: huybrechts cjo9900 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] (JENKINS-16967) Allow environment variables in phing properties
Erik Stielstra
created JENKINS-16967
Allow environment variables in phing properties
Issue Type:
New Feature
Affects Versions:
current
Assignee:
sogabe
Components:
phing
Created:
26/Feb/13 4:12 PM
Description:
I want to use the Jenkins build number as a phing property. But it is currently not possible to dynamically include the Jenkins build id into the Phing properties area. In the same way as the Jenkins SSH plugin has several environment variables available for substitution (see below), it would be super handy if this would be possible:
build.id=$BUILD_NUMBER
== For reference: SSH environment variables ===
The following variables are available to shell scripts
BUILD_NUMBER
The current build number, such as "153"
BUILD_ID
The current build id, such as "2005-08-22_23-59-59" (-MM-DD_hh-mm-ss)
JOB_NAME
Name of the project of this build, such as "foo" or "foo/bar"
BUILD_TAG
String of "jenkins-${JOB_NAME}-${BUILD_NUMBER}". Convenient to put into a resource file, a jar file, etc for easier identification.
EXECUTOR_NUMBER
The unique number that identifies the current executor (among executors of the same machine) that's carrying out this build. This is the number you see in the "build executor status", except that the number starts from 0, not 1.
NODE_NAME
Name of the slave if the build is on a slave, or "master" if run on master
NODE_LABELS
Whitespace-separated list of labels that the node is assigned.
WORKSPACE
The absolute path of the directory assigned to the build as a workspace.
JENKINS_HOME
The absolute path of the directory assigned on the master node for Jenkins to store data.
JENKINS_URL
Full URL of Jenkins, like http://server:port/jenkins/
BUILD_URL
Full URL of this build, like http://server:port/jenkins/job/foo/15/
JOB_URL
Full URL of this job, like http://server:port/jenkins/job/foo/
Environment:
Jenkins 1.5
Project:
Jenkins
Priority:
Major
Reporter:
Erik Stielstra
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-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Meng Xin Zhu commented on JENKINS-16940 Git publisher fails with Invalid id: origin/master when trying to publish changes +1 It's a regression bug, very annoying. 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-16958) I can't access M driver
kutzi resolved JENKINS-16958 as Not A Defect I cant access M driver This looks more like a "how do I do this" question than a bug. Please use the users mailing list for question! Change By: kutzi (26/Feb/13 4:14 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] (JENKINS-16965) Maven 3.0.5 upgrade
SCM/JIRA link daemon resolved JENKINS-16965 as Fixed Maven 3.0.5 upgrade Change By: SCM/JIRA link daemon (26/Feb/13 4:15 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] (JENKINS-16965) Maven 3.0.5 upgrade
SCM/JIRA link daemon commented on JENKINS-16965 Maven 3.0.5 upgrade Code changed in jenkins User: Jesse Glick Path: changelog.html maven-plugin/pom.xml http://jenkins-ci.org/commit/jenkins/2b125d7e417bdad881d1307dab9003e95a8e9cd7 Log: FIXED JENKINS-16965 Maven 3.0.5 upgrade. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16964) TAP Plug-in does not fail builds with old reports
Bruno P. Kinoshita started work on JENKINS-16964 TAP Plug-in does not fail builds with old reports Change By: Bruno P. Kinoshita (26/Feb/13 4:30 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16019) Copy Artifact Plugin isn't copying the last successful correctly
aldaris commented on JENKINS-16019 Copy Artifact Plugin isnt copying the last successful correctly I'm running into this very same problem, could be that this is limited to Maven artifact selection mechanism? 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-2879) Enhance starteam plugin
smadden commented on JENKINS-2879 Enhance starteam plugin Is this still being worked on? I'm really interested in the Multi-folder checkout and would like to put my vote on 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] (JENKINS-16282) JClouds fails to reconnect to slaves after Jenkins restart
Joel Johnson commented on JENKINS-16282 JClouds fails to reconnect to slaves after Jenkins restart We have the same problem. Is there any developer activity on this plugin anymore? 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-16965) Maven 3.0.5 upgrade
dogfood commented on JENKINS-16965 Maven 3.0.5 upgrade Integrated in jenkins_main_trunk #2302 FIXED JENKINS-16965 Maven 3.0.5 upgrade. (Revision 2b125d7e417bdad881d1307dab9003e95a8e9cd7) Result = SUCCESS Jesse Glick : 2b125d7e417bdad881d1307dab9003e95a8e9cd7 Files : maven-plugin/pom.xml changelog.html 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-16125) Variables cannot be resolved in Projects to build field when trigger is a post-build action
cjo9900 commented on JENKINS-16125 Variables cannot be resolved in Projects to build field when trigger is a post-build action Above comment is incorrect as I looked at this in more detail, and the problem is that because the plugin uses the DependancyGraph it creates the dependencies when the requested and at that point there are no build available so there the env variables cannot be replaced. DependancyGraph is only updated on modification to a job config (add, edit, copy,delete). To do this correctly the dependencies would need to be calculated during the build which is currently not supported by the 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] (JENKINS-16813) Check permission for parametized Project name instead of requiring global read
Jesse Glick resolved JENKINS-16813 as Duplicate Check permission for parametized Project name instead of requiring global read Yes it just seems like a duplicate. Change By: Jesse Glick (26/Feb/13 5:17 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16125) Variables cannot be resolved in Projects to build field when trigger is a post-build action
cjo9900 updated JENKINS-16125 Variables cannot be resolved in Projects to build field when trigger is a post-build action Core should provide a way of allowing temporary Dependencies to be added during a build, which are tied to a build not the main Dependency Graph. Change By: cjo9900 (26/Feb/13 5:18 PM) Labels: dependencies 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] (JENKINS-16957) Tracker field validations not working in CollabNet plugin
SCM/JIRA link daemon commented on JENKINS-16957 Tracker field validations not working in CollabNet plugin Code changed in jenkins User: John McNally Path: src/main/java/hudson/plugins/collabnet/filerelease/CNFileRelease.java http://jenkins-ci.org/commit/collabnet-plugin/abcc083a369dacc7edcedd5eabc49d0dd845db9e Log: JENKINS-16957 Tracker field validations not working in CollabNet plugin src/main/java/hudson/plugins/collabnet/filerelease/CNFileRelease.java (doFillReleaseItems): fix pkg parameter name You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16957) Tracker field validations not working in CollabNet plugin
John McNally commented on JENKINS-16957 Tracker field validations not working in CollabNet plugin Adding a minor File Release fix as part of this issue. Previously the entered package was not being used when filling the release combobox, so it would list releases in other packages. 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-16957) Tracker and File Release field validations not working in CollabNet plugin
John McNally updated JENKINS-16957 Tracker and File Release field validations not working in CollabNet plugin Change By: John McNally (26/Feb/13 5:23 PM) Summary: Tracker andFileRelease fieldvalidationsnotworkinginCollabNetplugin 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-16964) TAP Plug-in does not fail builds with old reports
SCM/JIRA link daemon commented on JENKINS-16964 TAP Plug-in does not fail builds with old reports Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapPublisher.java src/test/java/org/tap4j/plugin/issue16964/TestIssue16964.java src/test/java/org/tap4j/plugin/issue16964/package-info.java http://jenkins-ci.org/commit/tap-plugin/e3c3aa3fcaf91f4982a65022782ee74831021963 Log: FIXED JENKINS-16964 Fixed wrong build status You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16964) TAP Plug-in does not fail builds with old reports
SCM/JIRA link daemon resolved JENKINS-16964 as Fixed TAP Plug-in does not fail builds with old reports Change By: SCM/JIRA link daemon (26/Feb/13 5:48 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16968) Missing field (serialization error) after upgrading from 1.8 to 1.9
Bruno P. Kinoshita created JENKINS-16968 Missing field (serialization error) after upgrading from 1.8 to 1.9 Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap Created: 26/Feb/13 5:54 PM Description: After upgrading from 1.8 to 1.9 it looks like (it was reported by a user but hasn't been reproduced yet) there are serialization issues. 1) reproduce the issue 2) if reproducible, confirm with user and write serialization methods to help XStream Project: Jenkins Priority: Major Reporter: Bruno P. Kinoshita 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-16647) parse test duration from TAP file for tapTestReport pages
Bruno P. Kinoshita started work on JENKINS-16647 parse test duration from TAP file for tapTestReport pages Change By: Bruno P. Kinoshita (26/Feb/13 6:18 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16969) Mercurial plugin polling abort does not trigger a build
John A
created JENKINS-16969
Mercurial plugin polling abort does not trigger a build
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Jesse Glick
Components:
mercurial
Created:
26/Feb/13 6:18 PM
Description:
Steps to Reproduce:
1) Create a job using mercurial plugin, naming a given repository
2) run the job once (assume it succeeds)
3) delete the mercurial repo on the hg server
4) recreate the mercurial repo on the hg server
5) wait for the Mercurial Polling to occur on Jenkins
Actual Behavior:
The polling fails because the repository is unrelated to the original repo:
Mercurial Polling Log
Started on Feb 26, 2013 10:03:02 AM
workspace $ hg pull --rev default
pulling from http://cm5/hg/android/v01.1/trunk/
searching for changes
abort: repository is unrelated
workspace $ hg log --rev default --template {node}
workspace $ hg log --rev default --template {rev}
Done. Took 0.94 sec
No changes
Expected Behavior:
The workspace is automatically wiped
the repository is re-cloned
the job is triggered
Notes:
I assume this is a rare scenario. I only encountered it during some testing that I was performing which required me to create, delete and re-create the mercurial repository.
Thanks,
John
Environment:
Jenkins 1.502 Mercurial Plugin 1.43
Project:
Jenkins
Priority:
Minor
Reporter:
John A
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-15749) Predefined parameters not passing correct NODE_LABELS environment variable information.
cjo9900 commented on JENKINS-15749 Predefined parameters not passing correct NODE_LABELS environment variable information. Please retest with version 2.17 of the plugin and close if resolved. 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-12488) Need to get the name and number of ALL triggered builds (multiple triggered builds)
cjo9900 resolved JENKINS-12488 as Fixed Need to get the name and number of ALL triggered builds (multiple triggered builds) Added in 2.17 which lists all triggered projects and all builds for a particular project. See the help for block item for details. Change By: cjo9900 (26/Feb/13 6:30 PM) Status: Open Resolved Assignee: huybrechts cjo9900 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] (JENKINS-16647) parse test duration from TAP file for tapTestReport pages
SCM/JIRA link daemon resolved JENKINS-16647 as Fixed parse test duration from TAP file for tapTestReport pages Change By: SCM/JIRA link daemon (26/Feb/13 6:43 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16647) parse test duration from TAP file for tapTestReport pages
SCM/JIRA link daemon commented on JENKINS-16647 parse test duration from TAP file for tapTestReport pages Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/model/TapTestResultResult.java src/test/java/org/tap4j/plugin/issue16647/TestIssue16647.java src/test/java/org/tap4j/plugin/issue16647/package-info.java http://jenkins-ci.org/commit/tap-plugin/79e5e611cf1804d5190ee8bd50eac385ef3dd80a Log: FIXED JENKINS-16647 Added column for duration ms in test results UI You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16674) TAP parser fails parsing output with messages
Bruno P. Kinoshita started work on JENKINS-16674 TAP parser fails parsing output with messages Change By: Bruno P. Kinoshita (26/Feb/13 6:45 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-2879) Enhance starteam plugin
jan_ruzicka commented on JENKINS-2879 Enhance starteam plugin It is not being worked on at the moment. But there may be even better solution. If the Starteam Plugin behaves correctly, it can be used with Multiple SCMs Plugin1. Can you help with testing? 1 https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+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] (JENKINS-16674) TAP parser fails parsing output with messages
Bruno P. Kinoshita updated JENKINS-16674 TAP parser fails parsing output with messages Change By: Bruno P. Kinoshita (26/Feb/13 6:58 PM) Attachment: screenshot003.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] (JENKINS-16674) TAP parser fails parsing output with messages
Bruno P. Kinoshita resolved JENKINS-16674 as Wont Fix TAP parser fails parsing output with messages Hi there, First of all, sorry for taking long to work on this issue. Unfortunately the YAML provided is not a valid one. Try http://instantyaml.appspot.com/, paste the part message: ... and you'll receive the same error. Now, if you remove the "" (double double quotes), it'll work with no worries. Change By: Bruno P. Kinoshita (26/Feb/13 7:00 PM) Status: InProgress Resolved 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] (JENKINS-13727) FileNotFoundException Can't stat file with slave projects
Joshua Tharp
commented on JENKINS-13727
FileNotFoundException Cant stat file with slave projects
?xml version='1.0' encoding='UTF-8'?
project
actions/
descriptionClasses that support unit testing./description
keepDependenciesfalse/keepDependencies
properties
hudson.plugins.promoted__builds.JobPropertyImpl plugin="promoted-builds@2.8"
activeProcessNames
string1 Published to Ivy Repository/string
/activeProcessNames
/hudson.plugins.promoted__builds.JobPropertyImpl
/properties
scm class="hudson.scm.SubversionSCM" plugin="subversion@1.45"
locations
hudson.scm.SubversionSCM_-ModuleLocation
remotesvn://{mySVNHost}/testutils/remote
local./local
ignoreExternalsOptionfalse/ignoreExternalsOption
/hudson.scm.SubversionSCM_-ModuleLocation
/locations
excludedRegions/excludedRegions
includedRegions/includedRegions
excludedUsers/excludedUsers
excludedRevprop/excludedRevprop
excludedCommitMessages/excludedCommitMessages
workspaceUpdater class="hudson.scm.subversion.CheckoutUpdater"/
ignoreDirPropChangesfalse/ignoreDirPropChanges
filterChangelogfalse/filterChangelog
/scm
assignedNodegeneral/assignedNode
canRoamfalse/canRoam
disabledfalse/disabled
blockBuildWhenDownstreamBuildingfalse/blockBuildWhenDownstreamBuilding
blockBuildWhenUpstreamBuildingtrue/blockBuildWhenUpstreamBuilding
jdk(Default)/jdk
triggers class="vector"
hudson.triggers.SCMTrigger
spec@monthly/spec
ignorePostCommitHooksfalse/ignorePostCommitHooks
/hudson.triggers.SCMTrigger
/triggers
concurrentBuildfalse/concurrentBuild
builders
hudson.tasks.Ant plugin="ant@1.2"
targetsboot/targets
antNameAnt 1.8.x/antName
buildFile/home/hudson/.ant/bootstrap.xml/buildFile
propertiesbasedir=${WORKSPACE}
ivy.default.ivy.user.dir=${WORKSPACE}/ivy/properties
/hudson.tasks.Ant
hudson.tasks.Ant plugin="ant@1.2"
targetsci/targets
antNameAnt 1.8.x/antName
propertiesbasedir=${WORKSPACE}
ivy.default.ivy.user.dir=${WORKSPACE}/ivy
ivy.publish.d=/var/www/html/repository/properties
/hudson.tasks.Ant
/builders
publishers
hudson.plugins.tasks.TasksPublisher plugin="tasks@4.35"
healthy/healthy
unHealthy/unHealthy
thresholdLimitlow/thresholdLimit
pluginNameTASKS /pluginName
defaultEncoding/defaultEncoding
canRunOnFailedfalse/canRunOnFailed
useStableBuildAsReferencefalse/useStableBuildAsReference
useDeltaValuesfalse/useDeltaValues
thresholds plugin="analysis-core@1.48"
unstableTotalAll/unstableTotalAll
unstableTotalHigh/unstableTotalHigh
unstableTotalNormal/unstableTotalNormal
unstableTotalLow/unstableTotalLow
unstableNewAll/unstableNewAll
unstableNewHigh/unstableNewHigh
unstableNewNormal/unstableNewNormal
unstableNewLow/unstableNewLow
failedTotalAll/failedTotalAll
failedTotalHigh/failedTotalHigh
failedTotalNormal/failedTotalNormal
failedTotalLow/failedTotalLow
failedNewAll/failedNewAll
failedNewHigh/failedNewHigh
failedNewNormal/failedNewNormal
failedNewLow/failedNewLow
/thresholds
shouldDetectModulesfalse/shouldDetectModules
dontComputeNewfalse/dontComputeNew
doNotResolveRelativePathsfalse/doNotResolveRelativePaths
highFIXME/high
normalTODO/normal
lowXXX/low
ignoreCasefalse/ignoreCase
pattern/pattern
excludePattern/excludePattern
/hudson.plugins.tasks.TasksPublisher
hudson.plugins.warnings.WarningsPublisher plugin="warnings@4.21"
healthy/healthy
unHealthy/unHealthy
thresholdLimitlow/thresholdLimit
pluginNameWARNINGS /pluginName
defaultEncoding/defaultEncoding
canRunOnFailedfalse/canRunOnFailed
useStableBuildAsReferencefalse/useStableBuildAsReference
useDeltaValuesfalse/useDeltaValues
thresholds plugin="analysis-core@1.48"
unstableTotalAll/unstableTotalAll
unstableTotalHigh/unstableTotalHigh
unstableTotalNormal/unstableTotalNormal
unstableTotalLow/unstableTotalLow
unstableNewAll/unstableNewAll
unstableNewHigh/unstableNewHigh
unstableNewNormal/unstableNewNormal
unstableNewLow/unstableNewLow
failedTotalAll/failedTotalAll
failedTotalHigh/failedTotalHigh
failedTotalNormal/failedTotalNormal
[JIRA] (JENKINS-16889) No cleanup SSH connections when slave action occurs
Dan Doyle commented on JENKINS-16889 No cleanup SSH connections when slave action occurs +1 on this. I was very excited to see 1.7 pop up after so long because it fixed a number of things, but we had to revert to 1.6 because of the not closing connections issue. With lots of start/stop on temporary slaves this winds up happening: /var/log/libvirt/libvirtd.log 2013-02-24 03:59:54.919+: 32024: error : virNetServerDispatchNewClient:246 : Too many active clients (40), dropping connection from 127.0.0.1;0 Restarting Jenkins or libvirt solves the issue temporarily. Reverting back to 1.6 also solves the issue, so most likely a regression in 1.7. So far as we're concerned this is a show stopper bug as it renders Jenkins unusable. This is on a RHEL6 x86_64, Jenkins version 1.502 (though also tested with 1.478). Thanks for picking up this 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] (JENKINS-15466) Fatal Error No Class Definition found for Kernel32
pixman20 commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 Since this is fixed on the trunk, will/can this be marked as resolved soon so that it can be released into 1.504? 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-16970) Jenkins NUnit Plugin 0.14 incorrectly converts Unit XML results to JUnit
David Odren created JENKINS-16970 Jenkins NUnit Plugin 0.14 incorrectly converts Unit XML results to JUnit Issue Type: Bug Affects Versions: current Assignee: redsolo Attachments: ASI.SOP.AmazonBTI.Tests.xml, junitResult.xml, TestResultLevel1.jpg, TestResultLevel2.jpg, TestResultLevel3.jpg Components: junit, nunit Created: 26/Feb/13 7:56 PM Description: In the conversion of the NUnit XML results to JUnit, some tests are named incorrectly. When an NUnit output file contains a test-suite of type "TestFixture" containing a results element containing both test-suites of type "ParameterizedTest" and test-cases (not parameterized), the test-cases are reported with incorrect namespace and class names. It is as if some code were determining the namespace/class names to report by walking a certain number of tokens back in a fully qualified class name, and too many steps back are being taken for simple tests when parameterized tests are present. In TestResultLevel1.jpg all tests should appear under pacakge ASI.SOP.AmazonBTI.Tests. TestResultLevel3.jpg shows the badly parsed name AmazonUpcParseStrategyTests.ShouldRequireProductProgramFinder. Environment: Windows Server 2003, Jenkins 1.497, Jenkins NUnit plugin 0.14, NUnit 2.6.2 Project: Jenkins Priority: Minor Reporter: David Odren 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-16437) Extract MailAddressResolvers to dedicated plugins
Oliver Gondža commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins Well, lets try to delete it. https://github.com/jenkinsci/mailer-plugin/pull/6 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-16437) Extract MailAddressResolvers to dedicated plugins
Jesse Glick commented on JENKINS-16437 Extract MailAddressResolvers to dedicated plugins For the record, my proposal was to delete the known plugins implementing MailAddressResolver poorly, not to delete the extension point itself which is not inherently harmful. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl commented on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Also, you would be able to do this with a groovy template much easier, especially in the next version where I make it easier to use content tokens in the groovy template. 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-16716) FILE token does not evaluate a path that contains an environment variable
Alex Earl edited a comment on JENKINS-16716 FILE token does not evaluate a path that contains an environment variable Also, you would be able to do this with a groovy template much easier, especially in the next version where I make it easier to use content tokens in the groovy template. See https://issues.jenkins-ci.org/browse/JENKINS-16916 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-16971) TAP Plug-in not showing TAP contents if it resides in a subdirectory
Bruno P. Kinoshita created JENKINS-16971 TAP Plug-in not showing TAP contents if it resides in a subdirectory Issue Type: Bug Assignee: Bruno P. Kinoshita Components: tap Created: 26/Feb/13 8:45 PM Description: If the TAP file is created under any subdirectory, the contents are now shown to the user. Project: Jenkins Priority: Major Reporter: Bruno P. Kinoshita 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-16971) TAP Plug-in not showing TAP contents if it resides in a subdirectory
SCM/JIRA link daemon commented on JENKINS-16971 TAP Plug-in not showing TAP contents if it resides in a subdirectory Code changed in jenkins User: Bruno P. Kinoshita Path: src/main/java/org/tap4j/plugin/TapParser.java src/main/java/org/tap4j/plugin/TapResult.java src/main/java/org/tap4j/plugin/util/Util.java src/test/java/org/tap4j/plugin/util/TestUtil.java http://jenkins-ci.org/commit/tap-plugin/e8dcf5cae68f940143d6b46119829b0e1ab3582c Log: FIXED JENKINS-16971 Fixed blank content for TAP files residing in subdirectories You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16971) TAP Plug-in not showing TAP contents if it resides in a subdirectory
SCM/JIRA link daemon resolved JENKINS-16971 as Fixed TAP Plug-in not showing TAP contents if it resides in a subdirectory Change By: SCM/JIRA link daemon (26/Feb/13 8:46 PM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16971) TAP Plug-in not showing TAP contents if it resides in a subdirectory
Bruno P. Kinoshita started work on JENKINS-16971 TAP Plug-in not showing TAP contents if it resides in a subdirectory Change By: Bruno P. Kinoshita (26/Feb/13 8:45 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-16326) TAP Parser can't handle SKIP_ALL
Bruno P. Kinoshita updated JENKINS-16326 TAP Parser cant handle SKIP_ALL Change By: Bruno P. Kinoshita (26/Feb/13 8:50 PM) Attachment: screenshot004.png Attachment: screenshot005.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] (JENKINS-16326) TAP Parser can't handle SKIP_ALL
Bruno P. Kinoshita commented on JENKINS-16326 TAP Parser cant handle SKIP_ALL Hi there, First I created a simple freestyle job, with a shell build step (touch archive). Then I downloaded XML-Simple-2.20, copied the t/ folder to my job workspace and executed in another shell build step: prove t/*.t --archive archive/. Finally, added TAP to my project, with archive/*.t as pattern. The result archive/7_SaxStuff.t contains a SKIP_ALL: 1..0 # SKIP no XML::SAX It is interpreted neither as failure or as passed, it's simply treated as a skipped test Can you run your tests with prove and archive the results to an existing directory and check what happens, please? Thank you in advance, -B 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-16326) TAP Parser can't handle SKIP_ALL
Bruno P. Kinoshita updated JENKINS-16326 TAP Parser cant handle SKIP_ALL Job configuration Change By: Bruno P. Kinoshita (26/Feb/13 8:56 PM) Attachment: screenshot006.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] (JENKINS-16326) TAP Parser can't handle SKIP_ALL
Bruno P. Kinoshita stopped work on JENKINS-16326 TAP Parser cant handle SKIP_ALL Change By: Bruno P. Kinoshita (26/Feb/13 8:56 PM) Status: InProgress Open 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-16326) TAP Parser can't handle SKIP_ALL
Bruno P. Kinoshita resolved JENKINS-16326 as Not A Defect TAP Parser cant handle SKIP_ALL Marking as not a defect. If we find that it's not possible to interpret SKIP_ALL with the plug-in I'll change the bug status TY Change By: Bruno P. Kinoshita (26/Feb/13 8:57 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] (JENKINS-16325) TAP Parser can't handle the output from prove
Bruno P. Kinoshita commented on JENKINS-16325 TAP Parser cant handle the output from prove @Todd, I tried @Jochen proposal, and it works like a charm for me. Can you check if that works for you, please? Thank you in advance 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-16325) TAP Parser can't handle the output from prove
Bruno P. Kinoshita edited a comment on JENKINS-16325 TAP Parser cant handle the output from prove @Todd, I tried @Jochen proposal, and it works like a charm for me. Can you check if that works for you, please? The plug-in can parse multiple test sets in a single file only as sub tests at moment. Thank you in advance 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-13222) Allow job selection with fixed job names to contain variables without requiring job permissions for authenticated users
Jesse Glick commented on JENKINS-13222 Allow job selection with fixed job names to contain variables without requiring job permissions for authenticated users Getting rid of BuildFilter may be tricky at this point for compatibility reasons, but should still be possible to split its configuration into a different field at least. 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-2879) Enhance starteam plugin
smadden commented on JENKINS-2879 Enhance starteam plugin The Multiple SCMs plugin was a great idea, unfortunately it doesn't work quite yet with StarTeam. I setup a test system with the latest Jenkins (1.502), the Multiple SCMs and StarTeam plugins and tried to build a test project. Several problems exist 1) the Multiple SCMs plugin looses it's configuration when re-entering the Projects Config page. So you type the config in, apply the changes and save. Kick off a build and it checks out the files. Open the projects config page again and the StarTeam configuration fields are all empty. 2) all SCM's check out into the root of the workspace. E.g. I have two instances of the StarTeam plugin. The paths to the different folders in StarTeam are Suite\ToolA and \Suite\ToolB. Expected would be that the files are checked out into %WORKSPACE%\Suite\ToolA and %WORKSPACE%\Suite\ToolB or at least %WORKSPACE%\ToolA and %WORKSPACE%\ToolB. But they are all checked out into %WORKSPACE% directly. 3) Files that are not in the view of the current SCM will be deleted during checkout. Meaning if you have two StarTeam SCMs (using the example from above) and checkout Suite\ToolA, it'll delete all files that belong to Suite\ToolB because they are not in the View of Suite\ToolA. When it is done with the first SCM, it will start checking out all files from Suite\ToolB and this time around delete all files that it previously checked out for Suite\ToolA. It would be awesome if you could find a way to fix those things and make the StarTeam plugin compatible with the Multiple SCM's plugin. Maybe just an added job configuration option that says always cleanup workspace (enable/disable). And maybe specifying the root folder for the checkout, with the default of %WORKSPACE%\Starteam Folder name or so. Thanks for the quick response btw Sandra 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-16973) Apt repository doesn't contain metadata for jenkins-cli package
Jon Topper created JENKINS-16973 Apt repository doesnt contain metadata for jenkins-cli package Issue Type: Bug Assignee: magnayn Components: repository Created: 26/Feb/13 10:14 PM Description: Although the repository at http://pkg.jenkins-ci.org/debian contains packages for jenkins-cli, the metadata doesn't reference it, which makes it impossible to install. Environment: Debian Squeeze Project: Jenkins Priority: Minor Reporter: Jon Topper 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-16973) Apt repository doesn't contain metadata for jenkins-cli package
Jon Topper updated JENKINS-16973 Apt repository doesnt contain metadata for jenkins-cli package Change By: Jon Topper (26/Feb/13 10:19 PM) Component/s: cli Component/s: other Component/s: repository 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-16973) Apt repository doesn't contain metadata for jenkins-cli package
Jon Topper updated JENKINS-16973 Apt repository doesnt contain metadata for jenkins-cli package Change By: Jon Topper (26/Feb/13 10:20 PM) Assignee: magnayn 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-16974) Build Now link on MultiJob page doesn't work
David Ishee updated JENKINS-16974 Build Now link on MultiJob page doesnt work Change By: David Ishee (26/Feb/13 10:22 PM) Environment: MultiJobpluginv1.8,Javav1.6,Jenkins1.480.3 ,RedHatLinux 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-16649) Server load from l:ajax
Jesse Glick resolved JENKINS-16649 as Wont Fix Server load from l:ajax isPageVisible since 1.474 should reduce the number the requests, and caching Jelly tags should reduce the overhead of the HTML rendering. But TBD whether this is enough when there are many executors. Using push, or simplified JSON, may help. Change By: Jesse Glick (26/Feb/13 10:25 PM) Status: Open Resolved 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] (JENKINS-13995) Would like the ability to disable hover-over context menus.
Kohsuke Kawaguchi commented on JENKINS-13995 Would like the ability to disable hover-over context menus. We dicussed this in FOSDEM 2013, where we basically agreed on working toward the direction of this comment. I'll post the note to Wiki. 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-15484) New permission controlling ability to configure your own User
Kohsuke Kawaguchi commented on JENKINS-15484 New permission controlling ability to configure your own User Because of the compatibility issue, let's do it like how we did extended job configuration read permission define the permission in core, deactived by default, and a custom plugin that enables it. At the same time, we start remembering negative permissions in our authorization strategies so that new permissions like this can be added later more naturally in future 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] (JENKINS-16975) Artifacts is misspelled atrifacts in current groovy template groovy-html.template
Josh Unger created JENKINS-16975 Artifacts is misspelled atrifacts in current groovy template groovy-html.template Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 26/Feb/13 11:19 PM Description: The word artifacts is misspelled atrifacts in the current groovy template groovy-html.template. 1. Open https://github.com/jenkinsci/email-ext-plugin/blob/master/src/main/resources/hudson/plugins/emailext/templates/groovy-html.template 2. Search for "atrifacts". It should be spelled "artifacts". Project: Jenkins Priority: Major Reporter: Josh Unger 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-16975) Artifacts is misspelled atrifacts in current groovy template groovy-html.template
SCM/JIRA link daemon commented on JENKINS-16975 Artifacts is misspelled atrifacts in current groovy template groovy-html.template Code changed in jenkins User: Alex Earl Path: src/main/resources/hudson/plugins/emailext/templates/groovy-html.template http://jenkins-ci.org/commit/email-ext-plugin/d3faa0ac9ba557dd82894716e54c4cb9102c803f Log: Fix JENKINS-16975 Fixed typo You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16975) Artifacts is misspelled atrifacts in current groovy template groovy-html.template
Alex Earl resolved JENKINS-16975 as Fixed Artifacts is misspelled atrifacts in current groovy template groovy-html.template Fixed typo Change By: Alex Earl (26/Feb/13 11:22 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] (JENKINS-9598) Include the Git plugin as part of the standard distribution
Jesse Glick assigned JENKINS-9598 to Nicolas De Loof Include the Git plugin as part of the standard distribution Change By: Jesse Glick (26/Feb/13 11:33 PM) Assignee: abayer NicolasDeLoof 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-13341) Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail
Dave Hunt commented on JENKINS-13341 Upgrading to 1.458 with Jenkins on Ubuntu with OpenJDK cause Maven build to fail We had a similar issue to this that was resolved by switching to Oracle's JDK. 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-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Dave Hunt commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel We had a similar issue to this (but with Linux slaves) that was resolved by switching to Oracle's JDK from Open JDK. 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-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Dave Hunt commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We had a similar issue to this (but with Ubuntu slaves) that was resolved by switching to Oracle's JDK from Open JDK. 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-7641) Slaves hang when archiving artifacts
Dave Hunt commented on JENKINS-7641 Slaves hang when archiving artifacts We had a similar issue to this that was resolved by switching to Oracle's JDK from Open JDK. 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-13699) Jenkins plugin does not identify itself as a ClientApplication
jan_ruzicka resolved JENKINS-13699 as Fixed Jenkins plugin does not identify itself as a ClientApplication change released in starteam-0.6.8 Change By: jan_ruzicka (27/Feb/13 4:39 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] (JENKINS-13699) Jenkins plugin does not identify itself as a ClientApplication
jan_ruzicka closed JENKINS-13699 as Fixed Jenkins plugin does not identify itself as a ClientApplication checked in starteam-0.6.8 Change By: jan_ruzicka (27/Feb/13 4:41 AM) 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-14368) Create or Update Label in StarTeam displays passwords as clear text in Console Output
jan_ruzicka resolved JENKINS-14368 as Cannot Reproduce Create or Update Label in StarTeam displays passwords as clear text in Console Output Change By: jan_ruzicka (27/Feb/13 4:44 AM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-14368) Create or Update Label in StarTeam displays passwords as clear text in Console Output
jan_ruzicka closed JENKINS-14368 as Cannot Reproduce Create or Update Label in StarTeam displays passwords as clear text in Console Output Change By: jan_ruzicka (27/Feb/13 4:45 AM) 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-2879) Enhance starteam plugin
jan_ruzicka commented on JENKINS-2879 Enhance starteam plugin the multiple SCM seems to have issue with same types of repositories. (Git, TFS) JENKINS-9287. 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli created JENKINS-16976 [publish-over-ftp-1.8] upload creates unneeded folders Issue Type: Bug Assignee: bap Components: publish-over-ftp Created: 27/Feb/13 6:51 AM Description: There are actually 2 flavors to the same bug (it should be maybe 2 bugs): 1. in non-flaten mode, if the uploaded file path is - for example - dir1/dir2/dir3/file.zip then it creates those folders in the FTP server: dir2, dir3, dir1/dir2/dir3 (where it puts the file). The creation of dir2 and dir3 is wrong! 2. in flaten and non-flaten modes, if the target folder has - for example - the format dir1/dir2/dir3, the created folders in the FTP server are: dir1, dir2 and dir3 while it should create only a structure of dir1/dir2/dir3 and puts it there Environment: upload to ftp.box.com Project: Jenkins Priority: Major Reporter: Yoram Michaeli 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-15466) Fatal Error No Class Definition found for Kernel32
Nickolay Rumyantsev commented on JENKINS-15466 Fatal Error No Class Definition found for Kernel32 And what is also very important when it could be released in LTS? 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
bap commented on JENKINS-16976 [publish-over-ftp-1.8] upload creates unneeded folders Have you read https://wiki.jenkins-ci.org/display/JENKINS/Publish+Over+... - specifically the section on Transfer sets and the examples at the bottom of the page? 1. it looks like you should set: Source files: dir1/dir2/dir3/file.zip Remote directory: dir1 Remove prefix: dir1/dir2/dir3/ NB: the Remote directory is relative to the directory specified in the server configuration (in manage Jenkins) so if that is not root, but is dir1, then the remote directory in the transfer set should be empty. 2. I really cannot understand what problem you are trying to describe here. Can you provide an example? 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-16938) Information lost when build is stopped by user (our case 8705)
Jens Brejner updated JENKINS-16938 Information lost when build is stopped by user (our case 8705) pseudo linking to our tracker Change By: Jens Brejner (27/Feb/13 7:44 AM) Summary: Informationlostwhenbuildisstoppedbyuser (ourcase8705) 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-16977) Jenkins needs two initial builds for newly copied projects
Markus KARG created JENKINS-16977 Jenkins needs two initial builds for newly copied projects Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 27/Feb/13 7:48 AM Description: Created new project as copy from existing. In the initial config, I immediately change the SVN URL. Then pressing SAVE. Now Jenkins builds two times. First build (SVN CHECKOUT) is with OLD (original) URL, immediately follows a build with the NEW URL. This is weird, as even the first build does not start prior to pressing SAVE. So why not directly building ONCE with the NEW URL instead? Environment: Jenkins 1.502 / Tomcat 6 / JDK 1.6.0_18 / Debian 6 / x86 Project: Jenkins Priority: Major Reporter: Markus KARG 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-16976) [publish-over-ftp-1.8] upload creates unneeded folders
Yoram Michaeli
commented on JENKINS-16976
[publish-over-ftp-1.8] upload creates unneeded folders
About item #1 - the flaten checkbox solved it for me there for it is not critical. Still, seems like a but to be that it created all unneeded folders.
About item #2 - heres the configuration I tried and what it created for me:
Source files: multiPlatform/build/sdk/target/tabtale-sdk-osx-3.6.${BUILD_NUMBER}.zip
Remove prefix:
Remote directory: 3.6/3.6.${BUILD_NUMBER}
I've run it in flaten mode for avoid the first problem, and this is the resulted output:
if BUILD_NUMBER=11 (for example), it creates 2 folders: 3.6 and 3.6.11 (where it puts the zip file) while I expected it to create a 3.6/3.6.11 structure (meaning: a 3.6 folder with 3.6.11 folder in it).
For now I've solved it by avoiding the major-version folder (3.6 in this case) and created a 3.6.11 folder only but this is ugly since after have many versions I'll 3.6 folders in the same level as 3.7 and so on.
I can solve it - for now - by having a different 'ftp server' configuration for each major version (each one will have different 'remote directory') but I prefer to wait for a fix from you.
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.
