date:20140214















































Alex Earl
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















Is anyone willing to try a test version based on 2.37.2 to see if the fix I am putting in actually fixes the issue?



























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







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

[JIRA] [git] (JENKINS-21719) Unable to get Branch to build variable to work with wildcard















































Mark Waite
 updated  JENKINS-21719


Unable to get Branch to build variable to work with wildcard
















Change By:


Mark Waite
(14/Feb/14 11:47 AM)




Summary:


UnabletogetBranchtobuildvariabletowork
withwildcard



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)















































Alex Earl
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















http://earl-of-code.com/email-ext-2.37.2.1.hpi is the test 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] [git] (JENKINS-21809) Support for sparse checkout as introduced with Git 1.7.0















































Mark Waite
 commented on  JENKINS-21809


Support for sparse checkout as introduced with Git 1.7.0















Per http://stackoverflow.com/questions/18458608/how-to-do-sparse-checkout-in-git-using-java , JGit does not support sparse checkout.  I reviewed the pre-release source code for JGit 3.3.0 and found no indication of support for sparse checkout.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-21809) Support for sparse checkout as introduced with Git 1.7.0













































 
Mark Waite
 edited a comment on  JENKINS-21809


Support for sparse checkout as introduced with Git 1.7.0
















Per http://stackoverflow.com/questions/18458608/how-to-do-sparse-checkout-in-git-using-java , JGit does not support sparse checkout.  I reviewed the pre-release source code for JGit 3.3.0 and found no indication of support for sparse checkout.

That does not preclude implementing sparse checkout in the plugin for command line git, but it would be another case where the JGit implementation does not match the command line implementation.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-21774) Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit















































Mark Waite
 commented on  JENKINS-21774


Jenkins Git plugin some times shows incorrect and very long changelist (files) in commit 















Can you provide instructions to duplicate the problem?  That seems like the minimum needed to investigate the issue.

Even better, can you submit a pull request with a test which shows the problem?



























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







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

[JIRA] [git] (JENKINS-21001) Git plugin should use git init + git fetch instead of git clone













































 
Mark Waite
 edited a comment on  JENKINS-21001


Git plugin should use git init + git fetch instead of git clone
















The git-client-plugin 1.6.2 (and earlier, I believe) now use init followed by fetch.  Do they resolve this issue?



























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







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

[JIRA] [git] (JENKINS-21001) Git plugin should use git init + git fetch instead of git clone















































Mark Waite
 commented on  JENKINS-21001


Git plugin should use git init + git fetch instead of git clone















The git-client-plugin 1.6.2 (and I earlier, I believe) now use init followed by fetch.  Do they resolve this issue?



























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







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

[JIRA] [git] (JENKINS-20778) git HTTP request failed in Jenkins - not using http proxy
















































Mark Waite
 resolved  JENKINS-20778 as Not A Defect


git HTTP request failed in Jenkins - not using http proxy 
















That message means the computer running the git process (master or slave) could not convert the hostname atlgit-01.us.manh.com into an IP address.  Converting hostname to IP address is a function of a DNS client or of the operating system.  

When computer configuration does not allow hostname to IP address conversion, you can replace the hostname in the URL with the IP address as a work around.  Alternately, you can report the problem to your internal computer support team so that they can fix the problem with the computer configuration.





Change By:


Mark Waite
(14/Feb/14 12:18 PM)




Status:


Open
Resolved





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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-20778) git HTTP request failed in Jenkins - not using http proxy
















































Mark Waite
 closed  JENKINS-20778 as Not A Defect


git HTTP request failed in Jenkins - not using http proxy 
















Change By:


Mark Waite
(14/Feb/14 12:18 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-4418) do shallow clone by default
















































Mark Waite
 closed  JENKINS-4418 as Fixed


do shallow clone by default
















Change By:


Mark Waite
(14/Feb/14 12:26 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-4418) do shallow clone by default
















































Mark Waite
 resolved  JENKINS-4418 as Fixed


do shallow clone by default
















The "shallow clone" checkbox is available under "Advanced clone behaviors" along with the path to the reference repository.

I prefer the path to the reference repository over shallow clone because a reference repository clones very fast and still provides full functionality within the cloned repository.

Neither reference repository nor shallow clone are available with the JGit implementation, but both are available with the command line implementation.





Change By:


Mark Waite
(14/Feb/14 12:26 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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







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

[JIRA] [plot] (JENKINS-21811) Support semicolons as CSV delimiters

2014-02-14 Thread sschube...@gmail.com (JIRA)















































Sebastian Schuberth
 created  JENKINS-21811


Support semicolons as CSV delimiters















Issue Type:


Improvement



Assignee:


nidaley



Components:


plot



Created:


14/Feb/14 12:26 PM



Description:


For some reason Microsoft Excel (and probably other programs) expect semicolons instead of commas to be used in CSV files by default. So it would be nice if the plot plugin would accept semicolon separates CSV files, too, in order to be able to more easily share files with Excel.




Project:


Jenkins



Priority:


Minor



Reporter:


Sebastian Schuberth

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-7294) Included regions feature for GIT
















































