date:20140821















































Daniel Beck
 commented on  JENKINS-24383


Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin















What happens when you access the XML API of the broken view at /view/VIEWNAME/api/xml ? What's the error (possibly in the log) or output?



























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







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















































Daniel Beck
 commented on  JENKINS-23925


SSL weak ciphers















How can this be reproduced? I just tried with 1.574 and java -jar jenkins.war --httpsPort=, and sslscan reports:


$ sslscan localhost:
   _
   ___ ___| |___  ___ __ _ _ __
  / __/ __| / __|/ __/ _` | '_ \
  \__ \__ \ \__ \ (_| (_| | | | |
  |___/___/_|___/\___\__,_|_| |_|

  Version 1.8.0
 http://www.titania.co.uk
Copyright Ian Ventura-Whiting 2009

Testing SSL server localhost on port 

  Supported Server Cipher(s):
Rejected  N/A  SSLv2  168 bits  DES-CBC3-MD5
Rejected  N/A  SSLv2  56 bits   DES-CBC-MD5
Rejected  N/A  SSLv2  40 bits   EXP-RC2-CBC-MD5
Rejected  N/A  SSLv2  128 bits  RC2-CBC-MD5
Rejected  N/A  SSLv2  40 bits   EXP-RC4-MD5
Rejected  N/A  SSLv2  128 bits  RC4-MD5
Rejected  N/A  SSLv3  128 bits  ADH-SEED-SHA
Rejected  N/A  SSLv3  128 bits  DHE-RSA-SEED-SHA
Rejected  N/A  SSLv3  128 bits  DHE-DSS-SEED-SHA
Rejected  N/A  SSLv3  128 bits  SEED-SHA
Rejected  N/A  SSLv3  256 bits  ADH-AES256-SHA
Rejected  N/A  SSLv3  256 bits  DHE-RSA-AES256-SHA
Rejected  N/A  SSLv3  256 bits  DHE-DSS-AES256-SHA
Rejected  N/A  SSLv3  256 bits  AES256-SHA
Rejected  N/A  SSLv3  128 bits  ADH-AES128-SHA
Accepted  SSLv3  128 bits  DHE-RSA-AES128-SHA
Rejected  N/A  SSLv3  128 bits  DHE-DSS-AES128-SHA
Accepted  SSLv3  128 bits  AES128-SHA
Rejected  N/A  SSLv3  168 bits  ADH-DES-CBC3-SHA
Rejected  N/A  SSLv3  56 bits   ADH-DES-CBC-SHA
Rejected  N/A  SSLv3  40 bits   EXP-ADH-DES-CBC-SHA
Rejected  N/A  SSLv3  128 bits  ADH-RC4-MD5
Rejected  N/A  SSLv3  40 bits   EXP-ADH-RC4-MD5
Accepted  SSLv3  168 bits  EDH-RSA-DES-CBC3-SHA
Rejected  N/A  SSLv3  56 bits   EDH-RSA-DES-CBC-SHA
Rejected  N/A  SSLv3  40 bits   EXP-EDH-RSA-DES-CBC-SHA
Rejected  N/A  SSLv3  168 bits  EDH-DSS-DES-CBC3-SHA
Rejected  N/A  SSLv3  56 bits   EDH-DSS-DES-CBC-SHA
Rejected  N/A  SSLv3  40 bits   EXP-EDH-DSS-DES-CBC-SHA
Accepted  SSLv3  168 bits  DES-CBC3-SHA
Rejected  N/A  SSLv3  56 bits   DES-CBC-SHA
Rejected  N/A  SSLv3  40 bits   EXP-DES-CBC-SHA
Rejected  N/A  SSLv3  40 bits   EXP-RC2-CBC-MD5
Accepted  SSLv3  128 bits  RC4-SHA
Accepted  SSLv3  128 bits  RC4-MD5
Rejected  N/A  SSLv3  40 bits   EXP-RC4-MD5
Rejected  N/A  SSLv3  0 bitsNULL-SHA
Rejected  N/A  SSLv3  0 bitsNULL-MD5
Rejected  N/A  TLSv1  128 bits  ADH-SEED-SHA
Rejected  N/A  TLSv1  128 bits  DHE-RSA-SEED-SHA
Rejected  N/A  TLSv1  128 bits  DHE-DSS-SEED-SHA
Rejected  N/A  TLSv1  128 bits  SEED-SHA
Rejected  N/A  TLSv1  256 bits  ADH-AES256-SHA
Rejected  N/A  TLSv1  256 bits  DHE-RSA-AES256-SHA
Rejected  N/A  TLSv1  256 bits  DHE-DSS-AES256-SHA
Rejected  N/A  TLSv1  256 bits  AES256-SHA
Rejected  N/A  TLSv1  128 bits  ADH-AES128-SHA
Accepted  TLSv1  128 bits  DHE-RSA-AES128-SHA
Rejected  N/A  TLSv1  128 bits  DHE-DSS-AES128-SHA
Accepted  TLSv1  128 bits  AES128-SHA
Rejected  N/A  TLSv1  168 bits  ADH-DES-CBC3-SHA
Rejected  N/A  TLSv1  56 bits   ADH-DES-CBC-SHA
Rejected  N/A  TLSv1  40 bits   EXP-ADH-DES-CBC-SHA
Rejected  N/A  TLSv1  128 bits  ADH-RC4-MD5
Rejected  N/A  TLSv1  40 bits   EXP-ADH-RC4-MD5
Accepted  TLSv1  168 bits  EDH-RSA-DES-CBC3-SHA
Rejected  N/A  TLSv1  56 bits   EDH-RSA-DES-CBC-SHA
Rejected  N/A  TLSv1  40 bits   EXP-EDH-RSA-DES-CBC-SHA
Rejected  N/A  TLSv1  168 bits  EDH-DSS-DES-CBC3-SHA
Rejected  N/A  TLSv1  56 bits   EDH-DSS-DES-CBC-SHA
Rejected  N/A  TLSv1  40 bits   EXP-EDH-DSS-DES-CBC-SHA
Accepted  TLSv1  168 bits  DES-CBC3-SHA
Rejected  N/A  TLSv1  56 bits   DES-CBC-SHA
Rejected  N/A  TLSv1  40 bits   EXP-DES-CBC-SHA
Rej

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

2014-08-21 Thread k...@goyman.com (JIRA)















































Nicolas Goy
 commented on  JENKINS-22591


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















I have the same problem.

I added two branches under "Branches to build", "/develop" and "/staging".

When I push changes to develop, a build is triggered. After that if I do:

git checkout staging
git merge develop
git push

A new build is not triggered.

I use the conditional trigger plugin to have different test suites and post build hook.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin

2014-08-21 Thread rcpao1+jenkins-ci....@gmail.com (JIRA)















































Daniel Beck
 commented on  JENKINS-24383


Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin















Which Jenkins version is this? How is the view that's broken configured? (provide relevant snippet from JENKINS_HOME/config.xml)



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin

2014-08-21 Thread layton.white...@gmail.com (JIRA)















































Layton Whiteley
 updated  JENKINS-24383


Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
















Change By:


Layton Whiteley
(22/Aug/14 2:27 AM)




Environment:


ubuntu - latest
 (vagrant - ubuntu/trusty64 image)



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin

2014-08-21 Thread layton.white...@gmail.com (JIRA)















































Layton Whiteley
 updated  JENKINS-24383


Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
















Change By:


Layton Whiteley
(22/Aug/14 1:56 AM)




Description:


For non-Admin users, the only visible page currently is the new jobs page after the  'Use Github repository permissions' option is selected.Renders the oauth option useless since I cant fine tune access for the allowed users with this option
tested on latest stable jenkins and also latest versionplugin version: 0.19
=Stack trace:=javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.576.jar!/hudson/model/View/index.jelly:42:43:  Cannot invoke method isEmpty() on null object	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:717)	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795)	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)	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 jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117)	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:86)	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:46)	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)	a

[JIRA] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin

2014-08-21 Thread layton.white...@gmail.com (JIRA)















































Layton Whiteley
 created  JENKINS-24383


Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin















Issue Type:


Bug



Affects Versions:


current



Assignee:


Sam Kottler



Attachments:


Screen Shot 2014-08-21 at 9.39.14 PM.png



Components:


github-oauth, security



Created:


22/Aug/14 1:44 AM



Description:


For non-Admin users, the only visible page currently is the new jobs page after the  'Use Github repository permissions' option is selected.

Renders the oauth option useless since I cant fine tune access for the allowed users with this option

=
Stack trace:
=

javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.576.jar!/hudson/model/View/index.jelly:42:43:  Cannot invoke method isEmpty() on null object
	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:717)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	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 jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117)
	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:86)
	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.Hudso

[JIRA] [subversion] (JENKINS-1241) force using HEAD SVN version for build















































Roger C. Pao
 commented on  JENKINS-1241


force using HEAD SVN version for build















If svn:externals are used, the revision checked out will be the Last Changed Rev and not HEAD.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [xunit] (JENKINS-24382) Convert cunit XML to junit XML in xUnit plugin

2014-08-21 Thread rodr...@freebsd.org (JIRA)

Craig Rodrigues
created JENKINS-24382

Convert cunit XML to junit XML in xUnit plugin

Issue Type:

New Feature

Affects Versions:

current

Assignee:

Gregory Boissinot

Components:

xunit

Created:

22/Aug/14 12:17 AM

Description:

I am using xUnit plugin version 1.89

I have a few tests that were written using cunit ( http://cunit.sourceforge.net )
With cunit, it is possible to generate XML output in "automated mode".
See:

http://cunit.sourceforge.net/doc/running_tests.html#automated

However, this XML format is not the same as JUnit XML, so can't be imported
natively into Jenkins. I tried the cppunit converter in the xUnit plugin,
but that didn't import the test results.

I found this script which is part of the cyrus-imapd distribution:

http://git.cyrusimap.org/cyrus-imapd/tree/cunit/cunit-to-junit.pl

This script seems to do a good job of converting cunit xml to junit xml.

Can we port the logic from this script to the xUnit plugin?

It's not problem for me to use this script, but it would be super handy
if this conversion logic was built into the xUnit plugin directly.

I am new to writing Jenkins plugins, so would need some pointers. Thanks!

Project:

Jenkins

Priority:

Minor

Reporter:

Craig Rodrigues

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

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

[JIRA] [maven] (JENKINS-24299) OutOfMemoryError cause maven projects hang

2014-08-21 Thread de...@ikedam.jp (JIRA)















































ikedam
 updated  JENKINS-24299


OutOfMemoryError cause maven projects hang
















I reproduced the problem:

	Install Jenkins 1.565.1
	Install git-plugin and restart
	Go to Manage Jenkins > Configure System
	
		Add a valid JDK (I tested with jdk1.7.0_45)
		Add a valid Maven (I tested with auto-installed maven 3.2.1
	
	
	Create a maven 2/3 project
	
		Add a git repository https://github.com/jenkinsci/build-timeout-plugin.git
		Setup Build as followings:
		
			Root POM: pom.xml
			Goals and options: -DforkMode=never test
			MAVEN_OPTS: -XX:MaxPermSize=16m
		
		
	
	
	Run a build



Result:

	The build hangs with following output in console.

Exception in thread "Channel reader thread: channel" java.lang.OutOfMemoryError: PermGen space


	
		There are cases that log is not output till abort the build (first abort). It looks that the log is buffered.
		The child java process still remains.
	
	
	Aborting the build does not work for the first time.
	
		The child java process still remains.
	
	
	Aborting the build again works.



I attached console logs and outputs:

	Console text when the build hangs: hangingConsoleText.txt
	Thread dump (copied from the output from /threadDump) when the build hangs: hangingConsoleText.txt
	Thread dump when the build does not hang (launched without -XX:MaxPermSize): correctThreaddump.txt
	Output when launched maven in console: launchedFromConsole.log
	
		The process doesn't hang. (the control was returned)
		I launched it as following:

set MAVEN_OPTS=-XX:MaxPermSize=16m
mvn -DforkMode=never test


	
	







Change By:


ikedam
(21/Aug/14 11:56 PM)




Summary:


Maven project build fails to terminate hanging build process
OutOfMemoryError cause maven projects hang





Labels:


remoting





Attachment:


hangingConsoleText.txt





Attachment:


hangingThreadDump.txt





Attachment:


correctThreaddump.txt





Attachment:


launchedFromConsole.log





Environment:


Jenkins 1.565.1, SLES 11.3
Reproduced Jenkins 1.565.1, maven-plugin 2.3, Java 1.7, Windows 8 (64bits)





Component/s:


maven





Component/s:


core



























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







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

[JIRA] [nodejs] (JENKINS-24381) NodeJS Plugin installs while other jobs are running, breaking builds















































Daniel Beck
 commented on  JENKINS-24381


NodeJS Plugin installs while other jobs are running, breaking builds















This is an issue tracker. For requests for assistance (e.g. workaround), please ask on the jenkinsci-users list or in #jenkins on Freenode, you'll likely have more success there.



























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







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

[JIRA] [core] (JENKINS-24352) Unneccessary line breaks in JUnit test results table since 1.576

2014-08-21 Thread travis.cosgr...@patientordersets.com (JIRA)















































Daniel Beck
 updated  JENKINS-24352


Unneccessary line breaks in JUnit test results table since 1.576
















Speculatively assigning to Tom because Tom's the UI guy 





Change By:


Daniel Beck
(21/Aug/14 11:19 PM)




Assignee:


Tom FENNELLY



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-24381) NodeJS Plugin installs while other jobs are running, breaking builds















































Travis Cosgrave
 created  JENKINS-24381


NodeJS Plugin installs while other jobs are running, breaking builds















Issue Type:


Bug



Assignee:


Unassigned


Components:


nodejs



Created:


21/Aug/14 11:02 PM



Description:


I have multiple jobs configured to use the same NodeJS Installer. As a result, sometimes one job is running the installer to update the cache while another one starts. It seems as if all of node is removed making commands unavailable. It looks like it's event happened during a build resulting in a file not found error.

Is there a way to share a node js installer with multiple builds that may run concurrently?


This is the error I received during the middle of my job, after using this package a whole bunch of time before the error.


Error: ENOENT, no such file or directory '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/selenium/commands/'
at Object.fs.readdirSync (fs.js:654:18)
at loadCommandFiles (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:166:27)
at loadClientCommands (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:158:5)
at module.exports.load (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:381:5)
at new Nightwatch (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/index.js:41:18)
at Object.exports.client (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/index.js:432:10)
at runModule (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:142:27)
at runTestModule (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:481:7)
at null._onTimeout (/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:484:13)
at Timer.listOnTimeout [as ontimeout] (timers.js:110:15)

ENOENT, no such file or directory '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/selenium/commands/'+ true





Environment:


Ubuntu 14.04




Project:


Jenkins



Priority:


Major



Reporter:


Travis Cosgrave

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24379) Error while viewing console log

Daniel Beck
edited a comment on JENKINS-24379

Error while viewing console log

Could you please do the following:

1. On the Jenkins master, go to a build showing this behavior. (JENKINS_HOME/jobs/jobname/builds/2014-xx-yy_zz-ww-vv/), create a backup of the buildlog, and open the real one (original file name) in a text editor.
2. Do kind of a "binary search" for the location where it breaks by deleting the first or second half of the contents, saving, and reloading the log page in Jenkins. If it still occurs, repeat. Otherwise, delete the rest and insert the previously deleted half (easiest by working with the clipboard, just cut it rather than deleting), and reload Jenkins to see whether than second half breaks log display.
3. Repeat until you've isolated a small enough sample (no more than 10KB or so would be great), and post that.

Please note that console annotations (what makes text show up bold) look like garbage between escape chars. So 1. use a real text editor, not notepad, to slice the file and 2. keep those annotations intact.

[JIRA] [core] (JENKINS-24379) Error while viewing console log

Daniel Beck
commented on JENKINS-24379

Error while viewing console log

Could you please do the following:

1. On the Jenkins master, go to a build showing this behavior. (JENKINS_HOME/jobs/jobname/builds/2014-xx-yy_zz-ww-vv/), create a backup of the buildlog, and open the real one (original file name) in a text editor.
2. Do kind of a "binary search" for the location where it breaks by deleting half the contents, saving, and reloading the log page in Jenkins. If it still occurs, repeat. Otherwise, delete the rest and insert the previously deleted half (easiest by working with the clipboard, just cut it rather than deleting), and reload Jenkins to see whether than second half breaks log display.
3. Repeat until you've isolated a small enough sample (no more than 10KB or so would be great), and post that.

[JIRA] [core] (JENKINS-24358) Deadlock in OldDataMonitor















































SCM/JIRA link daemon
 commented on  JENKINS-24358


Deadlock in OldDataMonitor















Code changed in jenkins
User: Jesse Glick
Path:
 src/main/java/com/cloudbees/jenkins/support/impl/AdministrativeMonitors.java
http://jenkins-ci.org/commit/support-core-plugin/a116037fe3855d81be347c9835a7c48043d5786b
Log:
  Trying to avoid triggering JENKINS-24358 deadlock.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24379) Error while viewing console log















































Alex Rovner
 commented on  JENKINS-24379


Error while viewing console log















Result: [INFO] — .+-plugin:[^:]+:[^ ]+ (.) @ . —



























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







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

[JIRA] [core] (JENKINS-24379) Error while viewing console log













































  
Alex Rovner
 edited a comment on  JENKINS-24379


Error while viewing console log

















Result: \[INFO\] --- .+-plugin:[^:]+:[^ ]+ \(.+\) @ .+ ---





























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







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

[JIRA] [core] (JENKINS-24379) Error while viewing console log













































  
Alex Rovner
 edited a comment on  JENKINS-24379


Error while viewing console log
















This seems to happen on one project only and my wild guess its because the log from this project is fairly large. This also seems to happen only when you check the log while the build is in progress and only when it's towards the middle of the build cycle. 

Attaching systeminfo



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24379) Error while viewing console log















































Daniel Beck
 commented on  JENKINS-24379


Error while viewing console log















In Manage Jenkins » Script Console, run the following code and report the output:

hudson.tasks._maven.Maven3MojoNote.PATTERN



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24379) Error while viewing console log















































Alex Rovner
 updated  JENKINS-24379


Error while viewing console log
















Change By:


Alex Rovner
(21/Aug/14 10:43 PM)




Attachment:


System Information [Jenkins].html



























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







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

[JIRA] [core] (JENKINS-24379) Error while viewing console log















































Alex Rovner
 commented on  JENKINS-24379


Error while viewing console log















This seems to happen on one project only and my wild guess its because the log from this project is fairly large.

Attaching systeminfo



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24379) Error while viewing console log















































Daniel Beck
 commented on  JENKINS-24379


Error while viewing console log















Can you reproduce this? E.g. always on the same project? Always on the same build's log? If so, could you provide the build.xml and buildlog?

What plugins are installed? Go to /systemInfo and scroll down for a full list.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24380) Use build numbers as IDs















































Jesse Glick
 started work on  JENKINS-24380


Use build numbers as IDs
















Change By:


Jesse Glick
(21/Aug/14 10:20 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-24380) Use build numbers as IDs

Jesse Glick
created JENKINS-24380

Use build numbers as IDs

Issue Type:

Task

Assignee:

Jesse Glick

Components:

core

Created:

21/Aug/14 10:05 PM

Description:

Stop using the formatted timestamp to compute Run.id, and just use the build number as the directory name, so that

r.getId().equals(String.valueOf(r.number))

in which case the timestamp would have to be made a nontransient field (but number could be transient). Then build number symlinks could be dispensed with, saving some hassle and overhead; and AbstractLazyLoadRunMap could be greatly simplified, since the disk location would be immediately predictable from the number, which is what most API calls care about.

The downside is that there would have to be a one-time migration, which could be slow on a big installation, and not reversible.

Project:

Jenkins

Labels:

performance
lazy-loading

Priority:

Major

Reporter:

Jesse Glick

[JIRA] [core] (JENKINS-23963) Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs















































Daniel Beck
 started work on  JENKINS-23963


Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
















Change By:


Daniel Beck
(21/Aug/14 9:48 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-24358) Deadlock in OldDataMonitor















































Jesse Glick
 updated  JENKINS-24358


Deadlock in OldDataMonitor
















Probably always possible, but gets triggered a lot by Support Core plugin, which asks for getData.





Change By:


Jesse Glick
(21/Aug/14 8:55 PM)




Priority:


Major
Critical



























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







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

[JIRA] [core] (JENKINS-24379) Error while viewing console log















































Alex Rovner
 created  JENKINS-24379


Error while viewing console log















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


jenkins-log.txt



Components:


core



Created:


21/Aug/14 8:29 PM



Description:


Error message while viewing console log:

A problem occurred while processing the request.
Please check our bug tracker to see if a similar problem has already been reported.
If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem.
If you think this is a new issue, please file a new issue.
When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.
The users list might be also useful in understanding what has happened.

Stack trace

javax.servlet.ServletException: java.lang.IndexOutOfBoundsException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:390)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:225)
	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 jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117)
	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:86)
	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

[JIRA] [gerrit-trigger] (JENKINS-23871) Play-back Gerrit events which happened during a Jenkins downtime

2014-08-21 Thread ivelin.brata...@ericsson.com (JIRA)













































  
Ivelin Bratanov
 edited a comment on  JENKINS-23871


Play-back Gerrit events which happened during a Jenkins downtime
















It seems that this feature is not functional in the latest release of GT, nor in the master.
This is because the attempt to add the UnreviewedPatchesListener as a listener to the GerritConnection instance is ignored, causing the check for unreviewed patchsets to never occur. (In GerritServer.java)
We've created a fix for this bug and will be contributing it shortly.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-23871) Play-back Gerrit events which happened during a Jenkins downtime

2014-08-21 Thread ivelin.brata...@ericsson.com (JIRA)















































Ivelin Bratanov
 updated  JENKINS-23871


Play-back Gerrit events which happened during a Jenkins downtime
















Change By:


Ivelin Bratanov
(21/Aug/14 7:51 PM)




Assignee:


Ivelin Bratanov
Scott Hebert



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-23871) Play-back Gerrit events which happened during a Jenkins downtime

2014-08-21 Thread ivelin.brata...@ericsson.com (JIRA)















































Ivelin Bratanov
 commented on  JENKINS-23871


Play-back Gerrit events which happened during a Jenkins downtime















It seems that this feature is not functional in the latest release of GT, nor in the master.
This is because the attempt to add the UnreviewedPatchesListener as a listener to the GerritConnection instance is ignored, causing the check for unreviewed patchsets to never occur.
We've created a fix for this bug and will be contributing it shortly.



























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







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

[JIRA] [subversion] (JENKINS-24377) Create Tag (Tag this build) Not working















































Daniel Beck
 commented on  JENKINS-24377


Create Tag (Tag this build) Not working















Note that there are known issues in 1.576 that make it barely usable on some instances (JENKINS-24317). Make sure the issue occurs on 1.575.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ansicolor] (JENKINS-24378) Add support for 256-color and 24-bit-color ANSI escape sequences

2014-08-21 Thread smok...@softpixel.com (JIRA)















































Steve Mokris
 created  JENKINS-24378


Add support for 256-color and 24-bit-color ANSI escape sequences















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


ansicolor



Created:


21/Aug/14 7:29 PM



Project:


Jenkins



Priority:


Major



Reporter:


Steve Mokris

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ownership] (JENKINS-24370) Saving ownership redirects to absolute URL















































SCM/JIRA link daemon
 commented on  JENKINS-24370


Saving ownership redirects to absolute URL















Code changed in jenkins
User: Oleg Nenashev
Path:
 src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction.java
 src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction.java
http://jenkins-ci.org/commit/ownership-plugin/2eef2e88024107fab3401ab160e0df0a3c167628
Log:
  Merge pull request #26 from olivergondza/redirects

[FIXED JENKINS-24370] Saving ownership redirects to absolute URL


Compare: https://github.com/jenkinsci/ownership-plugin/compare/f1605fceac03...2eef2e880241




























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ownership] (JENKINS-24370) Saving ownership redirects to absolute URL















































SCM/JIRA link daemon
 commented on  JENKINS-24370


Saving ownership redirects to absolute URL















Code changed in jenkins
User: Oliver Gondža
Path:
 src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobAction.java
 src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnershipAction.java
http://jenkins-ci.org/commit/ownership-plugin/811c814f36dda92d32bf2d6a7a9cd52d32445300
Log:
  [FIXED JENKINS-24370] Saving ownership redirects to absolute URL





























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







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

[JIRA] [ownership] (JENKINS-24370) Saving ownership redirects to absolute URL

2014-08-21 Thread guillaume.sec+jenk...@gmail.com (JIRA)
















































SCM/JIRA link daemon
 resolved  JENKINS-24370 as Fixed


Saving ownership redirects to absolute URL
















Change By:


SCM/JIRA link daemon
(21/Aug/14 7:30 PM)




Status:


In Progress
Resolved





Resolution:


Fixed



























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







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

[JIRA] [confluence-publisher] (JENKINS-15472) Option to create a new page

2014-08-21 Thread th...@blackberry.com (JIRA)















































Trevor Hill
 commented on  JENKINS-15472


Option to create a new page















I ran into this same issue, so added a configuration parameter to let you specify the pageId of the parent page.  Pull request here: https://github.com/jenkinsci/confluence-publisher-plugin/pull/7



























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







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

[JIRA] [active-directory] (JENKINS-24195) Faster permission lookups when having many unused AD-groups

2014-08-21 Thread clinton.b...@eng-software.com (JIRA)















































Clinton Barr
 commented on  JENKINS-24195


Faster permission lookups when having many unused AD-groups















This may be the cause of our issues. We have two Windows Server 2012 masters, both configured with the Active Directory plugin and we intermittently experience login issues. Sometimes the permission lookup works, but occasionally (when no one has logged into either server for a while, less than a few hours) both servers will take quite a bit of time to login and either work or fail with the following exception (logged on the Jenkins server):


Aug 20, 2014 8:41:26 AM hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider retrieveUser
WARNING: Credential exception tying to authenticate against [domain].net domain
org.acegisecurity.BadCredentialsException: Failed to retrieve user information for [userdev]; nested exception is javax.naming.PartialResultException [Root exception is javax.naming.CommunicationException: [domain].net:389 [Root exception is java.net.ConnectException: Connection timed out: connect]]
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:309)
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:193)
	at hudson.plugins.active_directory.ActiveDirectoryUnixAuthenticationProvider.retrieveUser(ActiveDirectoryUnixAuthenticationProvider.java:137)
	at org.acegisecurity.providers.dao.AbstractUserDetailsAuthenticationProvider.authenticate(AbstractUserDetailsAuthenticationProvider.java:122)
	at org.acegisecurity.providers.ProviderManager.doAuthentication(ProviderManager.java:200)
	at org.acegisecurity.AbstractAuthenticationManager.authenticate(AbstractAuthenticationManager.java:47)
	at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74)
	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:46)
	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:1474)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
	at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
	at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
	at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
	at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
	at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
	at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
	at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
	at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
	at org.eclipse.jetty.server.Server.handle(Server.java:370)
	at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489)
	at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960)
	at org.eclipse.jetty.server.AbstractHttpConnection$RequestHan

[JIRA] [perforce] (JENKINS-24375) p4ticket randomly dropped from job execution

2014-08-21 Thread scasw...@battlecrystudios.com (JIRA)















































Sam Caswell
 updated  JENKINS-24375


p4ticket randomly dropped from job execution
















Change By:


Sam Caswell
(21/Aug/14 6:48 PM)




Priority:


Blocker
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] [subversion] (JENKINS-24377) Create Tag (Tag this build) Not working

2014-08-21 Thread jenkins.d...@spamgourmet.com (JIRA)















































Damon Overboe
 commented on  JENKINS-24377


Create Tag (Tag this build) Not working















I'm able to get login failures when adding a new project when I haven't set the credentials yet; those go to both the master log and the SubversionSCM log, but those failures are expected.

Also for what it's worth, I have the svnmerge plug-in, version 2.3, to create, update, and integrate feature branches, and that works well.

So, I'm going to try disabling as many plugins as I can on a test server to see if one of them is interfering with the Subversion Plugin to rule that out.




























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







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

[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb















































Guillaume
 commented on  JENKINS-11952


Emulator occasionally hangs indefinitely on startup, unable to connect adb















You're right, trying with emulators of different resolution / density I was able to connect to it in some instances (although it still fails sometimes, but I couldn't investigate it much yet).
Sorry for polluting the thread with an unrelated error. Eventually the patch seems to have solved the current issue for me (again, in some cases, I'll come back if I find out more and it seems directly related to this issue).

Thanks for helping out.



























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







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

[JIRA] [git] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git

2014-08-21 Thread mark.earl.wa...@gmail.com (JIRA)















































Mark Waite
 commented on  JENKINS-24368


Authentication failed for https://usern...@bitbucket.org/project/repository.git















My technique was to define a credential through the "Manage Credentials" page in Jenkins administration, then reference that credential in the job definition and remove the "username@" portion from the https URL.



























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







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

[JIRA] [subversion] (JENKINS-24377) Create Tag (Tag this build) Not working

2014-08-21 Thread jenkins.d...@spamgourmet.com (JIRA)















































Damon Overboe
 commented on  JENKINS-24377


Create Tag (Tag this build) Not working















Steps I took on the logs:

1. In log levels and added hudson.scm.SubversionSCM, setting it to Fine,
2. then tested tagging a successful build. No output.
3. Back in log levels, I bumped it to All,
4. Same result as #2,
5. So I added a new log recorder, set to hudson.scm.SubversionSCM, and level All.
6. Repeated #2, still no output, and the listener in #5 is empty.
7. Rebooted
8. Repeated #2, this time I saw the "Clear Error to Retry" 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] [subversion] (JENKINS-24377) Create Tag (Tag this build) Not working















































Daniel Beck
 updated  JENKINS-24377


Create Tag (Tag this build) Not working
















Change By:


Daniel Beck
(21/Aug/14 5:48 PM)




Summary:


CLONE -
 Create Tag (Tag this build) Not working



























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







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

[JIRA] [subversion] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working















































Daniel Beck
 updated  JENKINS-24377


CLONE - Create Tag (Tag this build) Not working
















Change By:


Daniel Beck
(21/Aug/14 5:43 PM)




Fix Version/s:


current





Affects Version/s:


current





Component/s:


subversion





Component/s:


svn-tag



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working

2014-08-21 Thread jenkins.d...@spamgourmet.com (JIRA)















































Damon Overboe
 commented on  JENKINS-24377


CLONE - Create Tag (Tag this build) Not working















It's actually not the SVN Tag plugin, it's just the plain Subversion plugin, using the manual "Tag this build" that you execute on a successful run.

It is the same behavior on both version 2.4.1 and and 2.4.3.  (The ...scm.xml file from above was before upgrading the plugin)



After restarting the server, I see an error page, but still no log. It simply says:


Build #36

Tagging is in progress:

[Clear Error to Retry]


I checked the logs before and after clicking the "Clear Error" button and there is nothing for the SCM plugin.



























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







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

[JIRA] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working















































Daniel Beck
 commented on  JENKINS-24377


CLONE - Create Tag (Tag this build) Not working















Which version of the SVN Tag plugin?



























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







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

[JIRA] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working

2014-08-21 Thread jenkins.d...@spamgourmet.com (JIRA)















































Damon Overboe
 commented on  JENKINS-24377


CLONE - Create Tag (Tag this build) Not working















I figured cloning the related issue was the right way to go, since that issue was never solved, but was just closed because not enough information was provided to track down the bug?

Yeah, I should have started with just a local draft before posting. I'm going to update it with a bit more information if I can get a good log output, but it's failing silently, even with the hudson.scm.SubversionSCM log set to 'All'.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working















































Daniel Beck
 reopened  JENKINS-24377


CLONE - Create Tag (Tag this build) Not working
















Change By:


Daniel Beck
(21/Aug/14 5:31 PM)




Resolution:


Incomplete





Status:


Resolved
Reopened



























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







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

[JIRA] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working















































Daniel Beck
 updated  JENKINS-24377


CLONE - Create Tag (Tag this build) Not working
















Change By:


Daniel Beck
(21/Aug/14 5:31 PM)




Status:


Reopened
Open



























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







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

[JIRA] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working

2014-08-21 Thread jenkins.d...@spamgourmet.com (JIRA)

Damon Overboe
updated JENKINS-24377

CLONE - Create Tag (Tag this build) Not working

Change By:

Damon Overboe
(21/Aug/14 5:30 PM)

Description:

This is a clone of the original bug, when When attempting a tag after selecting 'Tag this build', the tag fails.
Generally, it fails silently, not pumping any information
This is also related
to
the UI or even the event logs (even with the hudson Subversion SCM log set to 'fine' or higher)
https://issues
.
jenkins-ci.org/browse/JENKINS-21797, but I have eliminated that.
I was able to get it to pump one failure message, but I was not able to capture it. I am restarting the VM to see if it will pump the message again.
Generally, it fails silently, not pumping any information to the UI or even the event logs (even with the hudson.scm.SubversionSCM log set to 'fine' or higher).
I can recreate it using Jenkins 1.575 or 1.576 on Windows Server 2012, using the latest of the Subversion plugin
.Original meessage:Hudson
, with a working copy of
version 1.
227
7
.
Stand alone setup running on Winstone.

When attempting
The SVN server is "SmartSVN" hosted on
a
tag after selecting 'Tag this build',
Windows 2012 server. It has
the
tag fails with an error:Tagging http:
non-configurable convention of requiring serverpath
/
/subversion/
svn/
X/web/project/trunk (rev.19085)
before your repo name, and on the log I failed
to
http:
capture, I saw it complain about
/
/subversion/
svn/
X/web/project/tags/project-30
myreponame on the copy.

Failed to tagorg
There is only one user specified in the Jenkins credentials for SVN, and they have tagging privileges
.
tmatesoft.svn.core.SVNAuthenticationException: svn: Commit failed (details

follow):

svn
And I tried the workaround from a similar bug, where you
:
CHECKOUT of '/svn/X/!svn/ver/19211/web/project/tags': 403 Forbidden

(http://subversion)

atorg
1
.
tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84)
Connect to the target machine

at org
2
.
tmatesoft.
Run `
svn
.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354)
cleanup` & `svn up` on each workspace, specifying the credentials

athudson
But that had no impact on the result
.
scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167)

at hudson.model.TaskThread.run(TaskThread.java:77)

Completed

The error suggests the user setup within the
There are no credentials stored in my
hudson.scm.SubversionSCM.xml
does
file:

not have the authority to checkout the subversion tags directory revision

.
0' encoding='UTF-8'?>

Further investigation found the user being used for the tag is the user thatstarted Hudson in the first instance, and NOT the user declared in the
<
hudson.scm.
SubversionSCM
SubversionSCM_-DescriptorImpl plugin="subversion@2
.
xml file
4
.
Thus, if the user account that started Hudson
1">

does not have enough permissions for SVN, then the tagging fails with the above
49

error.
false

100

Regards
false

false

Matt Gaunt

[JIRA] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client

2014-08-21 Thread dacul...@cisco.com (JIRA)















































David Cullen
 commented on  JENKINS-22820


Changes are not commited when using a recent git client















I have the same problem: Jenkins 1.565.1 LTS, scm-sync-plugin 0.0.7.5, git plugin 2.2.5, git client plugin 1.10.1, Ubuntu 14.04.1 LTS.
I downloaded the source for the plugin so that I could try to fix the problem, but I am having difficulty figuring out how it works.
Also, is there a way to pass LANG=en_US.UTF-8 to git? If I can't fix the problem, maybe this would be a workaround.



























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







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

[JIRA] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working
















































Daniel Beck
 resolved  JENKINS-24377 as Incomplete


CLONE - Create Tag (Tag this build) Not working
















Please file an issue from scratch instead of cloning a six years old one.

Explain what the problems you're facing are, in detail.





Change By:


Daniel Beck
(21/Aug/14 5:22 PM)




Status:


Open
Resolved





Resolution:


Incomplete



























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







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

[JIRA] [core] (JENKINS-19764) Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist















































Daniel Beck
 started work on  JENKINS-19764


Jenkins with custom build record root dir: renaming a job should create the new build record dir if it does not already exist
















Change By:


Daniel Beck
(21/Aug/14 5:20 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working

2014-08-21 Thread jenkins.d...@spamgourmet.com (JIRA)















































Damon Overboe
 updated  JENKINS-24377


CLONE - Create Tag (Tag this build) Not working
















Change By:


Damon Overboe
(21/Aug/14 5:21 PM)




Fix Version/s:


current





Environment:


Platform: All, OS:
 HP-UX
 WIndows Server 2012





Description:


This is a clone of the original bug, when When attempting a tag after selecting 'Tag this build', the tag fails.Generally, it fails silently, not pumping any information to the UI or even the event logs (even with the hudson Subversion SCM log set to 'fine' or higher).I was able to get it to pump one failure message, but I was not able to capture it. I am restarting the VM to see if it will pump the message again.I can recreate it using Jenkins 1.575 or 1.576 on Windows Server 2012, using the latest of the Subversion plugin.Original meessage:
Hudson version 1.227. Stand alone setup running on Winstone.


When attempting a tag after selecting 'Tag this build', the tag fails with an error:


Tagging http://subversion/svn/X/web/project/trunk (rev.19085) to


http://subversion/svn/X/web/project/tags/project-30


Failed to tag


org.tmatesoft.svn.core.SVNAuthenticationException: svn: Commit failed (details


follow):


svn: CHECKOUT of '/svn/X/!svn/ver/19211/web/project/tags': 403 Forbidden


(http://subversion)


	at


org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84)


	at org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354)


	at


hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167)


	at hudson.model.TaskThread.run(TaskThread.java:77)


Completed


The error suggests the user setup within the hudson.scm.SubversionSCM.xml does


not have the authority to checkout the subversion tags directory revision.


Further investigation found the user being used for the tag is the user that


started Hudson in the first instance, and NOT the user declared in the


hudson.scm.SubversionSCM.xml file. Thus, if the user account that started Hudson


does not have enough permissions for SVN, then the tagging fails with the above


error.


Regards


Matt Gaunt



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [svn-tag] (JENKINS-24377) CLONE - Create Tag (Tag this build) Not working

2014-08-21 Thread jenkins.d...@spamgourmet.com (JIRA)















































Damon Overboe
 created  JENKINS-24377


CLONE - Create Tag (Tag this build) Not working















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


svn-tag



Created:


21/Aug/14 5:11 PM



Description:


Hudson version 1.227. Stand alone setup running on Winstone.

When attempting a tag after selecting 'Tag this build', the tag fails with an error:
Tagging http://subversion/svn/X/web/project/trunk (rev.19085) to
http://subversion/svn/X/web/project/tags/project-30

Failed to tag

org.tmatesoft.svn.core.SVNAuthenticationException: svn: Commit failed (details
follow):

svn: CHECKOUT of '/svn/X/!svn/ver/19211/web/project/tags': 403 Forbidden
(http://subversion)

	at
org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:84)

	at org.tmatesoft.svn.core.wc.SVNCopyClient.doCopy(SVNCopyClient.java:354)

	at
hudson.scm.SubversionTagAction$TagWorkerThread.perform(SubversionTagAction.java:167)

	at hudson.model.TaskThread.run(TaskThread.java:77)

Completed



The error suggests the user setup within the hudson.scm.SubversionSCM.xml does
not have the authority to checkout the subversion tags directory revision.

Further investigation found the user being used for the tag is the user that
started Hudson in the first instance, and NOT the user declared in the
hudson.scm.SubversionSCM.xml file. Thus, if the user account that started Hudson
does not have enough permissions for SVN, then the tagging fails with the above
error.

Regards

Matt Gaunt




Environment:


Platform: All, OS: HP-UX




Project:


Jenkins



Priority:


Major



Reporter:


Damon Overboe

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [maven2] (JENKINS-21522) Enable "Archive maven artifacts" post-build action for free-style jobs















































Jesse Glick
 commented on  JENKINS-21522


Enable "Archive maven artifacts" post-build action for free-style jobs















Via magic and tricks.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24244) Scheduled polling not run

2014-08-21 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-24244


Scheduled polling not run















Integrated in  jenkins_main_trunk #3642
 JENKINS-24244 If we are skipping polling due to quietingDown, at least record this fact in the system log. (Revision 608517e187cb5bd1566b1c3728a4df0f7ac4dd5c)

 Result = SUCCESS
Jesse Glick : 608517e187cb5bd1566b1c3728a4df0f7ac4dd5c
Files : 

	core/src/main/java/hudson/triggers/SCMTrigger.java





























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







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

[JIRA] [mailer] (JENKINS-24318) Restrict which domains mail is sent to















































Daniel Beck
 commented on  JENKINS-24318


Restrict which domains mail is sent to















Sorry about that, the other issue's title is misleading.



























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







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

[JIRA] [subversion] (JENKINS-24373) Changes - Links to Redmine Repo Browser don't work















































Daniel Beck
 updated  JENKINS-24373


Changes - Links to Redmine Repo Browser don't work
















Change By:


Daniel Beck
(21/Aug/14 4:55 PM)




Assignee:


Nicolas De Loof





Component/s:


subversion





Component/s:


changes-since-last-success



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24371) Neither dashboard nor build details work
















































Daniel Beck
 resolved  JENKINS-24371 as Duplicate


Neither dashboard nor build details work
















Change By:


Daniel Beck
(21/Aug/14 4:51 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [perforce] (JENKINS-24375) p4ticket randomly dropped from job execution

2014-08-21 Thread scasw...@battlecrystudios.com (JIRA)















































Sam Caswell
 commented on  JENKINS-24375


p4ticket randomly dropped from job execution















I have managed to find one work around.  p4 logout -a on the master server, then run the offending job in Jenkins to force a p4 login.  This appears to kick-start the use of the p4 ticket and the creation of the P4TICKET variable 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] [nodeofflinenotification] (JENKINS-20720) Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin

2014-08-21 Thread mille...@hp.com (JIRA)















































Jason Miller
 commented on  JENKINS-20720


Jenkins fails to connect to slave via ssh after nodeofflinenotification plugin















I want to add that in Jenkins build 1.575 + GIT plugin 2.2.5 where builds are only executed on slaves, this also appears to prevent push notifications from properly working.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ownership] (JENKINS-24370) Saving ownership redirects to absolute URL

2014-08-21 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 commented on  JENKINS-24370


Saving ownership redirects to absolute URL















This is a problem when user access Jenkins using different url than the one that is configured. Unwanted switch between http and https for instance.

This problem demonstrates the default configuration of hpi:run. It is launched on http://localhost:8080/jenkins but configured to be running at http://localhost.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [maven2] (JENKINS-21522) Enable "Archive maven artifacts" post-build action for free-style jobs

2014-08-21 Thread dm...@java.net (JIRA)















































dma_k
 commented on  JENKINS-21522


Enable "Archive maven artifacts" post-build action for free-style jobs















@Jesse: But this functionality works OK for "Maven-style" job. I wonder how?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [emailext-template] (JENKINS-22613) email-ext-template plugin has many names

2014-08-21 Thread slide.o....@gmail.com (JIRA)
















































Alex Earl
 resolved  JENKINS-22613 as Fixed


email-ext-template plugin has many names
















The old component has been removed.





Change By:


Alex Earl
(21/Aug/14 4:40 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-24376) Queue constantly locked when rapidly scheduling builds















































Jesse Glick
 commented on  JENKINS-24376


Queue constantly locked when rapidly scheduling builds















Oops, forgot about getIDFormatter(), which is also used by build-publisher-plugin and disk-usage-plugin.



























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







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

[JIRA] [core] (JENKINS-24376) Queue constantly locked when rapidly scheduling builds













































  
Jesse Glick
 edited a comment on  JENKINS-24376


Queue constantly locked when rapidly scheduling builds
















Compatibility implications: ftppublisher-plugin, jobConfigHistory-plugin, and support-core-plugin seem to assume something about the current ID format and so might be broken. (Just grepping sources for -MM-dd_HH-mm-ss and ID_FORMATTER.)



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24376) Queue constantly locked when rapidly scheduling builds
















































Jesse Glick
 assigned  JENKINS-24376 to Jesse Glick



Queue constantly locked when rapidly scheduling builds
















Change By:


Jesse Glick
(21/Aug/14 4:25 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-24376) Queue constantly locked when rapidly scheduling builds















































Jesse Glick
 started work on  JENKINS-24376


Queue constantly locked when rapidly scheduling builds
















Change By:


Jesse Glick
(21/Aug/14 4:25 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-24376) Queue constantly locked when rapidly scheduling builds















































Jesse Glick
 commented on  JENKINS-24376


Queue constantly locked when rapidly scheduling builds















Compatibility implications: ftppublisher-plugin, jobConfigHistory-plugin, and support-core-plugin seem to assume something about the current ID format and so might be broken. (Just grepping sources for -MM-dd_HH-mm-ss.)



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [mailer] (JENKINS-24318) Restrict which domains mail is sent to

2014-08-21 Thread jenk...@albersweb.de (JIRA)















































Harald Albers
 commented on  JENKINS-24318


Restrict which domains mail is sent to















It's about the same feature, but there are two distinct plugins involved, so we really need to issues here.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [mailer] (JENKINS-24318) Restrict which domains mail is sent to

2014-08-21 Thread jenk...@albersweb.de (JIRA)















































Harald Albers
 reopened  JENKINS-24318


Restrict which domains mail is sent to
















Change By:


Harald Albers
(21/Aug/14 4:12 PM)




Resolution:


Duplicate





Status:


Resolved
Reopened



























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







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

[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service















































Daniel Beck
 commented on  JENKINS-22685


Jenkins cannot restart Windows service















Are you running Jenkins as a non-default user? Maybe one who's not allowed to restart services? Try to give that user permission to use WMI:

http://technet.microsoft.com/en-us/library/cc787533%28v=WS.10%29.aspx

I'm asking, because in the default setup, it works for me:

Tried with 1.576 on Windows 8.1 Pro installed with the installer. Restart works without issues.


2014-08-21 17:41:00 - Starting C:\Program Files (x86)\Jenkins\jre\bin\java -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "C:\Program Files (x86)\Jenkins\jenkins.war" --httpPort=8080
2014-08-21 17:41:00 - Started 4088
2014-08-21 17:42:26 - Stopping jenkins
2014-08-21 17:42:26 - ProcessKill 4088
2014-08-21 17:42:26 - Send SIGINT 4088
2014-08-21 17:42:26 - SIGINT to 4088 failed - Killing as fallback
2014-08-21 17:42:26 - Send SIGINT 4088
2014-08-21 17:42:26 - SIGINT to 4088 failed - Killing as fallback
2014-08-21 17:42:26 - Finished jenkins
2014-08-21 17:42:28 - Starting C:\Program Files (x86)\Jenkins\jre\bin\java -Xrs -Xmx256m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "C:\Program Files (x86)\Jenkins\jenkins.war" --httpPort=8080
2014-08-21 17:42:28 - Started 568


Web UI was available again as well.

Then I tried 1.565.1 on the same machine (after resetting the VM to before I installed 1.576).

Again it worked like a charm.



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ssh-agent] (JENKINS-18897) ssh-agent & slave: 'JCE cannot authenticate the provider BC', because 'Class is on the bootclasspath'

2014-08-21 Thread courtla...@gamesalad.com (JIRA)















































Courtland Jones
 commented on  JENKINS-18897


ssh-agent & slave: 'JCE cannot authenticate the provider BC', because 'Class is on the bootclasspath'















This same error happened for me, but the JDK version did not appear to be the issue. I thought I would share, in case anyone else runs across what I did:
At least in some configurations, this error can be caused by using an SSH key that is too long. In my case, I used a 4096-bit RSA key, which ssh/git/GitHub normally have no problem with. Switching to using a 2048-bit RSA key alleviated this problem.



























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







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

[JIRA] [perforce] (JENKINS-24375) p4ticket randomly dropped from job execution

2014-08-21 Thread rob.pe...@gmail.com (JIRA)
















































Rob Petti
 assigned  JENKINS-24375 to Unassigned



p4ticket randomly dropped from job execution
















Change By:


Rob Petti
(21/Aug/14 3:48 PM)




Assignee:


Rob Petti



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24376) Queue constantly locked when rapidly scheduling builds















































Jesse Glick
 commented on  JENKINS-24376


Queue constantly locked when rapidly scheduling builds















Perhaps new SimpleDateFormat("-MM-dd_HH-mm-ss-SSS").setTimeZone(TimeZone.getTimeZone("UTC"))? Would use a similar format to what we already use, without introducing new characters. ISO-8601 etc. are not ideal for this purpose.



























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







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

[JIRA] [perforce] (JENKINS-24366) Missing Root in client spec

2014-08-21 Thread morne.joub...@u-blox.com (JIRA)















































Morne Joubert
 commented on  JENKINS-24366


Missing Root in client spec















Hi Rob,
We are using Jenkins 1.568 on master on linux (slaves on windows and linux) , Perforce plugin 1.3.27

We upgraded to 1.3.27 (from 1.3.24) in the last 2 weeks, we have only recently noticed these errors in the log files.

I am not sure if it is related to:
hudson.plugins.perforce.utils.ParameterSubstitutionException: <${jobName}_jenkins_mlb>: Found unresolved macro at '${jobName}_jenkins_mlb'
at hudson.plugins.perforce.utils.MacroStringHelper.checkString(MacroStringHelper.java:97)
at hudson.plugins.perforce.utils.MacroStringHelper.substituteParameters(MacroStringHelper.java:64)
at hudson.plugins.perforce.PerforceSCM.getDepot(PerforceSCM.java:463)
at hudson.plugins.perforce.PerforceMailResolver.findPerforceMailAddressFor(PerforceMailResolver.java:78)
at hudson.plugins.perforce.PerforceMailResolver.findMailAddressFor(PerforceMailResolver.java:25)
at hudson.tasks.MailAddressResolver.resolve(MailAddressResolver.java:112)
at hudson.tasks.Mailer$UserProperty.getAddress(Mailer.java:547)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
...

that we saw during this period as well

It doesn't seem to be impacted the actual running of the freestyle projects but wanted to check why these are in the log 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-24244) Scheduled polling not run















































SCM/JIRA link daemon
 commented on  JENKINS-24244


Scheduled polling not run















Code changed in jenkins
User: Jesse Glick
Path:
 core/src/main/java/hudson/triggers/SCMTrigger.java
http://jenkins-ci.org/commit/jenkins/608517e187cb5bd1566b1c3728a4df0f7ac4dd5c
Log:
  JENKINS-24244 If we are skipping polling due to quietingDown, at least record this fact in the system log.





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-24376) Queue constantly locked when rapidly scheduling builds















































Jesse Glick
 created  JENKINS-24376


Queue constantly locked when rapidly scheduling builds















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


21/Aug/14 3:31 PM



Description:


If there is a job that gets very rapidly scheduled, since a Run.id currently must be unique to the second, a lot of the time the Queue will be locked:


... waiting on condition [...]
   java.lang.Thread.State: TIMED_WAITING (sleeping)
at java.lang.Thread.sleep(Native Method)
at hudson.model.AbstractProject.newBuild(AbstractProject.java:1121)
- locked <...> (a hudson.model.FreeStyleProject)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1349)
at hudson.model.AbstractProject.createExecutable(AbstractProject.java:156)
at hudson.model.Executor.run(Executor.java:211)
- locked <...> (a hudson.model.Queue)


which can prevent other things from happening, such as routine queue maintenance, or even rendering of the queue widget (which expects a fresh snapshot every second):


"Handling ..." ... waiting for monitor entry [...]
   java.lang.Thread.State: BLOCKED (on object monitor)
at hudson.model.Queue.getItems(Queue.java:685)
- waiting to lock <...> (a hudson.model.Queue)
at hudson.model.Queue$CachedItemList.get(Queue.java:217)
at hudson.model.Queue.getApproximateItemsQuickly(Queue.java:715)
at hudson.model.View.getApproximateQueueItemsQuickly(View.java:483)


(This also artificially slows down some functional tests.)




Project:


Jenkins



Labels:


performance
queue




Priority:


Major



Reporter:


Jesse Glick

























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







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

[JIRA] [core] (JENKINS-22685) Jenkins cannot restart Windows service

2014-08-21 Thread mich...@glauche.de (JIRA)















































Michael Glauche
 commented on  JENKINS-22685


Jenkins cannot restart Windows service















Having the same problem with 1.565.1, running as windows service. Also stuck at "Please wait while Jenkins is restarting ..."



























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







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

[JIRA] [perforce] (JENKINS-24375) p4ticket randomly dropped from job execution

2014-08-21 Thread scasw...@battlecrystudios.com (JIRA)















































Sam Caswell
 created  JENKINS-24375


p4ticket randomly dropped from job execution















Issue Type:


Bug



Affects Versions:


current



Assignee:


Rob Petti



Components:


perforce



Created:


21/Aug/14 3:16 PM



Description:


The P4TICKET variable will randomly disappear in jobs running on the Jenkins Master.  This is job specific as other jobs running on the Master will continue to use the ticket properly.  This causes any jobs that rely on the existence of the P4TICKET variable to randomly fail.  So far I have not found a reliable work around to force the jobs to start using P4TICKETS in it's P4 commands again.  Forced logout/login with -a and restarts of Jenkins and the Master Node have not worked.




Environment:


Jenkins Master running on Windows Server 2008 R2 Standard SP1




Project:


Jenkins



Labels:


plugin
scm
perforce




Priority:


Blocker



Reporter:


Sam Caswell

























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-24372) Test runner should be able to specify the local *.hpi file to put into the test environment















































SCM/JIRA link daemon
 commented on  JENKINS-24372


Test runner should be able to specify the local *.hpi file to put into the test environment















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/org/jenkinsci/test/acceptance/update_center/LocalOverrideUpdateCenterMetadataDecoratorImpl.java
 src/main/java/org/jenkinsci/test/acceptance/update_center/PluginMetadata.java
http://jenkins-ci.org/commit/acceptance-test-harness/a0fc205fa89b1b447184638dcd866e1c44ceb9ec
Log:
  [FIXED JENKINS-24372]

Reimplemented local plugin override





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-24372) Test runner should be able to specify the local *.hpi file to put into the test environment















































SCM/JIRA link daemon
 commented on  JENKINS-24372


Test runner should be able to specify the local *.hpi file to put into the test environment















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/org/jenkinsci/test/acceptance/guice/LocalPluginOverride.java
 src/main/java/org/jenkinsci/test/acceptance/junit/WithPlugins.java
http://jenkins-ci.org/commit/acceptance-test-harness/8a94106542ba0a200a1fc7ad12a83a6480cbeee9
Log:
  Revert [FIXED JENKINS-24372]

This reverts commit aadc0f80798d6b983f056e0c7200daf01637ae5f.
I think a better way to do this is to hook up in the part of the code
that does Maven download





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [hipchat] (JENKINS-23720) jenkins hipchat plugin does not support hosted hipchat

2014-08-21 Thread ch...@orr.me.uk (JIRA)
















































Christopher Orr
 closed  JENKINS-23720 as Fixed


jenkins hipchat plugin does not support hosted hipchat
















Version 0.1.7 of the plugin has been released, which allows a custom server hostname to be entered.

Though note that once you've upgraded, you'll need to ensure you enter the global Jenkins config and explicitly set a hostname, otherwise the plugin will stop working:
https://github.com/jenkinsci/hipchat-plugin/pull/7#issuecomment-52929844





Change By:


Christopher Orr
(21/Aug/14 2:45 PM)




Status:


Open
Closed





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] [role-strategy] (JENKINS-19934) Add "Job Create" permission to project roles

2014-08-21 Thread mweb...@java.net (JIRA)















































mwebber
 commented on  JENKINS-19934


Add "Job Create" permission to project roles















Sorry, I should have said. This is Jenkins 1.575, with Role Strategy Plugin 2.2.0. and CAS Plugin 1.1.2.



























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







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

[JIRA] [core] (JENKINS-24357) Jenkins 1.535+ versions do not work on Solaris 10

2014-08-21 Thread valentino.s...@gmail.com (JIRA)













































  
Bhagyesh Shah
 edited a comment on  JENKINS-24357


Jenkins 1.535+ versions do not work on Solaris 10
















Thread dump for the process is attached

I thought the issue is similar but at this point I am not that sure about it



























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







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

[JIRA] [core] (JENKINS-24357) Jenkins 1.535+ versions do not work on Solaris 10

2014-08-21 Thread valentino.s...@gmail.com (JIRA)















































Bhagyesh Shah
 updated  JENKINS-24357


Jenkins 1.535+ versions do not work on Solaris 10
















Thread dump for the process





Change By:


Bhagyesh Shah
(21/Aug/14 2:29 PM)




Attachment:


threaddump.out



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [jira] (JENKINS-20322) JIRA plugin should be configurable to decide where to write other than comments

2014-08-21 Thread gianmario.conte...@gmail.com (JIRA)
















































Gian Mario Contessa
 assigned  JENKINS-20322 to Laszlo Miklosik



JIRA plugin should be configurable to decide where to write other than comments
















Hi Laszlo, I'm assigning this to you because I saw on github your activity and I'm not sure this task has ever been seen.

Maybe I didn't put it in the right project/component.

Could you please have a look and let me know what you think of the improvement I suggest?

Thanks,

Gian Mario





Change By:


Gian Mario Contessa
(21/Aug/14 2:29 PM)




Assignee:


Laszlo Miklosik



























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







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

[JIRA] [android-emulator] (JENKINS-11952) Emulator occasionally hangs indefinitely on startup, unable to connect adb

2014-08-21 Thread oldel...@java.net (JIRA)

Richard Mortimer
commented on JENKINS-11952

Emulator occasionally hangs indefinitely on startup, unable to connect adb

I extended my patch series to capture logcat output irrespective of whether boot completes or not. The change was quite simple although I did have to put a short delay in to allow the logcat output to be captured before the emulator was killed after a failed boot.

A test build can be downloaded from
android-emulator-2.12-SNAPSHOT.hpi

Pull request at
https://github.com/jenkinsci/android-emulator-plugin/pull/39

Note the pull request still contains the devices -l output. For now I think that will be useful in diagnosing the various causes of boot failures that may be out there. I'm not sure whether it just makes the logs too messy to be included long term.

I'm also considering getting rid of the connect and disconnect operations. I don't think they add anything to the robustness of startup now we are using the emulator- style device name.

[JIRA] [role-strategy] (JENKINS-19934) Add "Job Create" permission to project roles

2014-08-21 Thread o.v.nenas...@gmail.com (JIRA)















































Oleg Nenashev
 commented on  JENKINS-19934


Add "Job Create" permission to project roles















What Jenkins Core version do you use?



























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-24372) Test runner should be able to specify the local *.hpi file to put into the test environment















































SCM/JIRA link daemon
 commented on  JENKINS-24372


Test runner should be able to specify the local *.hpi file to put into the test environment















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 src/main/java/org/jenkinsci/test/acceptance/guice/LocalPluginOverride.java
 src/main/java/org/jenkinsci/test/acceptance/junit/WithPlugins.java
http://jenkins-ci.org/commit/acceptance-test-harness/aadc0f80798d6b983f056e0c7200daf01637ae5f
Log:
  [FIXED JENKINS-24372]

Allow test runner to override plugin installation from udpate center by
a local file. Useful for testing unreleased plugins





























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







-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [acceptance-test-harness] (JENKINS-24372) Test runner should be able to specify the local *.hpi file to put into the test environment