date:20150415















































Daniel Beck
 commented on  JENKINS-27527


Jenkins API: Set upstream and downstream projects















It's asynchronous.



























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







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

[JIRA] [core] (JENKINS-27527) Jenkins API: Set upstream and downstream projects













































  
Daniel Beck
 edited a comment on  JENKINS-27527


Jenkins API: Set upstream and downstream projects
















It's asynchronous so it could take a bit to set the relation.



























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







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

[JIRA] [core] (JENKINS-27924) Concurrent jobs don't queue/execute correctly after version 1.607 with Throttle Concurrent Builds Plugin

2015-04-15 Thread kuypers.d...@googlemail.com (JIRA)















































Dirk Kuypers
 commented on  JENKINS-27924


Concurrent jobs don't queue/execute correctly after version 1.607 with Throttle Concurrent Builds Plugin















I am seeing the same issue here. Any possibility to debug via enabling some logging that might help?



























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







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

[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job

Reiner Wirtz
created JENKINS-27948

Script timeout during start of configure a jenkins job

Issue Type:

Bug

Assignee:

Unassigned

Components:

core

Created:

15/Apr/15 8:09 AM

Description:

I updated jenkins from version 1.596 to version 1.609.
No I get a script timeout if I try to configure some of the larger jobs.
I can configure small jobs without any problems.
I increase the firefox script timeout from 10 seconds to 100 seconds.
Now I can configure the jenkins jobs, but it takes a very long time to start editing.
With version 1.596 it was possible to start configuring of the same larger jobs in the predefined timout of 10 seconds

Environment:

Suse Linux 11 Sp2, Oracle Java 1.7.0_45, jenkins with internal web interface, Mozilla FireFox 37.0.1 on Windows 7

Project:

Jenkins

Labels:

jenkins
performance
configuration

Priority:

Minor

Reporter:

Reiner Wirtz

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

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

[JIRA] [artifactory-plugin] (JENKINS-27949) "off switch" for Bintray feature

2015-04-15 Thread steffen.breitb...@1und1.de (JIRA)















































Steffen Breitbach
 created  JENKINS-27949


"off switch" for Bintray feature















Issue Type:


Improvement



Assignee:


yossis



Components:


artifactory-plugin



Created:


15/Apr/15 8:19 AM



Description:


Please add a checkbox that allows the administrator to disable the Bintray feature globally.




Project:


Jenkins



Priority:


Minor



Reporter:


Steffen Breitbach

























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







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

[JIRA] [build-pipeline-plugin] (JENKINS-27878) Failure with jenkins jenkins-core-1.593 and build pipeline plugin 1.4.3 views

2015-04-15 Thread satish.si...@gmail.com (JIRA)















































satish sidda
 commented on  JENKINS-27878


Failure with jenkins jenkins-core-1.593 and build pipeline plugin 1.4.3 views















AFter uninstalling build pipeline plugin, jenkins 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/d/optout.

[JIRA] [websphere-deployer-plugin] (JENKINS-27945) Support for deployment on cluster

2015-04-15 Thread valerio.po...@gmail.com (JIRA)















































Valerio Ponte
 commented on  JENKINS-27945


Support for deployment on cluster















Opened PR (https://github.com/jenkinsci/websphere-deployer-plugin/pull/5) to close this issue. I tested the proposed patches against WAS 8.5.5 environment, both clusterized (single server cluster) and standalone.

I think it might still not work correctly on a clusterized environment with multiple application server, since I think it will install the given application only on a single node. This case needs testing to be confirmed.



























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







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

[JIRA] [websphere-deployer-plugin] (JENKINS-27945) Support for deployment on cluster

2015-04-15 Thread valerio.po...@gmail.com (JIRA)















































Valerio Ponte
 started work on  JENKINS-27945


Support for deployment on cluster
















Change By:


Valerio Ponte
(15/Apr/15 8:31 AM)




Status:


Open
In Progress



























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







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

[JIRA] [websphere-deployer-plugin] (JENKINS-27945) Support for deployment on cluster

2015-04-15 Thread valerio.po...@gmail.com (JIRA)















































Valerio Ponte
 stopped work on  JENKINS-27945


Support for deployment on cluster
















Change By:


Valerio Ponte
(15/Apr/15 8:31 AM)




Status:


In Progress
Open



























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







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

[JIRA] [pmd-plugin] (JENKINS-27950) PMD-CPD is able to generate report but execute shell marked build as failure

2015-04-15 Thread satish.si...@gmail.com (JIRA)















































satish sidda
 created  JENKINS-27950


PMD-CPD is able to generate report but execute shell marked build as failure















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


pmd-plugin



Created:


15/Apr/15 8:31 AM



Description:


+ /home/jenkins/pmd-bin-5.3.0/bin/run.sh cpd --minimum-tokens 100 
+ --files . --language cpp --format xml
Added 
Added 
Added 
Build step 'Execute shell' marked build as failure [PMD] Skipping publisher since build result is FAILURE 




Project:


Jenkins



Priority:


Major



Reporter:


satish sidda

























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







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

[JIRA] [core] (JENKINS-27527) Jenkins API: Set upstream and downstream projects

2015-04-15 Thread sverre....@gmail.com (JIRA)















































Sverre Moe
 commented on  JENKINS-27527


Jenkins API: Set upstream and downstream projects















Waited 15 minutes, still no upstream projects on the project main page. The trigger is written into the config.xml file.

Still, I created this issue because it would be great if one could set the upstream and downstream projects with the API, but it only has getters for them.



























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







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

[JIRA] [core] (JENKINS-27527) Jenkins API: Set upstream and downstream projects

2015-04-15 Thread sverre....@gmail.com (JIRA)













































  
Sverre Moe
 edited a comment on  JENKINS-27527


Jenkins API: Set upstream and downstream projects
















It took over 20 minutes for the upstream project to appear on the project main page.

Still, I created this issue because it would be great if one could set the upstream and downstream projects with the API, but it only has getters for them.



























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







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

[JIRA] [ec2-plugin] (JENKINS-27951) Additional policy statement required in documentation in order to support updating ec2 slave nodes

2015-04-15 Thread nick.jo...@gmail.com (JIRA)















































Nick Johns
 created  JENKINS-27951


Additional policy statement required in documentation in order to support updating ec2 slave nodes















Issue Type:


Task



Assignee:


Francis Upton



Components:


ec2-plugin



Created:


15/Apr/15 9:02 AM



Description:


When trying to update the number of executors on an EC2-provisioned slave, I got the stack trace:

Caused by: com.amazonaws.AmazonServiceException: You are not authorized to perform this operation. (Service: AmazonEC2; Status Code: 403; Error Code: UnauthorizedOperation; Request ID: 74362561-8527-44c1-8f5e-564831b5ce39)
	at com.amazonaws.http.AmazonHttpClient.handleErrorResponse(AmazonHttpClient.java:1078)
	at com.amazonaws.http.AmazonHttpClient.executeOneRequest(AmazonHttpClient.java:726)
	at com.amazonaws.http.AmazonHttpClient.executeHelper(AmazonHttpClient.java:461)
	at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:296)
	at com.amazonaws.services.ec2.AmazonEC2Client.invoke(AmazonEC2Client.java:10549)
	at com.amazonaws.services.ec2.AmazonEC2Client.deleteTags(AmazonEC2Client.java:2040)
	at hudson.plugins.ec2.EC2AbstractSlave.clearLiveInstancedata(EC2AbstractSlave.java:386)
	at hudson.plugins.ec2.EC2AbstractSlave.reconfigure(EC2AbstractSlave.java:263)
	at hudson.plugins.ec2.EC2OndemandSlave.reconfigure(EC2OndemandSlave.java:98)
	at hudson.model.Computer.doConfigSubmit(Computer.java:1211)
	... 80 more

I resolved this by adding

"ec2:DeleteTags",

to the policy used by Jenkins.  

The documentation needs to be updated to include this in it's example policy.




Environment:


Jenkins ver. 1.599 

ec2-plugin 1.27




Project:


Jenkins



Priority:


Major



Reporter:


Nick Johns

























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







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

[JIRA] [core] (JENKINS-27527) Jenkins API: Set upstream and downstream projects















































Daniel Beck
 commented on  JENKINS-27527


Jenkins API: Set upstream and downstream projects















This isn't how the API works. Check out how hudson.model.DependencyGraph 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/d/optout.

[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.

2015-04-15 Thread ol...@icp.uni-stuttgart.de (JIRA)















































Olaf Lenz
 commented on  JENKINS-10629


Tar implimentation can't handle > 8GB and doesn't error out.















Well done! I had started to work on it, by I had only gotten as far as writing a regression test that shows the problem. If that test is of any interest, I can provide it. Unfortunately, the test is relatively costly (time and memory). Daniel Beck suggested to put the test into the acceptance test harness, however the test is currently written as a "normal" unit test, and to my understanding, converting it to a test useful for the acceptance test harness does not work as easily. Anyway, if you are interested, have a look here:
https://github.com/olenz/jenkins/commit/4ec5b7f30a843383739f80ddf12072f93865741a



























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







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

[JIRA] [build-pipeline-plugin] (JENKINS-27878) Failure with jenkins jenkins-core-1.593 and build pipeline plugin 1.4.3 views















































Daniel Beck
 commented on  JENKINS-27878


Failure with jenkins jenkins-core-1.593 and build pipeline plugin 1.4.3 views















This is due to incomplete configuration of a Build Pipeline view. The plugin doesn't handle that gracefully.



























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







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

[JIRA] [core] (JENKINS-27924) Concurrent jobs don't queue/execute correctly after version 1.607 with Throttle Concurrent Builds Plugin
















































Daniel Beck
 resolved  JENKINS-27924 as Duplicate


Concurrent jobs don't queue/execute correctly after version 1.607 with Throttle Concurrent Builds Plugin
















Duplicates JENKINS-27708, JENKINS-27871 (or at least has the same cause)





Change By:


Daniel Beck
(15/Apr/15 9:35 AM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.

2015-04-15 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 commented on  JENKINS-10629


Tar implimentation can't handle > 8GB and doesn't error out.















@Olaf
I've also created a unit test for the issue. BTW, any additional tests (especially use-case-reproductory builds with large artefacts archiving) will be appreciated. It would be great if you finalize your test and submit a pull request to jenkins or to https://github.com/jenkinsci/acceptance-test-harness



























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







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

[JIRA] [core] (JENKINS-27925) Build step is not always saved

2015-04-15 Thread r...@kamstrup.dk (JIRA)















































Rasmus Pedersen
 commented on  JENKINS-27925


Build step is not always saved















Q: And after submitting that, the job still contains two batch build steps?
A: Yes

There's one warning in /log/all

apr. 15, 2015 11:35:51 AM org.kohsuke.stapler.RequestImpl$TypePair convertJSON
WARNING: 'stapler-class' is deprecated: hudson.tasks.Shell





























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







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

[JIRA] [core] (JENKINS-27924) Concurrent jobs don't queue/execute correctly after version 1.607 with Throttle Concurrent Builds Plugin

2015-04-15 Thread tron...@gmail.com (JIRA)















































Tadej Lasic
 commented on  JENKINS-27924


Concurrent jobs don't queue/execute correctly after version 1.607 with Throttle Concurrent Builds Plugin















Yup, JENKINS-27708 seems to be it. Waiting for 1.610.



























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







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

[JIRA] [core] (JENKINS-27925) Build step is not always saved

2015-04-15 Thread r...@kamstrup.dk (JIRA)















































Rasmus Pedersen
 commented on  JENKINS-27925


Build step is not always saved















Sorry, wrong answer. It should have been:
Q: And after submitting that, the job still contains two batch build steps?
A: It contains a shell command build step at the top and a batch build step at the bottom. It is only the content of the shell command that doesn't get saved.



























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







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

[JIRA] [sauce-ondemand-plugin] (JENKINS-27884) Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125

2015-04-15 Thread costescuand...@skymail.ro (JIRA)















































Andrei Costescu
 commented on  JENKINS-27884


Doesn't work with: Jenkins1.608 with Sauce on demand plugin 1.125















Each time I kill the hanging processes, first job succeeds then the following ones fail and 'sc' progesses linger around.
I restarted the server completely, then asked 3 sauce jobs to run (which ended up in the build queue waiting to finish one by one).

Even though only the first job was running there were two 'sc' processes running. Second and third job failed as above and now Jenkins is stale - but 'sc' processes still linger around.

Starting Sauce Connect on master node using identifier: default
Launching Sauce Connect on ***
Process count non-zero, but no active tunnels found
Process count reset to zero
FATAL: Unable to start Sauce Connect, please see the Sauce Connect log
com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager$SauceConnectDidNotStartException: Unable to start Sauce Connect, please see the Sauce Connect log
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:308)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at com.saucelabs.ci.sauceconnect.AbstractSauceTunnelManager.openConnection(AbstractSauceTunnelManager.java:305)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper$SauceConnectHandler.call(SauceOnDemandBuildWrapper.java:819)
	at hudson.plugins.sauce_ondemand.SauceOnDemandBuildWrapper.setUp(SauceOnDemandBuildWrapper.java:279)
	at hudson.model.Build$BuildExecution.doRun(Build.java:154)
(...)




























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







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

[JIRA] [promoted-builds-plugin] (JENKINS-10068) Ability to remove a Promotion on a promoted build

2015-04-15 Thread vbes...@gmail.com (JIRA)















































Besho Beshko
 commented on  JENKINS-10068


Ability to remove a Promotion on a promoted build















Had the same issue, work-around for me was to add another process "demote", which adds a different color star (red), and clean up the files that were previously "promoted".

It is a bit inconvenient, as there are now 2 stars on the promoted and then demoted builds - gold, for being promoted, and red, for been demoted and deleted. It would be useful if there is an action "remove star" or something in the promote/demote process. This way, the promote process can check and eventually remove potential red stars, and the demote process can remove potential gold stars.



























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







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

[JIRA] [core] (JENKINS-27345) Jenkins 1.599 blocked when using slave nodes

2015-04-15 Thread cosmin.giur...@tora.com (JIRA)















































Cosmin Giurgiu
 commented on  JENKINS-27345


Jenkins 1.599 blocked when using slave nodes















Hi Dani
I did not specify any custom JVM parameters. And yes, after I enabled the SSH slaves plugin it started to block.

The jenkins process params are (jps -lvm | grep jenkins):
10867 /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=10 --handlerCountMax=50 --handlerCountMaxIdle=10 --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined --simpleAccessLogger.file=/var/log/jenkins/access_log -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -Dhudson.DNSMultiCast.disabled=true -DJENKINS_HOME=/var/lib/jenkins

Do you have any idea how to fix it or what should I change in order to have more info?
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/d/optout.

[JIRA] [core] (JENKINS-27345) Jenkins 1.599 blocked when using slave nodes

2015-04-15 Thread cosmin.giur...@tora.com (JIRA)

Cosmin Giurgiu
edited a comment on JENKINS-27345

Jenkins 1.599 blocked when using slave nodes

Hi Dani
I did not specify any custom JVM parameters. And yes, after I enabled the SSH slaves plugin it started to block.

The jenkins process params are (jps -lvm | grep jenkins):
10867 /usr/lib/jenkins/jenkins.war --logfile=/var/log/jenkins/jenkins.log --webroot=/var/cache/jenkins/war --daemon --httpPort=8080 --ajp13Port=8009 --debug=10 --handlerCountMax=50 --handlerCountMaxIdle=10 --accessLoggerClassName=winstone.accesslog.SimpleAccessLogger --simpleAccessLogger.format=combined --simpleAccessLogger.file=/var/log/jenkins/access_log -Dcom.sun.akuma.Daemon=daemonized -Djava.awt.headless=true -Dhudson.DNSMultiCast.disabled=true -DJENKINS_HOME=/var/lib/jenkins

Do you have any idea how to fix it or what should I change in order to have more info?
Thanks!

NOTE:
No luck when using the latest version (1.609).

[JIRA] [conditional-buildstep-plugin] (JENKINS-27952) Scriptsecurity: match regex not permitted with conditional build step plugin

2015-04-15 Thread tom.ghyseli...@excentis.com (JIRA)















































Tom Ghyselinck
 created  JENKINS-27952


Scriptsecurity: match regex not permitted with conditional build step plugin















Issue Type:


Bug



Assignee:


Dominik Bartholdi



Components:


conditional-buildstep-plugin



Created:


15/Apr/15 10:11 AM



Description:


Hi,

We have the following configuration in a job:



"conditional-buildstep@1.3.3">
  "org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail" plugin="run-condition@1.0"/>
  "org.jenkins_ci.plugins.run_condition.core.ExpressionCondition" plugin="run-condition@1.0">
<_expression_>[24][x0-9][0-9]{2}
${TYPE}
  
  ...


When the https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin Script Security Plugin is installed, we get the following error:


SEVERE: Failed Loading job MyJob
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.ScriptBytecodeAdapter matchRegex java.lang.Object java.lang.Object
at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:164)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:100)
at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:115)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:112)
at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)
at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)
at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.callStatic(StaticMetaMethodSite.java:99)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:177)
at Script1.run(Script1.groovy:1)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:139)
at hudson.matrix.FilterScript.evaluate(FilterScript.java:45)
at hudson.matrix.FilterScript.apply(FilterScript.java:85)
at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101)
at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91)
at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:638)
at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:505)
at hudson.model.Items.load(Items.java:279)
at jenkins.model.Jenkins$17.run(Jenkins.java:2673)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:903)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)





