date:20140303















































Mark Waite
 commented on  JENKINS-18951


Problems with too long paths 















I think that the git command line executable has the limitation, not the git-client-plugin.

You might try adding the JGit implementation to your Jenkins global configuration, then reconfigure the job to use JGit.  It is possible that JGit does not have the same problem as command line git.



























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







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

[JIRA] [git] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552















































Mark Waite
 updated  JENKINS-21954


Jenkins can not enter Jobs api page with latest version 1.552
















Change By:


Mark Waite
(03/Mar/14 1:01 PM)




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

[JIRA] [git] (JENKINS-21954) Jenkins can not enter Job's api page with latest version 1.552















































Mark Waite
 commented on  JENKINS-21954


Jenkins can not enter Jobs api page with latest version 1.552















The problem is fixed in the git-plugin source code and will be available in the next release after 2.0.3.



























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







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

[JIRA] [git] (JENKINS-22012) java.io.IOException: Failed to write timestamp when accessing REST API
















































Mark Waite
 resolved  JENKINS-22012 as Duplicate


java.io.IOException: Failed to write timestamp when accessing REST API
















Fixed in git-plugin source code, will be available in next release after 2.0.3.





Change By:


Mark Waite
(03/Mar/14 1:06 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/groups/opt_out.

[JIRA] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8

2014-03-03 Thread thomas.ru...@steria-mummert.de (JIRA)















































Thomas Runge
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















+1



























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







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

[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders
















































Walter Kacynski
 assigned  JENKINS-22002 to ikedam



Copy Artifact doesnt support jobs in different Folders
















I think I have all the information attached that you asked for.  The problem seems to occurs when we use a job build variable to find the source project to copy from.  If we use a hard-coded job path everything works fine.





Change By:


Walter Kacynski
(03/Mar/14 1:43 PM)




Assignee:


ikedam



























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







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

[JIRA] [copyartifact] (JENKINS-22002) Copy Artifact doesn't support jobs in different Folders















































Walter Kacynski
 updated  JENKINS-22002


Copy Artifact doesnt support jobs in different Folders
















Change By:


Walter Kacynski
(03/Mar/14 1:42 PM)




Attachment:


downstream-config.xml





Attachment:


OutputWithBuildVariable.png





Attachment:


OutputWithHardcodedJob.png





Attachment:


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

[JIRA] [git] (JENKINS-20818) git plugin 2.0 started giving error to connect git over https
















































Mark Waite
 closed  JENKINS-20818 as Cannot Reproduce


git plugin 2.0 started giving error to connect git over https
















Change By:


Mark Waite
(03/Mar/14 1:58 PM)




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







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

[JIRA] [git] (JENKINS-20818) git plugin 2.0 started giving error to connect git over https
















































Mark Waite
 resolved  JENKINS-20818 as Cannot Reproduce


git plugin 2.0 started giving error to connect git over https
















Based on no response from the submitter, and responses from others that these types of errors are significantly reduced in git-client-plugin 1.6.2 (and later) and git-plugin 2.0.1 (and later), I'm closing this as "cannot reproduce".





Change By:


Mark Waite
(03/Mar/14 1:58 PM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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







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

[JIRA] [dashboard-view] (JENKINS-22016) TAP test results of matrix configuration project do not show in main project overview and dashboard

2014-03-03 Thread kabelfrick...@gmail.com (JIRA)

Stefan Nuernberger
created JENKINS-22016

TAP test results of matrix configuration project do not show in main project overview and dashboard

Issue Type:

Bug

Affects Versions:

current

Assignee:

Peter Hayes

Components:

dashboard-view, tap

Created:

03/Mar/14 2:01 PM

Description:

I use the TAP Plugin to publish test results of a matrix configuration project. To see the results I have to select the project, then a specific build with test results and there I can access the extended TAP information.

I can access basic test results through the "test results" link beneath the projects configuration matrix. But "TAP Extended Test Results" says "No TAP Results available, yet." This is only available when choosing a specific build.

What is worse, the dashboard view test statistics do not pick up the test results from the project. The number of tests run is shown correctly in the "Test Trend Chart", but "Test Statistics Chart" and "Test Statictics Grid" do not pick up any results (0 tests / no data available).

I believe the TAP Plugin does not correctly publish results to the master project but only to the single configurations? A similar issue is reported in JENKINS-12205, although it is about xunit and not TAP.

Please check the interaction of the TAP Plugin and matrix configuration projects.

Environment:

Debian Linux Wheezy

Jenkins 1.552

TAP Plugin 1.17

Dashboard View 2.9.2

Project:

Jenkins

Labels:

tap
tapResults
dashboard
matrix
testreport

Priority:

Major

Reporter:

Stefan Nuernberger

[JIRA] [core] (JENKINS-11989) Build history time line chart doesn't render in Internet Explorer 8.0.6001

2014-03-03 Thread monc...@raytheon.com (JIRA)















































Greg Moncreaff
 commented on  JENKINS-11989


Build history time line chart doesnt render in Internet Explorer 8.0.6001















Not a problem with IE 8.0.7601.17514 and Jenkins ver. 1.552



























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







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

[JIRA] [junit] (JENKINS-21347) Jenkins failes with Incorrect XML attributes for test results

2014-03-03 Thread toom...@java.net (JIRA)















































toomasr
 commented on  JENKINS-21347


Jenkins failes with Incorrect XML attributes for test results















Also experiencing this on Jenkins ver 1.532.1



























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







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

[JIRA] [teamconcert] (JENKINS-21933) PermGen leaks

2014-03-03 Thread docw...@gerf.org (JIRA)















































Christian Höltje
 commented on  JENKINS-21933


PermGen leaks















So I was wrong about using the IBM JRE  It eventually filled up the heap and started thrashing.  I didn't get OOM errors, but performance went into the toilet.   I had 2g of heap and it filled it up. 

I'll email the PHD to Heather directly.



























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







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

[JIRA] [mailer] (JENKINS-19194) Recipients not being saved

2014-03-03 Thread abbybader+c...@gmail.com (JIRA)















































A Bader
 commented on  JENKINS-19194


Recipients not being saved















Any insight on the latter problem?  I'm fine using a free-style build job, but the email notification post-action is definitely not working.  Should I open a new issue?  Any output that I can capture that's useful to you?



























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







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

[JIRA] [mailer] (JENKINS-19194) Recipients not being saved

2014-03-03 Thread abbybader+c...@gmail.com (JIRA)















































A Bader
 commented on  JENKINS-19194


Recipients not being saved















Sure. It's not very interesting.   Pulling from {jenkins home}/jobs/{job}/{build}/log.  It's a test job that fails due to an "exit 1" in an ssh session, designed just to trigger a mail.

Started by user ...=anonymous
Building in workspace .../test email plugin/workspace
workspace $ /bin/sh -xe /tmp/hudson1200283283488152363.sh
+ exit 1
Build step 'Execute shell' marked build as failure
Sending e-mails to: m...@email.com
Finished: FAILURE

There aren't any stack traces in my system logs during the corresponding period.. no real mention of emails at all, in fact.

If you meant another log, please direct me.



























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







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

[JIRA] [mailer] (JENKINS-19194) Recipients not being saved

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















































Alex Earl
 commented on  JENKINS-19194


Recipients not being saved















Did you try sending a test email in the global config area? Also, did you check your spam folder for the emails? If you have the ability, you can add a system property to the Jenkins command line to enable debug in JavaMail as well. 

-Dmail.debug=true



























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







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

[JIRA] [git-client] (JENKINS-22017) Git client: NoClassDefFoundError

2014-03-03 Thread martijn.po...@ga.amgate.com (JIRA)















































Martijn Polak
 created  JENKINS-22017


Git client: NoClassDefFoundError















Issue Type:


Bug



Affects Versions:


current



Assignee:


Nicolas De Loof



Components:


git-client



Created:


03/Mar/14 4:49 PM



Description:


I have a similar issue as JENKINS-21745: whenever I type anything in the Git repository URL in the configuration page I get a NoClassDefFoundError (see top of dump below).

Contrary to the other issue I do have the Credentials plugin enabled and up to date. Here are my versions:

Jenkins: 1.553
GIT client plugin: 1.6.3
Git plugin: 2.0.3
Credentials plugin: 1.10

I've tried enabling and disabling other plugins, restarting, downgrading, upgrading and reinstalling the plugins but to no avail. I have no idea how to get this to work.

Top of dump as follows:

javax.servlet.ServletException: java.lang.NoClassDefFoundError: org.jenkinsci.plugins.gitclient.GitClient
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778)
	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.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 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.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.headerComplete(AbstractHttpConnection.java:949)
	at

[JIRA] [slave-status] (JENKINS-21920) Can't take node offline

2014-03-03 Thread arse...@front.ru (JIRA)















































Arseniy Arseniy
 commented on  JENKINS-21920


Cant take node offline















Yes, the same. Jenkins ver. 1.553



























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







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

[JIRA] [tasks-plugin] (JENKINS-17225) Allow regular expressions as tags

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
















































Ulli Hafner
 assigned  JENKINS-17225 to Ulli Hafner



Allow regular expressions as tags
















Change By:


Ulli Hafner
(03/Mar/14 5:04 PM)




Assignee:


FelixDuerrwanger
UlliHafner



























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







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

[JIRA] [warnings] (JENKINS-17787) Replace Codenarc parser with native parser

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
















































Ulli Hafner
 assigned  JENKINS-17787 to Ulli Hafner



Replace Codenarc parser with native parser
















Change By:


Ulli Hafner
(03/Mar/14 5:05 PM)




Assignee:


FelixDuerrwanger
UlliHafner



























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







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

[JIRA] [mailer] (JENKINS-19194) Recipients not being saved

2014-03-03 Thread abbybader+c...@gmail.com (JIRA)















































A Bader
 commented on  JENKINS-19194


Recipients not being saved















I did try a test email; it claims to have completed correctly, but no emails get delivered to any address I've tried (not even to the spam box). Again, no errors on the system logs.

Re: running from CLI, I've emailed you directly, will post again if I find an answer. Thanks.



























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







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

[JIRA] [jobconfighistory] (JENKINS-14295) WARNING: Called getInputStream after getParameter ... error















































Walter Kacynski
 reopened  JENKINS-14295


WARNING: Called getInputStream after getParameter ... error
















Change By:


Walter Kacynski
(03/Mar/14 5:45 PM)




Resolution:


Incomplete





Status:


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

[JIRA] [core] (JENKINS-14295) WARNING: Called getInputStream after getParameter ... error

2014-03-03 Thread jenkins-ci....@michael-prokop.at (JIRA)















































Walter Kacynski
 updated  JENKINS-14295


WARNING: Called getInputStream after getParameter ... error
















I see these messages associated with the following:
Mar 03, 2014 12:40:43 PM winstone.Logger logInternal
WARNING: Called getInputStream after getParameter ... error

Maybe this is released to the winstone servlet engine?





Change By:


Walter Kacynski
(03/Mar/14 5:46 PM)




Assignee:


WalterKacynski





Component/s:


core





Component/s:


jobconfighistory



























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







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

[JIRA] [rtc] (JENKINS-21964) Build definition and workspace name should accept parameters and/or environment variables.

2014-03-03 Thread griffman...@gmail.com (JIRA)















































James Griffin
 commented on  JENKINS-21964


Build definition and workspace name should accept parameters and/or environment variables.















we are using the build definition and jenkins integration in RTC. we have multiple streams which need to have separate build definitions for each stream. what I am asking is for the build definition field in jenkins to handle parameters so we can use the same jenkins project and choose the stream/build definition on the same project. otherwise we need separate projects for each build definition. 



























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







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

[JIRA] [core] (JENKINS-21999) Computer does not exist returns NPE

2014-03-03 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-21999


Computer does not exist returns NPE















What are the circumstances for this to happen?



























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







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

[JIRA] [core] (JENKINS-12569) Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes

2014-03-03 Thread caleb.t...@gmail.com (JIRA)















































Caleb Tote
 commented on  JENKINS-12569


Jenkins swap monitoring is running although swap monitoring is disbaled for all the nodes















We too are seeing this issue; as well as the issue referenced by Pavel.



























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







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

[JIRA] [core] (JENKINS-17051) Inconsistent latest build

2014-03-03 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-17051


Inconsistent latest build















Is it reproduced with a recent Jenkins version?



























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







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

[JIRA] [core] (JENKINS-17044) all master executors died

2014-03-03 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-17044


all master executors died















Is it reproduced with a recent Jenkins version?



























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







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

[JIRA] [s3] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)

2014-03-03 Thread tswee...@omnifone.com (JIRA)















































Tony Sweeney
 commented on  JENKINS-19725


Unable to unmarshall response (Couldnt initialize a SAX driver to create an XMLReader)















Also an issue for us with Jenkins 1.543 and Jekins S3 plugin version 0.5; seems to be a regression, as we definitely had this working before the last upgrade.



























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







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

[JIRA] [s3] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)