Mark Waite
 resolved  JENKINS-7294 as Fixed


Included regions feature for GIT
















With no response in a year on the "is this fixed" question, I'm marking this as "Fixed".  Include regions are available with the git plugin.





Change By:


Mark Waite
(14/Feb/14 12:28 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [git] (JENKINS-9620) Add an option to use the shared option during the git clone
















































Mark Waite
 closed  JENKINS-9620 as Wont Fix


Add an option to use the shared option during the git clone
















Change By:


Mark Waite
(14/Feb/14 12:33 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-9620) Add an option to use the shared option during the git clone

Mark Waite
resolved JENKINS-9620 as Wont Fix

Add an option to use the shared option during the git clone

The shared option is accepted in the plugin and throws an exception declaring that "shared is unsupported, and considered dangerous".

The git clone man page says:

NOTE: this is a possibly dangerous operation; do not use it unless you understand what it does. If you clone your repository using this option and then delete branches (or use any other git command that makes any existing commit unreferenced) in the source repository, some objects may become unreferenced (or dangling). These objects may be removed by normal git operations (such as git commit) which automatically call git gc --auto. (See git-gc(1).) If these objects are removed and were referenced by the cloned repository, then the cloned repository will become corrupt.

Note that running git repack without the -l option in a repository cloned with -s will copy objects from the source repository into a pack in the cloned repository, removing the disk space savings of clone -s. It is safe, however, to run git gc, which uses the -l option by default.

If you want to break the dependency of a repository cloned with -s on its source repository, you can simply run git repack -a to copy all objects from the source repository into a pack in the cloned repository.

Change By:

Mark Waite
(14/Feb/14 12:33 PM)

Status:

Open
Resolved

Resolution:

WontFix

[JIRA] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails

2014-02-14 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-21590


Master cannot connect to slave / search for Java on slave fails















Is this a duplicate of JENKINS-21373?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [all-changes] (JENKINS-21808) Error on Save Projet Modification

2014-02-14 Thread e...@vernichon.fr (JIRA)















































Eric Vernichon
 commented on  JENKINS-21808


Error on Save Projet Modification 















I don't know why but this problem appears only with chrome, with firefox it's ok




























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails

2014-02-14 Thread r...@owl.me.uk (JIRA)















































Rich Daley
 commented on  JENKINS-21590


Master cannot connect to slave / search for Java on slave fails















I think it is. Is that fixed in 1.550?



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [plot] (JENKINS-21812) Display tooltips for columns when hovering over plot

2014-02-14 Thread sschube...@gmail.com (JIRA)















































Sebastian Schuberth
 created  JENKINS-21812


Display tooltips for columns when hovering over plot















Issue Type:


New Feature



Assignee:


nidaley



Components:


plot



Created:


14/Feb/14 1:25 PM



Description:


If there are several plots in the chart, it quickly becomes hard to see which color belongs to which column. It would be very nice if there were tooltips being displayed when hovering over a line / bar that show the name of the belonging column.




Project:


Jenkins



Priority:


Major



Reporter:


Sebastian Schuberth

























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)















































Walter Kacynski
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















I have tested the new version and I do see an improvement.  So much so that I am unable to capture a thread dump during the run of the email generation.  When monitoring the process CPU, I still see a large spike in CPU time, but the duration of this spike is much smaller.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)















































Walter Kacynski
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)
















08:23:13 Deleting old workspace snapshot from #19.
08:23:13 Archiving artifacts
08:23:13 Sending artifact delta relative to Deploy » SND » Build_WAS_Environment #19
08:23:14 Archived 418 artifacts
08:23:14 Archive block size is 32768
08:23:14 Received 215 blocks and 142533 bytes
08:23:14 Compression is 98.0%
08:23:14 Checking for post-build
08:23:14 Performing post-build step
08:23:14 Checking if email needs to be generated
08:23:14 Email was triggered for: Success
08:23:14 Sending email for trigger: Success
08:23:14 NOT overriding default server settings, using Mailer to create session
08:23:17 messageContentType = text/html; charset=UTF-8
08:23:17 Adding developers
08:23:17 Sending to requester
08:23:17 Successfully created MimeMessage
08:23:17 Sending email to: ...
08:23:18 Finished: SUCCESS





























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







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

[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)















































Walter Kacynski
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















On additional comment, after the first job that builds an email the process is much slower like the original implementation.  The above log is from a second run so it appears that the caching has improved response 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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)















































Alex Earl
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















@Walter, just to clarify, are you saying the issue is "fixed" or that there is still an issue?



























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







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

[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)















































Walter Kacynski
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















I have Wily/Introscope available to perform a method level trace of the application.  Please let me know the package names that I can instrument that would be helpful to debug the slow areas of code if you are interested in this information.  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] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)















































