[JIRA] [plugin] (JENKINS-17711) Digest mismatch in update center for LTS 1.480.3

2013-04-22 Thread plescanstanis...@gmail.com (JIRA) 














































Potroshitel Jack
 created  JENKINS-17711


Digest mismatch in update center for LTS 1.480.3















Issue Type:


Bug



Assignee:


Unassigned


Components:


plugin, update-center



Created:


23/Apr/13 6:57 AM



Description:


I encountered an issue that seems that should be fixed since i saw it appear in JIRA a couple of times before.
When installing a fresh Jenkins LTS 1.480.3 release on Windows Server 2008 R2 x64 I can't find any plugins in "Available" and "Updates" tabs.
I receive the following error:
Apr 19, 2013 1:34:59 AM hudson.model.UpdateSite doPostBack
SEVERE: Digest mismatch: 1Woxyt3oLgioZax7SGlbwYITc98= vs +JLZbigPye2eA9Fsv6sa3DW3q2s= in update center 'default'
I have tried the latest Jenkins version and I don't receive this issue. The thing is - i want to go with the LTS version since i'm installing it on a PROD environment.




Environment:


Windows Server 2008 R2 x64 with latest updates (or without them)




Project:


Jenkins



Priority:


Major



Reporter:


Potroshitel Jack

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [update-center] (JENKINS-17677) Digest mismatch in update center for LTS 1.480.3

2013-04-22 Thread plescanstanis...@gmail.com (JIRA) 














































Potroshitel Jack
 updated  JENKINS-17677


Digest mismatch in update center for LTS 1.480.3
















Change By:


Potroshitel Jack
(23/Apr/13 6:51 AM)




Fix Version/s:


current



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [git] (JENKINS-17710) Windows: Using Shallow Clone cause a git fatal error - pack has 1 unresolved delta (index-pack failed)

2013-04-22 Thread dorons...@gmail.com (JIRA) 














































Doron Shai
 created  JENKINS-17710


Windows: Using Shallow Clone cause a git fatal error - pack has 1 unresolved delta (index-pack failed)















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git



Created:


23/Apr/13 5:29 AM



Description:


When i use the Shallow clone option in a Job that use the git plugin, i get the following Error:

ERROR: Problem fetching from origin / origin - could be unavailable. Continuing anyway
hudson.plugins.git.GitException: Command "C:\Program Files (x86)\Git\bin\git.exe fetch -t origin +refs/heads/:refs/remotes/origin/" returned status code 128:
stdout: 
stderr: fatal: pack has 1 unresolved delta
fatal: index-pack failed

removing the shallow clone option and then everything works good.




Environment:


Git Plugin 1.3.0, Jenkins 1.505, Windows 2008




Project:


Jenkins



Labels:


git




Priority:


Major



Reporter:


Doron Shai

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [repository] (JENKINS-17709) Expose artifacts from non-maven jobs too

2013-04-22 Thread jenkin...@mailinator.com (JIRA) 














































a b
 created  JENKINS-17709


Expose artifacts from non-maven jobs too















Issue Type:


New Feature



Assignee:


magnayn



Components:


repository



Created:


23/Apr/13 4:56 AM



Description:


There are other types of projects besides maven projects whose artifacts get published in maven repos; two examples are grails plugins and projects using Ivy. Also, maven projects are not always built using Jenkins Maven jobs. Therefore it would be really nice to be able to expose the artifacts from any type of job (in my case Freestyle jobs), as long as it provides a pom.xml (the location of which should probably be configurable).




Project:


Jenkins



Priority:


Major



Reporter:


a b

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [openid] (JENKINS-17499) OpenID plugin is using cryptic URL as the user ID with me.yahoo.com

2013-04-22 Thread br...@tangent.org (JIRA) 














































Brian Aker
 commented on  JENKINS-17499


OpenID plugin is using cryptic URL as the user ID with me.yahoo.com















It looks like a change in the way launchpad was handling openid triggered this (which... it turns out that the launchpad openid server is the same as the ubuntu one).

I was surprised to find that the URL returned by the openid server was inserted as the username in each page.






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [scriptler] (JENKINS-17708) Expose scriptler scripts via token macro token

2013-04-22 Thread slide.o....@gmail.com (JIRA) 














































Alex Earl
 created  JENKINS-17708


Expose scriptler scripts via token macro token















Issue Type:


Bug



Assignee:


domi



Components:


scriptler



Created:


23/Apr/13 4:43 AM



Description:


It would be nice to be able to store scripts in Scriptler and then use them in places that can consume Token Macro's. 




Project:


Jenkins



Priority:


Minor



Reporter:


Alex Earl

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-14551) an update which contains added files merged from a branch results in those files having doubled content

2013-04-22 Thread kay...@blizzard.com (JIRA) 














































Kenny Ayers
 commented on  JENKINS-14551


an update which contains added files merged from a branch results in those files having doubled content















I've posted a bug report to the SVNKit issue tracker, hopefully this will get some attention: http://issues.tmatesoft.com/issue/SVNKIT-368



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-14551) an update which contains added files merged from a branch results in those files having doubled content

2013-04-22 Thread kay...@blizzard.com (JIRA) 














































Kenny Ayers
 commented on  JENKINS-14551


an update which contains added files merged from a branch results in those files having doubled content















This bug may be in SVNKit, which is the Java library that subversion-plugin uses.  I determined this by modifying hudson.scm.subversion.UpdateUpdater by adding a loop to print the contents of each file after the SVN checkout is completed.  Immediately after the doUpdate() function which is responsible for updating a checkout is called, I inspect the file contents to find they are corrupted.

Here's the git patch to hudson.scm.subversion.UpdateUpdater with the debug output.  Please note I'm not a Java developer by trade, and this code has cruft from a lot of debugging iterations.  I've also modified the parameters being used by doUpdate() as part of the debugging process:


diff --git a/src/main/java/hudson/scm/subversion/UpdateUpdater.java b/src/main/java/hudson/scm/subversion/UpdateUpdater.java
index f00ebdb..021e18c 100755
--- a/src/main/java/hudson/scm/subversion/UpdateUpdater.java
+++ b/src/main/java/hudson/scm/subversion/UpdateUpdater.java
@@ -40,11 +40,21 @@ import org.tmatesoft.svn.core.wc.SVNInfo;
 import org.tmatesoft.svn.core.wc.SVNRevision;
 import org.tmatesoft.svn.core.wc.SVNUpdateClient;
 import org.tmatesoft.svn.core.wc.SVNWCClient;
+import org.tmatesoft.svn.core.wc.SVNClientManager;
+import org.tmatesoft.svn.core.SVNDepth;
+import org.tmatesoft.svn.core.wc.SVNRevision;
 
 import java.io.File;
 import java.io.IOException;
 import java.util.ArrayList;
+import java.util.Arrays;
 import java.util.List;