Project:


Jenkins



Labels:


security
regex




Priority:


Major



Reporter:


Tom Ghyselinck

[JIRA] [conditional-buildstep-plugin] (JENKINS-27952) Scriptsecurity: match regex not permitted with conditional build step plugin

2015-04-15 Thread tom.ghyseli...@excentis.com (JIRA)















































Tom Ghyselinck
 updated  JENKINS-27952


Scriptsecurity: match regex not permitted with conditional build step plugin
















Change By:


Tom Ghyselinck
(15/Apr/15 10:14 AM)




Description:


Hi,We have the following configuration in a job:{code}  <_expression_>[24][x0-9][0-9]{2}${TYPE}...{code}When the [https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin Script Security Plugin] is installed, we get the following error:{code}SEVERE: Failed Loading job MyJoborg.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.ScriptBytecodeAdapter matchRegex java.lang.Object java.lang.Objectat org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:164)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:100)at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:115)at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:112)at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.callStatic(StaticMetaMethodSite.java:99)at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50)at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157)at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:177)at Script1.run(Script1.groovy:1)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:139)at hudson.matrix.FilterScript.evaluate(FilterScript.java:45)at hudson.matrix.FilterScript.apply(FilterScript.java:85)at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101)at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91)at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:638)at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:505)at hudson.model.Items.load(Items.java:279)at jenkins.model.Jenkins$17.run(Jenkins.java:2673)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$7.runTask(Jenkins.java:903)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745){code}
*Note*: The current _workaround_ is to "_Approve_" the script via [http:///scriptApproval/]



























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







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

[JIRA] [conditional-buildstep-plugin] (JENKINS-27952) Scriptsecurity: match regex not permitted with conditional build step plugin

2015-04-15 Thread tom.ghyseli...@excentis.com (JIRA)















































Tom Ghyselinck
 updated  JENKINS-27952


Scriptsecurity: match regex not permitted with conditional build step plugin
















Change By:


Tom Ghyselinck
(15/Apr/15 10:16 AM)




Environment:


Jenkins 1.596.2



























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







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

[JIRA] [matrix-combinations-parameter-plugin] (JENKINS-27953) Scriptsecurity: MatrixJob combination filter

2015-04-15 Thread tom.ghyseli...@excentis.com (JIRA)















































Tom Ghyselinck
 created  JENKINS-27953


Scriptsecurity: MatrixJob combination filter















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


matrix-combinations-parameter-plugin, matrix-project-plugin



Created:


15/Apr/15 10:18 AM



Description:


Hi,

We have the following configuration in a matrix job:


label.startsWith('i386')


When the Script Security Plugin is installed, we get the following error:


SEVERE: Failed Loading job MyJob
org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method java.lang.String startsWith java.lang.String
at org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectMethod(StaticWhitelist.java:150)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onMethodCall(SandboxInterceptor.java:77)
at org.kohsuke.groovy.sandbox.impl.Checker$1.call(Checker.java:103)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedCall(Checker.java:100)
at org.kohsuke.groovy.sandbox.impl.Checker$checkedCall.callStatic(Unknown Source)
at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50)
at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157)
at Script1.run(Script1.groovy:1)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:139)
at hudson.matrix.FilterScript.evaluate(FilterScript.java:45)
at hudson.matrix.FilterScript.apply(FilterScript.java:85)
at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101)
at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91)
at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:638)
at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:505)
at hudson.model.Items.load(Items.java:279)
at jenkins.model.Jenkins$17.run(Jenkins.java:2673)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:903)
at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)


