date:20121206
















































anil kumar
 assigned  JENKINS-16040 to anil kumar



i am unable to sending the mail 
















Change By:


anil kumar
(06/Dec/12 8:51 AM)




Assignee:


anilkumar



























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

[JIRA] (JENKINS-16040) i am unable to sending the mail















































anil kumar
 commented on  JENKINS-16040


i am unable to sending the mail 
















configuration for the gmail SMTP SERVER 
SMTP SERVER NAME  : smtp.gmail.com
Default user e-mail suffix: @gmail.com
Sender E-mail Address : s...@gmail.com
tick the SMTP authentication 
provide the username and password
Port Number   : 587

after i am clicked on the Test Configuration it given following error :
530 5.7.0 Must issue a STARTTLS command first

i am created the JAVA_OPTIONS IN java tab of tomcat properties.


Dmail.smtp.starttls.enable="true"





























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

[JIRA] (JENKINS-16040) i am unable to sending the mail













































 
anil kumar
 edited a comment on  JENKINS-16040


i am unable to sending the mail 
















configuration for the gmail SMTP SERVER 
SMTP SERVER NAME  : smtp.gmail.com
Default user e-mail suffix: @gmail.com
Sender E-mail Address : s...@gmail.com
tick the SMTP authentication 
provide the username and password
Port Number   : 587

after i am clicked on the Test Configuration it given following error :
530 5.7.0 Must issue a STARTTLS command first

i am created the JAVA_OPTIONS IN java tab of tomcat properties.


Dmail.smtp.starttls.enable="true"

after creating the variable restart the tomcat.. it's working for me..





























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

[JIRA] (JENKINS-16040) i am unable to sending the mail
















































anil kumar
 closed  JENKINS-16040 as Duplicate


i am unable to sending the mail 
















issue solved





Change By:


anil kumar
(06/Dec/12 9:00 AM)




Status:


Resolved
Closed



























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

[JIRA] (JENKINS-14247) Master Executor Needed for SCM polling even with slaves

2012-12-06 Thread nicolas.del...@gmail.com (JIRA)















































Nicolas De Loof
 commented on  JENKINS-14247


Master Executor Needed for SCM polling even with slaves















in hudson.plugins.clearcase.ClearCaseSCM.ClearCaseScmDescriptor#getCleartoolExe

Computer.currentComputer() returns null when invoked from createRevisionState and master have no executor set



























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

[JIRA] (JENKINS-16054) Add ability to mute test(s) in the build

2012-12-06 Thread vova.krav...@gmail.com (JIRA)















































Vladimir Kravets
 created  JENKINS-16054


Add ability to mute test(s) in the build















Issue Type:


Improvement



Assignee:


Unassigned


Components:


junit, ui-changes



Created:


06/Dec/12 10:46 AM



Description:


In some cases we has tests which are failed due to defect or environment issue. In this case we need to have ability to ignore such tests during calculating build result.
E.g. We have 100 tests and 1 test is failed due to defect which can be fixed in nearest future but we don't need to have builds unstable to see if another tests will nothing broke. In this case this test marked as "muted test" and we need to see that 99 tests are passed - build is ok and 1 test is muted.

Also need to have ability to unmute tests manually of in automatic way. I see such conditions to unmute tests:

	manually
	at date
	number of build from first failed build (where this test was failed)
	when it's fixed



Similiar functionality already exists in the TeamCity. You can read about this at this link - http://confluence.jetbrains.net/display/TCD7/Muting+Test+Failures




Project:


Jenkins



Labels:


test
junit
usability




Priority:


Major



Reporter:


Vladimir Kravets

























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

[JIRA] (JENKINS-16054) Add ability to mute test(s) in the build

2012-12-06 Thread vova.krav...@gmail.com (JIRA)















































Vladimir Kravets
 commented on  JENKINS-16054


Add ability to mute test(s) in the build















Please be aware that such functionality don't need to change something from source control or source base from which build is building. Thus propose to add @Ignore to test is not good way. =)



























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

[JIRA] (JENKINS-16055) Matrix project with comma in values

2012-12-06 Thread mathieu.pou...@zenika.fr (JIRA)















































