[JIRA] [conditional-buildstep-plugin] (JENKINS-28023) A Jelly field of another plugin used inside conditional step is renamed
Sergey Kadaner created JENKINS-28023 A Jelly field of another plugin used inside conditional step is renamed Issue Type: Bug Assignee: Dominik Bartholdi Components: conditional-buildstep-plugin Created: 21/Apr/15 7:08 AM Description: I am using Checkmarx Jenkins plugin which works correctly by itself. However when it's placed inside conditional step a field of Jelly "f:entry" named "projectName: is being renamed to "buildStep" inside generated Jenkins HTML page. From what I seen the field is getting renamed on the server side. Project: Jenkins Priority: Critical Reporter: Sergey Kadaner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [docker-build-publish-plugin] (JENKINS-27970) Issue with docker-build-publish-plugin --- build failed, but success is reported
Gireesh Kumar commented on JENKINS-27970 Issue with docker-build-publish-plugin --- build failed, but success is reported Thanks Carlos Sanchez! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27845) Support auto install on Mac OS X
Derk-Jan Hartman commented on JENKINS-27845 Support auto install on Mac OS X Yeah I also have some problems. I was trying to do some global npm packages install, after the auto installed node, in this case `grunt-cli gulp-cli` and it simply fails to execute and find stuff. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28012) Failed to parse POMs during archiving of poms when running maven job
Daniel Hiller commented on JENKINS-28012 Failed to parse POMs during archiving of poms when running maven job Furthermore I don't think that this is related to the issue JENKINS-10629 as Oleg suggests because the generated jar file (of which I think that it would have been transferred) was only 20k of 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] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Qingyou Meng commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same problem on a slave node. Downgrade to 1.609 fixed the problem. size of jar files are about 1~2M size of a tar.gz file is about 37M build log = Notifying upstream projects of job completion Join notifier requires a CauseAction INFO INFO Reactor Summary: INFO INFO web-common SUCCESS 0.587s INFO web-common-open ... SUCCESS 3.574s INFO web-common-frontend ... SUCCESS 1.031s INFO web-common-backend SUCCESS 0.808s INFO web-common-business ... SUCCESS 10.231s INFO INFO BUILD SUCCESS INFO INFO Total time: 19.959s INFO Finished at: Tue Apr 21 14:14:53 CST 2015 INFO Final Memory: 30M/165M INFO JENKINS Archiving /home/jenkinsslave/workspace/workspace/web_dept/web_dept__devprj/考勤v2.0/web-common/web-common-frontend/pom.xml to com.jingoal.web-common/web-common-frontend/1.0.0/web-common-frontend-1.0.0.pom JENKINS Archiving /home/jenkinsslave/workspace/workspace/web_dept/web_dept__devprj/考勤v2.0/web-common/web-common-frontend/target/web-common-frontend-1.0.0.jar to com.jingoal.web-common/web-common-frontend/1.0.0/web-common-frontend-1.0.0.jar JENKINS Archiving /home/jenkinsslave/workspace/workspace/web_dept/web_dept__devprj/考勤v2.0/web-common/web-common-frontend/target/web-common-frontend-1.0.0-sources.jar to com.jingoal.web-common/web-common-frontend/1.0.0/web-common-frontend-1.0.0-sources.jar ERROR: Failed to parse POMs java.io.IOException: Failed to extract /home/jenkinsslave/workspace/workspace/web_dept/web_dept__devprj/考勤v2.0/web-common/web-common-frontend/transfer of 3 files at hudson.FilePath.readFromTar(FilePath.java:2299) at hudson.FilePath.copyRecursiveTo(FilePath.java:2208) channel stopped at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) at hudson.maven.MavenBuild$ProxyImpl.performArchiving(MavenBuild.java:483) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:851) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:536) at hudson.model.Run.execute(Run.java:1741) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) Caused by: java.io.IOException: Truncated TAR archive at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.read(TarArchiveInputStream.java:614) at java.io.InputStream.read(InputStream.java:101) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) at hudson.util.IOUtils.copy(IOUtils.java:40) at hudson.FilePath.readFromTar(FilePath.java:2289) ... 9 more Skipping sonar analysis due to bad build status FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Daniel Beck commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x Nobody here bothered to confirm this now works. So what's the point in nominating an unconfirmed fix for backporting? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28022) Build description longer than 30 chars has hex zero width space added
Daniel Beck commented on JENKINS-28022 Build description longer than 30 chars has hex zero width space added Why is this assigned to 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] [maven-plugin] (JENKINS-28012) Failed to parse POMs during archiving of poms when running maven job
Daniel Hiller updated JENKINS-28012 Failed to parse POMs during archiving of poms when running maven job I've attached the pom anyway Change By: Daniel Hiller (21/Apr/15 6:04 AM) Attachment: pom.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-parameter-plugin] (JENKINS-28019) Some jobs not pulling in revisions at all
ngiger commented on JENKINS-28019 Some jobs not pulling in revisions at all I will try to make a new release, adding among other https://github.com/jenkinsci/git-parameter-plugin/pull/11. Maybe this will fix your problem, too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28012) Failed to parse POMs during archiving of poms when running maven job
Daniel Hiller edited a comment on JENKINS-28012 Failed to parse POMs during archiving of poms when running maven job Furthermore I don't think that this is related to the issue JENKINS-10629 as Slavomir suggests because the generated jar file (of which I think that it would have been transferred) was only 20k of 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] [core] (JENKINS-28022) Build description longer than 30 chars has hex zero width space added
Daniel Beck
updated JENKINS-28022
Build description longer than 30 chars has hex zero width space added
Change By:
Daniel Beck
(21/Apr/15 5:31 PM)
Description:
WeuseaGroovyscripttowritethepackageversionintothebuilddescriptionofajobafteritcompletes.UsersthencopythisfromtheJenkinsUIandpasteittoperformadeploy.Ihavediscoveredoccasionalstrangeissueswiththiswherewhatseemstobeavalidversionnumberisnotfoundbyourdeploysystem.EventuallyIfiguredoutthatJenkinsisinsertinga
{code}
#8203;
{code}
inthestringifitexceeds30chars.Thisisinvisible(obviously)intheUIbutgetscapturedwhenthetextisselectedandcopied/pasted(atleastwithChromeonMacOS).Thisisaproblembecausethiscopy-pasteworkflowhasbeenembeddedhereforseveralyears,andarecentJenkinsupgradehasthrownthisentropyintoit:)
Assignee:
DanielBeck
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [copyartifact-plugin] (JENKINS-28029) Failed to instantiate class hudson.plugins.copyartifact.BuildSelector while copying artifact from another project
Daniel Beck commented on JENKINS-28029 Failed to instantiate class hudson.plugins.copyartifact.BuildSelector while copying artifact from another project Yep, same issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-18938) COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names
Johanns Gregorian
commented on JENKINS-18938
COPYARTIFACT_BUILD_NUMBER_ does not preserve numbers in job names
This issue is nearly (2) years old, unassigned and without comments.
I don't know and cannot imagine the technical issue that lead the developers to elect to remove numbers from the name; but the fix is trivial for anyone brave enough to patch and build the plugin from scratch (see below).
Anyone in the know, please let me know why numbers are removed.
diff --git a/src/main/java/hudson/plugins/copyartifact/CopyArtifact.java b/src/main/java/hudson/plugins/copyartifact/CopyArtifact.java
index 68d0671..4f976ad 100644
--- a/src/main/java/hudson/plugins/copyartifact/CopyArtifact.java
+++ b/src/main/java/hudson/plugins/copyartifact/CopyArtifact.java
@@ -600,7 +600,7 @@ public class CopyArtifact extends Builder implements SimpleBuildStep {
return;
}
data.put("COPYARTIFACT_BUILD_NUMBER_"
- + projectName.toUpperCase().replaceAll("[^A-Z]+", "_"), // Only use letters and _
+ + projectName.toUpperCase().replaceAll("[^A-Z0-9]+", "_"), // Only use alphanumeric and _
Integer.toString(buildNumber));
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [perforce-plugin] (JENKINS-27877) Parallel sync function in Jenkins Perforce Plugin
Oleg Nenashev commented on JENKINS-27877 Parallel sync function in Jenkins Perforce Plugin You can achieve such behavior by specifying extra command-line options in the advanced configuration section This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-14572) Git plug-in fetches all tags even when refspec is provided
Robert Moore
commented on JENKINS-14572
Git plug-in fetches all tags even when refspec is provided
I'm seeing this behavior on Jenkins 1.598, Git-Plugin 2.3.5. It appears that git-plugin first fetches all branches with depth=1 (~500MB in our case), and then it fetches the specific change it needs (~20MB). I've tested locally and the second fetch is the only one needed for a build.
git init /path/to/.jenkins/workspace/Example-Project-Job
Fetching upstream changes from ssh://u...@example.com/Project.git
git --version
using GIT_SSH to set credentials The Credentials for the user system user
git fetch --tags --progress ssh://u...@example.com/Project.git +refs/heads/:refs/remotes/origin/ --depth=1
git config remote.origin.url ssh://u...@example.com/Project.git
git config remote.origin.fetch +refs/heads/:refs/remotes/origin/
git config remote.origin.url ssh://u...@example.com/Project.git
Fetching upstream changes from ssh://u...@example.com/Project.git
using GIT_SSH to set credentials The Credentials for the user system user
git fetch --tags --progress ssh://u...@example.com/Project.git refs/changes/93/3393/2
git rev-parse 12345...123^{commit}
Checking out Revision 12345...123 (mainline)
git config core.sparsecheckout
git checkout -f 12345...123
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-28022) Build description longer than 30 chars has hex zero width space added
Daniel Beck commented on JENKINS-28022 Build description longer than 30 chars has hex zero width space added Workaround: Copy it from the build index 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] [core] (JENKINS-27708) Concurrent build limits not honored on Jenkins 1.607
Oleg Nenashev resolved JENKINS-27708 as Fixed Concurrent build limits not honored on Jenkins 1.607 Marking as fixed Change By: Oleg Nenashev (21/Apr/15 5:33 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-27708) Concurrent build limits not honored on Jenkins 1.607
Oleg Nenashev updated JENKINS-27708 Concurrent build limits not honored on Jenkins 1.607 Change By: Oleg Nenashev (21/Apr/15 5:33 PM) Environment: Jenkins1.607 -1.609 Throttleconcurrentbuildsplugin1.8.4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [perforce-plugin] (JENKINS-27877) Parallel sync function in Jenkins Perforce Plugin
Jerry Yu commented on JENKINS-27877 Parallel sync function in Jenkins Perforce Plugin Looks like I can't find extra command-line options in advanced configuration section, do you know the actual name for that option? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Daniel Beck resolved JENKINS-20211 as Duplicate Pairs of throttled node labels no longer seem to work starting from version 1.536 Assuming to be a duplicate of one of the recent queue processing fixes. Change By: Daniel Beck (21/Apr/15 5:28 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28029) Failed to instantiate class hudson.plugins.copyartifact.BuildSelector while copying artifact from another project
Miguel Rojas
created JENKINS-28029
Failed to instantiate class hudson.plugins.copyartifact.BuildSelector while copying artifact from another project
Issue Type:
Bug
Assignee:
Unassigned
Components:
copyartifact-plugin
Created:
21/Apr/15 7:00 PM
Description:
I've just updated Jenkins to 1.610 and while trying to run a project using a parameterized copy I got the following stack trace:
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class hudson.plugins.copyartifact.BuildSelector from {"name":"BUILD_SELECTOR","stableOnly":false,"kind":""}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
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:123)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
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:168)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
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:1482)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at
[JIRA] [copyartifact-plugin] (JENKINS-28029) Failed to instantiate class hudson.plugins.copyartifact.BuildSelector while copying artifact from another project
Daniel Beck resolved JENKINS-28029 as Duplicate Failed to instantiate class hudson.plugins.copyartifact.BuildSelector while copying artifact from another project Change By: Daniel Beck (21/Apr/15 7:02 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-28021) 'build' does not wait downstreams job to complete
Jesse Glick resolved JENKINS-28021 as Not A Defect build does not wait downstreams job to complete The flow is doing what you requested: starting Job 1, and waiting for it to complete, which it does (successfully). The fact that it happened to trigger a downstream job is irrelevant. (It may not even know about the downstream job, if that is using a reverse build trigger.) If you meant for Job 1 to wait for Job 2 to finish before itself completing, you would need to use the Parameterized Trigger plugin (or make Job 1 itself a workflow using build with wait: true). Change By: Jesse Glick (21/Apr/15 8:48 AM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [checkstyle-plugin] (JENKINS-27887) pmd plugin and checkstyle plugin fail to install
Sylwia Kludacz commented on JENKINS-27887 pmd plugin and checkstyle plugin fail to install The exception that I have reported is shown when I try to re-install the plugin via browser in Manage Plugins. If I try to re-install the plugin manually on Jenkins server by stopping Jenkins, then deleting the plugin file and folder and starting the Jenkins again then I can see the folder structure created fully but Jenkins still shows the plugin in manage plugins as available rather than installed. Where do I find the log message of Jenkins for loading the plugins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Marcus Klein
commented on JENKINS-24686
scm-sync-configuration fails if job name contains whitespace
To work around this issue use the following code in the Jenkins Script console:
hudson.PluginWrapper scmPluginWrapper = jenkins.model.Jenkins.getInstance().getPluginManager().getPlugin("scm-sync-configuration");
java.util.List? commitsQueue = scmPluginWrapper.getPlugin().business.commitsQueue;
// commitsQueue.remove(0);
println(commitsQueue);
Uncomment then the commented line to remove the commit, that breaks the commit process.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [workflow-plugin] (JENKINS-28021) 'build' does not wait downstreams job to complete
Nicolas Labrot commented on JENKINS-28021 build does not wait downstreams job to complete Thanks, I misread the documentation: if the downstream build is in singular This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-28021) 'build' does not wait downstreams job to complete
Nicolas Labrot edited a comment on JENKINS-28021 build does not wait downstreams job to complete Thanks, I misread the documentation: for completion of the downstream build. is in singular This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [workflow-plugin] (JENKINS-28021) 'build' does not wait downstreams job to complete
Nicolas Labrot edited a comment on JENKINS-28021 build does not wait downstreams job to complete Thanks, I misread the documentation: wait for completion of the downstream build. is in singular This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-27345) Jenkins 1.599 blocked when using slave nodes
Cosmin Giurgiu commented on JENKINS-27345 Jenkins 1.599 blocked when using slave nodes Thanks for the tips. I've just installed the monitoring plugin and modify the XMX to 2048M (I think it is enough, we don't have lot of jobs there - only unit test 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] [job-dsl-plugin] (JENKINS-28024) Support Build Publisher Plugin
Mark Syms created JENKINS-28024 Support Build Publisher Plugin Issue Type: New Feature Assignee: Mark Syms Components: job-dsl-plugin Created: 21/Apr/15 8:16 AM Description: Add support for Build Publisher plugin Project: Jenkins Priority: Minor Reporter: Mark Syms This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [plot-plugin] (JENKINS-28025) Additional line style without indicated data points
Hans-Juergen Hafner created JENKINS-28025 Additional line style without indicated data points Issue Type: Improvement Assignee: nidaley Components: plot-plugin Created: 21/Apr/15 8:43 AM Description: When many builds are included in plot line with indicated data points is sometimes unusable. In this case a line without data points looks much better. Environment: Jenkins 1.607 Plot Plugin 1.9 Project: Jenkins Priority: Minor Reporter: Hans-Juergen Hafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-27991) Unable to POST modified config.xml in Jenkins via curl API.
Mahendra Singh
commented on JENKINS-27991
Unable to POST modified config.xml in Jenkins via curl API.
Thanks Daniel:
This comment helped me:
In the Jenkins script console (in Manage Jenkins), enter the following:
System.clearProperty('org.xml.sax.driver')
Then, try the XML API call again.
It worked for me, I am just wondering that if this is a temporary solution. Hope the issue will not come agian.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Omar Kohl commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same issue here after upgrade to 1.610. Jenkins master running on Debian Wheezy. The artifact size is a few MB at most. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27981) Impossible to clone git repo
Sergei Antipov edited a comment on JENKINS-27981 Impossible to clone git repo I reinstalled Slave as a service. I tried 2.2.12 git plugin. I reinstalled msysgit. I deleted Tortoise Git. For now I have error without information: Building remotely on uk-world-jenk03 in workspace C:\Jenkins\workspace\project_win32 Cloning the remote Git repository Cloning repository https://gitlab.company.local/group/project.git git init C:\Jenkins\workspace\project_win32\project # timeout=10 ERROR: Error cloning remote repo 'origin' ERROR: Error cloning remote repo 'origin' Archiving artifacts Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-27991) Unable to POST modified config.xml in Jenkins via curl API.
Mahendra Singh
commented on JENKINS-27991
Unable to POST modified config.xml in Jenkins via curl API.
Just want to confirm that that clearing the system property will not impact my other Builds Jobs on the same Jenkins with uses analysis-core plugin ("Static Analysis Utilities").
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raghuveer Karumuri commented on JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Also.. it is asking Configuration File what should I give for this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27981) Impossible to clone git repo
Sergei Antipov updated JENKINS-27981 Impossible to clone git repo Change By: Sergei Antipov (21/Apr/15 8:20 AM) Description: IcantclonegitrepoonJenkinsSlavenodeviassh+gitprotocol.Error:Buildingremotelyonuk-world-jenk03inworkspaceC:\Jenkins\workspace\ v4world_win32 project_win32 gitrev-parse--is-inside-work-tree#timeout=10FetchingchangesfromtheremoteGitrepositorygitconfigremote.origin.urlgit@gitlab. 2gis company .local:world/ v4world project .git#timeout=10Fetchingupstreamchangesfromgit@gitlab. 2gis company .local:world/ v4world project .gitgit--version#timeout=10usingGIT_SSHtosetcredentialsuk-world-jenk03git-ccore.askpass=truefetch--tags--progressgit@gitlab. 2gis company .local:world/ v4world project .git+refs/heads/*:refs/remotes/origin/*ERROR:Errorfetchingremoterepooriginhudson.plugins.git.GitException:Failedtofetchfromgit@gitlab. 2gis company .local:world/ v4world project .git athudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:735) athudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:983) athudson.plugins.git.GitSCM.checkout(GitSCM.java:1016) atorg.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:122) athudson.scm.SCM.checkout(SCM.java:484) athudson.model.AbstractProject.checkout(AbstractProject.java:1270) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) athudson.model.Run.execute(Run.java:1741) athudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) athudson.model.ResourceController.execute(ResourceController.java:98) athudson.model.Executor.run(Executor.java:374)Causedby:hudson.plugins.git.GitException:Commandgit-ccore.askpass=truefetch--tags--progressgit@gitlab. 2gis company .local:world/ v4world project .git+refs/heads/*:refs/remotes/origin/*returnedstatuscode128:stdout:stderr:plink:unknownoption-ofatal:Couldnotreadfromremoterepository.Pleasemakesureyouhavethecorrectaccessrightsandtherepositoryexists.plinkreallydonthaveoption-o. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raghuveer Karumuri commented on JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Hi , Yes I have added jdk in global configuration as JAVA6 - /apps/opt/jdk160_39_64/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Oleg Nenashev commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive The issue seems to be platform-independent. BTW, I still cannot reproduce it in unit tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Oleg Nenashev updated JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Change By: Oleg Nenashev (21/Apr/15 2:54 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-10629) Tar implimentation can't handle 8GB and doesn't error out.
Kanstantsin Shautsou commented on JENKINS-10629 Tar implimentation cant handle 8GB and doesnt error out. lets remote lts-candidate, it causes issues. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [role-strategy-plugin] (JENKINS-27829) authenticated user role is not working after saml integration
jburrows commented on JENKINS-27829 authenticated user role is not working after saml integration We are seeing the same behavior: Jenkins versions: 1.588, 1.601 role-strategy-plugin version: 2.2.0 SAML Plugin version: 0.3 OS Windows 2008 R2 SP2 Jenkins is running as Service on each Master Server. All SAML functions are working fine, role-strategy-plugin authenticated user id worked with OpenID plugin authenticating through Google, SAML plugin now authenticating through internal PingFederated server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
boris ivan commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same issue here where build slave is Windows 2012. Artifact only a couple of MB. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cloudbees-folder-plugin] (JENKINS-24433) Searchbox cannot be used inside a folder
SCM/JIRA link daemon commented on JENKINS-24433 Searchbox cannot be used inside a folder Code changed in jenkins User: Felix Belzunce Arcos Path: core/src/main/java/hudson/search/Search.java core/src/main/java/hudson/search/SuggestedItem.java test/src/test/java/hudson/search/SearchTest.java http://jenkins-ci.org/commit/jenkins/44db6aef3f055455635da1e126bcd162c95f80df Log: JENKINS-24433 Searchbox doesn't work properly inside a folder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudbees-folder-plugin] (JENKINS-24433) Searchbox cannot be used inside a folder
SCM/JIRA link daemon resolved JENKINS-24433 as Fixed Searchbox cannot be used inside a folder Change By: SCM/JIRA link daemon (21/Apr/15 2:24 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] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Marcus Collins commented on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job Found this issue when I upgraded to Jenkins ver. 1.610, rolling back to Jenkins ver. 1.609 as a workaround. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [throttle-concurrent-builds-plugin] (JENKINS-20211) Pairs of throttled node labels no longer seem to work starting from version 1.536
Peter Triesz commented on JENKINS-20211 Pairs of throttled node labels no longer seem to work starting from version 1.536 with 1.610 throttling started to work again for us. YEY. thanks a bunch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Celso Kurrle commented on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job I got the same error on Debian Server with Jenkins 1.610 and Copy Artifact plugin 1.35 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28012) Failed to parse POMs during archiving of poms when running maven job
Oleg Nenashev commented on JENKINS-28012 Failed to parse POMs during archiving of poms when running maven job JENKINS-10629 updated Tar compression libs (from a legacy 3-years old impl to a modern commons-compress). So JENKINS-10629 should be blamed for any compression bug by default. I needed the file to reproduce the compression/decompression flow and to catch the issue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28011) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job
Peter Gerber commented on JENKINS-28011 Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact when saving a job We got the same issue!!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [scm-sync-configuration-plugin] (JENKINS-26728) scm sync plugin won't reload without saving first
Janno Jõgeva commented on JENKINS-26728 scm sync plugin wont reload without saving first This is my two cents. One way to approach this would be to add a dialogue box or a field to the Reload link which asks for the commit hash to be reloaded. This would be a somewhat untidy solution I agree. On the other hand it would also be a great feature for the plugin that would provide a workaround for the issue. I also think that this is the type of issue that does not get too many followers because people find it when they are not in the best situation in general and will revert to a manual fix 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] [core] (JENKINS-10629) Tar implimentation can't handle 8GB and doesn't error out.
Daniel Beck resolved JENKINS-10629 as Fixed Tar implimentation cant handle 8GB and doesnt error out. Typo in commit seems to have prevented the bot from resolving. Regression in 1.610 is tracked as JENKINS-28013. Change By: Daniel Beck (21/Apr/15 1:55 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] [cloudbees-folder-plugin] (JENKINS-24433) Searchbox cannot be used inside a folder
SCM/JIRA link daemon commented on JENKINS-24433 Searchbox cannot be used inside a folder Code changed in jenkins User: Felix Belzunce Arcos Path: test/src/test/java/hudson/search/SearchTest.java http://jenkins-ci.org/commit/jenkins/cb174607b348636eeaf27c6b0eab502ec1f2f3a6 Log: JENKINS-24433 Improving tests This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cloudbees-folder-plugin] (JENKINS-24433) Searchbox cannot be used inside a folder
SCM/JIRA link daemon commented on JENKINS-24433 Searchbox cannot be used inside a folder Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/search/Search.java core/src/main/java/hudson/search/SuggestedItem.java test/src/test/java/hudson/search/SearchTest.java http://jenkins-ci.org/commit/jenkins/64e832f9d6ff460a648eefcc5575158704b138b3 Log: FIXED JENKINS-24433 Noting merge of #1581. Compare: https://github.com/jenkinsci/jenkins/compare/1a8a00a82c3b...64e832f9d6ff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-27991) Unable to POST modified config.xml in Jenkins via curl API.
Daniel Beck resolved JENKINS-27991 as Duplicate Unable to POST modified config.xml in Jenkins via curl API. Duplicates JENKINS-27548. The plugin sets that value before it processes XML, and that is why you have the problem in the first place. Change By: Daniel Beck (21/Apr/15 12:29 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot-plugin] (JENKINS-28025) Additional line style without indicated data points
Hans-Juergen Hafner commented on JENKINS-28025 Additional line style without indicated data points Created pull request https://github.com/jenkinsci/plot-plugin/pull/18 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [plot-plugin] (JENKINS-28025) Additional line style without indicated data points
Hans-Juergen Hafner commented on JENKINS-28025 Additional line style without indicated data points Created pull request https://github.com/jenkinsci/plot-plugin/pull/18 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raghuveer Karumuri edited a comment on JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Getting below issue while loading the configuration file.. Apr 21, 2015 10:37:01 AM org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin$WeblogicDeploymentPluginDescriptor loadWeblogicEnvironments SEVERE: xs:schema com.thoughtworks.xstream.mapper.CannotResolveClassException: xs:schema at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:56) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:256) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:49) at com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:133) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925) at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin$WeblogicDeploymentPluginDescriptor.loadWeblogicEnvironments(WeblogicDeploymentPlugin.java:558) at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin$WeblogicDeploymentPluginDescriptor.configure(WeblogicDeploymentPlugin.java:527) at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2832) at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2795) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at
[JIRA] [jacoco-plugin] (JENKINS-25616) Support for coverage.xml generated by Android tools
Arno Moonen commented on JENKINS-25616 Support for coverage.xml generated by Android tools That is not really a solution, Better Shao. It does not make sense to parse the data again, if the report has already been generated. As you can tell, several people on GitHub also have mentioned this to be something they would like to see. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [other] (JENKINS-25592) Jenkins UserID's with \ in the name results in not loading of pages
Daniel Beck edited a comment on JENKINS-25592 Jenkins UserIDs with \ in the name results in not loading of pages (useless comment) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-22921) Build Now menu to trigger the pipeline manually
Dawid Malinowski commented on JENKINS-22921 Build Now menu to trigger the pipeline manually This feature was done by me and my pull request is already merged: https://github.com/Diabol/delivery-pipeline-plugin/pull/102 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [docker-build-publish-plugin] (JENKINS-27920) Code to match build ID to tag as latest does not work properly, causing redundant build
Carlos Sanchez resolved JENKINS-27920 as Fixed Code to match build ID to tag as latest does not work properly, causing redundant build Fixed in https://github.com/carlossg/docker-build-publish-plugin/commit/66574a0fa64c6f636a93911e66b24ec91e2573f3 Change By: Carlos Sanchez (21/Apr/15 3:59 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle 8GB and doesn't error out.
Daniel Beck commented on JENKINS-10629 Tar implimentation cant handle 8GB and doesnt error out. Could be backported together with the future fix to JENKINS-28013 once both are soaked enough. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [docker-build-publish-plugin] (JENKINS-27920) Code to match build ID to tag as latest does not work properly, causing redundant build
Carlos Sanchez assigned JENKINS-27920 to Carlos Sanchez Code to match build ID to tag as latest does not work properly, causing redundant build Change By: Carlos Sanchez (21/Apr/15 3:59 PM) Assignee: MichaelNeale CarlosSanchez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
K P commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same issue, identical stack trace. Seems to be platform independent indeed: platform is Windows server 2008. Jobs runs on slave jenkins, which runs on the same same machine (i.e. in the same Windows instance). Artifacts are rather small (.zip of 1.7 MB, .jar of merely 30 KB). Reverting to 1.609 restores the functionality. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [junit-plugin] (JENKINS-18696) Not all test results are being reported
Aaron Humerickhouse commented on JENKINS-18696 Not all test results are being reported Have the same issue. I was on 1.2-beta4 (default with Jenkins), just updated to 1.5 and am seeing the same issue. Files selenium-tests -results --results0.xml --results1.xml --results2.xml --results3.xml --results4.xml I've tried: */results.xml selenium-tests/results/results*.xml **/results/results.xml selenium-tests/results/results0.xml,selenium-tests/results/results1.xml,selenium-tests/results/results2.xml,selenium-tests/results/results3.xml,selenium-tests/results/results4.xml Four different patterns that should get me all of the files are failing to do 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] [junit-plugin] (JENKINS-18696) Not all test results are being reported
Aaron Humerickhouse edited a comment on JENKINS-18696 Not all test results are being reported Have the same issue. I was on 1.2-beta4 (default with Jenkins), just updated to 1.5 and am seeing the same issue. Files selenium-tests -results --results0.xml --results1.xml --results2.xml --results3.xml --results4.xml I've tried: **/results.xml selenium-tests/results/results.xml /results/results.xml selenium-tests/results/results0.xml,selenium-tests/results/results1.xml,selenium-tests/results/results2.xml,selenium-tests/results/results3.xml,selenium-tests/results/results4.xml Four different patterns that should get me all of the files are failing to do 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] [docker-build-publish-plugin] (JENKINS-27970) Issue with docker-build-publish-plugin --- build failed, but success is reported
SCM/JIRA link daemon commented on JENKINS-27970 Issue with docker-build-publish-plugin --- build failed, but success is reported Code changed in jenkins User: Carlos Sanchez Path: src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java http://jenkins-ci.org/commit/docker-build-publish-plugin/cf6e4a204bc5f04672d9d6d6807de06c442ac65a Log: Merge pull request #19 from carlossg/JENKINS-27970 JENKINS-27970 Build doesn't fail even if docker build does Compare: https://github.com/jenkinsci/docker-build-publish-plugin/compare/9bf9e37055f1...cf6e4a204bc5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-22921) Build Now menu to trigger the pipeline manually
Dawid Malinowski resolved JENKINS-22921 as Fixed Build Now menu to trigger the pipeline manually Change By: Dawid Malinowski (21/Apr/15 3:45 PM) Status: Open Resolved Assignee: DawidMalinowski 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] [docker-build-publish-plugin] (JENKINS-27970) Issue with docker-build-publish-plugin --- build failed, but success is reported
SCM/JIRA link daemon commented on JENKINS-27970 Issue with docker-build-publish-plugin --- build failed, but success is reported Code changed in jenkins User: Carlos Sanchez Path: src/main/java/com/cloudbees/dockerpublish/DockerBuilder.java http://jenkins-ci.org/commit/docker-build-publish-plugin/61e65974700c2ea31619782b32a3b27cac83edf0 Log: JENKINS-27970 Build doesn't fail even if docker build does This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [swarm-plugin] (JENKINS-24149) LogConfigurationException due to conflicting commons-logging versions
Dawid Malinowski commented on JENKINS-24149 LogConfigurationException due to conflicting commons-logging versions Gustavo Lucena Dalmaso Your patch works for me. I already created pull request https://github.com/jenkinsci/swarm-plugin/pull/24. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Joe Hansche
commented on JENKINS-20636
RVM and NodeJS plugins are incompatible
Kohsuke Kawaguchi, is this an issue with the ruby runtime plugin? Or an issue with how the NodeJS plugin does its set up? The fact that both rbenv and RVM plugins have this issue, and both rely on the ruby runtime. NodeJS modifies the environment from the decorateLauncher() method, injecting the bin dir of the NodeJS installation into the PATH env var from the Launcher#launch(ProcStarter) method:
@Override
public Launcher decorateLauncher(final AbstractBuild build, Launcher launcher, BuildListener listener) throws IOException, InterruptedException, Run.RunnerAbortedException {
return new DecoratedLauncher(launcher){
@Override
public Proc launch(ProcStarter starter) throws IOException {
...
// HACK: Avoids issue with invalid separators in EnvVars::override in case of different master/slave
String overriddenPaths = NodeJSInstaller.binFolderOf(nodeJSInstallation, build.getBuiltOn())
+ pathSeparator
+ vars.get("PATH");
vars.override("PATH", overriddenPaths);
return super.launch(starter.envs(Util.mapToEnv(vars)));
}
Could it be a threading issue between the NodeJS plugin and the ruby runtime?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Anthony Robinson reopened JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x Still not able to install (1.610) on Ubuntu 10.04 13:23 root@jenkins:~# apt-get install jenkins Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: jenkins 1 upgraded, 0 newly installed, 0 to remove and 38 not upgraded. Need to get 60.3MB of archives. After this operation, 1,063kB of additional disk space will be used. WARNING: The following packages cannot be authenticated! jenkins Authentication warning overridden. Get:1 http://pkg.jenkins-ci.org/debian/ binary/ jenkins 1.610 [60.3MB] Fetched 60.3MB in 3s (18.8MB/s) (Reading database ... 106408 files and directories currently installed.) Preparing to replace jenkins 1.594 (using .../archives/jenkins_1.610_all.deb) ... * Stopping Jenkins Continuous Integration Server jenkins [ OK ] Unpacking replacement jenkins ... dpkg-deb: file `/var/cache/apt/archives/jenkins_1.610_all.deb' contains ununderstood data member data.tar.xz , giving up dpkg: error processing /var/cache/apt/archives/jenkins_1.610_all.deb (--unpack): subprocess dpkg-deb --fsys-tarfile returned error exit status 2 * Starting Jenkins Continuous Integration Server jenkins [ OK ] Errors were encountered while processing: /var/cache/apt/archives/jenkins_1.610_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) 13:23 root@jenkins:~# uname -a Linux jenkins.mgt.test.skytap.com 2.6.32-41-server #90-Ubuntu SMP Tue May 22 12:41:40 UTC 2012 x86_64 GNU/Linux 13:28 root@jenkins:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=10.04 DISTRIB_CODENAME=lucid DISTRIB_DESCRIPTION="Ubuntu 10.04.4 LTS" Change By: Anthony Robinson (21/Apr/15 8:30 PM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Daniel Beck commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x Thanks Anthony! Back to the drawing board I guess. Will probably need to set up an old Ubuntu VM and a build environment to fix this (I doubt I'll have the time in the next few weeks), unless Kohsuke Kawaguchi or one of you steps in and takes a look. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Matt Evans commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same issue, same stack trace, reverted to 1.609 o fix issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [chef-identity-plugin] (JENKINS-28030) The .chef folder is not written on the first build of a job
Tyler Fitch created JENKINS-28030 The .chef folder is not written on the first build of a job Issue Type: Bug Assignee: Tyler Fitch Components: chef-identity-plugin Created: 21/Apr/15 8:42 PM Description: I've had a report that on the first time a job runs, the .chef folder is not being created in the workspace. It appears to be related to jobs that are checking out a git repo (or maybe code checkout in general) in the first build. Project: Jenkins Labels: chef Priority: Major Reporter: Tyler Fitch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27677) SCM Polling does not run
Mark Waite commented on JENKINS-27677 SCM Polling does not run I am not doing any investigation or work on this question. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-10629) Tar implimentation can't handle 8GB and doesn't error out.
Oleg Nenashev commented on JENKINS-10629 Tar implimentation cant handle 8GB and doesnt error out. We may need to revert the fix if I don't find the solution till 1.611 kick-off. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Marcel Beister edited a comment on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same issue, same stack trace after update from 1.608 to 1.610. All nodes run on Windows 7 and artifacts are approximately 10 to 50 MB in 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] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Marcel Beister commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same issue, same stack trace after update from 1.608 to 1.609. All nodes run on Windows 7 and artifacts are approximately 10 to 50 MB in 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] [git-plugin] (JENKINS-28031) Git plugin using committer rather than author name in Changes log
J John
updated JENKINS-28031
Git plugin using committer rather than author name in Changes log
Change By:
J John
(21/Apr/15 11:04 PM)
Issue Type:
Bug
Improvement
Description:
UsingGitPlugin2.3.4.WhenchoosingGITforsourcecontrolsystemandspecifying
Onusing
the
giturlwithhttpandnousername
environmentvariable${CHANGES}
,
when
the
pluginrunsitsetsthecommitterto
logisshownas
a
differentuserthantheauthorandtheonerunningthejenkinsbuild.
onelineas
Setup:JenkinsbuildwithGit.ExecutingNantbuildscript-thisscripthas
[
exec
committer
commandstocallgitforgitadd.andgitcommit-mBuildNumber--authorsvcClairviaBuildandgitpushoriginFixes
]message
Whenthegitpluginisenabled
Ithinkitshouldbeauthorvscommitter
forthe
repo
namein
the
finalpushcommittotheremoterepoalwaysshowsthewronguserbutwillshowtheauthorastheonespecified
log
.
JenkinsisrunningasaservicewiththesvcClairviaBuilduser.Hereisthecommitmessageontheserver:*MS030441isnotthecommitterwhyisthisshowingup?gitconfigglobal-l=user.name=svcClairviaBuilduser.email=svcclairviabu...@johndoe.comBUILD:8.4.2.0-11795a2a7bae5cBrowsecodesvcClairviaBuildauthored3minutesago**ms030441**committed3minutesago
Priority:
Critical
Trivial
Assignee:
NicolasDeLoof
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Jacek Sniecikowski updated JENKINS-28032 Included Regions do not work when monitoring all branches Change By: Jacek Sniecikowski (22/Apr/15 12:45 AM) Description: Setupajobtomonitorallbranches(\* \ *inBranchestobuild)butrestrictittoonefolder(Project1/.*inIncludedRegions).Aslongasyoumakesubmissionstoonebranch,theincludedregionsworksfine.However,whenyoumakeachangeonadifferentbranch,thefirstjobthattriggerswillignoreincludedregionsandpickupchangesfromanylocation.Afterthatthenextjobsonthesamebranchwillfollowtherestrictionscorrectlyuntilachangeonanotherbranchismade.Herespartofmyconfig.xml:scmclass=hudson.plugins.git.GitSCMplugin=git@2.3.5configVersion2/configVersionuserRemoteConfigshudson.plugins.git.UserRemoteConfigurlg...@github.com:SomeAccount/1.git/urlcredentialsIdff33d8db-ec3a-48d2-83cd-6d5cbd8f51a4/credentialsId/hudson.plugins.git.UserRemoteConfig/userRemoteConfigsbrancheshudson.plugins.git.BranchSpecname**/name/hudson.plugins.git.BranchSpec/branchesdoGenerateSubmoduleConfigurationsfalse/doGenerateSubmoduleConfigurationssubmoduleCfgclass=list/extensionshudson.plugins.git.extensions.impl.PathRestrictionincludedRegionsProject1/.*/includedRegionsexcludedRegions/excludedRegions/hudson.plugins.git.extensions.impl.PathRestriction/extensions/scm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Jacek Sniecikowski updated JENKINS-28032 Included Regions do not work when monitoring all branches Change By: Jacek Sniecikowski (22/Apr/15 12:45 AM) Description: Setupajobtomonitorallbranches( / **inBranchestobuild)butrestrictittoonefolder(Project1/.*inIncludedRegions).Aslongasyoumakesubmissionstoonebranch,theincludedregionsworksfine.However,whenyoumakeachangeonadifferentbranch,thefirstjobthattriggerswillignoreincludedregionsandpickupchangesfromanylocation.Afterthatthenextjobsonthesamebranchwillfollowtherestrictionscorrectlyuntilachangeonanotherbranchismade.Herespartofmyconfig.xml:scmclass=hudson.plugins.git.GitSCMplugin=git@2.3.5configVersion2/configVersionuserRemoteConfigshudson.plugins.git.UserRemoteConfigurlg...@github.com:SomeAccount/1.git/urlcredentialsIdff33d8db-ec3a-48d2-83cd-6d5cbd8f51a4/credentialsId/hudson.plugins.git.UserRemoteConfig/userRemoteConfigsbrancheshudson.plugins.git.BranchSpecname**/name/hudson.plugins.git.BranchSpec/branchesdoGenerateSubmoduleConfigurationsfalse/doGenerateSubmoduleConfigurationssubmoduleCfgclass=list/extensionshudson.plugins.git.extensions.impl.PathRestrictionincludedRegionsProject1/.*/includedRegionsexcludedRegions/excludedRegions/hudson.plugins.git.extensions.impl.PathRestriction/extensions/scm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Jacek Sniecikowski updated JENKINS-28032 Included Regions do not work when monitoring all branches Change By: Jacek Sniecikowski (22/Apr/15 12:45 AM) Description: Setupajobtomonitorallbranches( / \ **inBranchestobuild)butrestrictittoonefolder(Project1/.*inIncludedRegions).Aslongasyoumakesubmissionstoonebranch,theincludedregionsworksfine.However,whenyoumakeachangeonadifferentbranch,thefirstjobthattriggerswillignoreincludedregionsandpickupchangesfromanylocation.Afterthatthenextjobsonthesamebranchwillfollowtherestrictionscorrectlyuntilachangeonanotherbranchismade.Herespartofmyconfig.xml:scmclass=hudson.plugins.git.GitSCMplugin=git@2.3.5configVersion2/configVersionuserRemoteConfigshudson.plugins.git.UserRemoteConfigurlg...@github.com:SomeAccount/1.git/urlcredentialsIdff33d8db-ec3a-48d2-83cd-6d5cbd8f51a4/credentialsId/hudson.plugins.git.UserRemoteConfig/userRemoteConfigsbrancheshudson.plugins.git.BranchSpecname**/name/hudson.plugins.git.BranchSpec/branchesdoGenerateSubmoduleConfigurationsfalse/doGenerateSubmoduleConfigurationssubmoduleCfgclass=list/extensionshudson.plugins.git.extensions.impl.PathRestrictionincludedRegionsProject1/.*/includedRegionsexcludedRegions/excludedRegions/hudson.plugins.git.extensions.impl.PathRestriction/extensions/scm This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings-plugin] (JENKINS-28033) Warnings Plugin: The inconsistance between the totality warnings reported by Warnings Plugin and log files itself
Zheng Yan created JENKINS-28033 Warnings Plugin: The inconsistance between the totality warnings reported by Warnings Plugin and log files itself Issue Type: Bug Assignee: Ulli Hafner Components: warnings-plugin Created: 22/Apr/15 2:34 AM Description: I added Warnings Plugin to count all warnings from log files generated by gcc building according the following configuration: File pattern: results/*.log (all logs files will placed under results folder in the workspace) Parser: GUN Make + C Compiler(gcc) but I found there was the inconsistance between the warning totality reported by warning plugin and results/*.log itself. all full build logs will placed under results folder, i check the warning api files which shows all warnings with 11511 Now when I run a simple command in the workspace under results folder : cat *.log | grep -I warning: | wc -l , results is 44067 warnings issue 1: Why the result looks so many differences between them? then i try to check the log files one by one, but found another strange problems: at the end of the build console output, there is warning plugin output: (I put the latest result here and list all real warnings in each log files in the bracket) ... 17:30:10 WARNINGS Parsing warnings in files 'results/*.log' with parser GNU Make + GNU C Compiler (gcc) 17:30:16 WARNINGS Finding all files that match the pattern results/*.log 17:30:16 WARNINGS Parsing 15 files in /home/jenkins/workspace/JOB-DAILY-START 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/1.log with 0 unique warnings and 0 duplicates. (cat 1.log | grep -I warning: | wc -l - real warnings result in 1.log: 0) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/2.log with 703 unique warnings and 0 duplicates. (cat 2.log | grep -I warning: | wc -l - real warnings result in 2.log: 2321) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/3.log with 756 unique warnings and 684 duplicates. (cat 3.log | grep -I warning: | wc -l - real warnings result in 3.log: ) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/4.log with 756 unique warnings and 0 duplicates. (cat 4.log | grep -I warning: | wc -l - real warnings result in 4.log: 59) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/5.log with 756 unique warnings and 0 duplicates. (cat 5.log | grep -I warning: | wc -l - real warnings result in 5.log: 0) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/6.log with 1124 unique warnings and 5 duplicates. (cat 6.log | grep -I warning: | wc -l - real warnings result in 6.log: 1497) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/7.log with 1126 unique warnings and 23 duplicates. (cat 7.log | grep -I warning: | wc -l - real warnings result in 7.log: 347) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/8.log with 1126 unique warnings and 0 duplicates. (cat 8.log | grep -I warning: | wc -l - real warnings result in 8.log: 1) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/9.log with 1126 unique warnings and 0 duplicates. (cat 9.log | grep -I warning: | wc -l - real warnings result in 9.log: 1) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/10.log with 1172 unique warnings and 0 duplicates. (cat 10.log | grep -I warning: | wc -l - real warnings result in 10.log: 81) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/11.log with 1173 unique warnings and 0 duplicates. (cat 11.log | grep -I warning: | wc -l - real warnings result in 11.log: 1) 17:30:16 WARNINGS Successfully parsed file /home/jenkins/workspace/JOB-DAILY-START/results/12.log with 11240 unique warnings and 319 duplicates. (cat 12.log | grep -I warning: | wc -l
[JIRA] [git-plugin] (JENKINS-27981) Impossible to clone git repo
Sergei Antipov resolved JENKINS-27981 as Fixed Impossible to clone git repo Problem was in enviroment vairables. I created environment variables globally inside windows machine and now it works. I tried use jenkins settings for slave node, but this variables not used on slave. (Maybe it's a another bug) Change By: Sergei Antipov (22/Apr/15 5:38 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Andrew Sumner commented on JENKINS-27826 Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test That seems to have fixed it, although I ended up adding it as jenkinsTest 'org.jenkins-ci.plugins:matrix-project:1.4@jar'. I'm now getting a huge amount of warnings in in the console output which I can only assume means something isn't quite right (although as this is my first plugin I've got nothing to compare against): WARNING: Failed to load hudson.matrix.MatrixProject java.lang.NoClassDefFoundError: hudson/tasks/test/AggregatedTestResultAction ... WARNING: Failed to scout hudson.matrix.FilterScript$ImpliesWhitelist java.lang.InstantiationException: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/ProxyWhitelist ... My project is https://github.com/andrew-sumner/buildmaster-plugin/ This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [authorize-project-plugin] (JENKINS-25403) Plugins should switch to '$class' from 'stapler-class' and 'kind'
ikedam updated JENKINS-25403 Plugins should switch to $class from stapler-class and kind https://github.com/jenkinsci/jenkins/pull/1563 might break the backward compatibility. (I haven't tested that, but reported in https://wiki.jenkins-ci.org/display/JENKINS/Extensible+Choice+Parameter+plugin?focusedCommentId=78676310#comment-78676310 Change By: ikedam (22/Apr/15 12:21 AM) Environment: Jenkins1.610 Issue Type: Task Bug Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Jacek Sniecikowski
created JENKINS-28032
Included Regions do not work when monitoring all branches
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git-plugin
Created:
22/Apr/15 12:44 AM
Description:
Set up a job to monitor all branches ('*' in 'Branches to build') but restrict it to one folder ('Project1/.' in 'Included Regions').
As long as you make submissions to one branch, the included regions works fine.
However, when you make a change on a different branch, the first job that triggers will ignore included regions and pick up changes from any location. After that the next jobs on the same branch will follow the restrictions correctly until a change on another branch is made.
Here's part of my config.xml:
scm class="hudson.plugins.git.GitSCM" plugin="git@2.3.5"
configVersion2/configVersion
userRemoteConfigs
hudson.plugins.git.UserRemoteConfig
urlg...@github.com:SomeAccount/1.git/url
credentialsIdff33d8db-ec3a-48d2-83cd-6d5cbd8f51a4/credentialsId
/hudson.plugins.git.UserRemoteConfig
/userRemoteConfigs
branches
hudson.plugins.git.BranchSpec
name**/name
/hudson.plugins.git.BranchSpec
/branches
doGenerateSubmoduleConfigurationsfalse/doGenerateSubmoduleConfigurations
submoduleCfg class="list"/
extensions
hudson.plugins.git.extensions.impl.PathRestriction
includedRegionsProject1/.*/includedRegions
excludedRegions/excludedRegions
/hudson.plugins.git.extensions.impl.PathRestriction
/extensions
/scm
Environment:
Jenkins 1.608, Git plugin 2.3.5
Project:
Jenkins
Labels:
plugin
jenkins
git
Priority:
Minor
Reporter:
Jacek Sniecikowski
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-plugin] (JENKINS-28031) Git plugin using committer rather than author name in Changes log
J John created JENKINS-28031 Git plugin using committer rather than author name in Changes log Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 21/Apr/15 11:01 PM Description: Using Git Plugin 2.3.4. When choosing GIT for source control system and specifying the git url with http and no username, when the plugin runs it sets the committer to a different user than the author and the one running the jenkins build. Setup: Jenkins build with Git. Executing Nant build script - this script has exec commands to call git for "git add ." and "git commit -m "Build Number" --author "svcClairviaBuild" and "git push origin Fixes" When the git plugin is enabled for the repo the final "push" commit to the remote repo always shows the wrong user but will show the author as the one specified. Jenkins is running as a service with the "svcClairviaBuild" user. Here is the commit message on the server: *MS030441 is not the committer why is this showing up? git config global -l = user.name=svcClairviaBuild user.email=svcclairviabu...@johndoe.com BUILD:8.4.2.0-1179 5a2a7bae5cBrowse code svcClairviaBuild authored 3 minutes ago *ms030441* committed 3 minutes ago Project: Jenkins Priority: Critical Reporter: J John This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-5318) Allow default view at user level
Gemini A commented on JENKINS-5318 Allow default view at user level +1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [weblogic-deployer-plugin] (JENKINS-27992) Unable to launch weblogic Deployer plugin after installation
Raghuveer Karumuri commented on JENKINS-27992 Unable to launch weblogic Deployer plugin after installation Getting below issue while loading the configuration file.. Apr 21, 2015 10:37:01 AM org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin$WeblogicDeploymentPluginDescriptor loadWeblogicEnvironments SEVERE: xs:schema com.thoughtworks.xstream.mapper.CannotResolveClassException: xs:schema at com.thoughtworks.xstream.mapper.DefaultMapper.realClass(DefaultMapper.java:56) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.DynamicProxyMapper.realClass(DynamicProxyMapper.java:55) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.PackageAliasingMapper.realClass(PackageAliasingMapper.java:88) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ClassAliasingMapper.realClass(ClassAliasingMapper.java:79) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.ArrayMapper.realClass(ArrayMapper.java:74) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.XStream2$CompatibilityMapper.realClass(XStream2.java:256) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at hudson.util.xstream.MapperDelegate.realClass(MapperDelegate.java:43) at com.thoughtworks.xstream.mapper.MapperWrapper.realClass(MapperWrapper.java:30) at com.thoughtworks.xstream.mapper.CachingMapper.realClass(CachingMapper.java:49) at com.thoughtworks.xstream.core.util.HierarchicalStreams.readClassType(HierarchicalStreams.java:29) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:133) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1061) at hudson.util.XStream2.unmarshal(XStream2.java:109) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1045) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:925) at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin$WeblogicDeploymentPluginDescriptor.loadWeblogicEnvironments(WeblogicDeploymentPlugin.java:558) at org.jenkinsci.plugins.deploy.weblogic.WeblogicDeploymentPlugin$WeblogicDeploymentPluginDescriptor.configure(WeblogicDeploymentPlugin.java:527) at jenkins.model.Jenkins.configureDescriptor(Jenkins.java:2832) at jenkins.model.Jenkins.doConfigSubmit(Jenkins.java:2795) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at
[JIRA] [subversion-plugin] (JENKINS-28026) ERROR: Subversion update has been canceled
Roman Erzhukov created JENKINS-28026 ERROR: Subversion update has been canceled Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 21/Apr/15 11:22 AM Description: Subvresion update cancelled after job started. 14:09:40 EnvInject - Loading node environment variables. 14:09:40 Building on master in workspace C:\dev\jenkins\jobs\my-job\workspace 14:09:40 Cleaning up C:\dev\jenkins\jobs\my-job\workspace\my-module 14:09:45 Deleting C:\dev\jenkins\jobs\my-job\workspace\my-module\target 14:09:45 Updating http://my-svn/trunk/my-module at revision '2015-04-21T14:09:40.817 +0300' 14:09:50 ERROR: Subversion update has been canceled 14:09:50 Build was aborted 14:09:50 Finished: ABORTED Environment: Jenkins 1.610 Subversion plugin 2.5 Oracle JDK 1.7.0_67 x64 Windows Server 2008 R2 Standard Project: Jenkins Priority: Major Reporter: Roman Erzhukov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27998) Git plugin fails to connect
Mark Waite commented on JENKINS-27998 Git plugin fails to connect The git plugin definitely supports a non-standard port as part of the ssh protocol specification. I regularly test that ssh://mwaite@wheezy64b:45022/var/lib/git/mwaite/bin.git (an ssh protected private repo on my machine named "wheezy64b") can be retrieved with the git client plugin automated tests. If the ssh agent allows you to fetch, then it may be that you have an ssh passphrase configured on that ssh key. I believe that if a passphrase is configured on the ssh key, then the only way to make the git client use that passphrase is through the ssh agent. You might also try the "Advanced" button in the credentials plugin to see if it will allow you to enter the passphrase, but my recollection is that didn't allow the plugin to use the passphrase. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I understand your need to save space, but Perforce and the p4 plugin were not designed to share workspaces in quite this way. The server stores a have list (db.have) of the files that have been synced into the workspace. When you use the same workspace with two Jenkins jobs, the p4 plugin switched the workspace root to the Jenkins job build location, but uses the same have list server side. If you set the Workspace root to the same location, then you might have some success, but you must limit the jobs to single execution and use Auto clean/Sync. Another solution might be to use three Perforce workspaces (each with their own Jenkins jobs) one for the common art assets and the other two for the projects (lets call them A and B). Then use symlinks to bring the art assets into the projects for A and B (or instead of symlinks, update the build rules for the new location). For future solutions... I'm currently researching FlexClone with Perforce/Jenkins builds; it requires a NetApp storage, but there may be other similar solutions for other storage vendors. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [subversion-plugin] (JENKINS-26440) svn: E200015: authentication cancelled (subversion plugin 2.5)
Dhiren p commented on JENKINS-26440 svn: E200015: authentication cancelled (subversion plugin 2.5) Same issue on 1.586 with subversion 2.5 plugin. i am using username/password This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Is there an update on this? We're upgrading our Jenkins-Job-Builder program soon. Some issues that were fixed had to do with polling. Even if they caused it, which isn't certain until we've tested it, I'd like to see a list of the "clogged" polls in Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28028) Prevent slave launching when Jenkins is prepared to shutdown
Bruno Meneguello created JENKINS-28028 Prevent slave launching when Jenkins is prepared to shutdown Issue Type: Bug Assignee: Francis Upton Components: core, ec2-plugin Created: 21/Apr/15 5:06 PM Description: I'm using the ec2 plugin, so I don't know if this issue is a core issue or an ec2 issue. When I click in "Prepare to Shutdown", if there are jobs in the queue, Jenkins still launch slaves. I think in shutdown mode, this process shouldn't proceed. Project: Jenkins Priority: Minor Reporter: Bruno Meneguello This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-10629) Tar implimentation can't handle 8GB and doesn't error out.
Kanstantsin Shautsou commented on JENKINS-10629 Tar implimentation cant handle 8GB and doesnt error out. I see no fixes, so my suggestion to add lts label when issue will be resolved to exclude potential lts breakage. Or add some additional tag like "not-ready" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Matthew Smith commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I actually do have the workspace roots set to the same location, the problem is that the db have is being updated but not actually syncing files, this seems like a bug, since it definitely detects the changes in the depot, but doesn't actually update the files on disk. I've gotten around this issue by having one job that does the syncing that is called from the other jobs, and when that completes, the jobs run whatever steps the user originally requested. It's annoying, and a little obfuscated, but we can still limit executors meaningfully enough to let things happen in serial they way they currently need to on this box. We're doing some work internally to bring online a massive storage array, but that introduces other issues with having the files synced and replicated or referenced on the server. Thanks for the response! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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.