Note: The current workaround is to "Approve" the script via http:///scriptApproval/




Environment:


Jenkins 1.596.2 LTS




Project:


Jenkins



Labels:


matrix
security




Priority:


Minor



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/d/optout.

[JIRA] [conditional-buildstep-plugin] (JENKINS-27952) Scriptsecurity: match regex not permitted with conditional build step plugin

2015-04-15 Thread tom.ghyseli...@excentis.com (JIRA)















































Tom Ghyselinck
 updated  JENKINS-27952


Scriptsecurity: match regex not permitted with conditional build step plugin
















Change By:


Tom Ghyselinck
(15/Apr/15 10:19 AM)




Environment:


Jenkins 1.596.2
 LTS





Description:


Hi,We have the following configuration in a job:{code}  <_expression_>[24][x0-9][0-9]{2}${TYPE}...{code}When the [
Script Security Plugin|
https://wiki.jenkins-ci.org/display/JENKINS/Script+Security+Plugin
 Script Security Plugin
] is installed, we get the following error:{code}SEVERE: Failed Loading job MyJoborg.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use staticMethod org.codehaus.groovy.runtime.ScriptBytecodeAdapter matchRegex java.lang.Object java.lang.Objectat org.jenkinsci.plugins.scriptsecurity.sandbox.whitelists.StaticWhitelist.rejectStaticMethod(StaticWhitelist.java:164)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onStaticCall(SandboxInterceptor.java:100)at org.kohsuke.groovy.sandbox.impl.Checker$2.call(Checker.java:115)at org.kohsuke.groovy.sandbox.impl.Checker.checkedStaticCall(Checker.java:112)at sun.reflect.GeneratedMethodAccessor108.invoke(Unknown Source)at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)at java.lang.reflect.Method.invoke(Method.java:606)at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:90)at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:233)at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.invoke(StaticMetaMethodSite.java:43)at org.codehaus.groovy.runtime.callsite.StaticMetaMethodSite.callStatic(StaticMetaMethodSite.java:99)at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallStatic(CallSiteArray.java:50)at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:157)at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callStatic(AbstractCallSite.java:177)at Script1.run(Script1.groovy:1)at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.run(GroovySandbox.java:139)at hudson.matrix.FilterScript.evaluate(FilterScript.java:45)at hudson.matrix.FilterScript.apply(FilterScript.java:85)at hudson.matrix.Combination.evalGroovyExpression(Combination.java:101)at hudson.matrix.Combination.evalGroovyExpression(Combination.java:91)at hudson.matrix.MatrixProject.rebuildConfigurations(MatrixProject.java:638)at hudson.matrix.MatrixProject.onLoad(MatrixProject.java:505)at hudson.model.Items.load(Items.java:279)at jenkins.model.Jenkins$17.run(Jenkins.java:2673)at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)at jenkins.model.Jenkins$7.runTask(Jenkins.java:903)at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at java.lang.Thread.run(Thread.java:745){code}*Note*: The current _workaround_ is to "_Approve_" the script via [http:///scriptApproval/]



























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







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

[JIRA] [subversion-plugin] (JENKINS-25070) Subversion fails to update externals once after external is changed.

2015-04-15 Thread sgannon...@gmail.com (JIRA)















































Shane Gannon
 commented on  JENKINS-25070


Subversion fails to update externals once after external is changed.















It seems that nowadays the solution to https://issues.jenkins-ci.org/browse/JENKINS-21785 also resolves this problem. i.e. Set addition credentials with the correct realm name format. e.g.  ID. You can find the correct authentication realm name by using "svn --no-auth-cache --config-dir invalid info https://my-server-url.com/trunk". 

However this did not originally work for us. Not sure why it's working now. We upgraded the svn plugin to 2.5 then downgraded to 2.3. This may have had an impact. We also upgraded our version of Jenkins,

This defect can be marked as resolved.



























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







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

[JIRA] [envinject-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable

2015-04-15 Thread david.ru...@seebyte.com (JIRA)















































David Rubio
 commented on  JENKINS-13348


EnvInject overriding WORKSPACE variable















Same problem detected with EnvInject 1.91.1 and Jenkins 1.609. Version 1.90 does not have the problem



























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







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

[JIRA] [envinject-plugin] (JENKINS-13348) EnvInject overriding WORKSPACE variable

2015-04-15 Thread david.ru...@seebyte.com (JIRA)













































  
David Rubio
 edited a comment on  JENKINS-13348


EnvInject overriding WORKSPACE variable
















Similar problem detected with EnvInject 1.91.1 and Jenkins 1.609. Version 1.90 does not have the problem

For some reason the Path env variable is not updated but java.library.path is. When you try to build, it looks in the old path



























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







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

[JIRA] [clamav-plugin] (JENKINS-27954) Scan fail for "Too many open files"

2015-04-15 Thread fabio.farron...@lispa.it (JIRA)















































fabio farronato
 created  JENKINS-27954


Scan fail for "Too many open files"















Issue Type:


Bug



Assignee:


sogabe



Components:


clamav-plugin



Created:


15/Apr/15 10:53 AM



Description:


During scan of workspace, with a large number of files, ClamAvRecorder abort scan whith Error:

ERROR: Publisher org.jenkinsci.plugins.clamav.ClamAvRecorder aborted due to exception
java.io.FileNotFoundException: /home/sonar/.jenkins/jobs/PJ-PORT_PCPLS/workspace/proj/target/test-classes/generated/RESPONSE$DATA$CPLCOMANDOPL.class (Too many open files)
	at java.io.FileInputStream.open(Native Method)
	at java.io.FileInputStream.(FileInputStream.java:146)
	at hudson.FilePath.read(FilePath.java:1739)
	at org.jenkinsci.plugins.clamav.ClamAvRecorder.perform(ClamAvRecorder.java:117)
	at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683)
	at hudson.model.Run.execute(Run.java:1784)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)


I analyzed the source code and suggest you to manage the file's close() at

ClamAvScanner.java:97 with insert a finally block.


public ScanResult scan(InputStream file) {
if (file == null) {
throw new IllegalArgumentException("file is null.");
}
String response;
try {
response = instream(file);
} catch (IOException e) {
return new ScanResult(Status.WARNING, e.getMessage());
} finally {
...
file.close();
...
}
if (response.contains("FOUND\0")) {
String sig = response.substring("stream: ".length(), response.lastIndexOf("FOUND") - 1);
return new ScanResult(Status.INFECTED, sig);
}
return new ScanResult(Status.PASSED);
}





Environment:


Jenkins ver. 1.596.1

ClamAV Plugin 0.2.1

apache-tomcat-6.0.39

java version jdk1.7.0_55




Project:


Jenkins



Priority:


Major



Reporter:


fabio farronato

























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







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

