date:20140831















































Daniel Beck
 commented on  JENKINS-11543


UTF-8 encoding issue of build parameters as soon as including File parameter 















hudson-behavior.js seems to build a UTF-8 encoded JSON string, while the browser sets no charset, making it to default to Latin 1 when parsed on the server.

Not sure who's to blame here (although I'd tentatively guess YUI/behavior should make sure the browser sets a charset for all the multipart text parts), but the following patch in Stapler works for me by simply parsing the JSON string in multipart form data as UTF-8 if no other charset is set:

$ git diff
diff --git a/core/src/main/java/org/kohsuke/stapler/RequestImpl.java b/core/src/main/java/org/kohsuke/stapler/RequestImpl.java
index b8fb81c..230cef2 100644
--- a/core/src/main/java/org/kohsuke/stapler/RequestImpl.java
+++ b/core/src/main/java/org/kohsuke/stapler/RequestImpl.java
@@ -852,8 +852,19 @@ public class RequestImpl extends HttpServletRequestWrapper implements StaplerReq
 isSubmission=true;
 parseMultipartFormData();
 FileItem item = parsedFormData.get("json");
-if(item!=null)
-p = item.getString();
+if(item!=null) {
+if (item.getContentType() == null) {
+// JENKINS-11543: Client doesn't set charset per part, so
+// default to UTF-8 if no other charset is specified.
+try {
+p = item.getString("UTF-8");
+} catch (java.io.UnsupportedEncodingException uee) {
+throw new AssertionError("UTF-8 unsupported")
+}
+} else {
+p = item.getString();
+}
+}
 } else {
 p = getParameter("json");
 isSubmission = !getParameterMap().isEmpty();


Of course anything not relying on structured form submission will continue to be broken.

Asked KK on IRC where to file issues with Stapler, as the GitHub issue tracker seems abandoned.



























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







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

[JIRA] [git] (JENKINS-24520) Recent changes is always empty

2014-08-31 Thread daniel.anechito...@gmail.com (JIRA)















































Daniel Anechitoaie
 created  JENKINS-24520


Recent changes is always empty















Issue Type:


Bug



Assignee:


Nicolas De Loof



Components:


git



Created:


31/Aug/14 11:30 PM



Description:


After updating https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin to Version 2.2.5 (Aug 15, 2014) recent changes is always empty.
After i downgraded to previous version Version 2.2.4 (Aug 2, 2014), everything is working fine again.




Environment:


Jenkins ver. 1.575 

Git plugin Version 2.2.5 

Multiple SCMs plugin 0.3




Project:


Jenkins



Priority:


Critical



Reporter:


Daniel Anechitoaie

























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







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

[JIRA] [core] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter















































Daniel Beck
 commented on  JENKINS-11543


UTF-8 encoding issue of build parameters as soon as including File parameter 















When a file upload form field is included, it changes the request content type from application/x-www-form-urlencoded to multipart/form-data.



























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







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

[JIRA] [core] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter















































Daniel Beck
 updated  JENKINS-11543


UTF-8 encoding issue of build parameters as soon as including File parameter 
















Change By:


Daniel Beck
(31/Aug/14 9:50 PM)




Affects Version/s:


current





Due Date:


11/Nov/11





Component/s:


core



























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







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

[JIRA] [core] (JENKINS-24519) Flyweight tasks only use one-off executor when they can be scheduled immediately















































Daniel Beck
 commented on  JENKINS-24519


Flyweight tasks only use one-off executor when they can be scheduled immediately















FWIW I think I've seen this before with Build Flow as 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/d/optout.

[JIRA] [core] (JENKINS-24519) Flyweight tasks only use one-off executor when they can be scheduled immediately















































Daniel Beck
 updated  JENKINS-24519


Flyweight tasks only use one-off executor when they can be scheduled immediately
















Change By:


Daniel Beck
(31/Aug/14 9:26 PM)




Summary:


matrix build deadlocks slave
Flyweight tasks only use one-off executor when they can be scheduled immediately





Component/s:


matrix



























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







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

[JIRA] [core] (JENKINS-24519) matrix build deadlocks slave















































Daniel Beck
 commented on  JENKINS-24519


matrix build deadlocks slave















Source of the problem seems to be that Flyweight tasks (those running on one-off executors) effectively lose their "flyweight" property when they cannot be scheduled the moment they enter the queue:

https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/Queue.java#L1097



























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







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

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression















































Daniel Beck
 commented on  JENKINS-2


Label display wrong when using operators in _expression_















Re NodeLabel Parameter; I doubt it'll be possible to consider LabelAssignmentActions since the queue items are usually long gone when viewing this page and any further Actions added to a build are optional AFAIK. Scope should probably be only static label assignments (i.e. AbstractProject.getAssignedLabel()) only.



























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







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

[JIRA] [core] (JENKINS-24519) matrix build deadlocks slave















































Daniel Beck
 commented on  JENKINS-24519


matrix build deadlocks slave















Confirmed on Jenkins 1.577 out of the box. May be an element of randomness to it, as I've had to try twice. The first one (waiting one minute for the slave to come online) didn't work, but the second try (impatiently launched slave manually via web UI) worked.



























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







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

[JIRA] [core] (JENKINS-24519) matrix build deadlocks slave

2014-08-31 Thread flx107...@gmail.com (JIRA)

felix schwitzer
created JENKINS-24519

matrix build deadlocks slave

Issue Type:

Bug

Affects Versions:

current

Assignee:

Unassigned

Attachments:

config.xml

Components:

core, matrix

Created:

31/Aug/14 8:27 PM

Description:

I have a fresh downloaded jenkins whitout plugins running and configured
one dumb slave (slave1) connected via ssh+user/password.
I set up a matrix project (a minimal example is attached) to build on
slave1 and tie the parent to that slave (in advanced project settings)
When
1) the slave has only 1 executor
2) the slave is configured to get online when needed ("take this slave on-line when in demand and off-line when idle")
then the deadlock happens if the slave is offline when the project is triggered. The parent build wakes up the slave, but then stucks saying