Walter Kacynski
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















I compared the Master CPU from "SPEEDY" and this fix and I would say that the problem is NOT fixed.  When generating emails from "SPEEDY" I hardly notice a master CPU spike.  With this fix, I see a 10% spike every-time an email is generated.  This spike is much shorter than without the recent fix.



























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







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

[JIRA] [email-ext] (JENKINS-20078) email-ext plugin takes a huge amount of time to send out final status emails (30min)















































Alex Earl
 commented on  JENKINS-20078


email-ext plugin takes a huge amount of time to send out final status emails (30min)















hudson.plugins.emailext.* (mainly ExtendedEmailPublisher and EmailRecipientUtils)
hudson.plugins.emailext.plugins.* (mainly ContentBuilder)
org.jenkinsci.plugins.tokenmacro.*

The only thing I changed in the release was adding caching. Perhaps my caching implementation wasn't a good one.


public class ContentBuilder {

@CopyOnWrite
private static volatile ListTokenMacro privateMacros;
...

public String transformText(String origText, ExtendedEmailPublisherContext context, ListTokenMacro additionalMacros) {

   try {
   ListTokenMacro privMacros = getPrivateMacros();
   if(additionalMacros != null)
   privateMacros.addAll(additionalMacros);
   newText = TokenMacro.expandAll(context.getBuild(), context.getListener(), newText, false, privMacros);
   } catch (MacroEvaluationException e) {
   context.getListener().getLogger().println("Error evaluating token: " + e.getMessage());
   } catch (Exception e) {
   Logger.getLogger(ContentBuilder.class.getName()).log(Level.SEVERE, null, e);
   }
...
}

public static ListTokenMacro getPrivateMacros() {
if(privateMacros != null)
return privateMacros;

privateMacros = new ArrayListTokenMacro();
ClassLoader cl = Jenkins.getInstance().pluginManager.uberClassLoader;
for (final IndexItemEmailToken, TokenMacro item : Index.load(EmailToken.class, TokenMacro.class, cl)) {
try {
privateMacros.add(item.instance());
} catch (Exception e) {
// ignore errors loading tokens
}
}
return privateMacros;
}
}


I'm not a Java guy really, so if there is a better way to do it in Java, please give me some pointers.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-12235) FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
















































Jesse Glick
 resolved  JENKINS-12235 as Duplicate


FATAL, Unable to delete script file, IOException2, remote file operation failed, unexpected termination of channel
















Essentially a duplicate of JENKINS-1948.





Change By:


Jesse Glick
(14/Feb/14 2:41 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] [other] (JENKINS-1948) intermittent: fails to remove temporary file on remote.















































Jesse Glick
 commented on  JENKINS-1948


intermittent: fails to remove temporary file on remote.















JENKINS-5073 massaged the reporting a bit; should no longer give misleading error about deleting script file (which is merely an aftereffect of the slave connectivity issue).



























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







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

[JIRA] [master-slave] (JENKINS-5073) hudson.util.IOException2: Failed to join the process - on a Windows slave
















































Jesse Glick
 resolved  JENKINS-5073 as Duplicate


hudson.util.IOException2: Failed to join the process - on a Windows slave 
















Change By:


Jesse Glick
(14/Feb/14 2:42 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] [core] (JENKINS-21813) Provide better 404 pages















































Christian Höltje
 created  JENKINS-21813


Provide better 404 pages















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


14/Feb/14 2:42 PM



Description:


Feature Request:

Please add better 404 pages.

Motivation:

The default winstone 404 page is very ugly and unhelpful.  Even if you use a different app server, the 404 pages are usually not pretty.

In addition, if you proxy via apache or nginx you cannot override the 404s because there are pages that return 404 (such as the search results page) that would be disabled.

Suggestion:

Include a page that says something like:

if security is disabled
  The page you're looking for doesn't exist.
else security is enabled
  The page you're looking for either doesn't exist or is not available to you.
  if not logged in
Try logging in and see if that helps.
  /endif
/endif

You can try searching for the page you're looking for: ___





Environment:


Jenkins 1.532.1




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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-7391) hudson.util.IOException2: Failed to join the process during MSBuild task
















































Jesse Glick
 resolved  JENKINS-7391 as Duplicate


hudson.util.IOException2: Failed to join the process during MSBuild task
















Change By:


Jesse Glick
(14/Feb/14 2:45 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] [core] (JENKINS-1948) Intermittent slave disconnections with secondary symptoms















































Jesse Glick
 updated  JENKINS-1948


Intermittent slave disconnections with secondary symptoms
















Change By:


Jesse Glick
(14/Feb/14 2:45 PM)




Summary:


intermittent:failstoremovetemporaryfileonremote.
Intermittentslavedisconnectionswithsecondarysymptoms





Labels:


robustnessslave





Priority:


Major
Critical





