[JIRA] [core] (JENKINS-16871) Inconsistent use of XML escaping in config.xml when uploading through API
Magnus Jacobsson commented on JENKINS-16871 Inconsistent use of XML escaping in config.xml when uploading through API Reproducible with Jenkins 1.560. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-16871) Inconsistent use of XML escaping in config.xml when uploading through API
Magnus Jacobsson commented on JENKINS-16871 Inconsistent use of XML escaping in config.xml when uploading through API A workaround is to enable/disable the job through the REST API. Then the escaping comes back. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [security] (JENKINS-24215) Viewing Workspace or Last Successful Artifacts links throws an exception
Ryan Holmes created JENKINS-24215 Viewing Workspace or Last Successful Artifacts links throws an exception Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: security Created: 12/Aug/14 6:45 AM Description: Jenkins ver. 1.574: The following exception is being thrown now regardless of which project I am accessing, whenever I try to view the "Workspace" or access artifacts (e.g. "Last Successful Artifacts" from a module): java.lang.NoClassDefFoundError: Could not initialize class sun.text.normalizer.NormalizerImpl at java.text.RBTableBuilder.build(Unknown Source) at java.text.RBCollationTables.init(Unknown Source) at java.text.RuleBasedCollator.init(Unknown Source) at java.text.Collator.getInstance(Unknown Source) at hudson.model.DirectoryBrowserSupport$FileComparator.init(DirectoryBrowserSupport.java:436) at hudson.model.DirectoryBrowserSupport.buildChildPaths(DirectoryBrowserSupport.java:477) at hudson.model.DirectoryBrowserSupport.access$000(DirectoryBrowserSupport.java:63) at hudson.model.DirectoryBrowserSupport$BuildChildPaths.call(DirectoryBrowserSupport.java:465) at hudson.model.DirectoryBrowserSupport$BuildChildPaths.call(DirectoryBrowserSupport.java:457) at hudson.FilePath.act(FilePath.java:1014) at jenkins.util.VirtualFile$FilePathVF.run(VirtualFile.java:361) at hudson.model.DirectoryBrowserSupport.serveFile(DirectoryBrowserSupport.java:254) at hudson.model.DirectoryBrowserSupport.generateResponse(DirectoryBrowserSupport.java:123) at org.kohsuke.stapler.HttpResponseRenderer$Default.handleHttpResponse(HttpResponseRenderer.java:117) at org.kohsuke.stapler.HttpResponseRenderer$Default.generateResponse(HttpResponseRenderer.java:66) at org.kohsuke.stapler.Function.renderResponse(Function.java:113) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:98) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at
[JIRA] [core] (JENKINS-4433) log4j upgrade to version 1.2.12 or later
Stefan Brausch commented on JENKINS-4433 log4j upgrade to version 1.2.12 or later Same problem as Roman. Update would be great. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [reverse-proxy-auth] (JENKINS-22298) failing upgrade to 1.3.3
Asmund Ostvold commented on JENKINS-22298 failing upgrade to 1.3.3 I worked around the issue by uninstalling the plugin and installing it again after a restart of 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] [reverse-proxy-auth] (JENKINS-22298) failing upgrade to 1.3.3
Asmund Ostvold closed JENKINS-22298 as Wont Fix failing upgrade to 1.3.3 plugin is working upgrade was failing. See last comment Change By: Asmund Ostvold (12/Aug/14 7:12 AM) Status: Open Closed Fix Version/s: current Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuildscript] (JENKINS-24216) executeOn is created even for non-matrix jobs when updating config with REST API
Magnus Jacobsson created JENKINS-24216 executeOn is created even for non-matrix jobs when updating config with REST API Issue Type: Bug Assignee: Gregory Boissinot Components: postbuildscript Created: 12/Aug/14 7:15 AM Description: When the config is updated through the REST API an entry appears in the XML: executeOnBOTH/executeOn If the config is edited through the web i/f, it is removed again. This occurs for non-matrix jobs, that shouldn't even have this parameter. Environment: Jenkins core 1.560, PostBuildScript plugin 0.16. Project: Jenkins Priority: Minor Reporter: Magnus Jacobsson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [postbuildscript] (JENKINS-24216) executeOn is created even for non-matrix jobs when updating config with REST API
Magnus Jacobsson commented on JENKINS-24216 executeOn is created even for non-matrix jobs when updating config with REST API See also JENKINS-24216 that makes it a little harder to see this problem when diffing two versions of the 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] [postbuildscript] (JENKINS-24216) executeOn is created even for non-matrix jobs when updating config with REST API
Magnus Jacobsson edited a comment on JENKINS-24216 executeOn is created even for non-matrix jobs when updating config with REST API See also JENKINS-16871 that makes it a little harder to see this problem when diffing two versions of the 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] [postbuildscript] (JENKINS-24216) executeOn is created even for non-matrix jobs when updating config with REST API
Magnus Jacobsson commented on JENKINS-24216 executeOn is created even for non-matrix jobs when updating config with REST API There are a number of NPE's in the log during the upload that may be connected to the problem: aug 12, 2014 9:27:33 FM VARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: from.getReport() != null in /jenkins/job/SmokeTestTopTemplateJob/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.summary_report.ACIPluginProjectAction.getReport(ACIPluginProjectAction.java:128) at sun.reflect.GeneratedMethodAccessor331.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTNENode.value(ASTNENode.java:55) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:71) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] [jenkins-multijob-plugin] (JENKINS-22292) Canceling multijob should cancel all children
Dirk Heinrichs commented on JENKINS-22292 Canceling multijob should cancel all children Tested again on current Jenkins. child job are still not aborted... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [buildgraph-view] (JENKINS-19470) Build Graph not displaying
Asmund Ostvold commented on JENKINS-19470 Build Graph not displaying I believe this issue can be closed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23645) Archiving artifacts does not preserve timestamps if filter is **
Timmy Brolin commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** I upgraded to Jenkins 1.575, it made no difference. I will try different combinations of upstream/downstream jobs running on master/slave and post the results. Right now the timestamps are actually incorrect regardless of the filter setting. Not sure if it is connected to the updates I did, some other change, or if the "*" filter happened to run on the master, and the "myfolder/*" filter originally happened to run on the slave without me noticing it. Can't say for sure. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-22525) incompatible InnerClasses attribute error in IBM J9 VM
Martin Kutter commented on JENKINS-22525 incompatible InnerClasses attribute error in IBM J9 VM IBM has tracked the issue with "incompatible inner Class attribute" as APAR IV62298 - see http://www-01.ibm.com/support/docview.wss?uid=swg1IV62298 I've received an iFix for Java 7SR7 from IBM, which fixes the issue. The fix will be applied in the upcoming IBM JDK 7 SR 8. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24194) Build Pipeline Plugin: build cards in run are not aligned
Rostislav Svoboda updated JENKINS-24194 Build Pipeline Plugin: build cards in run are not aligned Change By: Rostislav Svoboda (12/Aug/14 8:26 AM) Attachment: after.png Attachment: before.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20777) Build now link brings up you must use POST method to trigger builds.
Oleg Nenashev resolved JENKINS-20777 as Duplicate Build now link brings up you must use POST method to trigger builds. Duplicates JENKINS-20085 Change By: Oleg Nenashev (12/Aug/14 8:27 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-20777) Build now link brings up you must use POST method to trigger builds.
Oleg Nenashev closed JENKINS-20777 as Duplicate Build now link brings up you must use POST method to trigger builds. Change By: Oleg Nenashev (12/Aug/14 8:27 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cvs] (JENKINS-24217) Trying to add link to diff listing in ViewVC/ViewCVS does not work, and breaks the change history.
Mads Brix created JENKINS-24217 Trying to add link to diff listing in ViewVC/ViewCVS does not work, and breaks the change history. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cvs Created: 12/Aug/14 8:30 AM Description: Simple setup to reproduce the problem: 1) File based CVS repository with one directory (module) with one file. 2) Jenkins project that polls CVS repository for changes. Only build action is "echo Hello". CVS plugin has CVSROOT and module set. Checkboxes enable are (the default) "Use Update" and "Prune Empty Directories". With 1) and 2) things are fine. When I trigger a build (build #1) by committing to the repository build is running. Changes are reported with correct CVS revision and commit message, and it says "Started by an SCM change". The I try to enable the use of a ViewVC server: 3) In "CVS Plugin configuration - Advanced" I change "Repository browser" from (auto) to ViewCVS. Then I add a URL and do Save. I trigger a build (build #2) by committing to the repository and the build is running. But now it says "No changes" instead of reporting CVS revision and commit message - but still says "Started by an SCM change". When I compare the build directories of the two builds there are differences in the files changelog.xml and polling.log: I the failing build (build #2) the changelog.xml is empty, and polling.log says "Repository not found in workspace state, scheduling build". In the OK build (build #1) the changelog.xml has information about CVS revision etc, and the polling.log says "cvs rlog -S -d12 Aug 2014 09:21:09 +020012 Aug 2014 09:25:00 +0200 aDirectory" If I change back to "(auto)" in "Repository browser" the problem is still there. Environment: Jenkins 1.575 and CVS plugin 2.12, running on Linux. Also seen with earlier versions of Jenkins/CVS plugin. Project: Jenkins Labels: viewcvs viewvc cvs Priority: Major Reporter: Mads Brix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [unity3d-plugin] (JENKINS-23081) unity3d plugin not catching compilation errors
lacostej
commented on JENKINS-23081
unity3d plugin not catching compilation errors
What does your editor script do ? In mine, I have something along:
string res = BuildPipeline.BuildPlayer(scenes,target_dir,build_target,build_options);
if (res.Length 0) {
throw new Exception("BuildPlayer failure: " + res);
}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [gerrit-trigger] (JENKINS-24099) Connection to Gerrit is always established on bootup
SCM/JIRA link daemon commented on JENKINS-24099 Connection to Gerrit is always established on bootup Code changed in jenkins User: rinrinne Path: src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer.java src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritItemListener.java src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer/index.jelly src/main/resources/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServer/index_ja.properties src/main/webapp/help-GerritNoConnectionOnBootup.html src/main/webapp/help-GerritPseudoMode.html src/test/java/com/sonyericsson/hudson/plugins/gerrit/trigger/GerritServerHudsonTest.java http://jenkins-ci.org/commit/gerrit-trigger-plugin/94c72b9c362ede876ee512934091d1e5c2f3356a Log: Add "No connection on bootup" option in server config This patch adds a feature that connection to server is not established on bootup. Fix for JENKINS-24099 Task-Url: https://issues.jenkins-ci.org/browse/JENKINS-24099 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23645) Archiving artifacts does not preserve timestamps if filter is **
Timmy Brolin commented on JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** Tested on Jenkins 1.575, with java 1.8 --- Job running on master archiving artifacts to master: Incorrect timestamps. Job running on slave archiving artifacts to master: Timestamps ok. Downstream job running on master copying artifacts from master: Timestamps ok. Downstream job running on slave copying artifacts from master: Timestamps ok. Does this make any sense? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [hockeyapp] (JENKINS-24218) HockeyApp Plugin Authentication Error after jenkins restart
Marcel Gehlen created JENKINS-24218 HockeyApp Plugin Authentication Error after jenkins restart Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: hockeyapp Created: 12/Aug/14 8:46 AM Description: Hello, I am currently setting up a new Jenkins CI for iOS, which also uploads to HockeyApp. Since the setup is not final and the server ist restarted from time to time I noticed a strange behavior when uploading to HockeyApp: 1. initially the configured Post-Build Step "Upload to HockeyApp" works correctly. App is uploaded 2. now restart Jenkins 3. run the job again an receive the following error: Uploading to HockeyApp... /Users/Shared/Jenkins/Home/workspace/iOS_trunk/build/myApp-42.ipa /Users/Shared/Jenkins/Home/workspace/iOS_trunk/build/myApp-42-dSYM.zip HockeyApp Upload Speed: 2,02Gbps Got unexpected response code from HockeyApp: 407 HEADTITLEProxy Authorization Required/TITLE/HEAD BODY BGCOLOR="white" FGCOLOR="black"H1Proxy Authorization Required/H1HR FONT FACE="Helvetica,Arial"B Description: Authorization is required for access to this proxy/B/FONT HR !-- default "Proxy Authorization Required" response (407) -- /BODY 4. create a new API-Token in HockeyApp and assign it in job configuration 5. run job again 6. upload works again ... until next jenkins restart I searched here on, HockeyApp and google, but did not find anything regarding this behavior. Is this a bug or a configuration issue on my side? Thank you very much for your help. Best regards, mgehlen Environment: Jenkins 1.5.72 Mac OS X HockeApp Plugin 1.1.0 Project: Jenkins Labels: plugin Priority: Major Reporter: Marcel Gehlen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24219) Jenkins keep forgetting my password
Matthias Viehweger created JENKINS-24219 Jenkins keep forgetting my password Issue Type: Bug Assignee: stephenconnolly Components: core, credentials Created: 12/Aug/14 9:05 AM Description: Every once in a while, but notably after plugin updates, Jenkins fails to recognize my password. This started several versions ago, but I cannot exactly tell when. After a password-reset through a different admin, I can login again. (Well, not the first time, but this might be related to Chrome auto-filling the password. When typed manually, it works) Project: Jenkins Priority: Major Reporter: Matthias Viehweger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24219) Jenkins keep forgetting my password
Matthias Viehweger commented on JENKINS-24219 Jenkins keep forgetting my password I am entirely unsure which component this is, please review that categorization. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24220) Pipeline without init jobs not migrated correctly. Jobs can not be renamed.
Oliver Gondža created JENKINS-24220 Pipeline without init jobs not migrated correctly. Jobs can not be renamed. Issue Type: Bug Assignee: Unassigned Components: build-pipeline Created: 12/Aug/14 9:16 AM Description: When a pipeline view without init job is migrated from version before ProjectGridBuilder was introduced, readResolve leaves null in gridBuilder. When a jobs is renamed NPE is thrown from BuildPipelineView#onJobRenamed. 1 https://github.com/jenkinsci/build-pipeline-plugin/blob/dcaca3b63a2f222631ef7ea50ef8c838706feb4b/src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java#L279-285 java.lang.NullPointerException at au.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.onJobRenamed(BuildPipelineView.java:808) at hudson.plugins.nested_view.NestedView.onJobRenamed(NestedView.java:163) at hudson.plugins.nested_view.NestedView.onJobRenamed(NestedView.java:163) at jenkins.model.Jenkins.onRenamed(Jenkins.java:2441) at jenkins.model.Jenkins.onRenamed(Jenkins.java:311) at hudson.model.AbstractItem.callOnRenamed(AbstractItem.java:307) at hudson.model.AbstractItem.renameTo(AbstractItem.java:293) at hudson.model.Job.renameTo(Job.java:608) at hudson.model.AbstractProject.renameTo(AbstractProject.java:1664) at hudson.model.Job.doDoRename(Job.java:1371) 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.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46) at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) ... 62 more Project: Jenkins Priority: Major Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-24220) Pipeline without init jobs not migrated correctly. Jobs can not be renamed.
Oliver Gondža
updated JENKINS-24220
Pipeline without init jobs not migrated correctly. Jobs can not be renamed.
Change By:
Oliver Gondža
(12/Aug/14 9:18 AM)
Description:
Whenapipelineviewwithoutinitjobismigratedfromversionbefore{{ProjectGridBuilder}}wasintroduced,{{readResolve}}leavesnullingridBuilder.WhenajobsisrenamedNPEisthrownfrom{{BuildPipelineView#onJobRenamed}}.[1]https://github.com/jenkinsci/build-pipeline-plugin/blob/dcaca3b63a2f222631ef7ea50ef8c838706feb4b/src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java#L279-285{noformat}java.lang.NullPointerException
atau.com.centrumsystems.hudson.plugin.buildpipeline.BuildPipelineView.onJobRenamed(BuildPipelineView.java:808)
athudson.plugins.nested_view.NestedView.onJobRenamed(NestedView.java:163)
athudson.plugins.nested_view.NestedView.onJobRenamed(NestedView.java:163)
atjenkins.model.Jenkins.onRenamed(Jenkins.java:2441)
atjenkins.model.Jenkins.onRenamed(Jenkins.java:311)
athudson.model.AbstractItem.callOnRenamed(AbstractItem.java:307)
athudson.model.AbstractItem.renameTo(AbstractItem.java:293)
athudson.model.Job.renameTo(Job.java:608)
athudson.model.AbstractProject.renameTo(AbstractProject.java:1664)
athudson.model.Job.doDoRename(Job.java:1371)
atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)
atsun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
atsun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
atjava.lang.reflect.Method.invoke(Method.java:597)
atorg.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298)
atorg.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:46)
atorg.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:399)
atorg.kohsuke.stapler.Function.bindAndInvoke(Function.java:161)
atorg.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96)
atorg.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120)
atorg.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
atorg.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
...62more{noformat}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] (JENKINS-24188) p4 credentials does not work for slave
SCM/JIRA link daemon commented on JENKINS-24188 p4 credentials does not work for slave Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/credentials/P4TicketImpl.java src/main/java/org/jenkinsci/plugins/p4/credentials/TicketModeImpl.java src/main/java/org/jenkinsci/plugins/p4/credentials/TrustImpl.java http://jenkins-ci.org/commit/p4-plugin/b27ecfb860f3d049020d7ef80e7621351813a19d Log: Serialisation fix for Credentials Missing `Serializable` implementation https://issues.jenkins-ci.org/browse/JENKINS-24188 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24221) Failed loading some of my job after upgrade to Jenkins 1.575
Pei-Tang Huang created JENKINS-24221 Failed loading some of my job after upgrade to Jenkins 1.575 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core, maven Created: 12/Aug/14 10:01 AM Description: After upgrading jenkins from 1.573 to 1.575 and maven plugin from 2.5 to 2.6, some of my job failed to load as following: java.lang.NullPointerException at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:971) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:740) at hudson.maven.MavenModule.updateTransientActions(MavenModule.java:485) at hudson.model.AbstractProject.save(AbstractProject.java:304) at hudson.plugins.disk_usage.DiskUsageProperty.setOwner(DiskUsageProperty.java:150) at hudson.model.Job.onLoad(Job.java:213) at hudson.model.AbstractProject.onLoad(AbstractProject.java:318) at hudson.maven.MavenModule.onLoad(MavenModule.java:283) at hudson.model.Items.load(Items.java:279) at hudson.model.ItemGroupMixIn.loadChildren(ItemGroupMixIn.java:108) at hudson.maven.MavenModuleSet.onLoad(MavenModuleSet.java:790) at hudson.model.Items.load(Items.java:279) at jenkins.model.Jenkins$18.run(Jenkins.java:2634) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:885) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) However, I downgrade jenkins to 1.573, the problem remains. 1.575 + maven plugin 2.5 has the same problem. Environment: Windows Server 2008 R2 Project: Jenkins Priority: Major Reporter: Pei-Tang Huang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-24206) Support for workflow plugins
Paul Allen commented on JENKINS-24206 Support for workflow plugins Added support for Run/Job in my dev branch: https://github.com/p4paul/p4-jenkins However, I have a few questions: What will be the LTS version to support Run/Job (from 1.568)? When will this LTS version be available? Is there a prefered way to support both Run/Job and AbstractProject/AbstractBuild for compatibility with older version of Jenkins? (just leave the old methods for checkout etc... or check object with instanceof) E.g. to avoid errors like: hudson.scm.SCM.checkout(Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/FilePath;Lhudson/model/BuildListener;Ljava/io/File;)Z java.lang.AbstractMethodError: hudson.scm.SCM.checkout(Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/FilePath;Lhudson/model/BuildListener;Ljava/io/File;)Z at hudson.model.AbstractProject.checkout(AbstractProject.java:1414) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:671) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:580) at hudson.model.Run.execute(Run.java:1684) at hudson.matrix.MatrixBuild.run(MatrixBuild.java:304) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43) Thanks, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [selenium] (JENKINS-23348) changes to selenium configuration under jenkins 'manager jenkins' is not saved
Semen Gabyshev commented on JENKINS-23348 changes to selenium configuration under jenkins manager jenkins is not saved Also voting for this issue. I'm trying to change 'timeout' value because some of our test steps doing their jobs more than a minute. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [slave-setup] (JENKINS-23366) jdk8u5 installation fails on windows slaves
Stefan Thurnherr commented on JENKINS-23366 jdk8u5 installation fails on windows slaves Same problem here with Jenkins v1.574 and master running on Ubuntu, and slave running on Windows7 (x64): Running our maven job with jdk8 required fails and gives the following console log: Started by user anonymous Building remotely on slave-stethu in workspace C:\Jenkins-slave\workspace\MyJob Installing JDK jdk-8u11-oth-JPR Downloading JDK from http://download.oracle.com/otn-pub/java/jdk/8u11-b12/jdk-8u11-windows-x64.exe Downloading 162831776bytes Installing C:\Jenkins-slave\tools\hudson.model.JDK\jdk8\jdk.exe [jdk8] $ C:\Jenkins-slave\tools\hudson.model.JDK\jdk8\jdk.exe /s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress INSTALLDIR=C:\Jenkins-slave\tools\hudson.model.JDK\jdk8 '/L \"C:\Jenkins-slave\tools\hudson.model.JDK\jdk8\jdk.exe.install.log\"' Failed to install JDK. Exit code=-80 ERROR: null Email was triggered for: Failure - Any Sending email for trigger: Failure - Any Installing C:\Jenkins-slave\tools\hudson.model.JDK\jdk8\jdk.exe [jdk8] $ C:\Jenkins-slave\tools\hudson.model.JDK\jdk8\jdk.exe /s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress INSTALLDIR=C:\Jenkins-slave\tools\hudson.model.JDK\jdk8 '/L \"C:\Jenkins-slave\tools\hudson.model.JDK\jdk8\jdk.exe.install.log\"' Failed to install JDK. Exit code=-80 Error retrieving environment vars: remote file operation failed: C:\Jenkins-slave\tools\hudson.model.JDK\jdk8 at hudson.remoting.Channel@77e302e6:slave-stethu Sending email to: notify...@company.com Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: FAILURE Running the same maven job with jdk7 required succeeds on the same slave: Started by user anonymous Building remotely on slave-stethu in workspace C:\Jenkins-slave\workspace\MyJob Installing JDK jdk-7u67-oth-JPR Downloading JDK from http://download.oracle.com/otn-pub/java/jdk/7u67-b01/jdk-7u67-windows-x64.exe Downloading 135998368bytes Installing C:\Jenkins-slave\tools\hudson.model.JDK\jdk7\jdk.exe [jdk7] $ C:\Jenkins-slave\tools\hudson.model.JDK\jdk7\jdk.exe /s ADDLOCAL="ToolsFeature" REBOOT=ReallySuppress INSTALLDIR=C:\Jenkins-slave\tools\hudson.model.JDK\jdk7 '/L \"C:\Jenkins-slave\tools\hudson.model.JDK\jdk7\jdk.exe.install.log\"' Cleaning local Directory trunk [...] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.1.0
Daniel Beck commented on JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.1.0 What about 1.9? Download from http://updates.jenkins-ci.org/download/plugins/mailer/ and install from Manage Plugins » Advanced. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [postbuildscript] (JENKINS-24216) executeOn is created even for non-matrix jobs when updating config with REST API
Daniel Beck commented on JENKINS-24216 executeOn is created even for non-matrix jobs when updating config with REST API Exceptions seem related to Summary Display 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] [gui] (JENKINS-24211) artifacts icons overlapping build history
Daniel Beck resolved JENKINS-24211 as Duplicate artifacts icons overlapping build history JENKINS-23829 Change By: Daniel Beck (12/Aug/14 11:35 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24196) When gzipped log contains trailing garbage, the GET on the log enters endless loop.
Daniel Beck commented on JENKINS-24196 When gzipped log contains trailing garbage, the GET on the log enters endless loop. Is there a reason you assigned this 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] [core] (JENKINS-24219) Jenkins keep forgetting my password
Daniel Beck updated JENKINS-24219 Jenkins keep forgetting my password Several plugins (and even Jenkins core) don't disable password autofill for various passwords entered in Jenkins. It's likely your browser gets confused with different passwords entered on the same site and updates your stored password with some other password. Other symptoms include you accidentally changing credentials stored on a config page when submitting it without changes. As this can result from any plugin allowing password storage, my suggestion is to remove stored password for Jenkins from your browser, make sure you get asked before it saves, and then try to find out which forms/form fields ask for passwords without setting the "do not autofill" flag (don't remember it's real name right now). Then you'll know which components to file an issue against. I'll leave this open for a bit but I'm fairly sure this is the issue as you mention manually entering the password works, and Jenkins doesn't store it your browser does. Change By: Daniel Beck (12/Aug/14 11:43 AM) Assignee: stephenconnolly Component/s: credentials This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24219) Jenkins keep forgetting my password
Daniel Beck edited a comment on JENKINS-24219 Jenkins keep forgetting my password Several plugins (and possibly even Jenkins core) don't disable password autofill for various passwords entered in Jenkins. It's likely your browser gets confused with different passwords entered on the same site and updates your stored password with some other password. Other symptoms include you accidentally changing credentials stored on a config page when submitting it without changes. As this can result from any plugin allowing password storage, my suggestion is to remove stored password for Jenkins from your browser, make sure you get asked before it saves, and then try to find out which forms/form fields ask for passwords without setting the "do not autofill" flag (don't remember it's real name right now). Then you'll know which components to file an issue against. I'll leave this open for a bit but I'm fairly sure this is the issue as you mention manually entering the password works, and Jenkins doesn't store it your browser 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] [core] (JENKINS-24221) Failed loading some of my job after upgrade to Jenkins 1.575
Daniel Beck commented on JENKINS-24221 Failed loading some of my job after upgrade to Jenkins 1.575 Did you recently update Disk Usage plugin as well? When you downgrade it, does the issue disappear? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24196) When gzipped log contains trailing garbage, the GET on the log enters endless loop.
Jaroslav Henner commented on JENKINS-24196 When gzipped log contains trailing garbage, the GET on the log enters endless loop. No. I just made a clone of the JENKINS-24171. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24196) When gzipped log contains trailing garbage, the GET on the log enters endless loop.
Jaroslav Henner updated JENKINS-24196 When gzipped log contains trailing garbage, the GET on the log enters endless loop. Change By: Jaroslav Henner (12/Aug/14 11:47 AM) Assignee: TomasWestling This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24196) When gzipped log contains trailing garbage, the GET on the log enters endless loop.
Daniel Beck updated JENKINS-24196 When gzipped log contains trailing garbage, the GET on the log enters endless loop. Change By: Daniel Beck (12/Aug/14 11:50 AM) Affects Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24196) When gzipped log contains trailing garbage, the GET on the log enters endless loop.
Daniel Beck updated JENKINS-24196 When gzipped log contains trailing garbage, the GET on the log enters endless loop. Change By: Daniel Beck (12/Aug/14 11:49 AM) Labels: performancepluginsecurity This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [artifactory] (JENKINS-24222) Release management issue with hidden files
Ian Watson created JENKINS-24222 Release management issue with hidden files Issue Type: Bug Assignee: yossis Components: artifactory, svn-release-mgr Created: 12/Aug/14 12:15 PM Description: When trying to create a tag using the Artifactory release management staging process I received the following error. Failure in post build SCM action: Subversion tag creation failed: svn: E155005: Commit failed (details follow): svn: E155005: Working copy '/var/lib/jenkins/jobs/CompileADF/workspace/AtradiusInsightsApp/.mdsExport' is missing or not locked I believe that because the .mdsExport folder is a hidden file the tool. Any ideas? Project: Jenkins Priority: Major Reporter: Ian Watson This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [artifactory] (JENKINS-24222) Release management issue with hidden files
Ian Watson updated JENKINS-24222 Release management issue with hidden files Change By: Ian Watson (12/Aug/14 12:16 PM) Description: WhentryingtocreateatagusingtheArtifactoryreleasemanagementstagingprocessIreceivedthefollowingerror.FailureinpostbuildSCMaction:Subversiontagcreationfailed:svn:E155005:Commitfailed(detailsfollow):svn:E155005:Workingcopy/var/lib/jenkins/jobs/CompileADF/workspace/AtradiusInsightsApp/.mdsExportismissingornotlockedIbelieve thatbecause thisisdueto the.mdsExportfolder is being ahiddenfilethetool.Anyideas? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [artifactory] (JENKINS-24222) Release management issue with hidden files
Ian Watson updated JENKINS-24222 Release management issue with hidden files Change By: Ian Watson (12/Aug/14 12:17 PM) Description: WhentryingtocreateatagusingtheArtifactoryreleasemanagementstagingprocessIreceivedthefollowingerror.FailureinpostbuildSCMaction:Subversiontagcreationfailed:svn:E155005:Commitfailed(detailsfollow):svn:E155005:Workingcopy/var/lib/jenkins/jobs/CompileADF/workspace/AtradiusInsightsApp/.mdsExportismissingornotlockedIbelievethisisduetothe.mdsExportfolderbeing a anempty hiddenfile iscausing the tool issue .Anyideas why ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-10102) site-deploy failed with java.io.IOException: Pipe is already closed
Aleksander Lech commented on JENKINS-10102 site-deploy failed with java.io.IOException: Pipe is already closed Hello, we have Jenkins 1.413 and copyartifacts plugin of version 1.17 and the same problem. Can you tell me which update od copy artifacts plugin can fix this? Or some workaround that works? I cannot update whole 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] [artifactory] (JENKINS-24222) Release management issue with hidden files
Ian Watson commented on JENKINS-24222 Release management issue with hidden files Possible cause - to do with the plugin is using SVN pre 1.7? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-23677) Web Server XSS filter prevents Java Warnings, Checkstyle, FindBugs and PMD icons from being displayed
Pavel Saab commented on JENKINS-23677 Web Server XSS filter prevents Java Warnings, Checkstyle, FindBugs and PMD icons from being displayed When will you make the fix available for the download? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23724) Node creation page cannot be displayed in IE 10 (normal mode)
Tom FENNELLY commented on JENKINS-23724 Node creation page cannot be displayed in IE 10 (normal mode) Henrik nice work tracking down the issue. I know Steven Christou has spent some time trying to track down the issue. This ticket is a duplicate of the earlier JENKINS-17825 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23724) Node creation page cannot be displayed in IE 10 (normal mode)
Tom FENNELLY edited a comment on JENKINS-23724 Node creation page cannot be displayed in IE 10 (normal mode) Henrik nice work tracking down the issue. I know Steven Christou has spent some time trying to track down the issue. Can you link PR please? This ticket is a duplicate of the earlier JENKINS-17825 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17825) Configure Job page makes IE10 crash down completely
Tom FENNELLY commented on JENKINS-17825 Configure Job page makes IE10 crash down completely Steven did you see the comment left by Henrik on JENKINS-23724 . Sounds like he tracked down this issue earlier and created a PR for it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-24222) Release management issue with hidden files
Ian Watson resolved JENKINS-24222 as Fixed Release management issue with hidden files Change By: Ian Watson (12/Aug/14 12:34 PM) Status: Open Resolved Assignee: yossis 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] [artifactory] (JENKINS-24222) Release management issue with hidden files
Ian Watson commented on JENKINS-24222 Release management issue with hidden files Issue resolved when using Subversion version of 1.7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-24199) Post Build trigger parameterized job does not resolve variables used for job name
ikedam resolved JENKINS-24199 as Duplicate Post Build trigger parameterized job does not resolve variables used for job name Duplicates JENKINS-11280 Change By: ikedam (12/Aug/14 12:39 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] [core] (JENKINS-23724) Node creation page cannot be displayed in IE 10 (normal mode)
Tom FENNELLY edited a comment on JENKINS-23724 Node creation page cannot be displayed in IE 10 (normal mode) Henrik nice work tracking down the issue. I know Steven Christou has spent some time trying to track down the issue. This ticket is a duplicate of the earlier JENKINS-17825 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23724) Node creation page cannot be displayed in IE 10 (normal mode)
Tom FENNELLY edited a comment on JENKINS-23724 Node creation page cannot be displayed in IE 10 (normal mode) Henrik nice work tracking down the issue. I know Steven Christou has spent some time trying to track down the issue. https://github.com/jenkinsci/jenkins/pull/1346 is the PR, correct? This ticket is a duplicate of the earlier JENKINS-17825 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17825) Configure Job page makes IE10 crash down completely
Tom FENNELLY edited a comment on JENKINS-17825 Configure Job page makes IE10 crash down completely Steven did you see the comment left by Henrik on JENKINS-23724 . Sounds like he tracked down this issue earlier and created a PR for it (https://github.com/jenkinsci/jenkins/pull/1346). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration
Joshua Sherwood commented on JENKINS-21496 Version .6.22 removes advanced options for AccuRev Servers in Global configuration I believe this was all pushed in july 2014, as part of 0.6.27 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration
Joshua Sherwood resolved JENKINS-21496 as Fixed Version .6.22 removes advanced options for AccuRev Servers in Global configuration Change By: Joshua Sherwood (12/Aug/14 12:50 PM) Status: Open Resolved Fix Version/s: current Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-trigger] (JENKINS-11280) Downstream project name is not accepting env variable/build parameters
Lorelei McCollum commented on JENKINS-11280 Downstream project name is not accepting env variable/build parameters Yes we would like this as well.. seems it works for the "Build" section but not the "Post Build" 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] [accurev] (JENKINS-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration
Walter Kacynski reopened JENKINS-21496 Version .6.22 removes advanced options for AccuRev Servers in Global configuration No, it's part of .6.27-SNAPSHOT. I needs to be re-released as .6.28 Change By: Walter Kacynski (12/Aug/14 1:03 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] [core] (JENKINS-24221) Failed loading some of my job after upgrade to Jenkins 1.575
Pei-Tang Huang resolved JENKINS-24221 as Duplicate Failed loading some of my job after upgrade to Jenkins 1.575 Duplicated to JENKINS-24182 Change By: Pei-Tang Huang (12/Aug/14 1:07 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] [core] (JENKINS-24221) Failed loading some of my job after upgrade to Jenkins 1.575
Pei-Tang Huang commented on JENKINS-24221 Failed loading some of my job after upgrade to Jenkins 1.575 Yes, we did updated a bulk of plugins from update center. The stack trace is exactly the same to JENKINS-24182, so I just resolved this issue as duplicated. Thank you! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [accurev] (JENKINS-21496) Version .6.22 removes advanced options for AccuRev Servers in Global configuration
Joshua Sherwood commented on JENKINS-21496 Version .6.22 removes advanced options for AccuRev Servers in Global configuration Hmm, that's not what I'm seeing on the WIKI, or in github (https://github.com/jenkinsci/accurev-plugin/blob/accurev-0.6.27/src/main/resources/hudson/plugins/accurev/AccurevSCM/global.jelly) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24223) Check possibility of having a single /plugin/styles.css
Tom FENNELLY created JENKINS-24223 Check possibility of having a single /plugin/styles.css Issue Type: Improvement Assignee: Tom FENNELLY Components: core Created: 12/Aug/14 1:12 PM Description: This could be a concat of style.css files from all plugins, loaded into the browser via a single request for "/plugin.styles.css". Sure... each plugin can already define and load a .css but if you have a load of plugins installed all loading css files etc etc Thinking of this wrt css based icons - plugins can define icon themes via a style.css file that they provide as part of the plugin. Project: Jenkins Labels: user-experience Priority: Minor Reporter: Tom FENNELLY This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24223) Check possibility of having a single /plugin/styles.css
Tom FENNELLY commented on JENKINS-24223 Check possibility of having a single /plugin/styles.css Playing: https://github.com/tfennelly/jenkins/compare/JENKINS-24223 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
Ryan Hummer
updated JENKINS-24202
Pin Build at Label Does not Sync at the CL of the Label
Change By:
Ryan Hummer
(12/Aug/14 1:20 PM)
Description:
WhentriggeringajobmanuallyorviaSCMPolling,theCLthejobsyncsitisnotwhatthelabelhasitsrevisionfieldsetto.Weusestaticlabelssojusttherevisionfieldistaggedforthelabel.TheSCMPollinglogcorrectlyidentifiesalltheCLsuptoandincludingtheCLthatthelabelistaggedat.SCMPollingLog:{quote}StartedonAug7,20143:18:48PMPollingSCMchangesonrsmsnbuild114P4:Pollingwithclient:rsmsnbuild114P4:Pollingwithlabel/change:latest_build_label...foundchange:978011...removingallthefoundCL#s...foundchange:978233Done.Took1min0secChangesfound{quote}LogfromJobtriggeredbytheSCMPolling:{quote}15:19:48StartedbyanSCMchange15:19:48[EnvInject]-Loadingnodeenvironmentvariables.15:19:49Buildingremotelyonrsmsnbuild116inworkspacec:\trees15:19:54SCMTask:cleanupworkspace:RSMSNBUILD11615:19:54SCMTask:syncingfilesatchange:97945215:19:54...syncc:\trees/...@97945215:19:54...forceupdatefalse15:19:54...bypasshavefalse{quote}AsyoucanseetheCLofthelabelis978233,whilethejobisactuallysyncingto979452.Whichisnot
desitred
desired
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] (JENKINS-24101) Poll Watching Label Continually Triggering
Ryan Hummer reopened JENKINS-24101 Poll Watching Label Continually Triggering This is still occurring, it may be related to JENKINS-24202 Change By: Ryan Hummer (12/Aug/14 1:22 PM) Resolution: Fixed Status: Closed 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] [remote-terminal-access] (JENKINS-24212) Remote Terminal Access Plugin doesn't work with Jenkins LTS
Daniel Beck commented on JENKINS-24212 Remote Terminal Access Plugin doesnt work with Jenkins LTS Issue is fixed on master, but no release has been created yet. If you know how, compile the plugin yourself and install that snapshot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [remote-terminal-access] (JENKINS-24212) Remote Terminal Access Plugin doesn't work with Jenkins LTS
Daniel Beck edited a comment on JENKINS-24212 Remote Terminal Access Plugin doesnt work with Jenkins LTS Issue is fixed on master, but no release has been created yet. If you know how, compile the plugin yourself and install that snapshot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24213) Jenkins slaves repeatable disconnect and connect during startup, related to remoting/nio or swarm plugin
Daniel Beck updated JENKINS-24213 Jenkins slaves repeatable disconnect and connect during startup, related to remoting/nio or swarm plugin Change By: Daniel Beck (12/Aug/14 1:33 PM) Labels: remoting This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24223) Check possibility of having a single /plugin/styles.css
Daniel Beck commented on JENKINS-24223 Check possibility of having a single /plugin/styles.css Won't a single malformed CSS potentially break a lot more that only the own style in this case? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline] (JENKINS-21181) Build pipeline creating stack trace after logging on as non-admin user
Roel Kramer commented on JENKINS-21181 Build pipeline creating stack trace after logging on as non-admin user A little difference with replies from above is that reverting "Global Security" back to "Anyone can do anything", does not help. I installed build pipeline 1.4.0, and it works again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-24223) Check possibility of having a single /plugin/styles.css
Tom FENNELLY commented on JENKINS-24223 Check possibility of having a single /plugin/styles.css Right... all the more reason to run each through a CSS pre-processor, rejecting those that cause it to barf. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23724) Node creation page cannot be displayed in IE 10 (normal mode)
Henrik Ygge commented on JENKINS-23724 Node creation page cannot be displayed in IE 10 (normal mode) Thanks! Yes, that is the pull request for the fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-24101) Poll Watching Label Continually Triggering
Paul Allen
commented on JENKINS-24101
Poll Watching Label Continually Triggering
I have looked at both of these issues and can't reproduce them in a simple environment. Freestyle + label.
I guess you have a more complex environment that is contributing to the issue. ${VAR} expansion or matrix builds or slaves. Would you consider a screen share or webex meeting to look closer at these 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] [xunit] (JENKINS-24224) improve xunit plugin with test-stability plugin
Jérôme BACHELET created JENKINS-24224 improve xunit plugin with test-stability plugin Issue Type: Improvement Affects Versions: current Assignee: Gregory Boissinot Components: xunit Created: 12/Aug/14 2:13 PM Description: Add the possibility to use test-stability plugin feature when result are published with xunit plugin Project: Jenkins Labels: plugin Priority: Minor Reporter: Jérôme BACHELET This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-24101) Poll Watching Label Continually Triggering
Ryan Hummer
commented on JENKINS-24101
Poll Watching Label Continually Triggering
The ${VAR} expansion is working. We have an extremely active P4 server. Our Jenkins environment is not overly complex. Our jobs that SCM Poll a label are just very simple freestyle jobs. All we use Jenkins/P4Jenkins for is to watch and trigger our build 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] [p4] (JENKINS-24101) Poll Watching Label Continually Triggering
Ryan Hummer
edited a comment on JENKINS-24101
Poll Watching Label Continually Triggering
The ${VAR} expansion is working. We have an extremely active P4 server. Our Jenkins environment is not overly complex. Our jobs that SCM Poll a label are just very simple freestyle jobs. All we use Jenkins/P4Jenkins for is to watch, trigger the job, sync and then run our build application.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer] (JENKINS-24225) Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure
Kong To created JENKINS-24225 Provide a stats page to display data for a given set of job(s) and period: job, rate of failure, reason for failure, category of failure Issue Type: New Feature Affects Versions: current Assignee: Tomas Westling Attachments: Build flow stats results.png Components: build-failure-analyzer Created: 12/Aug/14 2:39 PM Description: Within our organization (Ericsson), many end users show needs to display stats of builds. One team has implemented a Build stats plugin as a prototype and we see interests of such plugin. We are evaluating the capabilites of existing plugins vs requirements. We found out that BFA is responding the most to our needs. BFA is capable of storing stats into MongoDB and NodeJs (or something else) can be used to display them. However, it is also convenient to have a simple stats page to display them altogether. Only plaintext stats, dynamic charts are subject to performance issues in Jenkins. Is there any intention of adding such feature? If not, may I contribute to add that feature? Fix Versions: current Project: Jenkins Labels: BFA Stats Priority: Major Reporter: Kong To This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-24226) use credentials-plugin to define SCM credentials
Nicolas De Loof created JENKINS-24226 use credentials-plugin to define SCM credentials Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 12/Aug/14 2:42 PM Description: scm-sync-configuration has a dependency on subversion plugin as it relies on its legacy credentials support to define access to config repository. This make plugin incompatible with subversion plugin 2.X Should use credentials API to let user select credentials. Project: Jenkins Priority: Major Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [cvs] (JENKINS-23491) CVS Plugin deletes all files in workspace when Use Update is not selected
Pavel Saab reopened JENKINS-23491 CVS Plugin deletes all files in workspace when Use Update is not selected I am re-opening this issue because it's not clear why the plugin deletes everything in the workspace, instead of just the items that it checked out from CVS. I want to be able to keep certain items in my workspace, such as static analysis reports and the build.xml files, but I am forced to place those items outside of the workspace directory if "Use Update" option is not selected. Change By: Pavel Saab (12/Aug/14 2:41 PM) Resolution: WontFix Status: Closed 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] [other] (JENKINS-24227) Test Results Analyzer plugin doesn't produce anything
Jérôme BACHELET created JENKINS-24227 Test Results Analyzer plugin doesnt produce anything Issue Type: Bug Assignee: Unassigned Components: other Created: 12/Aug/14 2:43 PM Description: Test Results Analyzer plugin doesn't produce any report when I click on Get Build Report Project: Jenkins Priority: Major Reporter: Jérôme BACHELET This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-23273) RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
Tommy McNeely
commented on JENKINS-23273
RPM post-install should not do a chown -R ${JENKINS_USER:-jenkins} ${JENKINS_HOME:-/var/lib/jenkins}
@Daniel Beck:
I think you are correct. Sorry for my misunderstanding.
~tommy
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-7478) Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command
David Ruhmann assigned JENKINS-7478 to David Ruhmann Wrong EOL (UNIX type: LF) in Windows batch files executed for build steps of type Execute Windows batch command Change By: David Ruhmann (12/Aug/14 3:20 PM) Assignee: DavidRuhmann This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build on tests, claiming they're 44 years old
Sean Abbott created JENKINS-24228 maven project fails build on tests, claiming theyre 44 years old Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins_build-log Components: maven, maven2 Created: 12/Aug/14 3:22 PM Description: When building a project as a maven plugin, the weather marker and sonar plugin call the build failed, but at the end of the log it reports success. Also, when I run this build with the exact same setup and plugins, but as a freestyle project instead of a maven project, it succeeds. Environment: ubuntu 10.04 jenkins 1.573 maven 3.2.1 java 7u25 jenkins maven plugin 2.4 Project: Jenkins Priority: Major Reporter: Sean Abbott This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [postbuildscript] (JENKINS-24216) executeOn is created even for non-matrix jobs when updating config with REST API
Magnus Jacobsson commented on JENKINS-24216 executeOn is created even for non-matrix jobs when updating config with REST API I agree. The exceptions occur just by accessing the project page through web. I've spawned this to a new issue: JENKINS-24229. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gitlab-hook] (JENKINS-24230) allow build projects to be specified
Adrian Bridgett created JENKINS-24230 allow build projects to be specified Issue Type: Improvement Assignee: Unassigned Components: gitlab-hook Created: 12/Aug/14 3:28 PM Description: This is a great plugin, however we use templates and so when it searches jobs for matches it fails to find any (they are e.g. git.example.com/$NAME) I wondered if it could possibly accept job names as arguments - e.g.: https://jenkins.example.com/gitlab/build_now?jobs=foo,bar Project: Jenkins Priority: Major Reporter: Adrian Bridgett This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [artifactory] (JENKINS-23795) error connecting jenkins to artifactory
Jesus Tejedor commented on JENKINS-23795 error connecting jenkins to artifactory This problem was the same one that I had. I solved adding properly the Maven path (MAVEN_HOME) in configuration ( Manage Jenkins - Configure System - Maven - Maven Installations - MAVEN_HOME ) because I did not write properly it in first place. Maybe it is the solution for you too. Also, instead a bug maybe it is only a bad configuration. I hope this approach will help you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [summary_report] (JENKINS-24229) NPE in Summary Display Plugin
Magnus Jacobsson created JENKINS-24229 NPE in Summary Display Plugin Issue Type: Bug Assignee: Unassigned Components: summary_report Created: 12/Aug/14 3:28 PM Description: This occurs for a job that has never run (and never will since it is used as a template). aug 12, 2014 5:18:43 EM VARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: from.getReport() != null in /jenkins/view/Templates/job/SmokeTestTopTemplateJob/. Reason: java.lang.NullPointerException java.lang.NullPointerException at hudson.plugins.summary_report.ACIPluginProjectAction.getReport(ACIPluginProjectAction.java:128) at sun.reflect.GeneratedMethodAccessor331.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:622) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTNENode.value(ASTNENode.java:55) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateRecurse(ExpressionSupport.java:61) at org.apache.commons.jelly._expression_.ExpressionSupport.evaluateAsBoolean(ExpressionSupport.java:71) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] [artifactory] (JENKINS-23795) error connecting jenkins to artifactory
Jesus Tejedor edited a comment on JENKINS-23795 error connecting jenkins to artifactory This problem was the same one that I had. I solved it adding properly the Maven path (MAVEN_HOME) in configuration ( Manage Jenkins - Configure System - Maven - Maven Installations - MAVEN_HOME ) because I did not write properly it in first place. Maybe it is the solution for you too. Also, instead a bug maybe it is only a bad configuration. I hope this approach will help you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory] (JENKINS-23795) error connecting jenkins to artifactory
Jesus Tejedor edited a comment on JENKINS-23795 error connecting jenkins to artifactory This problem was the same one that I had. I solved it adding properly the Maven path (MAVEN_HOME) in configuration ( Manage Jenkins - Configure System - Maven - Maven Installations - MAVEN_HOME ) because I did not write it properly in first place. Maybe it is the solution for you too. Also, instead a bug maybe it is only a bad configuration. I hope this approach will help you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build on tests, claiming they're 44 years old
Daniel Beck commented on JENKINS-24228 maven project fails build on tests, claiming theyre 44 years old Didn't you already report 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] [job-dsl-plugin] (JENKINS-24231) Broken implementation for Workspace Cleanup Plugin
Andy Shulman
created JENKINS-24231
Broken implementation for Workspace Cleanup Plugin
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
12/Aug/14 3:37 PM
Description:
When I create a prebuild cleanup using
preBuildCleanup {
deleteCommand('sudo rm -rf %s')
}
I get the following XML block
hudson.plugins.ws__cleanup.PreBuildCleanup
patterns/patterns
deleteDirsfalse/deleteDirs
cleanupParameter/cleanupParameter
deleteCommandsudo rm -rf %s/deleteCommand
/hudson.plugins.ws__cleanup.PreBuildCleanup
However, the deleteCommand tag is wrong. It should be externalDelete. This is what I get when I configure the job directly:
hudson.plugins.ws__cleanup.PreBuildCleanup
deleteDirsfalse/deleteDirs
cleanupParameter/cleanupParameter
externalDeletesudo rm -rf %s/externalDelete
/hudson.plugins.ws__cleanup.PreBuildCleanup
This causes the plugin to not use the command specified. The postbuild cleanup gets the delete command tag right, but has several other differences:
hudson.plugins.ws__cleanup.WsCleanup
patterns/
deleteDirsfalse/deleteDirs
cleanWhenSuccesstrue/cleanWhenSuccess
cleanWhenUnstabletrue/cleanWhenUnstable
cleanWhenFailuretrue/cleanWhenFailure
cleanWhenNotBuilttrue/cleanWhenNotBuilt
cleanWhenAbortedtrue/cleanWhenAborted
notFailBuildfalse/notFailBuild
externalDeletesudo rm -rf %s/externalDelete
/hudson.plugins.ws__cleanup.WsCleanup
from the DSL, versus this block when generated directly:
hudson.plugins.ws__cleanup.WsCleanup
deleteDirsfalse/deleteDirs
skipWhenFailedfalse/skipWhenFailed
cleanWhenSuccesstrue/cleanWhenSuccess
cleanWhenUnstabletrue/cleanWhenUnstable
cleanWhenFailuretrue/cleanWhenFailure
cleanWhenNotBuilttrue/cleanWhenNotBuilt
cleanWhenAbortedtrue/cleanWhenAborted
notFailBuildfalse/notFailBuild
cleanupMatrixParentfalse/cleanupMatrixParent
externalDeletesudo rm -rf %s/externalDelete
/hudson.plugins.ws__cleanup.WsCleanup
Additionally, the documentation for "Workspace Cleanup Publisher" specifies that the Groovy command to use is "externalDeleteCommand(String)", but it is actually just "deleteCommand(String)".
Project:
Jenkins
Priority:
Major
Reporter:
Andy Shulman
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven] (JENKINS-24228) maven project fails build on tests, claiming they're 44 years old
Sean Abbott commented on JENKINS-24228 maven project fails build on tests, claiming theyre 44 years old This is the only bug report I've filed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-24200) All builds fail with E175002
System Administrator commented on JENKINS-24200 All builds fail with E175002 Bear with me, I'm figuring this out since the person who set it up left... Where is the 'full stack trace'? I have Jenkins 1.565.1 running on Windows Server 2008 R2. If I try to configure a job the Source Code Management section says: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /svn/path to Subversion repository failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2288) at hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl.doCheckCredentialsId(SubversionSCM.java:2997) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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 org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at 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
[JIRA] [cvs] (JENKINS-23491) CVS Plugin deletes all files in workspace when Use Update is not selected
Michael Clarke closed JENKINS-23491 as Wont Fix CVS Plugin deletes all files in workspace when Use Update is not selected Re-closing. The CVS plugin has always wiped out the workspace when not doing an update so ensure the workspace is in a clean state (no modified CVS control files, no non-cvs controlled files/directories etc). Since CVS has no way of reverting workspace changes (e.g. the equivalent of git clean), wiping out the workspace is the only consistent way to do this. There are no plans to change this. Change By: Michael Clarke (12/Aug/14 3:56 PM) Status: Reopened Closed Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-24200) All builds fail with E175002
System Administrator edited a comment on JENKINS-24200 All builds fail with E175002 Bear with me, I'm figuring this out since the person who set it up left... Where is the 'full stack trace'? I have Jenkins 1.565.1 running on Windows Server 2008 R2. If I try to configure a job the Source Code Management section says (despite the credentials working fine outside Jenkins): org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /svn/path to Subversion repository failed at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:388) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:373) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:361) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:707) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1020) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99) at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2288) at hudson.scm.SubversionSCM$ModuleLocation$DescriptorImpl.doCheckCredentialsId(SubversionSCM.java:2997) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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 org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:728) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at 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
[JIRA] [gitlab-hook] (JENKINS-24232) Hook fails on parametrized jobs
jsirex created JENKINS-24232 Hook fails on parametrized jobs Issue Type: Bug Assignee: Unassigned Components: gitlab-hook Created: 12/Aug/14 4:03 PM Description: Given: 1. Gitlab hooks configured and works well for few projects 2. For each project I'd created few jobs All works as expected. Step to reproduce: Add one job with GIT_BRANCH parameter (in my case I have job with choice parameter. Branch to build: $GIT_BRANCH). Note, that this job has triggered only manually, e.g. "poll scm periodically" is not configured. When Jenkins gets gitlab hook I see exception: Aug 12, 2014 6:52:38 PM org.eclipse.jetty.util.log.JavaUtilLog info INFO: TypeError - cannot convert instance of class org.jruby.RubyException to class java.lang.Throwable: org/jruby/RubyMethod.java:130:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/models/api.rb:53:in `process_projects' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/models/api.rb:24:in `POST /notify_commit' org/jruby/RubyMethod.java:118:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:1265:in `compile!' org/jruby/RubyProc.java:249:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:835:in `route!' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:851:in `route_eval' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:835:in `route!' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:872:in `process_route' org/jruby/RubyKernel.java:1174:in `catch' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:870:in `process_route' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:834:in `route!' org/jruby/RubyArray.java:1613:in `each' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:833:in `route!' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:936:in `dispatch!' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:769:in `call!' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:921:in `invoke' org/jruby/RubyKernel.java:1174:in `catch' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:921:in `invoke' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:769:in `call!' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/sinatra-1.3.3/lib/sinatra/base.rb:755:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/rack-protection-1.2.0/lib/rack/protection/path_traversal.rb:16:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/rack-protection-1.2.0/lib/rack/protection/json_csrf.rb:17:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/rack-protection-1.2.0/lib/rack/protection/base.rb:47:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/rack-protection-1.2.0/lib/rack/protection/xss_header.rb:22:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/rack-1.4.1/lib/rack/nulllogger.rb:9:in `call' /var/lib/jenkins/plugins/gitlab-hook/WEB-INF/classes/vendor/gems/gems/rack-1.4.1/lib/rack/head.rb:9:in `call'
[JIRA] [mailer] (JENKINS-24214) Test email fails with javax.mail.AuthenticationFailedException in mailer v1.1.0
James Nugent updated JENKINS-24214 Test email fails with javax.mail.AuthenticationFailedException in mailer v1.1.0 Change By: James Nugent (12/Aug/14 4:18 PM) Priority: Major Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
