[JIRA] [core] (JENKINS-15652) All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs
Christian Apel commented on JENKINS-15652 All executors dead with item.isStuck(): ArrayIndexOutOfBoundsException and more in logs We have the same issue with Jenkins 1.505 (running on Windows Server 2008 R2 Standard 64bit, deployed in a Tomcat 6 which is configured as a Windows service). In the last few days, I have found all executors dead every morning when I came into the office. This has started suddenly without any configuration changes or complex software updates, but after we have added approximately 400 further builds. Wouldn't it be an option to make the lazy loading configurable, so that this could be at least temporarily fixed? java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #6 DESC: lo=6,hi=4,size=6,size2=6 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1053) at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:434) at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:189) at hudson.model.Job.getLastBuildsOverThreshold(Job.java:877) at hudson.model.Job.getEstimatedDuration(Job.java:888) at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:320) at hudson.model.queue.MappingWorksheet.(MappingWorksheet.java:303) at hudson.model.Queue.maintain(Queue.java:1035) at hudson.model.Queue.pop(Queue.java:863) at hudson.model.Executor.grabJob(Executor.java:285) at hudson.model.Executor.run(Executor.java:206) 08.04.2013 08:41:45 hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: item.isStuck() in /jenkins/. Reason: java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #6 DESC: lo=6,hi=4,size=6,size2=6 java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #6 DESC: lo=6,hi=4,size=6,size2=6 at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432) at hudson.model.AbstractProject.getNearestOldBuild(AbstractProject.java:1053) at hudson.maven.MavenModuleSetBuild.getModuleLastBuilds(MavenModuleSetBuild.java:434) at hudson.maven.MavenModuleSetBuild.getResult(MavenModuleSetBuild.java:189) at hudson.model.Job.getLastBuildsOverThreshold(Job.java:877) at hudson.model.Job.getEstimatedDuration(Job.java:888) at hudson.model.Queue$BuildableItem.isStuck(Queue.java:1654) at sun.reflect.GeneratedMethodAccessor358.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) 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.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) 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.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java:41) 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.ChooseTag.doTag(ChooseTag.java:38) 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:98) at o
[JIRA] [integrity-plugin] (JENKINS-17292) PTC Integrity Plugin resyncs added members in 'pending-add' state
Joerg Steeg
commented on JENKINS-17292
PTC Integrity Plugin resyncs added members in 'pending-add' state
I believe this issue can be fixed easily. In class IntegritySCM change the method initializeCMProjectMembers(APISession api) accordingly:
IntegritySCM.java
private Response initializeCMProjectMembers(APISession api) throws APIException, SQLException
{
// Lets parse this project
Command siViewProjectCmd = new Command(Command.SI, "viewproject");
siViewProjectCmd.addOption(new Option("recurse"));
siViewProjectCmd.addOption(new Option("project", siProject.getConfigurationPath()));
// NEW LINES
siViewProjectCmd.addOption(new Option("filter", "!pending:add"));
siViewProjectCmd.addOption(new Option("filter", "!pending:renameto"));
// END NEW LINES
MultiValue mvFields = new MultiValue(",");
...
return viewRes;
}
We tested it locally at our site and the fix seems to work.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-17315) Nested view no longer shows unless logged in
stanislav bashkirtsev closed JENKINS-17315 as Fixed Nested view no longer shows unless logged in Change By: stanislav bashkirtsev (08/Apr/13 7:16 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-17352) Manage columns
stanislav bashkirtsev closed JENKINS-17352 as Fixed Manage columns Change By: stanislav bashkirtsev (08/Apr/13 7:15 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
stanislav bashkirtsev closed JENKINS-14546 as Duplicate Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated Change By: stanislav bashkirtsev (08/Apr/13 7:17 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-11580) nested-view plugin using wrong URL for health images
stanislav bashkirtsev closed JENKINS-11580 as Not A Defect nested-view plugin using wrong URL for health images Change By: stanislav bashkirtsev (08/Apr/13 7:17 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-9367) Access to api/json on second level view fails
stanislav bashkirtsev closed JENKINS-9367 as Fixed Access to api/json on second level view fails Change By: stanislav bashkirtsev (08/Apr/13 7:53 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17511) Option to disable "download as zip" in workspace
dotsev created JENKINS-17511 Option to disable "download as zip" in workspace Issue Type: Improvement Assignee: Unassigned Components: core Created: 08/Apr/13 7:55 AM Description: It would be great to have an option to disable "download as zip" in the workspace. For us, many users are downloading files with the "download as zip"-function bringing Jenkins under heavy load. For periodic downloads of zip-files it would be better to include creating zips into the build process and use the archive artifacts function. Environment: Jenkins ver. 1.466 LTS Project: Jenkins Priority: Major Reporter: dotsev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17443) 'connection refused by the server' causes NullPointerException
Chris Z
commented on JENKINS-17443
'connection refused by the server' causes NullPointerException
In general error handling in Subversion plugin is not on the same level as svnkit's. Currently I'm working on the externals proper handling. And new feture to fail build whenever error occurs.
For your problem this should help:
src/main/java/hudson/scm/subversion/CheckoutUpdater.java
index d6f36c3..44fb04e 100755
— a/src/main/java/hudson/scm/subversion/CheckoutUpdater.java
+++ b/src/main/java/hudson/scm/subversion/CheckoutUpdater.java
@@ -34,6 +34,7 @@ import hudson.util.StreamCopyThread;
import org.apache.commons.lang.time.FastDateFormat;
import org.kohsuke.stapler.DataBoundConstructor;
+import org.tmatesoft.svn.core.SVNErrorCode;
import org.tmatesoft.svn.core.SVNCancelException;
import org.tmatesoft.svn.core.SVNDepth;
import org.tmatesoft.svn.core.SVNException;
@@ -90,7 +91,7 @@ public class CheckoutUpdater extends WorkspaceUpdater {
listener.getLogger().println("Checking out " + location.remote + " at revision " + revisionName);
File local = new File(ws, location.getLocalDir());
SubversionUpdateEventHandler eventHandler = new SubversionUpdateEventHandler(new PrintStream(pos), externals, local, location.getLocalDir());
+SubversionUpdateEventHandler eventHandler = new SubversionUpdateEventHandler(new PrintStream(pos), externals, local, location.getLocalDir(),location.isExternalFailOption());
svnuc.setEventHandler(eventHandler);
svnuc.setExternalsHandler(eventHandler);
svnuc.setIgnoreExternals(location.isIgnoreExternalsOption());
@@ -106,8 +107,15 @@ public class CheckoutUpdater extends WorkspaceUpdater {
throw (InterruptedException)new InterruptedException().initCause(e);
}
} catch (SVNException e) {
e.printStackTrace(listener.error("Failed to check out " + location.remote));
return null;
+if(e.getErrorMessage().getErrorCode() == SVNErrorCode.CL_ERROR_PROCESSING_EXTERNALS){
+listener.getLogger().println(e.getMessage());
+listener.getLogger().println("Checkout failed due to the error in external !");
+throw (IOException) new IOException().initCause(new UpdaterException("failed to perform svn checkout", e));
+}
+else{
+e.printStackTrace(listener.error("Failed to check out " + location.remote));
+return null;
+}
} finally {
try {
pos.close();
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-17512) Throttling per category doesn't work for build flows
Jurgen Keller created JENKINS-17512 Throttling per category doesn't work for build flows Issue Type: Bug Affects Versions: current Assignee: abayer Components: throttle-concurrents Created: 08/Apr/13 9:03 AM Description: Throttling per category does not work for build flows created with the CloudBees Build Flow plugin. For two build flows I've enabled 'Throttle this project as part of one or more categories' and set both, 'Maximum Total Concurrent Builds' and 'Maximum Concurrent Builds Per Node' to 1. However, when I start both flows manually, the throttle settings seem to be ignored and the flows run in parallel. Project: Jenkins Priority: Major Reporter: Jurgen Keller This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17443) 'connection refused by the server' causes NullPointerException
Chris Z
edited a comment on JENKINS-17443
'connection refused by the server' causes NullPointerException
In general error handling in Subversion plugin is not on the same level as svnkit's. Currently I'm working on the externals proper handling. And new feture to fail build whenever error occurs.
For your problem this should help:
src/main/java/hudson/scm/subversion/CheckoutUpdater.java
index d6f36c3..44fb04e 100755
— a/src/main/java/hudson/scm/subversion/CheckoutUpdater.java
+++ b/src/main/java/hudson/scm/subversion/CheckoutUpdater.java
@@ -34,6 +34,7 @@ import hudson.util.StreamCopyThread;
import org.apache.commons.lang.time.FastDateFormat;
import org.kohsuke.stapler.DataBoundConstructor;
+import org.tmatesoft.svn.core.SVNErrorCode;
import org.tmatesoft.svn.core.SVNCancelException;
import org.tmatesoft.svn.core.SVNDepth;
import org.tmatesoft.svn.core.SVNException;
@@ -90,7 +91,7 @@ public class CheckoutUpdater extends WorkspaceUpdater {
listener.getLogger().println("Checking out " + location.remote + " at revision " + revisionName);
File local = new File(ws, location.getLocalDir());
SubversionUpdateEventHandler eventHandler = new SubversionUpdateEventHandler(new PrintStream(pos), externals, local, location.getLocalDir());
svnuc.setEventHandler(eventHandler);
svnuc.setExternalsHandler(eventHandler);
svnuc.setIgnoreExternals(location.isIgnoreExternalsOption());
@@ -106,8 +107,15 @@ public class CheckoutUpdater extends WorkspaceUpdater {
throw (InterruptedException)new InterruptedException().initCause(e);
}
} catch (SVNException e) {
e.printStackTrace(listener.error("Failed to check out " + location.remote));
return null;
+if(e.getErrorMessage().getErrorCode() == SVNErrorCode.CL_ERROR_PROCESSING_EXTERNALS){
+listener.getLogger().println(e.getMessage());
+listener.getLogger().println("Checkout failed due to the error in external !");
+throw (IOException) new IOException().initCause(new UpdaterException("failed to perform svn checkout", e));
+}
+else{
+e.printStackTrace(listener.error("Failed to check out " + location.remote));
+return null;
+}
} finally {
try {
pos.close();
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported
Christoph Moser created JENKINS-17513 For SVN only one workspaceupdater is supported Issue Type: Bug Affects Versions: current Assignee: Justin Ryan Components: job-dsl-plugin Created: 08/Apr/13 9:05 AM Description: When using SVN as SCM-tool, it is not possible to use e.a. "svnNode / workspaceUpdater(class:'hudson.scm.subversion.UpdateWithRevertUpdater')" - only the UpdateUpdater can be used. Project: Jenkins Labels: plugin jenkins scm subversion configuration Priority: Major Reporter: Christoph Moser This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17443) 'connection refused by the server' causes NullPointerException
Chris Z
edited a comment on JENKINS-17443
'connection refused by the server' causes NullPointerException
In general error handling in Subversion plugin is not on the same level as svnkit's. Currently I'm working on the externals proper handling. And new feature to fail build whenever error occurs.
For your problem this should help:
src/main/java/hudson/scm/subversion/CheckoutUpdater.java
index d6f36c3..44fb04e 100755
--- a/src/main/java/hudson/scm/subversion/CheckoutUpdater.java
+++ b/src/main/java/hudson/scm/subversion/CheckoutUpdater.java
@@ -34,6 +34,7 @@ import hudson.util.StreamCopyThread;
import org.apache.commons.lang.time.FastDateFormat;
import org.kohsuke.stapler.DataBoundConstructor;
+import org.tmatesoft.svn.core.SVNErrorCode;
import org.tmatesoft.svn.core.SVNCancelException;
import org.tmatesoft.svn.core.SVNDepth;
import org.tmatesoft.svn.core.SVNException;
@@ -90,7 +91,7 @@ public class CheckoutUpdater extends WorkspaceUpdater {
listener.getLogger().println("Checking out " + location.remote + " at revision " + revisionName);
File local = new File(ws, location.getLocalDir());
SubversionUpdateEventHandler eventHandler = new SubversionUpdateEventHandler(new PrintStream(pos), externals, local, location.getLocalDir());
svnuc.setEventHandler(eventHandler);
svnuc.setExternalsHandler(eventHandler);
svnuc.setIgnoreExternals(location.isIgnoreExternalsOption());
@@ -106,8 +107,15 @@ public class CheckoutUpdater extends WorkspaceUpdater {
throw (InterruptedException)new InterruptedException().initCause(e);
}
} catch (SVNException e) {
-e.printStackTrace(listener.error("Failed to check out " + location.remote));
-return null;
+if(e.getErrorMessage().getErrorCode() == SVNErrorCode.CL_ERROR_PROCESSING_EXTERNALS){
+listener.getLogger().println(e.getMessage());
+listener.getLogger().println("Checkout failed due to the error in external !");
+throw (IOException) new IOException().initCause(new UpdaterException("failed to perform svn checkout", e));
+}
+else{
+e.printStackTrace(listener.error("Failed to check out " + location.remote));
+return null;
+}
} finally {
try {
pos.close();
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17443) 'connection refused by the server' causes NullPointerException
Chris Z edited a comment on JENKINS-17443 'connection refused by the server' causes NullPointerException Answer deleted as it don't repairs your problem. I will try to prepare fix for that. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17382) Consider display name for sorting on main page
James Howe commented on JENKINS-17382 Consider display name for sorting on main page Applies to any view, not just the default one. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8922) Nested View Plugin: Worst Status is wrong if a failed job is disabled
stanislav bashkirtsev closed JENKINS-8922 as Fixed Nested View Plugin: Worst Status is wrong if a failed job is disabled Change By: stanislav bashkirtsev (08/Apr/13 11:36 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-7489) support geting the jobs using remote access api
stanislav bashkirtsev closed JENKINS-7489 as Fixed support geting the jobs using remote access api Change By: stanislav bashkirtsev (08/Apr/13 11:37 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-8237) Failed to add subview with regexp jobs selection
stanislav bashkirtsev closed JENKINS-8237 as Cannot Reproduce Failed to add subview with regexp jobs selection Change By: stanislav bashkirtsev (08/Apr/13 11:38 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-7904) Nested view broken since 1.379
stanislav bashkirtsev closed JENKINS-7904 as Duplicate Nested view broken since 1.379 Change By: stanislav bashkirtsev (08/Apr/13 11:38 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-7124) Add build status icon for nested view
stanislav bashkirtsev closed JENKINS-7124 as Fixed Add build status icon for nested view Change By: stanislav bashkirtsev (08/Apr/13 11:36 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-7815) Nested view not visible anymore
stanislav bashkirtsev closed JENKINS-7815 as Fixed Nested view not visible anymore Change By: stanislav bashkirtsev (08/Apr/13 11:36 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-7362) Setting Hudson default view to nested view locks access to standard views
stanislav bashkirtsev closed JENKINS-7362 as Fixed Setting Hudson default view to nested view locks access to standard views Change By: stanislav bashkirtsev (08/Apr/13 11:39 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-7862) "newView" link shows up as text instead of link
stanislav bashkirtsev closed JENKINS-7862 as Fixed "newView" link shows up as text instead of link Change By: stanislav bashkirtsev (08/Apr/13 11:39 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-7485) Missing icon "configure project" in nested view plugin
stanislav bashkirtsev closed JENKINS-7485 as Won't Fix Missing icon "configure project" in nested view plugin Change By: stanislav bashkirtsev (08/Apr/13 11:39 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-10065) Stack Trace displayed when creating a new view in a nested view
stanislav bashkirtsev closed JENKINS-10065 as Cannot Reproduce Stack Trace displayed when creating a new view in a nested view Change By: stanislav bashkirtsev (08/Apr/13 11:40 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-13429) Nested views not showing up with just read perms for View
stanislav bashkirtsev closed JENKINS-13429 as Fixed Nested views not showing up with just read perms for View Change By: stanislav bashkirtsev (08/Apr/13 11:40 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cli] (JENKINS-12302) Remote call on CLI channel from [ip] failed
Markus Hjerto closed JENKINS-12302 as Fixed Remote call on CLI channel from [ip] failed Change By: Markus Hjerto (08/Apr/13 11:56 AM) Status: Resolved Closed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
kutzi updated JENKINS-17431 500 Internal Server Error on attempt to run a build Change By: kutzi (08/Apr/13 11:59 AM) Priority: Blocker Major This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
kutzi commented on JENKINS-17431 500 Internal Server Error on attempt to run a build Why would a timestamp not be recorded on the svn server? IMO that's not possible: a revision has always also a timestamp. Can you give the full stacktrace of the error? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-4289) Hudson subversion checkout causes files to appear modified if they have no revision history
kutzi commented on JENKINS-4289 Hudson subversion checkout causes files to appear modified if they have no revision history Is this still reproducable with current versions of Jenkins and the subversion-plugin? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-4289) Hudson subversion checkout causes files to appear modified if they have no revision history
David Kocher commented on JENKINS-4289 Hudson subversion checkout causes files to appear modified if they have no revision history Reproducible here with 1.480.3 and Subversion Plugin 1.45. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Max Burdge commented on JENKINS-17248 java.lang.NullPointerException by start Also experiencing this after upgrade to 1.508 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [urlscm] (JENKINS-17479) URL SCM always marks URL as changed with Poll SCM option
Artur Szostak commented on JENKINS-17479 URL SCM always marks URL as changed with Poll SCM option I tried on a different installation of Jenkins (1.480.3 on Ubuntu) and have the same problem. Looking at the file timestamps returned by the FTP server, they do not change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Eric Anker commented on JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Suggested Fix Here: https://github.com/jenkinsci/xunit-plugin/pull/4 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Linards L commented on JENKINS-17248 java.lang.NullPointerException by start Any other plugin affected? I am prepping to upgrade from 1.494 to 1.510 this weekend ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [active-directory] (JENKINS-13058) E-mail to individuals who broke the build is sent to wrong address
Markus commented on JENKINS-13058 E-mail to individuals who broke the build is sent to wrong address We have changed the SVN server to report only "UserName", not "DomainName\UserName". This is therefore no longer a problem for us, but I'll leave this open if others experience the same problem. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17514) NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510
Ilya Lebedev created JENKINS-17514 NullPointerException: no workspace from node hudson.slaves.DumbSlave after upgrade to 1.510 Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Apr/13 1:15 PM Description: java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@17bd2 which is computer hudson.slaves.SlaveComputer@6fabefd3 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:70) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:818) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:769) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1543) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) project=hudson.maven.MavenModuleSet@233c779c[cserver-CONS-at1-job] project.getModules()=[hudson.maven.MavenModule@15e87941[cserver-CONS-at1-job/com.ctrader:xt-acceptance-tests][cserver-CONS-at1-job/com.ctrader:xt-acceptance-tests][relativePath:AcceptanceTests], hudson.maven.MavenModule@6aa0d4a3[cserver-CONS-at1-job/com.xtrader:xt-acceptance-tests][cserver-CONS-at1-job/com.xtrader:xt-acceptance-tests][relativePath:AcceptanceTests]] project.getRootModule()=hudson.maven.MavenModule@6aa0d4a3[cserver-CONS-at1-job/com.xtrader:xt-acceptance-tests][cserver-CONS-at1-job/com.xtrader:xt-acceptance-tests][relativePath:AcceptanceTests] FATAL: no workspace from node hudson.slaves.DumbSlave@17bd2 which is computer hudson.slaves.SlaveComputer@6fabefd3 and has channel null java.lang.NullPointerException: no workspace from node hudson.slaves.DumbSlave@17bd2 which is computer hudson.slaves.SlaveComputer@6fabefd3 and has channel null at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:70) at hudson.tasks.CommandInterpreter.perform(CommandInterpreter.java:60) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.build(MavenModuleSetBuild.java:818) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:769) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:592) at hudson.model.Run.execute(Run.java:1543) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:236) Environment: One master node and three slave node. All are running CentOS release 5.9 inside VM. Project: Jenkins Priority: Major Reporter: Ilya Lebedev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-iss
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-17515) HP Security Vulnerability in Password Handling
David Ehringer created JENKINS-17515 HP Security Vulnerability in Password Handling Issue Type: Bug Assignee: Ofir Shaked Components: hp-application-automation-tools-plugin Created: 08/Apr/13 1:26 PM Description: https://github.com/jenkinsci/hp-application-automation-tools-plugin/blob/master/src/main/java/com/hp/application/automation/tools/EncryptionUtils.java uses a non-secret key (the key is published on GitHub) and a static initialization vector. This renders the encryption useless. Furthermore, the exposed password is written to a text file in the build filesystem, which can be viewed directly through the Jenkins UI via file archiving. Project: Jenkins Priority: Blocker Reporter: David Ehringer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17516) "script textarea" quite annoying on Safari
Marc Günther created JENKINS-17516 "script textarea" quite annoying on Safari Issue Type: Bug Assignee: Unassigned Components: core Created: 08/Apr/13 1:51 PM Description: The "script textarea" (the one with the line numbers, as for example used in the Script Console and the scriptler plugin) has several annoying quirks (at least on Safari, didn't try on other browsers): doubleclick 'n drag to select multiple words does not work tripleclick 'n drag to select multiple lines does not work it insists on autoindenting lines by 2 characters, when you press return, even if it makes no sense at all it jumps around on every key press and mouse click (making it impossible to use the mouse at all), when you have a long line somewhere in the file, that is not currently visible. It is usually easier to copy the text into an external editor, and paste it back after editing, than using this control. Environment: Safari 6.0.3, MacOSX 10.8.3 Project: Jenkins Priority: Minor Reporter: Marc Günther This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Martin Kutter reopened JENKINS-14546 Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated The issue is not fixed in Jenkins 1.467. I'm on 1.480.3-LTS with Role Strategy plugin 1.1.2 and Nested View Plugin 1.8. We have several top-level-views, which are only shown, when a user has the (global) View.READ permission. They are not shown as tabs in the UI, but can be accesed by directly invoking the view's URL. These views are of the type "Nested View" and do not contain other jobs. This means that the "backward compatibility" trick in JENKINS-3681 does not work, when a view contains only other views (and no jobs). A user can either see all views (by means of the View.READ) permission, or only views containing Jobs. Change By: Martin Kutter (08/Apr/13 1:52 PM) Resolution: Duplicate 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/groups/opt_out.
[JIRA] [global-build-stats] (JENKINS-17248) java.lang.NullPointerException by start
Linards L edited a comment on JENKINS-17248 java.lang.NullPointerException by start Any other plugin affected? I am prepping to upgrade from 1.494 to 1.510 this weekend ... but seems like this and this (https://issues.jenkins-ci.org/browse/JENKINS-17514) is party-stopper ... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [security] (JENKINS-17510) Create an executor service wrapper class that sets the security context in each thread
Jesse Glick
updated JENKINS-17510
Create an executor service wrapper class that sets the security context in each thread
Change By:
Jesse Glick
(08/Apr/13 2:24 PM)
Description:
Initially suggested by jglick when I asked a question on the developer group https://groups.google.com/forum/?fromgroups=#!topic/jenkinsci-dev/H8gAZcDOqgc -Creates a delegating
{{
ExecutorService
}}
implementation whose submit and related methods capture the current
{{
SecurityContext
}}
and then wrap the task in a block that resets the context afterwards. Using this one could simply write:
{code}
SomeUtilityClass.wrapExecutorWithSecurity(service).submit(new Callable() { public Void call() throws Exception { Jenkins.getInstance().getItem(whatever); // should work return null; } });
{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon resolved JENKINS-17409 as Fixed looselyMatches throws exception if second parameter (repository) is null Change By: SCM/JIRA link daemon (08/Apr/13 2:41 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Code changed in jenkins User: U-ISI\jerry.maloney Path: pom.xml src/main/java/hudson/plugins/mercurial/MercurialStatus.java src/test/java/hudson/plugins/mercurial/MercurialStatusTest.java http://jenkins-ci.org/commit/mercurial-plugin/c12bfbfd24eb53760764a20a35558ef7bfcadd29 Log: [FIXED JENKINS-17409] unhandled exception in looselyMatches This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Code changed in jenkins User: U-ISI\jerry.maloney Path: src/main/java/hudson/plugins/mercurial/MercurialStatus.java http://jenkins-ci.org/commit/mercurial-plugin/0a71d81d3d205d24d3c3065ca7f693d4ea0e4b16 Log: JENKINS-17409 looselyMatches does not need to check for repository==null This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Code changed in jenkins User: U-ISI\jerry.maloney Path: pom.xml src/main/java/hudson/plugins/mercurial/MercurialStatus.java src/test/java/hudson/plugins/mercurial/MercurialStatusTest.java http://jenkins-ci.org/commit/mercurial-plugin/138dd817eea8020f3c0dddcbc21fba02799a1478 Log: [FIXED JENKINS-17409] remove extraneous dependency, slightly better flow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17409) looselyMatches throws exception if second parameter (repository) is null
SCM/JIRA link daemon commented on JENKINS-17409 looselyMatches throws exception if second parameter (repository) is null Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/mercurial/MercurialStatus.java http://jenkins-ci.org/commit/mercurial-plugin/b0abcf4403036bd1be3340469e2d29b2b9985790 Log: Merge pull request #35 from jerrymaloney/master [FIXED JENKINS-17409] looselyMatches throws exception if second parameter (repository) is null Compare: https://github.com/jenkinsci/mercurial-plugin/compare/36f762600f08...b0abcf440303 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-12032) Include SCM changes in environment variables
Christopher Orr commented on JENKINS-12032 Include SCM changes in environment variables For info, there's a workaround in this StackOverflow answer: http://stackoverflow.com/a/11837662/234938 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-16407) Android Emulator plugin does not compile with Java 7
Christopher Orr resolved JENKINS-16407 as Fixed Android Emulator plugin does not compile with Java 7 I moved the Jenkins dependency to 1.466 and now the plugin builds with Java 7. Change By: Christopher Orr (08/Apr/13 2:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
Jesse Glick reopened JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs This breaks JENKINS-15666; it was intentional to show items in folders. Change By: Jesse Glick (08/Apr/13 2:56 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/groups/opt_out.
[JIRA] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon commented on JENKINS-8614 ProcessTreeTest fails on Windows Code changed in jenkins User: Limin Wang Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/97c28e0a516a1647c3621838fb0629368c7b5873 Log: Fixed JENKINS-8614 ProcessTreeTest fails on Windows This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon commented on JENKINS-8614 ProcessTreeTest fails on Windows Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/91000fa5699c5fc7b48fcb061be9ded980aa8639 Log: Merge pull request #752 from lmwang/master [FIXED JENKINS-8614] ProcessTreeTest fails on Windows Compare: https://github.com/jenkinsci/jenkins/compare/b99a794c6ed2...91000fa5699c This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon commented on JENKINS-8614 ProcessTreeTest fails on Windows Code changed in jenkins User: limin wang Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/4709490334c2affd6b82270449daff7a6cb1e5e1 Log: [Fixed JENKINS-8614] ProcessTreeTest fails on Windows Add exception handler for getEnvironmentVariables(). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon resolved JENKINS-8614 as Fixed ProcessTreeTest fails on Windows Change By: SCM/JIRA link daemon (08/Apr/13 3:01 PM) Status: In Progress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
SCM/JIRA link daemon commented on JENKINS-8614 ProcessTreeTest fails on Windows Code changed in jenkins User: limin wang Path: core/src/main/java/hudson/util/ProcessTree.java http://jenkins-ci.org/commit/jenkins/cdc18ec56987204535c9919ea385c555d3d66863 Log: fixed JENKINS-8614 ProcessTreeTest fails on Windows This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-15666) Label.getTiedJobs ignores non-top-level jobs
SCM/JIRA link daemon commented on JENKINS-15666 Label.getTiedJobs ignores non-top-level jobs Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Label.java http://jenkins-ci.org/commit/jenkins/73bf0e5b4f1c038101e284ee8adfb56b0760addc Log: Revert "[FIXED JENKINS-17451] "projects tied to slave" shows unrelated maven module jobs. shows TopLevelItem only." This reverts commit 3a6de84f6746d54dd0f3048312db067c835ee727. (Regressed JENKINS-15666.) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-17517) Support for dynamic skins (a la JellyBean devices)
Andrew Zellman updated JENKINS-17517 Support for dynamic skins (a la JellyBean devices) Change By: Andrew Zellman (08/Apr/13 3:13 PM) Description: The Android Emulator plug-in does not expose the ability to use a dynamic skin.The problem is that newer devices do not have hardware buttons for most functionality (Home, Menu, etc.). Instead, they use a dynamic skin. This is especially true in devices running JellyBean. However, when using the Android Emulator plug-in, I have not been able to generate this type of device image.For instance, when I create an emulator using Android Virtual Device Manager, I can create it from a Device Definition. If I choose Nexus 7 by Google, I get an option to "Display a skin with hardware controls" under the "Skin:" category. This does not appear to be exposed in the Android Emulator plug-in.Upon inspection of the config.ini files in the AVD created through the GUI and the AVD created by Jenkins, I noticed the presence of skin.dynamic=yes. However, when I tried adding that as a Hardware property, I was unable to view the dynamic skin. The reason that this is a blocker for me is that I'm trying to run tests that rely on the existence of a MENU button, and I'm unable to hit that button if it does not exist. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
SCM/JIRA link daemon commented on JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/model/Label.java http://jenkins-ci.org/commit/jenkins/73bf0e5b4f1c038101e284ee8adfb56b0760addc Log: Revert "[FIXED JENKINS-17451] "projects tied to slave" shows unrelated maven module jobs. shows TopLevelItem only." This reverts commit 3a6de84f6746d54dd0f3048312db067c835ee727. (Regressed JENKINS-15666.) Conflicts: changelog.html This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [extended-choice-parameter] (JENKINS-17518) When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter
Michael Chmielewski created JENKINS-17518 When selecting multiple choices, it would be useful to choose the delimiter between choices in the build parameter Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: extended-choice-parameter Created: 08/Apr/13 3:18 PM Description: Currently the multiselect choice parameter delimits multiple selections with a comma. I have a situation where I am trying to create a staging/release package from multiple archived builds for use in an automated deployment system. I would like to use the multiselect choice parameter to select locations that the packages are going to be deployed to, and create a path structure with that information. As I do not want to necessarily create deeply nested folders, it would be nice to either declare the delimiter myself or choose from a small set of directory name safe characters (windows or linux). I think the comma delimiter should clearly be the default behavior. Environment: CentOS 6.3 Linux Project: Jenkins Priority: Major Reporter: Michael Chmielewski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ftp] (JENKINS-17165) "Publish over FTP" plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504
Alexander Fischer commented on JENKINS-17165 "Publish over FTP" plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504 I updated from Jenkins 1.497 to Jenkins 1.510. Now the only not working plugin is the "Publish over FTP"-plugin. The configuration is lost after restart of Jenkins. How can we speedup the Bugfixing? Do you need some more support? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-4289) Hudson subversion checkout causes files to appear modified if they have no revision history
kutzi commented on JENKINS-4289 Hudson subversion checkout causes files to appear modified if they have no revision history And it's easily reproducable by using $Id:$ as SVN keywords? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
Marc Günther commented on JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Isn't the problem that getAssignedLabel() of a MavenModule returns the last slave that the parent was build on (contrary to my observation above, which must have been mistaken)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
Jesse Glick commented on JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Well probably we just do not want to display a MavenModule here under any conditions, since (AFAIK) it is not possible to tie an individual module to a label, only to a module set. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported
Justin Ryan started work on JENKINS-17513 For SVN only one workspaceupdater is supported Change By: Justin Ryan (08/Apr/13 3:49 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [job-dsl-plugin] (JENKINS-17513) For SVN only one workspaceupdater is supported
Justin Ryan
commented on JENKINS-17513
For SVN only one workspaceupdater is supported
Please provide a full example of DSL code, and possibly the XML of what you're trying to accomplish in the future.
NodeEnhancement, in the context of a div ("/") will try to match an element by name and attributes. In your case, you'll have to leave off the class attribute and then override it. E.g.
def updaterNode = scmNode / workpaceUpdater
updateNode.attributes().put('class','hudson.scm.subversion.UpdateWithRevertUpdater')
It's definitely not ideal, but that should work for you.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8614) ProcessTreeTest fails on Windows
dogfood commented on JENKINS-8614 ProcessTreeTest fails on Windows Integrated in jenkins_main_trunk #2444 Fixed JENKINS-8614 ProcessTreeTest fails on Windows (Revision 97c28e0a516a1647c3621838fb0629368c7b5873) [Fixed JENKINS-8614] ProcessTreeTest fails on Windows (Revision 4709490334c2affd6b82270449daff7a6cb1e5e1) fixed JENKINS-8614 ProcessTreeTest fails on Windows (Revision cdc18ec56987204535c9919ea385c555d3d66863) Result = SUCCESS wang_limin : 97c28e0a516a1647c3621838fb0629368c7b5873 Files : core/src/main/java/hudson/util/ProcessTree.java wang_limin : 4709490334c2affd6b82270449daff7a6cb1e5e1 Files : core/src/main/java/hudson/util/ProcessTree.java wang_limin : cdc18ec56987204535c9919ea385c555d3d66863 Files : core/src/main/java/hudson/util/ProcessTree.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17451) "projects tied to slave" shows unrelated maven module jobs
dogfood commented on JENKINS-17451 "projects tied to slave" shows unrelated maven module jobs Integrated in jenkins_main_trunk #2445 Revert "[FIXED JENKINS-17451] "projects tied to slave" shows unrelated maven module jobs. shows TopLevelItem only." (Revision 73bf0e5b4f1c038101e284ee8adfb56b0760addc) Result = SUCCESS Jesse Glick : 73bf0e5b4f1c038101e284ee8adfb56b0760addc Files : changelog.html core/src/main/java/hudson/model/Label.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Steve Haworth created JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ssh-slaves Created: 08/Apr/13 5:31 PM Description: Slave nodes fail to start, Error Log shows, [04/08/13 18:22:49] [SSH] Opening SSH connection to :22. [04/08/13 18:22:53] [SSH] Authentication failed. hudson.AbortException: Authentication failed. at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:907) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:462) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:223) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) [04/08/13 18:22:53] [SSH] Connection closed. Environment: Master is a Windows 64 Bit VM with 6 Linux slave Nodes Project: Jenkins Labels: ssh Priority: Blocker Reporter: Steve Haworth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Steve Haworth commented on JENKINS-17519 After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online Note: Even rolling back the Windows VM to Jenkins v1.508 the nodes remain offline. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14749) Errors in style.css
Pedro Rodriguez assigned JENKINS-14749 to Pedro Rodriguez Errors in style.css Change By: Pedro Rodriguez (08/Apr/13 5:38 PM) Assignee: Pedro Rodriguez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-14749) Errors in style.css
Pedro Rodriguez updated JENKINS-14749 Errors in style.css Change By: Pedro Rodriguez (08/Apr/13 5:40 PM) Assignee: Pedro Rodriguez This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17422) Exceptions on start up: SEVERE: Failed Loading plugin dynamicparameter
Bruno P. Kinoshita commented on JENKINS-17422 Exceptions on start up: SEVERE: Failed Loading plugin dynamicparameter Hi, I used the wrong bug id in the commit log. Please ignore the message above. Sorry for the noise. /Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita resolved JENKINS-17442 as Fixed When connecting to TestLink, finding error ClassCastException Change By: Bruno P. Kinoshita (08/Apr/13 6:28 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Slava Maslenitsyn commented on JENKINS-17431 500 Internal Server Error on attempt to run a build thank you for responding. i see it has been changed to major from blocker... i think it should be blocker, as this problem prevents build to run... and our build engineer after we got this 500 response, ran build manually with mvn command... and build was fine. so, this tells me, that there is nothing wrong with the code, nor with subversion. and, please, let me make my point clearer. I saw the plugin code - it is very interesting and neat... however, I think in order to make a decision whether or not to run the build - you don't need to obtain the time and run svn command to see if there is any difference in the code between timestamps. 1. the difference can be found in easier way. svn -r is one of them. 2. the timestamp itself... is never reliable thing, in my opinion. there so many things affecting it, so you simply cannot rely on it. name just a few, would be: the precision you are retriving timestamp and other computer is different. the time between machines is NEVER the same. even ntpd server is synchronizing it, however, it runs periodically, plus, if nptd finds significant difference, it won't adjust time fully, being afraid to break system dependant thing, so will do it gracefuly... while your program obtains time... i can list some other things affecting timestamp... if you want to... so, my main point is do not use timestamp to calculate difference. i think would be easier and faster to calculate size of checked out space before svn update and after. ...and I am not saying that svn response on it is completely valid... 500 error actually perhaps not the best answer... but this is just a matter of how developer typed in the text in response to the error. and according to what I see in subversion code, and how I understand it - subversion could not find such timestamp in its db, so... responded... why it could not find it? could be because this time doesn't exist yet (like i said... time on the machine sending the request is running a little bit ahead of svn server), or it is being malformed somehow, or it is something else... it is not easy to process timestamps... anyway, please see below the errors: ERROR: Failed to update https://svn.xxx.com:xxx/svn/XXX org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT of '/svn/x/!XXX/default': 500 Internal Server Error (https://.com:xxx) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.getDatedRevision(DAVRepository.java:207) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:475) at org.tmatesoft.svn.core.internal.wc16.SVNBasicDelegate.getRevisionNumber(SVNBasicDelegate.java:464) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:486) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:364) at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:274) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27) at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:311) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:291) at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:387) at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:143) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:153) at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:903) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:884) at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:867) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run
[JIRA] [ssh-slaves] (JENKINS-17519) After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online
Steve Haworth closed JENKINS-17519 as Not A Defect After upgrading to Jenkins 1.510 from Jenkins 1.508 Slave Nodes will not come online After much messing around, downgrading to SSH Plug-in to 0.22 and reverting to Jenkins 1.508 and then upgrading to 1.510 and then upgrading the plug-in separately. I have managed to get it working with a user and password defined in the credentials plugin. Change By: Steve Haworth (08/Apr/13 6:31 PM) Status: Open Closed Resolution: Not A Defect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17520) xUnit check for old tests is too short
jpschewe created JENKINS-17520 xUnit check for old tests is too short Issue Type: Bug Assignee: Gregory Boissinot Components: xunit Created: 08/Apr/13 6:50 PM Description: The test for old test results is a little short. 4.1 seconds doesn't seem too old to me. 13:41:34 [xUnit] [ERROR] - Test reports were found but not all of them are new. Did all the tests run? 13:41:34 * /nfshomes/hudson/.hudson/jobs/grex-bps-geodesy/workspace/bps/geodesy-cpp/build/test/cpptestresults.xml is 4.1 sec old 13:41:34 Project: Jenkins Priority: Trivial Reporter: jpschewe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Per J. Lund
commented on JENKINS-17508
The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
I have investigated this problem further and found the following:
I have added some log to the LogRotator.java in both 1.502 and 1.510 - in the 'perform' method:
Added print-out of artifactsDir in the loop below:
if(artifactNumToKeep!=null && artifactNumToKeep!=-1) {
List> builds = job.getBuilds();
for (Run r : copy(builds.subList(Math.min(builds.size(), artifactNumToKeep), builds.size( {
LOGGER.log(INFO, "artifactsDir = {0} ", r.getArtifactsDir());
The log seen in version 1.502 is e.g:
INFO: artifactsDir = /var/lib/jenkins/jobs/PJLTEST/modules/com.corena.core$repository-management/builds/2013-04-08_20-28-13/archive
while in 1.510 it is e.g.:
INFO: artifactsDir = /var/lib/jenkins/jobs/PJLTEST/builds/2013-04-08_20-29-49/archive
This shows that it is a completely different behaviour between the two version and now artifacts will be removed as the directory seen in 1.510 does not even exist.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.
Per J. Lund assigned JENKINS-17508 to Kohsuke Kawaguchi The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503. Change By: Per J. Lund (08/Apr/13 7:07 PM) Assignee: vjuranek Kohsuke Kawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Fred Beringer commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hey Bruno, thanks for the quick fix! Need to find some time to test it this week. Happy to have influenced you one way or another But you're doing the real work here for the software testing community, so thanks for this! Fred This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.
Michael Marcil created JENKINS-17521 javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. Issue Type: Bug Affects Versions: current Assignee: redsolo Components: nunit Created: 08/Apr/13 7:13 PM Description: I have a .NET DLL which contains tests that run with NUnit 2.5 When a crash happens, the XML is malformed and the plugin crashes. I know the test should be fixed, but would it be possible for the plugin to not crash or filter the XML so that the failing test displays a generic error message in the final report. There's the call stack : -- hudson.util.IOException2: remote file operation failed: *** at hudson.remoting.Channel@* at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:102) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:739) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: hudson.util.IOException2: Could not transform the NUnit report. Please report this issue to the plugin author at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:57) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:26) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Caused by: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at hudson.plugins.nunit.NUnitReportTransformer.transform(NUnitReportTransformer.java:67) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:55) ... 12 more Caused by: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getDOM(Unknown Source) ... 16 more Caused by: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source) ... 17 more -- Part of the failing test output that is obviously causing the error : ydü> H† cÔ@?ˆ Ô¯ @v& @v& ? '?«C-äD|ªÔ¯ '?¶xŠï?;Ï’<Òš“÷[·ƒk>' ?…Ï <…6¤Ö c?…Ï ?…Ï @v& Ô¯ ?ÔÏ X…6 cäD?T`…6�& c\…6 >' Ô¯ |…6¤Ö cÔ¯ Ô¯ @v& _c"m,) co…6Ô¯ @†' �ƒ6ÞR‰Ts?
[JIRA] [nunit] (JENKINS-17521) javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section.
Michael Marcil updated JENKINS-17521 javax.xml.transform.TransformerException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. Change By: Michael Marcil (08/Apr/13 7:14 PM) Description: I have a .NET DLL which contains tests that run with NUnit 2.5When a crash happens, the XML is malformed and the plugin crashes.I know the test should be fixed, but would it be possible for the plugin to not crash or filter the XML so that the failing test displays a generic error message in the final report.There's the call stack :--hudson.util.IOException2: remote file operation failed: *** at hudson.remoting.Channel@* at hudson.FilePath.act(FilePath.java:861) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.nunit.NUnitPublisher.perform(NUnitPublisher.java:102) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:739) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237)Caused by: hudson.util.IOException2: Could not transform the NUnit report. Please report this issue to the plugin author at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:57) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:26) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2348) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source)Caused by: javax.xml.transform.TransformerException: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.transform(Unknown Source) at hudson.plugins.nunit.NUnitReportTransformer.transform(NUnitReportTransformer.java:67) at hudson.plugins.nunit.NUnitArchiver.invoke(NUnitArchiver.java:55) ... 12 moreCaused by: javax.xml.transform.TransformerException: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl.getDOM(Unknown Source) ... 16 moreCaused by: com.sun.org.apache.xml.internal.utils.WrappedRuntimeException: An invalid XML character (Unicode: 0x0) was found in the CDATA section. at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source) at com.sun.org.apache.xalan.internal.xsltc.dom.XSLTCDTMManager.getDTM(Unknown Source) ... 17 more--Part of the failing test output that is obviously causing the error :ydü> H† cÔ @?ˆ Ô¯ @v& @v& ? '?«C-äD|ªÔ¯ '?¶xŠï?;Ï’<Òš“÷[ ·ƒk>' ?…Ï <…6¤Ö c?…Ï ?…Ï @v& Ô¯ ?ÔÏ X…6 cäD?T`…6�& c\…6 >' Ô¯ |…6¤Ö cÔ¯ Ô¯ @v& _c"m,) co…6Ô¯ @†' �ƒ6ÞR‰ Ts? 6 …â� ·…6œb"mD®< 6Ñ…6BMO 69?O 6ÿ ‰ ÞR‰ Q?O ÿ ‰ 8†6@ › 6„1? › 6$ 6 „„6 2? @185** Thanks Thank you This message is automatically generated by JIRA.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita edited a comment on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hello @Supratim, Sorry for the delay. I've been busy with other project/plug-ins and couldn't find a cycle to work on Jenkins, TestLink or on this plug-in. Sorry. Since last Wednesday I've been working on these tools, but first I had to release a 1.9.4 testlink-java-api version. Yesterday I released another version of the testlink-java-api, 1.9.5-0. Now I'm working on these issues for 1.9.5/1.9.6. Thanks for confirming this issue @Fred. I'll take a look on this. Looks like a simple mismatch between the parameters of the testlink-java-api used by the plug-in, and TestLink. BTW, let me say that today I'm extremely happy, to receive a comment in this plug-in by you. When I wrote this plug-in, the initial version, was highly influenced by your blog entries. I was working on a telecom company, as QA engineer for the first time, and faced the need to integrate my CI jobs with the Test Management team. Not knowing much about test management, your blog was one of the most important resources. So, thank you very much!!! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-17522) Ability to start emulator only if Android build succeeds
Austyn Mahoney created JENKINS-17522 Ability to start emulator only if Android build succeeds Issue Type: New Feature Assignee: Christopher Orr Components: android-emulator Created: 08/Apr/13 7:21 PM Description: Waiting for the emulator to start should not be a requirement for an Ant build to start. On a server where you are forced to use the ARM emulator, it can be up to 3-5 minutes before your build even starts. The build can then fail, rendering the emulator useless for this particular build, and wasting 3-5 minutes of build time. Project: Jenkins Priority: Major Reporter: Austyn Mahoney This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException
Bruno P. Kinoshita commented on JENKINS-17442 When connecting to TestLink, finding error ClassCastException Hi Fred. I'll cut a new release with this fix included tomorrow, but it takes a few hours for the backend infrastructure to update the Jenkins update site. Let me know if you need anything in the meantime. Thanks! Bruno This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [parameterized-trigger] (JENKINS-17523) Gradle build parameter are not supplied correctly - Parameterized-trigger plugin
Jérémie Charest
created JENKINS-17523
Gradle build parameter are not supplied correctly - Parameterized-trigger plugin
Issue Type:
Bug
Assignee:
huybrechts
Components:
parameterized-trigger
Created:
08/Apr/13 7:24 PM
Description:
When using the "trigger other jobs" feature, build parameters are not send correctly to Gradle jobs.
The plugin format arguments by adding a -Dxxx which is an Ant syntax. In Gradle, build arguments follow -Pxxx syntax.
Example :
Predefined parameters : release=${release}
Job call (console output) : \gradle -Drelease=true
Should be : \gradle -Prelease=true
Environment:
Windows Server 2008 R2
parameterized-trigger v2.17
Jenkins v1.486
Project:
Jenkins
Labels:
plugin
gradle
Priority:
Minor
Reporter:
Jérémie Charest
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-17376) BZR Environment Variables
Alexandre Garnier updated JENKINS-17376 BZR Environment Variables Change By: Alexandre Garnier (08/Apr/13 7:35 PM) Description: When a Jenkins job executes, it sets some environment variables. It would be nice if BZR variables were available. I saw that BZR_REV--NO-+ID+ and BZR_REVISION are available, but it doesn't look like they currently work.I would also like to requestBZR_AUTHOR or BZR_COMMITER BZR_COMMITTER BZR_MESSAGEWould these be possible to implement? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [thinBackup] (JENKINS-17475) Backup stops when processing some file like 'latestfailedbuild'
Thomas Fürer commented on JENKINS-17475 Backup stops when processing some file like 'latestfailedbuild' unfortently the fix I have done is not working on all supported OS and also I have to search for some compatibility mode to older jenkins versions than 1.507. therfore it takes a little bit longer to fix this problem. stay tuned I'm working on it... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [other] (JENKINS-1948) intermittent: fails to remove temporary file on remote.
Erik Purins commented on JENKINS-1948 intermittent: fails to remove temporary file on remote. This is still occurring 1.504 debian squeeze master, osx 10.8 slave. If it's related to an unreliable connection and is this frequent, maybe a better error message (instead of the entire remote action callstack) or more fault-tolerent remote action retry system could be implemented? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
Erik Purins commented on JENKINS-12235 FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel We still get this from time to time with debian squeeze master 1.504 jenkins, osx 10.8 client. It would be nice to resolve this, or at least handle this common error, with less stack trace, more human-readable text. Alternately, it would be nice if we could have a more fault-tolerant delete temporary file command, that either retries or schedules a cleanup of the temp file when it can. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
SCM/JIRA link daemon commented on JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Code changed in jenkins User: bobtheshrew Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java http://jenkins-ci.org/commit/xunit-plugin/a7352df6dfb5b7e418fc2ea258c0ef1e6b67f689 Log: Fix for JENKINS-17438 Updated getXUnitToolInfoObject() to include: * BuildListener parameter * Use Util.replaceMacro() to expand CustomXSL string Updated performTests() call to getXUnitToolInfoObject() to include BuildListener parameter * Searched rest of the code, this seems to be the only call of getXUnitToolInfoObject() Addresses Bug: https://issues.jenkins-ci.org/browse/JENKINS-17438 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
SCM/JIRA link daemon commented on JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Code changed in jenkins User: Gregory Boissinot Path: src/main/java/org/jenkinsci/plugins/xunit/XUnitPublisher.java http://jenkins-ci.org/commit/xunit-plugin/6f0d4a8a6445ac66a07325acc3e778f895e4b576 Log: Merge pull request #4 from bobtheshrew/patch-1 Fix for JENKINS-17438 Compare: https://github.com/jenkinsci/xunit-plugin/compare/9bfb2611775b...6f0d4a8a6445 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Gregory Boissinot resolved JENKINS-17438 as Fixed xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Change By: Gregory Boissinot (08/Apr/13 7:58 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-17376) BZR Environment Variables
Alexandre Garnier commented on JENKINS-17376 BZR Environment Variables Does it make sense to add these variables? A build does not necessarily build only one commit and then there are multiple committers and messages. It is possible to do it, but is the last or first commit the more relevant? The solution I think of would not populate these variables in case of build without new commit (launched by a user or other build). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [nested-view] (JENKINS-17524) NPE when renaming job in My Views
David Ishee created JENKINS-17524 NPE when renaming job in My Views Issue Type: Bug Assignee: Unassigned Components: nested-view Created: 08/Apr/13 8:14 PM Description: I have the Nested View plugin installed. I was working in a nested view under my personal "My Views" tab. I renamed a job and got the following exception. The job does get renamed, but it disappears from the View it was in. I have to manually add it back to the view. It doesn't seem to do this on normal views outside "My Views". Status Code: 500 Exception: java.lang.NullPointerException Stacktrace: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:659) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:488) at org.kohsuke.stapler.Stapler.service(Stapler.java:162) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:173) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
[JIRA] [bazaar] (JENKINS-17376) BZR Environment Variables
Alexandre Garnier commented on JENKINS-17376 BZR Environment Variables A possible solution : bazaar-plugin@JENKINS-17376 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-13478) Redmine repository browser support should work in Bazaar and Mercurial
Alexandre Garnier closed JENKINS-13478 as Duplicate Redmine repository browser support should work in Bazaar and Mercurial Change By: Alexandre Garnier (08/Apr/13 8:40 PM) Status: Open Closed Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17520) xUnit check for old tests is too short
Gregory Boissinot started work on JENKINS-17520 xUnit check for old tests is too short Change By: Gregory Boissinot (08/Apr/13 8:59 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17520) xUnit check for old tests is too short
Gregory Boissinot commented on JENKINS-17520 xUnit check for old tests is too short At the moment, the plugin expects that the last modified date of test results were updated at build time (created by the plugin or the touch command is applied for example). The plugin tests that the test reports last modified date is inferior to 3 s. What is your build time? Moreover, you are able to check an option in the configuration to not activate this check. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17525) XUnit plugin fails to convert all tests to JUnit file.
Ben Vaughan created JENKINS-17525 XUnit plugin fails to convert all tests to JUnit file. Issue Type: Bug Affects Versions: current Assignee: Gregory Boissinot Attachments: SomeProject.Contracts.Tests.dll.xml Components: xunit Created: 08/Apr/13 9:03 PM Description: Some of our XUnit files are not fully converting to JUnit files. In the attached XUnit file all of the test suites show up except: SomeProject.Contracts.Tests.CustomerTests SomeProject.Contracts.Tests.DestinationTests These test suites both make extensive use of the xUnit "Theory" attribute which involves the writing out of test parameters into the test name. I guess is that the the xUnit -> jUnit converter is failing to parse test names correctly if they contain the " marker in them. Environment: v1.5.3 XUnit Plugin Fix Versions: current Project: Jenkins Labels: plugin Priority: Minor Reporter: Ben Vaughan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xunit] (JENKINS-17520) xUnit check for old tests is too short
jpschewe commented on JENKINS-17520 xUnit check for old tests is too short The time at the top of the job is Apr 8, 2013 1:40:36 PM. This particular build took 59 seconds. I found the checkbox, that's why I marked this trival for priority. I'm able to work around this by checking the box. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