2014-03-03 Thread tswee...@omnifone.com (JIRA)













































 
Tony Sweeney
 edited a comment on  JENKINS-19725


Unable to unmarshall response (Couldnt initialize a SAX driver to create an XMLReader)
















Also an issue for us with Jenkins 1.543 and Jenkins S3 plugin version 0.5; seems to be a regression, as we definitely had this working before the last upgrade.



























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







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

[JIRA] [jacoco] (JENKINS-22018) Support for ratcheting of minimum thresholds in Jacoco coverage

2014-03-03 Thread chris.a.willi...@gmail.com (JIRA)















































Chris Williams
 created  JENKINS-22018


Support for ratcheting of minimum thresholds in Jacoco coverage















Issue Type:


New Feature



Assignee:


Ognjen Bubalo



Components:


jacoco



Created:


03/Mar/14 6:52 PM



Description:


The addition of an option to "ratchet" or update the minimum thresholds for build failure would be very useful. This request is inspired by and heavily related to JENKINS-8326 for the Cobertura coverage plugin.

Ideally we'd be able to set the publisher to automatically update the minimum thresholds to higher values when a project's observed value is higher than a previously set minimum. This enables a project to help enforce that code coverage cannot decrease over time as a code quality standard.




Project:


Jenkins



Priority:


Major



Reporter:


Chris Williams

























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







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

[JIRA] [s3] (JENKINS-19725) Unable to unmarshall response (Couldn't initialize a SAX driver to create an XMLReader)

2014-03-03 Thread tswee...@omnifone.com (JIRA)













































 
Tony Sweeney
 edited a comment on  JENKINS-19725


Unable to unmarshall response (Couldnt initialize a SAX driver to create an XMLReader)
















Also an issue for us with Jenkins 1.543 and Jenkins S3 plugin version 0.5; seems to be a regression, as we definitely had this working before the last upgrade.  Previous version was 1.521 and Jenkins S3 0.4; Not 100% this was working with that combo, I just know that it worked in the past.



























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







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

[JIRA] [core] (JENKINS-17044) all master executors died

2014-03-03 Thread rsi...@gracenote.com (JIRA)















































robsimon
 commented on  JENKINS-17044


all master executors died















haven't seen it for a while. what i noticed with 1.552 is that when an executor dies that shortly after this executor seems to recover. but i had no time to look into the logs to see what happened at this point in time.



























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







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

[JIRA] [jacoco] (JENKINS-22018) Support for ratcheting of minimum thresholds in Jacoco coverage

2014-03-03 Thread chris.a.willi...@gmail.com (JIRA)















































Chris Williams
 commented on  JENKINS-22018


Support for ratcheting of minimum thresholds in Jacoco coverage















Because I've had to work around this myself in the meantime, I use the following groovy postbuild script to achieve this:

Unable to find source-code formatter for language: groovy. Available languages are: _javascript_, sql, xhtml, actionscript, none, html, xml, java// Grab the API for Jacoco
def b = manager.build;

def action = "" { it.getUrlName() == "jacoco" }
if (action == null) {
	// no Jacoco coverage, so nothing to do!
	manager.listener.logger.println "Unable to get Jacoco Build Action on build, so bailing out"
	return;
}

def publishers = b.getProject().publishersList;
def jacocoPublisher = publishers.find { it.getDescriptor().getId() == "hudson.plugins.jacoco.JacocoPublisher" }

// Collect the current "observed" values for coverage
def line = action.getLineCoverage();
def clazz = action.getClassCoverage();
def method = action.getMethodCoverage();
def instruction = action.getInstructionCoverage();
def branch = action.getBranchCoverage();
//def complexity = action.getComplexityScore();

// Now let's set the new threshold minimums to last value!
// Only set these values if the observed percent is _higher_ than the existing minimum threshold!
def thresholds = action.getThresholds();

// Classes
int percent = clazz.getPercentage();
manager.listener.logger.println "Observed class coverage: ${percent}%"
if (percent  thresholds.getMinClass()) {
	manager.listener.logger.println "Increasing minimum threshold to observed value for class coverage"
	thresholds.setMinClass(percent);
}
// methods
percent = method.getPercentage();
manager.listener.logger.println "Observed methods coverage: ${percent}%"
if (percent  thresholds.getMinMethod()) {
	manager.listener.logger.println "Increasing minimum threshold to observed value for methods coverage"
	thresholds.setMinMethod(percent);
}
// Branches
percent = branch.getPercentage();
manager.listener.logger.println "Observed branches coverage: ${percent}%"
if (percent  thresholds.getMinBranch()) {
	manager.listener.logger.println "Increasing minimum threshold to observed value for branches coverage"
	thresholds.setMinBranch(percent);
}
// Lines
percent = line.getPercentage();
manager.listener.logger.println "Observed lines coverage: ${percent}%"
if (percent  thresholds.getMinLine()) {
	manager.listener.logger.println "Increasing minimum threshold to observed value for lines coverage"
	thresholds.setMinLine(percent);
}
// Instructions
percent = instruction.getPercentage();
manager.listener.logger.println "Observed instruction coverage: ${percent}%"
if (percent  thresholds.getMinInstruction()) {
	manager.listener.logger.println "Increasing minimum threshold to observed value for instruction coverage"
	thresholds.setMinInstruction(percent);
}
// Complexity
//percent = complexity.getPercentage();
//if (percent  thresholds.getMinComplexity()) {
//	thresholds.setMinComplexity(percent);
//}

// We need to replace the publisher with a new instance that has updated minimums
// HACK to work around bug in plugin where we don't have access to plugin classes.
def c = Class.forName("hudson.plugins.jacoco.JacocoPublisher", true, manager.hudson.getPluginManager().uberClassLoader)
def constructor = c.getConstructor( [ String, String, String, String, String, String, String, String, String, String, String, String, String, String, String, String, String, boolean ] as Class[] )
// make a new version of the coverage publisher with updated minimums
def newPub = constructor.newInstance(jacocoPublisher.getExecPattern(), jacocoPublisher.getClassPattern(), jacocoPublisher.getSourcePattern(),
 jacocoPublisher.getInclusionPattern(), jacocoPublisher.getExclusionPattern(), jacocoPublisher.getMaximumInstructionCoverage(),
 jacocoPublisher.getMaximumBranchCoverage(), jacocoPublisher.getMaximumComplexityCoverage(), jacocoPublisher.getMaximumLineCoverage(),
 jacocoPublisher.getMaximumMethodCoverage(), jacocoPublisher.getMaximumClassCoverage(), Integer.toString(thresholds.getMinInstruction()), Integer.toString(thresholds.getMinBranch()),
 Integer.toString(thresholds.getMinComplexity()), Integer.toString(thresholds.getMinLine()), Integer.toString(thresholds.getMinMethod()), Integer.toString(thresholds.getMinClass()),
 jacocoPublisher.isChangeBuildStatus())
// Now remove the old version and replace with the new publisher with updated minimums
publishers.replace(jacocoPublisher, newPub); // remove old

[JIRA] [slave-status] (JENKINS-22019) Builders with full disks not being pulled out of rotation

2014-03-03 Thread jos...@azariah.com (JIRA)















































Joshua Kugler
 created  JENKINS-22019


Builders with full disks not being pulled out of rotation















Issue Type:


Bug



Assignee:


Unassigned


Components:


slave-status



Created:


03/Mar/14 7:35 PM



Description:


We recently had a builder fill its disk due to a large build. However, Jenkins did not pull it out of rotation, and it subsequently caused build after build to fail due to the full disk.

Is this expected? I have seen Jenkins pull other builders due to full disks before, and could not find an option to disable or enable this behavior.




Project:


Jenkins



Priority:


Minor



Reporter:


Joshua Kugler

























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







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

[JIRA] [job-dsl-plugin] (JENKINS-22020) Different Maven Installations are not supported

2014-03-03 Thread jenk...@soebes.de (JIRA)















































Karl-Heinz Marbaise
 created  JENKINS-22020


Different Maven Installations are not supported















Issue Type:


Improvement



Affects Versions:


current



Assignee:


Justin Ryan



Components:


job-dsl-plugin



Created:


03/Mar/14 7:39 PM



Description:


Currently the job dsl supports the following:

job {
  name '...'

  steps {
maven {
  goals("-B clean package")
  ...
}
  }
}


But it would be nice having support for different maven installation like this:


job {
  name '...'

  steps {

maven {
  mavenName("Maven 2.0.11")
  goals("-B clean package")
}
maven {
  mavenName("Maven 3.0.5")
  goals("-B clean package")
}
...
  }
}

But currently the code has hard coded the maveName with "default" which prevents any job configuration like the above.




Project:


Jenkins



Priority:


Major



Reporter:


Karl-Heinz Marbaise

























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







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

[JIRA] [core] (JENKINS-11989) Build history time line chart doesn't render in Internet Explorer 8.0.6001

2014-03-03 Thread ever...@free.fr (JIRA)
















































evernat
 resolved  JENKINS-11989 as Cannot Reproduce


Build history time line chart doesnt render in Internet Explorer 8.0.6001
















thanks, resolving as can not reproduced.





Change By:


evernat
(03/Mar/14 8:04 PM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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







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

[JIRA] [appaloosa] (JENKINS-22021) Make workspace archive validation at end of job optional.

2014-03-03 Thread msla...@gmail.com (JIRA)















































Mike Slaven
 created  JENKINS-22021


Make workspace archive validation at end of job optional.















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


appaloosa



Created:


03/Mar/14 8:31 PM



Description:


When a job is finished, the appaloosa plugin checks to ensure a .ipa/.apk file exists in the folders you indicated in your post-build step.

This is fine, except when you use a promotion plugin so that the promotion happens in it's own pre-built environment.

Please make this check optional at the end of the job.




Environment:


OSX 10.9.1




Project:


Jenkins



Priority:


Major



Reporter:


Mike Slaven

























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







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

[JIRA] [appaloosa] (JENKINS-22023) Allow builds with the same version number to be uploaded (perhaps a server side option per app)

2014-03-03 Thread msla...@gmail.com (JIRA)















































Mike Slaven
 created  JENKINS-22023


Allow builds with the same version number to be uploaded (perhaps a server side option per app)















Issue Type:


Bug



Assignee:


Unassigned


Components:


appaloosa



Created:


03/Mar/14 8:38 PM



Description:


Allow a build with the same version number to be uploaded on top of itself, replacing the current version. This would be very handy when other identifiers are used to identify the codebase an installer came from (a perforce changelist number for example)




Environment:


OSX 10.9.1




Project:


Jenkins



Priority:


Major



Reporter:


Mike Slaven

























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







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

[JIRA] [core] (JENKINS-21989) ReverseProxySetupMonitor broken in Jenkins release 1.552















































Michael Prokop
 commented on  JENKINS-21989


ReverseProxySetupMonitor broken in Jenkins release 1.552















Same here with Jenkins 1.552 and 1.553 + nginx, seems to be related to https://github.com/jenkinsci/jenkins/commit/724f9e0dfc2011d4c12e867bd85bc3f32c2b0513



























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







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

[JIRA] [core] (JENKINS-22024) Windows services shows Jenkins as not running.. but it is.

2014-03-03 Thread mlandma...@gmail.com (JIRA)

boris ivan
created JENKINS-22024

Windows services shows Jenkins as not running.. but it is.

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

core

Created:

03/Mar/14 8:47 PM

Description:

My Jenkins webserver is running on a Windows 2012 VM. It's been working fine and is still running fine after upgrading from 1.552 to 1.553. But after upgrading to 1.553, the 'services' tool in Windows tells me that Jenkins is not running. But it is running it's running fine. I can refresh webpages, launch jobs, etc, from web browsers.

But for the "Jenkins" service, the status is blank, where normally it would say: "running". I've closed the tool and relaunched it, hit F5 to refresh, etc. Jenkins is working fine, but the service tool from Microsoft doesn't say it's running.

This worked in 1.552.

Environment:

Windows 2012, Jenkins 1.553, Java 1.7.0-45

Project:

Jenkins

Priority:

Major

Reporter:

boris ivan

[JIRA] [job-dsl-plugin] (JENKINS-22020) Different Maven Installations are not supported

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
















































Daniel Spilker
 resolved  JENKINS-22020 as Fixed


Different Maven Installations are not supported
















This has been released with version 1.20. The option is called mavenInstallation. See https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-reference#wiki-maven-1 for details.





Change By:


Daniel Spilker
(03/Mar/14 9:15 PM)




Status:


Open
Resolved





Assignee:


JustinRyan
DanielSpilker





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

[JIRA] [vsphere-cloud] (JENKINS-22025) VM cannot be started repeatedly with vSphere plugin

2014-03-03 Thread bhave...@gmail.com (JIRA)

Bryan Havenstein
created JENKINS-22025

VM cannot be started repeatedly with vSphere plugin

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Components:

vsphere-cloud

Created:

03/Mar/14 9:29 PM

Description:

I've been using the vSphere plugin for 6 months or so successfully.

A couple of weeks ago, it started failing builds with "VM cannot be started" errors. It seems to happen about 50% of the time and could fail twice and then work fine a couple of minutes later.

Procedure for this particular job is to revert the VM to snapshot, then power off, then power on.

The ESXI host shows no issues. The event log shows the VM being started fine and it comes up working fine despite Jenkins declaring it failed.

Timeout is set to 600 sec, but the failures happen after ~1.5 min. A normal run takes about 2.5 min for the IP to become available, so the fail is triggered before the IP would normally be there.

Is there any debug log I could look into or is this a known issue?

Log:

vSphere
vSphere Performing vSphere build step: "Power-On/Resume VM"
vSphere Attempting to use server configuration: "sandbox"
vSphere Waiting for IP (VM may be restarted during this time)
vSphere vSphere Error: VM cannot be started
Build step 'vSphere Build Step' marked build as failure
Email was triggered for: Failure

Environment:

Jenkins master on RedHat

vSphere plugin used w/ ESXI host

Project:

Jenkins

Priority:

Major

Reporter:

Bryan Havenstein

[JIRA] [job-dsl-plugin] (JENKINS-22020) Different Maven Installations are not supported

2014-03-03 Thread jenk...@soebes.de (JIRA)















































Karl-Heinz Marbaise
 commented on  JENKINS-22020


Different Maven Installations are not supported















Hi Daniel, may be i misunderstand a thingif i do the job creationg like this:

job {
name 'DSL-maven-job'
jdk("JDK-1.7-u40")
scm {
git('g...@github.com:khmarbaise/artifactor-maven-plugin.git')
}
triggers {
scm('H/15 * * * *')
}
  steps {
maven {
mavenInstallation("Maven 3.0.5")
goals("-B -Prun-its clean verify")
localRepository(LocalToWorkspace)
}
maven {
mavenInstallation("Maven 3.1.1")
goals("-B -Prun-its clean verify")
localRepository(LocalToWorkspace)
}
  }
}

it works as expected but if i change the code to the following:

def existingMavenInstallations = [ "Maven 3.0.5", "Maven 3.1.1" ]
job {
name 'DSL-maven-job'
jdk("JDK-1.7-u40")
scm {
git('g...@github.com:khmarbaise/artifactor-maven-plugin.git')
}
triggers {
scm('H/15 * * * *')
}
steps {
  existingMavenInstallations.each {
  maven {
  mavenInstallation(it)
  goals("-B -Prun-its clean verify")
  localRepository(LocalToWorkspace)
 }
  }
}
}

it might be a Groovy problem on my site ?



























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







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

[JIRA] [core] (JENKINS-21605) Logging all UpstreamCause's floods Jenkins in large setups

2014-03-03 Thread dtho...@willowgarage.com (JIRA)















































Dirk Thomas
 updated  JENKINS-21605


Logging all UpstreamCauses floods Jenkins in large setups
















Change By:


Dirk Thomas
(03/Mar/14 10:08 PM)




URL:


http://jenkins.ros.org/job/ros-hydro-
metapackages_binarydeb_raring_i386
metapackages_binarydeb_precise_amd64
/
702
813
/
console



























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







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

[JIRA] [core] (JENKINS-21605) Logging all UpstreamCause's floods Jenkins in large setups

2014-03-03 Thread dtho...@willowgarage.com (JIRA)















































Dirk Thomas
 commented on  JENKINS-21605


Logging all UpstreamCauses floods Jenkins in large setups















Is there any chance this critical regression will be addressed? This makes Jenkins basically unusable in large setups. And going back to a one year old release where the problem was addressed is not really an option with the latest security fixes.



























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







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

[JIRA] [build-failure-analyzer] (JENKINS-22026) Propagate failure causes from downstream builds

2014-03-03 Thread aba...@java.net (JIRA)

abayer
created JENKINS-22026

Propagate failure causes from downstream builds

Issue Type:

Improvement

Assignee:

Tomas Westling

Components:

build-failure-analyzer

Created:

03/Mar/14 10:45 PM

Description:

This would be nice to have - I've got a fairly complex multi-level build setup, with a group of "generic" jobs for each platform we build on. Those generic jobs are then called by each of our 20+ component builds, passing certain information (i.e., what to build, where to find source packages) to the generic jobs as parameters.

When the generic jobs (i.e., the downstream builds) fail, they get the appropriate known cause associated with them, but the parent build doesn't, since it doesn't actually have the cause of the downstream failure in its log. It'd be handy if we could propagate failure causes up the stack from the downstream builds to their upstream builds - it'd make analysis much simpler.

Project:

Jenkins

Priority:

Major

Reporter:

abayer

[JIRA] [build-timeout] (JENKINS-21919) Extension point to define timeout action















































SCM/JIRA link daemon
 commented on  JENKINS-21919


Extension point to define timeout action















Code changed in jenkins
User: ikedam
Path:
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/config.jelly
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help.html
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help_ja.html
http://jenkins-ci.org/commit/build-timeout-plugin/dd5967987f57229afe1d870e4651f0464bae7a6a
Log:
  JENKINS-21919 Some fixes for views: changed the entry order from actions, strategy to strategy, actions/open a new window for the link to the build configuration page.





























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







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

[JIRA] [build-timeout] (JENKINS-21919) Extension point to define timeout action















































SCM/JIRA link daemon
 commented on  JENKINS-21919


Extension point to define timeout action















Code changed in jenkins
User: ikedam
Path:
 src/main/java/hudson/plugins/build_timeout/BuildTimeOutOperation.java
 src/main/java/hudson/plugins/build_timeout/BuildTimeOutOperationDescriptor.java
 src/main/java/hudson/plugins/build_timeout/BuildTimeoutWrapper.java
 src/main/java/hudson/plugins/build_timeout/operations/AbortOperation.java
 src/main/java/hudson/plugins/build_timeout/operations/FailOperation.java
 src/main/java/hudson/plugins/build_timeout/operations/WriteDescriptionOperation.java
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/config.jelly
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/config_ja.properties
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-failBuild.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-failBuild_ja.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-operationList.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-operationList_ja.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-writingDescription.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-writingDescription_ja.html
 src/main/resources/hudson/plugins/build_timeout/operations/AbortOperation/help.html
 src/main/resources/hudson/plugins/build_timeout/operations/AbortOperation/help_ja.html
 src/main/resources/hudson/plugins/build_timeout/operations/FailOperation/help.html
 src/main/resources/hudson/plugins/build_timeout/operations/FailOperation/help_ja.html
 src/main/resources/hudson/plugins/build_timeout/operations/Messages.properties
 src/main/resources/hudson/plugins/build_timeout/operations/Messages_ja.properties
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/config.jelly
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/config_ja.properties
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help-description.html
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help-description_ja.html
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help.html
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help_ja.html
http://jenkins-ci.org/commit/build-timeout-plugin/915c8bf0b2e1b27c483f7afdcd70dd16ebf856d1
Log:
  FIXED JENKINS-21919 Generalize actions performed in timeout with an extension point.





























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







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

[JIRA] [build-timeout] (JENKINS-21919) Extension point to define timeout action















































SCM/JIRA link daemon
 commented on  JENKINS-21919


Extension point to define timeout action















Code changed in jenkins
User: ikedam
Path:
 src/main/java/hudson/plugins/build_timeout/BuildTimeOutOperation.java
 src/main/java/hudson/plugins/build_timeout/BuildTimeOutOperationDescriptor.java
 src/main/java/hudson/plugins/build_timeout/BuildTimeoutWrapper.java
 src/main/java/hudson/plugins/build_timeout/operations/AbortOperation.java
 src/main/java/hudson/plugins/build_timeout/operations/FailOperation.java
 src/main/java/hudson/plugins/build_timeout/operations/WriteDescriptionOperation.java
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/config.jelly
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/config_ja.properties
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-failBuild.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-failBuild_ja.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-operationList.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-operationList_ja.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-writingDescription.html
 src/main/resources/hudson/plugins/build_timeout/BuildTimeoutWrapper/help-writingDescription_ja.html
 src/main/resources/hudson/plugins/build_timeout/operations/AbortOperation/help.html
 src/main/resources/hudson/plugins/build_timeout/operations/AbortOperation/help_ja.html
 src/main/resources/hudson/plugins/build_timeout/operations/FailOperation/help.html
 src/main/resources/hudson/plugins/build_timeout/operations/FailOperation/help_ja.html
 src/main/resources/hudson/plugins/build_timeout/operations/Messages.properties
 src/main/resources/hudson/plugins/build_timeout/operations/Messages_ja.properties
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/config.jelly
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/config_ja.properties
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help-description.html
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help-description_ja.html
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help.html
 src/main/resources/hudson/plugins/build_timeout/operations/WriteDescriptionOperation/help_ja.html
 src/test/java/hudson/plugins/build_timeout/BuildTimeoutWrapperIntegrationTest.java
 src/test/java/hudson/plugins/build_timeout/QuickBuildTimeOutStrategy.java
 src/test/java/hudson/plugins/build_timeout/operations/WriteDescriptionOperationTest.java
http://jenkins-ci.org/commit/build-timeout-plugin/651b539f789859e8ab90322f5315b8cddb89ec7d
Log:
  Merge pull request #18 from ikedam/feature/JENKINS-21919_TimeoutAction

JENKINS-21919 Extension point to define actions when timeout


Compare: https://github.com/jenkinsci/build-timeout-plugin/compare/f38708f00f49...651b539f7898




























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







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

[JIRA] [build-timeout] (JENKINS-21919) Extension point to define timeout action















































SCM/JIRA link daemon
 commented on  JENKINS-21919


Extension point to define timeout action















Code changed in jenkins
User: ikedam
Path:
 src/main/java/hudson/plugins/build_timeout/BuildTimeoutWrapper.java
http://jenkins-ci.org/commit/build-timeout-plugin/21db31b8fc7e929e85e3d2132bd2ab77d18418cd
Log:
  JENKINS-21919 transient for unused fields.





























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







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

[JIRA] [build-timeout] (JENKINS-21919) Extension point to define timeout action
















































SCM/JIRA link daemon
 resolved  JENKINS-21919 as Fixed


Extension point to define timeout action
















Change By:


SCM/JIRA link daemon
(03/Mar/14 10:54 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [build-timeout] (JENKINS-21919) Extension point to define timeout action