date:20130412















































Adam PAPAI
 commented on  JENKINS-16941


Git publisher post build action fails on slave agent - unable to serialize















I've started to find out where went it bad.

The affected commits are:

https://github.com/jenkinsci/git-plugin/compare/1349eaba9c5767e9bf52ab27b6c31681f0c13733...6336dc5595266b83c199710953c61351297b7bd8

 so this was the last stable commit:

https://github.com/jenkinsci/git-plugin/commit/1349eaba9c5767e9bf52ab27b6c31681f0c13733

The next few commits failed to compile.

This one compiles, but throws "kind of error", which means it fails to merge: 

Could not checkout release with start point 

https://github.com/jenkinsci/git-plugin/commit/a60b03fab35e62547a058cc8b4eefd62ee6b05b6

So somewhere between:

https://github.com/jenkinsci/git-plugin/compare/1349eaba9c5767e9bf52ab27b6c31681f0c13733...6336dc5595266b83c199710953c61351297b7bd8





























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [fstrigger] (JENKINS-17591) FSTrigger fails to poll when build node labels change

2013-04-12 Thread bdu...@lexmark.com (JIRA)

Brent Duffy
created JENKINS-17591

FSTrigger fails to poll when build node labels change

Issue Type:

Bug

Affects Versions:

current

Assignee:

Gregory Boissinot

Components:

fstrigger

Created:

12/Apr/13 2:48 PM

Description:

FSTrigger doesn't appear to honor changes in labels assignments to build nodes when polling for file changes. In my job configuration, I have "Restrict where this project can be run" set to a label ("label1", for example), instead of a build node name. I have 2 nodes with a set of labels assigned to them:

node1: label1, label2
node2: label1, label2

On the first FSTrigger polling, I see in the log that node1 was chosen for the polling and the poll was successful. If I remove label1 from node1, FSTrigger seems to not find any other nodes with label1 (From the FSTrigger Files log):

Polling started on Apr 12, 2013 10:22:47 AM
Polling for the job FSTrigger_Test_Job
Looking nodes where the poll can be run.
Looking for a candidate node to run the poll.
Trying to find an eligible node with the assigned project label label1.
Can't find any eligible nodes.
Trying to poll on master node.
Can't find any complete active node for the polling action.
Maybe slaves are not yet active at this time or the number of executor of the master is 0.
Checking again in next polling schedule.

It should have been able to use the node node2 since it also had the label label1 assigned to it. Instead, it seems to prefer to only want to use the last node that it used for the polling. If I add label1 back to node1, the polling then succeeds on the next poll.

Environment:

RHEL 6.2 x86-64

Project:

Jenkins

Priority:

Major

Reporter:

Brent Duffy

[JIRA] [testlink] (JENKINS-17442) When connecting to TestLink, finding error ClassCastException

2013-04-12 Thread brunodepau...@yahoo.com.br (JIRA)















































Bruno P. Kinoshita
 commented on  JENKINS-17442


When connecting to TestLink, finding error ClassCastException















That's definitely doable  could you file a new issue, and we'll move the discussion there. Maybe we can even include it in 3.4 (scheduled for this weekend or next week).

Thanks!!!



























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







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















































Alexander Fischer
 commented on  JENKINS-17058


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