Configuration tst » slave1 is still in the queue: Waiting for next available executor on slave1

Note that 1) and 2) are necessary to reproduce the bug. If the slave is
accidentally online at build start, the project builds fine.

This is maybe JENKINS-22502 but the minimalistic setup should allow
to reproduce the bug easily.

Environment:

Linux/ubuntu14.04

Project:

Jenkins

Priority:

Major

Reporter:

felix schwitzer

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

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

答复: GOOD NEWS

2014-08-31 Thread Shen, Jessica (JSH)




发件人: Shen, Jessica (JSH)
发送时间: 2014年9月1日 3:53
收件人: not...@domain.org
主题: GOOD NEWS


Private Donätion of $3million to you, Contact 
roycockru...@hotmail.com for More info

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

[JIRA] [cli] (JENKINS-24385) Jenkins CLI hangs with InvocationTargetException

2014-08-31 Thread mail.marcelrich...@googlemail.com (JIRA)















































Daniel Beck
 commented on  JENKINS-24385


Jenkins CLI hangs with InvocationTargetException















Back up the files identity.key and/or identity.key.enc in the Jenkins home directory on the master node, and then delete them. Restart.

From the documentation, it doesn't look like it's really used that much:
https://wiki.jenkins-ci.org/display/JENKINS/Instance+Identity

Still, make sure that e.g. SCM credentials (or any other passwords stored in Jenkins) still work with the newly generated instance identity.

If you could search older jenkins.logs for errors related to instance_identity to help identify the cause of the broken key file that would be great.

Related: https://groups.google.com/d/msg/jenkinsci-users/q9C1m8O0ruE/lrlSllwH-T8J



























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







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

[JIRA] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs

2014-08-31 Thread fetzer...@gmail.com (JIRA)















































Christian Fetzer
 commented on  JENKINS-24256


Fail build for missing / erroneous valgrind publisher XMLs















Thanks for the quick implementation! I've tested v0.21 confirming that it behaves as intended.



























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







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

[JIRA] [cli] (JENKINS-24385) Jenkins CLI hangs with InvocationTargetException















































Marcel Richter
 commented on  JENKINS-24385


Jenkins CLI hangs with InvocationTargetException















Yes, there is an error after restart:


Aug 31, 2014 7:39:52 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
WARNING: Failed to instantiate Key[type=org.jenkinsci.main.modules.sshd.SSHD, annotation=[none]]; skipping this component
com.google.inject.ProvisionException: Guice provision errors:
 
