date:20140425















































Soren Hansen
 commented on  JENKINS-21882


v1.551 + GitHub OAuth == broken api token access















It seems this broke again after I fixed it. AFter upgrading my Jenkins instance, it again does not work for me.

A number of bugs seem related: JENKINS-22346 JENKINS-20064 JENKINS-9258



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [crowd2] (JENKINS-21852) Allow configuration of HTTPS proxy for connection to Crowd















































Kanstantsin Shautsou
 commented on  JENKINS-21852


Allow configuration of HTTPS proxy for connection to Crowd















Please, try new plugin, i added parameters, but i have no proxy for testing.



























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







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

[JIRA] [crowd2] (JENKINS-13788) Git user and Crowd 2 authenticated user should be equal (one User-Id)
















































Kanstantsin Shautsou
 resolved  JENKINS-13788 as Fixed


Git user and Crowd 2 authenticated user should be equal (one User-Id)
















Was fixed in 1.6.





Change By:


Kanstantsin Shautsou
(25/Apr/14 11:37 AM)




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] [crowd2] (JENKINS-18791) session.validationinterval is not saved
















































Kanstantsin Shautsou
 resolved  JENKINS-18791 as Fixed


session.validationinterval is not saved
















Should be fixed in 1.7





Change By:


Kanstantsin Shautsou
(25/Apr/14 11:40 AM)




Status:


Reopened
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] [crowd2] (JENKINS-13279) Interface with Crowd embedded that runs in Jira















































Kanstantsin Shautsou
 commented on  JENKINS-13279


Interface with Crowd embedded that runs in Jira















Please, try new version.



























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







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

[JIRA] [crowd2] (JENKINS-17957) Crowd plugin - remember me doesn't work















































Kanstantsin Shautsou
 commented on  JENKINS-17957


Crowd plugin - remember me doesnt work















Initial author mapped autologin to rememberme functionality from servletfilter. ServletFilter should be reworked and auth bean should be checked, rememberme class should be removed at all so jenkins will use core rememberme functionality. Like it was fixed in latest ldap 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] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access

2014-04-25 Thread jenshniel...@gmail.com (JIRA)















































Jens Nielsen
 commented on  JENKINS-21882


v1.551 + GitHub OAuth == broken api token access















That seems likely and explains why it works on the latest LTS but not on the regular version. 



























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







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

[JIRA] [active-directory] (JENKINS-19052) upgrading from 1.523 to 1.524 or 1.525 breaks jenkins - ActiveDirectorySecurityRealm missing descriptor

2014-04-25 Thread peter.wa...@ikano.se (JIRA)















































Peter Walls
 commented on  JENKINS-19052


upgrading from 1.523 to 1.524 or 1.525 breaks jenkins - ActiveDirectorySecurityRealm missing descriptor















Hello,
I saw the exact same error after upgrading to Jenkins 1.560 on Windows. After some investigations I found a couple of strange .disabled files in the plugins-directory of the credentials and active-directory plugins.
I stopped the Jenkins service, removed all dirs and files for the following plugins: active-directory, credentials and ssh-credentials. After that I replaced the three plugins with fresh copies of the jpi files. And after restarting the Jenkins service it all suddenly worked again!



























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







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

[JIRA] [core] (JENKINS-22734) OutOfMemory on file transfer

2014-04-25 Thread tur...@chebucto.ns.ca (JIRA)















































Shane Turner
 commented on  JENKINS-22734


OutOfMemory on file transfer















Someone should update the "Affects Version" field to indicate that this is an issue with 1.560.



























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







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

[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access















































Soren Hansen
 commented on  JENKINS-21882


v1.551 + GitHub OAuth == broken api token access















Oh, found the problem!

Jenkins's User class now calls the loadUserByUsername on the UserDetailsService from the SecurityComponents object on the SecurityRealm, but that doesn't actually call the loadUserByUsername method, but rather provides its own "fake" one in the Github OAuth 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] [core] (JENKINS-22758) Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)















































Cees Bos
 commented on  JENKINS-22758


Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)















It looks like not only an issue with swarm plugin.
We have a number of jnlp slaves, but we don't get them connected anymore.
>From the perspective of the slave it shows 'connected', but Jenkins master shows it as still unconnected.
We have a Jenkins master on Linux and mix of all kind of slaves.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-21882) v1.551 + GitHub OAuth == broken api token access















































Soren Hansen
 commented on  JENKINS-21882


v1.551 + GitHub OAuth == broken api token access















https://github.com/jenkinsci/github-oauth-plugin/pull/23



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-22758) Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)













































 
Cees Bos
 edited a comment on  JENKINS-22758


Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)
















It looks like not only an issue with swarm plugin.
We have a number of jnlp slaves, but we don't get them connected anymore.
>From the perspective of the slave it shows 'connected', but Jenkins master shows it as still unconnected.
We have a Jenkins master on Linux and mix of all kind of slaves.

In Jenkins you can click on 'Log' for a node, then there is:
JNLP agent connected from /10.1.29.228

But the UI still shows it as offline.



























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







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

[JIRA] [core] (JENKINS-21882) v1.551 + GitHub OAuth == broken api token access















































Soren Hansen
 commented on  JENKINS-21882


v1.551 + GitHub OAuth == broken api token access















Plugin for testing can be found here: https://github.com/sorenh/github-oauth-plugin/releases/tag/0.16-pre-soren



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository
















































Mark Waite
 resolved  JENKINS-22752 as Not A Defect


Initial poll (just after project creation) spawns builds for all the existing branches in repository
















This is the intended behavior of the plugin.  I'm reasonably confident that among the 30 000+ installations of the git plugin there are users who depend on that behavior.  I don't think we can change that behavior without making many more users frustrated than we would satisfy with the change.





Change By:


Mark Waite
(25/Apr/14 12:38 PM)




Status:


Open
Resolved





Resolution:


NotADefect



























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







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

[JIRA] [tasks-plugin] (JENKINS-22744) cp1251 encoding issue when viewing Details tab

2014-04-25 Thread ullrich.haf...@gmail.com (JIRA)















































Ulli Hafner
 commented on  JENKINS-22744


