date:20130208















































Jesse Glick
 commented on  JENKINS-16705


Native support for settings-security.xml (i. e. encrypted passwords)















Possibly needs integration with the Credentials plugin.



























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







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

[JIRA] (JENKINS-16722) New users in people list after security scan
















































Jesse Glick
 resolved  JENKINS-16722 as Incomplete


New users in people list after security scan
















Well if any code calls User.get("some name") then a User with that name is created and cached in the system, and /asynchPeople (i.e. the People list from top level, not inside any view or folder) will show such transient users. But I do not know how such users would have been created unless your security realm let something log in with those names.

By the way if you believe you have found a reproducible security vulnerability, please file in the SECURITY component rather than the general issue tracker.





Change By:


Jesse Glick
(09/Feb/13 12:53 AM)




Status:


Open
Resolved





Resolution:


Incomplete



























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







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

[JIRA] (JENKINS-16722) New users in people list after security scan













































  
Jesse Glick
 edited a comment on  JENKINS-16722


New users in people list after security scan
















Well if any code calls User.get("some name") then a User with that name is created and cached in the system, and /asynchPeople (i.e. the People list from top level, not inside any view or folder) will show such transient users. But I do not know how such users would have been created unless your security realm let something log in with those names.

By the way if you believe you have found a reproducible security vulnerability, please file in the SECURITY project rather than the general issue tracker.



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable















































Alex Earl
 commented on  JENKINS-16716


FILE token does not evaluate a path that contains an environment variable















Yes, when you upgrade plugins, you need to restart Jenkins. 2.21 would definitely throw the exception for a file it couldn't find. 



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable















































Valerie Wagner
 commented on  JENKINS-16716


FILE token does not evaluate a path that contains an environment variable















Yes, the file definitely exists. I'm using 2.21. Actually I thought I upgraded to 2.25 earlier today in an attempt to see if it would fix it, but perhaps I need to restart Jenkins to get that to take effect. I'll give it a try.



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable















































Alex Earl
 commented on  JENKINS-16716


FILE token does not evaluate a path that contains an environment variable















That file exists relative to the workspace root? Also, what version of the plugin are you using? There was a version that threw an exception like you are seeing if the file didn't exist. I fixed that, but I don't remember what version it was.



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable















































Valerie Wagner
 commented on  JENKINS-16716


FILE token does not evaluate a path that contains an environment variable















I don't want to hijack this issue if mine is different. But perhaps adding a space above will solve kavita's original problem. As far as I can tell, this is exactly what my syntax should be:

${FILE, path="sw/java/libs/testutils/build/testng-changes.html"}

I've triple checked that the path is right & the file exists.  Incidentally, this now gives me an exception:

ERROR: Could not send email as a part of the post-build publishers.
java.lang.NullPointerException
	at java.util.regex.Matcher.quoteReplacement(Matcher.java:655)
	at hudson.plugins.emailext.plugins.ContentBuilder$Tokenizer.appendReplacement(ContentBuilder.java:211)
	at hudson.plugins.emailext.plugins.ContentBuilder.replaceTokensWithContent(ContentBuilder.java:112)
	at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:82)
	at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:482)
	at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:314)
	at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:259)
	at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:251)
	at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:211)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:192)
	at hudson.model.Run.execute(Run.java:1601)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)

Perhaps I should open a separate issue?

Thanks for your help!



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable















































Alex Earl
 commented on  JENKINS-16716


FILE token does not evaluate a path that contains an environment variable















Hmmm, I'll give it a shot locally.



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable















































Valerie Wagner
 commented on  JENKINS-16716


FILE token does not evaluate a path that contains an environment variable















I've tried it with & without a space. And with relative paths. Neither works for me.



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable















































Alex Earl
 commented on  JENKINS-16716


FILE token does not evaluate a path that contains an environment variable















It only works with workspace relative paths. Also, you need a space between the , and the path.



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable















































Valerie Wagner
 commented on  JENKINS-16716


FILE token does not evaluate a path that contains an environment variable















Does the $FILE token work at all? I'm trying to use it with literal paths and I get the same result as you once your environment variable has been substituted. Perhaps it's not the variable replacement that is broken but the file inclusion mechanism itself.

If I put in something like:

${FILE,path="custom_info.txt"}

That literal string appears in my email. I've tried all sorts of combinations of relative & absolute paths and I can't get any other result.



























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







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

[JIRA] (JENKINS-10893) Error when using Integrate to upstream upon successful build on branch project

2013-02-08 Thread javier.ortiz...@gmail.comt (JIRA)















































javydreamercsw
 commented on  JENKINS-10893


Error when using Integrate to upstream upon successful build on branch project















I thought it was the same issue but after reviewing the stack trace I opened a different issue: https://issues.jenkins-ci.org/browse/JENKINS-16723



























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







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

[JIRA] (JENKINS-16723) NPE when performing integration.

2013-02-08 Thread javier.ortiz...@gmail.comt (JIRA)















































javydreamercsw
 created  JENKINS-16723


NPE when performing integration.















Issue Type:


Bug



Affects Versions:


current



Assignee:


Kohsuke Kawaguchi



Components:


svnmerge



Created:


08/Feb/13 11:08 PM



Description:


I got the following error after it was working, without changes, on the previous job. I believe I re-ran the job and this time there were no changes on the branch. Not sure if this has something to do with it.

ERROR: Publisher jenkins.plugins.svnmerge.IntegrationPublisher aborted due to exception
java.lang.NullPointerException
	at org.tmatesoft.svn.core.SVNException.(SVNException.java:50)
	at org.tmatesoft.svn.core.SVNException.(SVNException.java:37)
	at jenkins.plugins.svnmerge.FeatureBranchProperty$2.invoke(FeatureBranchProperty.java:273)
	at jenkins.plugins.svnmerge.FeatureBranchProperty$2.invoke(FeatureBranchProperty.java:247)
	at hudson.FilePath.act(FilePath.java:865)
	at hudson.FilePath.act(FilePath.java:838)
	at jenkins.plugins.svnmerge.FeatureBranchProperty.integrate(FeatureBranchProperty.java:247)
	at jenkins.plugins.svnmerge.IntegrateAction.perform(IntegrateAction.java:141)
	at jenkins.plugins.svnmerge.IntegrateAction.perform(IntegrateAction.java:130)
	at jenkins.plugins.svnmerge.IntegrationPublisher.perform(IntegrationPublisher.java:47)
	at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:27)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:810)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:785)
	at hudson.model.Build$BuildExecution.post2(Build.java:183)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:732)
	at hudson.model.Run.execute(Run.java:1582)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:236)




Project:


Jenkins



Priority:


Major



Reporter:


javydreamercsw

























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







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

[JIRA] (JENKINS-16666) Jabber plugins stops working after upgrading to Jenkins 1.499

2013-02-08 Thread lpu...@sproutloud.com (JIRA)















































Laurentius Purba
 commented on  JENKINS-1


Jabber plugins stops working after upgrading to Jenkins 1.499















Hi kutzi,

I tried downloading and re-install jenkins, and it still gives me the same error.