[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.

2015-04-15 Thread ol...@icp.uni-stuttgart.de (JIRA)















































Olaf Lenz
 commented on  JENKINS-10629


Tar implimentation can't handle > 8GB and doesn't error out.















The trouble with the acceptance test harness is, that it would mean I first have to create a >8GB file in a job, then archive it, and finally download it to compare it. In sum, the test would require more than 24GB of disk space, even if it could be deleted afterwards. At the moment, the system were I develop Jenkins doesn't have that much free space... ;-(



























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







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

[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.

2015-04-15 Thread gentoo.inte...@gmail.com (JIRA)















































Kanstantsin Shautsou
 commented on  JENKINS-10629


Tar implimentation can't handle > 8GB and doesn't error out.















Do you know fallocate?



























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







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

[JIRA] [fitnesse-plugin] (JENKINS-27955) Add ability to define fitnesse port as enironment variable

2015-04-15 Thread voodoo...@yandex.ru (JIRA)















































Aleksey Alekseev
 created  JENKINS-27955


Add ability to define fitnesse port as enironment variable















Issue Type:


Bug



Assignee:


Unassigned


Components:


fitnesse-plugin



Created:


15/Apr/15 11:08 AM



Description:


if we set fitnesse port as ${SOME_VAR} we get validation form error. Sometimes it will be helpfull to define port as var (if you have a lot of fitnesse instances) 




Environment:


fitnesse plugin 1.12




Project:


Jenkins



Priority:


Major



Reporter:


Aleksey Alekseev

























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







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

[JIRA] [core] (JENKINS-26781) regression resolving Descriptor using "$class" vs "kind"















































SCM/JIRA link daemon
 commented on  JENKINS-26781


regression resolving Descriptor using "$class" vs "kind"















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/jenkins/model/Jenkins.java
 core/src/main/java/jenkins/security/NonSerializableSecurityContext.java
http://jenkins-ci.org/commit/jenkins/f3070d940c0e7655a50fc041e74d29a8e5ca2139
Log:
  Merge branch 'master' into JENKINS-26781


Compare: https://github.com/jenkinsci/jenkins/compare/f4ddac10838b...f3070d940c0e




























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







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

[JIRA] [core] (JENKINS-26781) regression resolving Descriptor using "$class" vs "kind"















































SCM/JIRA link daemon
 commented on  JENKINS-26781


regression resolving Descriptor using "$class" vs "kind"















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/model/Descriptor.java
 core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java
 core/src/main/resources/lib/form/class-entry.jelly
http://jenkins-ci.org/commit/jenkins/724df641168aa3a213d3322561782a1ba12b2ebd
Log:
  Merge remote-tracking branch 'origin/JENKINS-26781' into JENKINS-26781





























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







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

[JIRA] [core] (JENKINS-26781) regression resolving Descriptor using "$class" vs "kind"

2015-04-15 Thread jgl...@cloudbees.com (JIRA)
















































Jesse Glick
 resolved  JENKINS-26781 as Fixed


regression resolving Descriptor using "$class" vs "kind"
















Change By:


Jesse Glick
(15/Apr/15 11:18 AM)




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/d/optout.

[JIRA] [core] (JENKINS-26781) regression resolving Descriptor using "$class" vs "kind"















































SCM/JIRA link daemon
 commented on  JENKINS-26781


regression resolving Descriptor using "$class" vs "kind"















Code changed in jenkins
User: Jesse Glick
Path:
 test/src/test/java/hudson/model/DescriptorTest.java
http://jenkins-ci.org/commit/jenkins/33041903ab67c3e32959b7b78e557ffb7d4ecd16
Log:
  JENKINS-26781 Reproduced problem in test.
Besides failing in master, it also fails in 4e0af43 (merge of #1443), but passes in the 1.598-SNAPSHOT parent 239caf8.





























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







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

[JIRA] [core] (JENKINS-26781) regression resolving Descriptor using "$class" vs "kind"

2015-04-15 Thread charles.bouchard-leg...@frimastudio.com (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-26781


regression resolving Descriptor using "$class" vs "kind"















Code changed in jenkins
User: Jesse Glick
Path:
 changelog.html
 core/src/main/java/hudson/DescriptorExtensionList.java
 core/src/main/java/hudson/model/ComputerSet.java
 core/src/main/java/hudson/model/Descriptor.java
 core/src/main/java/hudson/model/Items.java
 core/src/main/java/hudson/tools/DownloadFromUrlInstaller.java
 core/src/main/java/hudson/tools/ToolLocationNodeProperty.java
 core/src/main/java/hudson/util/DescriptorList.java
 core/src/main/resources/lib/form/class-entry.jelly
 test/src/test/java/hudson/model/DescriptorTest.java
http://jenkins-ci.org/commit/jenkins/b688047877cf6b735ee17cd3d22436f5b4219b03
Log:
  JENKINS-26781 Merging #1563.


Compare: https://github.com/jenkinsci/jenkins/compare/bc8c0dfe0302...b688047877cf




























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







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

[JIRA] [global-build-stats-plugin] (JENKINS-27956) Jenkins Global Build Search - Cannot choose start date end date

2015-04-15 Thread narayanpradhan7...@gmail.com (JIRA)















































NARAYAN PRADHAN
 created  JENKINS-27956


Jenkins Global Build Search - Cannot choose start date end date















Issue Type:


Bug



Assignee:


Frédéric Camblor



Components:


global-build-stats-plugin



Created:


15/Apr/15 11:50 AM



Description:


Jenkins Global Build Search - Cannot able choose start date end date, as calender not apearing. tried with different browser (chrome, Firefox & IE)
collected some error trace with IE, following error is visible

===
Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3)
Timestamp: Wed, 15 Apr 2015 11:47:54 UTC


Message: Expected ';'
Line: 21
Char: 40
Code: 0
URI: http://subl655.na.mscsoftware.com:9000/jenkins/plugin/global-build-stats/buildHistory?jobFilter=ALL&start=1427353249320&end=1427439649320&successShown=true&failuresShown=false&unstablesShown=false&abortedShown=false�BuildShown=false&nodeFilter=ALL&launcherFilter=ALL"http://subl655:9000/jenkins/plugin/global-build-stats/buildHistory?jobFilter=ALL&start=1427353249320&end=1427439649320&successShown=true&failuresShown=false&unstablesShown=false&abortedShown=false�BuildShown=false&nodeFilter=ALL&launcherFilter=ALL


Message: 'FIELD_FILTER_REGEX' is undefined
Line: 49
Char: 5
Code: 0
URI: http://subl655.na.mscsoftware.com:9000/jenkins/plugin/global-build-stats/buildHistory?jobFilter=ALL&start=1427353249320&end=1427439649320&successShown=true&failuresShown=false&unstablesShown=false&abortedShown=false�BuildShown=false&nodeFilter=ALL&launcherFilter=ALL"http://subl655:9000/jenkins/plugin/global-build-stats/buildHistory?jobFilter=ALL&start=1427353249320&end=1427439649320&successShown=true&failuresShown=false&unstablesShown=false&abortedShown=false�BuildShown=false&nodeFilter=ALL&launcherFilter=ALL


Message: Object doesn't support this property or method
Line: 392
Char: 9
Code: 0
URI: http://subl655.na.mscsoftware.com:9000/jenkins/static/38cbf099/scripts/hudson-behavior.js


Message: Object doesn't support this property or method
Line: 8
Char: 403
Code: 0
URI: http://subl655.na.mscsoftware.com:9000/jenkins/static/38cbf099/scripts/yui/dom/dom-min.js





Environment:


OS:RHEL5.4 ; x86_64 GNU/Linux 

java version "1.7.0_80-ea" 

Server version: Apache Tomcat/8.0.15 

Server built: Nov 2 2014 19:25:20 UTC 

Server number: 8.0.15.0 

OS Name: Linux 

OS Version: 2.6.18-164.el5 

Architecture: amd64 

JVM Version: 1.7.0_80-ea-b03 

JVM Vendor: Oracle Corporation 

 

Browser : Chrome 

= 

Jenkins ver. 1.580.3




Project:


Jenkins



Priority:


Major



Reporter:


NARAYAN PRADHAN

























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







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

[JIRA] [unity3d-plugin] (JENKINS-27738) Build does not stop when build step is over

2015-04-15 Thread lacos...@java.net (JIRA)















































lacostej
 commented on  JENKINS-27738


Build does not stop when build step is over















Charles, I wonder if you could the latest version (0.7) and your previous logFile argument to see if the job stops properly (the job might not find the log though). 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/d/optout.

[JIRA] [clamav-plugin] (JENKINS-27954) Scan fail for "Too many open files"

2015-04-15 Thread s.sog...@gmail.com (JIRA)















































sogabe
 started work on  JENKINS-27954


Scan fail for "Too many open files"
















Change By:


sogabe
(15/Apr/15 11:59 AM)




Status:


Open
In Progress



























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







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

[JIRA] [unity3d-plugin] (JENKINS-27738) Build does not stop when build step is over















































Charles Bouchard-Légaré
 commented on  JENKINS-27738


Build does not stop when build step is over















Tested it and got this error, which seams the expected behavior.  Thanks !


WARNING: No change detected to Editor.log path: '/Users/cblegare/Settings-Log.txt'.
   The unity3d plugin was probably unable to find it in its expected locations (see JENKINS-24265).
   Consider using the -logFile argument to force a known editor.log path or report the issue.
FATAL: Unity3d command line execution failed with status 1




























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







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

[JIRA] [subversion-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy

2015-04-15 Thread tel...@gmail.com (JIRA)















































Telmah
 commented on  JENKINS-26458


org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy















+1



























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







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

[JIRA] [core] (JENKINS-26781) regression resolving Descriptor using "$class" vs "kind"

2015-04-15 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-26781


regression resolving Descriptor using "$class" vs "kind"















Integrated in  jenkins_main_trunk #4085
 JENKINS-26781 lookup descriptor by ID, then by class if explicitly set (Revision 8881703f7c7351695c5d5b2662faefae60de68e8)
JENKINS-26781 Reproduced problem in test. (Revision 33041903ab67c3e32959b7b78e557ffb7d4ecd16)

 Result = SUCCESS
nicolas de loof : 8881703f7c7351695c5d5b2662faefae60de68e8
Files : 

	core/src/main/resources/lib/form/class-entry.jelly
	core/src/main/java/hudson/model/Descriptor.java



jesse glick : 33041903ab67c3e32959b7b78e557ffb7d4ecd16
Files : 

	test/src/test/java/hudson/model/DescriptorTest.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/d/optout.

[JIRA] [core] (JENKINS-10629) Tar implimentation can't handle > 8GB and doesn't error out.

2015-04-15 Thread ol...@icp.uni-stuttgart.de (JIRA)















































Olaf Lenz
 commented on  JENKINS-10629


Tar implimentation can't handle > 8GB and doesn't error out.















How portable is fallocate? Also, this helps to make the creation of the file fast, but it does not reduce the disk space requirements, does it?



























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







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

[JIRA] [notification-plugin] (JENKINS-27323) Out of index error with logLines defaulting to 0

2015-04-15 Thread has...@free.fr (JIRA)















































Antoine Musso
 commented on  JENKINS-27323


Out of index error with logLines defaulting to 0















We have the same issue after upgrading from 1.7 to 1.9 our downstream bug is https://phabricator.wikimedia.org/T93321



























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







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

[JIRA] [core] (JENKINS-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value

2015-04-15 Thread swapnilvkot...@gmail.com (JIRA)















































Swapnil Kotwal
 commented on  JENKINS-26520


Environment Variables BUILD_ID and BUILD_NUMBER now return the same value















I have installed zentimestamp-plugin and trying to get build execution time in email notifications.
I used Zentimestamp plugin and using env variable BUILD_TIMESTAMP using following ways but not able to get actual time stamp value


${BUILD_TIMESTAMP}
$BUILD_TIMESTAMP
BUILD_TIMESTAMP



Somebody Please answer here ? http://stackoverflow.com/questions/29580315/jenkins-how-to-use-zentimestamp-plugin-to-get-build-execution-time



























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







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

[JIRA] [global-build-stats-plugin] (JENKINS-27956) Jenkins Global Build Search - Cannot choose start date end date

2015-04-15 Thread narayanpradhan7...@gmail.com (JIRA)















































NARAYAN PRADHAN
 updated  JENKINS-27956


Jenkins Global Build Search - Cannot choose start date end date
















Change By:


NARAYAN PRADHAN
(15/Apr/15 12:53 PM)




Description:


Jenkins Global Build Search - Cannot able choose start date end date, as calender not apearing. tried with different browser (chrome, Firefox & IE)collected some error trace with IE, following error is visible===Webpage error detailsUser Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3)Timestamp: Wed, 15 Apr 2015 11:47:54 UTCMessage: Expected ';'Line: 21Char: 40Code: 0URI: http://
subl655
xxx
.
na.mscsoftware.
com:9000/jenkins/plugin/global-build-stats/buildHistory?jobFilter=ALL&start=1427353249320&end=1427439649320&successShown=true&failuresShown=false&unstablesShown=false&abortedShown=false�BuildShown=false&nodeFilter=ALL&launcherFilter=ALL"http://
subl655
xxx
:9000/jenkins/plugin/global-build-stats/buildHistory?jobFilter=ALL&start=1427353249320&end=1427439649320&successShown=true&failuresShown=false&unstablesShown=false&abortedShown=false�BuildShown=false&nodeFilter=ALL&launcherFilter=ALLMessage: 'FIELD_FILTER_REGEX' is undefinedLine: 49Char: 5Code: 0URI: http://
subl655.na.mscsoftware.com
xxx
:9000/jenkins/plugin/global-build-stats/buildHistory?jobFilter=ALL&start=1427353249320&end=1427439649320&successShown=true&failuresShown=false&unstablesShown=false&abortedShown=false�BuildShown=false&nodeFilter=ALL&launcherFilter=ALL"http://
subl655
xxx
:9000/jenkins/plugin/global-build-stats/buildHistory?jobFilter=ALL&start=1427353249320&end=1427439649320&successShown=true&failuresShown=false&unstablesShown=false&abortedShown=false�BuildShown=false&nodeFilter=ALL&launcherFilter=ALLMessage: Object doesn't support this property or methodLine: 392Char: 9Code: 0URI: http://
subl655.na.mscsoftware.com
xxx
:9000/jenkins/static/38cbf099/scripts/hudson-behavior.jsMessage: Object doesn't support this property or methodLine: 8Char: 403Code: 0URI: http://
subl655.na.mscsoftware.com
xxx
:9000/jenkins/static/38cbf099/scripts/yui/dom/dom-min.js



























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







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

[JIRA] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository

2015-04-15 Thread david.is...@gmail.com (JIRA)















































David Ishee
 commented on  JENKINS-20263


Artifact Resolver does not retrieve the latest version from central Maven Repository















I lost hours of work trying to figure out why my upgrade jobs weren't installing the latest code. Now I'm manually deleting the localRepositoryDirectory to make workaround this bug. 



























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







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

[JIRA] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository

2015-04-15 Thread david.is...@gmail.com (JIRA)













































  
David Ishee
 edited a comment on  JENKINS-20263


Artifact Resolver does not retrieve the latest version from central Maven Repository
















I lost hours of work trying to figure out why my upgrade jobs weren't installing the latest code. Now I'm manually deleting the localRepositoryDirectory to workaround this bug. 



























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







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

[JIRA] [artifactory-plugin] (JENKINS-27840) Bintray href anchor link in Jenkins invalid

2015-04-15 Thread emiro...@yandex.com (JIRA)
















































Emir Ozer
 assigned  JENKINS-27840 to Emir Ozer



Bintray href anchor link in Jenkins invalid
















Change By:


Emir Ozer
(15/Apr/15 12:25 PM)




Assignee:


yossis
Emir Ozer



























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







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

[JIRA] [core] (JENKINS-27739) Changes to slave environment variables are ignored by master

2015-04-15 Thread funee...@yahoo.com (JIRA)















































marlene cote
 commented on  JENKINS-27739


Changes to slave environment variables are ignored by master















we are seeing the same behavior, although I did not try to delete the slave and recreate it.  We keep having to restart the jenkins server.  I also tried to uninstall the envinject plugin, but we have a multijob plugin that depends on it.  When I restarted jenkins server, none of my jobs would load due to the missing envinject plugin, so I had to reinstall it.  



























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







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

[JIRA] [artifactory-plugin] (JENKINS-27840) Bintray href anchor link in Jenkins invalid

2015-04-15 Thread emiro...@yandex.com (JIRA)
















































Emir Ozer
 resolved  JENKINS-27840 as Fixed


Bintray href anchor link in Jenkins invalid
















https://github.com/jenkinsci/artifactory-plugin/pull/15





Change By:


Emir Ozer
(15/Apr/15 12:27 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-22641) Jenkins no longer kills running processes after job fails















































SCM/JIRA link daemon
 commented on  JENKINS-22641


Jenkins no longer kills running processes after job fails















Code changed in jenkins
User: Jesse Glick
Path:
 pom.xml
 src/test/java/org/jenkinsci/plugins/durabletask/BourneShellScriptTest.java
http://jenkins-ci.org/commit/durable-task-plugin/fc48f447763cb69d6ebf7c67e54e476d9e903bbd
Log:
  Added test for stop.
JENKINS-22641 means that this does not work in 1.554.3, so need to bump up the dependency to 1.565.3.





























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







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

[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job















































Daniel Beck
 commented on  JENKINS-27948


Script timeout during start of configure a jenkins job















Please provide a list of installed plugins and their versions, as well as a sample config.xml of such a 'large job'.



























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







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

[JIRA] [core] (JENKINS-27937) Archives of Workspaces / Artifacts don't preserve extended attributes (like 'executable') although the Zip format supports it















































Daniel Beck
 commented on  JENKINS-27937


Archives of Workspaces / Artifacts don't preserve extended attributes (like 'executable') although the Zip format supports it















Permissions are not extended attributes.



























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







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

[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?

2015-04-15 Thread dfrancoeu...@gmail.com (JIRA)













































  
David Francoeur
 edited a comment on  JENKINS-27456


Emulator can't connect to adb server!?
















I am having the exact same issue. It used to work once in a while, but now it just doesn't work. The adb will try to connect forever until the build times out.

The only I can get it to work is by connecting to the CI server, killing all instance of the adb

killall adb


The next adb connect will start the daemon and successfully connect to it.


Android emulator plugin version : 	2.13
Jenkins version :   1.609

Emulator using arm-android-22 image with default hardware.




Started by user anonymous
Building in workspace /var/lib/jenkins/.jenkins/jobs/android-sdk-test/workspace
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git
 > git init /var/lib/jenkins/.jenkins/jobs/android-sdk-test/workspace # timeout=10
Fetching upstream changes from git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
 > git clean -fdx # timeout=10
Fetching upstream changes from git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git
 > git -c core.askpass=true fetch --tags --progress git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1dc350b59e44e24b5746bf28d5e824514076c913 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1dc350b59e44e24b5746bf28d5e824514076c913
 > git rev-list 1dc350b59e44e24b5746bf28d5e824514076c913 # timeout=10
$ /var/lib/jenkins/android-sdk/tools/android list target
[android] Using Android SDK: /var/lib/jenkins/android-sdk
$ /var/lib/jenkins/android-sdk/platform-tools/adb start-server
* daemon not running. starting it now on port 6607 *
* daemon started successfully *
$ /var/lib/jenkins/android-sdk/platform-tools/adb start-server
[android] Starting Android emulator
$ /var/lib/jenkins/android-sdk/tools/emulator -no-boot-anim -ports 6605,6606 -avd android-22-arm -no-snapshot-load -no-snapshot-save -no-window
Failed to open lib64EGL_translator
Failed to init_egl_dispatch
emulator: ERROR: OpenGLES initialization failed!
emulator: ERROR: OpenGLES emulation library could not be initialized!
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
emulator: warning: opening audio output failed

$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
connected to localhost:6606
[android] Waiting for emulator to finish booting...
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb disconnect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb disconnect localhost:6606
$ /var/lib/jenkins/andro

[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?

2015-04-15 Thread dfrancoeu...@gmail.com (JIRA)















































David Francoeur
 commented on  JENKINS-27456


Emulator can't connect to adb server!?















I am having the exact same issue. It used to work once in a while, but now it just doesn't work. The adb will try to connect forever until the build times out.

The only I can get it to work is by connecting to the CI server, killing all instance of the adb

killall adb


The next adb connect will start the daemon and successfully connect to it.


Android emulator plugin version : 	2.13
Jenkins version :   1.609

Emulator using arm-android-22 image with default hardware.




Started by user anonymous
Building in workspace /var/lib/jenkins/.jenkins/jobs/android-sdk-test/workspace
Wiping out workspace first.
Cloning the remote Git repository
Cloning repository git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git
 > git init /var/lib/jenkins/.jenkins/jobs/android-sdk-test/workspace # timeout=10
Fetching upstream changes from git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git +refs/heads/*:refs/remotes/origin/*
 > git config remote.origin.url git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git # timeout=10
 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
 > git config remote.origin.url git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
No valid HEAD. Skipping the resetting
 > git clean -fdx # timeout=10
Fetching upstream changes from git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git
 > git -c core.askpass=true fetch --tags --progress git...@git-lab1.mtl.mnubo.com:mnubo/sdk-android-test.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse refs/remotes/origin/master^{commit} # timeout=10
 > git rev-parse refs/remotes/origin/origin/master^{commit} # timeout=10
Checking out Revision 1dc350b59e44e24b5746bf28d5e824514076c913 (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 1dc350b59e44e24b5746bf28d5e824514076c913
 > git rev-list 1dc350b59e44e24b5746bf28d5e824514076c913 # timeout=10
$ /var/lib/jenkins/android-sdk/tools/android list target
[android] Using Android SDK: /var/lib/jenkins/android-sdk
$ /var/lib/jenkins/android-sdk/platform-tools/adb start-server
* daemon not running. starting it now on port 6607 *
* daemon started successfully *
$ /var/lib/jenkins/android-sdk/platform-tools/adb start-server
[android] Starting Android emulator
$ /var/lib/jenkins/android-sdk/tools/emulator -no-boot-anim -ports 6605,6606 -avd android-22-arm -no-snapshot-load -no-snapshot-save -no-window
Failed to open lib64EGL_translator
Failed to init_egl_dispatch
emulator: ERROR: OpenGLES initialization failed!
emulator: ERROR: OpenGLES emulation library could not be initialized!
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
emulator: warning: opening audio output failed

$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
connected to localhost:6606
[android] Waiting for emulator to finish booting...
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb disconnect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb disconnect localhost:6606
$ /var/lib/jenkins/android-sd

[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?

2015-04-15 Thread dfrancoeu...@gmail.com (JIRA)













































  
David Francoeur
 edited a comment on  JENKINS-27456


Emulator can't connect to adb server!?
















I am having the exact same issue. It used to work once in a while, but now it just doesn't work. The adb will try to connect forever until the build times out.

The only I can get it to work is by connecting to the CI server, killing all instance of the adb

killall adb


The next adb connect will start the daemon and successfully connect to it.


Android emulator plugin version : 	2.13
Jenkins version :   1.609

Emulator using arm-android-22 image with default hardware.




[android] Using Android SDK: /var/lib/jenkins/android-sdk
$ /var/lib/jenkins/android-sdk/platform-tools/adb start-server
* daemon not running. starting it now on port 6607 *
* daemon started successfully *
$ /var/lib/jenkins/android-sdk/platform-tools/adb start-server
[android] Starting Android emulator
$ /var/lib/jenkins/android-sdk/tools/emulator -no-boot-anim -ports 6605,6606 -avd android-22-arm -no-snapshot-load -no-snapshot-save -no-window
Failed to open lib64EGL_translator
Failed to init_egl_dispatch
emulator: ERROR: OpenGLES initialization failed!
emulator: ERROR: OpenGLES emulation library could not be initialized!
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.
emulator: warning: opening audio output failed

$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
connected to localhost:6606
[android] Waiting for emulator to finish booting...
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb disconnect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb disconnect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb disconnect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device offline
$ /var/lib/jenkins/android-sdk/platform-tools/adb disconnect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606 
/// ISSUED A killall adb RIGHT HERE
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
error: device not found
$ /var/lib/jenkins/android-sdk/platform-tools/adb connect localhost:6606
$ /var/lib/jenkins/android-sdk/platform-tools/adb -s localhost:6606 shell getprop init.svc.bootanim
$ /var/l

[JIRA] [core] (JENKINS-27957) NullPointerException in AdvancedQueueSorter

2015-04-15 Thread tom.ghyseli...@excentis.com (JIRA)















































Tom Ghyselinck
 created  JENKINS-27957


NullPointerException in AdvancedQueueSorter















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


15/Apr/15 1:56 PM



Description:


Hi,

Our Jenkins server seems to get locked at some point in time.
Many Jobs are in starvation, waiting for nodes with certain labels/label combinations.
(i.e. Waiting for next available executor on ...)

The log shows a lot of these entries:

Apr 15, 2015 3:44:25 PM SEVERE hudson.triggers.SafeTimerTask run

Timer task hudson.model.Queue$MaintainTask@5d00189f failed
java.lang.NullPointerException
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:99)
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:81)
	at java.util.TimSort.countRunAndMakeAscending(TimSort.java:329)
	at java.util.TimSort.sort(TimSort.java:189)
	at java.util.TimSort.sort(TimSort.java:173)
	at java.util.Arrays.sort(Arrays.java:659)
	at java.util.Collections.sort(Collections.java:217)
	at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:81)
	at hudson.model.Queue.maintain(Queue.java:1135)
	at hudson.model.Queue$MaintainTask.doRun(Queue.java:2197)
	at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)

Feed





Environment:


Jenkins 1.596.2 LTS




Project:


Jenkins



Labels:


trigger
core
queue




Priority:


Critical



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/d/optout.

[JIRA] [core] (JENKINS-27937) Archives of Workspaces / Artifacts don't preserve external attributes (like 'executable') although the Zip format supports it

2015-04-15 Thread count-jenk...@flatline.de (JIRA)















































Andreas Kotes
 updated  JENKINS-27937


Archives of Workspaces / Artifacts don't preserve external attributes (like 'executable') although the Zip format supports it
















Updated to read 'external' instead of 'extended' attributes, along with reference documentation.





Change By:


Andreas Kotes
(15/Apr/15 1:56 PM)




Summary:


Archives of Workspaces / Artifacts don't preserve
 extended
 external
 attributes (like 'executable') although the Zip format supports it





Description:


Zips would support including
 extended
 external
 attributes like the executable bit of files - this currently isn't done, so when a zipfile of a folder is downloaded, shell scripts stop being executable after unzipping :(
See https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT sections 4.3.12 & 4.4.15 as well as http://www.forensicswiki.org/wiki/Zip#External_file_attributes



























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







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

[JIRA] [next-build-number-plugin] (JENKINS-27958) Cannot reset the next build number

2015-04-15 Thread testingk...@gmail.com (JIRA)















































Maninder Singh
 created  JENKINS-27958


Cannot reset the next build number















Issue Type:


Bug



Assignee:


Dean Yu



Components:


next-build-number-plugin



Created:


15/Apr/15 1:58 PM



Description:


On Google Chrome set the next build number but it turned out to be not working the next build number remains the same.

About Jenkins 1.609
Next Build Number Plugin 1.1




Environment:


About Jenkins 1.609

Next Build Number Plugin 1.1




Project:


Jenkins



Priority:


Major



Reporter:


Maninder Singh

























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







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

[JIRA] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label

2015-04-15 Thread efa...@april.org (JIRA)















































Habeeb FKR
 commented on  JENKINS-23459


Cannot restrict a matrix build job to one node/label















Hello @Reiner Writz

Where have you put your script to force execution in the master ?

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/d/optout.

[JIRA] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label

2015-04-15 Thread efa...@april.org (JIRA)















































Habeeb FKR
 commented on  JENKINS-23459


Cannot restrict a matrix build job to one node/label















Hello @Reiner Writz

Where have you put your script to force execution in the master ?

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/d/optout.

[JIRA] [unity3d-plugin] (JENKINS-27738) Build does not stop when build step is over

2015-04-15 Thread lacos...@java.net (JIRA)
















































lacostej
 closed  JENKINS-27738 as Duplicate


Build does not stop when build step is over
















Change By:


lacostej
(15/Apr/15 2:07 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [unity3d-plugin] (JENKINS-27738) Build does not stop when build step is over

2015-04-15 Thread lacos...@java.net (JIRA)















































lacostej
 commented on  JENKINS-27738


Build does not stop when build step is over















Thanks. Really appreciated.



























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







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

[JIRA] [pretested-integration-plugin] (JENKINS-27516) Plugin hangs - reproduced with failed earlier build (Praqma case 12906)















































SCM/JIRA link daemon
 commented on  JENKINS-27516


Plugin hangs - reproduced with failed earlier build (Praqma case 12906)















Code changed in jenkins
User: Mads Nielsen
Path:
 pom.xml
 src/main/java/org/jenkinsci/plugins/pretestedintegration/PretestedIntegrationBuildWrapper.java
http://jenkins-ci.org/commit/pretested-integration-plugin/effcecf63a08fd3dc4c944b6e24cb166b4e1a19f
Log:
  For JENKINS-27516, remove semaphore





























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







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

[JIRA] [pretested-integration-plugin] (JENKINS-27516) Plugin hangs - reproduced with failed earlier build (Praqma case 12906)















































SCM/JIRA link daemon
 commented on  JENKINS-27516


Plugin hangs - reproduced with failed earlier build (Praqma case 12906)















Code changed in jenkins
User: Mads Nielsen
Path:
 src/main/java/org/jenkinsci/plugins/pretestedintegration/PretestedIntegrationBuildWrapper.java
http://jenkins-ci.org/commit/pretested-integration-plugin/e7e028e33dfbcfd14b7f117019684db0b06fad2f
Log:
  Fix for JENKINS-27516





























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







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

[JIRA] [prioritysorter-plugin] (JENKINS-27957) NullPointerException in AdvancedQueueSorter

2015-04-15 Thread tom.ghyseli...@excentis.com (JIRA)















































Tom Ghyselinck
 updated  JENKINS-27957


NullPointerException in AdvancedQueueSorter
















Change By:


Tom Ghyselinck
(15/Apr/15 2:20 PM)




Environment:


Jenkins 1.596.2 LTS
Priority Sorter plugin 2.11





Description:


Hi,Our Jenkins server seems to get locked at some point in time.Many Jobs are in _starvation_, waiting for nodes with certain _labels_/_label combinations_.(i.e. _Waiting for next available executor on ..._)The log shows a lot of these entries:{code}Apr 15, 2015 3:44:25 PM SEVERE hudson.triggers.SafeTimerTask runTimer task hudson.model.Queue$MaintainTask@5d00189f failedjava.lang.NullPointerException	at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:99)	at jenkins.advancedqueue.sorter.AdvancedQueueSorter$2.compare(AdvancedQueueSorter.java:81)	at java.util.TimSort.countRunAndMakeAscending(TimSort.java:329)	at java.util.TimSort.sort(TimSort.java:189)	at java.util.TimSort.sort(TimSort.java:173)	at java.util.Arrays.sort(Arrays.java:659)	at java.util.Collections.sort(Collections.java:217)	at jenkins.advancedqueue.sorter.AdvancedQueueSorter.sortBuildableItems(AdvancedQueueSorter.java:81)	at hudson.model.Queue.maintain(Queue.java:1135)	at hudson.model.Queue$MaintainTask.doRun(Queue.java:2197)	at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)	at java.lang.Thread.run(Thread.java:745)Feed{code}
and also some entries like{code}java.lang.NullPointerException	at jenkins.advancedqueue.sorter.AdvancedQueueSorter.onLeft(AdvancedQueueSorter.java:157)	at jenkins.advancedqueue.sorter.AdvancedQueueSorterQueueListener.onLeft(AdvancedQueueSorterQueueListener.java:47)	at hudson.model.Queue$LeftItem.enter(Queue.java:2087)	at hudson.model.Queue.onStartExecuting(Queue.java:924)	at hudson.model.Executor.run(Executor.java:209)	at hudson.model.OneOffExecutor.run(OneOffExecutor.java:43){code}We see theses issues since we updated the [Priority Sorter Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Priority+Sorter+Plugin] to _version 2.11_ (from _version 2.9_)Downgrading to _version 2.9_ seems to work fine!





Assignee:


Magnus Sandberg





Component/s:


prioritysorter-plugin





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/d/optout.

[JIRA] [clamav-plugin] (JENKINS-27954) Scan fail for "Too many open files"















































SCM/JIRA link daemon
 commented on  JENKINS-27954


Scan fail for "Too many open files"















Code changed in jenkins
User: Seiji Sogabe
Path:
 src/main/java/org/jenkinsci/plugins/clamav/ClamAvRecorder.java
http://jenkins-ci.org/commit/clamav-plugin/1cc0fa61061452f1ab5a98f04dc8221d083ec0af
Log:
  [FIXED JENKINS-27954] ensure file is closed.





























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







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

[JIRA] [clamav-plugin] (JENKINS-27954) Scan fail for "Too many open files"
















































SCM/JIRA link daemon
 resolved  JENKINS-27954 as Fixed


Scan fail for "Too many open files"
















Change By:


SCM/JIRA link daemon
(15/Apr/15 2:23 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/d/optout.

[JIRA] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label















































Reiner Wirtz
 commented on  JENKINS-23459


Cannot restrict a matrix build job to one node/label















In the first section of the multiconfiguration is an option to enter a groovy script to restrict where the job could be run.
Activating this option opens an edit field for the groovy script.
In this field I entered the mini groovy script: return "Master";
This worked 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/d/optout.

[JIRA] [android-emulator-plugin] (JENKINS-27456) Emulator can't connect to adb server!?

2015-04-15 Thread markbryantay...@gmail.com (JIRA)















































Mark Taylor
 commented on  JENKINS-27456


Emulator can't connect to adb server!?















My earlier theory (have to wait for emulator- to be available for connecting to localhost:) doesn't appear to be true.

It did seem to work better if I connected to emulator- rather than locahost:.  Locahost: never seems to some online (which I assume is an ADB/ SDK issue rather than the plugin).

I'm going to start from a clean plugin and try again with just connecting via emulator-.



























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







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

[JIRA] [matrix-project-plugin] (JENKINS-23459) Cannot restrict a matrix build job to one node/label















































Reiner Wirtz
 updated  JENKINS-23459


Cannot restrict a matrix build job to one node/label
















the attached png shows the script in a screen shot





Change By:


Reiner Wirtz
(15/Apr/15 2:28 PM)




Attachment:


MatrixConfigurationToRunAllOnMaster.png



























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







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

[JIRA] [core] (JENKINS-27621) Jenkins is not an Item

2015-04-15 Thread te...@java.net (JIRA)















































James Nord
 commented on  JENKINS-27621


Jenkins is not an Item















it is conveninent to handle in code such that you don't need to do have multiple paths through the code

if (ItemGroup instanceOf Item) { /* do something */} 
else if (ItemGroup instanceOf Jenkins) { /* do something else */ }

Item.getFullName should return the empty string or null (depending on if this is nullable), delete could throw an error, or (for bonus points) should remove itself from the OS :-P etc. etc.)



























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







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

[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job















































Reiner Wirtz
 commented on  JENKINS-27948


Script timeout during start of configure a jenkins job















The list of the installed plugins (copied from display of the system properties):


ant	1.2	true	true
antisamy-markup-formatter	1.3	true	true
any-buildstep	0.1	true	false
artifactdeployer	0.33	true	false
audit-trail	2.1	true	false
backup	1.6.1	true	false
batch-task	1.17	true	false
build-blocker-plugin	1.6	true	false
build-environment	1.4	true	false
build-pipeline-plugin	1.4.7	true	false
build-user-vars-plugin	1.4	true	false
clone-workspace-scm	0.6	true	false
conditional-buildstep	1.3.3	true	false
config-file-provider	2.7.5	true	false
copy-to-slave	1.4.4	true	false
copyartifact	1.35	true	false
credentials	1.22	true	true
custom-tools-plugin	0.4.4	true	false
CustomHistory	1.6	true	false
cvs	2.12	true	true
dashboard-view	2.9.4	true	false
delivery-pipeline-plugin	0.8.11	true	false
dependencyanalyzer	0.7	true	false
deploy	1.10	true	false
disk-usage	0.25	true	false
downstream-buildview	1.9	true	false
downstream-ext	1.8	true	false
dynamic-axis	1.0.3	true	false
dynamic_extended_choice_parameter	1.0.1	true	false
dynamicparameter	0.2.0	true	false
email-ext	2.39.3	true	false
envfile	1.2	true	false
envinject	1.91.2	true	false
extended-choice-parameter	0.35	true	false
extensible-choice-parameter	1.2.2	true	false
external-monitor-job	1.4	true	true
flexible-publish	0.15.1	true	false
git	2.3.5	true	false
git-client	1.16.1	true	false
git-server	1.6	true	false
groovy	1.24	true	false
groovy-label-assignment	1.1.0	true	false
groovyaxis	0.3	true	false
ivy	1.24	true	false
javadoc	1.3	true	true
job-log-logger-plugin	1.0	true	false
job-node-stalker	1.0.3	true	false
jobConfigHistory	2.10	true	false
jquery	1.11.2-0	true	false
jquery-ui	1.0.2	true	false
junit	1.5	true	true
labeled-test-groups-publisher	1.2.7	true	false
ldap	1.11	true	true
m2-repo-reaper	1.0	true	false
mailcommander	1.0.0	true	false
mailer	1.15	true	true
managed-scripts	1.1.1	true	false
mantis	0.26	true	false
mapdb-api	1.0.6.0	true	false
matrix-auth	1.2	true	true
matrix-combinations-parameter	1.0.7	true	false
matrix-project	1.4.1	true	false
Matrix-sorter-plugin	1.1	true	false
maven-plugin	2.9	true	true
metadata	1.1.0b	true	false
metrics	3.0.9	true	false
monitoring	1.55.0	true	false
nodelabelparameter	1.5.1	true	false
pam-auth	1.2	true	true
parameterized-trigger	2.26	true	false
periodicbackup	1.3	true	false
postbuild-task	1.8	true	false
postbuildscript	0.17	true	false
PrioritySorter	2.11	true	false
role-strategy	2.2.0	true	false
run-condition	1.0	true	false
scm-api	0.2	true	false
script-security	1.13	true	false
scriptler	2.7	true	false
selection-tasks-plugin	1.0	true	false
shared-objects	0.44	true	false
show-build-parameters	1.0	true	false
skip-certificate-check	1.0	true	false
sonar	2.2	true	false
ssh-credentials	1.11	true	true
ssh-slaves	1.9	true	true
statusmonitor	1.3	true	false
strawboss	1.3	true	false
subversion	2.5	true	true
support-core	2.20	true	false
svn-tag	1.17	true	false
testlink	3.10	true	false
throttle-concurrents	1.8.4	true	false
token-macro	1.10	true	false
translation	1.12	true	true
uno-choice	0.24	true	false
update-sites-manager	1.0.1	true	false
validating-string-parameter	2.3	true	false
vsphere-cloud	2.4	true	false
weblogic-deployer-plugin	3.2	true	false
websphere-deployer	1.3-SNAPSHOT (private-08/05/2014 09:34-nothhard)	true	false
windows-slaves	1.0	true	false
ws-cleanup	0.25	true	false
xunit	1.94	true	false




























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







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

[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job













































  
Reiner Wirtz
 edited a comment on  JENKINS-27948


Script timeout during start of configure a jenkins job
















The list of the installed plugins (copied from display of the system properties):

ant	1.2	true	true
antisamy-markup-formatter	1.3	true	true
any-buildstep	0.1	true	false
artifactdeployer	0.33	true	false
audit-trail	2.1	true	false
backup	1.6.1	true	false
batch-task	1.17	true	false
build-blocker-plugin	1.6	true	false
build-environment	1.4	true	false
build-pipeline-plugin	1.4.7	true	false
build-user-vars-plugin	1.4	true	false
clone-workspace-scm	0.6	true	false
conditional-buildstep	1.3.3	true	false
config-file-provider	2.7.5	true	false
copy-to-slave	1.4.4	true	false
copyartifact	1.35	true	false
credentials	1.22	true	true
custom-tools-plugin	0.4.4	true	false
CustomHistory	1.6	true	false
cvs	2.12	true	true
dashboard-view	2.9.4	true	false
delivery-pipeline-plugin	0.8.11	true	false
dependencyanalyzer	0.7	true	false
deploy	1.10	true	false
disk-usage	0.25	true	false
downstream-buildview	1.9	true	false
downstream-ext	1.8	true	false
dynamic-axis	1.0.3	true	false
dynamic_extended_choice_parameter	1.0.1	true	false
dynamicparameter	0.2.0	true	false
email-ext	2.39.3	true	false
envfile	1.2	true	false
envinject	1.91.2	true	false
extended-choice-parameter	0.35	true	false
extensible-choice-parameter	1.2.2	true	false
external-monitor-job	1.4	true	true
flexible-publish	0.15.1	true	false
git	2.3.5	true	false
git-client	1.16.1	true	false
git-server	1.6	true	false
groovy	1.24	true	false
groovy-label-assignment	1.1.0	true	false
groovyaxis	0.3	true	false
ivy	1.24	true	false
javadoc	1.3	true	true
job-log-logger-plugin	1.0	true	false
job-node-stalker	1.0.3	true	false
jobConfigHistory	2.10	true	false
jquery	1.11.2-0	true	false
jquery-ui	1.0.2	true	false
junit	1.5	true	true
labeled-test-groups-publisher	1.2.7	true	false
ldap	1.11	true	true
m2-repo-reaper	1.0	true	false
mailcommander	1.0.0	true	false
mailer	1.15	true	true
managed-scripts	1.1.1	true	false
mantis	0.26	true	false
mapdb-api	1.0.6.0	true	false
matrix-auth	1.2	true	true
matrix-combinations-parameter	1.0.7	true	false
matrix-project	1.4.1	true	false
Matrix-sorter-plugin	1.1	true	false
maven-plugin	2.9	true	true
metadata	1.1.0b	true	false
metrics	3.0.9	true	false
monitoring	1.55.0	true	false
nodelabelparameter	1.5.1	true	false
pam-auth	1.2	true	true
parameterized-trigger	2.26	true	false
periodicbackup	1.3	true	false
postbuild-task	1.8	true	false
postbuildscript	0.17	true	false
PrioritySorter	2.11	true	false
role-strategy	2.2.0	true	false
run-condition	1.0	true	false
scm-api	0.2	true	false
script-security	1.13	true	false
scriptler	2.7	true	false
selection-tasks-plugin	1.0	true	false
shared-objects	0.44	true	false
show-build-parameters	1.0	true	false
skip-certificate-check	1.0	true	false
sonar	2.2	true	false
ssh-credentials	1.11	true	true
ssh-slaves	1.9	true	true
statusmonitor	1.3	true	false
strawboss	1.3	true	false
subversion	2.5	true	true
support-core	2.20	true	false
svn-tag	1.17	true	false
testlink	3.10	true	false
throttle-concurrents	1.8.4	true	false
token-macro	1.10	true	false
translation	1.12	true	true
uno-choice	0.24	true	false
update-sites-manager	1.0.1	true	false
validating-string-parameter	2.3	true	false
vsphere-cloud	2.4	true	false
weblogic-deployer-plugin	3.2	true	false
websphere-deployer	1.3-SNAPSHOT (private-08/05/2014 09:34-nothhard)	true	false
windows-slaves	1.0	true	false
ws-cleanup	0.25	true	false
xunit	1.94	true	false



























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







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

[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job















































Reiner Wirtz
 updated  JENKINS-27948


Script timeout during start of configure a jenkins job
















The attached zip file contains the config.xml file from a job called DOXiS4_CSB-Test-All-Comb".
Opening this job for configuration exceeds the limit of 100 seconds configured in my firefox-browser.
During this time one core of the quad-core-cpu is busy for the whole time.





Change By:


Reiner Wirtz
(15/Apr/15 2:47 PM)




Attachment:


config.zip



























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







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

[JIRA] [maven-plugin] (JENKINS-27947) JDK 1.6 maven builds fail when running on Tomcat 8

2015-04-15 Thread p...@java.net (JIRA)















































pmv
 commented on  JENKINS-27947


JDK 1.6 maven builds fail when running on Tomcat 8















I think these tickets are similar, in that users running builds expect to be able to compile with any JDK.  However, the actual criteria seems to be this:

If you are building using the Maven project type, the minimum JDK you can compile with is determined by the maximum of the following:

	The java version Jenkins core was compiled with
	The java version your container was compiled with (specifically, the servlet-api jar)
	The java version the maven-plugin was compiled with



The versions for JENKINS-25272 are 1.6, 1.5, 1.5, so a 1.5 build broke due to be #1 (as I would consider the remoting jar to be part of core)
The versions for JENKINS-16920 were 1.5, 1.6, 1.5, so a 1.5 build broke due to #2. 
The versions for this ticket are 1.6, 1.7, 1.5, so 1.6 builds break due to #2.

We haven't actually seen #3, since it seems to be lagging behind the other two, but I suspect it is true.

These restrictions make some sense once you understand that Jenkins plugin classloading is hierarchical (rather than using something like OSGi), so plugin developers probably understand this: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+Structure#PluginStructure-Classloader  However, the first time you encounter it as a user it's not intuitive (especially the servlet-api dependency).  

If a fix is not going to be made, at minimum I would suggest calling out these restrictions on the Maven project plugin wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Maven+Project+Plugin



























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







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

[JIRA] [next-build-number-plugin] (JENKINS-27958) Cannot reset the next build number

2015-04-15 Thread testingk...@gmail.com (JIRA)















































Maninder Singh
 updated  JENKINS-27958


Cannot reset the next build number
















Change By:


Maninder Singh
(15/Apr/15 2:53 PM)




Attachment:


JENKINS-27958.txt



























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







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

[JIRA] [syslog-logger-plugin] (JENKINS-27959) NullPointerException in SyslogLoggerPlugin.applySettings after upgrading the plugin

2015-04-15 Thread clecl...@cloudbees.com (JIRA)















































Cyrille Le Clerc
 created  JENKINS-27959


NullPointerException in SyslogLoggerPlugin.applySettings after upgrading the plugin















Issue Type:


Bug



Assignee:


Cyrille Le Clerc



Components:


syslog-logger-plugin



Created:


15/Apr/15 2:55 PM



Description:


NullPointerException in SyslogLoggerPlugin.applySettings(SyslogLoggerPlugin.java:149) after upgrading to version 1.0.2


```
Caused by: java.lang.NullPointerException
	at org.jenkinsci.plugins.sysloglogger.SyslogLoggerPlugin.applySettings(SyslogLoggerPlugin.java:149)
	at org.jenkinsci.plugins.sysloglogger.SyslogLoggerPlugin.(SyslogLoggerPlugin.java:112)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:408)
	at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86)
	at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108)
	at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88)
	at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269)
	at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
	at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058)
	at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
	... 25 more
```





Environment:


syslog-logger-plugin:1.0.2




Project:


Jenkins



Priority:


Minor



Reporter:


Cyrille Le Clerc

























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







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

[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job















































Reiner Wirtz
 commented on  JENKINS-27948


Script timeout during start of configure a jenkins job















I increased the timeout value for scripts to run to 200 seconds.
The start to configure the job I added in the attachments took 180 seconds (yes 3 minutes) on my machine.



























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







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

[JIRA] [pretested-integration-plugin] (JENKINS-27516) Plugin hangs - reproduced with failed earlier build (Praqma case 12906)

2015-04-15 Thread b...@praqma.net (JIRA)
















































Bue Petersen
 resolved  JENKINS-27516 as Fixed


Plugin hangs - reproduced with failed earlier build (Praqma case 12906)
















Fixed in 2.2.3 - just released.





Change By:


Bue Petersen
(15/Apr/15 2:54 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job















































Reiner Wirtz
 commented on  JENKINS-27948


Script timeout during start of configure a jenkins job















If I should present the data in a special way or format, please feel free to contact me.



























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







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

[JIRA] [maven-plugin] (JENKINS-27686) Password Paramater in Maven project is sent build as stars instead real value

2015-04-15 Thread dpu...@selectica.com (JIRA)















































Dmitriy Pupov
 commented on  JENKINS-27686


Password Paramater in Maven project is sent build as stars instead real value
















Invoke top level maven target step



























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







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

[JIRA] [core] (JENKINS-27708) Concurrent build limits not honored on Jenkins 1.607

SCM/JIRA link daemon
commented on JENKINS-27708

Concurrent build limits not honored on Jenkins 1.607

Code changed in jenkins
User: Stephen Connolly
Path:
core/src/main/java/hudson/model/Queue.java
http://jenkins-ci.org/commit/jenkins/5880ed830201f9349ae9def6653c19a186e1eb18
Log:
[FIXED JENKINS-27708][FIXED JENKINS-27871] Ensure that identification of blocked tasks is using the live state.

The creation of a snapshot itself should be relatively cheap given the expected rate of
job execution. You probably would need 100's of jobs starting execution every iteration
of maintain() before this could even start to become an issue and likely the calculation
of isBuildBlocked(p) will become a bottleneck before updateSnapshot() will. Additionally
since the snapshot itself only ever has at most one reference originating outside of the stack
it should remain in the eden space and thus be cheap to GC.

JENKINS-27708 comments 225819 and 225906 provide more complex but logically equivalent fixes of
this issue. I am favouring this approach as it is simpler and provides less scope for error as any
new helper methods can just rely on the snapshot being up to date whereas with the other
two candidates if a new helper method is introduced there is the potential to miss adding support
for the live view. The comment 225819 has the risk of introducing extra lock contention while
the comment 225906 version forces every access to the helper methods to pass a second memory
barrier

[JIRA] [core] (JENKINS-27708) Concurrent build limits not honored on Jenkins 1.607















































SCM/JIRA link daemon
 commented on  JENKINS-27708


Concurrent build limits not honored on Jenkins 1.607















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/model/Queue.java
 test/src/test/java/hudson/model/QueueTest.java
http://jenkins-ci.org/commit/jenkins/152d00ad09931c10f02fab4ac8a42e574d622bd3
Log:
  Merge pull request #1645 from stephenc/jenkins-27708

JENKINS-27708, JENKINS-27871  Ensure that identification of blocked tasks is using the live state.


Compare: https://github.com/jenkinsci/jenkins/compare/b688047877cf...152d00ad0993




























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







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

[JIRA] [core] (JENKINS-27871) Block on upstream projects does not work

SCM/JIRA link daemon
commented on JENKINS-27871

Block on upstream projects does not work

[JIRA] [core] (JENKINS-27871) Block on upstream projects does not work















































SCM/JIRA link daemon
 commented on  JENKINS-27871


Block on upstream projects does not work















Code changed in jenkins
User: Stephen Connolly
Path:
 core/src/main/java/hudson/model/Queue.java
 test/src/test/java/hudson/model/QueueTest.java
http://jenkins-ci.org/commit/jenkins/152d00ad09931c10f02fab4ac8a42e574d622bd3
Log:
  Merge pull request #1645 from stephenc/jenkins-27708

JENKINS-27708, JENKINS-27871  Ensure that identification of blocked tasks is using the live state.


Compare: https://github.com/jenkinsci/jenkins/compare/b688047877cf...152d00ad0993




























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







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

[JIRA] [core] (JENKINS-27871) Block on upstream projects does not work















































SCM/JIRA link daemon
 commented on  JENKINS-27871


Block on upstream projects does not work















Code changed in jenkins
User: Oleg Nenashev
Path:
 test/src/test/java/hudson/model/QueueTest.java
http://jenkins-ci.org/commit/jenkins/7514e8c6ce35283da4a8bb4422fe885350fc8681
Log:
  JENKINS-27871 - Added a direct unit test for the issue





























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







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

[JIRA] [core] (JENKINS-27871) Block on upstream projects does not work