date:20150319













































  
pixman20
 edited a comment on  JENKINS-19409


Support case-insensitive mode for user IDs
















Oleg Nenashev, I'd be happy to contribute and test it out.  Feel free to email me (address in profile) unless there's somewhere I can grab it from.  Thanks!



























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







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

[JIRA] [role-strategy-plugin] (JENKINS-19409) Support case-insensitive mode for user IDs















































pixman20
 commented on  JENKINS-19409


Support case-insensitive mode for user IDs















@oleg_nenashev, I'd be happy to contribute and test it out.  Feel free to email me (address in profile) unless there's somewhere I can grab it from.  Thanks!



























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







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

[JIRA] [core] (JENKINS-6167) JNLP slave should support a connection via HTTP proxy















































SCM/JIRA link daemon
 commented on  JENKINS-6167


JNLP slave should support a connection via HTTP proxy















Code changed in jenkins
User: Hiroshi Shirosaki
Path:
 src/main/java/hudson/remoting/Engine.java
 src/main/java/hudson/remoting/Launcher.java
 src/main/java/hudson/remoting/Util.java
http://jenkins-ci.org/commit/remoting/8c875cbc81d22df898a57ef86e833b41c50470cb
Log:
  JENKINS-6167 Support JNLP slave connection via HTTP proxy

We get proxy setting from http.proxyHost property or http_proxy
environment variable.





























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







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

[JIRA] [core] (JENKINS-27218) Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy

2015-03-19 Thread peter_kl...@affirmednetworks.com (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-27218


Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy















Code changed in jenkins
User: Nicolas De Loof
Path:
 src/main/java/hudson/remoting/Engine.java
http://jenkins-ci.org/commit/remoting/5e3042bebc23d57eff50aea0ce454bfe5dee4145
Log:
  JENKINS-27218 support X-Jenkins-JNLP-Host





























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







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

[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin















































Peter Kline
 commented on  JENKINS-27491


kicking off of build via curl command not working in 1.16.1 version of plugin















I have attached a screenshot of our config.  We aren't using multiple repos. 

The plugin info i have is:
Git client plugin: 1.16.1
Git Parameter plugin: 0.4.0
Git plugin: 2.3.5
Git Server Plugin: 1.6



























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







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

[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin

2015-03-19 Thread peter_kl...@affirmednetworks.com (JIRA)















































Peter Kline
 updated  JENKINS-27491


kicking off of build via curl command not working in 1.16.1 version of plugin
















Here is the screenshot of our config





Change By:


Peter Kline
(20/Mar/15 1:31 AM)




Attachment:


git.jpg



























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







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

[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin















































Mark Waite
 commented on  JENKINS-27491


kicking off of build via curl command not working in 1.16.1 version of plugin















Does your job use multiple git repositories? When I have more than one git repository defined in my job, then the polling seems to run, but does not detect changes.  I think that matches the buggy behavior you describe, but it isn't clear from your output if you're using a single repository or multiple repositories.

Any other hints what might be different?

What version of the git plugin are you running?  You mentioned git client plugin 1.16.1, but didn't mention the version of the git plugin.

You might review the online help for the various forms in which the branch name can be specified.  There are many more options in the recent versions of the git plugin than were available in the earlier versions.



























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







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

[JIRA] [git-client-plugin] (JENKINS-27483) Repository URL containg double points couldn't be resolved correctly.













































  
Mark Waite
 edited a comment on  JENKINS-27483


Repository URL containg double points couldn't be resolved correctly.
















The git plugin does not support a colon embedded in an ssh:// protocol URL other than immediately following the protocol string (ssh). I think it is a bug in the plugin, but the investigation in the JENKINS-26680 bug report shows that there seem to be differences in handling of that style of URL between git versions.



























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







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

[JIRA] [git-client-plugin] (JENKINS-27483) Repository URL containg double points couldn't be resolved correctly.













































  
Mark Waite
 edited a comment on  JENKINS-27483


Repository URL containg double points couldn't be resolved correctly.
















The git plugin does not support a colon embedded in an ssh:// protocol URL other than immediately following the protocol string (ssh). I think it is a bug in the plugin, but the investigation in the JENKINS-26680 bug report shows that there seem to be differences in handling of that style of URL between git versions.

If allowed, an alternate work around is to not include the second ":" character in the URL, but use an absolute path instead.



























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







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

[JIRA] [multiple-scms-plugin] (JENKINS-27470) StackOverflowError with version 0.4

2015-03-19 Thread chiki...@java.net (JIRA)















































chikigai
 commented on  JENKINS-27470


StackOverflowError with version 0.4















I am experiencing a similar issue using Multiple SCMs plugin 0.4 and Jenkins 1.596.1.
The job loads, but if I click on any of the completed builds, I get the following error:


javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/jenkins/war/WEB-INF/lib/jenkins-core-1.596.1.jar!/lib/hudson/actions.jelly:39:70:  Error setting property 'from', exception - java.lang.StackOverflowError
	at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117)
	at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:735)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
	at org.eclipse.

[JIRA] [gradle-jpi-plugin] (JENKINS-27451) All .properties files are being compiled by localizer, rather than just Messages.properties















































SCM/JIRA link daemon
 commented on  JENKINS-27451


All .properties files are being compiled by localizer, rather than just Messages.properties















Code changed in jenkins
User: Daniel Spilker
Path:
 CHANGELOG.md
 src/main/groovy/org/jenkinsci/gradle/plugins/jpi/LocalizerTask.groovy
http://jenkins-ci.org/commit/gradle-jpi-plugin/9f5e4dd856c979f389b5df3e53fcc0200eeb8a5e
Log:
  Merge pull request #48 from daspilker/JENKINS-27451

JENKINS-27451 localize only Message.properties files


Compare: https://github.com/jenkinsci/gradle-jpi-plugin/compare/8b20ff9baf18...9f5e4dd856c9




























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







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

[JIRA] [gradle-jpi-plugin] (JENKINS-27451) All .properties files are being compiled by localizer, rather than just Messages.properties















































SCM/JIRA link daemon
 commented on  JENKINS-27451


All .properties files are being compiled by localizer, rather than just Messages.properties















Code changed in jenkins
User: Daniel Spilker
Path:
 CHANGELOG.md
 src/main/groovy/org/jenkinsci/gradle/plugins/jpi/LocalizerTask.groovy
http://jenkins-ci.org/commit/gradle-jpi-plugin/d06155b93251efc4bae3a20061d39021f7df5d3f
Log:
  JENKINS-27451 localize only Message.properties files





























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







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

[JIRA] [core] (JENKINS-27511) CLONE - Executors are dying after upgrading to 1605















































Daniel Beck
 commented on  JENKINS-27511


CLONE - Executors are dying after upgrading to 1605















What would be interesting is why Jenkins wants to assign an already assigned build number.

I think there's a known issue with Gerrit Trigger that can cause this. Do you have Gerrit Trigger installed?

Unfortunately you provide no information at all about your instance. Please read https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue and consider installing the Support Core plugin and attaching a support bundle to this issue.



























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







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

[JIRA] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs

2015-03-19 Thread ch...@orr.me.uk (JIRA)

Christopher Orr
commented on JENKINS-27507

Support multiple .apk files with different application IDs

This is something I'm not really willing to have in the plugin, as I believe uploading separate applications should be done in separate jobs.

If you attempt to upload, say three, completely different APKs in one Jenkins build, this requires opening and committing three separate "edit sessions" with the Google Play API. If any one of these fails — maybe because of an invalid APK, or due to an API failure (which, unfortunately, is not uncommon with the Google Play API) — you will end up with your Google Play account in an inconsistent state. Your build will be marked as failed, but one or more applications have actually been uploaded and published to Google Play, and you'll have to fix the situation manually. Also, you won't be able to just re-rerun the build again, as it will fail due to already-existing APKs.

The Jenkins best practice in this case would be to have one job that builds the different flavours (i.e. the APKs with different application IDs) and then, if the build is successful, it would archive the APKs and start multiple "downstream" Jenkins builds which individually publish each of the applications.
You can do this relatively easily, for example, with the Parameterized Trigger Plugin and the Copy Artifacts Plugin, i.e. the "upload" job could be generic, and would receive the APK information via parameter.

I will look at documenting this on the wiki.

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

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

[JIRA] [core] (JENKINS-25938) Lock an Executor without creating a Thread
















































Jesse Glick
 assigned  JENKINS-25938 to Jesse Glick



Lock an Executor without creating a Thread
















Change By:


Jesse Glick
(19/Mar/15 10:03 PM)




Assignee:


Jesse Glick



























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







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

[JIRA] [core] (JENKINS-25938) Lock an Executor without creating a Thread















































Jesse Glick
 started work on  JENKINS-25938


Lock an Executor without creating a Thread
















Change By:


Jesse Glick
(19/Mar/15 10:03 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/d/optout.

[JIRA] [core] (JENKINS-26092) executors.jelly interface underspecified















































Jesse Glick
 commented on  JENKINS-26092


executors.jelly interface underspecified















Or now just PlaceholderExecutable/executorCell.jelly after https://github.com/jenkinsci/workflow-plugin/pull/96.



























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







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

[JIRA] [gradle-jpi-plugin] (JENKINS-27451) All .properties files are being compiled by localizer, rather than just Messages.properties

2015-03-19 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 commented on  JENKINS-27451


All .properties files are being compiled by localizer, rather than just Messages.properties















Sorry, I don't have a public repo at the moment.  But I built and tested the pull request, and it worked as expected. Thanks!



























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







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

[JIRA] [core] (JENKINS-27436) 'Check Now' function seems to have no effect

2015-03-19 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-27436


'Check Now' function seems to have no effect















Integrated in  jenkins_main_trunk #4018
 [FIXED JENKINS-27436]  elements can’t be nested (Revision d892fd66f0d129ed83f2943f0bb6fd1f9bab3c3d)

 Result = SUCCESS
nicolas de loof : d892fd66f0d129ed83f2943f0bb6fd1f9bab3c3d
Files : 

	core/src/main/resources/hudson/PluginManager/check.jelly





























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







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

[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM















































Daniel Beck
 commented on  JENKINS-27514


Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM















What is the difference between real slaves and cloud slaves?

Cloud slaves are designed to be added and removed all the time, and managed by Jenkins. See some of the plugins on https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Slavelaunchersandcontrollers



























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







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

[JIRA] [core] (JENKINS-26090) Executables.getExecutor















































Jesse Glick
 started work on  JENKINS-26090


Executables.getExecutor
















Change By:


Jesse Glick
(19/Mar/15 9:06 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/d/optout.

[JIRA] [core] (JENKINS-26090) Executables.getExecutor
















































Jesse Glick
 assigned  JENKINS-26090 to Jesse Glick



Executables.getExecutor
















Change By:


Jesse Glick
(19/Mar/15 9:06 PM)




Assignee:


Jesse Glick



























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found

2015-03-19 Thread poohbla...@yahoo.com (JIRA)

jay hendren
commented on JENKINS-27488

gss.conf file not found

> Jay, I don't know why you think that smack 4 only supports gssapi. I can see e.g. here several other supported auths: http://www.igniterealtime.org/builds/smack/docs/4.0.6/javadoc/org/jivesoftware/smack/sasl/SASLMechanism.html

i apologize - i meant that smack 4 only supports sasl auth. non-sasl (a.k.a. simple) auth works, but is not available in smack 4.

where do you see the other supported auths? and how would i switch between them? (neither of us are java devs so it's a little bit challenging for us to grok java api docs)

> Also, I don't understand why you keep pressing this issue so much. I thought you had figured out a way to authenticate even with the latest version?

almost, but not quite. we found a manual way to authenticate, and the jenkins user would only be auth'd as long as the kerb ticket is valid. effectively, this means we need to manually authenticate the jenkins user once a day, which isn't acceptable. so really, we found a crummy workaround, but this doesn't resolve this bug report, and we're not entirely sure why or how our workaround solves the issue, or if it's really just a band-aid over a different problem.

personally, i don't believe the behavior described in this bug report ("gss.conf not found" exception) matches the expected behavior for this plugin (if i've supplied my jabber id and password to the jabber plugin, it should have all the information it needs - why is it complaining about something called "gss.conf"?).

> And again: the smack forum would be a better place to ask about xmpp/smack authentication details!

okay, i accept that this may be an upstream issue, but it seems to me that this kind of error shouldn't bubble up to the downstream consumer... i shouldn't need to know anything about gssapi in order to auth to an xmpp server through a jenkins plugin. i feel like that's really the crux of the issue.

kutzi, thanks for your time and help with this issue. i hope my little diatribe here clarifies why we keep bugging you

[JIRA] [job-dsl-plugin] (JENKINS-27504) support for commentFilePath for Pull Request Builder

2015-03-19 Thread m...@daniel-spilker.com (JIRA)
















































Daniel Spilker
 resolved  JENKINS-27504 as Fixed


support for commentFilePath for Pull Request Builder
















Will be released in 1.31.





Change By:


Daniel Spilker
(19/Mar/15 8:46 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-27504) support for commentFilePath for Pull Request Builder















































SCM/JIRA link daemon
 commented on  JENKINS-27504


support for commentFilePath for Pull Request Builder















Code changed in jenkins
User: Daniel Spilker
Path:
 docs/Home.md
 docs/Job-reference.md
 job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/triggers/PullRequestBuilderContext.groovy
 job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/triggers/TriggerContext.groovy
 job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/triggers/TriggerContextSpec.groovy
http://jenkins-ci.org/commit/job-dsl-plugin/091dc0cced9338393509db414326ad9f4b270e2f
Log:
  Merge branch 'JENKINS-27504'


Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/061b2ccdc2c1...091dc0cced93




























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







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

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















































Bue Petersen
 updated  JENKINS-27516


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
















Change By:


Bue Petersen
(19/Mar/15 8:43 PM)




Summary:


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



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-27517) Allow access to the Jenkins instance and/or plugins

2015-03-19 Thread pe...@algarvio.me (JIRA)















































Pedro Algarvio
 created  JENKINS-27517


Allow access to the Jenkins instance and/or plugins















Issue Type:


Improvement



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


19/Mar/15 8:42 PM



Description:


I'd like to be able to access the Jenkins instance(probably a configurable setting) and it's plugins classes. Importing them fails...

This will allow, for example, to use the github-api as an authenticated user(as long as it's configurable in Jenkins of course) as opposed to accessing it anonymously(and this will require additional libs in the classpath).

The groovy post build plugin add the jenkins instance classpath as seen here.




Project:


Jenkins



Priority:


Minor



Reporter:


Pedro Algarvio

























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







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

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















































Bue Petersen
 created  JENKINS-27516


Plugin hangs - reproduced with failed earlier build















Issue Type:


Bug



Assignee:


Praqma Support



Components:


pretested-integration-plugin



Created:


19/Mar/15 8:39 PM



Description:


Example of console log:


Started by user Jenkins Admin
[EnvInject] - Loading node environment variables.
Building remotely on jenkins-training-linux-slave (linux) in workspace /home/praqma/.jenkins/workspace/bpe.roadshow.verify
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/buep/roadshow.git # timeout=10
Fetching upstream changes from https://github.com/buep/roadshow.git
 > git --version # timeout=10
using .gitcredentials to set credentials
 > git config --local credential.helper store --file=/tmp/git6460479601874649810.credentials # timeout=10
 > git -c core.askpass=true fetch --tags --progress https://github.com/buep/roadshow.git +refs/heads/*:refs/remotes/origin/*
 > git config --local --remove-section credential # timeout=10
Seen branch in repository origin/master
Seen branch in repository origin/ready/buep
Seen 2 remote branches
Checking out Revision 8b7d9910d213bf7e235beb528bfd416d0941a168 (origin/ready/buep)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 8b7d9910d213bf7e235beb528bfd416d0941a168
 > git rev-list 8b7d9910d213bf7e235beb528bfd416d0941a168 # timeout=10
2.2.1 (63b83)


jobs just hangs here...

How to reproduce

The situation is reproduceable every time (tried three times) after the problem reported in JENKINS-27515.

After a successful job, that by an error is successful, I fixed the credentials to enable the job to push.
When building manually after the configuration change the same branch is picked up again (correct, as it isn't deleted remotely), but the plugin hangs just after printing version number.

A similar problem was reported in JENKINS-27328 but not reproduced.

After the problem described above, the slave is killed (slave process) and master restarted. The situation can then be recreated after reboot.




Environment:


pretested integration plugin 2.2.1

Linux Ubuntu 14.04 slave, master Linux Ubuntu 14.04.

jenkins core 1.605




Project:


Jenkins



Priority:


Critical



Reporter:


Bue Petersen

























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







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

[JIRA] [core] (JENKINS-27436) 'Check Now' function seems to have no effect















































SCM/JIRA link daemon
 commented on  JENKINS-27436


'Check Now' function seems to have no effect















Code changed in jenkins
User: Nicolas De Loof
Path:
 core/src/main/resources/hudson/PluginManager/check.jelly
http://jenkins-ci.org/commit/jenkins/d892fd66f0d129ed83f2943f0bb6fd1f9bab3c3d
Log:
  [FIXED JENKINS-27436]  elements can’t be nested





























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







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

[JIRA] [core] (JENKINS-27436) 'Check Now' function seems to have no effect
















































SCM/JIRA link daemon
 resolved  JENKINS-27436 as Fixed


'Check Now' function seems to have no effect
















Change By:


SCM/JIRA link daemon
(19/Mar/15 8:28 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-27436) 'Check Now' function seems to have no effect















































SCM/JIRA link daemon
 commented on  JENKINS-27436


'Check Now' function seems to have no effect















Code changed in jenkins
User: Nicolas De loof
Path:
 core/src/main/resources/hudson/PluginManager/check.jelly
http://jenkins-ci.org/commit/jenkins/6f4b467d8857c73dd1da8303cc863c8f6401c4a6
Log:
  Merge pull request #1608 from ndeloof/JENKINS-27436

[FIXED JENKINS-27436]  elements can’t be nested


Compare: https://github.com/jenkinsci/jenkins/compare/b62c927a27d5...6f4b467d8857




























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







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

[JIRA] [pretested-integration-plugin] (JENKINS-27515) Stack trace if push fails - build shows successful but is not (Praqma case 12833)















































Bue Petersen
 updated  JENKINS-27515


Stack trace if push fails - build shows successful but is not (Praqma case 12833)
















Change By:


Bue Petersen
(19/Mar/15 8:25 PM)




Summary:


Stack trace if push fails - build shows successful but is not
 (Praqma case 12833)



























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







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

[JIRA] [pretested-integration-plugin] (JENKINS-27515) Stack trace if push fails - build shows successful but is not















































Bue Petersen
 created  JENKINS-27515


Stack trace if push fails - build shows successful but is not















Issue Type:


Bug



Assignee:


Praqma Support



Components:


pretested-integration-plugin



Created:


19/Mar/15 8:21 PM



Description:


When build is successful, but the push fails the plugin tries to change state of the build to failed. At this point it is not allowed by the Jenkins plugin model.


So integration is successful according to build status, but the changes never got pushed.


Performing pre-verified post build steps
[PREINT-GIT] Commiting changes
[PREINT]  git push origin master
[bpe.roadshow.verify] $ git push origin master

Failed to commit integrated changes, message was:
fatal: could not read Username for 'https://github.com': No such device or address

ERROR: Build step failed with exception
java.lang.IllegalStateException: cannot change build result while in POST_PRODUCTION
	at hudson.model.Run.setResult(Run.java:461)
	at org.jenkinsci.plugins.pretestedintegration.PretestedIntegrationPostCheckout.perform(PretestedIntegrationPostCheckout.java:71)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:761)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:721)
	at hudson.model.Build$BuildExecution.cleanUp(Build.java:193)
	at hudson.model.Run.execute(Run.java:1797)
	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
	at hudson.model.ResourceController.execute(ResourceController.java:89)
	at hudson.model.Executor.run(Executor.java:240)
Build step 'Pretested Integration post-build' marked build as failure
Finished: SUCCESS





Environment:


pretested integration plugin 2.2.1

Linux Ubuntu 14.04 slave, master Linux Ubuntu 14.04.




Project:


Jenkins



Priority:


Critical



Reporter:


Bue Petersen

























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found















































kutzi
 commented on  JENKINS-27488


gss.conf file not found















Also, I don't understand why you keep pressing this issue so much. I thought you had figured out a way to authenticate even with the latest version?

And again: the smack forum would be a better place to ask about xmpp/smack authentication details!



























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found















































kutzi
 commented on  JENKINS-27488


gss.conf file not found















Jay, I don't know why you think that smack 4 only supports gssapi. I can see e.g. here several other supported auths: http://www.igniterealtime.org/builds/smack/docs/4.0.6/javadoc/org/jivesoftware/smack/sasl/SASLMechanism.html

Maybe I'll find some time to test this in the next days but cannot promise anything.
The plugin has a reported 2000 installations. I'm pretty confidend at least some of them are at a reasonable new version and don't have the problems you have



























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found

2015-03-19 Thread dylan.canfi...@colorado.edu (JIRA)















































Dylan Canfield
 commented on  JENKINS-27488


gss.conf file not found















Kutzi,
Do you mind installing and testing the latest version of the plugin? I would greatly appreciate to see your results.



























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found

2015-03-19 Thread poohbla...@yahoo.com (JIRA)

jay hendren
edited a comment on JENKINS-27488

gss.conf file not found

kutzi,

the jabber plugin was changed to use the smack 4 library in october of last year. have you used this plugin since then? we are only seeing this issue with plugin version >= 1.26, which is when the dependency on smack 4 was introduced.

>I understand that the situation for GSSAPI authentication is far from being satisfactory.
>The thing is that you probably know now - after debugging the issue on your side - infinitely more about how to configure it than I do.
>So if you could document your findings on the Wiki, this would be great. If you have other suggestions on how to improve default user behaviour reagrding this issue with the plugin, I'm also happy to hear it.
>
>Sorry, I do know basically nothing about GSSAPI. If you're looking for documentation/help, the Smack API site is probably a better location.

the official smack documentation doesn't have any information about configuring gss.conf or any krb5 configuration in general. smack docs only talk about the java api.

since the jabber plugin only supports gssapi auth (since smack 4 only supports gssapi auth), i'm not sure i understand how it's possible to use or develop this plugin without needing to configure or touch gssapi.

jay

[JIRA] [sectioned-view-plugin] (JENKINS-26818) Test result trends not showing in sectioned dashboard view

2015-03-19 Thread ralf.stuck...@gmx.de (JIRA)















































Ralf Stuckert
 commented on  JENKINS-26818


Test result trends not showing in sectioned dashboard view















Very similar here: all other graphs (checkstyle, task, etc) but test trends are visualized. Test trends are shown neither in the job graphs nor in the dedicated test results section. In the test result section only the name is shown. I'm using free style jobs and the test result publisher to show the trend on the job's view.



























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found















































kutzi
 commented on  JENKINS-27488


gss.conf file not found















No, I haven't used in since then. Maybe some short tests against a testserver.



























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







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

[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM

2015-03-19 Thread clark.boy...@gmail.com (JIRA)















































Clark Boylan
 commented on  JENKINS-27514


Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM















What is the difference between real slaves and cloud slaves? These are cloud VMs added and removed to the Jenkins master using the Jenkins api via python-jenkins, http://python-jenkins.readthedocs.org/en/latest/

If opportunity arises I can try to get the support plugin installed. We do have the melody plugin installed though so can get thread dump from that if/when this happens again.



























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found

2015-03-19 Thread poohbla...@yahoo.com (JIRA)















































jay hendren
 commented on  JENKINS-27488


gss.conf file not found















kutzi,

the jabber plugin was changed to use the smack 4 library in october of last year.  have you used this plugin since then?  we are only seeing this issue with plugin version >= 1.26, which is when the dependency on smack 4 was introduced.

jay



























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







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

[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM















































Daniel Beck
 commented on  JENKINS-27514


Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM















We do add and delete slave nodes frequently (thousands per day per master) which I think may be part of the problem.

Real slaves, or cloud slaves?

Hoping that by filing it with as much info as I can

Install the Support Core Plugin and attach a support bundle to this issue.



























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found















































kutzi
 commented on  JENKINS-27488


gss.conf file not found















I'm not using the plugin currently. When I used it last time several month ago, I didn't need to configure a gss.conf file.



























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







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

[JIRA] [core] (JENKINS-27514) Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM

2015-03-19 Thread clark.boy...@gmail.com (JIRA)

Clark Boylan
created JENKINS-27514

Jenkins leaks thousands of Computer.threadPoolForRemoting threads leading to eventual server OOM

Issue Type:

Bug

Assignee:

Kohsuke Kawaguchi

Components:

core, ssh-slaves-plugin

Created:

19/Mar/15 7:14 PM

Description:

After some period of time the Jenkins master will have up to ten thousand or so threads most of which are Computer.theadPoolForRemoting threads that have leaked. This forces us to restart the Jenkins master.

We do add and delete slave nodes frequently (thousands per day per master) which I think may be part of the problem.

I thought https://github.com/jenkinsci/ssh-slaves-plugin/commit/b5f26ae3c685496ba942a7c18fc9659167293e43 may be the fix because stacktraces indicated threads are hanging in the plugins afterDisconnect() method. I have updated half of our Jenkins masters to ssh-slaves plugin version 1.9 which includes that change, but early today we had a master with ssh-slaves plugin fall over from this issue.

Unfortunately I don't have any stacktraces handy (we had to force reboot the master today), but will update this bug if we get another case of this problem. Hoping that by filing it with as much info as I can we can at least start to diagnose the problem.

Environment:

We are running Jenkins 1.565.3 with ssh-plugin 1.5 (the default with 1.565.3) on half the masters and ssh-plugin 1.9 (latest version) on the other half of the masters. Both sets exhibit this thread leakage. All masters run on Ubuntu Precise with java version "1.7.0_65" OpenJDK Runtime Environment (IcedTea 2.5.1) (7u65-2.5.1-4ubuntu1~0.12.04.2) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode).

Project:

Jenkins

Labels:

slave

Priority:

Major

Reporter:

Clark Boylan

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found

2015-03-19 Thread dylan.canfi...@colorado.edu (JIRA)















































Dylan Canfield
 commented on  JENKINS-27488


gss.conf file not found















Do you have anything in your gss.conf file? Does this plugin work for you?



























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







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

[JIRA] [core] (JENKINS-27472) Exception on default view and other list views
















































Daniel Beck
 resolved  JENKINS-27472 as Cannot Reproduce


Exception on default view and other list views
















Very weird, and not exactly a satisfactory outcome.

If this happens again, please reopen (if it's within a few weeks) or file a new issue (if later).





Change By:


Daniel Beck
(19/Mar/15 7:05 PM)




Status:


Open
Resolved





Resolution:


Cannot Reproduce



























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







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

[JIRA] [git-plugin] (JENKINS-26482) Git trigger build on push in any branch















































Mark Waite
 commented on  JENKINS-26482


Git  trigger build on push in any branch















I'm not aware of any way to solve this through configuration.



























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







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

[JIRA] [core] (JENKINS-27472) Exception on default view and other list views

2015-03-19 Thread dne...@yahoo.com (JIRA)

Demitrius Nelon
commented on JENKINS-27472

Exception on default view and other list views

Somehow this managed to work itself out. I tried several different things with no success. Ultimately the two things that were done last are most likely what cleared up the issue. One of them was a job being modified to "get a build working" and it appeared that Jenkins wasn't retaining changes I was making to the job definition until several attempts were done. The job would execute with the modified script, but then it would revert back somehow on it's own to the state before my changes. Then the next thing that was done was to clone a job with a build on github PR. I had gotten pulled away on a conference call and when I came back a little more than an hour later to "dig back in", I noticed that the site was working and others on the team were able to verify. Mental note to self... snapshot the VM before changing anything.

[JIRA] [git-plugin] (JENKINS-26482) Git trigger build on push in any branch

2015-03-19 Thread stefan.thurnh...@gmail.com (JIRA)















































Stefan Thurnherr
 updated  JENKINS-26482


Git  trigger build on push in any branch
















Same problem here, attaching a screenshot of our job configuration. Jenkins 1.602, git-plugin 2.3.4, builds get triggered from GitLab web hook.

The build shown in the screenshot triggers when any change on any branch gets pushed.

Specifying branch name in the notifyCommit url (if it would work) is not an option since we want to have builds for all branches (using the jenkins-build-per-branches "plugin").

Is there a way to solve this through configuration?





Change By:


Stefan Thurnherr
(19/Mar/15 6:47 PM)




Attachment:


jenkins-gitPlugin-buildsForAllBranches.png



























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







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

[JIRA] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13

2015-03-19 Thread francis.obri...@datacert.com (JIRA)















































Francis O'Briant
 commented on  JENKINS-27100


Regressions in 1.12 and 1.13















Has there been any progress on a rebuilt version yet?  There obviously isn't a new version out yet, and as far as my team can tell the existing 1.13 file on the download site has not changed.



























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







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

[JIRA] [nodejs-plugin] (JENKINS-27513) Nodejs plugin breaks node's require() mechanism















































Daniel Beck
 commented on  JENKINS-27513


Nodejs plugin breaks node's require() mechanism















I know nothing about node, but doesn't the WORKSPACE environment variable help with this?



























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







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

[JIRA] [nodejs-plugin] (JENKINS-27513) Nodejs plugin breaks node's require() mechanism

2015-03-19 Thread jochen.hinrich...@kambrium.net (JIRA)

Jochen Hinrichsen
created JENKINS-27513

Nodejs plugin breaks node's require() mechanism

Issue Type:

Bug

Assignee:

Unassigned

Components:

nodejs-plugin

Created:

19/Mar/15 6:07 PM

Description:

Executing code entered direclty into the text fields runs like a charm. This procedure works fine for small adhoc snippets, but has its limitations in an enterprise strength setup. Sooner or later one might want to keep the code under SCM control and only use a 'run' stub to execute.

A workspace local, node module compliant directory 'node_modules' is not taken into account when require()ing modules, because the script is executed in /tmp using a unique ID as filename.

Copying the local node_modules folder to /tmp resolves the issue, but this is a rather clumsy workaround because (a) you have to remember to remove it afterwards, and (b) what if two jobs need different node_module folder.

Is it a viable option to have a '[x] Stay local' option for scripts that require require()?

Environment:

Any

Project:

Jenkins

Priority:

Minor

Reporter:

Jochen Hinrichsen

[JIRA] [core] (JENKINS-27511) CLONE - Executors are dying after upgrading to 1605















































Daniel Beck
 commented on  JENKINS-27511


CLONE - Executors are dying after upgrading to 1605















Not so sure if there was an option to change description while cloning

There is at least afterwards.

Cloning just confuses, better to create an issue from scratch if you're positive it's not 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/d/optout.

Fwd: Cara Menyuburkan Sperma Pria Alami

2015-03-19 Thread didin chy

Cara Menyuburkan Sperma Pria Alami


Berikut ini *Cara Menyuburkan Sperma Pria Alami
*
- Jika Anda
Mengalami Sperma Encer / Air Mani kurang subur dengan cara menyembuhkan
sperma yang tidak subur dengan secara ala mi menggunakasexual
characteristicsbat herbal / Obat Penyubur Sperma terbaik ini maka anda
tidak perlu bingung lagi untuk mencari solusi pengobatan sperma tidak subur
hanya dengan menggunakan obat penyubur sperma herbal, sperma yasexual
characteristicstidak subur akan kembali customary obat ini mujarab yang
paling ampuh, karena dengan cara cepat mengobati sperma tidak subur
menggunakan obat herbal ini maka anda akan sembuh juga dari berbagai macam
penyakit. Mengapa bisa demikian? Karena obat penyubur sperma ini adalah
obat herbal multi khasiat yang berguna juga untuk mengobati berbagai macam
penyakit, oleh karena itu maka jangan tunggu lama lagi, segeralah sembuhkan
penyakit sperma anda yang tidak subur dengan menggunakan obat penyubur
sperma yang mujarab dan ampuh ini.

Menderita sperma encer? Ejakulasi dini? Tidak bisa ereksi? Susah punya
keturunan? Menderita virgit? Sperma Susah keluar? Dan mandul? Segeralah
sembuhkan hanya dengan menggunakan obat herbal terbaik yan g aman dan alami
untuk mengobati berbagai macam penyakit.

Apa saja faktor penyebab sperma tidak subur?
Ada banyak faktor penyebab yang bisa menimbulkan ketidak suburan pada
sperma diantaranya:

Pola Hidup /Gaya hidup yang tidak sehat
Kegemukan / Obesitas
Minim / Kurang olahraga
Stress
Terlalu aktif secara seksual pada usia dini
Merokok, mengkonsumsi alkohol dan narkoba
Berendan di air panas dengan waktu lebih dari 15 menit
Radiasi ponsel dan lapot
Radang testis
Kanker testis
Kecelakaan yang bisa menimbulkan gangguan pada sistem reproduksi

Itulah beberapa faktor penyebabsexual characteristicserma tidak subur maka
dari itu kita harus mengetahui dan mencegah terjadinya sperma tidak subur
sexual characteristics.

Me mpunyai keturunan adalah keinginan semua manusia, namun jika anda
menderita susah punya keturunan, maka segeralah sembuhkan hanya dengan
tricajus obat sperma tidak subur yang muujarab, alami, aman, terpercaya dan
bebas dari efek samping.

Bagaimana cara mengatasi sperma tidak subur? Apakah pencerita sperma tidak
subur masih sexual characteristicsa punya keturunan?
Untuk anda yang menderita sperma tidak subur maka tidak perlu mengeluh,
karensexual characteristicsetiap masalah juga pasti ada solusinya, dan jika
anda sedang mencari solusi pengobatan untuk sperma tidak subur maka
segeralah atasi dengan menggunakan tricaju obat herbal untuk pengobatan
sperma tidak subur.

Tips Pengganti Obat Penyubur Sperma Secara Alami secara Perlakuan :

Anda ingin meningkatkan peluang memiliki anak atau hanya sekadar ingin
ejakulasi dengan tingkat sperma dan air mani yang tinggi? Sperma yang
banyak merupakan satu tanda sistem reproduksi yang sehat.

Tidak diragukan memiliki air mani dan sperma yang lebih banyak menghasilkan
orgasme lebih lama, termasuk meningkatnya hasrat seks. Jika Anda ingin
menyirami pasangan dengan cinta sekaligus menjadi seorang calon ayah,
inilah beberapa tips untuk memperbaiki dan meningkatkan jumlah sperma:

Berhenti merokok
Jika Anda seorang perokok saat ini, berhentilah. Selain menyebabkan napas
tak sedap, merokok juga dapat memengaruhi jumlah sperma. Penelitian
menujukan perokok memiliki jumlah sperma lebih kecil dibanding pria yang
tidak merokok.

Hindari memakai celana ketat dan panas
Testis perlu memiliki suhu lebih sejuk dibanding bagian tubuh lain karena
itu memakai celana dalam atau celana panjang ketat akan mengakibatkan suhu
di sekitarnya panas. Sedapat mungkin usahakan tidak mengenakan celana dalam
sewaktu tidur untuk menjaga suhu tetap sejuk.

Mulailah makanan makanan yang tepat
Diyakini atau tidak, pola makan akan memengaruhi produksi sperma. Cobalah
makan makanan rendah lemak, berprotein tinggi, sayuran dan seluruh jenis
padi-padian yang baik bagi kesehatan.

Kurangi hubungan intim dan masturbasi
Banyak pria mengeluhkan air mani mereka sedikit dan encer. Semakin banyak
ejakulasi, semakin berkurang kekentalalan air mani tersebut. Jika Anda
melakukan hubungan intim setiap hari atau lebih buruk lagi masturbasi akan
berpengaruh pada jumlah sperma dan kekentalan air mani itu sendiri.

Kurangi alkohol
Alkohol dapat memengaruhi fungsi liver yang pada gilirannya menyebabkan
peningkatan tingkat essexual characteristicsgen. Jumlah estrogen yang
tinggi dalam tubuh akan memengaruhi produksi sperma. Sebaiknya hentikan
minum alkohol mulai saat ini apabila Anda tidak ingin kehilangan jumlah
produksi sperma.

Mencobasexual characteristicsplemen alami
Obat-obatan buatan pabrikan mungkin bisa menghalangi produksi sperma,
sementara suplemen alami diyakini dapat meningkatkan produksi sperma,
seperti L-carnitine yang ditemuk

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found















































kutzi
 commented on  JENKINS-27488


gss.conf file not found















Dylan,
I understand that the situation for GSSAPI authentication is far from being satisfactory.
The thing is that you probably know now - after debugging the issue on your side - infinitely more about how to configure it than I do.
So if you could document your findings on the Wiki, this would be great. If you have other suggestions on how to improve default user behaviour reagrding this issue with the plugin, I'm also happy to hear it.

Sorry, I do know basically nothing about GSSAPI. If you're looking for documentation/help, the Smack API site is probably a better location.



























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







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

[JIRA] [core] (JENKINS-27511) CLONE - Executors are dying after upgrading to 1605















































Ajay Kumar
 commented on  JENKINS-27511


CLONE - Executors are dying after upgrading to 1605















Not so sure if there was an option to change description while cloning. Still a newbee 



























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







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

[JIRA] [core] (JENKINS-27511) CLONE - Executors are dying after upgrading to 1605















































Ajay Kumar
 commented on  JENKINS-27511


CLONE - Executors are dying after upgrading to 1605















to track it if there is any fixes ..and if other are also facing the same issue after upgrading.



























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







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

[JIRA] [core] (JENKINS-27511) CLONE - Executors are dying after upgrading to 1605















































Daniel Beck
 commented on  JENKINS-27511


CLONE - Executors are dying after upgrading to 1605















So why exactly did you clone JENKINS-27081 and not even bother to change the description properly?



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-27512) Support icons for folders

2015-03-19 Thread jskj...@rei.com (JIRA)















































Jeff Skjonsby
 updated  JENKINS-27512


Support icons for folders
















Change By:


Jeff Skjonsby
(19/Mar/15 5:38 PM)




Description:


It would be nice if folders natively supported icons. Proposed syntax:folder('my folder') {  bundledIcon('package')  iconUrl('http://url/to/icon.png')}Relevant configure blocks:bundled icon:configure { folder ->		folder / icon(class:'com.cloudbees.hudson.plugins.folder.icons.BuiltinFolderIcon') {baseName('package')}	}icon url:configure { folder ->		folder / icon(class:'

com.cloudbees.hudson.plugins.folder.icons.UrlFolderIcon') {url('http://url/to/icon.png')}	}



























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







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

[JIRA] [role-strategy-plugin] (JENKINS-19409) Support case-insensitive mode for user IDs

2015-03-19 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 commented on  JENKINS-19409


Support case-insensitive mode for user IDs















@pixman20
Yes, it should work with the "authenticated" user group.
If you want to perform an additional testing, I can provide the plugin's build with the patch. Such contribution will be appreciated.



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-27512) Support icons for folders

2015-03-19 Thread jskj...@rei.com (JIRA)















































Jeff Skjonsby
 created  JENKINS-27512


Support icons for folders















Issue Type:


New Feature



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


19/Mar/15 5:32 PM



Description:


It would be nice if folders natively supported icons. 
Proposed syntax:

folder('my folder') {
  bundledIcon('package')
  iconUrl('http://url/to/icon.png')
}

Relevant configure blocks:
bundled icon:
configure { folder ->
		folder / icon(class:'com.cloudbees.hudson.plugins.folder.icons.BuiltinFolderIcon') {
baseName('package')
}
	}

icon url:
configure { folder ->
		folder / icon(class:'

Project:


Jenkins



Priority:


Minor



Reporter:


Jeff Skjonsby

























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







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

[JIRA] [core] (JENKINS-27511) CLONE - Executors are dying after upgrading to 1605















































Ajay Kumar
 commented on  JENKINS-27511


CLONE - Executors are dying after upgrading to 1605















After upgrade to 1.605 executors are dying 

java.lang.IllegalStateException: /home//.jenkins/jobs/*/builds/834 already existed; will not overwite ** #834
	at hudson.model.RunMap.put(RunMap.java:187)
	at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178)
	at hudson.model.AbstractProject.newBuild(AbstractProject.java:1006)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
	at hudson.model.Executor.run(Executor.java:213)



























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







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

[JIRA] [core] (JENKINS-27511) CLONE - Executors are dying after upgrading to 1605















































Ajay Kumar
 created  JENKINS-27511


CLONE - Executors are dying after upgrading to 1605















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


19/Mar/15 5:28 PM



Description:


After upgrading Jenkins to 1.599 all executors start dying because of the error below. All my jobs are configured to discard old builds.

java.lang.IllegalStateException: cannot create a build with number 1447 since that (or higher) is already in use among [1415, 1416, 1417, 1418, 1419, 1420, 1421, 1422, 1423, 5288]
	at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361)
	at hudson.model.RunMap.put(RunMap.java:189)
	at jenkins.model.lazy.LazyBuildMixIn.newBuild(LazyBuildMixIn.java:178)
	at hudson.model.AbstractProject.newBuild(AbstractProject.java:1006)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205)
	at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144)
	at hudson.model.Executor.run(Executor.java:213)



I could see that the method SortedIntList.isInRange does not check the list content. So I changed it to the code below and everything worked fine.

public boolean isInRange(int idx) {
return find(idx)>-1;
}

I will make a pull request with this solution.




Environment:


Linux Suse, Tomcat 7.0.27, JDK 1.6.0_29




Project:


Jenkins



Priority:


Critical



Reporter:


Ajay Kumar

























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







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

[JIRA] [job-dsl-plugin] (JENKINS-27510) Support "Deploy artifacts to maven repository" for Maven jobs

2015-03-19 Thread jskj...@rei.com (JIRA)















































Jeff Skjonsby
 created  JENKINS-27510


Support "Deploy artifacts to maven repository" for Maven jobs















Issue Type:


New Feature



Assignee:


Daniel Spilker



Components:


job-dsl-plugin



Created:


19/Mar/15 5:21 PM



Description:


We started moving away from using templates and just build the jobs from scratch and were surprised to find this isn't supported by the DSL from what I can tell. 

The configure block that implements this is below:
configure {
it / 'publishers' / 'hudson.maven.RedeployPublisher'() {
 id()
 uniqueVersion('true')
 evenIfUnstable('false')
}
}




Project:


Jenkins



Priority:


Minor



Reporter:


Jeff Skjonsby

























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







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

[JIRA] [gerrit-trigger-plugin] (JENKINS-27438) Gerrit Trigger NPE causes folder not to load















































SCM/JIRA link daemon
 commented on  JENKINS-27438


Gerrit Trigger NPE causes folder not to load















Code changed in jenkins
User: Robert Sandell
Path:
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/b43acba07674bfb7a2023989a9d7d07822d3f46a
Log:
  Merge pull request #214 from ydubreuil/fix-JENKINS-27438

JENKINS-27438: fix NPE when gerritProjects is null


Compare: https://github.com/jenkinsci/gerrit-trigger-plugin/compare/874cc250031b...b43acba07674




























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







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

[JIRA] [gerrit-trigger-plugin] (JENKINS-27438) Gerrit Trigger NPE causes folder not to load















































SCM/JIRA link daemon
 commented on  JENKINS-27438


Gerrit Trigger NPE causes folder not to load















Code changed in jenkins
User: Yoann Dubreuil
Path:
 src/main/java/com/sonyericsson/hudson/plugins/gerrit/trigger/hudsontrigger/GerritTrigger.java
http://jenkins-ci.org/commit/gerrit-trigger-plugin/9f12892b4f72e63054a6620707ad05e6fbee8a0f
Log:
  JENKINS-27438: fix NPE when gerritProjects is null

This NPE is triggered when saving a job where user deleted all Gerrit
Project filters and checked 'Check Non-Reviewed Patchsets'. The job is
saved anyway.

On Jenkins start, it's also triggered when job is loaded, preventing
such jobs to be loaded.





























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







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

[JIRA] [core] (JENKINS-27509) Operations on slave fails after long idle period

2015-03-19 Thread amozgove...@griddynamics.com (JIRA)















































Alexander Mozgovenko
 created  JENKINS-27509


Operations on slave fails after long idle period















Issue Type:


Bug



Assignee:


Francis Upton



Attachments:


git-execption.log, jdkInstaller-exception.log, support.zip



Components:


core, ec2-plugin



Created:


19/Mar/15 4:42 PM



Description:


Operations on slave fails after long idle period of master (>1d).
After restarting master all works fine.

This issue also reproduced on 1.596.1
Slaves are provisioned dynamically by ec2-plugin. Logs attached.




Environment:


CentOS 6.3 x86_64, Jenkins LTS 1.580.2




Project:


Jenkins



Labels:


slave
remoting




Priority:


Major



Reporter:


Alexander Mozgovenko

























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







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

[JIRA] [jabber-plugin] (JENKINS-27488) gss.conf file not found

2015-03-19 Thread dylan.canfi...@colorado.edu (JIRA)















































Dylan Canfield
 commented on  JENKINS-27488


gss.conf file not found















Kutzi,
Where should we go from here? Unfortunately, the way that this problem manifests itself ("gss.conf file not found") does not clearly point to a resolution. Even if we say, "This is an issue with Smack" it will prevent many users from using your plugin. Additional documentation (on your GitHub page), providing a default gss.conf file with the plugin, and/or opening a bug report for Smack is probably warranted.

Also, can you point me to a clear and concise resource for configuring GSSAPI authentication for Java, like the Smack library expects? I have been searching for two days and have only found fragmented pieces of information here and there, which are extremely difficult to piece together.

Thanks, again, for your assistance. I believe that this plugin will be extremely valuable to my team.



























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







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

[JIRA] [role-strategy-plugin] (JENKINS-19409) Support case-insensitive mode for user IDs













































  
pixman20
 edited a comment on  JENKINS-19409


Support case-insensitive mode for user IDs
















Has this been verified to work when using the "authenticated" special "user" when assigning roles.
It may be that it works inherently, but I just want to verify prior to release.
Also, will the update provide an option or will it automatically be case insensitive? (n/m, just saw the png)



























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







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

[JIRA] [role-strategy-plugin] (JENKINS-20340) Allow case insensitive user matching















































pixman20
 commented on  JENKINS-20340


Allow case insensitive user matching















Is this a duplicate of JENKINS-19409?



























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







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

[JIRA] [role-strategy-plugin] (JENKINS-19409) Support case-insensitive mode for user IDs















































pixman20
 commented on  JENKINS-19409


Support case-insensitive mode for user IDs















Has this been verified to work when using the "authenticated" special "user" when assigning roles.
It may be that it works inherently, but I just want to verify prior to release.
Also, will the update provide an option or will it automatically be case insensitive?



























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







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

[JIRA] [teamconcert-plugin] (JENKINS-27464) Workflow integration with Team Concert plugin















































SCM/JIRA link daemon
 commented on  JENKINS-27464


Workflow integration with Team Concert plugin















Code changed in jenkins
User: Jesse Glick
Path:
 COMPATIBILITY.md
http://jenkins-ci.org/commit/workflow-plugin/15d2612bd743f9a000bb73c380e87e8f237157bc
Log:
  JENKINS-27464 Noting.





























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







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

[JIRA] [git-plugin] (JENKINS-27508) Cannot used ENV Variable for repository url in GIT-Plugin in GIT Publisher

2015-03-19 Thread peter....@hotmail.co.uk (JIRA)















































Peter lai
 created  JENKINS-27508


Cannot used ENV Variable for repository url in GIT-Plugin in GIT Publisher 















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git-plugin



Created:


19/Mar/15 3:49 PM



Description:


If you've a variable as the Repository URL, e.g. ${GIT_REPO} doesn't get replaced in git publisher - it will do

hudson.plugins.git.GitException: Command "git push ${GIT_REPO} 1.1.761 -f" returned status code 128:
stdout:




Project:


Jenkins



Priority:


Minor



Reporter:


Peter lai

























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







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

[JIRA] [script-security-plugin] (JENKINS-27306) unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[]















































Jesse Glick
 commented on  JENKINS-27306


unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[]















Just saw that the duplicate is actually a slightly different signature:


unclassified new org.codehaus.groovy.runtime.GStringImpl groovy.lang.GString$2 java.lang.String[]




























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







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

[JIRA] [junit-plugin] (JENKINS-26276) Expose JUnit test results to workflow scripts















































Jesse Glick
 commented on  JENKINS-26276


Expose JUnit test results to workflow scripts















A new use case: mark the build unstable only if the failure count exceeds some threshold. (The current PR does not set the build status, so you can do this yourself via currentBuild.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/d/optout.

[JIRA] [core] (JENKINS-26838) Utility API to check if a file is physically inside a given directory















































Jesse Glick
 commented on  JENKINS-26838


Utility API to check if a file is physically inside a given directory















Does not suffice. First of all, it assumes the child exists, which many legitimate use cases cannot assume. Second, it is buggy:


$ mkdir -p /tmp/basedir && touch /tmp/basedir-attacked && jrunscript -classpath ~/.m2/repository/commons-io/commons-io/2.4/commons-io-2.4.jar -e 'println(org.apache.commons.io.FileUtils.directoryContains(new java.io.File("/tmp/basedir"), new java.io.File("/tmp/basedir-attacked")))'
true




























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







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

[JIRA] [test-stability-plugin] (JENKINS-26625) Support xUnit plugin tests

2015-03-19 Thread nikolay.v.borise...@gmail.com (JIRA)















































Nikolay Borisenko
 commented on  JENKINS-26625


Support xUnit plugin tests















Post-build action is available for "Maven" jobs, but not for "Freestyle" jobs.



























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







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

[JIRA] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs

2015-03-19 Thread f...@geekplace.eu (JIRA)















































Florian Schmaus
 updated  JENKINS-27507


Support multiple .apk files with different application IDs
















Change By:


Florian Schmaus
(19/Mar/15 1:51 PM)




Issue Type:


Improvement
New Feature





Priority:


Minor
Major



























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







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

[JIRA] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs

2015-03-19 Thread f...@geekplace.eu (JIRA)















































Florian Schmaus
 updated  JENKINS-27507


Support multiple .apk files with different application IDs
















Change By:


Florian Schmaus
(19/Mar/15 1:42 PM)




Description:


My project's build system produces multiple .apk with different application IDs. For example there isfoo-main.apk (id: org.foo.main)foo-module-bar.apk (id: org.foo.module.bar)foo-module-baz.apk (id: org.foo.module.baz)currently the google-play-android-publisher-plugin fails with
{noformat}
Multiple APKs were found but they have inconsistent application IDs:- org.foo.main- org.foo.module.bar- org.foo.module.bazBuild step 'Upload Android APK to Google Play' marked build as failure
{noformat}
Please add support for builds creating multiple .apk files with different application IDs.



























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







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

[JIRA] [google-play-android-publisher-plugin] (JENKINS-27507) Support multiple .apk files with different application IDs

2015-03-19 Thread f...@geekplace.eu (JIRA)















































Florian Schmaus
 created  JENKINS-27507


Support multiple .apk files with different application IDs















Issue Type:


Improvement



Assignee:


Christopher Orr



Components:


google-play-android-publisher-plugin



Created:


19/Mar/15 1:41 PM



Description:


My project's build system produces multiple .apk with different application IDs. For example there is
foo-main.apk (id: org.foo.main)
foo-module-bar.apk (id: org.foo.module.bar)
foo-module-baz.apk (id: org.foo.module.baz)

currently the google-play-android-publisher-plugin fails with

Multiple APKs were found but they have inconsistent application IDs:

	org.foo.main
	org.foo.module.bar
	org.foo.module.baz
Build step 'Upload Android APK to Google Play' marked build as failure




Please add support for builds creating multiple .apk files with different application IDs.




Project:


Jenkins



Priority:


Minor



Reporter:


Florian Schmaus

























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







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

[JIRA] [walldisplay-plugin] (JENKINS-27506) Too many yellow dots on Wall Display

2015-03-19 Thread m...@nordicsemi.no (JIRA)















































Markus
 updated  JENKINS-27506


Too many yellow dots on Wall Display
















Change By:


Markus
(19/Mar/15 1:26 PM)




Description:


We often have quite a few jobs in the queue. That is normal operation. And we use this very nice plugin on our monitors. Problem is that when a job is in the back of the queue, get get up to 15 yellow dots. They often block major parts of the text: !dots.PNG
|thumbnail
! Could maybe the maximum number of yellow dots be limited, or add a feature where we can turn the dots off?
(I should add - we have hundreds of jobs so the view used to generate this screen only shows jobs that have failed one of the last X builds.)



























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







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

[JIRA] [walldisplay-plugin] (JENKINS-27506) Too many yellow dots on Wall Display

2015-03-19 Thread m...@nordicsemi.no (JIRA)















































Markus
 created  JENKINS-27506


Too many yellow dots on Wall Display















Issue Type:


Bug



Assignee:


Christian Pelster



Attachments:


dots.PNG



Components:


walldisplay-plugin



Created:


19/Mar/15 1:23 PM



Description:


We often have quite a few jobs in the queue. That is normal operation. And we use this very nice plugin on our monitors. Problem is that when a job is in the back of the queue, get get up to 15 yellow dots. They often block major parts of the text: 

 

Could maybe the maximum number of yellow dots be limited, or add a feature where we can turn the dots off?




Environment:


Jenkins ver. 1.580.2

Wall Display Master Project 0.6.27




Project:


Jenkins



Priority:


Minor



Reporter:


Markus

























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







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

[JIRA] [core] (JENKINS-27505) A blank line in the beginning of a textarea is removed















































Daniel Beck
 commented on  JENKINS-27505


A blank line in the beginning of a textarea is removed















I always thought core trimmed this deliberately. Great 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/d/optout.

[JIRA] [core] (JENKINS-22767) AbstractLazyLoadRunMap.getById subject to race condition with .load















































SCM/JIRA link daemon
 commented on  JENKINS-22767


AbstractLazyLoadRunMap.getById subject to race condition with .load















Code changed in jenkins
User: Jesse Glick
Path:
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java
http://jenkins-ci.org/commit/workflow-plugin/7022e83ecadb84717f65682cd3ec72af4c07f13c
Log:
  @RandomlyFails that I suspect is traceable to JENKINS-22767.





























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







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

[JIRA] [core] (JENKINS-26399) Utility method in JenkinsRule to wait for build to complete















































SCM/JIRA link daemon
 commented on  JENKINS-26399


Utility method in JenkinsRule to wait for build to complete















Code changed in jenkins
User: Jesse Glick
Path:
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/JenkinsRuleExt.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/SingleJobTestBase.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/WorkflowTest.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/PushdStepTest.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/SleepStepTest.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/StageTest.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/WorkspaceStepTest.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/BuildTriggerStepTest.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/build/RunWrapperTest.java
 aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/input/InputStepRestartTest.java
http://jenkins-ci.org/commit/workflow-plugin/fac5ce62db53f18cabb2347f0bb6ae9e3f3ea1f9
Log:
  JENKINS-26399 JenkinsRuleExt.waitForCompletion/Message





























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







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

[JIRA] [core] (JENKINS-27505) A blank line in the beginning of a textarea is removed

2015-03-19 Thread de...@ikedam.jp (JIRA)

ikedam
created JENKINS-27505

A blank line in the beginning of a textarea is removed

Issue Type:

Bug

Assignee:

ikedam

Components:

core

Created:

19/Mar/15 12:16 PM

Description:

A blank line in the beginning of a textarea is removed.
It is caused for the specification of HTML:
http://www.w3.org/TR/html5/syntax.html#syntax-newlines

A single newline may be placed immediately after the start tag of pre and textarea elements. If the element's contents are intended to start with a newline, two consecutive newlines thus need to be included by the author.
(I could not found the description in HTML4.01)

How to reproduce an issue:

Create a new free style project.
Check "This build is parameterized"
Add "Choice Parameter":

Name: PARAM1
Choices

value1

value2

value3

Save the project configuration.
Click "configuration" and go to the project configuration page again.
Choices of PARAM1 gets like this:

value1

value2

value3

The empty line at the beginning is removed!

Environment:

Jenkins 1.605

Project:

Jenkins

Priority:

Minor

Reporter:

ikedam

[JIRA] [job-dsl-plugin] (JENKINS-27504) support for commentFilePath for Pull Request Builder

2015-03-19 Thread vmec...@gmail.com (JIRA)















































Victor Cabello
 created  JENKINS-27504


support for commentFilePath for Pull Request Builder















Issue Type:


New Feature



Assignee:


Victor Cabello



Components:


job-dsl-plugin



Created:


19/Mar/15 12:11 PM



Description:


I was working with this great plugin but I need to use the field commentFilePath from the Pull Request Builder pulgin, right now I have a dirty solution where I inject a new method to trigggercontext meta class but I think it is better to update the library.




Project:


Jenkins



Priority:


Minor



Reporter:


Victor Cabello

























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







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

[JIRA] [pmd-plugin] (JENKINS-24873) Wrong number of new warnings

2015-03-19 Thread dirme...@java.net (JIRA)















































dirmeier
 commented on  JENKINS-24873


Wrong number of new warnings















Hi Ulli, after updating we now have the warning that all warnings are new (and fixed at the same time). May this problem relates to this issue?



























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







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

[JIRA] [mercurial-plugin] (JENKINS-26762) notifyCommit should trigger builds with trailing / defined in SCM URL

2015-03-19 Thread jgrant...@gmail.com (JIRA)















































Jeff G
 commented on  JENKINS-26762


notifyCommit should trigger builds with trailing / defined in SCM URL















Thank you for the clarification on the process here Jesse.



























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







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

[JIRA] [other] (JENKINS-2795) Wrong Url for Artifacts with Space in Name















































Daniel Beck
 commented on  JENKINS-2795


Wrong Url for Artifacts with Space in Name















Commit above is for JENKINS-27495.



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-27495) ListView doesn't support recurse















































SCM/JIRA link daemon
 commented on  JENKINS-27495


ListView doesn't support recurse















Code changed in jenkins
User: Daniel Spilker
Path:
 docs/Home.md
http://jenkins-ci.org/commit/job-dsl-plugin/061b2ccdc2c103a04cfedd6a1b59f4d9b6eab55f
Log:
  added release notes entry for JENKINS-27495





























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







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

[JIRA] [job-dsl-plugin] (JENKINS-27495) ListView doesn't support recurse

2015-03-19 Thread m...@daniel-spilker.com (JIRA)
















































Daniel Spilker
 resolved  JENKINS-27495 as Fixed


ListView doesn't support recurse
















Will be released in 1.31.





Change By:


Daniel Spilker
(19/Mar/15 11:15 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [other] (JENKINS-2795) Wrong Url for Artifacts with Space in Name















































SCM/JIRA link daemon
 commented on  JENKINS-2795


Wrong Url for Artifacts with Space in Name















Code changed in jenkins
User: Vincent Janelle
Path:
 docs/View-Reference.md
 job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/views/ListView.groovy
 job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/views/ListViewSpec.groovy
http://jenkins-ci.org/commit/job-dsl-plugin/d21759bed951c01b9396a5fff4249fc1e74aa87b
Log:
  JENKINS-2795 Add recurse parameter to listView

Adds the recurse parameter, which is necessary when using the folders
plugin to get things to actually show up.





























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







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

[JIRA] [core] (JENKINS-9911) JNLP slave JVM options are ignored

2015-03-19 Thread r...@kamstrup.dk (JIRA)















































Rasmus Pedersen
 commented on  JENKINS-9911


JNLP slave JVM options are ignored















I tried it on 1.599 - doesn't work.



























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







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

[JIRA] [matrix-project-plugin] (JENKINS-27502) Combination filter groovy script fails after upgrade