1) Error injecting constructor, java.io.IOException: javax.crypto.BadPaddingException: Given final block not properly padded
  at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.(Unknown Source)
  while locating org.jenkinsci.main.modules.instance_identity.InstanceIdentity
for field at org.jenkinsci.main.modules.sshd.SSHD.identity(Unknown Source)
 
1 error
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:54)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:132)
at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:117)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.Scopes$1$1.get(Scopes.java:65)
at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:429)
at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41)
at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1051)
at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001)
at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:391)
at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:382)
at hudson.ExtensionFinder._find(ExtensionFinder.java:151)
at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:341)
at hudson.ExtensionList.load(ExtensionList.java:295)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
at hudson.ExtensionList.iterator(ExtensionList.java:138)
at jenkins.model.Jenkins.(Jenkins.java:860)
at hudson.model.Hudson.(Hudson.java:82)
at hudson.model.Hudson.(Hudson.java:78)
at hudson.WebAppMain$3.run(WebAppMain.java:222)
Caused by: java.io.IOException: javax.crypto.BadPaddingException: Given final block not properly padded
at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.(InstanceIdentity.java:62)
at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.(InstanceIdentity.java:38)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86)
at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269)
at com.google.inject.internal.SingleFieldInjector.inject(SingleFieldInjector.java:54)
at com.google.inject.internal.MembersInjectorImpl.injectMembers(MembersInjectorImpl.java:132)
at com.goog

[JIRA] [cvs] (JENKINS-24429) CVSRoot is not accepted by CVS plugin

2014-08-31 Thread michael.m.cla...@gmail.com (JIRA)
















































Michael Clarke
 closed  JENKINS-24429 as Duplicate


CVSRoot is not accepted by CVS plugin
















Change By:


Michael Clarke
(31/Aug/14 6:35 PM)




Status:


Open
Closed





Assignee:


Michael Clarke





Resolution:


Duplicate



























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







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

[JIRA] [warnings] (JENKINS-12743) Warnings plugin does not aggregate for multi-configuration projects















































SCM/JIRA link daemon
 commented on  JENKINS-12743


Warnings plugin does not aggregate for multi-configuration projects















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/warnings/WarningsAnnotationsAggregator.java
http://jenkins-ci.org/commit/warnings-plugin/d574ea518bfaf2d83bad4fc43f6e52fde8e3bf2c
Log:
  Merge pull request #42 from timangus/master

JENKINS-12743 Fix WarningsAnnotationsAggregator not aggregating


Compare: https://github.com/jenkinsci/warnings-plugin/compare/9dd4214ce443...d574ea518bfa




























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







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

[JIRA] [core] (JENKINS-24517) there is no api access to changes

2014-08-31 Thread gray...@gmail.com (JIRA)















































Alex Gray
 commented on  JENKINS-24517


there is no api access to changes 















Thanks Daniel.  That makes sense to me.



























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







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

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

2014-08-31 Thread domi.br...@free.fr (JIRA)















































Dominique Brice
 commented on  JENKINS-2


Label display wrong when using operators in _expression_















I checked in the list if plugin at https://wiki.jenkins-ci.org/display/JENKINS/Plugins and didn't see any existing plugin that would cover this need.
However the interaction between some existing plugin and this potentially new plugin would be interesting (for instance with https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin).



























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







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

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

2014-08-31 Thread domi.br...@free.fr (JIRA)















































Dominique Brice
 commented on  JENKINS-2


Label display wrong when using operators in _expression_















Sounds good, let me get to it.



























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







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

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

2014-08-31 Thread domi.br...@free.fr (JIRA)















































Dominique Brice
 started work on  JENKINS-2


Label display wrong when using operators in _expression_
















Change By:


Dominique Brice
(31/Aug/14 3:19 PM)




Status:


Open
In Progress



























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







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

[JIRA] [core] (JENKINS-24513) Zero executors on master not well documented or enforced

2014-08-31 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 updated  JENKINS-24513


Zero executors on master not well documented or enforced
















Change By:


Jesse Glick
(31/Aug/14 3:17 PM)




Labels:


security



























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







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

[JIRA] [core] (JENKINS-24513) Zero executors on master not well documented or enforced