FATAL: hudson/model/ResultTrend
java.lang.NoClassDefFoundError: hudson/model/ResultTrend
	at hudson.plugins.im.build_notify.SummaryOnlyBuildToChatNotifier.buildCompletionMessage(SummaryOnlyBuildToChatNotifier.java:39)
	at hudson.plugins.im.build_notify.DefaultBuildToChatNotifier.buildCompletionMessage(DefaultBuildToChatNotifier.java:50)
	at hudson.plugins.im.IMPublisher.notifyChatsOnBuildEnd(IMPublisher.java:577)
	at hudson.plugins.im.IMPublisher.notifyOnBuildEnd(IMPublisher.java:304)
	at hudson.plugins.im.IMPublisher.perform(IMPublisher.java:291)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:630)
	at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:608)
	at hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:584)
	at hudson.model.Build$RunnerImpl.post2(Build.java:159)
	at hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:553)
	at hudson.model.Run.run(Run.java:1391)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:145)
Caused by: java.lang.ClassNotFoundException: hudson.model.ResultTrend
	at org.aspectj.weaver.bcel.ExtensibleURLClassLoader.findClass(ExtensibleURLClassLoader.java:54)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
	at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
	... 15 more

While below is from catalina.log

INFO: Trying to reconnect
Feb 8, 2013 5:55:36 PM hudson.plugins.jabber.im.transport.JabberIMConnection createConnection
INFO: Trying to connect to XMPP on chat.MYDOMAIN.com:5222/chat.MYDOMAIN.com with SASL
Feb 8, 2013 5:55:36 PM hudson.plugins.jabber.im.transport.JabberIMConnection setupSubscriptionMode
INFO: Accepting all subscription requests
Feb 8, 2013 5:55:36 PM hudson.plugins.jabber.im.transport.JabberIMConnection connect
INFO: Connected to XMPP on chat.MYDOMAIN.com:5222/chat.MYDOMAIN.com using TLS

Any idea?

Thanks!
-Laurent



























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







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

[JIRA] (JENKINS-16722) New users in people list after security scan

2013-02-08 Thread adam.mur...@redgiantmobile.com (JIRA)

Adam Murphy
created JENKINS-16722

New users in people list after security scan

Issue Type:

Bug

Assignee:

Unassigned

Attachments:

Screen Shot 2013-02-07 at 4.37.15 PM.png

Components:

core

Created:

08/Feb/13 10:50 PM

Description:

After running a security scan of our instance of Jenkins there were users in the people list that should not be there. We can recreate the issue but are unable to collect information pertinent to pointing exactly to how the users ended up in the system. We're willing to provide additional information with guidance from the project. This may be an issue of security since each of those people are assigned an API key. If there was a way to obtain the API key then the method by which the scanner was able to create the users in the people list could eventually lead to access.

Project:

Jenkins

Priority:

Major

Reporter:

Adam Murphy

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

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

[JIRA] (JENKINS-16721) Task is not available from release plugin options

2013-02-08 Thread javier.ortiz...@gmail.comt (JIRA)















































javydreamercsw
 created  JENKINS-16721


Task is not available from release plugin options















Issue Type:


Improvement



Affects Versions:


current



Assignee:


k2nakamura



Components:


svn-tag



Created:


08/Feb/13 10:42 PM



Description:


In some cases, like when releasing from trunk, it would be nice to have this available within the release build context. Right now is only available outside of it but I want to have it only when I schedule a release.




Project:


Jenkins



Priority:


Major



Reporter:


javydreamercsw

























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







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

[JIRA] (JENKINS-10893) Error when using Integrate to upstream upon successful build on branch project

2013-02-08 Thread javier.ortiz...@gmail.comt (JIRA)













































  
javydreamercsw
 edited a comment on  JENKINS-10893


Error when using Integrate to upstream upon successful build on branch project
















I have the same issue. It was successful once and then failed afterwards.

Any work around/fix?



























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







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

[JIRA] (JENKINS-10893) Error when using Integrate to upstream upon successful build on branch project

2013-02-08 Thread javier.ortiz...@gmail.comt (JIRA)















































javydreamercsw
 commented on  JENKINS-10893


Error when using Integrate to upstream upon successful build on branch project















I have the same issue. Any work around/fix?



























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







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

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

2013-02-08 Thread johno.crawf...@gmail.com (JIRA)















































Johno Crawford
 commented on  JENKINS-15156


Builds disappear from build history after completion















Current build stability is STABLE, see https://ci.jenkins-ci.org/job/jenkins_main_trunk/ .



























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable
















































Alex Earl
 assigned  JENKINS-16716 to Alex Earl



FILE token does not evaluate a path that contains an environment variable
















Change By:


Alex Earl
(08/Feb/13 8:37 PM)




Assignee:


Alex Earl



























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







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

[JIRA] (JENKINS-16701) As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request

2013-02-08 Thread manuel.delape...@liferay.com (JIRA)
















































Manuel de la Peña
 assigned  JENKINS-16701 to Honza Brázdil



As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request
















Change By:


Manuel de la Peña
(08/Feb/13 8:31 PM)




Assignee:


Manuel de la Peña
Honza Brázdil



























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







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

[JIRA] (JENKINS-13742) Field validation does not pass required query parameters when some fields are specified in a nested Describable

2013-02-08 Thread jmcna...@collab.net (JIRA)















































John McNally
 commented on  JENKINS-13742


Field validation does not pass required query parameters when some fields are specified in a nested Describable















Kohsuke,
As you pointed out there was some work in the collabnet plugin which could improve this behavior and I have used this issue for a commit to the plugin.  However, there are a couple of issues in the core that still prevent the plugin from optimium behavior.  Feel free to assign this issue to me. But could you look at JENKINS-16676 and JENKINS-16719 for bugs in core Jenkins?



























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







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

[JIRA] (JENKINS-16701) As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request

2013-02-08 Thread manuel.delape...@liferay.com (JIRA)















































Manuel de la Peña
 commented on  JENKINS-16701


As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request















I've sent a pull request here: https://github.com/jenkinsci/ghprb-plugin/pull/7

Thanks!



























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







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

[JIRA] (JENKINS-16701) As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request

2013-02-08 Thread manuel.delape...@liferay.com (JIRA)
















































Manuel de la Peña
 assigned  JENKINS-16701 to Manuel de la Peña



As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request
















Change By:


Manuel de la Peña
(08/Feb/13 8:29 PM)




Assignee:


Honza Brázdil
Manuel de la Peña



























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







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

[JIRA] (JENKINS-16701) As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request

2013-02-08 Thread manuel.delape...@liferay.com (JIRA)















































Manuel de la Peña
 started work on  JENKINS-16701


As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request
















Change By:


Manuel de la Peña
(08/Feb/13 8:29 PM)




Status:


Open
In Progress



























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







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

[JIRA] (JENKINS-16719) Combobox with relative dependencies does not work

2013-02-08 Thread jmcna...@collab.net (JIRA)















































John McNally
 commented on  JENKINS-16719


Combobox with relative dependencies does not work















Pull request including test:
https://github.com/jenkinsci/jenkins/pull/700



























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







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

[JIRA] (JENKINS-16343) Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.

2013-02-08 Thread r...@wright.org (JIRA)















