+import java.io.InputStream;
+import java.io.BufferedInputStream;
+import java.io.FileInputStream;
+import java.io.DataInputStream;
+import java.io.InputStreamReader;
+import java.io.BufferedReader;
 
 /**
  * {@link WorkspaceUpdater} that uses "svn update" as much as possible.
@@ -154,7 +164,38 @@ public class UpdateUpdater extends WorkspaceUpdater {
 switch (svnCommand) {
 case UPDATE:
 listener.getLogger().println("Updating " + location.remote + " at revision " + revisionName);
-svnuc.doUpdate(local.getCanonicalFile(), r, svnDepth, true, true);
+//svnuc.doUpdate(local.getCanonicalFile(), r, svnDepth, true, true);
+SVNClientManager cM = SVNClientManager.newInstance();
+SVNUpdateClient updateClient = cM.getUpdateClient();
+updateClient.doUpdate(local.getCanonicalFile(), SVNRevision.HEAD, SVNDepth.INFINITY, true, true);
+
+ArrayList files = new ArrayList(Arrays.asList(local.listFiles()));
+for (int i = 0; i < files.size(); i++)
+{
+if (files.get(i).isFile())
+{
+String fname = files.get(i).getName();
+listener.getLogger().println("File: " + fname);
+try{
+  // Open the file that is the first 
+  // command line parameter
+  FileInputStream fstream = new FileInputStream(files.get(i));
+  // Get the object of DataInputStream
+  DataInputStream in = new DataInputStream(fstream);
+  BufferedReader br = new BufferedReader(new InputStreamReader(in));
+  String strLine;
+  //Read File Line By Line
+  while ((strLine = br.readLine()) != null)   {
+  // Print the content on the console
+  listener.getLogger().println(strLine);
+  }
+  //Close the input stream
+  in.close();
+}catch (Exception e){//Catch exception if any
+  listener.getLogger().println("Error: " + e.getMessage());
+  }
+}
+}
 break;
 case SWITCH:
 listener.getLogger().println("Switching to " + location.remote + " at revision " + revisionName);

[JIRA] [active-directory] (JENKINS-17676) ADSI mode auth no longer working after update to AD plugin v 1.31

2013-04-22 Thread jaeic...@gmail.com (JIRA) 














































Jason Eick
 commented on  JENKINS-17676


ADSI mode auth no longer working after update to AD plugin v 1.31















This is a blocker for me as well. Look forward to it quickly getting resolved.

Jenkins: 1.512
ActiveDirectory: 1.31



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [openid] (JENKINS-17499) OpenID plugin is using cryptic URL as the user ID with me.yahoo.com

2013-04-22 Thread br...@tangent.org (JIRA) 














































Brian Aker
 commented on  JENKINS-17499


OpenID plugin is using cryptic URL as the user ID with me.yahoo.com















BTW if this helps... when it asks to authenticate I don't think it is requesting the username be sent back.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [openid] (JENKINS-17499) OpenID plugin is using cryptic URL as the user ID with me.yahoo.com

2013-04-22 Thread br...@tangent.org (JIRA) 














































Brian Aker
 commented on  JENKINS-17499


OpenID plugin is using cryptic URL as the user ID with me.yahoo.com















This just started showing up today for us. We use launchpad.net as our provider.

The bad news about this bug is that it locked us out of the Jenkins instance which... we are now trying to figure out what we need to do since this is our authentication method.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-13079) memory error watching console of a verbose job (20M log)

2013-04-22 Thread ever...@free.fr (JIRA) 















































evernat
 resolved  JENKINS-13079 as Cannot Reproduce


memory error watching console of a verbose job (20M log) 
















Ok, thanks.
So resolving as can not reproduced.
The main cause may have been setting the PermGen.





Change By:


evernat
(22/Apr/13 11:00 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-13079) memory error watching console of a verbose job (20M log)

2013-04-22 Thread monc...@raytheon.com (JIRA) 














































Greg Moncreaff
 commented on  JENKINS-13079


memory error watching console of a verbose job (20M log) 















I no longer have the enviornment that produced this available to me...



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [core] (JENKINS-17707) Mark slave offline when fail to create temp file

2013-04-22 Thread nicolas.del...@gmail.com (JIRA) 














































Nicolas De Loof
 created  JENKINS-17707


Mark slave offline when fail to create temp file















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


22/Apr/13 8:43 PM



Description:


As Jenkins fails to create a temp file running a script, it should mark the slave as offline to avoid subsequent errors, as it already does for full filesystem




Project:


Jenkins



Priority:


Major



Reporter:


Nicolas De Loof

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [core] (JENKINS-17526) Broken CSS when reloading Jenkins after a time of inactivity

2013-04-22 Thread vondiefinster...@gmail.com (JIRA) 














































Pedro Rodriguez
 updated  JENKINS-17526


Broken CSS when reloading Jenkins after a time of inactivity
















Change By:


Pedro Rodriguez
(22/Apr/13 7:44 PM)




Priority:


Minor
Major



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [core] (JENKINS-17706) [core] “Execute Windows batch command” incorrectly switches to workspace with UNC path

2013-04-22 Thread o.v.nenas...@gmail.com (JIRA) 














































Oleg Nenashev
 created  JENKINS-17706


[core] “Execute Windows batch command” incorrectly switches to workspace with UNC path















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


22/Apr/13 7:36 PM



Description:


Hello,

We have several Win7 nodes, which use workspaces at unmapped shared directories (we use UNC path at slave configuration). For those nodes, “Execute Windows batch command” build step incorrectly changes working directory before execution of script (see log below). Unfortunately, cmd only prints warning to console and then executes script in Windows directory.

It would be great to add UNC path check before script executtion(even if it fails the build). For example, in case of admin rights flushing of working directory from “Execute Windows batch command” could cause… unexpected results

I propose to add check of working directory path at hudson::tasks::BatchFile::getContents(). If working directory has UNC format, it is possible to extend script content by pushd/popd wrapper (see http://superuser.com/questions/282963/can-you-browse-a-unc-path-using-a-command-line-environment-without-mapping-it-to). 

Log:

Started by user Oleg Nenashev
  [EnvInject] - Loading node environment variables.
  Building remotely on ${MY_NODE} in workspace ${NODE_WORKSPACE}
  [Test_BatchOnSharedWorkspace] $ cmd /c call C:\Users\${MY_USER} \AppData \Local\Temp\hudson1138943559754710435.bat
  '${NODE_WORKSPACE}’
  CMD.EXE was started with the above path as the current directory.
  UNC paths are not supported.  Defaulting to Windows directory.

  C:\Windows>dir
Volume in drive C is System
Volume Serial Number is ${MY_SN}

Directory of C:\Windows




Environment:


Windows slaves, UNC path to workspace at slave




Project:


Jenkins



Priority:


Major



Reporter:


Oleg Nenashev

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17526) Broken CSS when reloading Jenkins after a time of inactivity

2013-04-22 Thread prest...@gmail.com (JIRA) 














































Preston Jennings
 commented on  JENKINS-17526


Broken CSS when reloading Jenkins after a time of inactivity















+1 for this issue appearing in 1.480.3 LTS. I installed the build via a debian package (ubuntu linux OS).

My feeling is that this issue should have a higher priority than minor as it gives the impression that the 1.480.3 "LTS" build is unpolished. However as noted above, using shift + refresh does make the problem go away.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [maven] (JENKINS-17402) Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact

2013-04-22 Thread jhu...@java.net (JIRA) 














































jhurne
 commented on  JENKINS-17402


Failed to instantiate class hudson.plugins.copyartifact.CopyArtifact















Is there a workaround for this problem (maybe using the Jenkins console or REST API)?  No matter what I do, I cannot get the Config GUI to allow me to set the project name.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

2013-04-22 Thread jhans...@meetme.com (JIRA) 












































  
Joe Hansche
 edited a comment on  JENKINS-17693


Confluence Publisher for Confluence 5x
















Interesting...  I see two potential issues here:


	The SSL exception seems to imply that your Confluence instance is requiring HTTPS, but the certificate can't be validated by the Jenkins server. Is your instance accessible via non-SSL (http:// only)?
	
		If your server allows that, what happens if you change the URL in the Jenkins system configuration to remove the https requirement?
		If your server requires HTTPS, then it will likely require importing the SSL certificate from the Confluence server into the Jenkins server's JVM. I've had to do this a couple times in the past, particularly with newer Certificate Authorities that weren't available (or weren't widely popular) at the time the JVM you use was released.  If this is what's required, I will look up instructions for importing that certificate and see if it helps.  On a side note, how many Jenkins servers are in your cluster?  Because I believe all servers (master and slaves) will need to have the certificate imported in order to support this.
	
	
	It sounds like your Confluence instance does not have the remote APIs enabled, based on the "There is no SOAP service at this location" error.
	
		Can you try these steps to enable the SOAP API?  https://confluence.atlassian.com/display/DOC/Enabling+the+Remote+API
	
	





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [trayapp] (JENKINS-1697) FileExecutor defines equals() but not hashCode()

2013-04-22 Thread scm_issue_l...@java.net (JIRA) 














































SCM/JIRA link daemon
 commented on  JENKINS-1697


FileExecutor defines equals() but not hashCode()















Code changed in jenkins
User: David
Path:
 .gitignore
 client-common/src/main/java/org/hudson/trayapp/HudsonTrayApp.java
 client-common/src/main/java/org/hudson/trayapp/actions/FileExecutor.java
http://jenkins-ci.org/commit/hudsontrayapp-plugin/ec008f5e39bbf6857970156dd0f9dfb62920c52e
Log:
  JENKINS-1697 - Adding hashCode method, also fixing a typo in the TrayIcon exception handling, and adding gitignore






























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [trayapp] (JENKINS-1694) Server.isHudsonBuild173orGreater() bug

2013-04-22 Thread davyboyha...@java.net (JIRA) 















































davyboyhayes
 resolved  JENKINS-1694 as Cannot Reproduce


Server.isHudsonBuild173orGreater() bug
















This appears to have already been fixed.





Change By:


davyboyhayes
(22/Apr/13 6:05 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [trayapp] (JENKINS-1697) FileExecutor defines equals() but not hashCode()

2013-04-22 Thread davyboyha...@java.net (JIRA) 















































davyboyhayes
 resolved  JENKINS-1697 as Fixed


FileExecutor defines equals() but not hashCode()
















Change By:


davyboyhayes
(22/Apr/13 6: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] [trayapp] (JENKINS-1697) FileExecutor defines equals() but not hashCode()

2013-04-22 Thread davyboyha...@java.net (JIRA) 














































davyboyhayes
 commented on  JENKINS-1697


FileExecutor defines equals() but not hashCode()















Committed openticketsapril2013 branch commit: ec008f5



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-8052) "No changes" shown after change found but before sync completed

2013-04-22 Thread rob.pe...@gmail.com (JIRA) 















































Rob Petti
 resolved  JENKINS-8052 as Fixed


"No changes" shown after change found but before sync completed
















Jenkins now displays "Not yet determined" instead of "No changes" when still syncing.





Change By:


Rob Petti
(22/Apr/13 5:01 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] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

2013-04-22 Thread jhans...@meetme.com (JIRA) 














































Joe Hansche
 commented on  JENKINS-17693


Confluence Publisher for Confluence 5x















Interesting...  I see two potential issues here:


	The SSL exception seems to imply that your Confluence instance is requiring HTTPS, but the certificate can't be validated by the Jenkins server. Is your instance accessible via non-SSL (http:// only)?
	
		If your server allows that, what happens if you change the URL in the Jenkins system configuration to remove the https requirement?
		If your server requires HTTPS, then it will likely require importing the SSL certificate from the Confluence server into the Jenkins server's JVM. I've had to do this a couple times in the past, particularly with newer Certificate Authorities that weren't available (or weren't widely popular) at the time the JVM you use was released.  If this is what's required, I will look up instructions for importing that certificate and see if it helps.  On a side note, how many Jenkins servers are in your cluster?  Because I believe all servers (master and slaves) will need to have the certificate imported in order to support this.
	
	
	It sounds like your Confluence instance does not have the remote APIs enabled, based on the "There is no SOAP service at this location
" error.
	
		Can you try these steps to enable the SOAP API?  https://confluence.atlassian.com/display/DOC/Enabling+the+Remote+API
	
	





























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

2013-04-22 Thread m...@kevenbauke.com (JIRA) 















































Keven Bauke
 assigned  JENKINS-17693 to Joe Hansche



Confluence Publisher for Confluence 5x
















Change By:


Keven Bauke
(22/Apr/13 4:55 PM)




Assignee:


Keven Bauke
Joe Hansche



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ant] (JENKINS-17705) NullPointerException when rename a job (Status Code: 500)

2013-04-22 Thread baldo.dan...@gmail.com (JIRA) 














































Daniel Baldo
 commented on  JENKINS-17705


NullPointerException when rename a job (Status Code: 500)















It's important to say that the change save.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17648) SSH Slaves Plugin 0.24: Exception while connection slaves

2013-04-22 Thread rainer.weinh...@seitenbau.com (JIRA) 














































Rainer Weinhold
 commented on  JENKINS-17648


SSH Slaves Plugin 0.24: Exception while connection slaves















It looks like 0.25 is working. Not totally sure, because the plugin-center reports version 0.23. But i had to replace the jpi by hand, so i'm pretty sure this is actually the 0.25 version.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

2013-04-22 Thread m...@kevenbauke.com (JIRA) 












































  
Keven Bauke
 edited a comment on  JENKINS-17693


Confluence Publisher for Confluence 5x
















Sure, thx for your fast reply. In my case I can't log in.
Unfortunately I can not provide you the wsdl because I get an error-message saying:
There is no SOAP service at this location


Failed to login
AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
 faultActor: 
 faultNode: 
 faultDetail: 
	{http://xml.apache.org/axis/}stackTrace:javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1731)
	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:241)
	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:235)
	at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1206)
	at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136)
	at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
	at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:925)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1197)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1181)
	at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:186)
	at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
	at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
	at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
	at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
	at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
	at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
	at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
	at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
	at org.apache.axis.client.Call.invoke(Call.java:2767)
	at org.apache.axis.client.Call.invoke(Call.java:2443)
	at org.apache.axis.client.Call.invoke(Call.java:2366)
	at org.apache.axis.client.Call.invoke(Call.java:1812)
	at jenkins.plugins.confluence.soap.v1.ConfluenceserviceV1SoapBindingStub.login(ConfluenceserviceV1SoapBindingStub.java:4619)
	at com.myyearbook.hudson.plugins.confluence.ConfluenceSite.createSession(ConfluenceSite.java:100)
	at com.myyearbook.hudson.plugins.confluence.ConfluenceSite$DescriptorImpl.doLoginCheck(ConfluenceSite.java:160)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
	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:573)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
	at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
	at winstone.RequestDispatcher.forward(RequestDi

[JIRA] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

2013-04-22 Thread m...@kevenbauke.com (JIRA) 














































Keven Bauke
 commented on  JENKINS-17693


Confluence Publisher for Confluence 5x















Sure, thx for your fast reply. In my case I can't log in.


Failed to login
AxisFault
 faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
 faultSubcode: 
 faultString: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
 faultActor: 
 faultNode: 
 faultDetail: 
	{http://xml.apache.org/axis/}stackTrace:javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
	at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Alerts.java:174)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1731)
	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:241)
	at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Handshaker.java:235)
	at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1206)
	at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:136)
	at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Handshaker.java:593)
	at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Handshaker.java:529)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:925)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1170)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1197)
	at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1181)
	at org.apache.axis.components.net.JSSESocketFactory.create(JSSESocketFactory.java:186)
	at org.apache.axis.transport.http.HTTPSender.getSocket(HTTPSender.java:191)
	at org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:404)
	at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
	at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
	at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
	at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
	at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
	at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
	at org.apache.axis.client.Call.invoke(Call.java:2767)
	at org.apache.axis.client.Call.invoke(Call.java:2443)
	at org.apache.axis.client.Call.invoke(Call.java:2366)
	at org.apache.axis.client.Call.invoke(Call.java:1812)
	at jenkins.plugins.confluence.soap.v1.ConfluenceserviceV1SoapBindingStub.login(ConfluenceserviceV1SoapBindingStub.java:4619)
	at com.myyearbook.hudson.plugins.confluence.ConfluenceSite.createSession(ConfluenceSite.java:100)
	at com.myyearbook.hudson.plugins.confluence.ConfluenceSite$DescriptorImpl.doLoginCheck(ConfluenceSite.java:160)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
	at java.lang.reflect.Method.invoke(Method.java:597)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
	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:573)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:164)
	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.doFilt

[JIRA] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

2013-04-22 Thread jhans...@meetme.com (JIRA) 












































  
Joe Hansche
 edited a comment on  JENKINS-17693


Confluence Publisher for Confluence 5x
















Keven Bauke, until I have a chance to test this against a 5.x confluence instance, can you provide more information about what failures you're experiencing?  Any log messages would be useful (from either Jenkins or Confluence side), etc.

Also, can you please attach your SOAP WSDL file from your instance of Confluence?  Should be accesible from http:///rpc/soap-axis/confluenceservice-v2?wsdl



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

2013-04-22 Thread jhans...@meetme.com (JIRA) 















































Joe Hansche
 assigned  JENKINS-17693 to Keven Bauke



Confluence Publisher for Confluence 5x
















Keven Bauke, until I have a chance to test this against a 5.x confluence instance, can you provide more information about what failures you're experiencing?  Any log messages would be useful (from either Jenkins or Confluence side), etc.





Change By:


Joe Hansche
(22/Apr/13 4:26 PM)




Assignee:


Joe Hansche
Keven Bauke



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [mstest] (JENKINS-8805) Problem with MSTest post build action with following message: "FATAL: No MSTest TRX test report files were found. Configuration error?"

2013-04-22 Thread gopivi...@gmail.com (JIRA) 














































gopivinay gande
 commented on  JENKINS-8805


Problem with MSTest post build action with following message: "FATAL: No MSTest TRX test report files were found. Configuration error?"















Thanks Vishal It got passed through the step .BUt i coudn't see any results or any information from .trx

17:07:57   Loading F:\RequestManagement\Jenkins\jobs\NewTestJob2\workspace\trunk\Hp.Rm.PropelWebTests\Deployment.testsettings...
17:07:57   Loading F:\RequestManagement\Jenkins\jobs\NewTestJob2\workspace\trunk\Hp.Rm.PropelWebTests\Hp.Rm.PropelWebTests.vsmdi...
17:07:58   Starting execution...
17:10:02   
17:10:02   Results   Top Level Tests
17:10:02   ---   ---
17:10:02   Passed(SampleTests/)f:\requestmanagement\jenkins\jobs\newtestjob2\workspace\trunk\hp.rm.propelwebtests\hp.rm.propelwebtests\servicecatalog\singletenant\webtest\loginlogout.webtest
17:10:02   1/1 test(s) Passed
17:10:02   
17:10:02   Summary
17:10:02   ---
17:10:02   Test Run Completed.
17:10:02 Passed  1
17:10:02 -
17:10:02 Total   1
17:10:02   Results file:  F:\RequestManagement\Jenkins\jobs\NewTestJob2\workspace\trunk\build\TestOutput\results.trx
17:10:02   Test Settings: Deployment
17:10:02   ** The msbuild mstest task for this hudson job is finished *
17:10:02 Done Building Project "F:\RequestManagement\Jenkins\jobs\NewTestJob2\workspace\trunk\build\MasterBuildScript.proj" (UnitTest target(s)).
17:10:02 
17:10:02 Build succeeded.
17:10:02 0 Warning(s)
17:10:02 0 Error(s)
17:10:02 
17:10:02 Time Elapsed 00:02:06.02
17:10:02 Processing tests results in file(s)  trunk\build\TestOutput\results.trx
17:10:02 trunk\build\TestOutput\results.trx
17:10:02 Finished: SUCCESS

how am i gonna see my Stats from the trx file on to jenkins Dash borad



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session

2013-04-22 Thread ku...@gmx.de (JIRA) 














































kutzi
 commented on  JENKINS-17684


Dashboard web pages don't render correctly in Chrome because of bad cache/session















Seeing something similar quite frequently (Jenkins ver. 1.480.2, Chrome Version 26.0.1410.64)
I can resolve it by forcing a full reload (CTRL+SHIFT+R)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ant] (JENKINS-17705) NullPointerException when rename a job (Status Code: 500)

2013-04-22 Thread baldo.dan...@gmail.com (JIRA) 














































Daniel Baldo
 created  JENKINS-17705


NullPointerException when rename a job (Status Code: 500)















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


ant



Created:


22/Apr/13 4:13 PM



Description:


When i change the job name i get this error after save and confirm the change.

Status Code: 500

Exception: java.lang.NullPointerException
Stacktrace:
javax.servlet.ServletException: java.lang.NullPointerException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	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:677)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	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:677)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	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:677)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:722)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
	at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
	at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$1.doFilter(Chaine

[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache/session

2013-04-22 Thread r...@burhum.com (JIRA) 














































Ragi Burhum
 updated  JENKINS-17684


Dashboard web pages don't render correctly in Chrome because of bad cache/session
















Change By:


Ragi Burhum
(22/Apr/13 3:52 PM)




Summary:


Dashboard web pages don't render correctly in Chrome because of bad cache
/session





Description:


After using Chrome for a day, the page renders incorrectly. Screenshot: http://imgur.com/9Y11bqzIt doesn't matter if I hit refresh multiple times, it always renders the same way. If I open another browser, it works fine.If I debug under Chrome Dev Tools, I don't see any errors when fetching the resources... just a whole bunch of 304s.If I clear the cache manually using the Chrome Web settings, then everything works fine again.I went to #jenkins on freenode and apparently other people were having the same issue.
**Update** I can make the error go away by simply clearing the jenkins cookie and leaving the rest of the cache intact. It seems the error is session related (all the cookie contains is a session id).I am using the GitHub plugin for authentication/authorization.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache

2013-04-22 Thread r...@burhum.com (JIRA) 














































Ragi Burhum
 commented on  JENKINS-17684


Dashboard web pages don't render correctly in Chrome because of bad cache















I am going to update the main bug description to account for this.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [core] (JENKINS-17684) Dashboard web pages don't render correctly in Chrome because of bad cache

2013-04-22 Thread r...@burhum.com (JIRA) 














































Ragi Burhum
 commented on  JENKINS-17684


Dashboard web pages don't render correctly in Chrome because of bad cache















I can get it to happen without having automatic refresh for awhile. After the site goes into a bad state, it remain so.

I was also told (in IRC) to look at the contents of screen.css. I don't see any screen.css file though.

*I found something interesting though*. If I delete the jenkins cookie and open the page again, the page starts working again. The cookie contains the session value, so it seems that the error is related to a session id expiring. I am using the GitHub plugin for authentication/authorization.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [deploy] (JENKINS-4949) Deploy to more than one container

2013-04-22 Thread jenk...@phil-schneider.de (JIRA) 














































Philipp Schneider
 commented on  JENKINS-4949


Deploy to more than one container















This ticket is almost 2.5 years old and since six month a fix (pull request) is waiting.
Is anybody talking care of this?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [plugin] (JENKINS-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild

2013-04-22 Thread david.is...@gmail.com (JIRA) 














































David Ishee
 created  JENKINS-17704


Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild















Issue Type:


Bug



Assignee:


Unassigned


Components:


plugin



Created:


22/Apr/13 3:26 PM



Description:


I have a MultiJob Project that fails occasionally with:


FATAL: Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild#subBuilds for class com.tikal.jenkins.plugins.multijob.MultiJobBuild
java.lang.RuntimeException: Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild#subBuilds for class com.tikal.jenkins.plugins.multijob.MultiJobBuild
	at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:167)
	at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:135)
	at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:130)
	at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:120)
	at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:94)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:78)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:63)
	at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:98)
	at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:38)
	at com.thoughtworks.xstream.XStream.marshal(XStream.java:840)
	at com.thoughtworks.xstream.XStream.marshal(XStream.java:829)
	at com.thoughtworks.xstream.XStream.toXML(XStream.java:804)
	at hudson.XmlFile.write(XmlFile.java:177)
	at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.save(DownstreamBuildViewUpdateListener.java:105)
	at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:91)
	at org.jvnet.hudson.plugins.DownstreamBuildViewUpdateListener.onStarted(DownstreamBuildViewUpdateListener.java:46)
	at hudson.model.listeners.RunListener.fireStarted(RunListener.java:188)
	at hudson.model.Run.execute(Run.java:1497)
	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: java.util.ConcurrentModificationException
	at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
	at java.util.AbstractList$Itr.next(AbstractList.java:343)
	at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:54)
	at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:68)
	at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:78)
	at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:176)
	at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:163)
	... 21 more






Environment:


Multijob Plugin v1.8

Jenkins 1.480.3

Red Hat Linux




Project:


Jenkins



Priority:


Major



Reporter:


David Ishee

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issu

[JIRA] [active-directory] (JENKINS-17703) Active Directory plugin crashes on version 1.31 (2013/04/18)

2013-04-22 Thread fernando.ru...@gmail.com (JIRA) 














































Fernando Rubbo
 commented on  JENKINS-17703


Active Directory plugin crashes on version 1.31 (2013/04/18)















We have faced the same issue



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"

2013-04-22 Thread liuou...@sina.com (JIRA) 














































liu ou
 commented on  JENKINS-15587


Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"















I'm still having this issue on 1.512 win7x64 with a maven project..

 [33m2013-4-22 22:51:06 hudson.model.RunMap retrieve
警告: could not load D:\jenkins\jobs\TestNGMavenCI\builds\29
hudson.util.IOException2: Invalid directory name D:\jenkins\jobs\TestNGMavenCI\builds\29
at hudson.model.Run.parseTimestampFromBuildDir(Run.java:354)
at hudson.model.Run.(Run.java:294)
at hudson.model.AbstractBuild.(AbstractBuild.java:182)
at hudson.maven.AbstractMavenBuild.(AbstractMavenBuild.java:54)
at hudson.maven.MavenModuleSetBuild.(MavenModuleSetBuild.java:135)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1122)
at hudson.model.AbstractProject$1.create(AbstractProject.java:319)
at hudson.model.AbstractProject$1.create(AbstractProject.java:317)
at hudson.model.RunMap.retrieve(RunMap.java:225)
at hudson.model.RunMap.retrieve(RunMap.java:59)
at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667)
at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629)
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368)
at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526)
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:379)
at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:321)
at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1059)
at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184)
at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:448)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17703) Active Directory plugin crashes on version 1.31 (2013/04/18)

2013-04-22 Thread baldo.dan...@gmail.com (JIRA) 














































Daniel Baldo
 created  JENKINS-17703


Active Directory plugin crashes on version 1.31 (2013/04/18)















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


active-directory



Created:


22/Apr/13 2:47 PM



Description:


Today we have updated the active-directory plugin from 1.30 to 1.31 and, after jenkins restart, we got the following error


Apr 22, 2013 7:51:05 AM hudson.security.AuthenticationProcessingFilter2 onUnsuccessfulAuthentication
INFO: Login attempt failed
org.acegisecurity.BadCredentialsException: Failed to retrieve user information for daniel; nested exception is javax.naming.InvalidNameException: CN=Info Desenv - Daniel,OU=Desenvolvimento,OU=Inform\u00E1tica,OU=Administra\u00E7\u00E3o,DC=ciaX,DC=com,DC=br: [LDAP: error code 34 - 208F: LdapErr: DSID-0C09070B, comment: Error processing name, data 0, v1772]; remaining name 'CN=Info Desenv - Daniel,OU=Desenvolvimento,OU=Inform\u00E1tica,OU=Administra\u00E7\u00E3o,DC=ciaX,DC=com,DC=br'
at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:309)
at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:193)
at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:137)
at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)
at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)
at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.j

[JIRA] [core] (JENKINS-17594) incessant jenkins.model.PeepholePermalink updateCache WARNINGS

2013-04-22 Thread cynic...@gmail.com (JIRA) 














































Dan Lewis
 commented on  JENKINS-17594


incessant jenkins.model.PeepholePermalink updateCache WARNINGS















This continues to occur in 1.512.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.

2013-04-22 Thread nick.pa...@gmail.com (JIRA) 














































Nick Pannu
 commented on  JENKINS-17058


Publish over SSH plugin XML configuration cannot be read on jenkins start up.















$ java -version
java version "1.6.0_24"

$ uname -a
Linux 2.6.32-279.22.1.el6.x86_64 #1 SMP Wed Feb 6 03:10:46 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
$ cat /etc/issue
CentOS release 6.3 (Final)
Kernel \r on an \m

Jenkins v1.502 and Plugin v1.10 works, upgrading Jenkins to v1.504 caused the issue. Haven't tried any of the newer versions of Jenkins.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?

2013-04-22 Thread jda...@ipswitch.com (JIRA) 














































Jason Davis
 commented on  JENKINS-17652


Poll Exclude Files Too Aggressive on Blocking Builds?















Thank you for the clarification.  Neither  nor  include non-alphanumeric characters.  The paths are in completely separate locations in the source tree sharing only the topmost level of the path.   does contain a space so I have to quote the path in the exclude list.   

Thanks for looking into this!




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [core] (JENKINS-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"

2013-04-22 Thread akuj...@evertz.com (JIRA) 














































Andrew Kujtan
 reopened  JENKINS-15587


Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"
















Change By:


Andrew Kujtan
(22/Apr/13 2:34 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-15587) Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"

2013-04-22 Thread akuj...@evertz.com (JIRA) 














































Andrew Kujtan
 commented on  JENKINS-15587


Builds disappear from jobs - hudson.util.IOException2: Invalid directory name - java.text.ParseException: Unparseable date: "39"















I'm still having this issue on 1.512 win7x64,


WARNING: could not load D:\jenkins\jobs\Job1\builds\851
hudson.util.IOException2: Invalid directory name D:\jenkins\jobs\Job1\builds\851
	at hudson.model.Run.parseTimestampFromBuildDir(Run.java:354)
	at hudson.model.Run.(Run.java:294)
	at hudson.model.AbstractBuild.(AbstractBuild.java:182)
	at hudson.model.Build.(Build.java:103)
	at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41)
	at sun.reflect.GeneratedConstructorAccessor47.newInstance(Unknown Source)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
	at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1122)
	at hudson.model.AbstractProject$1.create(AbstractProject.java:319)
	at hudson.model.AbstractProject$1.create(AbstractProject.java:317)
	at hudson.model.RunMap.retrieve(RunMap.java:225)
	at hudson.model.RunMap.retrieve(RunMap.java:59)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:220)
	at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:354)
	at hudson.model.Run.onLoad(Run.java:319)
	at hudson.model.RunMap.retrieve(RunMap.java:226)
	at hudson.model.RunMap.retrieve(RunMap.java:59)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:650)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:456)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:526)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:379)
	at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:321)
	at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1059)
	at hudson.model.AbstractProject.poll(AbstractProject.java:1425)
	at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439)
	at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468)
	at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
	at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
	at java.util.concurrent.FutureTask.run(FutureTask.java:138)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
	at java.lang.Thread.run(Thread.java:662)
Caused by: java.text.ParseException: Unparseable date: "851"
	at java.text.DateFormat.parse(DateFormat.java:337)
	at hudson.model.Run.parseTimestampFromBuildDir(Run.java:352)
	... 37 more




























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?

2013-04-22 Thread rob.pe...@gmail.com (JIRA) 














































Rob Petti
 commented on  JENKINS-17652


Poll Exclude Files Too Aggressive on Blocking Builds?















To clarify, it should only ever skip a changeset if every file in it is excluded. If it contains a file that is not excluded, then it will not skip the change.

In this case it appears to be mistakenly excluding every single file as if you had put //... as your excluded path.

Does  or  contain any non-alphanumeric characters?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [copyartifact] (JENKINS-17702) CopyArtifact with parameter selection fails when parameters changed

2013-04-22 Thread tom.ghyseli...@excentis.com (JIRA) 














































Tom Ghyselinck
 created  JENKINS-17702


CopyArtifact with parameter selection fails when parameters changed















Issue Type:


Bug



Assignee:


Unassigned


Components:


copyartifact



Created:


22/Apr/13 2:10 PM



Description:


Copy Artifact fails from (source) projects when
their build parameters changed between different builds

e.g. When ProjectY copies artifacts from ProjectX with parameter MY_X_PARAM=test
ProjectY CopyArtifact fails when
build #1 for ProjectX used no parameters,
build #2 for ProjectX has (choice) parameter MY_X_PARAM=test




Environment:


Jenkins 1.480.3

CopyArtifact 1.26




Project:


Jenkins



Labels:


copyartifact
plugin
parameterized
parameter
build




Priority:


Blocker



Reporter:


Tom Ghyselinck

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [rebuild] (JENKINS-17701) IllegalArgumentException with copyartifact.BuildSelector

2013-04-22 Thread tom.ghyseli...@excentis.com (JIRA) 














































Tom Ghyselinck
 created  JENKINS-17701


IllegalArgumentException with copyartifact.BuildSelector















Issue Type:


Bug



Assignee:


ragesh_nair



Components:


rebuild



Created:


22/Apr/13 1:52 PM



Description:


Rebuild with CopyArtifact build selector throws an exception:

Status Code: 500

Exception: java.lang.IllegalArgumentException: Failed to instantiate class hudson.plugins.copyartifact.BuildSelector from {"name":"BYTEBLOWER_SERVER_BUILD","value":""}
Stacktrace:
javax.servlet.ServletException: java.lang.IllegalArgumentException: Failed to instantiate class hudson.plugins.copyartifact.BuildSelector from {"name":"BYTEBLOWER_SERVER_BUILD","value":""}
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:616)
	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$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:717)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
	at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
	at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	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)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$

[JIRA] [git] (JENKINS-17700) Windows: Git clone fails on computer with multiple executors or slaves

2013-04-22 Thread to...@hellberg.name (JIRA) 














































Tomas Hellberg
 created  JENKINS-17700


Windows: Git clone fails on computer with multiple executors or slaves















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git



Created:


22/Apr/13 1:10 PM



Description:


This problem relates to Git on Windows slaves.

Git clone hangs indefinitely for about one in three builds on slaves with multiple executors, or on a computers with multiple slaves.

If each slave is placed within a virtual machine on the same computer we experience no hangs.

So the problem seems to be occurring when multiple "git clone" operations are executed at the same time on the same computer, regardless if the multiple executions of "git clone" are performed on on slave with multiple executors or on a computer with multiple slaves.

Example build output:

Triggered by Gerrit: http://gerrit.int/573
Building remotely on Slave 1h   in workspace c:\Jenkins1h\workspace\Fw_BuildSystem_Verify
Checkout:Fw_BuildSystem_Verify / c:\Jenkins1h\workspace\Fw_BuildSystem_Verify - hudson.remoting.Channel@1b53c3c6:Slave 1h
Using strategy: Gerrit Trigger
Last Built Revision: Revision 1387f2632ef7b7a576597a3eecfd0542e28d085f (develop)
Cloning the remote Git repository
Cloning repository ssh://gerrit.int:29418/Fw/Framework.git
git --version
git version 1.8.1.msysgit.1
Build was aborted
Notifying upstream projects of job completion
Finished: ABORTED




Environment:


Windows 7 x64, Jenkins 1.511, git version 1.8.1.msysgit.1




Project:


Jenkins



Priority:


Major



Reporter:


Tomas Hellberg

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [template-workflows] (JENKINS-17699) Template jobs do not adhere to job permissions

2013-04-22 Thread aszos...@partner.eso.org (JIRA) 














































Artur Szostak
 created  JENKINS-17699


Template jobs do not adhere to job permissions















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


template-workflows



Created:


22/Apr/13 12:57 PM



Description:


When the "Project-based Matrix Authorization Strategy" is enabled in the global Jenkins configuration and a user Alice does not have "Administer" permissions set under the "Overall" heading, the following is observed: When user Alice creates a new "Template Workflow Job" they are not subsequently able to actually create nor delete any workflows, even though they have modification and configuration permissions for individual jobs. It looks like template workflow jobs do not adhere to job security permissions correctly. This makes the plugin effectively useless in a fully fledged multi user environment.




Environment:


Jenkins 1.480.3 running on Scientific Linux 5.5

Java runtime 1.6.0_20-b02




Project:


Jenkins



Priority:


Major



Reporter:


Artur Szostak

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17698) [ssh slaves] - No support of user's custom credentials since 0.23

2013-04-22 Thread o.v.nenas...@gmail.com (JIRA) 














































Oleg Nenashev
 created  JENKINS-17698


[ssh slaves] - No support of user's custom credentials since 0.23















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Components:


ssh-slaves



Created:


22/Apr/13 12:29 PM



Description:


Hello, 

“Credentials plugin” allows to create user-specific SSH credentials. Unfortunately, “ssh slaves” doesn’t support user’s custom credentials in slave configuration. 

So: 
1) User without “Overall/Administer” rights can’t edit global/system credentials => He can’t create node with custom credentials even if he has “Slave/Configure” privilege 
2) Admin can create custom credentials for user in global space, but then he will need user’s password => not good
3) Admin can grant temporary  “Overall/Administer” rights to user => not good too

So, version 0.23 prohibits several use-cases from previous versions. I suppose that plugin should support user’s credentials or legacy user/password approach from previous versions.





Project:


Jenkins



Labels:


security
plugin
exception




Priority:


Major



Reporter:


Oleg Nenashev

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [timestamper] (JENKINS-17697) Different timestamp between short and full console log on timeout

2013-04-22 Thread jcarsi...@java.net (JIRA) 














































Julien Carsique
 created  JENKINS-17697


Different timestamp between short and full console log on timeout















Issue Type:


Bug



Assignee:


stevengbrown



Components:


timestamper



Created:


22/Apr/13 12:22 PM



Description:


When a timeout occurs, it seems the timestamp shown in the short console log is sometimes wrong. Whereas it's right on the full console log.

Extract from /console
07:53:24 ==
07:53:24 Build timed out (after 300 minutes). Marking the build as aborted.
07:53:24 Build was aborted
07:53:24 Recording test results
11:02:31 [ci-game] evaluating rule: Build result


Extract from /consoleFull
07:53:24 ==
11:02:31 Build timed out (after 300 minutes). Marking the build as aborted.
11:02:31 Build was aborted
11:02:31 Recording test results
11:02:31 [ci-game] evaluating rule: Build result


The right one must be the consoleFull since the timeout occurred at 11h02, not 07:53.




Project:


Jenkins



Priority:


Minor



Reporter:


Julien Carsique

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [perforce] (JENKINS-17652) Poll Exclude Files Too Aggressive on Blocking Builds?

2013-04-22 Thread jda...@ipswitch.com (JIRA) 














































Jason Davis
 commented on  JENKINS-17652


Poll Exclude Files Too Aggressive on Blocking Builds?















Just checked polling on a build that has this single row in the exclude files section:


///VersionInfo.cs


However the build is not being triggered when it finds changes in other paths:


Exclude file(s) found:
	///ScriptBox/Help.fbp7	
///LaunchChecker.fbp7
Changelist 185127 is composed of file(s) and/or user(s) that are excluded.


Is it correct that even if VersionInfo.cs was in the list of excluded files, these changes should still trigger a build?  btw - In this actual build, VersionInfo.cs isn't even in the list of changes that the build is currently aware of.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17696) javax.naming.InvalidNameException

2013-04-22 Thread dma...@gmail.com (JIRA) 














































dmatag
 created  JENKINS-17696


javax.naming.InvalidNameException















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


error.log



Components:


active-directory



Created:


22/Apr/13 11:41 AM



Description:


Active directory plugin fails to authenticate some users. We think they're people who has special characters in their names, like 'ñ', 'ó'.





Due Date:


21/Apr/13 12:00 AM




Environment:


Jenkins 1.511,




Project:


Jenkins



Priority:


Major



Reporter:


dmatag

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [join] (JENKINS-16201) Join plugin - join job does not run

2013-04-22 Thread 1990.a...@gmail.com (JIRA) 














































Alex Vesely
 commented on  JENKINS-16201


Join plugin - join job does not run















For some unrelated reasons, I had to migrate to Jenkins 1.506. The bug continues to randomly appear.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17684) Dashboard web pages don't render correctly in Chrome because of bad cache

2013-04-22 Thread rosenb...@bias.de (JIRA) 














































Lars Rosenboom
 commented on  JENKINS-17684


Dashboard web pages don't render correctly in Chrome because of bad cache















Same problem here with Google Chrome, Version 26.0.1410.64 m under Windows 7, 64-bit.

Can't enforce the bug, but it happens quite regularly after automatic refresh ran in the background for a while. Agree that it looks like a problem with CSS. Maybe a bug of Chrome, not necessarily Jenkins.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [android-emulator] (JENKINS-14901) Emulator start failed on Ubuntu (SDK 20.0.3)

2013-04-22 Thread matti.linnanvu...@ecolane.com (JIRA) 














































Matti Linnanvuori
 commented on  JENKINS-14901


Emulator start failed on Ubuntu (SDK 20.0.3)















The pull request code did not work for me but I got the following error:

Starting xvnc
[tests] $ vncserver :10 -localhost -nolisten tcp

New 'X' desktop is madmax2.ecolane.com:10

Starting applications specified in /var/lib/jenkins/.vnc/xstartup
Log file is /var/lib/jenkins/.vnc/madmax2.ecolane.com:10.log

[android] Using Android SDK: /opt/adt-bundle-linux-x86_64/sdk
[android] Waiting 30 seconds before starting emulator...
$ /opt/adt-bundle-linux-x86_64/sdk/platform-tools/adb start-server
[android] Starting Android emulator
$ /opt/adt-bundle-linux-x86_64/sdk/tools/emulator -no-boot-anim -ports 32988,58093 -avd Android2.3GoogleAPIs -no-snapshot-load -no-snapshot-save
SDL init failure, reason is: No available video device

	daemon not running. starting it now on port 5037 *
	daemon started successfully *



[android] Emulator did not appear to start; giving up



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17695) error 500 after "Delete Project"

2013-04-22 Thread epikur2...@java.net (JIRA) 














































epikur2412
 created  JENKINS-17695


error 500 after "Delete Project"















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


22/Apr/13 10:21 AM



Description:


I tried to delete a project. After pressing the button ok, this messages appeared. The project itself was deleted.



Error 500
Status Code: 500Exception: java.lang.NullPointerExceptionStacktrace: javax.servlet.ServletException: java.lang.NullPointerException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	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:677)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:214)
	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.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:48)
	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:124)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.util.CharacterEnco

[JIRA] [update-center] (JENKINS-17694) Update center JSON broken, no updates available

2013-04-22 Thread jalka...@iki.fi (JIRA) 














































Janne Jalkanen
 updated  JENKINS-17694


Update center JSON broken, no updates available
















Change By:


Janne Jalkanen
(22/Apr/13 9:58 AM)




Environment:


Ubuntu 12.04 LTSOpenJDK Runtime Environment (IcedTea7 2.3.7) (7u15-2.3.7-0ubuntu1~12.04.1)





Description:



Checking for plugin updates on the LTS version causes the following exception trace in /var/log/jenkins/jenkins.logCaused by: net.sf.json.JSONException: Unterminated string at character 417757 of at net.sf.json.util.JSONTokener.syntaxError(JSONTokener.java:512)at net.sf.json.util.JSONTokener.nextString(JSONTokener.java:244)at net.sf.json.util.JSONTokener.nextValue(JSONTokener.java:352)at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:875)at net.sf.json.JSONObject.fromObject(JSONObject.java:170)at net.sf.json.util.JSONTokener.nextValue(JSONTokener.java:355)at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:875)at net.sf.json.JSONObject.fromObject(JSONObject.java:170)at net.sf.json.util.JSONTokener.nextValue(JSONTokener.java:355)at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:875)at net.sf.json.JSONObject._fromString(JSONObject.java:1064)at net.sf.json.JSONObject.fromObject(JSONObject.java:176)at net.sf.json.JSONObject.fromObject(JSONObject.java:147)at hudson.model.UpdateSite.doPostBack(UpdateSite.java:168)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:601)at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)... 60 more



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [update-center] (JENKINS-17694) Update center JSON broken, no updates available

2013-04-22 Thread jalka...@iki.fi (JIRA) 














































Janne Jalkanen
 created  JENKINS-17694


Update center JSON broken, no updates available















Issue Type:


Bug



Assignee:


Unassigned


Components:


update-center



Created:


22/Apr/13 9:56 AM



Description:



Checking for plugin updates on the LTS version causes the following exception trace in /var/log/jenkins/jenkins.log

Caused by: net.sf.json.JSONException: Unterminated string at character 417757 of 

at net.sf.json.util.JSONTokener.syntaxError(JSONTokener.java:512)
at net.sf.json.util.JSONTokener.nextString(JSONTokener.java:244)
at net.sf.json.util.JSONTokener.nextValue(JSONTokener.java:352)
at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:875)
at net.sf.json.JSONObject.fromObject(JSONObject.java:170)
at net.sf.json.util.JSONTokener.nextValue(JSONTokener.java:355)
at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:875)
at net.sf.json.JSONObject.fromObject(JSONObject.java:170)
at net.sf.json.util.JSONTokener.nextValue(JSONTokener.java:355)
at net.sf.json.JSONObject._fromJSONTokener(JSONObject.java:875)
at net.sf.json.JSONObject._fromString(JSONObject.java:1064)
at net.sf.json.JSONObject.fromObject(JSONObject.java:176)
at net.sf.json.JSONObject.fromObject(JSONObject.java:147)
at hudson.model.UpdateSite.doPostBack(UpdateSite.java:168)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:574)
... 60 more




Project:


Jenkins



Priority:


Blocker



Reporter:


Janne Jalkanen

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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

2013-04-22 Thread hal...@cisco.com (JIRA) 














































Hansen Loke
 commented on  JENKINS-17248


java.lang.NullPointerException by start















Updated to 1.512 and the web interface gave the same error message as reported, unusable. Fortunately the workaround of removing the path to global-build-stats works. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [confluence-publisher] (JENKINS-17693) Confluence Publisher for Confluence 5x

2013-04-22 Thread m...@kevenbauke.com (JIRA) 














































Keven Bauke
 created  JENKINS-17693


Confluence Publisher for Confluence 5x















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Joe Hansche



Components:


confluence-publisher



Created:


22/Apr/13 9:29 AM



Description:


It would be great if the plugin would get an upgrade to work with Confluence- Versions higher than 4.x.




Project:


Jenkins



Priority:


Major



Reporter:


Keven Bauke

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [pmd] (JENKINS-17663) Fail by publishing report will fail whole build

2013-04-22 Thread ullrich.haf...@gmail.com (JIRA) 














































Ulli Hafner
 updated  JENKINS-17663


Fail by publishing report will fail whole build
















Change By:


Ulli Hafner
(22/Apr/13 9:06 AM)




Priority:


Major
Minor



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [pmd] (JENKINS-17663) Fail by publishing report will fail whole build

2013-04-22 Thread ullrich.haf...@gmail.com (JIRA) 














































Ulli Hafner
 updated  JENKINS-17663


Fail by publishing report will fail whole build
















Change By:


Ulli Hafner
(22/Apr/13 9:06 AM)




Description:


We encounter error by parsing file (there was character not supported by XML 1.0 version). On build overview PMD plugin show that there is problem ("During parsing an error has been reported.") but build end with success. Consequently number of warning drop to 0.It would be nice that information about failure will be throw to Jenkins so that it tell us, that something is wrong.Console output with error:
{noformat}
[PMD] ./pmd_report.xml failed due to an exception:org.xml.sax.SAXParseException; lineNumber: 1224; columnNumber: 26; An invalid XML character (Unicode: 0x1f) was found in the element content of the document.	at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1236)	at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:568)	at org.apache.commons.digester.Digester.parse(Digester.java:1666)	at hudson.plugins.pmd.parser.PmdParser.parse(PmdParser.java:70)	at hudson.plugins.analysis.core.AbstractAnnotationParser.parse(AbstractAnnotationParser.java:53)	at hudson.plugins.analysis.core.FilesParser.parseFile(FilesParser.java:306)	at hudson.plugins.analysis.core.FilesParser.parseFiles(FilesParser.java:264)	at hudson.plugins.analysis.core.FilesParser.parserCollectionOfFiles(FilesParser.java:215)	at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:184)	at hudson.plugins.analysis.core.FilesParser.invoke(FilesParser.java:31)	at hudson.FilePath.act(FilePath.java:852)	at hudson.FilePath.act(FilePath.java:825)	at hudson.plugins.pmd.PmdPublisher.perform(PmdPublisher.java:139)	at hudson.plugins.analysis.core.HealthAwarePublisher.perform(HealthAwarePublisher.java:146)	at hudson.plugins.analysis.core.HealthAwareRecorder.perform(HealthAwareRecorder.java:331)	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)	at hudson.model.Build$BuildExecution.post2(Build.java:183)	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732)	at hudson.model.Run.execute(Run.java:1568)	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)	at hudson.model.ResourceController.execute(ResourceController.java:88)	at hudson.model.Executor.run(Executor.java:236)
{noformat}





Component/s:


analysis-core



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [pmd] (JENKINS-17663) Fail by publishing report will fail whole build

2013-04-22 Thread ullrich.haf...@gmail.com (JIRA) 














































Ulli Hafner
 commented on  JENKINS-17663


Fail by publishing report will fail whole build















Ok, now I understand. I.e., this should be an option that could be activated.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [warnings] (JENKINS-17691) Cannot catch filename and linenumber

2013-04-22 Thread ullrich.haf...@gmail.com (JIRA) 














































Ulli Hafner
 updated  JENKINS-17691


Cannot catch filename and linenumber
















Change By:


Ulli Hafner
(22/Apr/13 9:03 AM)




Description:


Hello,I’m using the Warnings plugin (version 4.23) and I’m trying to parse a bunch of log files generated by an in-house tool that look like the following example “scen_Rollcontrol.prop.txt.log”. Note that one build generates a bunch of log files and I need to collect all the warnings/errors contained in all the log files of the current build.Here is the content of one log file:
{noformat}
ADEPAUTO (CLI) v2.0.3 running on Java 1.7.0_09-b05Signals definition context: [-Inf - +Inf]** Scade **  SCENARIO -> ERROR: Not verified in true context [0.2 - 8.1] at time [0.2 - 8.1] : RollcontrolManoeuvre -> Not verified in true context [0.2 - 8.1] at time [0.2 - 8.1] : Conditions initiales : -Contexte : [0 - 15.6]  P1 [0.2 - 8.1]=> ERROR: Not verified in true context [0.2 - 8.1] at time [0.2 - 8.1]Manoeuvre -> OK : Conditions initiales : -Contexte : [0 - 15.6]  P1 [8.2 - 12.1]=> OKManoeuvre -> OK : Conditions initiales : -Contexte : [0 - 15.6]  P1 [12.2 - 14.1] U [14.7 - 15.1]=> OKManoeuvre -> OK : Conditions initiales : -Contexte : [0 - 15.6]  P1 [2.2 - 3.1] U [6.2 - 7.1] U [10.2 - 11.1]=> OK
{noformat}
The problem is that there is no filename in the text above, the filename I’d like to collect is the actual file name of the log file being analyzed. Similarly, the line I’d like to show in Jenkins is the actual line where “Manoeuvre -> Not verified” appears in the log file.Is there any way I can configure the Warnings plugin to do that i.e. provide filename and linenumber to the Warning declaration in the Groovy Mapping Script ?Thank you in advance. 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-17692) Active Directory Plugin - Fails to retreive users with swedish characters in full name

2013-04-22 Thread jocke.pihlst...@netrelations.se (JIRA) 














































Jocke Pihlström
 created  JENKINS-17692


Active Directory Plugin - Fails to retreive users with swedish characters in full name















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


active-directory



Created:


22/Apr/13 9:00 AM



Description:


I've added the AD Plugin 1.31 to my Jenkins installation and it works as long as my users don't have swedish characters in their full name in the AD. For example, username test.testsson with full name Test Testsson will work just fine. Username bjorn.borg with full name Björn Borg will fail.

I'm pretty sure this has something to do with it:
CN=Bj\u00F6mrn Borg,OU=Users,DC=my,DC=Domain

If I change Björns full name to "Bjorn Borg" in AD, it works just fine:
CN=Bjorn Borg,OU=Users,DC=my,DC=Domain

Is there a work-around or a fix?

/Jocke

Here is a Log example:

Apr 22, 2013 10:20:44 AM hudson.plugins.active_directory.ActiveDirectorySecurityRealm
FINE: Connecting to ldap://server.my.domain:3268/

Apr 22, 2013 10:20:44 AM hudson.plugins.active_directory.ActiveDirectorySecurityRealm
FINE: _gc._tcp.my.domain resolved to [server.my.domain:3268]

Apr 22, 2013 10:20:44 AM hudson.plugins.active_directory.ActiveDirectorySecurityRealm
FINE: SRV record found: 0 100 3268 server.my.domain.

Apr 22, 2013 10:20:44 AM hudson.plugins.active_directory.ActiveDirectorySecurityRealm
FINE: Attempting to resolve _gc._tcp.my.domain to SRV record

Apr 22, 2013 10:20:17 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider
FINE: Failed toretrieve user bjorn.borg
org.acegisecurity.BadCredentialsException: Failed to retrieve user information for bjorn.borg; nested exception is javax.naming.InvalidNameException: CN=Bj\u00F6mrn Borg,OU=Users,DC=my,DC=domain: [LDAP: error code 34 - 208F: LdapErr: DSID-0C090715, comment: Error processing name, data 0, v1db1]; remaining name 'CN=Bj\u00F6mrn Borg,OU=Users,DC=my,DC=domain'
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:309)
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:193)
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:137)
	at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)
	at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)
	at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
	at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)

[JIRA] [analysis-core] (JENKINS-17663) Fail by publishing report will fail whole build

2013-04-22 Thread p.spir...@mwaysolutions.com (JIRA) 














































Peter Spireng
 commented on  JENKINS-17663


Fail by publishing report will fail whole build















Ok. The story was so that:
1. PMD + PMD plugin was set and work without problem
2. we add new code that contains character "0x1f" and it was in string that was couple of times in code, so PMD generate warning about more occurrences of this string and copy string to PMD resolution report
3. PMD plugin try to parse this report but this character isnt supported for XML 1.0 and end with error. But we noticed this about some time and only so, that graph suddenly show 0 count of PMD warnings.

Hopefully now is more clear ... 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [analysis-core] (JENKINS-17690) Checkbox "Only use stable builds as reference" probably doesnt work

2013-04-22 Thread p.spir...@mwaysolutions.com (JIRA) 














































Peter Spireng
 commented on  JENKINS-17690


Checkbox "Only use stable builds as reference" probably doesnt work















Thanks for clarification. I will look forward for solving JENKINS-13458 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [warnings] (JENKINS-17691) Cannot catch filename and linenumber

2013-04-22 Thread garnikarakel...@gmail.com (JIRA) 














































Garnik Arakelian
 created  JENKINS-17691


Cannot catch filename and linenumber















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


warnings



Created:


22/Apr/13 8:23 AM



Description:


Hello,
I’m using the Warnings plugin (version 4.23) and I’m trying to parse a bunch of log files generated by an in-house tool that look like the following example “scen_Rollcontrol.prop.txt.log”. Note that one build generates a bunch of log files and I need to collect all the warnings/errors contained in all the log files of the current build.
Here is the content of one log file:
ADEPAUTO (CLI) v2.0.3 running on Java 1.7.0_09-b05

Signals definition context: [-Inf - +Inf]

	
	
		Scade **
  SCENARIO -> ERROR: Not verified in true context [0.2 - 8.1] at time [0.2 - 8.1] : Rollcontrol
	
	



Manoeuvre -> Not verified in true context [0.2 - 8.1] at time [0.2 - 8.1] : 
Conditions initiales : -
Contexte : [0 - 15.6]
  P1 [0.2 - 8.1]
=> ERROR: Not verified in true context [0.2 - 8.1] at time [0.2 - 8.1]
Manoeuvre -> OK : 
Conditions initiales : -
Contexte : [0 - 15.6]
  P1 [8.2 - 12.1]
=> OK
Manoeuvre -> OK : 
Conditions initiales : -
Contexte : [0 - 15.6]
  P1 [12.2 - 14.1] U [14.7 - 15.1]
=> OK
Manoeuvre -> OK : 
Conditions initiales : -
Contexte : [0 - 15.6]
  P1 [2.2 - 3.1] U [6.2 - 7.1] U [10.2 - 11.1]
=> OK

The problem is that there is no filename in the text above, the filename I’d like to collect is the actual file name of the log file being analyzed. Similarly, the line I’d like to show in Jenkins is the actual line where “Manoeuvre -> Not verified” appears in the log file.
Is there any way I can configure the Warnings plugin to do that i.e. provide filename and linenumber to the Warning declaration in the Groovy Mapping Script ?
Thank you in advance. 




Environment:


Windows XP




Project:


Jenkins



Labels:


plugin




Priority:


Major



Reporter:


Garnik Arakelian

























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [analysis-core] (JENKINS-17663) Fail by publishing report will fail whole build

2013-04-22 Thread ullrich.haf...@gmail.com (JIRA) 














































Ulli Hafner
 commented on  JENKINS-17663


Fail by publishing report will fail whole build















I don't understand how this problem can occur in between successful PMD executions. Shouldn't the problem be only visible when you enable PMD using a wrong configuration?



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [fitnesse] (JENKINS-12380) Display results whilst build is in progress

2013-04-22 Thread sta...@yahoo.com (JIRA) 














































Stanimir Stamenkov
 commented on  JENKINS-12380


Display results whilst build is in progress















Discard my previous comment about the nochunk parameter.  It should be the other way round, but it seems using format=xml always spits the output after all suite passes.



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [analysis-core] (JENKINS-17690) Checkbox "Only use stable builds as reference" probably doesnt work

2013-04-22 Thread ullrich.haf...@gmail.com (JIRA) 















































Ulli Hafner
 resolved  JENKINS-17690 as Duplicate


Checkbox "Only use stable builds as reference" probably doesnt work
















Please vote for JENKINS-13458 (and attach yourself as watchee) 





Change By:


Ulli Hafner
(22/Apr/13 7:49 AM)




Status:


Open
Resolved





Resolution:


Duplicate



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [analysis-core] (JENKINS-17690) Checkbox "Only use stable builds as reference" probably doesnt work

2013-04-22 Thread ullrich.haf...@gmail.com (JIRA) 














































Ulli Hafner
 commented on  JENKINS-17690


Checkbox "Only use stable builds as reference" probably doesnt work















The checkbox "Only use stable builds as reference" means that only builds should be considered that are stable before my plug-ins run, e.g. have no unit test failures. This has no influence if a build is set to unstable due to new warnings...

BTW: when you check for new warnings you should use the threshold "0". 



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[JIRA] [build-flow] (JENKINS-16295) [ERROR] BUILD ERROR - (Permission denied)

2013-04-22 Thread sergej.kl...@hermes-softlab.com (JIRA) 














































Sergej Kleva
 commented on  JENKINS-16295


[ERROR] BUILD ERROR - (Permission denied)















I tried with different java versions (64bti and 32bit), svn versions, various jenkins versions but the problem still exists.
On slave machines there is no such problem.

Anyone?!



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-13011) Jenkins server stops responding via http

2013-04-22 Thread stanislav.abadj...@softwareag.com (JIRA) 















































Stanislav Abadjiev
 closed  JENKINS-13011 as Cannot Reproduce


Jenkins server stops responding via http
















It is not reproducible.

I'm closing this.

Regards





Change By:


Stanislav Abadjiev
(22/Apr/13 7:10 AM)




Status:


Open
Closed





Resolution:


Cannot Reproduce



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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.