Component/s:


core





Component/s:


other



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [master-slave] (JENKINS-7690) Connection to slave is dropped in the middle of a build
















































Jesse Glick
 resolved  JENKINS-7690 as Duplicate


Connection to slave is dropped in the middle of a build
















Change By:


Jesse Glick
(14/Feb/14 2:44 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] [monitoring] (JENKINS-21814) Plugin wiki page: Change URL for source















































Christian Höltje
 created  JENKINS-21814


Plugin wiki page: Change URL for source















Issue Type:


Bug



Assignee:


Unassigned


Components:


monitoring



Created:


14/Feb/14 2:50 PM



Description:


On https://wiki.jenkins-ci.org/display/JENKINS/Monitoring the source code still links to the subversion URL: https://svn.jenkins-ci.org/trunk/hudson/plugins/monitoring/

I expected it to link to the github location: https://github.com/jenkinsci/monitoring-plugin





Project:


Jenkins



Priority:


Trivial



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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [monitoring] (JENKINS-21815) Images for node monitoring are broken















































Christian Höltje
 commented on  JENKINS-21815


Images for node monitoring are broken















This may be obsolete in light of JENKINS-21357



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [monitoring] (JENKINS-21815) Images for node monitoring are broken















































Christian Höltje
 created  JENKINS-21815


Images for node monitoring are broken















Issue Type:


Bug



Assignee:


Unassigned


Components:


monitoring



Created:


14/Feb/14 2:53 PM



Description:


When visiting:

https://jenkins.example.com/computer/slave01/monitoring/?

I get broken images.

For example, the "view threads" link has an image url of:

https://jenkins.example.com/static/32a48b63/monitoring?resource=threads.png

Visiting that URL returns 404.




Environment:


Jenkins 1.532.1

Winstone behind an apache proxy.

Monitoring plugin: 1.49.0




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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-20640) Jenkins become very slow and had 'proxy error'















































Christian Höltje
 commented on  JENKINS-20640


Jenkins become very slow and had proxy error















@evernat Do you have a link to the bug about HTTP sessions?  I'm seeing problems (with all endpoints) with both our 1.532.1 Jenkins servers.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-import] (JENKINS-21779) Job Importer doesn't work over https or http

2014-02-14 Thread jie...@java.net (JIRA)















































jieryn
 updated  JENKINS-21779


Job Importer doesnt work over https or http
















Change By:


jieryn
(14/Feb/14 3:28 PM)




Assignee:


jieryn



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-21694) Building from workspace: Add checkbox to return workspace to a pristine state

2014-02-14 Thread heath...@ca.ibm.com (JIRA)

Heather Fraser-Dube
commented on JENKINS-21694

Building from workspace: Add checkbox to return workspace to a pristine state

So right now the load is not going to do what you want because it leaves the ignored files on disk.

So I made a work item that will request that option on the load 303187: Provide a "Pristine" option for load

I also made the work item for the build definition source control participant to support it too Support a "Pristine" load when configuring the source control of a build definition which would make the functionality available for use consistently in the plugin.

I also updated work item 296206: Make "Just accept and fetch from a build workspace" more full featured to make sure it includes this as well.

wrt to being able to have API to programmatically create/update/destroy build definitions, you will be interested in [272836: CCM Design SDK API|https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/272836]. You might want to chime in there and identify the forum posts/workitems you have the describe your needs.

[JIRA] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin















































Alex Earl
 updated  JENKINS-21760


Unable to attach pdf as an attachment in email-ext plugin
















Change By:


Alex Earl
(14/Feb/14 3:49 PM)




Summary:


Unabletoattachpdfasan
attachemnt
attachment
inemail-extplugin



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [email-ext] (JENKINS-21760) Unable to attach pdf as an attachment in email-ext plugin















































Alex Earl
 commented on  JENKINS-21760


Unable to attach pdf as an attachment in email-ext plugin















In the attachments section you should just put *.pdf if the file is in the root of the workspace. You can only attach things that are under the workspace, nothing outside of that area. The pattern in the attachments pattern follows the Ant file pattern syntax. Please don't try and use the FILE token, that would try and match against the CONTENTS of the file, which won't match anything. I believe I gave you the exact syntax on the mailing list already.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-20445) Git plugin timeout is too small















































Christian Höltje
 commented on  JENKINS-20445


Git plugin timeout is too small















Is there a way we can bump up the priority for releasing 2.0.3 with the fix?

This broke our LTS systems using the stable plugins channel.  We have windows systems that do git clones very very slowly.

When we rolled back to 1.5.0 we lose build history because the build.xml files can't load.  I assume there was an incompatible XML change between 1.5.0 and 2.0.0?

I'll attach an example traceback.




























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-20445) Git plugin timeout is too small















































Christian Höltje
 updated  JENKINS-20445


Git plugin timeout is too small
















This is a traceback of what happens if we try to rollback to 1.5 after having been on 2.0.1.