Roy Wright
 commented on  JENKINS-16343


Access to the Subversion repository doesn't work via the subversion plugin - Always get a E200015: No credential to try. Authentication failed error.















I hit this issue on a new installation.  What's happening is the subversion access to the repository from the jenkins account is not initialized.

What you need to do is:

log into your account
sudo -i
su jenkins

cd /tmp
svn checkout https://part/of/your/repository

Subversion will prompt you for required credentials.

Once you have successfully checked out part of your repository, choosing to save credentials, you can exit the jenkins account and the sudo, then go back to your browser and your job configuration.

HTH



























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







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

[JIRA] (JENKINS-16720) Android SDK installation fails

2013-02-08 Thread botte...@gmail.com (JIRA)

Hugo Visser
created JENKINS-16720

Android SDK installation fails

Issue Type:

Bug

Affects Versions:

current

Assignee:

Christopher Orr

Components:

android-emulator

Created:

08/Feb/13 8:10 PM

Description:

When installing and updating the Android SDK, the installation fails, because an obsolete flat (-o) is used. I think it should use --all.

Here's a log:

[android] Searching for Android projects...
[android] Project file 'project.properties' requires platform 'android-15'
[android] No Android SDK found; let's install it automatically...
Downloading and installing Android SDK from http://dl.google.com/android/android-sdk_r21.0.1-macosx.zip
[android] Base SDK installed successfully
[android] Going to install required Android SDK components...
[android] Installing the 'platform-tool,tool' SDK component(s)...
$ /Users/hugo/Code/jenkins/slave/tools/android-sdk/tools/android update sdk -u -o -t platform-tool,tool
Error: Flag '-o' is not valid for 'update sdk'.

Usage:
android [global options] update sdk [action options]
Global options:
-h --help : Help on a specific command.
-v --verbose: Verbose mode, shows errors, warnings and all messages.
--clear-cache: Clear the SDK Manager repository manifest cache.
-s --silent : Silent mode, shows errors only.

Action "update sdk":
Updates the SDK by suggesting new platforms to install if available.
Options:
--proxy-port: HTTP/HTTPS proxy port (overrides settings if defined)
--proxy-host: HTTP/HTTPS proxy host (overrides settings if defined)
-s --no-https : Uses HTTP instead of HTTPS (the default) for downloads.
-a --all : Includes all packages (such as obsolete and non-dependent
ones.)
-f --force : Forces replacement of a package or its parts, even if
something has been modified.
-u --no-ui : Updates from command-line (does not display the GUI)
-p --obsolete : Deprecated. Please use --all instead.
-t --filter: A filter that limits the update to the specified types of
packages in the form of a comma-separated list of
[platform, system-image, tool, platform-tool, doc, sample,
source]. This also accepts the identifiers returned by
'list sdk --extended'.
-n --dry-mode : Simulates the update but does not download or install
anything.
[android] Android SDK installation failed
Build step 'Install Android project prerequisites' marked build as failure
Archiving artifacts
Finished: FAILURE

Project:

Jenkins

Priority:

Major

Reporter:

Hugo Visser

[JIRA] (JENKINS-16719) Combobox with relative dependencies does not work

2013-02-08 Thread jmcna...@collab.net (JIRA)















































John McNally
 created  JENKINS-16719


Combobox with relative dependencies does not work















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


08/Feb/13 7:51 PM



Description:


A combobox whose fill method involves RelativePath arguments will have those arguments set to null.  The fix is very simply to increase an index on the Behaviour.specify call.  A pull request including test will be entered shortly.




Project:


Jenkins



Priority:


Major



Reporter:


John McNally

























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







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

[JIRA] (JENKINS-16718) non-hacky way to access current build

2013-02-08 Thread nicolas.del...@gmail.com (JIRA)
















































Nicolas De Loof
 resolved  JENKINS-16718 as Won't Fix


non-hacky way to access current build
















groovy plugin already exposes 
shell.setVariable("build", build);
shell.setVariable("launcher", launcher);
shell.setVariable("listener", listener);
shell.setVariable("out", listener.getLogger());

so this is a documentation issue





Change By:


Nicolas De Loof
(08/Feb/13 7:31 PM)




Status:


Open
Resolved





Assignee:


vjuranek
Nicolas De Loof





Resolution:


Won't Fix



























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







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

[JIRA] (JENKINS-15748) fix Executor.interrupt(ABORTED) to let Groovy script cancel a build

2013-02-08 Thread nicolas.del...@gmail.com (JIRA)
















































Nicolas De Loof
 resolved  JENKINS-15748 as Won't Fix


fix Executor.interrupt(ABORTED) to let Groovy script cancel a build
















Both options are hacky, as they rely on implementation details. There is no guarantee this will work after an upgrade or that using some plugins may not interfere and change behavior. The sole "official" way to cancel a build is the '/stop' URI, so use build.doStop(). 





Change By:


Nicolas De Loof
(08/Feb/13 7:29 PM)




Status:


Open
Resolved





Assignee:


vjuranek
Nicolas De Loof





Resolution:


Won't Fix



























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







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

[JIRA] (JENKINS-16718) non-hacky way to access current build

2013-02-08 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 created  JENKINS-16718


non-hacky way to access current build















Issue Type:


Bug



Assignee:


vjuranek



Components:


groovy



Created:


08/Feb/13 7:18 PM



Description:


documentation on https://wiki.jenkins-ci.org/display/JENKINS/Groovy+plugin explains how to retrieve the current build, as Thread.currentThread().executable.
This looks like a hack, and an implementation detail.

a variable bound to groovy shell, or a method to retrieve the current build would be far cleaner.




Project:


Jenkins



Priority:


Major



Reporter:


Nicolas De Loof

























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







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

[JIRA] (JENKINS-16717) Message Box in browser "failed to evaluate. Invalid Argument" when clicking "test email configuration"















































Markus KARG
 created  JENKINS-16717


Message Box in browser "failed to evaluate. Invalid Argument" when clicking "test email configuration"















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


mail



Created:


08/Feb/13 7:11 PM



Description:


When clicking the button "test email configuration", IE9 shows a message box saying "failed to evaluate. Invalid Argument.". Strange but true: The mail actually IS getting sent!




Environment:


Win 7 IE9




Project:


Jenkins



Priority:


Major



Reporter:


Markus KARG

























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







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

[JIRA] (JENKINS-16716) FILE token does not evaluate a path that contains an environment variable

2013-02-08 Thread tiwar...@gmail.com (JIRA)

Kavita Tiwari
created JENKINS-16716

FILE token does not evaluate a path that contains an environment variable

Issue Type:

Improvement

Assignee:

Unassigned

Components:

email-ext

Created:

08/Feb/13 6:36 PM

Description:

When I try the following in the Default Content of the Editable E-mail Notification:

${FILE,path="$MY_FILE_PATH"}

The contents of the file specified by the path do not get displayed. I have MY_FILE_PATH defined as a property in a properties file that is injected into the environment in the "Prepare an environment for the run" option where the full path of the property file is specified.

The property file defines: MY_FILE_PATH=custom_info.txt

where "custom_info.txt" is a file in the workspace of the job that contains some text that I would like to display as part of the e-mail.

