[JIRA] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
rggjan commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build No, I would definitively not change the behaviour! I think it should be another option, so you can set something like: Trigger: "Failure" Send to: "Build breaker" (instead of only "Recipients", "Developers", ...) I actually thought that setting it to "Culprits" would do exactly what I proposed, but somehow this works differently. What does the "Culprits" checkbox do? Shouldn't the "Culprits" be exactly the persons who broke the build in the first place? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mailer] (JENKINS-20305) Jobs are waiting concurrent builds to finish when mailer is active
BOURON Nicolas stopped work on JENKINS-20305 Jobs are waiting concurrent builds to finish when mailer is active Change By: BOURON Nicolas (18/Dec/13 8:31 AM) 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] [job-restrictions] (JENKINS-21059) Stack Trace: Form too large
Arpad Hegedues created JENKINS-21059 Stack Trace: Form too large Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: job-restrictions Created: 18/Dec/13 8:34 AM Description: Stack trace javax.servlet.ServletException: java.lang.IllegalStateException: Form too large 20564920 at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at
[JIRA] [m2release] (JENKINS-21060) Number of successful release builds to keep does not work
Anders Hammar created JENKINS-21060 Number of successful release builds to keep does not work Issue Type: Bug Assignee: teilo Components: m2release Created: 18/Dec/13 8:42 AM Description: The "Number of successful release builds to keep" configuration does seem to work. I've configured it to "1", but the no release build is kept. To reproduce: 1. Configure "Number of successful release builds to keep" to "1" 2. Do a release build 3. Do Snapshot builds until the release build is the last build 4. Do yet another Snapshot build and you'll see the release build getting disposed Environment: Jenkins LTS 1.509.4, m2release 0.13-SNAPSHOT, Oracle JDK 1.7.0_25 Project: Jenkins Priority: Major Reporter: Anders Hammar This message is automatically generated by JIRA. 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] [m2release] (JENKINS-21060) Number of successful release builds to keep does not work
Anders Hammar commented on JENKINS-21060 Number of successful release builds to keep does not work Seems as I switched the order of 1) and 2) when doing my tests, which doesn't work. The configuration of "Number of successful release builds to keep" isn't applied until a release build is done. So if I re-configure and then only do Snapshot builds the new configuration will not be used. The help text should be improved with this info. I'll fix this and issue a pull request. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21061) JENKINS_HOME ignored in JENKINS 1.544
Sascha Vet
created JENKINS-21061
JENKINS_HOME ignored in JENKINS 1.544
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
core
Created:
18/Dec/13 9:17 AM
Description:
JENKINS 1.544 ignores env var JENKINS_HOME for the WAR extraction.
D:\tempset JENKINS_HOME=D:\temp\jserver
D:\tempjava -jar jenkins-1.531.war
Running from: D:\temp\jenkins-1.531.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
18.12.2013 10:13:21 winstone.Logger logInternal
INFO: Beginning extraction from war file
= extracts to D:\temp\jserver\war
D:\tempset JENKINS_HOME=D:\temp\jserver
D:\tempjava -jar jenkins-1.544.war
Running from: D:\temp\jenkins-1.544.war
webroot: EnvVars.masterEnvVars.get("JENKINS_HOME")
18.12.2013 10:15:15 org.eclipse.jetty.util.log.JavaUtilLog info
INFO: jetty-8.y.z-SNAPSHOT
18.12.2013 10:15:17 org.eclipse.jetty.util.log.JavaUtilLog info
INFO: Extract jar:file:/D:/temp/jenkins-1.544.war!/ to C:\Documents and Settings\...\Local Settings\Temp\jetty-0.0.0.0-8080-jenkins-1.544.war-any\webapp
= extracts to C:\Documents and Settings\...\Local Settings\Temp\jetty-0.0.0.0-8080-jenkins-1.544.war-any\webapp, why?
Environment:
Windows XP
Project:
Jenkins
Labels:
windows
jenkins
Priority:
Major
Reporter:
Sascha Vet
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21061) JENKINS_HOME ignored in JENKINS 1.544
Sascha Vet
updated JENKINS-21061
JENKINS_HOME ignored in JENKINS 1.544
Change By:
Sascha Vet
(18/Dec/13 9:18 AM)
Description:
*JENKINS1.544*ignoresenvvar*JENKINS_HOME*fortheWARextraction.{quote}D:\tempsetJENKINS_HOME=D:\temp\jserverD:\tempjava-jarjenkins-1.531.warRunningfrom:D:\temp\jenkins-1.531.warwebroot:EnvVars.masterEnvVars.get(JENKINS_HOME)18.12.201310:13:21winstone.LoggerlogInternalINFO:Beginningextractionfromwarfile{quote}=extractsto
*
D:\temp\jserver\war
*
{quote}D:\tempsetJENKINS_HOME=D:\temp\jserverD:\tempjava-jarjenkins-1.544.warRunningfrom:D:\temp\jenkins-1.544.warwebroot:EnvVars.masterEnvVars.get(JENKINS_HOME)18.12.201310:15:15org.eclipse.jetty.util.log.JavaUtilLoginfoINFO:jetty-8.y.z-SNAPSHOT18.12.201310:15:17org.eclipse.jetty.util.log.JavaUtilLoginfoINFO:Extractjar:file:/D:/temp/jenkins-1.544.war!/toC:\DocumentsandSettings\...\LocalSettings\Temp\jetty-0.0.0.0-8080-jenkins-1.544.war--any-\webapp{quote}=extractsto
{color:red}*
C:\DocumentsandSettings\...\LocalSettings\Temp\jetty-0.0.0.0-8080-jenkins-1.544.war--any-\webapp
*{color}
,why?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Andreas Loew commented on JENKINS-21057 Cannot checkout git repository with submodules: FATAL: No remotes found! It seems that the problem is not the "git plugin" but the "git *client* plugin" Version 1.4.6 seems to work whereas 1.5.1 does not. This message is automatically generated by JIRA. 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] [m2release] (JENKINS-15298) Default versioning mode is not getting picked while invoking the maven release build
Anders Hammar commented on JENKINS-15298 Default versioning mode is not getting picked while invoking the maven release build What about the 'autoVersionSubmodules' param configuration of maven-release-plugin from the pom, shouldn't it be honored instead? I guess it's a question about which path to take here. Either the m2release plugin is just a shell around m-release-p and uses it's configuration as much as possible or it replaces the configuration of m-release-p. Pros and cons with both paths. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
Andrey Regentov commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Same on Jenkins 1.544, Active Directory 1.33 on SLES 11. Now I'm using "--sessionTimeout=sane_number_of_minutes" jenkins cmdline switch as a workaround, but still it is a hack. This message is automatically generated by JIRA. 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] [downstream-buildview] (JENKINS-21062) Downstream build view shows jobs as NOT_BUILT
Per Arnold Blaasmo created JENKINS-21062 Downstream build view shows jobs as NOT_BUILT Issue Type: Bug Assignee: shinodkm Attachments: screenshot_040.png, screenshot_041.png Components: downstream-buildview Created: 18/Dec/13 9:58 AM Description: Jobs in the downstram build view show jobs as NOT_BUILT. In some of the subjobs there is jobs sowing as success, but not in upstrem job. screenshot_040.png shows top job. screenshot_040.png shows on level down and has some downstream jobs as success. Environment: Jenkins 1.544 Downstream build view 1.8 Parameterized trigger 2.22 Project: Jenkins Priority: Major Reporter: Per Arnold Blaasmo This message is automatically generated by JIRA. 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] [m2release] (JENKINS-21060) Improve help text of Number of successful release builds to keep
Anders Hammar updated JENKINS-21060 Improve help text of Number of successful release builds to keep Change By: Anders Hammar (18/Dec/13 10:03 AM) Priority: Major Minor This message is automatically generated by JIRA. 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] [m2release] (JENKINS-21060) Improve help text of Number of successful release builds to keep
Anders Hammar updated JENKINS-21060 Improve help text of Number of successful release builds to keep Change By: Anders Hammar (18/Dec/13 10:03 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. 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] [m2release] (JENKINS-21063) Indicate in icon (or tooltip) if a release build failed
Anders Hammar created JENKINS-21063 Indicate in icon (or tooltip) if a release build failed Issue Type: Improvement Affects Versions: current Assignee: teilo Components: m2release Created: 18/Dec/13 10:03 AM Description: I find my self often stare at the release icons in the build history and not realize at first glance that some of them are failed release builds. This can of course be seen in the red ball of the build, but I'm thinking that it would be good if the release build icon would show this as well. At least the tooltip should clearly state that the release build failed. Environment: n/a Project: Jenkins Priority: Minor Reporter: Anders Hammar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
Björn Pedersen created JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 18/Dec/13 10:21 AM Description: java.lang.IllegalStateException: Form too large 476344320 at org.eclipse.jetty.server.Request.extractParameters(Request.java:352) at org.eclipse.jetty.server.Request.getParameterNames(Request.java:813) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:67) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at
[JIRA] [job-restrictions] (JENKINS-21059) Stack Trace: Form too large
Oleg Nenashev commented on JENKINS-21059 Stack Trace: Form too large Why have you decided that the issue is related to job-restriction plugin? Anyway, please provide info about your Jenkins installation (version, platform, etc.) and the form you're trying to submit This message is automatically generated by JIRA. 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] [testlink] (JENKINS-20624) TAP result seeker's include test notes adds poor values
Javier Delgado commented on JENKINS-20624 TAP result seekers include test notes adds poor values From my understanding, saving as notes the whole Testset might be a litte bit overkill (Im thinking in really big streams, with stacktraces and embedded files). Moreover, theres already a functionality to attach the whole tap stream and to attach the tap stream´s embedded files. Wouldnt it be nice to extract just a part of the stream (such as the proposed Notes element)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21059) Stack Trace: Form too large
Arpad Hegedues updated JENKINS-21059 Stack Trace: Form too large sorry, my mistaken Change By: Arpad Hegedues (18/Dec/13 10:42 AM) Component/s: core Component/s: job-restrictions This message is automatically generated by JIRA. 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] [config-rotator] (JENKINS-21065) Hijacked files should be overwritten by files from versioned files in vob (our case 10498)
Mads Nielsen created JENKINS-21065 Hijacked files should be overwritten by files from versioned files in vob (our case 10498) Issue Type: Bug Assignee: Praqma Support Components: config-rotator Created: 18/Dec/13 10:44 AM Description: The update view functionality does not use the possibility to use the -overwrite flag when udating views. This should be possible. Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21059) Stack Trace: Form too large
Oleg Nenashev closed JENKINS-21059 as Duplicate Stack Trace: Form too large Change By: Oleg Nenashev (18/Dec/13 10:52 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] [core] (JENKINS-21059) Stack Trace: Form too large
Oleg Nenashev resolved JENKINS-21059 as Duplicate Stack Trace: Form too large OK, I'll close the issue as a "duplicate" Change By: Oleg Nenashev (18/Dec/13 10:51 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-20699) NPE when MultiJobBuilder reaches a disabled job
André Söderlind commented on JENKINS-20699 NPE when MultiJobBuilder reaches a disabled job Bugfix committed to the branch: https://github.com/andresoderlind/tikal-multijob-plugin/tree/ISSUE-J-20619 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16152) Jobs failing to load due to NPE
evernat commented on JENKINS-16152 Jobs failing to load due to NPE Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16146) Jenkins Webpage can't opened
evernat commented on JENKINS-16146 Jenkins Webpage cant opened @Youcai Your issue was incomplete: to diagnose a blocked server, most important is to get a thread dump, either with Jenkins or with jstack. Is your issue reproduced with recent versions of Jenkins (and of the clearcase plugin if used) ? @santi I do not see a thread named "R1" in your thread dump. But I see the famous thread in "org.kohsuke.stapler.compression.CompressionFilter.reportException", which is JENKINS-14362 and already 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
takeshi ito commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Hi. Your code seems good. I suspect probrem is in your network, or server. Tell me your network path to jenkins server from local. I write C# code to access jenkins api too. and it works well. /// mono JenkinsAccess.exe http://localhost:8080/job/asd/api/xml complete 200freeStyleProjectdescription/descriptiondisplayNameasd/displayNamenameasd/nameurlhttp://localhost:8080/job/asd//url /// See attach file JenkinsAccess.cs. It seems as same as your code. So that, I suppose probrem is in your network. This message is automatically generated by JIRA. 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
takeshi ito updated JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Change By: takeshi ito (18/Dec/13 11:47 AM) Attachment: JenkinsAccess.cs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Alex Earl commented on JENKINS-21057 Cannot checkout git repository with submodules: FATAL: No remotes found! I see an issue with missing remotes during the publisher stage as well. The .git/config is missing the remotes section. I don't have submodules at all in my config. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21041) Impossible to keeps sending mails to people who broke the build
Alex Earl commented on JENKINS-21041 Impossible to keeps sending mails to people who broke the build Culprits are those that committed something since it started failing if I remember correctly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [integrity-plugin] (JENKINS-20977) Integrity Plugin does not generate changelog when used with multiple-scms plugin
Tyrel Alastair Hunter commented on JENKINS-20977 Integrity Plugin does not generate changelog when used with multiple-scms plugin It also appears that when in use with multiple SCM there is no way to perform multiple checkins, and multiple checkpoints This message is automatically generated by JIRA. 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.
Jenkins Build periodically not working
Hi, I have scheduled job using build periodically(45 17 * * *). But its not scheduling at 5:45 pm.. Please help -- View this message in context: http://jenkins-ci.361315.n4.nabble.com/Jenkins-Build-periodically-not-working-tp4684694.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- 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] [config-rotator] (JENKINS-21066) Config Rotator jobs builds needlessly (our case 10378)
Mads Nielsen created JENKINS-21066 Config Rotator jobs builds needlessly (our case 10378) Issue Type: Bug Assignee: Praqma Support Components: config-rotator Created: 18/Dec/13 12:12 PM Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
Björn Pedersen created JENKINS-21067 New server config not reachable if using a prefix in URL Issue Type: Bug Assignee: rsandell Components: gerrit-trigger Created: 18/Dec/13 12:23 PM Description: On jenkins instances the URL for the server configuration does not consider this prefix. Project: Jenkins Priority: Major Reporter: Björn Pedersen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
cswarren commented on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I believe I'm seeing the same problem (or a related problem) on Windows 2003 systems using Jenkins's credential-storing, once I updated the git-client plugin to 1.5.0. (A .gitcredentials file is mentioned in the error message, but There's no such file on the machine that I know of.) Cloning the remote Git repository Cloning repository https://github.com/merchantwarehouse/merchantware.git Fetching upstream changes from https://github.com/merchantwarehouse/merchantware.git using .gitcredentials to set credentials ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git config --local --remove-section credential.helper" returned status code 128: stdout: stderr: fatal: No such section! at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1098) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1075) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:930) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:993) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:68) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:217) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:349) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:828) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: null This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21064) Form too large if there are many patchsets in the selection list (manual trigger)
Björn Pedersen commented on JENKINS-21064 Form too large if there are many patchsets in the selection list (manual trigger) One possible solution would be to only list the latest patchset of each change by default. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21016) Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?)
cswarren edited a comment on JENKINS-21016 Problems with git-credentials-store for http credentials (introduced with fix for issue #20318 ?) I believe I'm seeing the same problem (or a related problem) on Windows 2003 systems using Jenkins's credential-storing, once I updated the git-client plugin to 1.5.0. (A .gitcredentials file is mentioned in the error message, but there's no such file on the machine that I know of.) Cloning the remote Git repository Cloning repository https://github.com/merchantwarehouse/merchantware.git Fetching upstream changes from https://github.com/merchantwarehouse/merchantware.git using .gitcredentials to set credentials ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "git config --local --remove-section credential.helper" returned status code 128: stdout: stderr: fatal: No such section! at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1098) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1075) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:930) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:993) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$200(CliGitAPIImpl.java:68) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:217) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:349) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:828) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:861) at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:561) at hudson.model.Run.execute(Run.java:1678) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) ERROR: null This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
Björn Pedersen commented on JENKINS-21067 New server config not reachable if using a prefix in URL It is maybe a problem with with the absoulte path generatrion in GerritServer: getUrlName. This message is automatically generated by JIRA. 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] [config-rotator] (JENKINS-21069) Improve the performance of config rotator (our case 10377)
Mads Nielsen created JENKINS-21069 Improve the performance of config rotator (our case 10377) Issue Type: New Feature Assignee: Praqma Support Components: config-rotator Created: 18/Dec/13 12:44 PM Description: We need to selectively load the basline we need Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [testlink] (JENKINS-20624) TAP result seeker's include test notes adds poor values
Bruno P. Kinoshita commented on JENKINS-20624 TAP result seekers include test notes adds poor values You're right. I believe you've told me this before either via e-mail or GitHub. Sorry. Let's add an option to look for the notes YAMLish attribute. Thanks! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21057) Cannot checkout git repository with submodules: FATAL: No remotes found!
Luis Arias commented on JENKINS-21057 Cannot checkout git repository with submodules: FATAL: No remotes found! I had to downgrade the git plugin to 1.5 and the git client plugin to 1.4.6 to get this to work again (With the recursively update submodules option checked in my job). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
rsandell commented on JENKINS-21067 New server config not reachable if using a prefix in URL what prefix? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-21030) Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location
Mark Waite updated JENKINS-21030 Git CLI cannot clone with ssh protocol on Windows if Git is in non-default location Change By: Mark Waite (18/Dec/13 1:46 PM) Summary: GitCLIcannotclone withsshprotocol onWindowsifGitisinnon-defaultlocation This message is automatically generated by JIRA. 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] [promoted-builds] (JENKINS-19863) Can we get more colors for promotion stars?
Marvi Benedet commented on JENKINS-19863 Can we get more colors for promotion stars? Would be good to have both "filled" stars, like the ones already present, but also others where the inner star is left white (or transparent). So for example the promotion "approved for deployment production" would have the filled gold star, all other promotion which are used for executing a production deploy would have the "empty" gold star. This message is automatically generated by JIRA. 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] [scriptler] (JENKINS-21071) Using Scriptlers in Dynamic Build Parameters AND Build-Steps executs the wrong Scriptler in the Build-Step
Angelo Schneider created JENKINS-21071 Using Scriptlers in Dynamic Build Parameters AND Build-Steps executs the wrong Scriptler in the Build-Step Issue Type: Bug Assignee: Dominik Bartholdi Components: scriptler Created: 18/Dec/13 1:58 PM Description: I use a named Scriptler Script first in a "Dynamic Parameter (Scriptler)", then I use another named Scriptler Script in a Build-Step. When the Build-Step is executed it does not executed the configured Scriptler Script but executes the one I have chosen first in the "Dynamic Parameter". My workaround is not to use named Scriptler scripts in the Parameter section but to write the relevant Groovy inline. Environment: Jenkins 1.515; Jenkins Dynamic Parameter Plug-in 0.2.0; Scriptler Plugin 2.2 Project: Jenkins Labels: configuration Priority: Major Reporter: Angelo Schneider This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
SCM/JIRA link daemon commented on JENKINS-21067 New server config not reachable if using a prefix in URL Code changed in jenkins User: Robert Sandell Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServerTest.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/c3d922b942233eb3f423a5b8f52cf234e2fba0de Log: Fix JENKINS-21067 by jumping hoops This message is automatically generated by JIRA. 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] [m2release] (JENKINS-21063) Indicate in icon (or tooltip) if a release build failed
Anders Hammar assigned JENKINS-21063 to Anders Hammar Indicate in icon (or tooltip) if a release build failed Change By: Anders Hammar (18/Dec/13 3:02 PM) Assignee: teilo AndersHammar This message is automatically generated by JIRA. 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] [m2release] (JENKINS-21063) Indicate in icon (or tooltip) if a release build failed
Anders Hammar started work on JENKINS-21063 Indicate in icon (or tooltip) if a release build failed Change By: Anders Hammar (18/Dec/13 3:02 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] [m2release] (JENKINS-4560) POMs left in a modified state after failed release
Anders Hammar commented on JENKINS-4560 POMs left in a modified state after failed release This is a fairly nasty issue! Imagine this scenario: A Maven build job "mvn clan deploy" or similar, which will deploy a new snapshot version on every build. Not too uncommon I think. If a release build fails, the next build triggered on a code change will actually deploy to the repo based on the failed release version number (as the modified pom is left in the workspace)! And it could some time until people notice this and understand what has happened. This message is automatically generated by JIRA. 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] [plot] (JENKINS-18644) Loading Overlay
Esteban Socas commented on JENKINS-18644 Loading Overlay i have Jenkins ver. 1.521 i solve the issue uninstalling Environment Injector 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] [gui] (JENKINS-12787) LOADING overlay does not go away on the Configure System page
Esteban Socas commented on JENKINS-12787 LOADING overlay does not go away on the Configure System page i have Jenkins ver. 1.521 i solve the issue uninstalling Environment Injector 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams updated JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Change By: Bill Williams (18/Dec/13 3:45 PM) Attachment: JenkinsApiCallsPowerShell.doc This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobgenerator] (JENKINS-21072) White screen after submitting job generation
Alex Artyukhovskii
created JENKINS-21072
White screen after submitting job generation
Issue Type:
Bug
Affects Versions:
current
Assignee:
Unassigned
Components:
jobgenerator
Created:
18/Dec/13 3:46 PM
Description:
A white screen of death appears when running the generator job, displaying URL like ${JENKINS_URL}/job/${JOB_NAME}/build?delay=0sec.
Nevertheless, generation job executes successfully, generated jobs appear / disappear as expected after build, and after refreshing the page Jenkins displays generator job page again.
All other builds, both parametrized and not-parametrized are triggered as expected, without blank screen.
Both system log and jenkins.log files display no errors or exceptions:
Dec 18, 2013 10:11:59 AM org.jenkinsci.plugins.jobgenerator.GeneratorRun$GeneratorImpl doRun
INFO: Updated configuration of job gen_madre_mio
Dec 18, 2013 10:11:59 AM hudson.model.Run execute
INFO: mcs-tools-simple-generator #9 main build action completed: SUCCESS
Environment:
Server: RHEL 6.0 + Jenkins 1.544 + latest version of Jobgenerator plugin
Client: Win 7 + Firefox / MSIE
Project:
Jenkins
Labels:
jobgenerator
whitescreen
Priority:
Major
Reporter:
Alex Artyukhovskii
This message is automatically generated by JIRA.
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] [mailer] (JENKINS-21045) maven 2/3 projects cannot store emailaddress
Jesse Glick resolved JENKINS-21045 as Fixed maven 2/3 projects cannot store emailaddress Was fixed in 2.1. (JIRA was apparently down so the issue link daemon did not note this.) Change By: Jesse Glick (18/Dec/13 3:45 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] [active-directory] (JENKINS-21073) Fix forceLdaps system property
Brandon Turner created JENKINS-21073 Fix forceLdaps system property Issue Type: Bug Assignee: Unassigned Components: active-directory Created: 18/Dec/13 3:50 PM Description: The Active Directory documentation 1 says you can use the `hudson.plugins.active_directory.ActiveDirectorySecurityRealm.forceLdaps` system property to force connecting via LDAPS. This is broken. The following pull request updates the code to use this system property: https://github.com/jenkinsci/active-directory-plugin/pull/8 It also changes the default LDAPS port from 686 to 636. 1 https://wiki.jenkins-ci.org/display/JENKINS/Active+Directory+plugin#ActiveDirectoryplugin-SecuringaccesstoActiveDirectoryservers Project: Jenkins Priority: Minor Reporter: Brandon Turner This message is automatically generated by JIRA. 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Hi, the network issue is a good suggestion, I should have tested on the server locally sooner. I have now moved the logic to the server and I'm still getting the same 404 error but just on "job" calls. Please see the newly attached JenkinsApiCallsPowerShell.doc. It shows that I am calling localhost and the script is installed on the server. Same issue, so it is not a network issue (I don't think). It is very frustrating because I can get lots of data (both remotely and locally) but not job or build data. Again, thanks for your help. This message is automatically generated by JIRA. 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] [m2release] (JENKINS-4560) POMs left in a modified state after failed release
Anders Hammar commented on JENKINS-4560 POMs left in a modified state after failed release Figured out that if Subversion is used as scm, "Use 'svn update' as much as possible, with 'svn revert' before update" (or "Always check out a fresh copy") can be selected as check-out strategy as a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven] (JENKINS-20725) maven build creates symlinkd files that Windows OS does not understand
Joe Knudsen updated JENKINS-20725 maven build creates symlinkd files that Windows OS does not understand Change By: Joe Knudsen (18/Dec/13 3:58 PM) Affects Version/s: current This message is automatically generated by JIRA. 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] [envinject] (JENKINS-17241) GEM_PATH env variable wrong when using rvm
James Tomson updated JENKINS-17241 GEM_PATH env variable wrong when using rvm Change By: James Tomson (18/Dec/13 4:04 PM) Summary: GEM_PATHenvvariablewrongwhenusing rvm Labels: envinjectenvironment-variablesgem_pathjenkinslinux,plugin rvm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [gerrit-trigger] (JENKINS-21067) New server config not reachable if using a prefix in URL
SCM/JIRA link daemon commented on JENKINS-21067 New server config not reachable if using a prefix in URL Code changed in jenkins User: Robert Sandell Path: gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritManagement.java gerrithudsontrigger/src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer.java gerrithudsontrigger/src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServerTest.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/b2028be83114eb94f732b3d160e89af5da368632 Log: Fix JENKINS-21067 by jumping hoops Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/2b3f1af83e7d...b2028be83114 This message is automatically generated by JIRA. 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
takeshi ito commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. And, sorry, I'm sleepy, I response you tomorrow. Goot night. This message is automatically generated by JIRA. 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
takeshi ito commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. Right. It's not network problem. what is response when you access http://localhost:8080/job/SubCode with your script? If job "SubCode" visible, it returns status code 200 and html. or not, return 404. It's show me "Job" is invisible, or "API" is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudbees-folder] (JENKINS-21075) When renaming a job in a folder, higher level views aren't notified
Daniel Beck created JENKINS-21075 When renaming a job in a folder, higher level views arent notified Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder, core Created: 18/Dec/13 4:22 PM Description: 1. Create a folder 'F' 2. Create a job 'F/a' 3. Create a list view 'V' in top level Jenkins, check 'recursive', and add 'F/a' to the it. 4. (F/a shows up in V) 5. Rename F/a to F/b Expected result: F/b shows up in V Actual result: Empty list view Environment: 1.532.1, Folders 4.x Project: Jenkins Labels: lts-candidate Priority: Major Reporter: Daniel Beck This message is automatically generated by JIRA. 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] [envinject] (JENKINS-17241) GEM_PATH env variable wrong when using rvm
James Tomson updated JENKINS-17241 GEM_PATH env variable wrong when using rvm Change By: James Tomson (18/Dec/13 4:23 PM) Component/s: rvm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git-client] (JENKINS-21074) Git Client plugin fails to install on fresh Jenkins installation
Peter Miklosko created JENKINS-21074 Git Client plugin fails to install on fresh Jenkins installation Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 18/Dec/13 4:20 PM Description: When installing GitHub Plugin that requires Git Client Plugin, plugin installation will fail with following error java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1304) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1103) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.IOException: Failed to initialize git-client plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:451) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1300) ... 5 more Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at hudson.PluginManager.dynamicLoad(PluginManager.java:449) ... 6 more Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:109) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ... 1 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:483) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) ... 7 more Caused by: java.lang.ArrayIndexOutOfBoundsException: -1 at com.thoughtworks.xstream.core.util.OrderRetainingMap.entrySet(OrderRetainingMap.java:77) at java.util.HashMap.putMapEntries(HashMap.java:511) at java.util.HashMap.putAll(HashMap.java:784) at com.thoughtworks.xstream.core.util.OrderRetainingMap.init(OrderRetainingMap.java:36) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.buildMap(FieldDictionary.java:135) at com.thoughtworks.xstream.converters.reflection.FieldDictionary.fieldsFor(FieldDictionary.java:76) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:127) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:143) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:102) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:898) at com.thoughtworks.xstream.XStream.marshal(XStream.java:887) at com.thoughtworks.xstream.XStream.toXML(XStream.java:860) at hudson.XmlFile.write(XmlFile.java:182) at hudson.model.Descriptor.save(Descriptor.java:758) at hudson.plugins.git.GitTool.onLoaded(GitTool.java:106)
[JIRA] [s3] (JENKINS-14395) S3 Plugin credentials stored insecurely
Tim Olsen commented on JENKINS-14395 S3 Plugin credentials stored insecurely It looks like this issue may have been resolved in 0.4 (according to the Version History). Should this issue be 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] [envinject] (JENKINS-17241) GEM_PATH env variable wrong when using envinject + rvm plugins
James Tomson updated JENKINS-17241 GEM_PATH env variable wrong when using envinject + rvm plugins Change By: James Tomson (18/Dec/13 4:28 PM) Summary: GEM_PATHenvvariablewrongwhenusing envinject+ rvm plugins This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Marcel Beister commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work I can no longer reproduce the problem with Jenkins 1.544 and Plugin 1.8.1. This message is automatically generated by JIRA. 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] [maven] (JENKINS-17362) Maven build cannot find JDK when project uses default
Jirong Hu commented on JENKINS-17362 Maven build cannot find JDK when project uses default I am having the same issue. Run "mvn compile" from DOS command line is all right, but getting this error from Jenkins. Very simple Maven "my-app" sample project. Even I copied the tool.jar to the path below, still same error. I am running the build on a Slave on XP, in the System Information of Slave, the JAVA_HOME is showing different. ERROR Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5.1:compile (default-compile) on project my-app: Fatal error compiling: tools.jar not found: C:\Program Files\Java\jre7\..\lib\tools.jar - Help 1 ERROR This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Marcel Beister commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 I can no longer reproduce the problem with Jenkins 1.544 and Plugin 1.8.1. This message is automatically generated by JIRA. 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] [backup] (JENKINS-21076) Workspace zip from windows host wrong
Jesse Wiles created JENKINS-21076 Workspace zip from windows host wrong Issue Type: Bug Assignee: Daniel Petisme Components: backup Created: 18/Dec/13 4:39 PM Description: Workspace zip from windows host results in flat filenames with windows path separator. So the files within the zip appear as: file\dir\alpha.txt file\dir\beta.txt file\dir\gamma.txt where backslash ( is a part of the archived filename. Environment: windows server 2012 Project: Jenkins Priority: Major Reporter: Jesse Wiles This message is automatically generated by JIRA. 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] [dashboard-view] (JENKINS-21048) Image portlet not collapsible
Kyle Paice edited a comment on JENKINS-21048 Image portlet not collapsible I was able to fix the problem by modifying the portlet.jelly file for the ImagePortlet, attached. The section is now collapsible but I don't know how to check my changes into the 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] [envinject] (JENKINS-17241) GEM_PATH env variable wrong when using envinject + rvm plugins
James Tomson commented on JENKINS-17241 GEM_PATH env variable wrong when using envinject + rvm plugins I can reproduce using Jenkins ver. 1.541 Environment Injector Plugin 1.89 Rvm Plugin 0.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [call-remote-job] (JENKINS-21005) API calls return 404 error when asking for JOB information. API returns data for non-Job information.
Bill Williams commented on JENKINS-21005 API calls return 404 error when asking for JOB information. API returns data for non-Job information. PS C:\Windows\system32 D:\Download\JenkinsApi.ps1 DEBUG: http://localhost:8080/job DEBUG: Exception calling "DownloadString" with "1" argument(s): "The remote server returned an error: (404) Not Found." PS C:\Windows\system32 D:\Download\JenkinsApi.ps1 DEBUG: http://localhost:8080/job/SubCode DEBUG: Exception calling "DownloadString" with "1" argument(s): "The remote server returned an error: (404) Not Found." PS C:\Windows\system32 D:\Download\JenkinsApi.ps1 DEBUG: http://localhost:8080/job/SubCode/api DEBUG: Exception calling "DownloadString" with "1" argument(s): "The remote server returned an error: (404) Not Found." PS C:\Windows\system32 D:\Download\JenkinsApi.ps1 DEBUG: http://localhost:8080/job/SubCode/api/xml DEBUG: Exception calling "DownloadString" with "1" argument(s): "The remote server returned an error: (404) Not Found." PS C:\Windows\system32 D:\Download\JenkinsApi.ps1 DEBUG: http://localhost:8080/job/SubCode/api/json DEBUG: Exception calling "DownloadString" with "1" argument(s): "The remote server returned an error: (404) Not Found." PS C:\Windows\system32 D:\Download\JenkinsApi.ps1 DEBUG: http://localhost:8080/job/TritonLegacy DEBUG: Exception calling "DownloadString" with "1" argument(s): "The remote server returned an error: (404) Not Found." PS C:\Windows\system32 D:\Download\JenkinsApi.ps1 DEBUG: http://localhost:8080/ RETURNS LOTS OF HTML !DOCTYPE htmlhtmlhead titleDashboard Jenkins... Thank you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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] [dashboard-view] (JENKINS-21048) Image portlet not collapsible
Kyle Paice updated JENKINS-21048 Image portlet not collapsible I was able to fix the problem by modifying the portlet.jelly file for the ImagePortlet. The section is now collapsible but I don't know how to check my changes into the repository. Change By: Kyle Paice (18/Dec/13 4:47 PM) Attachment: portlet.jelly This message is automatically generated by JIRA. 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] [weblogic-deployer] (JENKINS-20970) Unexpected close of a file stream
Yos Stef commented on JENKINS-20970 Unexpected close of a file stream I have the same problem. All settings seem to be correct. WebLogic 11 (10.3.6) , Jenkins v1.543 , Weblogic Deployment Plugin 2.9 . JDK 1.7 ... I will provide with any info needed. Here is the plugin configuration : ?xml version="1.0" encoding="UTF-8"? config xmlns="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://org.jenkinsci.plugins/WeblogicDeploymentPlugin plugin-configuration.xsd" weblogic-targets weblogic-target nameWebLogic11/name hosthttp://dev.company.com/host port6001/port loginuser/login passworduser/password authModeBY_LOGIN/authMode !-- -- /weblogic-target /weblogic-targets /config This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21075) When renaming a job in a folder, higher level views aren't notified
Jesse Glick updated JENKINS-21075 When renaming a job in a folder, higher level views arent notified Change By: Jesse Glick (18/Dec/13 5:25 PM) Labels: folders lts-candidate Component/s: cloudbees-folder This message is automatically generated by JIRA. 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] [cvs] (JENKINS-21077) CVS plugin uses different timestamps
P-C Johansson created JENKINS-21077 CVS plugin uses different timestamps Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 18/Dec/13 5:33 PM Description: When using the CVS plugin to checkout I see it doesn't use the same timestamps for checkout as for rlog: - 17:48:40 Started by user testadmin 17:48:40 EnvInject - Loading node environment variables. 17:48:40 Building on master in workspace /var/lib/jenkins/jobs/test_checkout/workspace 17:48:42 cvs checkout -f -P -r test_branch -D 18 Dec 2013 17:48:42 +0100 -d module1 module1 17:48:52 cvs checkout -f -P -r test_branch -D 18 Dec 2013 17:48:42 +0100 -d module2 module2 17:48:58 cvs checkout -f -P -r test_branch -D 18 Dec 2013 17:48:42 +0100 -d module3 module3 17:49:01 cvs checkout -f -P -r test_branch -D 18 Dec 2013 17:48:42 +0100 -d module4 module4 17:49:15 cvs rlog -S -d18 Dec 2013 17:46:21 +010018 Dec 2013 17:48:40 +0100 module1 17:49:17 cvs rlog -S -d18 Dec 2013 17:46:21 +010018 Dec 2013 17:48:40 +0100 module2 17:49:19 cvs rlog -S -d18 Dec 2013 17:46:21 +010018 Dec 2013 17:48:40 +0100 module3 17:49:20 cvs rlog -S -d18 Dec 2013 17:46:21 +010018 Dec 2013 17:48:40 +0100 module4 - The job is started 17:48:40. The first CVS checkout is done 17:48:42 and all subsequent checkouts uses the 17:48:42 timestamp. Shouldn't they rather use 17:48:40 when the job started? The rlog is done but now against when the job started and not against the actual checkout. I've seen a time difference between 1 and 5 seconds, but there is always a difference. Environment: Ubuntu 12.04 Project: Jenkins Labels: cvs Priority: Minor Reporter: P-C Johansson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21078) Loading projects too slow because of File.isDirectory calls
Jesse Glick created JENKINS-21078 Loading projects too slow because of File.isDirectory calls Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Dec/13 5:47 PM Description: With lazy loading, Jenkins no longer reads $JENKINS_HOME/jobs//builds/*/config.xml during startup. But it still checks File.isDirectory on the containing directories, which makes loadIdOnDisk slow. It should suffice for RunMap.createDirectoryFilter to assume that any file in builds which matches the date pattern for a build directory is in fact a directory. (If it is not, retrieve will return null later, so no harm done.) loadIdOnDisk could also avoid calling dir.list twice (once for build directories, once for shortcuts): call it once and filter appropriately. Project: Jenkins Labels: performance lazy-loading Priority: Major Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21078) Loading projects too slow because of File.isDirectory calls
Jesse Glick started work on JENKINS-21078 Loading projects too slow because of File.isDirectory calls Change By: Jesse Glick (18/Dec/13 6:16 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] [core] (JENKINS-21078) Loading projects too slow because of File.isDirectory calls
Jesse Glick assigned JENKINS-21078 to Jesse Glick Loading projects too slow because of File.isDirectory calls Change By: Jesse Glick (18/Dec/13 6:16 PM) Assignee: JesseGlick This message is automatically generated by JIRA. 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] [s3] (JENKINS-14395) S3 Plugin credentials stored insecurely
mcrooney resolved JENKINS-14395 as Fixed S3 Plugin credentials stored insecurely Thanks Tim, I think so, as it specifically references this issue. Change By: mcrooney (18/Dec/13 6:24 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-20767) Git plugin 2.0: Git polling causes builds even if no changes
Mark Waite commented on JENKINS-20767 Git plugin 2.0: Git polling causes builds even if no changes Corey O'Connor when you say "confirmed" do you mean that you used command line or that you used jgit? This message is automatically generated by JIRA. 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] [matrix] (JENKINS-1040) Staggering builds (on virtual machine slaves)
Heather McKinnon edited a comment on JENKINS-1040 Staggering builds (on virtual machine slaves) I too need this functionality - but not for the same reason. I would like to stagger my axis (matrix) builds by a set amount of time in order to reduce any bottleneck of them running certain stages concurrently on another server (ie automated sanity or testing or transfers) I have seperate build nodes and the load is not the issue - there are concurrency issues with transferring output etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix] (JENKINS-1040) Staggering builds (on virtual machine slaves)
Heather McKinnon edited a comment on JENKINS-1040 Staggering builds (on virtual machine slaves) I too need this functionality - but not for the same reason. I would like to stagger my axis (matrix) builds by a set amount of time in order to reduce any bottleneck of them running certain stages concurrently on another server (ie automated sanity or testing or transfers) I have seperate build nodes and the load is not the issue - there are concurrency issues with transferring output etc. Sorry - different issue - I thought this was a request to allow quiet periods / staggered timed matrix builds. This message is automatically generated by JIRA. 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] [matrix] (JENKINS-21079) Request to have the ability to stagger matrix builds by a certain amount of time
Heather McKinnon created JENKINS-21079 Request to have the ability to stagger matrix builds by a certain amount of time Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: matrix Created: 18/Dec/13 7:07 PM Description: I have some matrix jobs configured, but when I run the build - they all launch at precisely the same time. This is great however, there is a stage where it is transferring large amounts of data for automated sanity, which results in a bottleneck and increases the build time significanlty. It would be good to set a stagger of x minutes to allow one builds' transfer to complete before the next one starts .. or at least reduce the concurrency. I have tried the Advanced 'Quiet Period' however, it doesn't seem to work for matrix builds - I have tried many tests - unsuccessfully. Thanks Environment: Jenkins 1.543 Ubuntu 12.04 Project: Jenkins Labels: matrix stagger Priority: Major Reporter: Heather McKinnon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Arvind Ramalingam commented on JENKINS-15156 Builds disappear from build history after completion Is this Issue Fixed..As We are having the same issue on Jenkins ver. 1.509.4 LTS..Is there a fix for the issue?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Jesse Glick updated JENKINS-15156 Builds disappear from build history after completion @arvindramalingam you mean you are experiencing a different bug with a similar symptom. Without knowing how to reproduce from scratch we cannot help. See comments above. Change By: Jesse Glick (18/Dec/13 7:17 PM) Assignee: JesseGlick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21075) When renaming a job in a folder, higher level views aren't notified
Jesse Glick resolved JENKINS-21075 as Duplicate When renaming a job in a folder, higher level views arent notified Change By: Jesse Glick (18/Dec/13 7:19 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] [core] (JENKINS-18680) View.onJobRenamed should be deprecated
Jesse Glick updated JENKINS-18680 View.onJobRenamed should be deprecated Change By: Jesse Glick (18/Dec/13 7:19 PM) Labels: api folders lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18680) View.onJobRenamed should be deprecated
Jesse Glick updated JENKINS-18680 View.onJobRenamed should be deprecated Change By: Jesse Glick (18/Dec/13 7:19 PM) Labels: api folderslts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Arvind Ramalingam commented on JENKINS-15156 Builds disappear from build history after completion Hi Jesse, Thanks for the quick response.We have renamed the jobs and pointed it to a different release and the Build history keeps disappearing everyday.If there is a fix for the issue can you please send it to me so that I will build the war file with the change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobcopy-builder] (JENKINS-21080) Build results page shows wrong link for Copied To and Copied From
Christian Galsterer created JENKINS-21080 Build results page shows wrong link for Copied To and Copied From Issue Type: Bug Assignee: Christian Galsterer Components: jobcopy-builder Created: 18/Dec/13 7:26 PM Description: The link for Copied To and Copied From is missing the context in the URL. Local fix already available, will create patch/pull request in the next day(s). Project: Jenkins Priority: Major Reporter: Christian Galsterer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21081) Multi-config projects option to import configuration from existing projects of other types
Mani Sarkar created JENKINS-21081 Multi-config projects option to import configuration from existing projects of other types Issue Type: New Feature Assignee: Unassigned Components: core Created: 18/Dec/13 7:28 PM Description: This feature concerns the New Job option when you log into your Cloudbees account. Would it be possible to have an option within the multi-config projects option to import configuration from existing projects of other types, the options mostly overlap between the two and can be tedious to copy them over. Also the options that might not be directly map-able, can be enlisted or some help can be provided to alternatively make them map-able. Project: Jenkins Priority: Major Reporter: Mani Sarkar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15156) Builds disappear from build history after completion
Arvind Ramalingam commented on JENKINS-15156 Builds disappear from build history after completion I see the builds on the server but not on the UI...The trend on the UI also does not show the history This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-21081) Multi-config projects option to import configuration from existing projects of other types
Mani Sarkar updated JENKINS-21081 Multi-config projects option to import configuration from existing projects of other types Change By: Mani Sarkar (18/Dec/13 7:30 PM) Description: ThisfeatureconcernstheNewJoboptionwhenyoulogintoyourCloudbeesaccount -wouldhelpDEV@CloudJenkinshosting .Woulditbepossibletohaveanoptionwithinthemulti-configprojectsoptiontoimportconfigurationfromexistingprojectsofothertypes,theoptionsmostlyoverlapbetweenthetwoandcanbetedioustocopythemover.Alsotheoptionsthatmightnotbedirectlymap-able,canbeenlistedorsomehelpcanbeprovidedtoalternativelymakethemmap-able. Workaround:youcanusejenkinsCLItocreate/updatejobsfromXML,canuseitasaworkaroundtoconvertprojecttypes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21082) Build with parameters doesn't work within a multi-job view
hagzag created JENKINS-21082 Build with parameters doesnt work within a multi-job view Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 18/Dec/13 7:35 PM Description: When multijob build has parameters you cannot execute it from a multi-job view. If you use a "regular" jenkins view the "play" button works. It seems like there is some method missing in the implementation. Due Date: 23/Dec/13 12:00 AM Project: Jenkins Priority: Major Reporter: hagzag This message is automatically generated by JIRA. 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] [publish-over-ftp] (JENKINS-21083) Connection timed out
j serup created JENKINS-21083 Connection timed out Issue Type: Bug Assignee: bap Components: publish-over-ftp Created: 18/Dec/13 7:42 PM Description: I have installed Publish Over FTP Plugin 1.9 on Jenkins 1.532 and configured it against a FileZilla Ftp server running on windows 7. I have verified that I can connect to the ftp server from a shell on the slave that runs my jobs. But when I try to copy a single test.txt file using the Publish Over Ftp plugin (I have configured the server and tested in the master configuration) in a freeStyleProject I get: FTP: Connecting from host debian7-slave FTP: Connecting with configuration fileshare ... FTP: Disconnecting configuration fileshare ... ERROR: Exception when publishing, exception message Connection timed out Build step 'Send build artifacts over FTP' changed build result to UNSTABLE Finished: UNSTABLE I have tried using this plugin instead: http://wiki.hudson-ci.org/display/HUDSON/FTP-Publisher+Plugin and it works fine with the same configuration. Environment: Linux Project: Jenkins Priority: Major Reporter: j serup This message is automatically generated by JIRA. 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] [weblogic-deployer] (JENKINS-20970) Unexpected close of a file stream
Raphael CHAUMIER started work on JENKINS-20970 Unexpected close of a file stream Change By: Raphael CHAUMIER (18/Dec/13 7:54 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] [core] (JENKINS-21078) Loading projects too slow because of File.isDirectory calls
SCM/JIRA link daemon resolved JENKINS-21078 as Fixed Loading projects too slow because of File.isDirectory calls Change By: SCM/JIRA link daemon (18/Dec/13 7:58 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] [core] (JENKINS-21078) Loading projects too slow because of File.isDirectory calls
SCM/JIRA link daemon commented on JENKINS-21078 Loading projects too slow because of File.isDirectory calls Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/RunMap.java core/src/main/java/jenkins/model/lazy/AbstractLazyLoadRunMap.java http://jenkins-ci.org/commit/jenkins/a6e01f77c6d3d72f7ac9e99ce061ce04dbf4b515 Log: FIXED JENKINS-21078 Optimizing loadIdOnDisk. Compare: https://github.com/jenkinsci/jenkins/compare/d81c2406a27c...a6e01f77c6d3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-9258) Remember me on this computer, still getting asked to log in after a few hours
m_broida commented on JENKINS-9258 Remember me on this computer, still getting asked to log in after a few hours Linux is not an option. And we do -NOT- use ActiveDirectory. We authenticate with a Ruby script. AD is not involved at all. Yet Jenkins logs me out after some period of time. Usually a couple of hours, whether inactive or not. Note: =I= am the only user of our buildserver that is experiencing the periodic logouts. (Or no-one else is complaining.) At least one other user NEVER gets logged out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