Mathieu POUSSE
 created  JENKINS-16055


Matrix project with comma in values















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core, matrix



Created:


06/Dec/12 11:25 AM



Description:


It seems that if the values of an axis in a matrix project contains a comma, jenkins starts failing to execute the job.

I have only one axis {mvnProfile} that contains the values: 
postgresql,build-flex
mysql,build-flex
oracle,build-flex

the command of my maven project is : mvn clean install -P ${mvnProfile}

It works fine when there is only one profile but fails silently with a list separated with comma (I don't have logs to attach as it just says: Job  return with FAILURE).


My understanding of the bug is that the comma is also the separator of axis in jenkins. When we have multiple axis, in the URL, we can see they are comma separated: /myjob/.../axis1=value,axis2=value

I suspect jenkins is interpreting the comma in my parameter value as an axis separator and starts failing.

To be continued...
M.




Environment:


Windows XP 

JAVA 6




Project:


Jenkins



Labels:


jenkins
maven
matrix
axis




Priority:


Major



Reporter:


Mathieu POUSSE

























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

[JIRA] (JENKINS-16055) Matrix project with comma in values

2012-12-06 Thread mathieu.pou...@zenika.fr (JIRA)















































Mathieu POUSSE
 updated  JENKINS-16055


Matrix project with comma in values
















Change By:


Mathieu POUSSE
(06/Dec/12 11:27 AM)




Description:


Itseemsthatifthevaluesofanaxisinamatrixprojectcontainsacomma,jenkinsstartsfailingtoexecutethejob.Ihaveonlyoneaxis{mvnProfile}thatcontainsthevalues:postgresql,build-flexmysql,build-flexoracle,build-flexthecommandofmymavenprojectis:mvncleaninstall-P${mvnProfile}Itworksfinewhenthereisonlyoneprofilebutfailssilentlywithalistseparatedwithcomma
(
.
Idonthavelogstoattachasitjustsays:JobreturnwithFAILURE).
AlsonotethatIhavea404whenIclicktoviewthesubjobexecutiondetails.

---


Myunderstandingofthebugisthatthecommaisalsotheseparatorofaxisinjenkins.Whenwehavemultipleaxis,intheURL,wecanseetheyarecommaseparated:/myjob/.../axis1=value,axis2=valueIsuspectjenkinsisinterpretingthecommainmyparametervalueasanaxisseparatorandstartsfailing.Tobecontinued...M.



























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

[JIRA] (JENKINS-16055) Matrix project with comma in values

2012-12-06 Thread mathieu.pou...@zenika.fr (JIRA)















































Mathieu POUSSE
 updated  JENKINS-16055


Matrix project with comma in values
















Change By:


Mathieu POUSSE
(06/Dec/12 11:37 AM)




Description:


Itseemsthatifthevaluesofanaxisinamatrixprojectcontainsacomma,jenkinsstartsfailingtoexecutethejob.Ihaveonlyoneaxis{mvnProfile}thatcontainsthevalues:postgresql,build-flexmysql,build-flexoracle,build-flexthecommandofmymavenprojectis:mvncleaninstall-P${mvnProfile}Itworksfinewhenthereisonlyoneprofilebutfailssilentlywithalistseparatedwithcomma.Idonthavelogstoattachasitjustsays:JobreturnwithFAILURE).AlsonotethatIhavea404whenIclicktoviewthesubjobexecutiondetails.
Ihavetriedtoquote,escape,urlencodethecommabutitdoesnotsolvetheissue.
---Myunderstandingofthebugisthatthecommaisalsotheseparatorofaxisinjenkins.Whenwehavemultipleaxis,intheURL,wecanseetheyarecommaseparated:/myjob/.../axis1=value,axis2=valueIsuspectjenkinsisinterpretingthecommainmyparametervalueasanaxisseparatorandstartsfailing.Tobecontinued...M.



























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

[JIRA] (JENKINS-16023) Lazy loading causes massive delays after a period of inactivity when loading index page with job listing

2012-12-06 Thread johno.crawf...@gmail.com (JIRA)















































johno
 commented on  JENKINS-16023


Lazy loading causes massive delays after a period of inactivity when loading index page with job listing