Our log file is full of these and bunches of jobs missing build histories.  And we were having things retriggering over and over again as if they didn't know about previous builds.





Change By:


Christian Höltje
(14/Feb/14 3:59 PM)




Attachment:


traceback.out



























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







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

[JIRA] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails

2014-02-14 Thread nades...@ringler.ch (JIRA)















































Yuri Nadestin
 commented on  JENKINS-21590


Master cannot connect to slave / search for Java on slave fails















Just tried 1.550. Problem still exists.
(Back to 1.546)



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [email-ext] (JENKINS-21672) Need Pre-send Script to support classpath options















































Alex Earl
 commented on  JENKINS-21672


Need Pre-send Script to support classpath options















Can you give me some details on how you specify the classpath with the Groovy Postbuild Plugin? I've never used that plugin, so I'm not sure where to start looking in the source.



























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







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

[JIRA] [email-ext] (JENKINS-21672) Need Pre-send Script to support classpath options

2014-02-14 Thread fmer...@qualcomm.com (JIRA)















































Frank Merrow
 updated  JENKINS-21672


Need Pre-send Script to support classpath options
















Shows a fully configured Groovy Post Build script with two added ClassPaths





Change By:


Frank Merrow
(14/Feb/14 4:11 PM)




Attachment:


2-14-20148-06-43AM.png



























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







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

[JIRA] [teamconcert] (JENKINS-21694) Building from workspace: Add checkbox to return workspace to a pristine state

2014-02-14 Thread heath...@ca.ibm.com (JIRA)

Heather Fraser-Dube
edited a comment on JENKINS-21694

Building from workspace: Add checkbox to return workspace to a pristine state

So right now the load is not going to do what you want because it leaves the ignored files on disk.

So I made a work item that will request that option on the load 303187: Provide a "Pristine" option for load

I also updated work item 296206: Make "Just accept and fetch from a build workspace" more full featured to make sure it includes this as well.

wrt to being able to have API to programmatically create/update/destroy build definitions, you will be interested in 272836: CCM Design SDK API. You might want to chime in there and identify the forum posts/workitems you have that describe your needs.

[JIRA] [teamconcert] (JENKINS-21694) Building from workspace: Add checkbox to return workspace to a pristine state

2014-02-14 Thread heath...@ca.ibm.com (JIRA)

Heather Fraser-Dube
edited a comment on JENKINS-21694

Building from workspace: Add checkbox to return workspace to a pristine state

So right now the load is not going to do what you want because it leaves the ignored files on disk.

So I made a work item that will request that option on the load 303187: Provide a "Pristine" option for load

I also updated work item 296206: Make "Just accept and fetch from a build workspace" more full featured to make sure it includes this as well.

[JIRA] [xunit] (JENKINS-18443) SkipNoTestFiles flag ignored. Build still set to failed if test files missing

2014-02-14 Thread clpalexan...@gmail.com (JIRA)















































Carlos Alexandre
 commented on  JENKINS-18443


SkipNoTestFiles flag ignored. Build still set to failed if test files missing















I never noticed this issue until I upgraded from 1.78 to 1.81
After upgrading to 1.81 some projects started failing due to the absence of results files...

I downgraded back to 1.78 and now everything is OK.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails

2014-02-14 Thread jerry.delgau...@intergraph.com (JIRA)















































Jerry Del Gaudio
 commented on  JENKINS-21590


Master cannot connect to slave / search for Java on slave fails















We're seeing the same issue.  We're stuck at 1.546 until this is resolved.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails

2014-02-14 Thread e...@poegel.de (JIRA)
















































Eike Poegel
 resolved  JENKINS-21590 as Duplicate


Master cannot connect to slave / search for Java on slave fails
















Jenkins-21373





Change By:


Eike Poegel
(14/Feb/14 5:42 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] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails

2014-02-14 Thread e...@poegel.de (JIRA)















































Eike Poegel
 commented on  JENKINS-21590


Master cannot connect to slave / search for Java on slave fails















thx Daniel, really looks like a dup of 21373. Closed this bug here therefore,



























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







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

[JIRA] [jenkins-multijob-plugin] (JENKINS-21675) Concurrent multijob build runs incorrectly link to the latest dependent build run.

2014-02-14 Thread david.tw...@jivesoftware.com (JIRA)
















































David Tweet
 resolved  JENKINS-21675 as Fixed


Concurrent multijob build runs incorrectly link to the latest dependent build run.
















Looks like this was fixed in 1.12. Thanks!





Change By:


David Tweet
(14/Feb/14 6:03 PM)




Status:


Reopened
Resolved





Resolution:


Fixed



























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







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

[JIRA] [git] (JENKINS-20445) Git plugin timeout is too small

2014-02-14 Thread dvannieuwenbo...@ompartners.com (JIRA)















































Mark Waite
 commented on  JENKINS-20445