What is strange is that when I receive the e-mail, this appears:

${FILE,path="custom_info.txt"}

So the email-ext plugin evaluates the environment variable MY_FILE_PATH, but the FILE token does not evaluate it as a path.

The ability to have the FILE token evaluate a path that contains an environment variable would be useful for displaying different information depending on which file path is stored in the environment variable.

I am running Jenkins 1.480.2.

Due Date:

15/Feb/13 12:00 AM

Project:

Jenkins

Priority:

Minor

Reporter:

Kavita Tiwari

[JIRA] (JENKINS-5413) SCM polling getting hung

2013-02-08 Thread r...@cmbasics.com (JIRA)















































Raja Aluri
 commented on  JENKINS-5413


SCM polling getting hung















For people who are on windows and want to setup a scheduled task. Here is a oneliner in powershell.

PS C:\Users\jenkins>
PS C:\Users\jenkins>
PS C:\Users\jenkins>
PS C:\Users\jenkins> tasklist /FI "IMAGENAME eq ssh.exe" /FI "Status eq Unknown" /NH | %{ $_.Split(' *',[StringSplitOptions]"RemoveEmptyEntries")[1]}  |ForEach-Object {taskkill /F /PID $_}
PS C:\Users\jenkins>
PS C:\Users\jenkins>
PS C:\Users\jenkins>
PS C:\Users\jenkins>




























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







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

[JIRA] (JENKINS-13978) Add posibility to copy view

2013-02-08 Thread nickbo...@gmail.com (JIRA)















































Nick Boldt
 commented on  JENKINS-13978


Add posibility to copy view















Same here. This would be incredibly handy for spawning new views to track new branches (and the accompanying jobs for that new 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/groups/opt_out.

[JIRA] (JENKINS-15156) Builds disappear from build history after completion

2013-02-08 Thread linards.liep...@gmail.com (JIRA)















































Linards L
 commented on  JENKINS-15156


Builds disappear from build history after completion















hmm. Is there any hope to get this fix-set STABLE? 



























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







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

[JIRA] (JENKINS-16714) Plugin dynamic load doesn't init PeriodicWork and AperiodicWork extensions

2013-02-08 Thread aba...@java.net (JIRA)















































abayer
 commented on  JENKINS-16714


Plugin dynamic load doesn't init PeriodicWork and AperiodicWork extensions















Ok, it looks like dynamicLoad(..) never ends up calling PeriodicWork.run() - I'm not sure where that's supposed to be called normally.



























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







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

[JIRA] (JENKINS-16715) Multijob builder creates two ParameterActions when using parameters from triggering job.

2013-02-08 Thread cjo9...@java.net (JIRA)

cjo9900
created JENKINS-16715

Multijob builder creates two ParameterActions when using parameters from triggering job.

Issue Type:

Bug

Assignee:

Unassigned

Components:

jenkins-multijob-plugin

Created:

08/Feb/13 5:22 PM

Description:

From Email Chain
https://groups.google.com/d/topic/jenkinsci-dev/mqyMUbLT-Ac/discussion

The job is triggered by a phase in a Multijob (Jenkins Multijob plugin v1.7), with the default "current job parameters" setting.

This produces a build.xml with two ParametersAction elements: the first is from the Multijob build which triggered this job, the second is the default parameters for the current job.

The buildstep sees the first block, but the publisher sees the second block.

If I use a parameterized trigger to launch a third job, that one has only one set of parameters, and works as expected. It also managed to capture the parameters as seen by the buildstep, so it has the value I put into the original Multijob build page.

Does this imply that the problem is in the Multijob plugin?

Just looked at the case you mentioned and can reproduce it, from what I can see in the Multijob plugin, it creates both of the Parameter actions itself, and does not seem to combine them.

and then due to the way that the Enviroment variables are provided to the different items via build.getBuildVariables() (added to launcher) and via build.getEnviroment() causes you to only see one of the sets of the values as they override eachother.

at [1] in the code it creates the default parameters from the job to be triggered. not added to the actions list.
At [2] it gets the parameters from the build that is triggering it and merges it with any actions already added to the list. if none already exist it creates a new one and adds it.
At [3] It gets additional actions from the configs (Add Parameters items) and merges/adds these as needed

At [4] it then adds the default parameters to the action list created at [1] which I think is the error causing the duplicate ParametersAction.
These two lines should be moved to [1] and added to the action list first, and all other code will merge with these default Parameters overriding as necessary.

Please create a Issue on that plugin reporting this.
I have created an Issue for this

[1] https://github.com/jenkinsci/tikal-multijob-plugin/blob/master/src/main/java/com/tikal/jenkins/plugins/multijob/PhaseJobsConfig.java#L292
[2] https://github.com/jenkinsci/tikal-multijob-plugin/blob/master/src/main/java/com/tikal/jenkins/plugins/multijob/PhaseJobsConfig.java#L297
[3] https://github.com/jenkinsci/tikal-multijob-plugin/blob/master/src/main/java/com/tikal/jenkins/plugins/multijob/PhaseJobsConfig.java#L312
[4] https://github.com/jenkinsci/tikal-multijob-plugin/blob/master/src/main/java/com/tikal/jenkins/plugins/multijob/PhaseJobsConfig.java#L321

Environment:

Multijob plugin 1.7

Jenkins 1.498

Project:

Jenkins

Priority:

Major

Reporter:

cjo9900

[JIRA] (JENKINS-16710) Confluence publisher: Add boolean to choose whether to perform publish action if plugin sees page does not exist

2013-02-08 Thread jhans...@meetme.com (JIRA)















































Joe Hansche
 commented on  JENKINS-16710


Confluence publisher: Add boolean to choose whether to perform publish action if plugin sees page does not exist















I'm not sure I would make it a checkbox based on if the page exists, but making it so the plugin does not cause the build to fail (or give the option to fail the build if publishing does not succeed) makes sense.



























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







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

[JIRA] (JENKINS-16714) Plugin dynamic load doesn't init PeriodicWork and AperiodicWork extensions

2013-02-08 Thread aba...@java.net (JIRA)















































abayer
 created  JENKINS-16714


Plugin dynamic load doesn't init PeriodicWork and AperiodicWork extensions















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


08/Feb/13 5:06 PM



Description:


PluginManager.dynamicLoad(..) doesn't properly load/init extensions of PeriodWork and AperiodicWork. Still trying to figure out why. =)




Project:


Jenkins



Priority:


Minor



Reporter:


abayer

























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







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

[JIRA] (JENKINS-16671) Multiple Selective Claiming of Broken Builds

2013-02-08 Thread savier...@gmail.com (JIRA)
















































Ankur Goyal
 assigned  JENKINS-16671 to Ankur Goyal



Multiple Selective Claiming of Broken Builds
















Change By:


Ankur Goyal
(08/Feb/13 5:03 PM)




Assignee:


Christian Åkerström
Ankur Goyal



























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







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

[JIRA] (JENKINS-16671) Multiple Selective Claiming of Broken Builds

2013-02-08 Thread savier...@gmail.com (JIRA)















































Ankur Goyal
 updated  JENKINS-16671


Multiple Selective Claiming of Broken Builds
















Change By:


Ankur Goyal
(08/Feb/13 5:04 PM)




Assignee:


Ankur Goyal
Christian Åkerströ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/groups/opt_out.

[JIRA] (JENKINS-15974) FATAL: Failed to link the library: interface hudson.util.jna.Kernel32

2013-02-08 Thread vladdruss...@gmail.com (JIRA)















































VladDRussian
 commented on  JENKINS-15974


FATAL: Failed to link the library: interface hudson.util.jna.Kernel32















I hit the same thing after i upgraded to 1.500.  Around the time i saw the below error as well as original posted.  After a restart / reupdate. i was able to run a job on the node again.

Feb 8, 2013 2:25:53 AM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record run
WARNING: Failed to monitor FFX-MOM-BLD10 for Free Swap Space
java.io.IOException: Remote call on FFX-MOM-BLD10 failed
	at hudson.remoting.Channel.call(Channel.java:681)
	at hudson.node_monitors.SwapSpaceMonitor$1.monitor(SwapSpaceMonitor.java:83)
	at hudson.node_monitors.SwapSpaceMonitor$1.monitor(SwapSpaceMonitor.java:81)
	at hudson.node_monitors.AbstractNodeMonitorDescriptor$Record.run(AbstractNodeMonitorDescriptor.java:219)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class org.jvnet.hudson.Windows$MEMORYSTATUSEX
	at org.jvnet.hudson.Windows.monitor(Windows.java:40)
	at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:113)
	at hudson.node_monitors.SwapSpaceMonitor$MonitorTask.call(SwapSpaceMonitor.java:99)
	at hudson.remoting.UserRequest.perform(UserRequest.java:118)
	at hudson.remoting.UserRequest.perform(UserRequest.java:48)
	at hudson.remoting.Request$2.run(Request.java:326)
	at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at hudson.remoting.Engine$1$1.run(Engine.java:60)
	at java.lang.Thread.run(Unknown Source)



























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







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

