[JIRA] [plugin] (JENKINS-22496) Error when Applying what execution to run with SCTMExecutor 1.5.1 plugin.
Sebastian Kornexl commented on JENKINS-22496 Error when Applying what execution to run with SCTMExecutor 1.5.1 plugin. This is a known problem in this version. As workaround please click on the "Advanced..." button when specifying Execution ID and Project ID and select one of the radiobuttons (eg. "Dont care about a build number"). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-21333) Variable injected with EnvInject not supported
christophe dehaudt
commented on JENKINS-21333
Variable injected with EnvInject not supported
I'm facing the same problem
trying to do such things like :
${FILE:${ENV:INSTALL_DIR}/Success.html}
= the result is : I see that the env variable is resolved but not the file
did a bit of digging, i believe the problem is here
RichTextPublisher.java (line 165)
Matcher matcher = FILE_VAR_PATTERN.matcher(text);
int start = 0;
while (matcher.find(start)) {
String fileName = matcher.group(2);- HERE
FilePath filePath = new FilePath(build.getWorkspace(), fileName);
if (filePath.exists()) {
String value = filePath.readToString();
if (matcher.group(1).length() != 4) { // Group is file_sl
value = value.replace("\n", "").replace("\r", "");
}
vars.put(String.format("%s:%s", matcher.group(1), fileName), value);
}
start = matcher.end();
}
can we do something like
String fileName = replaceVars(matcher.group(2), vars);
that might do the job, no?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22496) Error when Applying what execution to run with SCTMExecutor 1.5.1 plugin.
Micky Rathod commented on JENKINS-22496 Error when Applying what execution to run with SCTMExecutor 1.5.1 plugin. Thank you Sebastian! I figured it out by playing around with the options! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-22497) Variables inside FILE content are not replaced
christophe dehaudt created JENKINS-22497 Variables inside FILE content are not replaced Issue Type: New Feature Assignee: Dmitry Korotkov Components: rich-text-publisher Created: 04/Apr/14 7:04 AM Description: "I really like the idea of this plugin, that you can customize the message of the build, but I miss you can any other lightweight markup language like AsciiDoc. You can use: https://github.com/asciidoctor/asciidoctor-java-integration for Java integration." Project: Jenkins Priority: Major Reporter: christophe dehaudt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-22497) Variables inside FILE content are not replaced
christophe dehaudt
updated JENKINS-22497
Variables inside FILE content are not replaced
Change By:
christophe dehaudt
(04/Apr/14 7:11 AM)
Description:
I
really
would
like
touse${FILE:mypath/xxx.html}tocreate
the
ideaof
samerichcontentforallmyjobs.Using
this
plugin,thatyou
willallowmetohaveauniqueplacewheni
can
customize
change
the
messageof
contentandwillbeapplytoall
the
build
jobTheproblemisthatiwantalsotohavevariableinterpolationLikeJENKINS-21333
,
butImissyou
ibelievetheproblem
can
anyotherlightweightmarkuplanguagelikeAsciiDoc
besolvedatthesameplaceRichTextPublisher
.
Youcanuse:https://github
java(line165)Matchermatcher=FILE_VAR_PATTERN
.
com/asciidoctor/asciidoctor
matcher(text);intstart=0;while(matcher.find(start)){StringfileName=matcher.group(2);
-
java-integration
HERE
for
Javaintegration
21=replaceVars(matcher
.
group(2),vars);FilePathfilePath=newFilePath(build.getWorkspace(),fileName);if(filePath.exists()){Stringvalue=filePath.readToString();if(matcher.group(1).length()!=4){//Groupisfile_slvalue=value.replace(
\n,).replace(\r,);}vars.put(String.format(%s:%s,matcher.group(1),fileName),value);}start=matcher.end();}canwedosomethinglike
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-22497) Variables inside FILE content are not replaced
christophe dehaudt
updated JENKINS-22497
Variables inside FILE content are not replaced
Change By:
christophe dehaudt
(04/Apr/14 7:14 AM)
Description:
Iwouldliketouse${FILE:mypath/xxx.html}tocreatethesamerichcontentforallmyjobs.UsingthiswillallowmetohaveauniqueplacewhenicanchangethecontentandwillbeapplytoallthejobTheproblemisthatiwantalsotohavevariableinterpolationLikeJENKINS-21333,ibelievetheproblemcanbesolvedatthesameplaceRichTextPublisher.java(line165)Matchermatcher=FILE_VAR_PATTERN.matcher(text);intstart=0;while(matcher.find(start)){StringfileName=matcher.group(2);-HEREfor21
fileName
=replaceVars(matcher.group(2),vars);FilePathfilePath=newFilePath(build.getWorkspace(),fileName);if(filePath.exists()){Stringvalue=filePath.readToString();if(matcher.group(1).length()!=4){//Groupisfile_slvalue=value.replace(\n,).replace(\r,);}vars.put(String.format(%s:%s,matcher.group(1),fileName),value);
--HEREinsteadofvalue=replaceVars(value,vars)
}start=matcher.end();}
canwedosomethinglike
Isitpossibletohavethose2bugsfixed?
Thanksinadvance
Xtof
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-22497) Variables inside FILE content are not replaced
christophe dehaudt updated JENKINS-22497 Variables inside FILE content are not replaced Change By: christophe dehaudt (04/Apr/14 7:16 AM) Issue Type: NewFeature Bug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [rich-text-publisher] (JENKINS-21333) Variable injected with EnvInject not supported
christophe dehaudt assigned JENKINS-21333 to Dmitry Korotkov Variable injected with EnvInject not supported Change By: christophe dehaudt (04/Apr/14 7:18 AM) Assignee: DmitryKorotkov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time
Marcus Philip commented on JENKINS-22482 Display pipeline total build time We (the authors of the plugin, i.e. Diabol), believe that manual triggers DO make sense in a pipeline. A high degree of automation is great and necessary in a pipeline, but some decisions will be taken by humans in many pipelines. What should always be automated is the repetitive tasks. This is one of the reasons that we believe that the total CYCLE time is an important measure. Also, I think your presentation is focusing too much on 'anecdotal' measurements. It's the statistical values that should matter. I attach a suggestion for displaying total cycle time and total build time. For the aggregate row, it's the same but with statistical values: average, minimum, median, 90-percentile and maximum. How about that? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time
Marcus Philip updated JENKINS-22482 Display pipeline total build time Pipeline with individual cycle and build times and stats. Change By: Marcus Philip (04/Apr/14 7:57 AM) Attachment: SeachangeDPP.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22498) After crash, Multijob plugin cannot create new and show old views anymore
Stenver Jerkku created JENKINS-22498 After crash, Multijob plugin cannot create new and show old views anymore Issue Type: Bug Assignee: Unassigned Components: plugin Created: 04/Apr/14 8:44 AM Description: We had a powercut on our jenkins machine, which killed the virtual machines. After everything was booted, we are unable to show old and create new multijob views. The multijob plugin otherwise works Ok Here is the stacktrace when we try to look at the view javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8080-jenkins.war--any-/webapp/WEB-INF/lib/jenkins-core-1.550.jar!/hudson/model/View/index.jelly:42:43: st:include Cannot invoke method isEmpty() on null object at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java: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.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 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
[JIRA] [git] (JENKINS-22499) Allow Git Publisher to create a tag for a secific SHA1
Sebastian Schuberth created JENKINS-22499 Allow Git Publisher to create a tag for a secific SHA1 Issue Type: Improvement Assignee: Nicolas De Loof Components: git Created: 04/Apr/14 8:55 AM Description: It would be nice if the Git Publisher would not just create the tag for HEAD, but for any optionally specified SHA1. Project: Jenkins Priority: Minor Reporter: Sebastian Schuberth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-13833) Git Publisher should allow ForceTag instead of CreateTag
Sebastian Schuberth commented on JENKINS-13833 Git Publisher should allow ForceTag instead of CreateTag I think this is exactly what the "Update new tag" option is for (though I agree that its name is misleading and probably should have said "Force create new tag" instead). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrents] (JENKINS-19986) Throttle Concurrent Builds plugin doesn't appear to work
Igor Turchenko commented on JENKINS-19986 Throttle Concurrent Builds plugin doesnt appear to work Looks broken on Jenkins 1.551 + 1.8.2 or Jenkins 1.557 + 1.8.2 Jobs still stacking in queue instead concurrent running on different nodes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22484) Clashing URL for test results
raboof commented on JENKINS-22484 Clashing URL for test results Currently using the workaround at https://github.com/raboof/maven-plugin/commit/c8894e8fd7ab4beb3e39b9217dea6fb7f0f9ac35 but that can't be the solution... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22484) Clashing URL for test results
raboof edited a comment on JENKINS-22484 Clashing URL for test results Currently using the workaround at https://github.com/raboof/maven-plugin/commit/c8894e8fd7ab4beb3e39b9217dea6fb7f0f9ac35 combined with https://github.com/raboof/xunit-plugin/commit/5eab9cc115b320a2e830b9707b1be7ea6adcc543 but that can't be the solution... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19244) jenkins random hang during startup - Solaris and Linux
Ben Ketteridge commented on JENKINS-19244 jenkins random hang during startup - Solaris and Linux We have the same problem on 1.554. We don't use throttle-concurrents. Moving the jobs to a backup directory and back after start-up works. Adding -Dhudson.model.Hudson.parallelLoad=false did not. Our configuration has 80 maven builds, none of which are matrix jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-22492) java.io.IOException: Pipe broken
lacostej commented on JENKINS-22492 java.io.IOException: Pipe broken Do you have a way to reproduce this often ? Was this happening with v0.5 ? Are you using the -logFile option ? (supported properly from 0.6) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Tomas Bezdek edited a comment on JENKINS-19470 Build Graph not displaying DELETED This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sctmexecutor] (JENKINS-12255) SCTM plugin reports null pointer when creating a new job description
nyoung02 commented on JENKINS-12255 SCTM plugin reports null pointer when creating a new job description Hi Micky, This bug was marked as a duplicate of another issue (JENKINS-6619). In that bug Thomas provided a workaround: https://issues.jenkins-ci.org/browse/JENKINS-6619?focusedCommentId=157219page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-157219 In my case I resolved by using the Jenkins build number. (You must click "Advanced" to see the options). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17459) Little red/yellow/green icons should get you to Console everywhere
evernat commented on JENKINS-17459 Little red/yellow/green icons should get you to Console everywhere reproduced with Jenkins 1.555 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22342) Gitweb URL can be mangled (if it doesn't contain a path?)
Mark Waite commented on JENKINS-22342 Gitweb URL can be mangled (if it doesnt contain a path?) I hope to look at it within the next 7 days. I'd prefer that Nicolas be the one to evaluate it, since he made the most recent code changes in that area, but he's been busy in other areas. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks
Heather Fraser-Dube commented on JENKINS-21933 PermGen leaks Jim you also need to enable garbage collection on classes loaded. See the comment from Abhishek above. If you are using more than 1 toolkit you may also need to increase the permgen area size. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobgenerator] (JENKINS-22500) Not able to add step: Post build action - Build other Projects with Job name that uses generator parameter for generating Job name.
Tanvi Shrivastava created JENKINS-22500 Not able to add step: Post build action - Build other Projects with Job name that uses generator parameter for generating Job name. Issue Type: Bug Assignee: Unassigned Components: jobgenerator Created: 04/Apr/14 11:37 AM Project: Jenkins Labels: plugin Priority: Major Reporter: Tanvi Shrivastava This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild] (JENKINS-18989) Cannot get Plugin to honor Java Jar added via Additional groovy classpath
Viktor Berke commented on JENKINS-18989 Cannot get Plugin to honor Java Jar added via Additional groovy classpath Frank, how did that work? For me that says: groovy.lang.MissingPropertyException: No such property: manager for class: Script1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-15442) email-ext plugin does not save configuration on job
Alex Earl commented on JENKINS-15442 email-ext plugin does not save configuration on job This looks like a completely different problem. Please post your hudson.plugins.emailext.ExtendedEmailPublisher.xml file. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep] (JENKINS-22501) advanced options (e.g., fail the build) are not saved or executed
Bob Marinier created JENKINS-22501 advanced options (e.g., fail the build) are not saved or executed Issue Type: Bug Affects Versions: current Assignee: Dominik Bartholdi Components: conditional-buildstep Created: 04/Apr/14 12:22 PM Description: I'm trying to configure a build step to fail the build if a file doesn't exist. I did this by using the File Exists condition, specifying the file of interest, and then selecting advanced and "fail the build" (if condition not met). I also added an "execute shell script" action to echo that the file was found. I saved and ran the build, but the step didn't work as expected the echo did not happen (the output indicates that this is because the condition was not met), but the build did not fail. I went back into the configuration and saw that the "fail the build" step I added was gone. I tried adding it several times, but it doesn't seem to stick. Environment: Linux 3.2.0-58-generic, jenkins 1.556 Project: Jenkins Priority: Major Reporter: Bob Marinier This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-15442) email-ext plugin does not save configuration on job
Baskaran D commented on JENKINS-15442 email-ext plugin does not save configuration on job @Alex Earl - Currently, I upgraded my email-ext plugin to v2.34, where i am not seeing this problem. I got this when I followed the workaround provided by Jhon Cruz and restarted my jenkins. However.. Current content in hudson.plugins.emailext.ExtendedEmailPublisher.xml file ?xml version='1.0' encoding='UTF-8'? hudson.plugins.emailext.ExtendedEmailPublisherDescriptor plugin="email-ext@2.34" hudsonUrlhttp://ci.net//hudsonUrl adminAddressjenk...@test.com/adminAddress smtpHostgmail-smtp-in.l.google.com/smtpHost useSslfalse/useSsl defaultContentTypetext/plain/defaultContentType defaultSubject$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS!/defaultSubject defaultBody$PROJECT_NAME - Build # $BUILD_NUMBER - $BUILD_STATUS:#xd; #xd; Check console output at $BUILD_URL to view the results./defaultBody defaultPresendScript/defaultPresendScript maxAttachmentSize-1/maxAttachmentSize recipientList/recipientList defaultReplyTo/defaultReplyTo excludedCommitters/excludedCommitters overrideGlobalSettingstrue/overrideGlobalSettings precedenceBulkfalse/precedenceBulk debugModefalse/debugMode enableSecurityfalse/enableSecurity enableWatchingfalse/enableWatching /hudson.plugins.emailext.ExtendedEmailPublisherDescriptor I cannot downgrade again now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-15442) email-ext plugin does not save configuration on job
Alex Earl commented on JENKINS-15442 email-ext plugin does not save configuration on job Version 2.34 is still pretty old. Everything looks fine in the file. If you are no longer seeing the issue, then I won't worry. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [urlscm] (JENKINS-21633) HTTP Proxy setting ignored?
Marco Tizzoni commented on JENKINS-21633 HTTP Proxy setting ignored? I confirm we are experiencing the same issue. Proxy settings are being ignored when Jenkins run under openJDK-1.7 and Oracle JDK 1.8. It works with openJDK-1.6. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-15442) email-ext plugin does not save configuration on job
Baskaran D commented on JENKINS-15442 email-ext plugin does not save configuration on job No more updates available on jenkins pluginManager page. This might be because my Jenkins is running on ver. 1.532. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [email-ext] (JENKINS-15442) email-ext plugin does not save configuration on job
Alex Earl commented on JENKINS-15442 email-ext plugin does not save configuration on job Could be, if you were running LTS (1.532.x), it would be up to 2.37.2.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-flow] (JENKINS-22502) Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue
Vadim Lipatov created JENKINS-22502 Matrix parent occupies an executor and blocks child jobs from execution if appropriate slave becomes online after matrix job was already in the queue Issue Type: Bug Assignee: Nicolas De Loof Components: build-flow, core Created: 04/Apr/14 12:56 PM Description: There is a matrix job with 1 axis and 3 child jobs. A label of slaves for execution is assigned via parameter using LabelNode plugin. Initially there is no available executors in the system. To reproduce: run the matrix job with the label parameter "exp_label1". Job is set to the queue; run the swarm slave and assign it the same label that provided in the parameter for the job: "exp_label1". the swarm slave appears in the list of executors and matrix parent occupies it. After that 3 child jobs are set to the queue forever. I tried to use MatrixTieParent plugin but it looks it does not work correctly with NodeLabel plugin. Environment: Windows 7, 64bit, jdk 1.7.0_21 Project: Jenkins Priority: Major Reporter: Vadim Lipatov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22503) There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears
Vitaliy Baskoff created JENKINS-22503 There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears Issue Type: Bug Assignee: rsandell Attachments: gerrit_retrigger_mult_patchsets.png Components: gerrit-trigger Created: 04/Apr/14 1:03 PM Description: Hi, Gerrit-trigger can't fire multiple builds, if they are ticked in "Query String: portaum/porta-um" search result list, however if "Query String: Change Nr." build is re-triggered normally. STR: 0. Go to https://jenkins_url/gerrit_manual_trigger/ 1. Set "Query string" to gerrit project name(e.g. portaum/porta-um) 2. Select several patch-sets from separate review 3. Press "Trigger selected" button Expected results: Jenkins starts appropriate builds for selected patch-sets Current results: "Please select something to build" error appears over the "Trigger selected" button, no builds re-triggered Please fix if possible. Environment: gentoo, tomcat 7, jenkins 1.532.2, firefox 28.0 Project: Jenkins Priority: Minor Reporter: Vitaliy Baskoff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22503) There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears
Vitaliy Baskoff updated JENKINS-22503 There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears Change By: Vitaliy Baskoff (04/Apr/14 1:07 PM) Environment: gentoo,tomcat7,jenkins1.532.2,firefox28.0 ,gerrit-trigger2.11.0 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time
Zihao Yu commented on JENKINS-22482 Display pipeline total build time Great suggestion. I will work more on that. Meanwhile I'm going to close the PR and lower the priority of this JIRA. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline] (JENKINS-22482) Display pipeline total build time
Zihao Yu updated JENKINS-22482 Display pipeline total build time Change By: Zihao Yu (04/Apr/14 1:11 PM) Priority: Minor Trivial This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19468) Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature.
Mark Waite edited a comment on JENKINS-19468 Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature. The pull request for the git-plugin has been included in git-plugin 2.2.0, release 4 Apr 2014. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19468) Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature.
Mark Waite commented on JENKINS-19468 Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature. The pull request(https://github.com/jenkinsci/git-plugin/pull/214) for the git-plugin has been included in git-plugin 2.2.0, release 4 Apr 2014. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19468) Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature.
Mark Waite edited a comment on JENKINS-19468 Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature. The pull request for the git-plugin has been included in git-plugin 2.2.0, release 4 Apr 2014. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-16242) Github pull request builder - branch to merged before build
Matt Lauber commented on JENKINS-16242 Github pull request builder - branch to merged before build A couple points on this one. First, there does exist the Github Pull Request Builder plugin, which basically accomplishes just this functionality, but it could benefit from some of the capabilities of this plugin. Second, it might be nice to be able to specify which github API events you want a job to respond to. So one job responds to only commits on a certain branch, another responds to pull requests. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19468) Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature.
Mark Waite resolved JENKINS-19468 as Fixed Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature. Change By: Mark Waite (04/Apr/14 1:28 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/d/optout.
[JIRA] [git] (JENKINS-19468) Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature.
Mark Waite closed JENKINS-19468 as Fixed Git plugin does not support Git 1.8.2 integrate with the tip of the remote branch submodule branch tracking feature. Change By: Mark Waite (04/Apr/14 1:29 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21124) Use proxy to access git repository
Mark Waite resolved JENKINS-21124 as Cannot Reproduce Use proxy to access git repository Closing this bug report as cannot reproduce because the original author has not responded and the https support in the git-client-plugin uses the Apache httpclient and is confirmed to work through http proxy servers. Change By: Mark Waite (04/Apr/14 1:33 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobgenerator] (JENKINS-22500) Not able to add step: Post build action - Build other Projects with Job name that uses generator parameter for generating Job name.
Sylvain Benner assigned JENKINS-22500 to Sylvain Benner Not able to add step: Post build action - Build other Projects with Job name that uses generator parameter for generating Job name. Change By: Sylvain Benner (04/Apr/14 1:33 PM) Assignee: SylvainBenner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-21124) Use proxy to access git repository
Mark Waite closed JENKINS-21124 as Cannot Reproduce Use proxy to access git repository Change By: Mark Waite (04/Apr/14 1:33 PM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobgenerator] (JENKINS-22500) Not able to add step: Post build action - Build other Projects with Job name that uses generator parameter for generating Job name.
Sylvain Benner commented on JENKINS-22500 Not able to add step: Post build action - Build other Projects with Job name that uses generator parameter for generating Job name. Hi Tanvi, Thank you for the report. Sorry, I don't understand your use case with just the title. Can you be more specific ? Instead of Build Other Projects, I would use the publisher "Trigger new parameterized job" where you can pass the job generators, see the example on the wiki page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-22504) Mark Unstable build in github as value does not display correctly in UI, gets overwritten with subsequent saves
Trevor Baker created JENKINS-22504 Mark Unstable build in github as value does not display correctly in UI, gets overwritten with subsequent saves Issue Type: Bug Assignee: Honza Brázdil Components: ghprb Created: 04/Apr/14 1:40 PM Description: The "configure system" page containing the master config for the GHPRB has the setting "Mark Unstable build in github as" with a default of "Failure." Attempting to save with any other appears to persist to the xml file, but subsequent saves to the config replace it with the default "Failure" value and your intention is lost. Expect the specified value to persist and the UI to select the correct value based on user's intention. Environment: ghprb 1.11.2 jenkins 1.557 git client 1.7 github plugin 1.8 git plugin 2.1 Project: Jenkins Priority: Major Reporter: Trevor Baker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [batch-task] (JENKINS-21329) Can't do git commands in Jenkins
Mark Waite commented on JENKINS-21329 Cant do git commands in Jenkins The command "git clone git@host:/opt/git/..." needs to use ssh authentication to read from the remote repository. That read from the remote repository is probably failing because the service account you're using on Windows is not configured to perform ssh authentication to the remote git repository. JENKINS-20356 reports that Jenkins cannot clone ssh based git repositories when running as a service. You might explore the ideas in that bug report to see if they help you further. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs] (JENKINS-22102) NodeJS plugin does not remember the saved NodeJS Installation
Frédéric Camblor updated JENKINS-22102 NodeJS plugin does not remember the saved NodeJS Installation Change By: Frédéric Camblor (04/Apr/14 1:42 PM) Priority: Minor Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22503) There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears
rin_ne commented on JENKINS-22503 There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears Seems your selected patchsets are both abandoned. Could you select opened one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodejs] (JENKINS-22103) NodeJS buildstep succeeds, although installation failed
Frédéric Camblor commented on JENKINS-22103 NodeJS buildstep succeeds, although installation failed I agree with your assumption. But I'm wondering if I can do anything about this : I'm relying on a common "XXX Installations" layer which seems to behave like this by default. I'll try to see if I can change this default behaviour This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-22492) java.io.IOException: Pipe broken
Juan Fornos commented on JENKINS-22492 java.io.IOException: Pipe broken Hi lacostej, Thanks for your feedback. With that job, it fails every time I try to build for the webplayer. Didn't try with v0.5 (Jenkins doesn't let me downgrade) but I remember having this issue less frequently. I'm not using -logFile option. The full stack trace is: LZMA 4.43 Copyright (c) 1999-2006 Igor Pavlov 2006-06-04 Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(Unknown Source) at java.io.PipedInputStream.read(Unknown Source) at java.io.InputStream.read(Unknown Source) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) FATAL: Unity3d command line execution failed with status 1 Build step 'Invoke Unity3d Editor' marked build as failure FATAL: Remote call on MacServer failed java.io.IOException: Remote call on MacServer failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.util.ProcessTree$UnixReflection at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:552) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:572) at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:496) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:899) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:890) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Let me know if I can be of any help. Thanks, Juan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-22492) java.io.IOException: Pipe broken
Juan Fornos edited a comment on JENKINS-22492 java.io.IOException: Pipe broken Hi lacostej, Thanks for your feedback. With that job, it fails every time I try to build for the webplayer. Didn't try with v0.5 (Jenkins doesn't let me downgrade) but I remember having this issue less frequently. I'm not using the -logFile option. The full stack trace is: LZMA 4.43 Copyright (c) 1999-2006 Igor Pavlov 2006-06-04 Failure on remote java.io.IOException: Pipe broken at java.io.PipedInputStream.read(Unknown Source) at java.io.PipedInputStream.read(Unknown Source) at java.io.InputStream.read(Unknown Source) at org.jenkinsci.plugins.unity3d.io.StreamCopyThread.run(StreamCopyThread.java:64) FATAL: Unity3d command line execution failed with status 1 Build step 'Invoke Unity3d Editor' marked build as failure FATAL: Remote call on MacServer failed java.io.IOException: Remote call on MacServer failed at hudson.remoting.Channel.call(Channel.java:731) at hudson.Launcher$RemoteLauncher.kill(Launcher.java:887) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.lang.NoClassDefFoundError: Could not initialize class hudson.util.ProcessTree$UnixReflection at hudson.util.ProcessTree$UnixProcess.kill(ProcessTree.java:552) at hudson.util.ProcessTree$UnixProcess.killRecursively(ProcessTree.java:572) at hudson.util.ProcessTree$Unix.killAll(ProcessTree.java:496) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:899) at hudson.Launcher$RemoteLauncher$KillTask.call(Launcher.java:890) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:744) Let me know if I can be of any help. Thanks, Juan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-22505) jenkins unable to discover OpenID (unsupported SNI by Jenkins)
Florian Klink created JENKINS-22505 jenkins unable to discover OpenID (unsupported SNI by Jenkins) Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: openid Created: 04/Apr/14 2:00 PM Description: Jenkins is configured to authenticate using OpenID. The OpenID Server is behind a SSL reverse proxy thats using SNI. However, Jenkins is not using SNI when connecting to the URL (verfified by setting apache's SSLStrictSNIVHostCheck to on) This leads to the following "Oops!": javax.servlet.ServletException: org.openid4java.discovery.DiscoveryException: 0x706: Failed to discover OpenID: https://openid.somedomain.com/ at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) 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.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:135) 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:79) 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
[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build
Mark Waite commented on JENKINS-22144 Cant specify remote repositorys branch to build I've attempted an experiment or two and was not successful trying to checkout a branch from a second repository with the syntax "refs/remotes/somename/somebranch". More investigation is needed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-token-root] (JENKINS-22458) java.lang.NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission
jenkins jenkins updated JENKINS-22458 java.lang.NoSuchMethodError: hudson.model.BuildAuthorizationToken.checkPermission Change By: jenkins jenkins (04/Apr/14 2:05 PM) Component/s: build-token-root This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22503) There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears
Vitaliy Baskoff updated JENKINS-22503 There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears Change By: Vitaliy Baskoff (04/Apr/14 2:08 PM) Attachment: gerrit_retrigger_mult_patchsets.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22503) There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears
Vitaliy Baskoff commented on JENKINS-22503 There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears The same is for opened ones. Screen-shot was made for reference only, I will replace it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-22503) There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears
Vitaliy Baskoff updated JENKINS-22503 There is no possibility manually re-trigger patchsets from several review simulteniosly, Please select something to build appears Change By: Vitaliy Baskoff (04/Apr/14 2:11 PM) Attachment: gerrit_retrigger_mult_patchsets.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-22506) HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details
Keith Jacobs created JENKINS-22506 HP ALM Tools Plug-In Displays ALM URL to View Test Results Rather Than Showing Reporter Details Issue Type: Bug Affects Versions: current Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 04/Apr/14 2:22 PM Description: Based on the user guide and current behavior for the HP ALM Tools plug-in, it appears that the plug-in is moving away from displaying detailed information for failed tests directly in Jenkins, and instead simply provides an ALM URL to view results for the test instance. Previously, when viewing test results in Jenkins, the failed test instances displayed the actual Reporter output information from the automated scripts. Now, the test results for the failed tests simply point the user to an ALM URL with the format "td://Project.Domain.qcserver/qcbin/TestRuns?EntityLogicalName=runEntityID=run_id" The URL is not clickable. It must be pasted into a browser. However, that is not our main concern. We have developers who want to see the results directly in Jenkins without having to log into ALM. It appears that the build option to "Running Tests Sets from ALM" is still showing Reporter statements, but the build option to "Run Server Side tests using HP ALM Lab Management" is just showing the ALM URL. We would like an option to have the Reporter statement details displayed in our test results. Project: Jenkins Priority: Major Reporter: Keith Jacobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [openid] (JENKINS-22505) jenkins unable to discover OpenID (unsupported SNI by Jenkins)
Florian Klink commented on JENKINS-22505 jenkins unable to discover OpenID (unsupported SNI by Jenkins) Seems like it comes down to this issue for Apache HttpComponents: https://issues.apache.org/jira/browse/HTTPCLIENT-1119 (which was fixed with Version 4.3.2) Could you update the bundled commons-httpclient to version 4.3.2 (or latest 4.3.3), so that SNI works? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-22507) org.jvnet.hudson.reactor.ReactorException in Jenkins 1.556 after click on monitor maven process during a Build
Peter Lomax created JENKINS-22507 org.jvnet.hudson.reactor.ReactorException in Jenkins 1.556 after click on monitor maven process during a Build Issue Type: Bug Assignee: Unassigned Attachments: jenkins button.png Components: maven, plugin Created: 04/Apr/14 3:24 PM Description: In Jenkins 1.556, during a Build i clicked on the button "monitor maven process" (i'm not sure about is name, my jenkins installation is in french, i post the picture of the menu) and it cause an OutOfMemory error. I tried to restart to solve the problem and my Jenkins never restart... In all version above the 1.540 i have the following error on starting : hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:234) 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 jenkins.model.Jenkins.executeReactor(Jenkins.java:910) at jenkins.model.Jenkins.init(Jenkins.java:809) at hudson.model.Hudson.init(Hudson.java:82) at hudson.model.Hudson.init(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) 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 jenkins.model.Jenkins$7.runTask(Jenkins.java:899) 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:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) ... 8 more Caused by: java.lang.OutOfMemoryError: unable to create new native thread at java.lang.Thread.start0(Native Method) at java.lang.Thread.start(Thread.java:691) at hudson.model.ViewJob.clinit(ViewJob.java:81) at sun.misc.Unsafe.ensureClassInitialized(Native Method) at sun.reflect.UnsafeFieldAccessorFactory.newFieldAccessor(UnsafeFieldAccessorFactory.java:43) at sun.reflect.ReflectionFactory.newFieldAccessor(ReflectionFactory.java:140) at java.lang.reflect.Field.acquireFieldAccessor(Field.java:949) at java.lang.reflect.Field.getFieldAccessor(Field.java:930) at java.lang.reflect.Field.get(Field.java:372) at net.java.sezpoz.IndexItem.instance(IndexItem.java:185) at hudson.ExtensionFinder$GuiceFinder.instantiate(ExtensionFinder.java:355) at hudson.ExtensionFinder$GuiceFinder.access$700(ExtensionFinder.java:234) at hudson.ExtensionFinder$GuiceFinder$SezpozModule$1.get(ExtensionFinder.java:531) at com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86) at com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55) at com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:66) at com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path OK, I found a possible solution: is the old java.io.* API still being used? If so, upgrade to java.nio.*, especially when reading filenames from disk the java.io.File.listFiles() method replaces invalid chars with the default unknown char character of the active charset, whereas java.nio.Files.newDirectoryStream does not do such a thing (at least apparently, see https://github.com/jjYBdx4IL/filenameenc/blob/master/src/main/java/filenameenc/Test.java). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero commented on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path OK, I found a possible solution: is the old java.io.* API still being used? If so, upgrade to java.nio.*, especially when reading filenames from disk the java.nio.File.listFiles() method replaces invalid chars with the default unknown char character of the active charset, whereas java.nio.Files.newDirectoryStream does not do such a thing (at least apparently, see https://github.com/jjYBdx4IL/filenameenc/blob/master/src/main/java/filenameenc/Test.java). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mr Cinquero edited a comment on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path OK, I found a possible solution: is the old java.io.* API still being used? If so, upgrade to java.nio.*, especially when reading filenames from disk the java.io.File.listFiles() method replaces invalid chars with the default unknown char character of the active charset, whereas java.nio.Files.newDirectoryStream() does not do such a thing (at least apparently, see https://github.com/jjYBdx4IL/filenameenc/blob/master/src/main/java/filenameenc/Test.java). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21999) Computer does not exist returns NPE
Clinton Barr commented on JENKINS-21999 Computer does not exist returns NPE Any idea when this will make it into an official release? I was actually making a comment yesterday evening when I saw these updates. We're having a similar problem: Basically, when we start a job on any given node, there's a high chance that the next job queued to run on the same node will attempt to start and then fail with this exception: FATAL: null java.lang.NullPointerException at hudson.model.Slave.createLauncher(Slave.java:348) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:564) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:481) at hudson.model.Run.execute(Run.java:1688) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) I say "high chance" because this exception is fairly reproducible in our systems with some variation. Most often, this occurs in builds triggered used in the Parameterized Build Plugin. Does anyone have an idea if our issues might be solved by this fix as well? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-22115) FATAL: hudson/tasks/Mailer$UserProperty
Valerio Santinelli commented on JENKINS-22115 FATAL: hudson/tasks/Mailer$UserProperty We are experiencing the same issue with 1.557 and all plugins up to date. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [grails] (JENKINS-22508) grails.work.dir breaks if the job has spaces in the name
john cooper
created JENKINS-22508
grails.work.dir breaks if the job has spaces in the name
Issue Type:
Bug
Affects Versions:
current
Assignee:
jeffg2one
Components:
grails
Created:
04/Apr/14 4:33 PM
Description:
If your workspace has spaces in the name then it breaks the wordir param.
It uses "-Dgrails.work.dir=/var/lib/jenkins/jobs/Job With Spaces/workspace//target" by default with that quoting and so breaks.
Should have single quotes around the directroy. Setting the grails.work.dir manually to '${WORKSPACE}/.grails' with the single quotes in the interface seems to work around the issue but is a bit of a hack.
Environment:
Grails plug 1.7 and Jenkins ver. 1.532.2
Project:
Jenkins
Priority:
Minor
Reporter:
john cooper
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ui-changes] (JENKINS-22476) Create new job using Copy existing item autocomplete does not work
richard alanis commented on JENKINS-22476 Create new job using Copy existing item autocomplete does not work I've checked this is a clean installation. The problem is present in Jenkins versions 1.557, 1.555, and 1.553, but is not in versions 1.552, 1.551, and 1.550. So, seems the problem was introduced with version 1.553. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb] (JENKINS-22509) ghprb requires restart Jenkins when authTokens are changed in configuration
Radek Chromy created JENKINS-22509 ghprb requires restart Jenkins when authTokens are changed in configuration Issue Type: Bug Affects Versions: current Assignee: Honza Brázdil Components: ghprb Created: 04/Apr/14 4:53 PM Description: When github oauth tokens are regenerated and updated in jenkins configuration, ghprb plugin still uses the old configuration and does not tries to reconnect with new one. Jenkins has to be restarted to apply new settings. Project: Jenkins Labels: plugins Priority: Major Reporter: Radek Chromy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Eric Helgeson commented on JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm This may have caused a regression in JENKINS-22346 with ssh key auth. Workes in 1.555 and below. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-21999) Computer does not exist returns NPE
Daniel Beck commented on JENKINS-21999 Computer does not exist returns NPE Clinton Barr: Unless delayed, the change will be in 1.559 to be released in 1.5 weeks or so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity
Kevin Wojniak commented on JENKINS-17526 Broken CSS when reloading Jenkins after a time of inactivity I'm still seeing this issue with 1.556 on OS X 10.9.2. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Adam Daughterson commented on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel We are seeing this constantly on our build slaves during gcc and ARM compilation: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at com.sun.proxy.$Proxy47.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1676) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) I've completely turned off the Response Time check, bumped the heap size to 512MB (monitoring indicates that this is ample), ensured that the slave is using Oracle JRE (1.6.0_45-b06). Slave is Ubuntu 10.04 (fully updated) 4 core, 1GB RAM living on Suse KVM host. Monitoring indicates that CPU consumption and load average are definitely high (compilation, etc). This is a really ugly issue. What is the status of development? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-6817) FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel
Adam Daughterson edited a comment on JENKINS-6817 FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel We are seeing this constantly on our build slaves during gcc and ARM compilation: FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) at com.sun.proxy.$Proxy47.join(Unknown Source) at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:925) at hudson.tasks.CommandInterpreter.join(CommandInterpreter.java:137) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:97) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:66) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:585) at hudson.model.Run.execute(Run.java:1676) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) I've completely turned off the Response Time check, bumped the heap size to 512MB (monitoring indicates that this is ample), ensured that the slave is using Oracle JRE (1.6.0_45-b06). Master is Ubuntu 10.04 (fully updated) 8 core, 16GB RAM physical host with Jenkins 1.555. Slave is Ubuntu 10.04 (fully updated) 4 core, 1GB RAM living on Suse KVM host. Monitoring indicates that CPU consumption and load average are definitely high (compilation, etc). This is a really ugly issue. What is the status of development? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-21998) Testlink plugin - Unable to retrieve test-steps
Sebastien Girard commented on JENKINS-21998 Testlink plugin - Unable to retrieve test-steps Can anyone please advise? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobgenerator] (JENKINS-22500) Not able to add step: Post build action - Build other Projects with Job name that uses generator parameter for generating Job name.
Sylvain Benner edited a comment on JENKINS-22500 Not able to add step: Post build action - Build other Projects with Job name that uses generator parameter for generating Job name. Hi Tanvi, Thank you for the report. Sorry, I don't understand your use case with just the title. Can you be more specific ? Instead of Build Other Projects, I would use the publisher "Trigger new parameterized job" where you can pass the generator parameters, see the example on the wiki page. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22053) NullPointerException during polling when using git inverse branch choosing strategy
Mark Waite commented on JENKINS-22053 NullPointerException during polling when using git inverse branch choosing strategy I confirmed that the null pointer exception is still visible in the log as of git-client-plugin 1.8.0 and git-plugin 2.2.0. Started on Apr 4, 2014 2:49:22 PM Polling SCM changes on master Using strategy: Inverse [poll] Last Built Revision: Revision 79b09609c1304a3db713c6a4f3bab0d46c85db56 (origin/master) Fetching changes from the remote Git repositories Fetching upstream changes from git://github.com/jenkinsci/git-client-plugin.git Polling for changes in ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@38b93a92[JENKINS-22053-inverse-build-strategy-npe] java.lang.NullPointerException at hudson.plugins.git.util.InverseBuildChooser.getCandidateRevisions(InverseBuildChooser.java:45) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:535) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:457) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1588) at hudson.model.AbstractProject._poll(AbstractProject.java:1558) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-22468) Changes Transaction links are losing a character from the webui url
Joshua Sherwood resolved JENKINS-22468 as Fixed Changes Transaction links are losing a character from the webui url Fixed in 0.6.26, parsing of url was off by 1 in substring. Change By: Joshua Sherwood (04/Apr/14 8:57 PM) Status: Open Resolved Fix Version/s: current 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/d/optout.
[JIRA] [accurev] (JENKINS-6485) Accurev sometimes fails to export the ACCUREV_LAST_TRANSACTION variable, causing build to fail
Joshua Sherwood resolved JENKINS-6485 as Fixed Accurev sometimes fails to export the ACCUREV_LAST_TRANSACTION variable, causing build to fail Should be fixed in 0.6.26 (actually I believe it was fixed in 0.6.23, but you should take 26 or higher) Change By: Joshua Sherwood (04/Apr/14 8:59 PM) Status: Open Resolved Fix Version/s: current 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/d/optout.
[JIRA] [accurev] (JENKINS-11241) AccuRev: reduce load and increase speed for SCM polling
Joshua Sherwood assigned JENKINS-11241 to Joshua Sherwood AccuRev: reduce load and increase speed for SCM polling Change By: Joshua Sherwood (04/Apr/14 9:00 PM) Assignee: ScottTatum JoshuaSherwood This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-6175) Accurev changelog fails with return code 1
Joshua Sherwood resolved JENKINS-6175 as Fixed Accurev changelog fails with return code 1 Timewarp errors should no longer occur. Calls to accurev should now be setting AC_SYNC=ignore, which disables any timewarp checking. Change By: Joshua Sherwood (04/Apr/14 9:04 PM) Status: Open Resolved Assignee: ScottTatum JoshuaSherwood Fix Version/s: current 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/d/optout.
[JIRA] [accurev] (JENKINS-13817) Jenkins Displays Accurev Password in Logs
Joshua Sherwood assigned JENKINS-13817 to Joshua Sherwood Jenkins Displays Accurev Password in Logs Change By: Joshua Sherwood (04/Apr/14 9:06 PM) Assignee: ScottTatum JoshuaSherwood This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22053) NullPointerException during polling when using git inverse branch choosing strategy
Mark Waite edited a comment on JENKINS-22053 NullPointerException during polling when using git inverse branch choosing strategy I confirmed that the null pointer exception is still visible in the log as of git-client-plugin 1.8.0 and git-plugin 2.2.0. Started on Apr 4, 2014 2:49:22 PM Polling SCM changes on master Using strategy: Inverse [poll] Last Built Revision: Revision 79b09609c1304a3db713c6a4f3bab0d46c85db56 (origin/master) Fetching changes from the remote Git repositories Fetching upstream changes from git://github.com/jenkinsci/git-client-plugin.git Polling for changes in ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@38b93a92[JENKINS-22053-inverse-build-strategy-npe] java.lang.NullPointerException at hudson.plugins.git.util.InverseBuildChooser.getCandidateRevisions(InverseBuildChooser.java:45) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:535) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:457) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1588) at hudson.model.AbstractProject._poll(AbstractProject.java:1558) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) The work around (use a workspace for polling) is successful. The root problem seems to be that the call to expand variable names needs the environment variables for a job, yet the environment variables for a job are only available when a workspace is available. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22053) NullPointerException during polling when using git inverse branch choosing strategy
Mark Waite edited a comment on JENKINS-22053 NullPointerException during polling when using git inverse branch choosing strategy I confirmed that the null pointer exception is still visible in the log as of git-client-plugin 1.8.0 and git-plugin 2.2.0. Started on Apr 4, 2014 2:49:22 PM Polling SCM changes on master Using strategy: Inverse [poll] Last Built Revision: Revision 79b09609c1304a3db713c6a4f3bab0d46c85db56 (origin/master) Fetching changes from the remote Git repositories Fetching upstream changes from git://github.com/jenkinsci/git-client-plugin.git Polling for changes in ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@38b93a92[JENKINS-22053-inverse-build-strategy-npe] java.lang.NullPointerException at hudson.plugins.git.util.InverseBuildChooser.getCandidateRevisions(InverseBuildChooser.java:45) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:535) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:457) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject.pollWithWorkspace(AbstractProject.java:1588) at hudson.model.AbstractProject._poll(AbstractProject.java:1558) at hudson.model.AbstractProject.poll(AbstractProject.java:1490) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) The suggested work around (use a workspace for polling) did not seem to work for me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22434) jgit clean after checkout fails with unmappable chars in path
Mark Waite commented on JENKINS-22434 jgit clean after checkout fails with unmappable chars in path Unfortunately, I don't think we can use java.nio.Files.newDirectoryStream() since it seems to be limited to JDK 7. Jenkins continues to support JDK 6 so that we don't drop users from platforms they are using, even though those platforms are only supported by open source versions of Java. JDK 5 support was only dropped from Jenkins about a year ago, and there are still many users running Java 6 on their Jenkins servers. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-22495) When rundeck job option values have hyphens in them, they don't get correctly parsed in RDECK_EXEC_ARG_
Roshan Revankar resolved JENKINS-22495 as Fixed When rundeck job option values have hyphens in them, they dont get correctly parsed in RDECK_EXEC_ARG_ Fixed and merged https://github.com/jenkinsci/rundeck-plugin/pull/6 Change By: Roshan Revankar (04/Apr/14 10:22 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-19244) jenkins random hang during startup - Solaris and Linux
Michael Whidden commented on JENKINS-19244 jenkins random hang during startup - Solaris and Linux Having the same issue. Jenkins startup on Solaris hangs after 'Augmented all extensions'. Removing all jobs works (103 jobs). I tried adding back the jobs one at a time, and it only seems to be an issue when there are more than 5 or 6 jobs. -Dhudson.model.Hudson.parallelLoad=false did solve the problem, so it seems to be an issue with the parallel load when there are more than a small number of jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project] (JENKINS-22469) SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI
ikedam commented on JENKINS-22469 SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI example steps using CLI: Parepare users and projects as above. *Grant Overall.Read and Job.Read to Anonymous, for JENKINS-12543.* retreive jenkins-cli.jar curl -o jenkins-cli.jar http://[path to jenkins]/jnlpJars/jenkins-cli.jar retreive current config.xml java -jar jenkins-cli.jar -s http://[path to jenkins]/ get-job [projectname] --username devel --password devel config.xml modify "useriddevel/userid" to "useridadmin/userid" in config.xml Overwrite the configuration java -jar jenkins-cli.jar -s http://[path to jenkins]/ update-job [projectname] --username devel --password devel config.xml Open the configuration page. The project is configured to run as "admin". This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ssh-slaves] (JENKINS-7641) Slaves hang when archiving artifacts
Gene Ratzlaff commented on JENKINS-7641 Slaves hang when archiving artifacts Like mjmac, hangs after "Archiving artifacts" if I don't have "Response Time" checked under "Preventive Node Monitoring" for my slave nodes. However, if the monitoring is enabled, I get the IOException. Happens more often than not, but is intermittent. If I use my Jenkins master (jenkins-1.549-1.1; Intel server with RHEL 6.4) as a slave I don't see any issues, ever. My other slaves are IBM PPC servers (also with RHEL6.4) - that's where I see the problem. I've only tested with a 20-byte file, so size isn't the issue. If I kill a hung job I get the following: Archiving artifacts ERROR: Failed to archive artifacts: the_date.txt java.io.IOException: java.io.IOException: Failed to extract /bgusr/home1/jenkins/bgqmsn0/workspace/gene_triggerer2/transfer of 1 files at hudson.FilePath.readFromTar(FilePath.java:2088) at hudson.FilePath.copyRecursiveTo(FilePath.java:2000) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1695) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.io.IOException at hudson.remoting.FastPipedInputStream.read(FastPipedInputStream.java:175) at hudson.util.HeadBufferingStream.read(HeadBufferingStream.java:61) at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:175) at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) at org.apache.tools.tar.TarBuffer.readBlock(TarBuffer.java:257) at org.apache.tools.tar.TarBuffer.readRecord(TarBuffer.java:223) at hudson.org.apache.tools.tar.TarInputStream.getNextEntry(TarInputStream.java:228) at hudson.FilePath.readFromTar(FilePath.java:2066) ... 12 more at hudson.FilePath.copyRecursiveTo(FilePath.java:2007) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:756) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:705) at hudson.model.Run.execute(Run.java:1695) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.util.concurrent.ExecutionException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request$1.get(Request.java:278) at hudson.remoting.Request$1.get(Request.java:210) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) at hudson.FilePath.copyRecursiveTo(FilePath.java:2003) ... 11 more Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2570) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1314) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:368) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at
[JIRA] [scm-sync-configuration] (JENKINS-15128) Renaming job doesn't work with Git
Ronald Chen commented on JENKINS-15128 Renaming job doesnt work with Git This is the single biggest blocker for the usage of this plugin. I want people to freely rename jobs and give them better names as they see fit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project] (JENKINS-22469) SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI
ikedam commented on JENKINS-22469 SpecificUsersAuthorizationStrategy easily bypassed by REST/CLI Authentications when called SpecificUsersAuthorizationStrategy#readResolve (tested with 1.532) When Authentication Jenkins Boot SYSTEM REST devel CLI devel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Ray Sennewald created JENKINS-22510 Clean After Checkout Results in Failed to Checkout Revision Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 05/Apr/14 12:20 AM Description: We're executing a job, and trying to perform a git clean. One of our submodules is dirty, and unfortunately since the Jenkins GIT plugin cleans after checkout, we get the following error: FATAL: Command "git submodule update --init --recursive" returned status code 1: stdout: stderr: error: Your local changes to the following files would be overwritten by checkout: minified/sidecar.js minified/sidecar.lite.js minified/sidecar.lite.min.js minified/sidecar.min.js Please, commit your changes or stash them before you can switch branches. Aborting Unable to checkout 'd58c3304230e4bf26ffb3fa6986d4b6ba90d4c66' in submodule path 'sugarcrm/sidecar' I tested using the Pre-SCM Buildstep plugin and performing a git clean before the checkout fixes the problem. Project: Jenkins Priority: Major Reporter: Ray Sennewald This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Ray Sennewald commented on JENKINS-22510 Clean After Checkout Results in Failed to Checkout Revision David Wang has implemented functionality to Clean Before Checkout, which actually helps fix this scenario. His pull request is here: https://github.com/jenkinsci/git-plugin/pull/220. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Ray Sennewald updated JENKINS-22510 Clean After Checkout Results in Failed to Checkout Revision Change By: Ray Sennewald (05/Apr/14 12:24 AM) Description: Wereexecutingajob,andtryingtoperformagitclean.Oneofoursubmodulesisdirty,andunfortunatelysincetheJenkinsGITplugincleansaftercheckout,wegetthefollowingerror:FATAL:Commandgitsubmoduleupdate--init--recursivereturnedstatuscode1:stdout:stderr:error:Yourlocalchangestothefollowingfileswouldbeoverwrittenbycheckout: minified/sidecar.js minified/sidecar.lite.js minified/sidecar.lite.min.js minified/sidecar.min.jsPlease,commityourchangesorstashthembeforeyoucanswitchbranches.AbortingUnabletocheckoutd58c3304230e4bf26ffb3fa6986d4b6ba90d4c66insubmodulepathsugarcrm/sidecarItestedusingthePre-SCMBuildsteppluginandperformingagitcleanbeforethecheckoutfixestheproblem. Specificallyhavingitperform:gitsubmoduleforeach--recursivegitclean-fdxgitsubmoduleforeach--recursivegitreset--hardbeforewedothecheckoutfixesit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Mark Waite commented on JENKINS-22510 Clean After Checkout Results in Failed to Checkout Revision Considering the number of cases related to this topic over the course of the evolution of the git plugin, I'd very much prefer that we have a very deep set of tests created which will assure that submodules behave as desired. Some of the related bugs (JENKINS-8315, JENKINS-7445) are listed as fixed, yet those fixes either did not survive, or do not meet your need. I'd really like more tests that express the failure cases, since the git-client-plugin has very few submodule tests. Ultimately, we may need a "clean before checkout" operation, but it seems like we should first invest effort to create unit tests which will assure that submodules are behaving as expected in the git client plugin (and possibly in the git plugin). Relying on the user to know when they should select "clean before checkout" and when they should "clean after checkout" seems like we're expecting too much from the users. I would very much prefer to find a sequence which avoids requiring the addition of yet another form of clean. We have "wipe workspace" which removes everything, we have "clean after checkout", and this will add "clean before checkout". Since you and David are active users of submodules, would you be willing to provide one or more test cases which illustrate this failure mode, then use that test case to evaluate alternatives to fix the test? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Mark Waite edited a comment on JENKINS-22510 Clean After Checkout Results in Failed to Checkout Revision Considering the number of cases related to this topic over the course of the evolution of the git plugin, I'd very much prefer that we have a very deep set of tests created which will assure that submodules behave as desired. Some of the related bugs (JENKINS-8315, JENKINS-7445) are listed as fixed, yet those fixes either did not survive, or do not meet your need. I'd really like more tests that express the failure cases, since the git-client-plugin has very few submodule tests. Ultimately, we may need a "clean before checkout" operation, but it seems like we should first invest effort to create unit tests which will assure that submodules are behaving as expected in the git client plugin (and possibly in the git plugin). Relying on the user to know when they should select "clean before checkout" and when they should "clean after checkout" seems like we're expecting too much from the users. I would very much prefer to find a sequence which avoids requiring the addition of yet another form of clean. We have "wipe workspace" which removes everything, we have "clean after checkout", and this will add "clean before checkout". Since you and David are active users of submodules, would you be willing to provide one or more test cases which illustrate this failure mode, then use that test case to evaluate alternatives to fix the test? As an example of an alternative, would the "git clean -ffxd" command (double f arguments clean untracked directories managed by another repository) resolve the issue without requiring the addition of a new command This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-22510) Clean After Checkout Results in Failed to Checkout Revision
Mark Waite edited a comment on JENKINS-22510 Clean After Checkout Results in Failed to Checkout Revision Considering the number of cases related to this topic over the course of the evolution of the git plugin, I'd very much prefer that we have a very deep set of tests created which will assure that submodules behave as desired. Some of the related bugs (JENKINS-8315, JENKINS-7445) are listed as fixed, yet those fixes either did not survive, or do not meet your need. I'd really like more tests that express the failure cases, since the git-client-plugin has very few submodule tests. Ultimately, we may need a "clean before checkout" operation, but it seems like we should first invest effort to create unit tests which will assure that submodules are behaving as expected in the git client plugin (and possibly in the git plugin). Relying on the user to know when they should select "clean before checkout" and when they should "clean after checkout" seems like we're expecting too much from the users. I would very much prefer to find a sequence which avoids requiring the addition of yet another form of clean. We have "wipe workspace" which removes everything, we have "clean after checkout", and this will add "clean before checkout". Since you and David are active users of submodules, would you be willing to provide one or more test cases which illustrate this failure mode, then use that test case to evaluate alternatives to fix the test? As an example of an alternative, would the "git clean -ffxd" command (double f arguments clean untracked directories managed by another repository) resolve the issue without requiring the addition of a new command? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [svnmerge] (JENKINS-22284) new field in the feature branch creation form, to manage multi-project repository layout
Hugues Chabot commented on JENKINS-22284 new field in the feature branch creation form, to manage multi-project repository layout The Multi Project Layout is documented in the Subversion Book. I think it should be well supported by the plugin. However, is it possible to handle that directory structure in a general way? For instance, given a SVN path prefix/(trunk|branches)(/suffix)? and a branch name feature, we could create the new branch in prefix/branches/feature/suffix. In the case of a multi projects layout, suffix is the sub-project name, isn't it? In the end, the advanced options could be the complete path of the branch/tag with default values based on your proposal. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