2014-08-31 Thread jgl...@cloudbees.com (JIRA)













































  
Jesse Glick
 edited a comment on  JENKINS-24513


Zero executors on master not well documented or enforced
















Well in practice it is not so obvious.

Also there are some use cases for administrators to configure special projects that must run on the master, to do backups and the like. For these cases you want to leave some executor slots open, yet block regular projects from using them. The natural way to do that would be to have Jenkins.MasterComputer.checkPermission(Computer.BUILD) require RUN_SCRIPTS on Jenkins, so that only admin-authorized projects could run on it; and then display an admin monitor when security is enabled yet there is no configured QueueItemAuthenticator.



























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







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

[JIRA] [core] (JENKINS-24513) Zero executors on master not well documented or enforced

2014-08-31 Thread jgl...@cloudbees.com (JIRA)















































Jesse Glick
 commented on  JENKINS-24513


Zero executors on master not well documented or enforced















Well in practice it is not so obvious.

Also there are some use cases for administrators to configure special projects that must run on the master, to do backups and the like. For these cases you want to leave some executor slots open, yet block regular projects from using them. The natural way to do that would be to have Jenkins.MasterComputer.checkPermission(Computer.BUILD) require RUN_SCRIPTS on Jenkins, so that only admin-authorized projects could run on it; and then display an admin monitor when there is no configured QueueItemAuthenticator.



























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







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

[JIRA] [parameters] (JENKINS-11543) UTF-8 encoding issue of build parameters as soon as including File parameter

2014-08-31 Thread krizleeb...@java.net (JIRA)















































krizleebear
 updated  JENKINS-11543


UTF-8 encoding issue of build parameters as soon as including File parameter 
















Change By:


krizleebear
(31/Aug/14 2:42 PM)




Summary:


UTF-8 encoding
 crash
 issue
 when include
 of build parameters as soon as including
 File
 paramemter
 parameter
 





Environment:


none
Linux





Description:


String parameter UTF-8 encoding crash issue when include File paramemterfor example, setting up File
 paramemter
 parameter
 and String parameter. > String parameter is  "가나다라마바" (in korean) > buildparameter result is "ê°€ë‚˜ë‹¤ë ¼" (encoding crashed)please check itthanks



























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







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

[JIRA] [parameters] (JENKINS-11543) UTF-8 encoding crash issue when include File paramemter

2014-08-31 Thread krizleeb...@java.net (JIRA)















































krizleebear
 updated  JENKINS-11543


UTF-8 encoding crash issue when include File paramemter 
















The issue still exists with the newest version (1.577) today. This makes File parameters practically unusable for internationalized use cases! 

I've attached a minimal repro case config.xml. When you build it with default parameters (String parameter is defaulted to "äöü"), then this build will fail. Removing the File parameter restores the build.

Please fix this issue. I was pretty surprised when I found this issue being known for 3 years.





Change By:


krizleebear
(31/Aug/14 2:39 PM)




Attachment:


config.xml



























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







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

[JIRA] [core] (JENKINS-22750) Polling no longer triggers builds (regression 1.560)

2014-08-31 Thread kirill...@gmail.com (JIRA)

Kirill Peskov
commented on JENKINS-22750

Polling no longer triggers builds (regression 1.560)

The bug is still there, easily reproducible in following configuration:

Server: most recent Bitnami Appliance (Ubuntu-based), jenkins.war manually upgraded to 1.577
Slaves: 1 'cloud' in-demand slave, managed by virtualbox plugin, Ubuntu 14.04 LTS x86_64 with OS 'native' LAMP stack.
SCM: git in local network on a separate server, accessible by ssh & git
Job: default 'free-style job', with Build Trigger set to 'Poll SCM' once per hour (doesn't matter fixed or randomized), tied by node name to the particular slave (in-demand cloud VB slave)

Manual job triggering brings the node online and after the configured delay (3 min in my case) jenkins proceeds with the rest of the job. Changes in SCM cannot trigger the build because of typical error message mentioned above: "We need to schedule a new build to get a workspace, but deferring in the hope that one will become available soon (all_suitable_nodes_are_offline)".

This is not just a bug, it's SEVERE failure breaking typical workflow in any cloud environment. Jenkins has to make the decision to power up slave(s) based on the results of SCM Polling, but unable to do that, because the very SCM Polling can be done only on the node(s) which are currently offline.

[JIRA] [git] (JENKINS-22706) Warn that space in TEMP or TMP causes msysgit ssh credentials failure

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















































Mark Waite
 updated  JENKINS-22706


Warn that space in TEMP or TMP causes msysgit ssh credentials failure
















Change By:


Mark Waite
(31/Aug/14 1:15 PM)




Summary:


Warn that space in TEMP or TMP causes msysgit
 internal
 ssh credentials
 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/d/optout.

[JIRA] [git] (JENKINS-22706) Warn that space in TEMP or TMP causes msysgit internal failure

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















































Mark Waite
 updated  JENKINS-22706


Warn that space in TEMP or TMP causes msysgit internal failure
















Change By:


Mark Waite
(31/Aug/14 1:13 PM)




Summary:


git fetching fails after switching from HTTPS to SSH
Warn that space in TEMP or TMP causes msysgit internal 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/d/optout.

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

2014-08-31 Thread schristo...@gmail.com (JIRA)















































Steven Christou
 commented on  JENKINS-18935


Make Subversion plugin support Subversion 1.8















https://github.com/jenkinsci/subversion-plugin/pull/94 removes the modified svnkit from the subversion plugin.



























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







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

[JIRA] [plugin] (JENKINS-17268) Post build task plugin: Passing arguments does not work as documented

2014-08-31 Thread francis.lab...@gmail.com (JIRA)















































Francis Labrie
 commented on  JENKINS-17268


Post build task plugin: Passing arguments does not work as documented















This functionality doesn't work on Linux and OS X either. Group captures are not available as script arguments. Example:



Regular _expression_
(?m)^.*: warning: (Incomplete '.+' bundle copy detected.)$


Script
echo "Info: Post Build Task did detect a recoverable error:\n\t${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/d/optout.

[JIRA] [build-monitor] (JENKINS-24518) Define different colors to unstable and aborted statuses















































Or Shachar
 commented on  JENKINS-24518


Define different colors to unstable and aborted statuses















see https://github.com/jan-molak/jenkins-build-monitor-plugin/pull/9



























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







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

[JIRA] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs















































SCM/JIRA link daemon
 commented on  JENKINS-24256


Fail build for missing / erroneous valgrind publisher XMLs















Code changed in jenkins
User: Johannes Ohlemacher
Path:
 src/main/java/org/jenkinsci/plugins/valgrind/ValgrindPublisher.java
 src/main/java/org/jenkinsci/plugins/valgrind/ValgrindResult.java
 src/main/java/org/jenkinsci/plugins/valgrind/config/ValgrindPublisherConfig.java
 src/main/java/org/jenkinsci/plugins/valgrind/model/ValgrindReport.java
 src/main/java/org/jenkinsci/plugins/valgrind/parser/ValgrindParserResult.java
 src/main/java/org/jenkinsci/plugins/valgrind/parser/ValgrindSaxParser.java
 src/main/java/org/jenkinsci/plugins/valgrind/util/ValgrindEvaluator.java
 src/main/resources/org/jenkinsci/plugins/valgrind/ValgrindPublisher/config.jelly
http://jenkins-ci.org/commit/valgrind-plugin/66a39a978b63b090528a78934d304e9731fd7207
Log:
  JENKINS-24256: added option to fail build on invalid/malformed xml
reports





























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







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

[JIRA] [build-monitor] (JENKINS-24518) Define different colors to unstable and aborted statuses
















































Or Shachar
 assigned  JENKINS-24518 to Unassigned



Define different colors to unstable and aborted statuses
















I see you already opened pull request https://github.com/jan-molak/jenkins-build-monitor-plugin/pull/9





Change By:


Or Shachar
(31/Aug/14 12:24 PM)




Assignee:


Or Shachar



























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







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

[JIRA] [build-monitor] (JENKINS-24518) Define different colors to unstable and aborted statuses















































Or Shachar
 started work on  JENKINS-24518


Define different colors to unstable and aborted statuses
















Change By:


Or Shachar
(31/Aug/14 11:44 AM)




Status:


Open
In Progress



























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







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

[JIRA] [build-monitor] (JENKINS-24518) Define different colors to unstable and aborted statuses

Or Shachar
created JENKINS-24518

Define different colors to unstable and aborted statuses

Issue Type:

Improvement

Affects Versions:

current

Assignee:

Or Shachar

Attachments:

31-08-2014 14-21-00.png

Components:

build-monitor

Created:

31/Aug/14 11:44 AM

Description:

While some people want to get binary result of their job (0/1 passed/not-passed) - a lot of the times we want to seperate between the different statuses:

Stable - everything passed
Unstable - Test were successfully executed but found failures.
Failed - Problem with compilation / configuration / runtime error.
Aborted - Build time-out, someone intentionally stopped the run in the middle.

This gives a more realistic image of the build status.

I suggest a small improvement to build monitor plugin that would support more statuses and show more accurate dashboard of the jobs.
(I already created private patch to plugin - see screenshot).

Correct me if I'm wrong but I believe this is the more common need in the dashboard.

Thanks!

Environment:

Any Jenkins core and build monitor plugin <= [1.5+build.123]

Project:

Jenkins

Labels:

build-monitor-plugin

Priority:

Major

Reporter:

Or Shachar

[JIRA] [core] (JENKINS-24517) there is no api access to changes
















































Daniel Beck
 resolved  JENKINS-24517 as Not A Defect


there is no api access to changes 
















/job/foo/changes shares the API of the project, and as is documented on /job/foo/api:

Controlling the amount of data you fetch

The tree query parameter allows you to explicitly specify and retrieve only the information you are looking for, by using an XPath-ish path _expression_. The value should be a list of property names to include, with sub-properties inside square braces.

So:


http://jenkins/job/foo/api/xml?tree=builds[number,changeSet[items[*]]]


Resolving as Not a Defect; the API does not mirror the UI exactly but that would just be less stable, and it's still possible to get the data out.





Change By:


Daniel Beck
(31/Aug/14 11:43 AM)




Status:


Open
Resolved





Assignee:


wolfs





Resolution:


Not A Defect



























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







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

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















































Daniel Beck
 commented on  JENKINS-22017


Git client: NoClassDefFoundError















For reference, I filed JENKINS-23150 for the invalid configuration issue.



























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







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

[JIRA] [core] (JENKINS-24517) there is no api access to changes















































Daniel Beck
 updated  JENKINS-24517


there is no api access to changes 
















Changes page is not provided by a plugin.





Change By:


Daniel Beck
(31/Aug/14 11:36 AM)




Summary:


there is no api access to changes
 plugin
 





Component/s:


core





Component/s:


all-changes



























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







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

[JIRA] [core] (JENKINS-23334) Jenkins Frezees After Windows Security Patches Applied
















































Daniel Beck
 resolved  JENKINS-23334 as Incomplete


Jenkins Frezees After Windows Security Patches Applied
















Resolving as incomplete, as no

information required for further investigation, such as thread dumps [...], possibly relevant log output, Windows system log information, ...

was provided in almost three months.





Change By:


Daniel Beck
(31/Aug/14 11:33 AM)




Status:


Reopened
Resolved





Resolution:


Incomplete



























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







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

[JIRA] [core] (JENKINS-24513) Zero executors on master not well documented or enforced















































Daniel Beck
 commented on  JENKINS-24513


Zero executors on master not well documented or enforced















Jenkins allows users with configure privileges to run arbitrary shell or batch scripts as the user Jenkins runs as (bonus: When using the Windows installer, it runs as SYSTEM).

How is this NOT obvious?



























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







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

[JIRA] [tasks-plugin] (JENKINS-23635) When Ignore-Case is set, tasks types should be rolled up regardless of case















































SCM/JIRA link daemon
 commented on  JENKINS-23635


When Ignore-Case is set, tasks types should be rolled up regardless of case















Code changed in jenkins
User: Ulli Hafner
Path:
 src/main/java/hudson/plugins/tasks/parser/TaskScanner.java
 src/test/java/hudson/plugins/tasks/parser/TaskScannerTest.java
http://jenkins-ci.org/commit/tasks-plugin/cfdc2990a00d43f18baf188d133c52ada3f49b5e
Log:
  [FIXED JENKINS-23635] Use upper case tag as type when parsing with ignore case option.





























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







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

[JIRA] [tasks-plugin] (JENKINS-23635) When Ignore-Case is set, tasks types should be rolled up regardless of case















































SCM/JIRA link daemon
 commented on  JENKINS-23635


When Ignore-Case is set, tasks types should be rolled up regardless of case















Code changed in jenkins
User: Ulli Hafner
Path:
 .idea/libraries/Maven__org_jvnet_hudson_plugins_analysis_core_1_58.xml
http://jenkins-ci.org/commit/analysis-suite-plugin/1eff43553154d19e1bee96b669a2372c3401f585
Log:
  [FIXED JENKINS-23635] Use upper case tag as type when parsing with ignore case option.





























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







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

[JIRA] [tasks-plugin] (JENKINS-23635) When Ignore-Case is set, tasks types should be rolled up regardless of case
















































SCM/JIRA link daemon
 resolved  JENKINS-23635 as Fixed


When Ignore-Case is set, tasks types should be rolled up regardless of case
















Change By:


SCM/JIRA link daemon
(31/Aug/14 11:29 AM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

Daniel Beck
edited a comment on JENKINS-2

Label display wrong when using operators in _expression_

I would not change the definition of getTiedJobs, as that could be considered a regression for others using it.

Simple string matching also will not work, consider the labels windows and windows-server: jobs with the latter will show up for the former which is inconsistent with how labels work.

Note also e.g. negation operators (!windows) that would make no sense for jobs to show up on the windows node page as "tied". Or what about windows||!windows?

A more informative "This label is used by:" is needed (e.g. group jobs by label containing the current LabelAtom) and could be provided as an Action for Labels so it shows up on a separate page.

windows-server&&jdk7

job1
job2

windows-server&&msbuild

job3
job4

This is why I suggest this could (and probably should, for now) be provided by a plugin. If it proves useful (and does not result in e.g. performance regressions), this functionality could also be integrated into core in some way later, using essentially the same code.

[JIRA] [core] (JENKINS-23333) Label display wrong when using operators in expression

Daniel Beck
commented on JENKINS-2

Label display wrong when using operators in _expression_

I would not change the definition of getTiedJobs, as that could be considered a regression for others using it.

Simple string matching also will not work, consider the labels windows and windows-server: jobs with the latter will show up for the former which is inconsistent with how labels work.

Note also e.g. negation operators (!windows) that would make no sense for jobs to show up on the windows node page as "tied". Or what about windows||!windows?

A more informative "This label is used by:" is needed (e.g. group jobs by label containing the current LabelAtom) and could be provided as an Action for Labels.

[JIRA] [warnings] (JENKINS-24463) PyLint parse missing errors

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















































Ulli Hafner
 commented on  JENKINS-24463


PyLint parse missing errors















Seems that the error format is totally different. Is this a new pylint version with different output format? Or are warnings still reported correctly? Here is the test case for the current format:

trunk/src/python/cachedhttp.py:3: [C] Line too long (85/80)
trunk/src/python/tv.py:28: [C0103, Show.__init__] Invalid name "seasonCount" (should match [a-z_][a-z0-9_]{2,30}$)
trunk/src/python/tv.py:35: [C0111, Episode] Missing docstring


Can you please add an example with both warnings and errors? Note that the error format has no associated file in the message, should the filename be empty? Where do the numbers after the error refer to? 



























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







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

[JIRA] [valgrind] (JENKINS-24256) Fail build for missing / erroneous valgrind publisher XMLs















































SCM/JIRA link daemon
 commented on  JENKINS-24256


Fail build for missing / erroneous valgrind publisher XMLs















Code changed in jenkins
User: Johannes Ohlemacher
Path:
 src/main/java/org/jenkinsci/plugins/valgrind/ValgrindPublisher.java
 src/main/java/org/jenkinsci/plugins/valgrind/config/ValgrindPublisherConfig.java
 src/main/resources/org/jenkinsci/plugins/valgrind/ValgrindPublisher/config.jelly
http://jenkins-ci.org/commit/valgrind-plugin/9ec3eb12b292923e40b59585791817d39ec3cee7
Log:
  JENKINS-24256: added option to fail build on missing xml reports





























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







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

[JIRA] [vstestrunner] (JENKINS-22450) Make trx and coverage files paths available to further build steps in VSTestRunner plugin