Git plugin timeout is too small















The git-plugin 2.0 release was a major change (as noted by the change of major number in the version string).  It changes the job definition and simplifies the user interface dramatically.  There is no facility for "downgrade", or rollback on major version changes like that.  It is already challenging enough assuring that old versions upgrade correctly.

If you need the plugin sooner, it may be simplest for you to build it yourself to confirm that it works for your use case.

I've built a copy of the git-plugin based on https://github.com/jenkinsci/git-plugin/commit/eec487fc52ca3165fc8190858cea23e3e3a21db0 .  

It is not an official release, but you could download it and try it at https://www.dropbox.com/s/tsoboofl14ejwrj/git.hpi



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [master-slave] (JENKINS-21590) Master cannot connect to slave / search for Java on slave fails

2014-02-14 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 commented on  JENKINS-21590


Master cannot connect to slave / search for Java on slave fails















This is the Jenkins changelog: http://jenkins-ci.org/changelog

It documents the major changes between Jenkins releases.

In this particular case (or rather JENKINS-21373), the fix will be included in 1.551  click "Upcoming Changes" to see it. Changes without a version header will likely be in the one after that, but might 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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-7414) Git submodules support does not work with relative url path

2014-02-14 Thread brandon.hel...@gmail.com (JIRA)















































Brandon Heller
 commented on  JENKINS-7414


Git submodules support does not work with relative url path















guillon, thanks for posting the patch!  I didn't try it but it confirmed the Jenkins bug, which is still present as of version 1.540.  Hopefully the developers are listening and will update the patch.  It's really easy to test, and yields this in the console output:

+ git submodule update --init --recursive
fatal: repository '/var/lib/jenkins/workspace/x-data' does not exist
Clone of '/var/lib/jenkins/workspace/x-data' into submodule path 'x-data' failed
Build step 'Execute shell' marked build as failure
Recording test results
An attempt to send an e-mail to empty list of recipients, ignored.
Finished: FAILURE



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-14847) Apply button not taken into account

2014-02-14 Thread jasondt...@gmail.com (JIRA)















































Jason Tran
 commented on  JENKINS-14847


Apply button not taken into account















Update (regarding issue Jenkins 21807):
As you as I enter URL, without clicking 'Apply' or 'Save' button, I would receive this crash/error message (also reported in 21807).

javax.servlet.ServletException: java.lang.NullPointerException
	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.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter$1.call(ScmSyncConfigurationFilter.java:46)
	at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationDataProvider.provideRequestDuring(ScmSyncConfigurationDataProvider.java:103)
	at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationFilter.doFilter(ScmSyncConfigurationFilter.java:42)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203)
	at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181)
	at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
	at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at

[JIRA] [subversion] (JENKINS-21785) Check for changes in folders linked via svn:externals fails due to missing credentials















































Davy Van Nieuwenborgh
 commented on  JENKINS-21785


Check for changes in folders linked via svn:externals fails due to missing credentials















I notice the same in our setup. After an upgrade, none of our jobs work correctly as we get "Authentication failures" randomly on one or more externals.
When reverting to 1.54, everything works fine again.
Very annoying that after a simple upgrade your complete installation does not work anymore ...



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-10442) RestartNotSupportedException when trying to do safeRestart

2014-02-14 Thread shannonck...@gmail.com (JIRA)















































Shannon Kerr
 commented on  JENKINS-10442


RestartNotSupportedException when trying to do safeRestart















dvaske, did you encounter any stability issues after moving to Oracle Java?  I just had Jenkins web service stop serving up pages on the web.  I could see the Jenkins process still running on the Ubuntu VM.  I ended up restarting the VM.  When Jenkins came back up, our jnlp Windows slaves did not reconnect automatically.  I had to restart those Windows servers and then all was well.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [copy-project-link] (JENKINS-13517) CopyProjectLink plugin: does not work with jobs using 'display name' feature

2014-02-14 Thread gpgarrettbo...@gmail.com (JIRA)















































Garrett Boast
 commented on  JENKINS-13517


CopyProjectLink plugin: does not work with jobs using display name feature















I've submitted a pull request that resolves this: https://github.com/jenkinsci/copy-project-link-plugin/pull/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] [copy-project-link] (JENKINS-13517) CopyProjectLink plugin: does not work with jobs using 'display name' feature

2014-02-14 Thread gpgarrettbo...@gmail.com (JIRA)















































Garrett Boast
 started work on  JENKINS-13517


CopyProjectLink plugin: does not work with jobs using display name feature
















Change By:


Garrett Boast
(14/Feb/14 8:11 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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-20640) Jenkins become very slow and had 'proxy error'

2014-02-14 Thread ever...@free.fr (JIRA)















































evernat
 commented on  JENKINS-20640


Jenkins become very slow and had proxy error