[JIRA] (JENKINS-16678) java.lang.NoSuchMethodError: hudson.model.Job.hasCascadingProject
















































Jesse Glick
 resolved  JENKINS-16678 as Not A Defect


java.lang.NoSuchMethodError: hudson.model.Job.hasCascadingProject
















You are apparently using a Hudson fork of the Subversion plugin which will not work on Jenkins. Remove it and install the Jenkins plugin instead.





Change By:


Jesse Glick
(08/Feb/13 4:28 PM)




Status:


Open
Resolved





Resolution:


Not A Defect



























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







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

[JIRA] (JENKINS-16664) No GUI for adding multiple update centers















































Jesse Glick
 updated  JENKINS-16664


No GUI for adding multiple update centers
















Note that as of 1.483 Jenkins will at least display non-default update centers.

A GUI to manage them may be trickier. Each needs to have a unique ID (so the proposed UI would not fly); and they typically have their own certificates too.

(As an aside, Jenkins Enterprise by CloudBees includes a plugin which can create custom UCs that can incorporate upstream UCs but add custom additions; and then generates a plugin on the fly which can be installed in another Jenkins instance to connect to this custom UC including certificate.)





Change By:


Jesse Glick
(08/Feb/13 4:25 PM)




Issue Type:


Bug
New Feature





Environment:


WIN7



























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







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

[JIRA] (JENKINS-16686) Add support of Java-less slaves (typically for WinRT / Windows on ARM)

2013-02-08 Thread peter_kl...@affirmednetworks.com (JIRA)
















































Jesse Glick
 resolved  JENKINS-16686 as Won't Fix


Add support of Java-less slaves (typically for WinRT / Windows on ARM)
















Sorry, there is no way—the slave agent is just a bootstrapper which loads arbitrary Java code from plugins running build steps and more. You would need to run a slave agent on a proxy machine of some kind and then configure your job to run some sort of remote command on the WinRT system.





Change By:


Jesse Glick
(08/Feb/13 4:20 PM)




Status:


Open
Resolved





Resolution:


Won't Fix



























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







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

[JIRA] (JENKINS-14336) Too many open files upon HTTP listener init or shutdown















































Peter Kline
 commented on  JENKINS-14336


Too many open files upon HTTP listener init or shutdown















Same here for us, Jenkins 1.500 on Centos 5.8 Java 1.6.38
Only solution is for us to restart Jenkins.  



























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







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

[JIRA] (JENKINS-16713) Mask Passwords config does not work in Hudson 3.0.0

2013-02-08 Thread karsten.guent...@continental-corporation.com (JIRA)















































Karsten Günther
 created  JENKINS-16713


Mask Passwords config does not work in Hudson 3.0.0















Issue Type:


Bug



Affects Versions:


current



Assignee:


Daniel Petisme



Components:


mask-passwords



Created:


08/Feb/13 3:39 PM



Description:


I am not sure, whether this is the right place for reporting bugs related to Hudson. But the plugin is hosted here, so I report here. Hope, that does not offend anyone.

In the global Hudson config no name/value pairs are accepted for masked environment variables. Log file has the following entry:


Feb 08, 2013 3:40:02 PM com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsConfig load
WARNING: No configuration found for Mask Passwords plugin
Feb 08, 2013 3:43:04 PM com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsBuildWrapper$DescriptorImpl configure
SEVERE: Failed to save Mask Passwords plugin configuration
net.sf.json.JSONException: JSONObject["maskedParamDefs"] is not a JSONArray.
	at net.sf.json.JSONObject.getJSONArray(JSONObject.java:2038)
	at com.michelin.cio.hudson.plugins.maskpasswords.MaskPasswordsBuildWrapper$DescriptorImpl.configure(MaskPasswordsBuildWrapper.java:226)
	at hudson.model.Hudson.configureDescriptor(Hudson.java:2525)
	at hudson.model.Hudson.doConfigSubmit(Hudson.java:2480)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:601)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:274)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:141)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:80)
	at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:95)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:45)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:565)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:650)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:481)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:152)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:648)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1336)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:86)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179)
	at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
	at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:89)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:89)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:78)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:81)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:73)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:157)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:70)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1307)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:453)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:534)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
	at org.eclipse.je

[JIRA] (JENKINS-16712) Let people pick SVN URL from a tree-like view















































Markus KARG
 created  JENKINS-16712


Let people pick SVN URL from a tree-like view















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


subversion



Created:


08/Feb/13 3:36 PM



Description:


Many SVN GUIs, e. g. TortoiseSVN or Eclipse's Subversive Plugin, allow people to pick URLs from a tree-like view. This makes it easy and error-free to select the right (possibly lenghty or complex) URL.

It would be great if the Jenkins SVN plugin would allow to pick a SVN URL from such a tree-like view, e. g. the could be a small button right to the URL field in a job. 




Project:


Jenkins



Labels:


svn
url




Priority:


Major



Reporter:


Markus KARG

























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







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

[JIRA] (JENKINS-16711) Cannot process %20 in repository URL















































Markus KARG
 created  JENKINS-16711


Cannot process %20 in repository URL















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


subversion



Created:


08/Feb/13 3:32 PM



Description:


A URL cannot contain blains. According to the RFC, all blanks (and some other characters) have to be encoded as %20 etc. As a result, "svn info" shows correct URLs (i. e. URLs with %20 in it, not with blanks in it).

When providing a URL with %20 in it to the Jenkins GUI, Jenkins makes two errors:
(1) It says that this URL is not in the repository, which is simply wrong.
(2) It can checkout using this URL but is unable to further proceed.

So the syntax handling should be improved.




Project:


Jenkins



Labels:


url-encoding
svn




Priority:


Critical



Reporter:


Markus KARG

























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







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

[JIRA] (JENKINS-16637) problems exposing P4CLIENT and P4PASSWD to env

2013-02-08 Thread rob.pe...@gmail.com (JIRA)















































Rob Petti
 commented on  JENKINS-16637


problems exposing P4CLIENT and P4PASSWD to env















Unfortunately it can't be fixed by the perforce plugin. I would double check the options you are using in the envinject plugin and try different combinations. If I recall correctly, some of them cause weird issues with other plugins, especially the "Keep X" checkboxes.



























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







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

[JIRA] (JENKINS-16710) Confluence publisher: Add boolean to choose whether to perform publish action if plugin sees page does not exist

2013-02-08 Thread acolic...@gmail.com (JIRA)

sid nancy
created JENKINS-16710

Confluence publisher: Add boolean to choose whether to perform publish action if plugin sees page does not exist

Issue Type:

Improvement

Assignee:

Joe Hansche

Components:

confluence-publisher

Created:

08/Feb/13 3:19 PM

Description:

I've run into a situation a couple of times in my environment where if our confluence site goes down (for whatever reason) the publish action for numerous jobs causes the run to fail. This causes QA and dev to question whether they should proceed with upgrades etc, and overall a lot of churn.

Using the flexible publisher I could devise a method to conditionally run the confluence post build action only if certain criterion were met that guaranteed the confluence site was available. However since the plugin already has the ability to look ahead to see if it can connect to a page it would be an ideal way to provide this switch to the user who does not want or know how to work around cases like mine.

Something like:

[X] Do not publish if the page does not exist

Environment:

Ubuntu 12.04 Server, Jenkins LTS 1.480.2

Project:

Jenkins

Priority:

Trivial

Reporter:

sid nancy

[JIRA] (JENKINS-7683) "Restrict where this project can be run"-Option not available for Matrix builds

2013-02-08 Thread d...@gweep.net (JIRA)















































Don Ross
 commented on  JENKINS-7683


"Restrict where this project can be run"-Option not available for Matrix builds















Okay, that does work.  A little clumsy, but an acceptable workaround.



























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







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

[JIRA] (JENKINS-16709) Copy this job















































Markus KARG
 created  JENKINS-16709


Copy *this* job















Issue Type:


Improvement



Assignee:


Unassigned


Components:


core



Created:


08/Feb/13 3:03 PM



Description:


Jenkins is already able to create new jobs from existing jobs.
But it would be really smart if there would be a "Copy this job" button inside of a job page.

Maybe it is only me, but I think it is more intuitive to navigate to a job and then say "copy this", instead of saying "copy something" and then have to guess which job.




Project:


Jenkins



Labels:


job




Priority:


Major



Reporter:


Markus KARG

























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







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

[JIRA] (JENKINS-16708) Jenkins does not update screen when shutting down















































Markus KARG
 created  JENKINS-16708


Jenkins does not update screen when shutting down















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


08/Feb/13 3:00 PM



Description:


When shutting down Jenkins (e. g. when doing "prepare for shutdown" or "restart after plugin installation), the browser does not update. The screen forever says "Jenkins is shutting down", and even after minutes (while Jenkins is already restarted) it does not update.

This is not smart, as one does not know when Jenkins really is finished shut down. It would be better to at least say "Jenkins is shut down. Please press refresh after it is restarted.".




Project:


Jenkins



Labels:


shutdown




Priority:


Minor



Reporter:


Markus KARG

























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







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

[JIRA] (JENKINS-16707) Ship Jenkins with Config File Provider included by default

Markus KARG
created JENKINS-16707

Ship Jenkins with Config File Provider included by default

Issue Type:

New Feature

Assignee:

Unassigned

Components:

maven

Created:

08/Feb/13 2:57 PM

Description:

To be able to use a Maven Cache Proxy (Mirror) or a local Maven Release Repository (Company Repo), Maven needs to be configured for that using settings.xml. When using lots of slaves, this becomes an administrative nightmare. Also it is unclear why the Maven plugin distributes complete Maven installations to the slaves, but is unable to distribute the information where the Mirror is located or what the Repository URL and password is.

The Config File Provider plugin solves this problem, hence it is more or less an essential part in virtually all production environments. Or in other words, I didn't see any use in having the Maven plugin bundled with Jenkins, while the Config File Provider is not!

So I want to propose to add the Config File Provider to the core Jenkins bundle. It simply looks like a bug that Jenkins comes with Maven but not with any facility to provide settings.xml to slaves.

A different approach could be to enhance the Maven plugin in a way that allows people to simply declare the URL and password of Nexus directly in the Maven installation panel, so the Maven plugin could patch this information into the default settings.xml it is installing on the slaves. This would be even the smartest solution!

Project:

Jenkins

Labels:

settings.xml

Priority:

Major

Reporter:

Markus KARG

[JIRA] (JENKINS-16706) Configure provided settings.xml at the Maven plugin level, not at the Maven job level

Markus KARG
created JENKINS-16706

Configure provided settings.xml at the Maven plugin level, not at the Maven job level

Issue Type:

New Feature

Affects Versions:

current

Assignee:

domi

Components:

config-file-provider

Created:

08/Feb/13 2:48 PM

Description:

To use global and user settings.xml provided by the Config File Provider plugin, one must declare both files to be used with every single job. This is a lot of work, hence error prone.

It would be smarter if one could simply go to "Manage Jenkins > Configure Jenkins > Maven" and declare the provided settings.xml files to be used there.

Benefit: The jobs do not need to know about any particular settings.xml file. All jobs run with this Maven version will then use that settings.xml files automatically. One could not accidentially forget to configure these files at new jobs.

Project:

Jenkins

Priority:

Major

Reporter:

Markus KARG

[JIRA] (JENKINS-16689) Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized















































Markus KARG
 commented on  JENKINS-16689


Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized















The funny thing is that at some later time when I check again the config, the warning is gone.
Tried it several times, always with the same behaviour: The warning will stay there for rather long time, then suddenly is gone.
Browser is IE9.



























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







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

[JIRA] (JENKINS-16705) Native support for settings-security.xml (i. e. encrypted passwords)

Markus KARG
created JENKINS-16705

Native support for settings-security.xml (i. e. encrypted passwords)

Issue Type:

New Feature

Affects Versions:

current

Assignee:

domi

Components:

config-file-provider

Created:

08/Feb/13 2:43 PM

Description:

To be able to upload into a company's Maven Repository (like Nexus), Jenkins typically needs to know the passwort of the repo. The typical solution is to let the Config File Provider Plugin provide an account-specific settings.xml which contains this password. This works well already.

Unfortunately, the password is in plain text in this file so every user having read access to Jenkins now can see the upload password, which is typically not wanted in production environments. Maven could encrypt the password, but to decrypt it, Jenkins would need to know the master password, which typically is stored in a separate settings-security.xml file.

The Config File Provider plugin does not know directly how to handle settings-security.xml, so one has to put up a rather complex fixture with given paths and so on. This should work, but is neither smart now comfortable.

Hence my proposal is that the Config File Provider plugin should learn to natively deal with settings-security.xml files, just as it already natively knows how to deal with settings.xml files. One could then simply tell the plugin to provide a settings-security.xml file, then tell the Maven job to use the provided settings-security.xml file (just as one tells the Maven job to use the provided settings-security.xml file already).

This makes using settings-security.xml rather simple, smart, stable and secure, especially in environments with lots of clients and nosy users!

Project:

Jenkins

Labels:

settings-security.xml

Priority:

Major

Reporter:

Markus KARG

[JIRA] (JENKINS-16704) Wrong file delimiters - our case 8584

2013-02-08 Thread jbrej...@praqma.net (JIRA)















































Jens  Brejner
 updated  JENKINS-16704


Wrong file delimiters -  our case 8584
















Change By:


Jens  Brejner
(08/Feb/13 2:21 PM)




Summary:


Wrong file delimiters
 -  our case 8584



























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







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

[JIRA] (JENKINS-16669) GitHub SQS Plugin works only once after project config

2013-02-08 Thread b...@issuu.com (JIRA)















































Brian Stengaard
 commented on  JENKINS-16669


GitHub SQS Plugin works only once after project config















Linked to #JENKINS-16617 ? 



























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







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

[JIRA] (JENKINS-16704) Wrong file delimiters

2013-02-08 Thread c...@praqma.net (JIRA)















































Christian Wolfgang
 created  JENKINS-16704


Wrong file delimiters















Issue Type:


Bug



Assignee:


Praqma Support



Components:


clearcase-ucm



Created:


08/Feb/13 2:00 PM



Description:


Platform unspecific delimiters used.




Project:


Jenkins



Priority:


Critical



Reporter:


Christian Wolfgang

























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







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

[JIRA] (JENKINS-16702) USERNAME IS TAKING INVALID CHARACTERS
















































Ulli Hafner
 resolved  JENKINS-16702 as Incomplete


USERNAME IS TAKING INVALID CHARACTERS
















Can you please be more precise? I don't think that someone knows what is going wrong with such a short issue description.





Change By:


Ulli Hafner
(08/Feb/13 1:57 PM)




Status:


Open
Resolved





Assignee:


Ulli Hafner





Resolution:


Incomplete



























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







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

[JIRA] (JENKINS-16702) USERNAME IS TAKING INVALID CHARACTERS















































Ulli Hafner
 updated  JENKINS-16702


USERNAME IS TAKING INVALID CHARACTERS
















Change By:


Ulli Hafner
(08/Feb/13 1:56 PM)




Component/s:


core





Component/s:


analysis-core



























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







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

[JIRA] (JENKINS-16703) Too many periodic requests to Crowd server

2013-02-08 Thread g.schla...@mjl.at (JIRA)















































Gerhard Schlager
 created  JENKINS-16703


Too many periodic requests to Crowd server















Issue Type:


Bug



Affects Versions:


current



Assignee:


Thorsten Heit



Components:


crowd2



Created:


08/Feb/13 1:28 PM



Description:


The logfile of Crowd contain lots of periodic requests coming from Jenkins. They occur every 5 seconds and are always the same. The following snippet from the log file shows the requests while one user (foo) is logged into Jenkins.


127.0.0.1 - - [08/Feb/2013:14:09:41 +0100] "POST /rest/usermanagement/1/session/fZ2pVLxOteqInIc0VYr0tQ00 HTTP/1.1" 200 346
127.0.0.1 - - [08/Feb/2013:14:09:41 +0100] "POST /rest/usermanagement/1/session/fZ2pVLxOteqInIc0VYr0tQ00 HTTP/1.1" 200 346
127.0.0.1 - - [08/Feb/2013:14:09:41 +0100] "GET /rest/usermanagement/1/session/fZ2pVLxOteqInIc0VYr0tQ00?expand=user HTTP/1.1" 200 752
127.0.0.1 - - [08/Feb/2013:14:09:41 +0100] "GET /rest/usermanagement/1/session/fZ2pVLxOteqInIc0VYr0tQ00?expand=user HTTP/1.1" 200 752
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/group?groupname=jenkins-users HTTP/1.1" 200 381
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/group?groupname=jenkins-users HTTP/1.1" 200 381
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/group/user/direct?groupname=jenkins-users&username=foo HTTP/1.1" 404 129
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/group/user/direct?groupname=jenkins-users&username=foo HTTP/1.1" 404 129
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/group/user/nested?groupname=jenkins-users&username=foo HTTP/1.1" 200 173
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/group/user/nested?groupname=jenkins-users&username=foo HTTP/1.1" 200 173
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/user/group/direct?username=foo&start-index=0&max-results=500&expand=group HTTP/1.1" 200 987
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/user/group/direct?username=foo&start-index=0&max-results=500&expand=group HTTP/1.1" 200 987
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/user/group/direct?username=foo&start-index=500&max-results=500&expand=group HTTP/1.1" 200 79
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/user/group/direct?username=foo&start-index=500&max-results=500&expand=group HTTP/1.1" 200 79
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/user/group/nested?username=foo&start-index=0&max-results=500&expand=group HTTP/1.1" 200 4374
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/user/group/nested?username=foo&start-index=0&max-results=500&expand=group HTTP/1.1" 200 4374
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/user/group/nested?username=foo&start-index=500&max-results=500&expand=group HTTP/1.1" 200 79
127.0.0.1 - - [08/Feb/2013:14:09:42 +0100] "GET /rest/usermanagement/1/user/group/nested?username=foo&start-index=500&max-results=500&expand=group HTTP/1.1" 200 79

127.0.0.1 - - [08/Feb/2013:14:09:47 +0100] "POST /rest/usermanagement/1/session/fZ2pVLxOteqInIc0VYr0tQ00 HTTP/1.1" 200 346
127.0.0.1 - - [08/Feb/2013:14:09:47 +0100] "POST /rest/usermanagement/1/session/fZ2pVLxOteqInIc0VYr0tQ00 HTTP/1.1" 200 346
127.0.0.1 - - [08/Feb/2013:14:09:47 +0100] "GET /rest/usermanagement/1/session/fZ2pVLxOteqInIc0VYr0tQ00?expand=user HTTP/1.1" 200 752
127.0.0.1 - - [08/Feb/2013:14:09:47 +0100] "GET /rest/usermanagement/1/session/fZ2pVLxOteqInIc0VYr0tQ00?expand=user HTTP/1.1" 200 752
127.0.0.1 - - [08/Feb/2013:14:09:47 +0100] "GET /rest/usermanagement/1/group?groupname=jenkins-users HTTP/1.1" 200 381
127.0.0.1 - - [08/Feb/2013:14:09:47 +0100] "GET /rest/usermanagement/1/group?groupname=jenkins-users HTTP/1.1" 200 381
127.0.0.1 - - [08/Feb/2013:14:09:47 +0100] "GET /rest/usermanagement/1/group/user/direct?groupname=jenkins-users&username=foo HTTP/1.1" 404 129
127.0.0.1 - - [08/Feb/2013:14:09:47 +0100] "GET /rest/userm

[JIRA] (JENKINS-16607) the login is not aligne properly

2013-02-08 Thread ch...@orr.me.uk (JIRA)
















































Christopher Orr
 closed  JENKINS-16607 as Not A Defect


the login is not aligne properly
















Change By:


Christopher Orr
(08/Feb/13 1:22 PM)




Status:


Open
Closed





Resolution:


Not A Defect



























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







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

[JIRA] (JENKINS-16694) Config-file-provider does not submit modified file (submit button simply does nothing at all)















































Markus KARG
 commented on  JENKINS-16694


Config-file-provider does not submit modified file (submit button simply does nothing at all)















Thanks for picking this up.
Happens using Internet Explorer 9 on Windows 7 but works well with Safari!
No _javascript_ errors shown by the browser.
All the rest of Jenkins (all other plugins) run fine.
Just this button in this single plugin is the problem.



























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







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

[JIRA] (JENKINS-16622) NPE while creating new job as copy of existing maven job

2013-02-08 Thread xavier.leprev...@atmel.com (JIRA)













































  
Xavier Leprévost
 edited a comment on  JENKINS-16622


NPE while creating new job as copy of existing maven job
















I have the same issue. The job is created but it is empty.



























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







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

[JIRA] (JENKINS-16607) the login is not aligne properly

2013-02-08 Thread reddysneh...@gmail.com (JIRA)















































sneha reddy
 commented on  JENKINS-16607


the login is not aligne properly















THIS IS NOT REAL ISSUE,YOU CAN RECHECK IT 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/groups/opt_out.

[JIRA] (JENKINS-16622) NPE while creating new job as copy of existing maven job

2013-02-08 Thread xavier.leprev...@atmel.com (JIRA)















































Xavier Leprévost
 commented on  JENKINS-16622


NPE while creating new job as copy of existing maven job















I have the same issue.



























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







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

[JIRA] (JENKINS-16702) USERNAME IS TAKING INVALID CHARACTERS

2013-02-08 Thread reddysneh...@gmail.com (JIRA)















































sneha reddy
 created  JENKINS-16702


USERNAME IS TAKING INVALID CHARACTERS















Issue Type:


Bug



Assignee:


Ulli Hafner



Components:


analysis-core



Created:


08/Feb/13 1:16 PM



Project:


Jenkins



Priority:


Blocker



Reporter:


sneha reddy

























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







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

[JIRA] (JENKINS-11985) javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37

2013-02-08 Thread ku...@gmx.de (JIRA)















































kutzi
 commented on  JENKINS-11985


javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37















See http://issues.tmatesoft.com/issue/SVNKIT-176 for the underlying issue in the SVNKit project



























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







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

[JIRA] (JENKINS-11985) javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37

2013-02-08 Thread jes...@lundogbendsen.dk (JIRA)















































Jesper Tejlgaard
 commented on  JENKINS-11985


javax.net.ssl.SSLException: Received fatal alert: bad_record_mac with subversion-plugin 1.37















I made it work with JDK 7 on Tomcat. Only trouble were the Tomcat Windows Service configuration: http://jespertejlgaard.blogspot.dk/2013/01/solved-badrecordmac-error-for.html



























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







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

[JIRA] (JENKINS-16701) As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request

2013-02-08 Thread manuel.delape...@liferay.com (JIRA)















































Manuel de la Peña
 created  JENKINS-16701


As plugin administrator, I'd like to configure the message when a non-whitelisted user sends a pull request















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Honza Brázdil



Components:


ghprb



Created:


08/Feb/13 12:25 PM



Description:


The default message "Can one of the admins verify this patch?" is confusing and should be configured by plugin configuration.

It should be great to add the ability to enable/disable the message, and then to change it in the same way as other messages ("ok to test", "add to whitelist", etc)




Project:


Jenkins



Priority:


Major



Reporter:


Manuel de la Peña

























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







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

[JIRA] (JENKINS-16700) [cppccheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException

2013-02-08 Thread e...@altoqi.com.br (JIRA)

Eric Brito
created JENKINS-16700

[cppccheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException

Issue Type:

Bug

Assignee:

Gregory Boissinot

Components:

cppcheck

Created:

08/Feb/13 12:23 PM

Description:

If I use --enable=style or --enable=all I get this error:

[Cppcheck] Starting the cppcheck analysis.
[Cppcheck] Processing 1 files with the pattern 'cppcheck-result2.xml'.
[Cppcheck] Parsing throws exceptions. javax.xml.bind.UnmarshalException

with linked exception:
[com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Invalid byte 2 of 3-byte UTF-8 sequence.]
Build step 'Publish Cppcheck results' changed build result to FAILURE
Build step 'Publish Cppcheck results' marked build as failure

how I run cppcheck:

cppcheck --enable=style --xml-version=2 %workspace%\Main\ 2> cppcheck-result2.xml

this works fine: cppcheck --xml-version=2 %workspace%\Main\ 2> cppcheck-result2.xml

Environment:

Windows XP, Jenkins 1.498, cppcheck plug-in 1.13, Cppcheck 1.57

Project:

Jenkins

Priority:

Major

Reporter:

Eric Brito

[JIRA] (JENKINS-16688) Duplications in different files shown only in one file

2013-02-08 Thread hans-juergen.haf...@nsn.com (JIRA)















































Hans-Juergen Hafner
 commented on  JENKINS-16688


Duplications in different files shown only in one file















I´ve checked it again, screen shots are form same build. I attached cpd.xml and main page of DRY results dry1.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/groups/opt_out.

[JIRA] (JENKINS-16688) Duplications in different files shown only in one file

2013-02-08 Thread hans-juergen.haf...@nsn.com (JIRA)















































Hans-Juergen Hafner
 updated  JENKINS-16688


Duplications in different files shown only in one file
















Change By:


Hans-Juergen Hafner
(08/Feb/13 12:01 PM)




Attachment:


cpd.xml





Attachment:


dry1.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/groups/opt_out.

[JIRA] (JENKINS-16688) Duplications in different files shown only in one file

Ulli Hafner
commented on JENKINS-16688

Duplications in different files shown only in one file

Are these two screenshots from the same build? These warnings seem not to be correlated?

I think the following behavior makes sense:

the plug-in should count the number of warnings (regardless of the category) as the total number of duplicated blocks.
I.e. if we have one block in A3 and A12 and B3 duplicated, then the number of warnings is 1 for total, and 1 for file A and 1 for file B
This result should be shown in the Summary view
in the warnings details there should be one row for each duplication
I.e the "primary file and line" (as reported from CPD) is shown on the left, the duplications are shown on the right
If a duplication is in two files, then on the left only one file is shown

Does that make sense? If not can you please explain in more detail what you would like to expect? Maybe you can attach a cpd XML file that I can use a staring point for a unit test.

[JIRA] (JENKINS-16688) Duplications in different files shown only in one file