cp1251 encoding issue when viewing Details tab















Ah, this is a useful hint. I.e. the encoding is correctly read from your pom. Just the display in the details tab is broken, the source view works. 

Would it be possible to provide a text file in your locale (just a "TODO: Hello world" with Russian letters) so I can use it for a test?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [prqa] (JENKINS-22763) PRQA - Graphs not getting generated

2014-04-25 Thread jra...@visteon.com (JIRA)















































Rainy John
 created  JENKINS-22763


PRQA - Graphs not getting generated















Issue Type:


Bug



Assignee:


Praqma Support



Attachments:


PRQA_Issue.txt



Components:


prqa



Created:


25/Apr/14 12:52 PM



Description:


I use ver 1.556 of Jenkins and Ver 1.2.2 of PRQA plug-in and I have a Master-Salve Configuration. 
I have installed QAC 8.0 R version, QAW and QAR files in Slave PC.
If I configure 'Programming Research Report' in the Post Build section of Jenkins Job, I am getting the error "the build fails saying "Build step 'Programming Research Report' marked build as failure"

Note that the QAC HTML files are getting generated as part of Build.




Environment:


Ver 1.556 of Jenkins and Ver 1.2.2 of PRQA plug-in.




Project:


Jenkins



Priority:


Major



Reporter:


Rainy John

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-22758) Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)

Cees Bos
edited a comment on JENKINS-22758

Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)

It looks like not only an issue with swarm plugin.

Today we did an update to 1.560 (from 1.554).
We noticed 2 things:

We have a regular restart of the JNLP slaves with a Groovy script executed on the slave itself as soon as the executor is free. Each slave has only 1 executed.
There are long running jobs active on the JNLP saves. So normally it waits till the job is completed, then the next item gets executed.
But now the restart task got executed right away, and broke the running job.

The machine got restarted and then tried to connect again to Jenkins, that fails.
We have a number of jnlp slaves, but we don't get them connected anymore.
>From the perspective of the slave it shows 'connected', but Jenkins master shows it as still unconnected.
We have a Jenkins master on Linux and mix of all kind of slaves.

In Jenkins you can click on 'Log' for a node, then there is:
JNLP agent connected from /10.1.29.228

But the UI still shows it as offline.

[JIRA] [tasks-plugin] (JENKINS-22744) cp1251 encoding issue when viewing Details tab

2014-04-25 Thread dzianis.frydli...@gmail.com (JIRA)















































Dennis F.
 updated  JENKINS-22744


cp1251 encoding issue when viewing Details tab
















Sure.
Attached a file in cp1251 and 2 screenshots.





Change By:


Dennis F.
(25/Apr/14 1:02 PM)




Attachment:


TestTaskScannerDetails.png





Attachment:


TestTaskScanner.java





Attachment:


TestTaskScannerView.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-21882) v1.551 + GitHub OAuth == broken api token access

2014-04-25 Thread to...@starhill.org (JIRA)















































Tomas Bezdek
 commented on  JENKINS-21882


v1.551 + GitHub OAuth == broken api token access















works for me now!



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cli] (JENKINS-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown

2014-04-25 Thread f...@wizcorp.jp (JIRA)















































Frank Lee
 commented on  JENKINS-21086


jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown















This is also occurring with Jenkins v1.558.

I have the same error as well with delete-job command. The Jenkins server authenticates with LDAP. When no permissions are allowed for Anonymous, the same error occurs. When Overall Read permissions is applied to Anonymous, a "java.lang.NullPointerException" error occurs.


Command:
java -jar /usr/lib/jenkins/jenkins-cli.jar -s http://localhost:8080 delete-job blah-job --username admin --password mypassword

Permissions:
no permissions are allowed for Anonymous

Error:
hudson.security.AccessDeniedException2: anonymous is missing the Overall/Read permission
	at hudson.security.ACL.checkPermission(ACL.java:54)
	at hudson.model.Node.checkPermission(Node.java:418)
	at hudson.cli.declarative.CLIRegisterer$1.main(CLIRegisterer.java:180)
	at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92)
	at sun.reflect.GeneratedMethodAccessor409.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63)
	at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	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:744)


Same command again with "Overall Read" permissions applied to Anonymous


java.lang.NullPointerException
	at hudson.model.AbstractItem.resolveForCLI(AbstractItem.java:677)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at hudson.cli.declarative.MethodBinder.call(MethodBinder.java:102)
	at hudson.cli.declarative.CLIRegisterer$1.main(CLIRegisterer.java:185)
	at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92)
	at sun.reflect.GeneratedMethodAccessor409.invoke(Unknown Source)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:299)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:280)
	at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:239)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:328)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63)
	at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95)
	at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	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:744)



























This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA

[JIRA] [core] (JENKINS-22734) OutOfMemory on file transfer in 1.560

2014-04-25 Thread tomas.ko...@eccam.com (JIRA)















































Tomas Kopal
 updated  JENKINS-22734


OutOfMemory on file transfer in 1.560
















Change By:


Tomas Kopal
(25/Apr/14 1:38 PM)




Summary:


OutOfMemoryonfiletransfer
in1.560





Affects Version/s:


current



























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







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

[JIRA] [perforce] (JENKINS-11600) Implement Entry functions for email-ext support

2014-04-25 Thread niknap...@hotmail.com (JIRA)















































Nik San
 commented on  JENKINS-11600


Implement Entry functions for email-ext support















My first time using github and everything in relation to developing jenkins plugins, but I have a pull request for this.

https://github.com/jenkinsci/perforce-plugin/pull/49



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cli] (JENKINS-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown

2014-04-25 Thread f...@wizcorp.jp (JIRA)















































Frank Lee
 commented on  JENKINS-21086


jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown















Found a workaround. Instead of using the jenkins-cli.jar, use curl:

curl -u admin:mypassword -fs --data "" "http://localhost:8080/job/blah-job/doDelete"

This works with no permissions given to Anonymous. Hopes this helps someone out there.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-22734) OutOfMemory on file transfer in 1.560

2014-04-25 Thread peter.vanbie...@vaph.be (JIRA)















































Peter Van Biesen
 commented on  JENKINS-22734