@Christian Höltje
The bug with HTTP sessions is JENKINS-20532
It happened since Jenkins v1.535 with the change to Jetty.
The bug is fixed since the Monitoring plugin v1.48



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-18937) Add DSL support for the Timestamper plugin
















































Daniel Spilker
 resolved  JENKINS-18937 as Fixed


Add DSL support for the Timestamper plugin
















Has been released in 1.19.





Change By:


Daniel Spilker
(14/Feb/14 8:40 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] [infrastructure] (JENKINS-21056) Ability to separate build build history of parameterized projects















































Daniel Spilker
 updated  JENKINS-21056


Ability to separate build build history of parameterized projects
















Change By:


Daniel Spilker
(14/Feb/14 8:44 PM)




Component/s:


job-dsl-plugin



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-18964) Clone Workspace SCM should be supported by job-dsl
















































Daniel Spilker
 closed  JENKINS-18964 as Fixed


Clone Workspace SCM should be supported by job-dsl
















Has been released in 1.16.





Change By:


Daniel Spilker
(14/Feb/14 8:46 PM)




Status:


Open
Closed





Resolution:


Fixed



























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







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

[JIRA] [job-dsl-plugin] (JENKINS-18396) Add ability to inject imports for helper classes used in job dsl.















































Daniel Spilker
 commented on  JENKINS-18396


Add ability to inject imports for helper classes used in job dsl.















Has been released in 1.16.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-18396) Add ability to inject imports for helper classes used in job dsl.
















































Daniel Spilker
 resolved  JENKINS-18396 as Fixed


Add ability to inject imports for helper classes used in job dsl.
















Change By:


Daniel Spilker
(14/Feb/14 8:51 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] [job-dsl-plugin] (JENKINS-18251) Add support for Do not fail build if archiving returns nothing option of archiveArtifacts publisher
















































Daniel Spilker
 resolved  JENKINS-18251 as Fixed


Add support for Do not fail build if archiving returns nothing option of archiveArtifacts publisher
















Has been release in 1.20, see https://github.com/jenkinsci/job-dsl-plugin/wiki/Job-reference#wiki-archive-artifacts





Change By:


Daniel Spilker
(14/Feb/14 8:56 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] [all-changes] (JENKINS-21808) Error on Save Projet Modification

2014-02-14 Thread madhuwh...@gmail.com (JIRA)

madhu cs
commented on JENKINS-21808

Error on Save Projet Modification

Same happening with me and also I am not able to build existing projects too

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

Stack trace

javax.servlet.ServletException: Failed to parse JSON:{parameter: {name: X, value: XXX}, statusCode: 303, redirectTo: .}
at org.kohsuke.stapler.RequestImpl.getSubmittedForm(RequestImpl.java:878)
at hudson.model.ParametersDefinitionProperty._doBuild(ParametersDefinitionProperty.java:128)
at hudson.model.AbstractProject.doBuild(AbstractProject.java:1860)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)

[JIRA] [all-changes] (JENKINS-21808) Error on Save Projet Modification

2014-02-14 Thread madhuwh...@gmail.com (JIRA)

madhu cs
edited a comment on JENKINS-21808

Error on Save Projet Modification

Same happening with me and also I am not able to build existing projects too

Jenkins ver. 1.547

Stack trace

[JIRA] [ec2] (JENKINS-19880) Cannot configure EC2 plugin due to errors

2014-02-14 Thread dim.horb...@gmail.com (JIRA)















































Dzmitry Horbach
 commented on  JENKINS-19880


Cannot configure EC2 plugin due to errors















Well thought i had the same problem only to figure out that my Jenkins had '1.2' instead of latest '1.20' version of plugin
Make sure you have region dropdown and select appropriate one and try with 1.20 - works on 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] [cobertura] (JENKINS-19204) Unable to remove unused Coverage Metric Targets from Cobertura Report Graph















































JP Rosevear
 commented on  JENKINS-19204


Unable to remove unused Coverage Metric Targets from Cobertura Report Graph















Latest versions of createcoverage allow for branch coverage (--branch) structure the xml output for packages, classes.  Methods seem to get an empty xml node, but its present.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cobertura] (JENKINS-12886) Cobertura plugin triggers inaccurate build failures















































JP Rosevear
 commented on  JENKINS-12886


Cobertura plugin triggers inaccurate build failures 















There is a "Fail builds if no reports" option in the Advanced config, it can be unchecked.



























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cobertura] (JENKINS-10788) Unable to parse cobertura coverage results
















































JP Rosevear
 resolved  JENKINS-10788 as Incomplete


Unable to parse cobertura coverage results
















Without the coverage file, this is not possible to resolve sanely.





Change By:


JP Rosevear
(15/Feb/14 12:03 AM)




Status:


Open
Resolved





Assignee:


stephenconnolly





Resolution:


Incomplete



























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







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

[JIRA] [cobertura] (JENKINS-12886) Cobertura plugin triggers inaccurate build failures
















































JP Rosevear
 resolved  JENKINS-12886 as Fixed