I have resolved the problem for Publish-Over-FTP (I'm sure, the solution for Publish-Over-SSH is the same).
You have to override the method readResolve() in all inherited classes, for Publish-Over-FTP this are:

	BapFtpHostConfiguration
	BapFtpPublisherPlugin$Descriptor



The reason is, that the reflection-mechanism looks for the method readResolve() in the inherited class (see above) and after this in the base-class. The reflection-invoke of the method fails, if the method is declared in the base-class and call over the derived class.
Can I check in the patched classes on GitHub?




























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







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















































Alexander Fischer
 updated  JENKINS-17058


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
















The patched sources for resolving the bug...





Change By:


Alexander Fischer
(12/Apr/13 3:03 PM)




Attachment:


BapFtpHostConfiguration.java





Attachment:


BapFtpPublisherPlugin.java



























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







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

[JIRA] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.

2013-04-12 Thread joerg.pancake-st...@lhsystems.com (JIRA)















































Alexander Fischer
 started work on  JENKINS-17058


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
















Change By:


Alexander Fischer
(12/Apr/13 3:10 PM)




Status:


Open
InProgress



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [testflight] (JENKINS-17592) Testflight uploader plugin doesn't allow to upload multiple files

2013-04-12 Thread leszczynski.miko...@gmail.com (JIRA)















































Mikolaj Leszczynski
 created  JENKINS-17592


Testflight uploader plugin doesnt allow to upload multiple files















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


testflight



Created:


12/Apr/13 3:13 PM



Description:


In a job where multiple .apk files are produced it's not possible to use wildcards or to specify multiple artifacts to upload:

Uploading to testflight
File: */bin/*release.apk
java.io.FileNotFoundException: */bin/*release.apk (No such file or directory)
java.io.FileNotFoundException: */bin/*release.apk (No such file or directory)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.init(FileInputStream.java:137)
	at org.apache.http.entity.mime.content.FileBody.writeTo(FileBody.java:78)
	at org.apache.james.mime4j.message.MessageWriter.writeBody(MessageWriter.java:76)
	at org.apache.http.entity.mime.HttpMultipart.doWriteTo(HttpMultipart.java:165)
	at org.apache.http.entity.mime.HttpMultipart.writeTo(HttpMultipart.java:223)
	at org.apache.http.entity.mime.MultipartEntity.writeTo(MultipartEntity.java:179)
	at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:127)
	at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:253)
	at org.apache.http.impl.conn.AbstractClientConnAdapter.sendRequestEntity(AbstractClientConnAdapter.java:218)
	at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:249)
	at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:124)
	at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:483)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:641)
	at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:597)
	at testflight.TestflightUploader.upload(TestflightUploader.java:117)
	at testflight.TestflightRemoteRecorder.call(TestflightRemoteRecorder.java:61)
	at hudson.remoting.LocalChannel.call(LocalChannel.java:45)
	at testflight.TestflightRecorder.perform(TestflightRecorder.java:158)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:770)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:720)
	at hudson.model.Run.execute(Run.java:1600)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
Build step 'Upload to Testflight' marked build as failure

This is basically an app with several different skins, so the build produces multiple apk files. Archiving the artifacts using the above wildcard gives the expected results. It would be nice be able to pass either a wildcard or list of build files to the plugin.




Project:


Jenkins



Priority:


Minor



Reporter:


Mikolaj Leszczynski

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from

[JIRA] [github-oauth] (JENKINS-15765) IRC Bot does not take commands

2013-04-12 Thread jabr...@gmail.com (JIRA)















































Josh Brand
 commented on  JENKINS-15765


IRC Bot does not take commands















Same issue with the same versions.  Additionally, I caught a null pointer exception trying to use !jenkins help: https://gist.github.com/joshbrand/5372875



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [github-oauth] (JENKINS-15765) IRC Bot does not take commands

2013-04-12 Thread jabr...@gmail.com (JIRA)













































 
Josh Brand
 edited a comment on  JENKINS-15765


IRC Bot does not take commands
















Same issue with the same plugin/jenkins versions, on Ubuntu.  Additionally, I caught a null pointer exception trying to use !jenkins help: https://gist.github.com/joshbrand/5372875



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [artifactory] (JENKINS-17593) Artifactory Plugin Uses Incorrect Artifact Names

2013-04-12 Thread ja...@carmanconsulting.com (JIRA)















































James Carman
 created  JENKINS-17593


Artifactory Plugin Uses Incorrect Artifact Names















Issue Type:


Bug



Assignee:


yossis



Components:


artifactory



Created:


12/Apr/13 3:35 PM



Description:


When publishing this project:

https://github.com/jwcarman/gradle-test

on my local Jenkins server using a gradle build, it publishes the artifacts using this name:

com.carmanconsulting.gradle:workspace:1.0-SNAPSHOT

The "workspace" name is not mentioned anywhere in my build.gradle file.  Presumably it comes from the name of the Jenkins workspace directory where the files are checked out and the project is built.  Is there a work-around?




Project:


Jenkins



Priority:


Major



Reporter:


James Carman

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [integrity-plugin] (JENKINS-17292) PTC Integrity Plugin resyncs added members in 'pending-add' state













































 
Joerg Steeg
 edited a comment on  JENKINS-17292


PTC Integrity Plugin resyncs added members in pending-add state
















I believe this issue can be fixed easily. In class IntegritySCM change the method initializeCMProjectMembers(APISession api) accordingly:

IntegritySCM.java
private Response initializeCMProjectMembers(APISession api) throws APIException, SQLException
{
// Lets parse this project
Command siViewProjectCmd = new Command(Command.SI, "viewproject");
siViewProjectCmd.addOption(new Option("recurse"));
siViewProjectCmd.addOption(new Option("project", siProject.getConfigurationPath()));
// NEW LINES
siViewProjectCmd.addOption(new Option("filter", "!pending:add"));
siViewProjectCmd.addOption(new Option("filter", "!pending:addfromarchive"));
siViewProjectCmd.addOption(new Option("filter", "!pending:import"));
siViewProjectCmd.addOption(new Option("filter", "!pending:movememberto"));
siViewProjectCmd.addOption(new Option("filter", "!pending:renameto"));
// END NEW LINES
MultiValue mvFields = new MultiValue(",");
...
return viewRes;
}
 

We tested it locally at our site and the fix seems to work.



























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







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

[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize

2013-04-12 Thread markwa...@yahoo.com (JIRA)

Mark Waite
commented on JENKINS-16941

Git publisher post build action fails on slave agent - unable to serialize

Thanks for spending the effort to seek the failing submission. Unfortunately, I think that the actual problem change is hidden in the refactoring which abstracted the Git implementation into an interface, then provided two alternate implementations of that interface, one using the command line Git, the other using JGit. Initially, the default implementation was JGit. With git-client-plugin 1.0.5, the default implementation is now command line Git.

I think the problem was introduced by the refactoring because the problem still exists even after the default implementation was switched from JGit to command line git.

The high level history (as far as I can see), looks something like this:

Git plugin 1.1.26 - last version known able to push a merged submission back from a slave agent
Git plugin 1.2.0 + Git client plugin 1.0.1 through 1.0.4 - refactored to provide a Git interface, default implementation with JGit
Git plugin 1.3.0 + Git client plugin 1.0.5 - bug fixes and switch default implementation to command line Git

Part of me makes the wild guess that this issue would be resolved if we could understand why it cannot serialize. I don't understand the architecture of the slave to master communication, but I thought it was defined by the Java classes and was implemented with Java serialization. My wild guess was that some field or fields were "lost" or "redefined" in the refactoring which break the serialization between the master and slave. However, that is truly just wild guessing on my part.

[JIRA] [git] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize















































Adam PAPAI
 commented on  JENKINS-16941


Git publisher post build action fails on slave agent - unable to serialize















Meanwhile I think I've found the problematic part. It now works for me locally. Trying to create a patch.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-16941) Git publisher post build action fails on slave agent - unable to serialize

2013-04-12 Thread markwa...@yahoo.com (JIRA)















































Mark Waite
 commented on  JENKINS-16941


Git publisher post build action fails on slave agent - unable to serialize















That sounds great!  If you'd like additional testing of your patch, I'd be happy to help over the weekend.  If you submit it as a pull request to the plugin repository, I can pull it into my repository as well and build it locally for my testing.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [sauce-ondemand] (JENKINS-17595) Updating sauce job fails with io.filenotfoundexception

2013-04-12 Thread james.eisenha...@gmail.com (JIRA)















































james eisenhauer
 created  JENKINS-17595


Updating sauce job fails with io.filenotfoundexception















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Components:


sauce-ondemand



Created:


12/Apr/13 5:39 PM



Description:


Using 1.5.3 version

Scanning for Sauce OnDemand test data...
ERROR: Error while updating job [Ljava.lang.String;@3f013f78
java.io.FileNotFoundException: http://saucelabs.com/rest/v1/jim_hubbubhealth/jobs/f489ca8d272e443da44767c5c4bf4671
	at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1623)
	at com.saucelabs.saucerest.SauceREST.updateJobInfo(SauceREST.java:142)
	at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.getTestData(SauceOnDemandReportPublisher.java:105)
	at hudson.plugins.sauce_ondemand.SauceOnDemandReportPublisher.getTestData(SauceOnDemandReportPublisher.java:55)
	at hudson.tasks.junit.JUnitResultArchiver.perform(JUnitResultArchiver.java:149)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:798)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:770)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:720)
	at hudson.model.Run.execute(Run.java:1600)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)




Environment:


ubuntu, ec2,Jenkins 1.510




Project:


Jenkins



Priority:


Major



Reporter:


james eisenhauer

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [artifactdeployer] (JENKINS-17494) Copy Artifact fails when trying to copy artifact stored by ArtifactDeployer

2013-04-12 Thread greg.ro...@carestream.com (JIRA)















































Greg Roper
 commented on  JENKINS-17494


Copy Artifact fails when trying to copy artifact stored by ArtifactDeployer















I'm having the same issue.  I need to save the artifacts on either the slave that ran the build job or at least a machine on the local network and not across a WAN which adds a lot of time to build job.  I've tried using the ArtifactDeployer plugin, which works great, but downstream jobs using the CopyArtifact plugin are still looking to the Jenkins server for the artifacts, which is located in a different country.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-16941) Git publisher post build action fails on slave agent - unable to serialize
















































Adam PAPAI
 assigned  JENKINS-16941 to Adam PAPAI



Git publisher post build action fails on slave agent - unable to serialize
















Change By:


Adam PAPAI
(12/Apr/13 6:19 PM)




Assignee:


NicolasDeLoof
AdamPAPAI



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-16941) Git publisher post build action fails on slave agent - unable to serialize















































Adam PAPAI
 started work on  JENKINS-16941


Git publisher post build action fails on slave agent - unable to serialize
















Change By:


Adam PAPAI
(12/Apr/13 6:19 PM)




Status:


Open
InProgress



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-16941) Git publisher post build action fails on slave agent - unable to serialize















































Adam PAPAI
 commented on  JENKINS-16941


Git publisher post build action fails on slave agent - unable to serialize















This one breaks the feature. At last for us it breaks when it wants to merge the main with another branch. (so merge before build)

https://github.com/cosmin/git-plugin/commit/a7a9e3d714adc80eab8a9271c79883b6cdf7bd93



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-16941) Git publisher post build action fails on slave agent - unable to serialize













































 
Adam PAPAI
 edited a comment on  JENKINS-16941


Git publisher post build action fails on slave agent - unable to serialize
















This one breaks the feature. At last for us it breaks when it wants to merge the main with another branch. (so merge before build)

https://github.com/cosmin/git-plugin/commit/a7a9e3d714adc80eab8a9271c79883b6cdf7bd93

Try to revert it and test it on your system.

Let me know how it 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] [core] (JENKINS-17508) The 'Discard Old Builds' advanced option - removal of only artifacts - does not work for me after 1.503.

2013-04-12 Thread bal...@redlab.be (JIRA)















































Balder VC
 commented on  JENKINS-17508


The Discard Old Builds advanced option - removal of only artifacts - does not work for me after 1.503.















It seems to me that each of the modules have their own configuration file. But the tag e.g.
logRotator class="hudson.tasks.LogRotator"
daysToKeep-1/daysToKeep
numToKeep50/numToKeep
artifactDaysToKeep-1/artifactDaysToKeep
artifactNumToKeep2/artifactNumToKeep
 /logRotator
 that enables the cleanup is not propagated to these build modules configuration files. It is in the master configuration file of the job though. I think if you add logRotator to the modules config.xml they will be cleaned. I'll add it to some jobs on our Jenkins on Monday to see if that is the case.



























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







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

[JIRA] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others













































 
drnic
 edited a comment on  JENKINS-11024


Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others
















Having the same issue with -username  -password authentication.



























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







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

[JIRA] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others















































drnic
 commented on  JENKINS-11024


Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others















Having the same issue with -username/-password authentication.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [scripttrigger] (JENKINS-17091) Keep a history of script logs

2013-04-12 Thread gregory.boissi...@gmail.com (JIRA)
















































Gregory Boissinot
 resolved  JENKINS-17091 as Fixed


Keep a history of script logs
















If you look for each build, there is the build cause with a link to log





Change By:


Gregory Boissinot
(12/Apr/13 6:38 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] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others















































drnic
 commented on  JENKINS-11024


Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others















Sad panda for the 1.5 year old ticket 



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-17596) NullPointerException on project rename

2013-04-12 Thread mattrie...@gmail.com (JIRA)















































Matt Riedemann
 created  JENKINS-17596


NullPointerException on project rename















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


copyartifact



Created:


12/Apr/13 6:48 PM



Description:


When renaming a job, whether it's artifacts are copied into another job or not, I hit this NullPointerException with version 1.26 of the CopyArtifact plugin.

SEVERE: Error while serving http://esbld9.rch.stglabs.ibm.com:8080/job/test-copyartifact-plugin-rename-error/doRename
java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:616)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
	at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:29)
	at org.kohsuke.stapler.Function$InterceptedFunction.invoke(Function.java:389)
	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: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: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.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

[JIRA] [cli] (JENKINS-11024) Some commands don't work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others















































drnic
 commented on  JENKINS-11024


Some commands dont work when using _jenkins-cli.jar with -i switch, get-job and update-job for sure, not certain about others















Confirming the workaround - I toggled the Job  Read checkbox for the anonymous user and I can now run builds via the CLI and anonymous users can not see anything when they visit the jenkins URL.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [view-job-filters] (JENKINS-17597) Poor performance using ParameterFilter















































Jesse Glick
 created  JENKINS-17597


Poor performance using ParameterFilter















Issue Type:


Bug



Assignee:


Jacob Robertson



Components:


view-job-filters



Created:


12/Apr/13 7:29 PM



Description:


A user of ParameterFilter had an unresponsive UI; the thread dump revealed several HTTP handling threads (e.g. GET /) busy as follows:


at hudson.views.ParameterFilter.matchesRun(ParameterFilter.java:142)
at hudson.views.ParameterFilter.matchesBuildValue(ParameterFilter.java:129)
at hudson.views.ParameterFilter.matches(ParameterFilter.java:97)
at hudson.views.AbstractIncludeExcludeJobFilter.doFilter(AbstractIncludeExcludeJobFilter.java:68)
at hudson.views.AbstractIncludeExcludeJobFilter.filter(AbstractIncludeExcludeJobFilter.java:57)
at hudson.model.ListView.getItems(ListView.java:170)


While I am not sure whether matchAllBuilds was set in this case, inspecting the code of matchesBuildValue shows that it could be quite expensive when run against a job with hundreds or thousands of build records. This is doubly true in Jenkins 1.485+ where build records are lazily loaded, so doing a search like this could cause a great deal of activity to occur loading build.xml from disk, increasing memory as well—and soft reference eviction could mean that this needs to be done repeatedly.

Would be better for matchAllBuilds to be replaced with an int limit = 1, so that users could put a cap on how many builds would be consulted before giving up.

It may also be useful to cache information about matches, since parameters of build records should be immutable once the build is complete.




Project:


Jenkins



Labels:


performance




Priority:


Major



Reporter:


Jesse Glick

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [htmlpublisher] (JENKINS-17598) HTML Publisher Repeating Links in Left sidebar

2013-04-12 Thread muellerk...@gmail.com (JIRA)

Kevin Mueller
created JENKINS-17598

HTML Publisher Repeating Links in Left sidebar

Issue Type:

Bug

Affects Versions:

current

Assignee:

mcrooney

Attachments:

HTMLPublisherCapture.JPG

Components:

htmlpublisher

Created:

12/Apr/13 7:38 PM

Description:

A job configured with two directories that is part of a pipeline that includes the Join plugin. This job is a down stream of a parent job that is using the join plug. This job is also displayed in a pipeline view job.

The job is "Started" via the "trigger" button in the pipeline view multiple times.

The resulting build page display the html links multiple times in a repeating fashion versus just displaying the latest build. Attached is a partial screen shot.

Each time the job is trigger to run with the "trigger" icon from the pipeline view we get one more HTML link on the job page.

If the pipeline is run from the start again, the job in question correctly has only the latest html links as you expect.

Environment:

Jenkins ver. 1.4.78

Project:

Jenkins

Priority:

Major

Reporter:

Kevin Mueller

[JIRA] [core] (JENKINS-15796) NoClassDefFoundError in monitoring Windows slave















































Kevin Thieling
 reopened  JENKINS-15796


NoClassDefFoundError in monitoring Windows slave
















It looks like this exact issue is still occurring on 1.506.  It appears to only be occuring on one of our slaves however.  Any ideas?

Apr 12, 2013 9:41:05 AM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run
WARNING: Failed to monitor Build.VS6 for Free Swap Space
java.io.IOException: Remote call on Build.VS6 failed
	at hudson.remoting.Channel.call(Channel.java:681)
	at hudson.node_monitors.SwapSpaceMonitor$1.monitor(SwapSpaceMonitor.java:83)
	at hudson.node_monitors.SwapSpaceMonitor$1.monitor(SwapSpaceMonitor.java:81)
	at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:219)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jvnet.hudson.Windows$MEMORYSTATUSEX
	at org.jvnet.hudson.Windows.monitor(Windows.java:40)
	at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:109)
	at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:99)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1$1.run(Engine.java:58)
	at java.lang.Thread.run(Unknown Source)





Change By:


Kevin Thieling
(12/Apr/13 7:48 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-16845) NullPointer in getPreviousBuild















































Jesse Glick
 commented on  JENKINS-16845


NullPointer in getPreviousBuild















@christianapel: looks unrelated.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-15796) NoClassDefFoundError in monitoring Windows slave















































Jesse Glick
 commented on  JENKINS-15796


NoClassDefFoundError in monitoring Windows slave















@kt I have no idea but as the comment in the commit says there was no attempt to cause this error to not happen, only to make it be reported only once and not break other things. Check your log for the root cause. Pull requests welcome.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-15796) NoClassDefFoundError in monitoring Windows slave















































Kevin Thieling
 commented on  JENKINS-15796


NoClassDefFoundError in monitoring Windows slave















Right, got it.  Not sure if this is related or how it could be related but we are seeing this error in the log:

Email was triggered for: Success
Sending email for trigger: Success
ERROR: Could not send email as a part of the post-build publishers.
java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #77 DESC: lo=6,hi=2,size=13,size2=13
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:214)
	at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1564)
	at hudson.model.User.getProjects(User.java:448)
	at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21)
	at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101)
	at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532)
	at hudson.plugins.emailext.EmailRecipientUtils.getUserConfiguredEmail(EmailRecipientUtils.java:90)
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:518)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:304)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:296)
	at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:256)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1612)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)

This seems to only happen on jobs that build on that slave.  Other emails work jsut fine.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-15796) NoClassDefFoundError in monitoring Windows slave















































Jesse Glick
 commented on  JENKINS-15796


NoClassDefFoundError in monitoring Windows slave















@kt: that is probably unrelated: JENKINS-15652



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [email-ext] (JENKINS-17599) ERROR: Could not send email as a part of the post-build publishers.















































Kevin Thieling
 created  JENKINS-17599


ERROR: Could not send email as a part of the post-build publishers.















Issue Type:


Bug



Assignee:


Alex Earl



Components:


email-ext



Created:


12/Apr/13 8:18 PM



Description:


We are seeing this error in console output of random builds.  It happens a lot but not every time:

Email was triggered for: Success
Sending email for trigger: Success
ERROR: Could not send email as a part of the post-build publishers.
java.lang.ArrayIndexOutOfBoundsException: Assertion error: failing to load #77 DESC: lo=6,hi=2,size=13,size2=13
	at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:432)
	at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:214)
	at hudson.model.AbstractProject.hasParticipant(AbstractProject.java:1564)
	at hudson.model.User.getProjects(User.java:448)
	at hudson.scm.MailAddressResolverImpl.findMailAddressFor(MailAddressResolverImpl.java:21)
	at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:101)
	at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:532)
	at hudson.plugins.emailext.EmailRecipientUtils.getUserConfiguredEmail(EmailRecipientUtils.java:90)
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:518)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:304)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:296)
	at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:256)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1612)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)

Any ideas?




Environment:


Jenkins 1.506 with Email-ext plugin 2.27.1 running on Windows Server 2008 R2 Enterprise 64 bit, 4GB RAM, 2 3.10GHz QuadCore AMD Opteron processor 2393 SE.




Project:


Jenkins



Priority:


Major



Reporter:


Kevin Thieling

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [email-ext] (JENKINS-17599) ERROR: Could not send email as a part of the post-build publishers.

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















































Alex Earl
 commented on  JENKINS-17599


ERROR: Could not send email as a part of the post-build publishers.















This looks like an issue in core, not email-ext.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-17599) ERROR: Could not send email as a part of the post-build publishers.















































Kevin Thieling
 updated  JENKINS-17599


ERROR: Could not send email as a part of the post-build publishers.
















Change By:


Kevin Thieling
(12/Apr/13 8:22 PM)




Component/s:


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] [sauce-ondemand] (JENKINS-17595) Updating sauce job fails with io.filenotfoundexception

2013-04-12 Thread james.eisenha...@gmail.com (JIRA)
















































james eisenhauer
 assigned  JENKINS-17595 to james eisenhauer



Updating sauce job fails with io.filenotfoundexception
















Change By:


james eisenhauer
(12/Apr/13 8:46 PM)




Assignee:


KohsukeKawaguchi
jameseisenhauer



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [sauce-ondemand] (JENKINS-17595) Updating sauce job fails with io.filenotfoundexception

2013-04-12 Thread james.eisenha...@gmail.com (JIRA)
















































james eisenhauer
 resolved  JENKINS-17595 as Not A Defect


Updating sauce job fails with io.filenotfoundexception
















config issue sorry.  great job guys I love it!





Change By:


james eisenhauer
(12/Apr/13 8:47 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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







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

[JIRA] [copyartifact] (JENKINS-17600) Unable to find build for artifact copy using specific build number and current slave.jar

2013-04-12 Thread cameron.h...@boxtone.com (JIRA)















































Cameron Horn
 created  JENKINS-17600


Unable to find build for artifact copy using specific build number and current slave.jar















Issue Type:


Bug



Assignee:


Unassigned


Components:


copyartifact



Created:


12/Apr/13 8:51 PM



Description:


We are having a build that fails when passed this build selector parameter:
SpecificBuildSelector plugin="copyartifact@1.26"  buildNumber2/buildNumber/SpecificBuildSelector
like so:
Unable to find a build for artifact copy from: 7.2patch211_integrated-installer_patch

Yet passes with a parameter like this:
StatusBuildSelector plugin="copyartifact@1.26"/
like so:
Copied 17 artifacts from "7.2patch211_integrated-installer_patch" build number 2

The failures only occur for us on slaves version 2.20. Slaves with version 2.20 have been verified to work, while we have seen version 2.22 and 2.23 fail.




Environment:


Jenkins 1.510, Windows




Project:


Jenkins



Priority:


Major



Reporter:


Cameron Horn

























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







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

[JIRA] [publish-over-ftp] (JENKINS-17165) Publish over FTP plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504















































Alexander Fischer
 started work on  JENKINS-17165


Publish over FTP plugin with version 1.9 doesnt work after Jenkins upgrade to Version 1.504
















Change By:


Alexander Fischer
(12/Apr/13 9:24 PM)




Status:


Open
InProgress



























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







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

[JIRA] [publish-over-ftp] (JENKINS-17165) Publish over FTP plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504















































Alexander Fischer
 commented on  JENKINS-17165


Publish over FTP plugin with version 1.9 doesnt work after Jenkins upgrade to Version 1.504















I have resolved the problem for Publish-Over-FTP (I'm sure, the solution for Publish-Over-SSH is the same).
You have to override the method readResolve() in all inherited classes, for Publish-Over-FTP this are:

	BapFtpHostConfiguration
	BapFtpPublisherPlugin$Descriptor
The reason is, that the reflection-mechanism looks for the method readResolve() in the inherited class (see above) and after this in the base-class. The reflection-invoke of the method fails, if the method is declared in the base-class and call over the derived class.
Can I check in the patched classes on GitHub?





























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







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

[JIRA] [publish-over-ftp] (JENKINS-17165) Publish over FTP plugin with version 1.9 does'nt work after Jenkins upgrade to Version 1.504