OutOfMemory on file transfer in 1.560















1.559 does not have the problem, 1.560 does. To reproduce, create a job with a shell build step and following code :

dd if=/dev/urandom of=target.out bs=1M count=50
for a in 1 2 3 4
do
cat target.out  bigtarget.out
done

and in post-build actions add a "Archive the artifacts", file : bigtarget.out

For every build on the same slave, the archived file will increase by 200 Mb.
Effects :

	the slave will disconnect
	the master will not be able to reconnect to the slave UNLESS you choose "configure" on the node, click "save" and then relaunch the slave connection
	the master will not stop in a normal fasion, only kill -9 will do the trick
	the slave.jar will keep running on the client and needs to be killed too ( otherwise multiple will keep running )





























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-22734) OutOfMemory on file transfer in 1.560

2014-04-25 Thread peter.vanbie...@vaph.be (JIRA)













































 
Peter Van Biesen
 edited a comment on  JENKINS-22734


OutOfMemory on file transfer in 1.560
















1.559 does not have the problem, 1.560 does. To reproduce, create a job with a shell build step and following code :

dd if=/dev/urandom of=target.out bs=1M count=50
for a in 1 2 3 4
do
cat target.out  bigtarget.out
done

and in post-build actions add a "Archive the artifacts", file : bigtarget.out

For every build on the same slave, the archived file will increase by 200 Mb.
Effects :

	the slave will disconnect
	the master will not be able to reconnect to the slave UNLESS you choose "configure" on the node, click "save" and then relaunch the slave connection
	the master will not stop in a normal fashion, only kill -9 will do the trick
	the slave.jar will keep running on the client and needs to be killed too ( otherwise multiple will keep running )





























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







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

[JIRA] [build-pipeline] (JENKINS-22196) Validation error when choosing a valid project as manual downstream project

2014-04-25 Thread wilco.gre...@ibridge.nl (JIRA)















































Wilco Greven
 commented on  JENKINS-22196


Validation error when choosing a valid project as manual downstream project















Hello Thomas,

A folder is indeed a Cloudbees Folder Plugin folder.

Wilco



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-22750) Polling no longer triggers builds (regression 1.560)

2014-04-25 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 updated  JENKINS-22750


Polling no longer triggers builds (regression 1.560)
















Change By:


Jesse Glick
(25/Apr/14 2:36 PM)




Priority:


Major
Critical



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [support-core] (JENKINS-22764) Record update center information

2014-04-25 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 created  JENKINS-22764


Record update center information















Issue Type:


New Feature



Assignee:


Unassigned


Components:


support-core



Created:


25/Apr/14 2:49 PM



Description:


Often people say they are not seeing an expected plugin update. Would be useful for a support bundle to record:


	list of configured update sites
	core version string being sent to them
	registered site certificates
	last update time
	pending plugin updates (could be moved from about.md, or just shown in a different form: list of plugins, with current and newest versions)
	status of Downloader instances (tool definitions, usually)
	whether a proxy is configured






Project:


Jenkins



Priority:


Major



Reporter:


Jesse Glick

























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







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

[JIRA] [accurev] (JENKINS-22765) configuring a job show an accurev syntax output

2014-04-25 Thread kacynski.w...@aoins.com (JIRA)















































Walter Kacynski
 created  JENKINS-22765


configuring a job show an accurev syntax output















Issue Type:


Bug



Assignee:


Scott Tatum



Components:


accurev



Created:


25/Apr/14 3:14 PM



Description:


When clicking on the configure option for a job, a few seconds after the page has loaded, the following output appears in the jenkins master log:


Apr 25, 2014 11:09:17 AM hudson.plugins.accurev.cmd.ShowStreams getStreamsForGlobalConfig
WARNING: AccuRev Server: Production Accurev.


SHOW


   list objects of a particular kind

-
USAGE
-

show [ -fx ] accuwork
show [ -fx ] depots
show [ -fformat(s) ] [ -u principal ] groups
show [ -fx ] locks
show [ -fx ] [ -g group-name ] members
show [ -fformat(s) ] [ -ks [ -p depot ] | -ku | -s stream |
-u principal ] [ -n pattern ] [ -r ] properties
show [ -fformat(s) ] refs
show [ -fx ] sessions
show [ -fformat(s) ] slices
show [ -fformat(s) ] [ -p depot ] [ -d ] [ -t time-spec ]
[ -s stream [ -m[match-type] ] [ -r | -R | -1 ] ] streams
show [ -fformat(s) ] [ -p depot ] [ -d ] [ -t time-spec ]
[ -l list-file [ -m[match-type] ] [ -r | -R | -1 ] ] streams
show [ -fx ] [ -p depot ] -s depot stream_rules
show [ -fformat(s) ] [ -p depot ] triggers
show [ -fformat(s) ] users
show [ -fformat(s) ] [ -a ] wspaces



MORE INFORMATION

Type 'accurev help' for a complete list of topics.

AccuRev Inc.   http://www.accurev.com   supp...@accurev.com



This appears to be linked back to file:
https://github.com/jenkinsci/accurev-plugin/blob/master/src/main/java/hudson/plugins/accurev/cmd/ShowStreams.java




Project:


Jenkins



Priority:


Major



Reporter:


Walter Kacynski

























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







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

[JIRA] [accurev] (JENKINS-22765) configuring a job show an accurev syntax output

2014-04-25 Thread kacynski.w...@aoins.com (JIRA)
















































Walter Kacynski
 assigned  JENKINS-22765 to Joshua Sherwood



configuring a job show an accurev syntax output
















Change By:


Walter Kacynski
(25/Apr/14 3:14 PM)




Assignee:


ScottTatum
JoshuaSherwood



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [master-slave] (JENKINS-22494) Multiconfiguration project does not respect label restrictions

2014-04-25 Thread courtla...@gamesalad.com (JIRA)















































Courtland Jones
 commented on  JENKINS-22494


Multiconfiguration project does not respect label restrictions















This seems to be borne out with tests of my own; essentially you must use both "Restrict where this project can be built" as Mark Waite says, for the initial task, as well as using the Slaves axis, to control the execution. Forgive me if I have missed it, but, this seems to be documented nowhere.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [nunit] (JENKINS-22579) Failing to process NUnit results xml