Cobertura plugin triggers inaccurate build failures 
















Change By:


JP Rosevear
(15/Feb/14 12:02 AM)




Status:


Open
Resolved





Assignee:


stephenconnolly





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] [git] (JENKINS-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked















































Mark Waite
 commented on  JENKINS-21622


Build creates new workspace@2 (and so on) when option concurrent builds NOT checked















I have never seen this before. Workspace creation is handled by Jenkins core, so I think this should be unassigned from git and assigned to 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-21622) Build creates new workspace@2 (and so on) when option concurrent builds NOT checked















































Mark Waite
 commented on  JENKINS-21622


Build creates new workspace@2 (and so on) when option concurrent builds NOT checked















I have never seen this before. Workspace creation is handled by Jenkins core, so I think this should be unassigned from git and assigned to 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] [matrix-combinations-parameter] (JENKINS-21816) Rebuild plugin support by Matrix Combinations plugin

2014-02-14 Thread de...@ikedam.jp (JIRA)















































ikedam
 created  JENKINS-21816


Rebuild plugin support by Matrix Combinations plugin















Issue Type:


Improvement



Assignee:


ikedam



Components:


matrix-combinations-parameter



Created:


15/Feb/14 1:56 AM



Description:


Rebuild Plugin now provides an extension point to add support for new parameters since 1.21 (see JENKINS-19843 for details).

It's time for Matrix Combination Plugin to support rebuild plugin.




Environment:


Matrix Combinations Plugin 1.0.4




Project:


Jenkins



Priority:


Major



Reporter:


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] [parameters] (JENKINS-19843) Adding option to extend the rebuild to other parameters types

2014-02-14 Thread de...@ikedam.jp (JIRA)
















































ikedam
 resolved  JENKINS-19843 as Fixed


Adding option to extend the rebuild to other parameters types
















Supported in rebuild-plugin-1.21.





Change By:


ikedam
(15/Feb/14 2:08 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [cobertura] (JENKINS-4795) OutOfMemorr Exception while generating the cobertura report
















































JP Rosevear
 resolved  JENKINS-4795 as Incomplete


OutOfMemorr Exception while generating the cobertura report
















There are several memory reduction commits on CoveragePaint.java since the last update on this ticket.  Closing this as incomplete since if there is still a problem it would need a new assessment.

commit daf038cf41e67beca0edbbdc7c3a6940abe1fd72
Author: Kohsuke Kawaguchi k...@kohsuke.org
Date:   Thu Oct 11 14:11:50 2012 -0700

More memory saving.

Lines with branches are relatively rare. Introduce a dedicated subtype for non-zero branch coverage information so that if there's no branching information, we can save 8 more b

commit acf4b9dc4e0170943a84326ec66cd242771d4de8
Author: Kohsuke Kawaguchi k...@kohsuke.org
Date:   Thu Oct 11 14:01:32 2012 -0700

use fly-weight pattern to save more memory

commit 32b902a583ce2943f7b01791f12d010adfefce8d
Author: Kohsuke Kawaguchi k...@kohsuke.org
Date:   Thu Oct 11 13:52:03 2012 -0700

CoveragePaintDetails is made immutable in preparation for the flyweight pattern

commit f957bc25748bf134d90c78f7626ac05012a2
Author: Jesse Glick jgl...@cloudbees.com
Date:   Thu Sep 27 13:42:37 2012 -0400

gnu.trove.map.hash.TIntObjectHashMap yields ~5.5% savings on coverage-with-lots-of-data.xml.





Change By:


JP Rosevear
(15/Feb/14 2:29 AM)




Status:


Reopened
Resolved





Assignee:


stephenconnolly





Resolution:


Incomplete



























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







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

[JIRA] [junit] (JENKINS-21261) CaseResult/index.jelly can be rendered with text/plain content type

2014-02-14 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-21261


CaseResult/index.jelly can be rendered with text/plain content type















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 core/src/main/java/hudson/tasks/junit/TestResultAction.java
http://jenkins-ci.org/commit/jenkins/411c3cfecb8094da86fd0397dc8c29c723f53da3
Log:
  JENKINS-21261

plugin might erranously put null into the collection, so filter them out





























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







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

[JIRA] [junit] (JENKINS-21261) CaseResult/index.jelly can be rendered with text/plain content type

2014-02-14 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-21261


CaseResult/index.jelly can be rendered with text/plain content type















Code changed in jenkins
User: Kohsuke Kawaguchi
Path:
 test/src/test/java/hudson/tasks/junit/CaseResultTest.java
http://jenkins-ci.org/commit/jenkins/c88698c0afc35d7427b16349f4d411d184f3ae3f
Log:
  JENKINS-21261 while I originally misdiagnosed the problem, the test is still marginally useful.





























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







-- 
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [cobertura] (JENKINS-6314) matrix build fails with coverage reporting only in some configurations