I suspect this is actually caused by the massive amount of build history we had for some jobs. After enabling fine logging on hudson.model.RunMap it was obvious which jobs were causing Jenkins to hang. I have now configured discard old builds for the jobs, will report back if it helped or not.



























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

[JIRA] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.

2012-12-06 Thread tomas.westl...@sonymobile.com (JIRA)
















































Tomas Westling
 closed  JENKINS-15948 as Fixed


Analyzer Icons arent displayed if Jenkins isnt installed at root context.
















Fixed in Build Failure Analyzer 1.3.0





Change By:


Tomas Westling
(06/Dec/12 11:55 AM)




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

[JIRA] (JENKINS-15986) Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed

2012-12-06 Thread tomas.westl...@sonymobile.com (JIRA)
















































Tomas Westling
 closed  JENKINS-15986 as Fixed


Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed
















Fixed in Build Failure Analyzer 1.3.0





Change By:


Tomas Westling
(06/Dec/12 11:55 AM)




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

[JIRA] (JENKINS-15926) Build Failure Analyzer with Timestamper output ugly.

2012-12-06 Thread tomas.westl...@sonymobile.com (JIRA)
















































Tomas Westling
 closed  JENKINS-15926 as Fixed


Build Failure Analyzer with Timestamper output ugly.
















Fixed in Build Failure Analyzer 1.3.0





Change By:


Tomas Westling
(06/Dec/12 11:56 AM)




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

[JIRA] (JENKINS-16056) Numbered ports don't check whether the port is actually in use

2012-12-06 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 created  JENKINS-16056


Numbered ports dont check whether the port is actually in use















Issue Type:


Bug



Assignee:


ramapulavarthi



Components:


port-allocator



Created:


06/Dec/12 12:04 PM



Description:


If you create a numbered TCP port (e.g. "9876", as opposed to a named port), then the plugin doesn't appear to actually check whether this port is free on the slave.

i.e. It only checks that no other builds are using the port.

Preferably, as with named ports, the actual availability of the port on the slave should be checked.




Project:


Jenkins



Priority:


Minor



Reporter:


Christopher Orr

























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

[JIRA] (JENKINS-16057) Problems with dual-stack IPv4 / IPv6 machines

2012-12-06 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 created  JENKINS-16057


Problems with dual-stack IPv4 / IPv6 machines















Issue Type:


Bug



Assignee:


Christopher Orr



Components:


port-allocator



Created:


06/Dec/12 12:16 PM



Description:


The plugin was checking whether a named port was free on the build machine, but even when the port was already in use by some daemon, the plugin wrongly reported that the port was available.

The reason appeared to be that our daemon was listening on an IPv4 socket, but the ServerSocket created on the same port by Jenkins defaulted to IPv6, which apparently succeeded.

Switching Jenkins to IPv4 (via java.net.preferIPv4Stack=true) solved the problem.

But it would be nice if Jenkins could handle this situation automatically.

Maybe something like this?  I need to investigate when I get time:

server = new ServerSocket();
server.bind(new InetSocketAddress(InetAddress.getByName("::"), port));






Environment:


Mac OS X 10.8.2 master, no slaves




Project:


Jenkins



Priority:


Minor



Reporter:


Christopher Orr

























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

[JIRA] (JENKINS-10127) M2 Release plugin ignores parameters from a parameterized build

2012-12-06 Thread jsi...@java.net (JIRA)
















































jsirex
 assigned  JENKINS-10127 to jsirex



M2 Release plugin ignores parameters from a parameterized build
















Change By:


jsirex
(06/Dec/12 12:36 PM)




Assignee:


teilo
jsirex



























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

[JIRA] (JENKINS-15986) Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed

2012-12-06 Thread ch...@orr.me.uk (JIRA)















































Christopher Orr
 commented on  JENKINS-15986


Cannot save job configuration pages on Jenkins 1.463 or newer when Build Failure Analyzer installed















Works for me. Thanks!



























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

[JIRA] (JENKINS-15783) email-ext Groovy script does not run when machine shuts down during job

2012-12-06 Thread william.kil...@targetstream.com (JIRA)















