2014-04-25 Thread dick.gi...@perkinelmer.com (JIRA)















































Dick Ginga
 commented on  JENKINS-22579


Failing to process NUnit results xml















found my problem. another user lack of knowledge. wrong formatted file



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-17999) deadlock in 1.509.1 deleting multiple jobs with REST API

2014-04-25 Thread e...@ql.org (JIRA)
















































Jay Berkenbilt
 closed  JENKINS-17999 as Duplicate


deadlock in 1.509.1 deleting multiple jobs with REST API
















This bug is no longer reproducible starting with 1.509.4. It looks like the commit 5407d9fbce6b10d6902f0cc5971ee95c71619f3a, cherry picked from 7facc7733c7040536d4074a2c5805b75ee1d8f35, which was to fix JENKINS-18589 also solved this problem. I have confirmed that I can easily reproduce the problem with 1.509.1 and can no longer reproduce it with 1.509.4. It also looks like the parameterized trigger plugin, which was then at 2.17 and is currently at 2.24, has a different code path as well. As the reporter, I'm closing this issue since I believe it no longer exists.





Change By:


Jay Berkenbilt
(25/Apr/14 3:59 PM)




Status:


Open
Closed





Resolution:


Duplicate



























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







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

[JIRA] [cppcheck] (JENKINS-22761) Missing links to source in cppcheck plugin

2014-04-25 Thread mixaltu...@users.sf.net (JIRA)
















































Michal Turek
 assigned  JENKINS-22761 to Michal Turek



Missing links to source in cppcheck plugin
















Change By:


Michal Turek
(25/Apr/14 4:04 PM)




Assignee:


GregoryBoissinot
MichalTurek



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cppcheck] (JENKINS-22761) Missing links to source in cppcheck plugin

2014-04-25 Thread mixaltu...@users.sf.net (JIRA)















































Michal Turek
 commented on  JENKINS-22761


Missing links to source in cppcheck plugin















Hi, can you attach a screenshot? The issues that were in the previous build but are solved in the current build (the green ones) doesn't contain the link, it is a "feature". It would require a change of data model and was just too difficult to implement.



























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







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

[JIRA] [plugin] (JENKINS-22766) Jenkins RTC Plugin does not work with RTC Server Version 4

2014-04-25 Thread junejo.shee...@gmail.com (JIRA)















































Sheeraz Junejo
 created  JENKINS-22766


Jenkins RTC Plugin does not work with RTC Server Version 4















Issue Type:


Bug



Affects Versions:


current



Assignee:


Deluan Quintão



Components:


plugin, rtc



Created:


25/Apr/14 4:42 PM



Description:


While accessing RTC Server for accepting Accept changes I get following exception;

$ /home/hudson/Hudson/tools/rtc-scm/jazz/scmtools/eclipse/scm.sh version
Build Id: RTC-I20120911-1740

com.ibm.team.filesystem.cli.core, version 3.1.100.v20120822_0505
  Subcommands: help version daemon daemon/start daemon/stop daemon/deregister daemon/register

com.ibm.team.filesystem.cli.client, version 3.1.100.v20120817_2130
  Subcommands: load login logout create create/workspace create/baseline create/changeset create/snapshot create/component create/loadrules create/stream changeset changeset/comment changeset/complete changeset/current changeset/relocate changeset/associate changeset/disassociate changeset/suspend changeset/resume changeset/discard changeset/extract changeset/locate change-target change-target/workspace change-target/component change-target/unset-workspace list list/workspaces list/projectareas list/teamareas list/streams list/components list/remotefiles list/credentials list/daemons list/snapshots list/locks list/properties list/changes list/users list/baselines list/changesets list/states checkin accept deliver status conflicts resolve move lastmod share discard undo compare history diff repair workspace workspace/change-target workspace/component workspace/unset workspace/add-components workspace/remove-components workspace/replace-components workspace/delete workspace/unload property property/list property/get property/set property/remove lock lock/list lock/acquire lock/release annotate snapshot snapshot/promote refresh users users/set delete delete/state-content changeaccess extract extract/file

com.ibm.team.filesystem.cli.tools, version 3.1.100.v20120817_2130
  Subcommands: tools.verify tools.validate tools.echo.stdin tools.metronome tools.pkgtest tools.configvalue tools.log
FATAL: null
java.lang.NullPointerException
	at com.deluan.jenkins.plugins.rtc.commands.AcceptCommand.init(AcceptCommand.java:30)
	at com.deluan.jenkins.plugins.rtc.JazzClient.accept(JazzClient.java:126)
	at com.deluan.jenkins.plugins.rtc.JazzClient.accept(JazzClient.java:107)
	at com.deluan.jenkins.plugins.rtc.JazzSCM.checkout(JazzSCM.java:104)
	at hudson.model.AbstractProject.checkout(AbstractProject.java:1353)
	at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:689)
	at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
	at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:594)
	at hudson.model.Run.execute(Run.java:1567)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)




Environment:


Linux AS5, Jenkins 1.506, Jenkins RTC Plugin 0.3




Project:


Jenkins



Priority:


Blocker



Reporter:


Sheeraz Junejo

























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







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

[JIRA] [plugin] (JENKINS-22766) Jenkins RTC Plugin does not work with RTC Server Version 4

2014-04-25 Thread junejo.shee...@gmail.com (JIRA)















































Sheeraz Junejo
 updated  JENKINS-22766


Jenkins RTC Plugin does not work with RTC Server Version 4
















Change By:


Sheeraz Junejo
(25/Apr/14 4:52 PM)




Component/s:


teamconcert



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-22767) AbstractLazyLoadRunMap.getById subject to race condition with .load

2014-04-25 Thread jgl...@cloudbees.com (JIRA)

Jesse Glick
created JENKINS-22767

AbstractLazyLoadRunMap.getById subject to race condition with .load

Issue Type:

Bug

Assignee:

Jesse Glick

Components:

core

Created:

25/Apr/14 4:53 PM

Description:

If Run.onLoad takes a little while to run, or generally if RunMap.retrieve is not instantaneous, a race condition can arise. Say thread 1 calls getByNumber for a Run which in fact exists on disk (with a numeric symlink). search will call load(int, null), which will delegate to load(File, null) which acquires the lock; and then blocks for a while in retrieve. Then thread 2 calls getById with the ID of the same build. index.byId is still empty, so it jumps to load(String, null) and then blocks waiting to enter load(File, null). Now thread 1 finishes retrieve, stores the newly loaded Run in the index, and returns. When the lock is released, thread 2 enters it, loads another copy of the same Run, and stores it in the index, clobbering the first entry, and returns that.

Seems to be fixable by making getById double-check the index while holding the lock, forcing it to wait for the first thread to store an entry. (Or could just check under lock whether snapshot != index, and if so, retry.)

Also load(File, null) should assert that there is no current entry for a build before it stores one.

Project:

Jenkins

Labels:

lazy-loading
threads

Priority:

Major

Reporter:

Jesse Glick

[JIRA] [core] (JENKINS-22768) Groovy Filter for Run Parameter

2014-04-25 Thread gtmacdon...@gmail.com (JIRA)















































Greg MacDonald
 created  JENKINS-22768


Groovy Filter for Run Parameter















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


25/Apr/14 5:16 PM



Description:


For matrix jobs, it would be great to be able to filter the builds by config type. For example all clean release builds.




Project:


Jenkins



Priority:


Minor



Reporter:


Greg MacDonald

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [master-slave] (JENKINS-22494) Multiconfiguration project does not respect label restrictions













































 
Mark Waite
 edited a comment on  JENKINS-22494


Multiconfiguration project does not respect label restrictions
















My apologies that it isn't documented anywhere.  I'm sure I read it somewhere, but I could not find a reference in any of the places I checked.  I think that confirms your statement that it is documented nowhere.

Would you be willing to describe it on the "Building a matrix project wiki page"?



























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







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

[JIRA] [master-slave] (JENKINS-22494) Multiconfiguration project does not respect label restrictions













































 
Mark Waite
 edited a comment on  JENKINS-22494


Multiconfiguration project does not respect label restrictions
















My apologies that it isn't documented anywhere.  I'm sure I read it somewhere, but I could not find a reference in any of the places I checked.  I think that confirms you statement that it is documented nowhere.

Would you be willing to describe it on the "Building a matrix project wiki page"?



























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







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

[JIRA] [master-slave] (JENKINS-22494) Multiconfiguration project does not respect label restrictions















































Mark Waite
 commented on  JENKINS-22494


Multiconfiguration project does not respect label restrictions















My apologies that it isn't documented anywhere.  I'm sure I read it somewhere, but I could not find a reference to that on any of the places I checked.  I think that confirms you statement that it is documented nowhere.

Would you be willing to describe it on the "Building a matrix project wiki page"?



























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







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

[JIRA] [subversion] (JENKINS-22199) Jenkins throwing errors in SCM Polling and Updates with Subversion















































Cees Bos
 commented on  JENKINS-22199


Jenkins throwing errors in SCM Polling and Updates with Subversion















We currently use the snapshot plugin, and the issues reported in this ticket does not occur anymore.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-22758) Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)















































Cees Bos
 updated  JENKINS-22758


Jenkins =1.560 breaks Jenkins slave handling / NIO JNLP related (using swarm plugin)
















Reverting to 1.559 solved the issue for us.

Version 1.560 also gave memory issues for us. Java heap kept growing. 

After the upgrade it grew up to the max value we have set. Jenkins became slower and slower.

After downgrade to 1.559 memory usage is now below 1Gb heap.





Change By:


Cees Bos
(25/Apr/14 6:04 PM)




Attachment:


usedMemory.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] [delivery-pipeline] (JENKINS-22611) Triggered by SCM multiple times
















































Patrik Boström
 resolved  JENKINS-22611 as Fixed


Triggered by SCM multiple times
















Change By:


Patrik Boström
(25/Apr/14 6:06 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] [delivery-pipeline] (JENKINS-22635) Committer names not shown in pipeline heading
















































Patrik Boström
 resolved  JENKINS-22635 as Fixed


Committer names not shown in pipeline heading
















Change By:


Patrik Boström
(25/Apr/14 6:07 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] [sauce-ondemand] (JENKINS-22055) add support for sauce connect v4

2014-04-25 Thread hinl...@hotmail.com (JIRA)















































hinling yeung
 commented on  JENKINS-22055


add support for sauce connect v4















nice! upgrading tonight.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [mask-passwords] (JENKINS-22770) Mask password plugin fails to mask password with $ character in the middle of the password

2014-04-25 Thread raghav.vaidyanat...@gmail.com (JIRA)

Raghav Vaidhyanathan
created JENKINS-22770

Mask password plugin fails to mask password with $ character in the middle of the password

Issue Type:

Bug

Affects Versions:

current

Assignee:

Daniel Petisme

Components:

mask-passwords

Created:

25/Apr/14 6:26 PM

Description:

Jenkins instance is running on a linux and i use Invoke Ant build step.
The build job is parameterized and one of the parameter is password
Ant targets are written in an xml called run.xml so I pass the arg -file run.xml -Dserver.password=apr20$1 to the ant build.

The password contains $ in the middle - like apr20$1.
The $ in the password is referenced as $1 command argument and password parameter is now changed to apr20-file ( -file is my first parameter)

The password is getting logged when i turn on the -d trace in Ant.
Setting ro property server.password=apr20-file is what i see in the console

The mask property should somehow try to address masking this information being logged. I have written my own script to introduce escape sequence in the passwords.

Due Date:

30/Apr/14 12:00 AM

Project:

Jenkins

Priority:

Critical

Reporter:

Raghav Vaidhyanathan

[JIRA] [cvs] (JENKINS-22771) CVS Plugin update adjusts version but not timestamp in CVS/Entries

2014-04-25 Thread mark.ru...@alcatel-lucent.com (JIRA)

Mark Ruedy
created JENKINS-22771

CVS Plugin update adjusts version but not timestamp in CVS/Entries

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

cvs

Created:

25/Apr/14 6:35 PM

Description:

Intermittent issue where a cvs triggered build fails to update the static custom workspace properly. A commit went into CVS at Fri Apr 25 14:49:03 2014 UTC, the build was triggered at Apr 25, 2014 7:50:10 AM PDT (less than a minute later). The CVS update modified the CVS/Entries file with the new revision but left the old timestamp. The contents of the file remained the old version, but running manual cvs status claims the file is up-to-date and on the new revision. File is proven to be not updated and has the contents of the old revision. CVS can be corrected by adjusting CVS/Entries revision back to it's true value. Then when I manually update the file, the changes are incorporated and the CVS/Entries file is left correct.

This has occurred just twice in the last month or so, but make Jenkins unsuitable since it corrupts the workspace and reports invalid build breakages.

(redacted)

X/x cvs status xx.h
===
File: xx.h Status: Up-to-date

Working revision:1.132.2.1
Repository revision: 1.132.2.1 XXX/xx.h,v
Sticky Tag: BRANCH (branch: 1.132.2)
Sticky Date: (none)
Sticky Options: (none)

CVS status is apparently not checking the contents of the file.

Here we see the truth about the file
grep \$Id xx.h

$Id: xx.h,v 1.132 2013/11/26 20:23:34 s Exp $
/

And other tests prove the local file is unchanged.

Below, a diff of CVS/Enties. The top one is from a fresh checkout of the branch and the bottom is our corrupt Jenkins workspace

/xxx.h/1.132.2.1/Fri Apr 25 14:49:03 2014//TBRANCH

/xxx.h/1.132.2.1/Tue Nov 26 20:23:34 2013//TBRANCH

Environment:

CentOS 6.4, Jenkins 1.532.2, CVS Plugin 2.11

Project:

Jenkins

Labels:

plugin
scm

Priority:

Major

Reporter:

Mark Ruedy

[JIRA] [delivery-pipeline] (JENKINS-21123) Macro for PIPELINE_VERSION
















































Patrik Boström
 assigned  JENKINS-21123 to Unassigned



Macro for PIPELINE_VERSION
















Change By:


Patrik Boström
(25/Apr/14 6:39 PM)




Assignee:


PatrikBoström



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [delivery-pipeline] (JENKINS-22751) Status QUEUED are wrong in some cases
















































Patrik Boström
 resolved  JENKINS-22751 as Fixed


Status QUEUED are wrong in some cases
















Change By:


Patrik Boström
(25/Apr/14 6:42 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] [naginator] (JENKINS-22459) NullPointerException in NaginatorActionFactory

2014-04-25 Thread netappbluede...@java.net (JIRA)















































NetAppBlueDevil
 commented on  JENKINS-22459


NullPointerException in NaginatorActionFactory















Seeing the same on Linux with 1.11 version



























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







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

[JIRA] [subversion] (JENKINS-21617) List Subversion Tags job parameter wants svn credentials but there is no way to fill it

2014-04-25 Thread lmcdon...@apriva.com (JIRA)















































linda mcdonald
 commented on  JENKINS-21617


List Subversion Tags job parameter wants svn credentials but there is no way to fill it















I am experiencing the same issue.
Jenkins v1.551
svn plugin 2.2
Subversion copy failed. svn: E200015

what is the resolution?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [publish-over-cifs] (JENKINS-12433) Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found















































Hans Loeblich
 commented on  JENKINS-12433


Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found















I'm having this same issue.  I looked at the browser request log and its checking for example:
http://servername/build/build/plugin/publish-over-cifs/help/config/removePrefix.html

My regular jenkins URL is http://servername/build/ 
Its putting the build path twice for some reason.  This is the only plugin I have noticed this issue with.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [publish-over-cifs] (JENKINS-12433) Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found















































Hans Loeblich
 commented on  JENKINS-12433


Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found















Also don't know what "Jenkins URL in mailer setup" Alex is referring to, I'm not seeing any such field on the global config page.

Jenkins 1.560
Publish over CIFS plugin 1.1.14



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [publish-over-cifs] (JENKINS-12433) Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found













































 
Hans Loeblich
 edited a comment on  JENKINS-12433


Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found
















I'm having this same issue.  I looked at the browser request log and its checking for example:
http://servername/build/build/plugin/publish-over-cifs/help/config/removePrefix.html

My regular jenkins URL is http://servername/build/ 
Its putting the "build" path twice for some reason.  This is the only plugin I have noticed this issue with.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ivy] (JENKINS-22447) Ivy Job builds don't release workspace lock due to override of cleanup















































SCM/JIRA link daemon
 commented on  JENKINS-22447


Ivy Job builds dont release workspace lock due to override of cleanup















Code changed in jenkins
User: Kevin Formsma
Path:
 src/main/java/hudson/ivy/IvyBuild.java
 src/main/java/hudson/ivy/IvyModuleSetBuild.java
http://jenkins-ci.org/commit/ivy-plugin/cff77d00d897498147229ff762f0d1a1b55c072a
Log:
  Merge pull request #14 from arothian/master

FIXED JENKINS-22447 Fix workspace lock release for ivy build


Compare: https://github.com/jenkinsci/ivy-plugin/compare/2a1932612a99...cff77d00d897




























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ivy] (JENKINS-22447) Ivy Job builds don't release workspace lock due to override of cleanup
















































SCM/JIRA link daemon
 resolved  JENKINS-22447 as Fixed


Ivy Job builds dont release workspace lock due to override of cleanup
















Change By:


SCM/JIRA link daemon
(25/Apr/14 7:29 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] [android-emulator] (JENKINS-22334) plugin thinks emulator always crashes using sdk 22.6.1

2014-04-25 Thread m...@zavislak.net (JIRA)















































Matthew Zavislak
 commented on  JENKINS-22334


plugin thinks emulator always crashes using sdk 22.6.1















Pauli Kaupppinen (or anyone else) - do you know of a workaround for Gradle builds similar to the one suggested (-Dandroid.device=usb)?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [publish-over-cifs] (JENKINS-12433) Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found













































 
Hans Loeblich
 edited a comment on  JENKINS-12433


Publish Over CIFS Plugin - Interactive Help Not Displayed - ERROR: Failed to load help file: Not Found
