Slide-O-Mix
 commented on  JENKINS-15783


email-ext Groovy script does not run when machine shuts down during job















Please attach a 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

[JIRA] (JENKINS-8226) Add reviewers in gerrit when a build is successful

2012-12-06 Thread rsand...@java.net (JIRA)















































rsandell
 commented on  JENKINS-8226


Add reviewers in gerrit when a build is successful















I did a new release anyways without this feature.
Fingers crossed that it gets into the next one.



























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

[JIRA] (JENKINS-16059) Plugin Management page needs a column for unused plugins to identify for removal

2012-12-06 Thread patmccarth...@gmail.com (JIRA)















































Patrick McCarthy
 created  JENKINS-16059


Plugin Management page needs a column for unused plugins to identify for removal















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


06/Dec/12 3:17 PM



Description:


As a jenkins administrator prior to upgrading jenkins I would like to be able to easily identify which plugins have been installed but are not being used, in order to remove them to keep jenkins instance lean. 




Project:


Jenkins



Priority:


Minor



Reporter:


Patrick McCarthy

























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

[JIRA] (JENKINS-16058) [Email-Ext] Not able to use a parameter that i define in the Job

2012-12-06 Thread dorons...@gmail.com (JIRA)















































Doron Shai
 created  JENKINS-16058


[Email-Ext] Not able to use a parameter that i define in the Job















Issue Type:


Bug



Affects Versions:


current



Assignee:


Slide-O-Mix



Components:


email-ext



Created:


06/Dec/12 3:15 PM



Description:


Hello,

At the end of my Job that I set a post build step that will send a mail.

This mail format is HTML and I am trying to use few variables.

I am able to use Tokens such: $PROJECT_NAME, $BUILD_NUMBER, $BUILD_STATUS but when I want to use a System Variable then i get nothing. (This variable is being set at the beginning of the Job using the "This build is parameterized"

The system Variable name is JobBranch and I already tried to call it in all the ways i know:

${ENV, JobBranch}
${ENV, %JobBranch%}
%JobBranch% 
$JobBranch

for all of these i get nothing (It is actually print this text as it is ...)

What i am doing wrong?

Doron




Environment:


Win Server 2008 R2, Jenkins 1.7




Project:


Jenkins



Labels:


email
email-ext
token




Priority:


Major



Reporter:


Doron Shai

























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

[JIRA] (JENKINS-16058) [Email-Ext] Not able to use a parameter that i define in the Job

2012-12-06 Thread dorons...@gmail.com (JIRA)
















































Doron Shai
 closed  JENKINS-16058 as Not A Defect


[Email-Ext] Not able to use a parameter that i define in the Job
















Managed to find the answer after some more digging in the Net.

the way to use this Token is ${ENV,var="variable_name"}

I found the answer Here





Change By:


Doron Shai
(06/Dec/12 3:25 PM)




Status:


Open
Closed





Fix Version/s:


current





Resolution:


NotADefect



























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

[JIRA] (JENKINS-13587) Buildstep for delay for a minute















































William Kilian
 commented on  JENKINS-13587


Buildstep for delay for a minute















The DSL is groovy code, just do this:


out.println(System.currentTimeMillis())
Thread.sleep(1000)
out.println(System.currentTimeMillis())




























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

[JIRA] (JENKINS-15886) parameterized builds start default ant target in Ant-Task

2012-12-06 Thread cjo9...@java.net (JIRA)















































cjo9900
 commented on  JENKINS-15886


parameterized builds start default ant target in Ant-Task















Pull request submitted
https://github.com/jenkinsci/copyartifact-plugin/pull/13



























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

[JIRA] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException

2012-12-06 Thread robert_lloyd_1...@yahoo.com (JIRA)















































Bob Lloyd
 commented on  JENKINS-14362


100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException















I have the same issue, but cannot track it to a specific job.  I am not generating Performance reports (to my knowledge, unless it's happening w/o my intention).  I've attached my log below (though, it's pretty much the same as above).

This happens for me after about 36 hours of up-time for Jenkins.  I have ~30 jobs running on 6 servers.  One server runs jobs pretty much constantly, while other servers run much less frequently.


"RequestHandlerThread541" daemon prio=6 tid=0x4959d800 nid=0x8c4 runnable 0x4b40f000
   java.lang.Thread.State: RUNNABLE
	at java.util.zip.Deflater.deflateBytes(Native Method)
	at java.util.zip.Deflater.deflate(Unknown Source)

	locked 0x19974c70 (a java.util.zip.ZStreamRef)
	at java.util.zip.DeflaterOutputStream.deflate(Unknown Source)
	at java.util.zip.DeflaterOutputStream.write(Unknown Source)
	at java.util.zip.GZIPOutputStream.write(Unknown Source)
	locked 0x19974c80 (a java.util.zip.GZIPOutputStream)
	at org.kohsuke.stapler.compression.FilterServletOutputStream.write(FilterServletOutputStream.java:31)
	at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source)
	at sun.nio.cs.StreamEncoder.implClose(Unknown Source)
	at sun.nio.cs.StreamEncoder.close(Unknown Source)
	locked 0x19976ce0 (a java.io.OutputStreamWriter)
	at java.io.OutputStreamWriter.close(Unknown Source)
	at java.io.PrintWriter.close(Unknown Source)
	locked 0x19976ce0 (a java.io.OutputStreamWriter)
	at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:53)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
	at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
	at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)



   Locked ownable synchronizers:

	0x19973bf8 (a java.util.concurrent.locks.ReentrantLock$NonfairSync)





























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