Also don't know what "Jenkins URL in mailer setup" Alex is referring to, I'm not seeing any such field on the global config page.

Jenkins 1.560
Publish over CIFS plugin 0.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] [cifs] (JENKINS-22219) Publish over CIFS complains that field is empty, but actually it is filled out AND WORKS!















































Hans Loeblich
 commented on  JENKINS-22219


Publish over CIFS complains that field is empty, but actually it is filled out AND WORKS!















Same issue encountered here

I suspected maybe some _javascript_ errors but did not find any in my browser console.

Jenkins 1.559
Publish Over CIFS 0.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] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository

Robert Luberda
reopened JENKINS-22752

Initial poll (just after project creation) spawns builds for all the existing branches in repository

I am reasonably confident that in all those 3 installations there are people who find this behaviour pretty much useless and strange. To be honest I am one of such persons. Most probably reporter of https://issues.jenkins-ci.org/browse/JENKINS-15407 would be the second one ("Then, when I commit to some branch and run curl, it started building but some other branch (ancient)")

Possibly it would be much more if '**' stayed the default setting (https://issues.jenkins-ci.org/browse/JENKINS-18820 - "As a new user to the GIT SCM, I was very surprised to find out that the default (empty) value for the Branches to Build parameter attempted to pull all branches in the repo and execute the build operation on them").

I am pretty sure that most of the 3 installations do not use sophisticated configurations, probably it is just polling single master branch or polling simple repositories with a few leaf branches only, so they are not affected by this bug at all

To be honest I don't think the "users who depend on that behavior" really want jenkins to build several years old branches (especially that they might be so outdated that they are not buildable any longer). If a branch hasn't been updated for, let's say, a few months, then most probably there should be no point in building it. If you still think that there are people who really want to build ancient branches, could you please fix provide some configuration option for them, while fixing the bug?

BTW. What is really annoying that jenkins starts building in order from the most outdated branches to the most recent ones, ant what is really surprising - it builds branches, that would be skip during normal operations (see my other `not-a-bug': https://issues.jenkins-ci.org/browse/JENKINS-22591).

BTW2. The other annoying thing is that each build log is spoilt with hundreds of 'Seen branch in repository' lines...

Regards,
Robert

Change By:

Robert Luberda
(25/Apr/14 8:06 PM)

Resolution:

NotADefect

Status:

Resolved
Reopened

[JIRA] [git] (JENKINS-22591) Does not spawn build if a branch refers to the same SHA1 as another already built branch















































Robert Luberda
 commented on  JENKINS-22591


Does not spawn build if a branch refers to the same SHA1 as another already built branch















Oh, I'm not the only one who want this feature, see

https://issues.jenkins-ci.org/browse/JENKINS-11337?focusedCommentId=159670page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-159670

and other comments in that JIRA report



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ivy] (JENKINS-22447) Ivy Job builds don't release workspace lock due to override of cleanup

2014-04-25 Thread kevin.form...@gmail.com (JIRA)
















































Kevin Formsma
 assigned  JENKINS-22447 to Kevin Formsma



Ivy Job builds dont release workspace lock due to override of cleanup
















Change By:


Kevin Formsma
(25/Apr/14 8:24 PM)




Assignee:


TimothyBingaman
KevinFormsma



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [ant] (JENKINS-22772) ivy-plugin build creating duplicate numbered workspaces

2014-04-25 Thread awb...@hotmail.com (JIRA)

andrew beck
created JENKINS-22772

ivy-plugin build creating duplicate numbered workspaces

Issue Type:

Bug

Assignee:

Timothy Bingaman

Attachments:

job workspace with duplicate module workspaces.PNG

Components:

ant, ivy, subversion

Created:

25/Apr/14 8:34 PM

Description:

Our jenkin's builds using Ivy plugin 1.23.2 and Subversion plugin 1.45 is somehow creating duplicate numbered workspaces. Notice the additional "@" included in the build path. This build path is incorrect and is automatically increasing per module build. See attached screen shot.

This issue did not occur when using Jenkins ver. 1.509.2.

Console output during ivy module build:
Building remotely on odcsgcxpbat03 in workspace D:/Jenkins_eCare2/Slave/workspace/eCare2_BuildConsumerProjects/ecare-acp-messaging-api@10
No emails were triggered.
FATAL: Unable to find build script at D:/Jenkins_eCare2/Slave/workspace/eCare2_BuildConsumerProjects/ecare-acp-messaging-api@10/build.xml

Environment:

Jenkins ver.1.532.3, Ivy plugin 1.23.2, Subversion plugin 1.45

Project:

Jenkins

Labels:

ivy
subversion
jenkins
ant

Priority:

Major

Reporter:

andrew beck

[JIRA] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository















































Robert Luberda
 commented on  JENKINS-22752


Initial poll (just after project creation) spawns builds for all the existing branches in repository















I've just realized that I was wrong in my assumption that "it builds branches, that would be skip during normal operations", sorry about that.

The other things remain true, especially that building all the branches, including the ancient ones, does not makes much sense. On the other hand I would agree that building a few most fresh ones could be useful sometimes - maybe this is the behavior you wrote that users depend on?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [vsphere-cloud] (JENKINS-22740) Launcher's afterDisconnect() method is called twice

2014-04-25 Thread hrabb...@gmail.com (JIRA)















































Hossam Rabbouh
 commented on  JENKINS-22740


Launchers afterDisconnect() method is called twice















Pull request successfully merged; thanks to the team. Fix available in version 1.1.6.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [vsphere-cloud] (JENKINS-22740) Launcher's afterDisconnect() method is called twice

2014-04-25 Thread hrabb...@gmail.com (JIRA)
















































Hossam Rabbouh
 resolved  JENKINS-22740 as Fixed


Launchers afterDisconnect() method is called twice
















Change By:


Hossam Rabbouh
(25/Apr/14 9:18 PM)




Status:


Open
Resolved





Fix Version/s:


current





Resolution:


Fixed



























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







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

[JIRA] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository

Mark Waite
commented on JENKINS-22752

Initial poll (just after project creation) spawns builds for all the existing branches in repository

The use case that I've used has been that I want any new branch to be built which follows a specific naming convention, without requiring that I list the name of that branch explicitly. I use a naming convention for branches with a wildcard at the end of the "Branches to build" value. That allows multiple team members to each submit their proposal on their own branch, which the Jenkins job detects and builds.

For example, when I think I'm ready to submit a change to the git-client-plugin, I submit the change to my repository on GitHub with the branch name "master-some-description-of-the-change". The job I have defined is configured to build all branches named "/master". I don't change the job definition, and my change is evaluated.

I've used that same technique to merge proposed changes from the submitter branch to a destination branch, and then push the destination branch when the tests are successful. I'm not willing to lose that capability.

[JIRA] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository

Mark Waite
edited a comment on JENKINS-22752

Initial poll (just after project creation) spawns builds for all the existing branches in repository

[JIRA] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository

Mark Waite
edited a comment on JENKINS-22752

Initial poll (just after project creation) spawns builds for all the existing branches in repository

[JIRA] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository

Mark Waite
edited a comment on JENKINS-22752

Initial poll (just after project creation) spawns builds for all the existing branches in repository

Thanks for including the reference to JENKINS-22591. I agree with ~ndelooof that it should not be fixed, and that refining the branch specifier is the way to handle that case.

[JIRA] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository

Mark Waite
edited a comment on JENKINS-22752

Initial poll (just after project creation) spawns builds for all the existing branches in repository

Thanks for including the reference to JENKINS-22591. I agree with Nicolas De Loof that it should not be fixed, and that refining the branch specifier is the way to handle that case.

[JIRA] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository

Mark Waite
edited a comment on JENKINS-22752

Initial poll (just after project creation) spawns builds for all the existing branches in repository

I agree with Nicolas De Loof that it should not be fixed, and that refining the branch specifier is the way to handle that case.

[JIRA] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository















































Mark Waite
 updated  JENKINS-22752


Initial poll (just after project creation) spawns builds for all the existing branches in repository
















Change By:


Mark Waite
(25/Apr/14 9:31 PM)




Status:


Reopened
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] [disk-usage] (JENKINS-22773) OutOfMemoryError when calculateWorkspaceDiskUsage

2014-04-25 Thread br...@meneguello.com (JIRA)















































Bruno Meneguello
 created  JENKINS-22773


OutOfMemoryError when calculateWorkspaceDiskUsage















Issue Type:


Bug



Assignee:


Lucie Votypkova



Components:


disk-usage



Created:


25/Apr/14 9:52 PM



Description:


Getting frequent OutOfMemoryError.

Analysing the source code, I think is the DiskUsageCallable.call() creating the "exceeded" file list.

Shouldn't it be iterable to avoid large memory loads?




Project:


Jenkins



Priority:


Major



Reporter:


Bruno Meneguello

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository

Mark Waite
edited a comment on JENKINS-22752

Initial poll (just after project creation) spawns builds for all the existing branches in repository

I agree with Nicolas De Loof that it should not be fixed, and that refining the branch specifier is the way to handle that case. Refer to JENKINS-15407 for his comments.

[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)

2014-04-25 Thread jerem...@eye.fi (JIRA)















































Jeremiah Njoroge
 commented on  JENKINS-22750


Polling no longer triggers builds (regression 1.560)















also running into this issue polling a Git repo.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository















































Robert Luberda
 commented on  JENKINS-22752


Initial poll (just after project creation) spawns builds for all the existing branches in repository















I think there is some kind of misunderstanding, my bug is about git plugin behavior shortly after the job creation. 

I agree that it is useful that you can push something into "master-some-description-of-the-change" branch, and the branch gets build.

But let's imagine that after 10 years of pushing changes to different branches (and assume that many of those haven't been merged to master for any reason) your jenkins server dies (e.g. because of disk failure), and you need to set up a new job on a different server. 

Would you be glad if the new jenkins server build all those 10-or-less-years-old "master-something" branches? If no, how would you refine your "/master/" branch specifier to avoid building of old branches?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [git] (JENKINS-22752) Initial poll (just after project creation) spawns builds for all the existing branches in repository













































 
Robert Luberda
 edited a comment on  JENKINS-22752


Initial poll (just after project creation) spawns builds for all the existing branches in repository
















I think there is some kind of misunderstanding, my bug is about git plugin behavior shortly after the job creation. 

I agree that it is useful that you can push something into "master-some-description-of-the-change" branch, and the branch gets build.

But let's imagine that after 10 years of pushing changes to different branches (and assume that many of those haven't been merged to master for any reason) your jenkins server dies (e.g. because of disk failure), and you need to set up a new job on a different server. 

Would you be glad if the new jenkins server build all those 10-or-less-years-old "master-something" branches? If no, how would you refine your "/master/" branch specifier to avoid building of old branches?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] (JENKINS-22169) Migration from setenv overwrites existing envinject configuration















































SCM/JIRA link daemon
 commented on  JENKINS-22169


Migration from setenv overwrites existing envinject configuration















Code changed in jenkins
User: Gregory Boissinot
Path:
 .gitignore
 src/main/java/hudson/plugins/envfile/EnvFileBuildWrapper.java
 src/main/java/hudson/plugins/setenv/SetEnvBuildWrapper.java
 src/main/java/org/jenkinsci/plugins/envinject/migration/EnvInjectMigrationBuildWrapper.java
 src/main/java/org/jenkinsci/plugins/envinject/migration/EnvInjectMigrationListener.java
 src/test/java/org/jenkinsci/plugins/envinject/migration/EnvInjectMigrationBuildWrapperTest.java
 src/test/resources/org/jenkinsci/plugins/envinject/migration/EnvInjectMigrationBuildWrapperTest/testSetEnvAndEnvInject.zip
http://jenkins-ci.org/commit/envinject-plugin/c68558aba60280ea1d56978d827e91da5a5118e2
Log:
  Merge pull request #28 from rsandell/jenkins-22169

Fix JENKINS-22169


Compare: https://github.com/jenkinsci/envinject-plugin/compare/0287bec62dd8...c68558aba602




























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] (JENKINS-22169) Migration from setenv overwrites existing envinject configuration