[JIRA] (JENKINS-14362) 100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException

2012-12-06 Thread robert_lloyd_1...@yahoo.com (JIRA)













































 
Bob Lloyd
 edited a comment on  JENKINS-14362


100% CPU load during org.kohsuke.stapler.compression.CompressionFilter.reportException
















I have the same issue, but cannot track it to a specific job.  I am not generating Performance reports (to my knowledge, unless it's happening w/o my intention).  I've attached my log below (though, it's pretty much the same as above).  I'm running with Jenkins 1.491 with Sun JDK 1.6.0_26

This happens for me after about 36 hours of up-time for Jenkins.  I have ~30 jobs running on 6 servers.  One server runs jobs pretty much constantly, while other servers run much less frequently.


"RequestHandlerThread541" daemon prio=6 tid=0x4959d800 nid=0x8c4 runnable 0x4b40f000
   java.lang.Thread.State: RUNNABLE
	at java.util.zip.Deflater.deflateBytes(Native Method)
	at java.util.zip.Deflater.deflate(Unknown Source)

	locked 0x19974c70 (a java.util.zip.ZStreamRef)
	at java.util.zip.DeflaterOutputStream.deflate(Unknown Source)
	at java.util.zip.DeflaterOutputStream.write(Unknown Source)
	at java.util.zip.GZIPOutputStream.write(Unknown Source)
	locked 0x19974c80 (a java.util.zip.GZIPOutputStream)
	at org.kohsuke.stapler.compression.FilterServletOutputStream.write(FilterServletOutputStream.java:31)
	at sun.nio.cs.StreamEncoder.writeBytes(Unknown Source)
	at sun.nio.cs.StreamEncoder.implClose(Unknown Source)
	at sun.nio.cs.StreamEncoder.close(Unknown Source)
	locked 0x19976ce0 (a java.io.OutputStreamWriter)
	at java.io.OutputStreamWriter.close(Unknown Source)
	at java.io.PrintWriter.close(Unknown Source)
	locked 0x19976ce0 (a java.io.OutputStreamWriter)
	at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:53)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
	at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
	at winstone.RequestDispatcher.forward(RequestDispatcher.java:331)
	at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:215)
	at winstone.RequestHandlerThread.run(RequestHandlerThread.java:138)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)



   Locked ownable synchronizers:

	0x19973bf8 (a java.util.concurrent.locks.ReentrantLock$NonfairSync)





























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

[JIRA] (JENKINS-15970) JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action

2012-12-06 Thread aba...@java.net (JIRA)















































abayer
 commented on  JENKINS-15970


JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action















Merged - thanks!



























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

[JIRA] (JENKINS-15970) JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action















































SCM/JIRA link daemon
 commented on  JENKINS-15970


JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action















Code changed in jenkins
User: Adam Rofer
Path:
 src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate.java
 src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/config.jelly
 src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/help-spoolDelayMs.html
 src/test/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplateTest.java
http://jenkins-ci.org/commit/jclouds-plugin/e7eb5a32647971ec3cc204100861c43c6bcca0ad
Log:
  Fix for JENKINS-15970: Add forcible synchronized serial delay option





























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

[JIRA] (JENKINS-15970) JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action















































SCM/JIRA link daemon
 commented on  JENKINS-15970


JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action















Code changed in jenkins
User: Andrew Bayer
Path:
 src/main/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate.java
 src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/config.jelly
 src/main/resources/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplate/help-spoolDelayMs.html
 src/test/java/jenkins/plugins/jclouds/compute/JCloudsSlaveTemplateTest.java
http://jenkins-ci.org/commit/jclouds-plugin/42167b274770ba9ba4c4c57105d0c939d76b4d47
Log:
  Merge pull request #35 from adamrofer/JENKINS-15970

Fix for JENKINS-15970: Add forcible synchronized serial delay option


Compare: https://github.com/jenkinsci/jclouds-plugin/compare/67af6abca653...42167b274770




























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

[JIRA] (JENKINS-15970) JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action

2012-12-06 Thread aba...@java.net (JIRA)
















































abayer
 resolved  JENKINS-15970 as Fixed


JClouds plugin: add optional delay between instantiations of Instance Creation Build Environment action
















Will be in next release - probably 2.3.2.





Change By:


abayer
(06/Dec/12 5:03 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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

[JIRA] (JENKINS-15964) All configuration screens are stuck LOADING

2012-12-06 Thread adam.de...@sematree.com (JIRA)















































ada, devoe
 commented on  JENKINS-15964


All configuration screens are stuck LOADING















This is a pain - we're waiting eagerly for a fix or 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

[JIRA] (JENKINS-15126) typo in init.js file for anchor, jelly tag f:section gets an empty line on top of the title because of a typo, semicolon inserted in javascript file: $(e.section).insert({top:















































SCM/JIRA link daemon
 commented on  JENKINS-15126


typo in init.js file for anchor, jelly tag f:section gets an empty line on top of the title because of a typo, semicolon inserted in _javascript_ file: $(e.section).insert({top:a id= + id +  class=section-anchor#;/a});















Code changed in jenkins
User: Seiji Sogabe
Path:
 core/src/main/resources/lib/form/breadcrumb-config-outline/init.js
http://jenkins-ci.org/commit/jenkins/c660ba57bcce24ec322826c3bba67d6a60e25e96
Log:
  Merge pull request #642 from kraai/master

FIXED JENKINS-15126 Remove ";" from closing tag


Compare: https://github.com/jenkinsci/jenkins/compare/b89b4ddedf06...c660ba57bcce




























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

[JIRA] (JENKINS-15126) typo in init.js file for anchor, jelly tag f:section gets an empty line on top of the title because of a typo, semicolon inserted in javascript file: $(e.section).insert({top:















































SCM/JIRA link daemon
 commented on  JENKINS-15126


typo in init.js file for anchor, jelly tag f:section gets an empty line on top of the title because of a typo, semicolon inserted in _javascript_ file: $(e.section).insert({top:a id= + id +  class=section-anchor#;/a});















Code changed in jenkins
User: Matt Kraai
Path:
 core/src/main/resources/lib/form/breadcrumb-config-outline/init.js
http://jenkins-ci.org/commit/jenkins/c6190cb707227255e956cdaaa22da8e311e847e9
Log:
  FIXED JENKINS-15126 Remove ";" from closing 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

[JIRA] (JENKINS-15126) typo in init.js file for anchor, jelly tag f:section gets an empty line on top of the title because of a typo, semicolon inserted in javascript file: $(e.section).insert({top:
















































SCM/JIRA link daemon
 resolved  JENKINS-15126 as Fixed


typo in init.js file for anchor, jelly tag f:section gets an empty line on top of the title because of a typo, semicolon inserted in _javascript_ file: $(e.section).insert({top:a id= + id +  class=section-anchor#;/a});
















Change By:


SCM/JIRA link daemon
(06/Dec/12 5:32 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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

[JIRA] (JENKINS-14625) Exception no page found

2012-12-06 Thread mcroo...@java.net (JIRA)
















































mcrooney
 resolved  JENKINS-14625 as Duplicate


Exception no page found
















This appears to be a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-12967.





Change By:


mcrooney
(06/Dec/12 5:39 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

[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.

2012-12-06 Thread mcroo...@java.net (JIRA)















































mcrooney
 commented on  JENKINS-12967


Cannot view HTML report for a specific build.















Okay, thanks Carsten, I've applied the patch to a fork and submitted a pull request. If the build passes I can merge it in.

Would this patch change any functionality or simply fix the bug? Thanks again for your contribution!



























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

[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.

2012-12-06 Thread mcroo...@java.net (JIRA)















































mcrooney
 commented on  JENKINS-12967


Cannot view HTML report for a specific build.















Actually this patch appears to introduce a syntax error, due to line 108 of fix.patch, the empty "File" line. Let me know if I can just delete that line or if the patch is 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

[JIRA] (JENKINS-15126) typo in init.js file for anchor, jelly tag f:section gets an empty line on top of the title because of a typo, semicolon inserted in javascript file: $(e.section).insert({top:

2012-12-06 Thread dogf...@java.net (JIRA)















































dogfood
 commented on  JENKINS-15126


typo in init.js file for anchor, jelly tag f:section gets an empty line on top of the title because of a typo, semicolon inserted in _javascript_ file: $(e.section).insert({top:a id= + id +  class=section-anchor#;/a});















Integrated in  jenkins_main_trunk #2128
 FIXED JENKINS-15126 Remove ";" from closing tag (Revision c6190cb707227255e956cdaaa22da8e311e847e9)

 Result = SUCCESS
Matt.Kraai : c6190cb707227255e956cdaaa22da8e311e847e9
Files : 

	core/src/main/resources/lib/form/breadcrumb-config-outline/init.js





























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

[JIRA] (JENKINS-15977) java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild

2012-12-06 Thread cjo9...@java.net (JIRA)















































cjo9900
 commented on  JENKINS-15977


java.lang.NoClassDefFoundError: hudson/maven/MavenModuleSetBuild















Do you have the Maven plugin installed/enabled?
As this copy artifact plugin depends on it, during compile time but there is no checking at runtime to see if it is installed before using it.

as indicated in 
https://wiki.jenkins-ci.org/display/JENKINS/Dependencies+among+plugins

so code needs to be added to do the check for the plugin before use

if (Hudson.getInstance().getPlugin("maven-plugin") != null) {
// use classes in the "maven-plugin" 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

[JIRA] (JENKINS-12967) Cannot view HTML report for a specific build.

2012-12-06 Thread carsten.pfeif...@gebit.de (JIRA)















































Carsten Pfeiffer
 commented on  JENKINS-12967


Cannot view HTML report for a specific build.















D'oh, I'm so sorry. The patch contained stuff that was not meant to be in there. It appears as though the Eclipse egit plugin created the patch for the entire project instead of just the single file that I had selected. The patch should be tiny and contain only the change in HtmlPublisherTarget.java (i.e. the new method getOwner()).

The other changes were an attempt to support reports in arbitrary directories, to be specified by an ant pattern. Please disregard that.



























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

[JIRA] (JENKINS-16061) jenkins-slave.xml has lots of issues

2012-12-06 Thread docw...@gerf.org (JIRA)

Christian Höltje
created JENKINS-16061

jenkins-slave.xml has lots of issues

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

core

Created:

06/Dec/12 7:55 PM

Description:

The jenkins-slave.xml file is a great idea, but has some problems:

1. As of 1.467 the jenkins-slave.xml file is overwritten every update; issue #JENKINS-14559

2. The execute node never sets the path to the just installed JDK (e.g. it says javaw.exe instead of c:\jenkins\jdk\bin\javaw.exe). This is problematic on multiple levels since by default c:\windows\syswow64 is not in the PATH and any new version of Java installed outside Jenkins will override the syswow executables.

I'd like to propose that the jenkins-slave.exe stuff works like so:

Add a checksum for the jenkins-slave.xml file (perhaps jenkins-slave.xml.md5)
If the checksums do not match; do not override the jenkins-slave.xml file.
If the checksums match; then overwrite the jenkins-slave.xml file.
When auto-generating the jenkins-slave.xml file, set the execute node to 'path-to-slave-dir\jdk-path\bin\javaw.exe'

This would fix a bunch of issues with getting windows slaves up-and-running. See the wiki (https://wiki.jenkins-ci.org/display/JENKINS/Windows+slaves+fail+to+start+via+DCOM#WindowsslavesfailtostartviaDCOM-Windows64bitinstallationrelatedissues ) for more info about this.

Ciao!

Environment:

Jenkins: 1.480.1

Windows Slaves

Project:

Jenkins

Priority:

Major

Reporter:

Christian Höltje

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

[JIRA] (JENKINS-16062) Batch Tasks invoked by a post-build action use incorrect build/workspace when using concurrent builds

2012-12-06 Thread pixma...@gmail.com (JIRA)















































pixman20
 created  JENKINS-16062


Batch Tasks invoked by a post-build action use incorrect build/workspace when using concurrent builds















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


batch-task



Created:


06/Dec/12 9:11 PM



Description:


When batch tasks get invoked at the completion of a build (that is when the "Invoke batch tasks" post-build action is used), then each batch task uses the latest build rather than the build that invoked the task.

For example, doing the following:
1) Create a project and turn on concurrent building
2) Have the project sleep as part of the main build in order to have multiple builds occur at the same time
3) Add a batch task that echos the workspace and invoke it as a post-build action.
4) Start 2 builds such that the second starts before the first completes

In the console output of Build #1, it will show that it is invoking task 2-1 and Build #2 invokes task 2-2.
Both tasks use Build #2's workspace as denoted by the naming convention 2-#.

The expected behavior is for Build #1 to invoke task 1-1 with Build #1's workspace, and Build #2 to invoke task 2-1 with Builds #2's workspace.

This allows concurrent building to invoke batch tasks such as cleaning a workspace as a post-build action.




Environment:


Windows Server 2003




Project:


Jenkins



Priority:


Major



Reporter:


pixman20

























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

Jenkins soft/symbolic links

2012-12-06 Thread stewart8787

Everyone,
   I am new to Jenkins and am trying to build a software baseline in which
over half of the files are soft linked back to other locations within the
file system.  However, when Jenkins tries to build these soft linked files,
I get the following error:
Error: Expected to find filename at:  (full path of file)

   When I do a 'ls -l full path of file' in a terminal window, the file
exists, but it is linked as follows:
-r-x.. file name - full path to where the file actually exists

How can I get Jenkins to recognize and navigate to the full path to
where the file actually exists using the soft/symbolic link?

Thanks,
Sara




--
View this message in context: 
http://jenkins.361315.n4.nabble.com/Jenkins-soft-symbolic-links-tp4648331.html
Sent from the Jenkins issues mailing list archive at Nabble.com.

[JIRA] (JENKINS-5756) Poll SCM fails with java.lang.AbstractMethodError

2012-12-06 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 commented on  JENKINS-5756


Poll SCM fails with java.lang.AbstractMethodError















Cannot reproduce using your test program in 5u22, 6u37, or 7u9 on Linux—nor in 6u18, your originally reported platform. So are these workarounds still needed?



























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

[JIRA] (JENKINS-10952) Aggregated e-mails for Matrix Projects
















































Slide-O-Mix
 resolved  JENKINS-10952 as Incomplete


Aggregated e-mails for Matrix Projects
















Change By:


Slide-O-Mix
(06/Dec/12 10:04 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

[JIRA] (JENKINS-13848) Option to add full build console log as an attachment















































Slide-O-Mix
 started work on  JENKINS-13848


Option to add full build console log as an attachment
















Change By:


Slide-O-Mix
(06/Dec/12 10:06 PM)




Status:


Open
InProgress



























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

[JIRA] (JENKINS-5949) Trim JUnit stack traces logs to reasonable length before mailing