[JIRA] (JENKINS-61670) Attribute like e.g. class gets lost from HTML code in description fields

2020-03-24 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-61670  
 
 
  Attribute like e.g. class gets lost from HTML code in description fields   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 antisamy-markup-formatter-plugin  
 
 
Created: 
 2020-03-24 19:13  
 
 
Environment: 
 Jenkins 2.227  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 After upgrading the markup formatter plugin from 1.8 to 2.0 HTML code in system message, job description, build description and testresult description fields loses attributes like for example class attributes. We use these HTML descriptions a lot and also use the Simple Theme Plugin to style them. Without CSS classes this is not really possible.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
  

[JIRA] (JENKINS-54596) can't parse argument number: changelog.url

2020-01-20 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars commented on  JENKINS-54596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: can't parse argument number: changelog.url   
 

  
 
 
 
 

 
 Same issue here with v2.214 and Jenkins appearing in German. When forcing locale to English everything works. Doesn't seem to have something to do with the Chinese localization plugin.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195383.1542102275000.2783.157953502%40Atlassian.JIRA.


[JIRA] (JENKINS-56755) JUnit test report: Age and failedSince are wrong if test method names are not unique

2020-01-07 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars commented on  JENKINS-56755  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JUnit test report: Age and failedSince are wrong if test method names are not unique   
 

  
 
 
 
 

 
 ... and is still not merged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198398.1553601185000.4048.1578411661392%40Atlassian.JIRA.


[JIRA] (JENKINS-49164) CloneWorkspaceSCM does not work in a pipeline job

2019-05-09 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars commented on  JENKINS-49164  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CloneWorkspaceSCM does not work in a pipeline job   
 

  
 
 
 
 

 
 Too bad this does not receive any attention. That makes it even harder to rebuild complex jobs in pipeline when you additionally have to abandon the workspace cloning.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188001.1516887946000.21584.1557388740119%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-57080) Cannot hide Pipeline output when using Timestamps

2019-04-17 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57080  
 
 
  Cannot hide Pipeline output when using Timestamps   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Steven G Brown  
 
 
Components: 
 timestamper-plugin  
 
 
Created: 
 2019-04-17 11:31  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 In JENKINS-41845 they added the CSS class "pipeline-new-node" to the default pipeline console output lines to make it possible to hide these lines via CSS. When using timestamps in Pipeline jobs this leads to lines with multiple timestamps since the timestamps for these lines stay visible. It would be nice to also add a CSS class for the timestamps in "pipeline-new-node" lines to be able to also hide them.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
   

[JIRA] (JENKINS-57077) Let the user decide whether to accept any value for choice parameter

2019-04-17 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57077  
 
 
  Let the user decide whether to accept any value for choice parameter   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline-build-step-plugin  
 
 
Created: 
 2019-04-17 10:33  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 In JENKINS-52038 it was introduced that parameter values not defined in the choice parameter get rejected. Same thing has been done to the Parameterized Trigger Plugin some time ago. But for this plugin there is a switch (hudson.plugins.parameterizedtrigger.ProjectSpecificParametersActionFactory.compatibility_mode=true) to allow undefined parameter values. There should also be a switch like that for the Pipeline Build Step Plugin to let the user decide whether he thinks it is safe to accept undefined values or not.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[JIRA] (JENKINS-56755) JUnit test report: Age and failedSince are wrong if test method names are not unique

2019-03-26 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56755  
 
 
  JUnit test report: Age and failedSince are wrong if test method names are not unique   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 junit-plugin  
 
 
Created: 
 2019-03-26 11:53  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 In the JUnit test report the age and failedSince values are sometimes wrong. A newly failed test sometimes gets an age greater than 1 and a failedSince pointing to a build where the test did not fail. I found out that this always happens to tests whose failed method names are not unique. If there are other failed tests with the same method names in the previous report, the wrong failure seems to be recognized as the predecessor. In my opinion this could be easily fixed by returning className + '.' + testName instead of just testName from CaseResult.java#getTransformedTestName  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
  

[JIRA] (JENKINS-55677) Enable autocomplete for parameterized build settings

2019-01-18 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55677  
 
 
  Enable autocomplete for parameterized build settings   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-01-18 11:42  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 When starting a parameterized build, the form to enter the build parameters has autocomplete="off". So no textfield parameter input supports autocompletion. Enabling autocomplete would improve usability.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira 

[JIRA] (JENKINS-54581) Possibility to limit the amount of executed configurations of a matrix job

2018-11-12 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54581  
 
 
  Possibility to limit the amount of executed configurations of a matrix job   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 throttle-concurrent-builds-plugin  
 
 
Created: 
 2018-11-12 15:10  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 Currently it is possible to limit the executions of a matrix job per parent and per configuration. It would be useful to be able to limit the amount of executed configurations, so that, for example, I can limit a matrix job with 8 configurations to execute only 4 of them in parallel. Currently I found no way to achieve that.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
  

[JIRA] (JENKINS-54580) Possibility to define a maximum value for jobs with identical parameters

2018-11-12 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54580  
 
 
  Possibility to define a maximum value for jobs with identical parameters   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 throttle-concurrent-builds-plugin  
 
 
Created: 
 2018-11-12 15:03  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 Right now it is possible to set a maximum amount of concurrently executed builds and to prevent the execution of builds with identical parameters. It would be nice to also be able to set a maximum amount of concurrently executed builds with identical parameters. This can be useful in cases where you just want to limit the amount of builds with identical parameters while still allowing some parallelization.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 


[JIRA] (JENKINS-54579) Allow the max builds value to be a parameter

2018-11-12 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54579  
 
 
  Allow the max builds value to be a parameter   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 throttle-concurrent-builds-plugin  
 
 
Created: 
 2018-11-12 14:55  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 It should be possible to use a build parameter as the value for "Maximum Total Concurrent Builds" and "Maximum Concurrent Builds Per Node". Then it would be possible to trigger builds from different jobs with different max. builds values.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 

[JIRA] (JENKINS-54578) Cannot delete last category

2018-11-12 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54578  
 
 
  Cannot delete last category   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 throttle-concurrent-builds-plugin  
 
 
Created: 
 2018-11-12 14:50  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lars  
 

  
 
 
 
 

 
 1. Go to Jenkins configuration and create a Multi-Project Throttle Category and save. 2. Go to Jenkins configuration and delete the category so that no category is left and save. 3. Go to Jenkins configuration -> the deleted category is back  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This 

[JIRA] (JENKINS-49164) CloneWorkspaceSCM does not work in a pipeline job

2018-02-10 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W commented on  JENKINS-49164  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CloneWorkspaceSCM does not work in a pipeline job   
 

  
 
 
 
 

 
 Have you found some time to have a look at this problem?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40682) User names/passwords are masked even if they are just a substring

2017-03-31 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W commented on  JENKINS-40682  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: User names/passwords are masked even if they are just a substring   
 

  
 
 
 
 

 
 The way it is currently realized it also leaks secrets. The Mask Passwords Plugin masked only whole words and always worked reliably in terms of masking passwords.      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-40682) User names/passwords are masked even if they are just a substring

2016-12-27 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40682  
 
 
  User names/passwords are masked even if they are just a substring   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 credentials-binding-plugin  
 
 
Created: 
 2016/Dec/27 12:23 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Lars W  
 

  
 
 
 
 

 
 User names and passwords are masked in the log even if they are just substrings of other strings. A simple example: The log says: "service postgresql restart" and "postgres" is a user name, then the log says "service ql restart" Someone who knows what the partly masked string originally was or who can derive that from the context, now also knows that this substring is a user name or a password. Apart from that it can be annoying to have a log with partly masked strings that actually should be readable. User names and passwords should only be masked if they are not a substring of another word.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-38274) Archiving artifacts loses file permissions

2016-09-28 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W commented on  JENKINS-38274  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Archiving artifacts loses file permissions   
 

  
 
 
 
 

 
 Even if I did search for it... It is a bug report from 2012 and it is still not fixed. Does it really have a chance to get fixed in the near future if no one files a new report? No.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-38274) Archiving artifacts loses file permissions

2016-09-16 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-38274  
 
 
  Archiving artifacts loses file permissions   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Sep/16 1:16 PM  
 
 
Environment: 
 Jenkins 2.22  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Lars W  
 

  
 
 
 
 

 
 Make a file in a job's workspace executable. Let the job archive this file. The archived artifact is not executable any more.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

[JIRA] (JENKINS-36539) OK button disabled if project type chosen first

2016-07-08 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36539  
 
 
  OK button disabled if project type chosen first   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Jul/08 3:10 PM  
 
 
Environment: 
 Jenkins 2.12  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Lars W  
 

  
 
 
 
 

 
 1. Create a new project 2. Choose project type 3. Enter project name -> OK button is disabled OK button is only enabled when choosing project type after entering the name.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
  

[JIRA] (JENKINS-36477) Weird plugin dependencies

2016-07-06 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-36477  
 
 
  Weird plugin dependencies   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2016/Jul/06 2:57 PM  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Lars W  
 

  
 
 
 
 

 
 I don't know whether this is a bug in the dependency determination. Perhaps I misunterstood something. But since Jenkins started to show the plugin dependencies on the Installed Plugins page (since 2.0 I think) I noticed some weird dependencies. For example the LDAP plugin and the PAM Authentication plugin are installed as dependencies of the Run Condition and the Workspace Cleanup Plugin. Why should I need to install LDAP - which I will never use - to just clean up the workspace? Another example: The Run Condition plugin depends on the Conditional BuildStep plugin. But for the Conditional BuildStep plugin Jenkins only shows that Parameterized Trigger depends on it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-34046) Plots in Multi-configuration project

2016-06-28 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W commented on  JENKINS-34046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plots in Multi-configuration project   
 

  
 
 
 
 

 
 I looked into the code. In case of MatrixProjects the plots are stored in maps. On initialization these maps are not filled. So no plots are shown after restart. I changed this, but the next problem was that the project the plots belong to was null after initialization. (A project in this case is one configuration of a multi-configuration project.) In my opinion connecting a plot to a configuration is completely unneccessary since all configurations have the same plots (with different values of course, but the plots are the same). But I did not change that and tried to find a minimally invasive solution by using the null project plots in case no plots are found for a project. With my pull request https://github.com/jenkinsci/plot-plugin/pull/24 there are plots shown even after restart.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] (JENKINS-34046) Plots in Multi-configuration project

2016-06-23 Thread l.wol...@his.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Lars W commented on  JENKINS-34046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plots in Multi-configuration project   
 

  
 
 
 
 

 
 Annoying bug since the plots not only disappear after restart. They also seem to disappear some time after build. That makes this plugin unusable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)  
 
 

 
   
 

  
 

  
 

   





-- 
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] [parameterized-trigger-plugin] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)

2016-06-10 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-34871 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)  
 
 
 
 
 
 
 
 
 
 

Well, you can always disable this protection mechanism. It's specifically for existing instances that for one reason or another need to rely the existing behavior.
 
Always? https://wiki.jenkins-ci.org/display/SECURITY/Jenkins+Security+Advisory+2016-05-11 said this is "intended as a short-term workaround only". 
Thank you for proposing the Hidden Parameter Plugin. I didn't know it. I will give it a try. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [parameterized-trigger-plugin] (JENKINS-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)

2016-06-10 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-34871 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)  
 
 
 
 
 
 
 
 
 
 
Besides that, adding the parameters to a project causes them to be editable by the user in case of a manual build. In some cases this is not intended. Some parameters are only needed when triggered by another project. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)

2016-05-17 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-34871 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)  
 
 
 
 
 
 
 
 
 
 
I set this property on master - we only have one master. So my problem with this change is not as difficult as yours. And I only set hudson.model.ParametersAction.keepUndefinedParameters=true to completely disable this new behaviour and did not pass all safe parameters, because I don't think that this is maintainable. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-34871) After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)

2016-05-17 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-34871 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: After upgrading to Jenkins 2.3 we are unable to trigger parametrized build using prop file (maybe due to SECURITY-170 / CVE-2016-3721?)  
 
 
 
 
 
 
 
 
 
 
Same here, this change broke several of my jobs that need to pass undeclared parameters. I was able to fix this by setting hudson.model.ParametersAction.keepUndefinedParameters to true as said in the security advisory. But the security advisory also said that this is a short-term workaround which made me worry. If the user does not consider this behaviour unsafe, he should be able to enable it.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [envinject-plugin] (JENKINS-30028) EnvInject mask passwords interferes with timestamper

2016-04-13 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-30028 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EnvInject mask passwords interferes with timestamper  
 
 
 
 
 
 
 
 
 
 
But no one seems to care about merging and releasing it  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [envinject-plugin] (JENKINS-30028) EnvInject mask passwords interferes with timestamper

2016-02-11 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-30028 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EnvInject mask passwords interferes with timestamper  
 
 
 
 
 
 
 
 
 
 
OK, to illustrate it I built a job executing the shell script for i in $(seq 1 10); do echo time: `date +%H:%M:%S`; sleep 1; done 
As you can see the console output should show Timestamper's timestamps next to the timestamps from the shell script. Both timestamps should be equal. At first the console output with no EnvInject enabled: 20:04:01 Gestartet durch Benutzer 20:04:01 [EnvInject] - Loading node environment variables. 20:04:01 Baue in Arbeitsbereich /var/lib/jenkins/jobs/XYZ/workspace 20:04:01 [workspace] $ /bin/bash -e /tmp/hudson5525335093485642436.sh 20:04:01 time: 20:04:01 20:04:02 time: 20:04:02 20:04:03 time: 20:04:03 20:04:04 time: 20:04:04 20:04:05 time: 20:04:05 20:04:06 time: 20:04:06 20:04:07 time: 20:04:07 20:04:08 time: 20:04:08 20:04:09 time: 20:04:09 20:04:10 time: 20:04:10 20:04:11 Finished: SUCCESS 
Everything OK. Then I enabled 'Inject passwords to the build as environment variables' and 'Global passwords' and the output was: 20:03:39 [EnvInject] - Inject global passwords. 20:03:39 [EnvInject] - Mask passwords passed as build parameters. 20:03:39 Gestartet durch Benutzer 20:03:39 [EnvInject] - Loading node environment variables. 20:03:39 Baue in Arbeitsbereich /var/lib/jenkins/jobs/XYZ/workspace 20:03:40 [workspace] $ /bin/bash -e /tmp/hudson2882475315826943329.sh 20:03:41 time: 20:03:39 20:03:42 time: 20:03:40 20:03:43 time: 20:03:41 20:03:44 time: 20:03:42 20:03:45 time: 20:03:43 20:03:46 time: 20:03:44 20:03:47 time: 20:03:45 20:03:48 time: 20:03:46 20:03:49 time: 20:03:47 time: 20:03:48 Finished: SUCCESS 
Now the timestamps are shifted. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 

[JIRA] [envinject-plugin] (JENKINS-30028) EnvInject mask passwords interferes with timestamper

2016-02-11 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-30028 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: EnvInject mask passwords interferes with timestamper  
 
 
 
 
 
 
 
 
 
 
There was no load on the system when I ran the test from my previous comment. 
For me these time differences are a bug, because in some cases the timestamps don't help when they are shifted. And since it's a constant two-line-shift with EnvInject enabled and not a random occurrence, I wouldn't think it's something that's caused by delays or load. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [envinject-plugin] (JENKINS-30028) EnvInjject mask passwords interferes with timestamper

2015-08-20 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-30028 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: EnvInjject mask passwords interferes with timestamper  
 
 
 
 
 
 
 
 
 
 
I added the version numbers. I don't know whether it is a regression, because I have just started to use both plugins together. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [envinject-plugin] (JENKINS-30028) EnvInject mask passwords interferes with timestamper

2015-08-20 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30028 
 
 
 
  EnvInject mask passwords interferes with timestamper  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lars W 
 
 
 

Summary:
 
 EnvInjject EnvInject maskpasswordsinterfereswithtimestamper 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [envinject-plugin] (JENKINS-30028) EnvInjject mask passwords interferes with timestamper

2015-08-20 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W updated an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30028 
 
 
 
  EnvInjject mask passwords interferes with timestamper  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lars W 
 
 
 

Summary:
 
 EnvInjjectmaskpasswordsinterferes with timestamper 
 
 
 

Environment:
 
 Jenkins1.624EnvInject1.91.4Timestamper1.7.2 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [copyartifact-plugin] (JENKINS-30027) Ability to unzip artifacts

2015-08-19 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30027 
 
 
 
  Ability to unzip artifacts  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 copyartifact-plugin 
 
 
 

Created:
 

 19/Aug/15 11:14 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Lars W 
 
 
 
 
 
 
 
 
 
 
When copying zipped artifacts, I always have to add a shell build step to unzip and delete that copied file. It would be great if the Copy Artifact plugin had an option to unzip the artifact into the target directory instead of copy. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
  

[JIRA] [envinject-plugin] (JENKINS-30028) EnvInjject mask passwords interferes timestamper

2015-08-19 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-30028 
 
 
 
  EnvInjject mask passwords interferes timestamper  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Manuel Jess Recena Soto 
 
 
 

Components:
 

 envinject-plugin, timestamper-plugin 
 
 
 

Created:
 

 19/Aug/15 11:23 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Lars W 
 
 
 
 
 
 
 
 
 
 
When using EnvInject's option Inject passwords to the build as environment variables with password parameter masking and timestamper the timestamps in the console log are shifted by two lines (and the last two lines don'T have timestamps). These two lines are probably [EnvInject] - Inject global passwords. [EnvInject] - Mask passwords passed as build parameters. 
But why do they cause a shift? 
The second problem ist, when viewing the log while the job is still running newly added lines do not get timestamps. I have to reload the page to see timestamps. 
Both problems are gone for jobs without EnvInject passwords. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
   

[JIRA] [extensible-choice-parameter-plugin] (JENKINS-29934) UnsupportedOperationException with empty choice

2015-08-13 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29934 
 
 
 
  UnsupportedOperationException with empty choice  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 extensible-choice-parameter-plugin 
 
 
 

Created:
 

 13/Aug/15 12:34 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Lars W 
 
 
 
 
 
 
 
 
 
 
When using File Choice Parameter with active Empty Choice setting the parameter list cannot be generated because of java.lang.UnsupportedOperationException at java.util.AbstractList.add(AbstractList.java:148) at jp.ikedam.jenkins.plugins.extensible_choice_parameter.FilenameChoiceListProvider.getFileList(FilenameChoiceListProvider.java:333) 
No values can be added to a list returned by Arrays.asList. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

[JIRA] [extensible-choice-parameter-plugin] (JENKINS-29934) UnsupportedOperationException with empty choice

2015-08-13 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-29934 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: UnsupportedOperationException with empty choice  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/extensible-choice-parameter-plugin/pull/16 should fix it 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [performance-plugin] (JENKINS-29832) NumberFormatException with German Locale

2015-08-06 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29832 
 
 
 
  NumberFormatException with German Locale  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Manuel Carrasco 
 
 
 

Components:
 

 performance-plugin 
 
 
 

Created:
 

 06/Aug/15 2:33 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Lars W 
 
 
 
 
 
 
 
 
 
 
The total traffic is rounded to 2 decimal places in PerformanceReport.java by converting it to a string and back. That fails with a system locale using a comma to separate the decimal places. 
Exception in Jenkins log: 
Caught exception evaluating: it.getTotalTrafficInKb() in ... Reason: java.lang.NumberFormatException: For input string: 5351,75 java.lang.NumberFormatException: For input string: 5351,75 at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1250) at java.lang.Double.valueOf(Double.java:504) at hudson.plugins.performance.PerformanceReport.roundTwoDecimals(PerformanceReport.java:325) at hudson.plugins.performance.PerformanceReport.getTotalTrafficInKb(PerformanceReport.java:211) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
   

[JIRA] [performance-plugin] (JENKINS-29832) NumberFormatException with German Locale

2015-08-06 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-29832 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: NumberFormatException with German Locale  
 
 
 
 
 
 
 
 
 
 
https://github.com/jenkinsci/performance-plugin/pull/53 should fix this by avoiding unneccessary conversion 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-29591) Build can be cancelled without the cancel right

2015-07-23 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-29591 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Build can be cancelled without the cancel right  
 
 
 
 
 
 
 
 
 
 
Hm OK, but why? That would mean with Job/Cancel someone would be allowed to cancel builds but not to start builds. With Job/Build he would be allowed to do both. Did I understand that correctly? 
Why should anyone be allowed to only cancel builds? I would unterstand if Job/Cancel would imply Job/Build. But this way around it seems strange. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-29591) Build can be cancelled without the cancel right

2015-07-23 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-29591 
 
 
 
  Build can be cancelled without the cancel right  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 23/Jul/15 11:02 AM 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Lars W 
 
 
 
 
 
 
 
 
 
 
We use project-based matrix authorization and the Anonymous user has the global rights Job - Discover, Job - Read, Job - Workspace. 
There is one Job where Anonymous should be able to build it. When I add the right Job - Build via the job config, the anonymous user can build it - but he can also cancel it even though the cancel right is not activated. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 

[JIRA] [junit-plugin] (JENKINS-29383) Failure summary does not work when special chars are present in path

2015-07-22 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-29383 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Failure summary does not work when special chars are present in path  
 
 
 
 
 
 
 
 
 
 
Why? You tried to fix something and broke something else. So your fix is not OK and this issue is not solved. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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] [junit-plugin] (JENKINS-29383) Failure summary does not work when special chars are present in path

2015-07-22 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-29383 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Failure summary does not work when special chars are present in path  
 
 
 
 
 
 
 
 
 
 
With that change the page always scrolls to the top when clicking the '+' icon. That is very annoying. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-flow-plugin] (JENKINS-25420) Stack trace thrown even with simply failure fail in parallel block

2015-07-16 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-25420 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Stack trace thrown even with simply failure fail in parallel block  
 
 
 
 
 
 
 
 
 
 
I think the stacktrace output was added with https://github.com/jenkinsci/build-flow-plugin/commit/2854dcd2e1e095a8f9b52749eeccc5c1a460dc44#diff-6276501be42f45c099a641d6ebebcc8b But why? I would propose to revert that. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-28601) Order of job table reverse

2015-06-07 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-28601 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Order of job table reverse  
 
 
 
 
 
 
 
 
 
 


JENKINS-17290
 reversed the sort order 
initialsortdir=up is now ascending - A-Z initialsortdir=down is now descending - Z-A 
So the initialsort dir attributes should be reversed too. 
https://github.com/jenkinsci/jenkins/pull/1729 should fix this 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-28601) Order of job table reverse

2015-06-03 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W commented on  JENKINS-28601 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Order of job table reverse  
 
 
 
 
 
 
 
 
 
 
The InitialSortDir of the job table (and some other tables) should be changed to up. But I don't know where to do it. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-28425) UI: Build history overflows

2015-06-02 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W reopened an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
This reverted https://github.com/jenkinsci/jenkins/commit/1dd60ec7780870f9c11686659178e52d251c15fc Now the animated ball in the build history again won't open console 
 
 
 
 
 
 
 
 
 
 Jenkins /  JENKINS-28425 
 
 
 
  UI: Build history overflows  
 
 
 
 
 
 
 
 
 

Change By:
 
 Lars W 
 
 
 

Resolution:
 
 Fixed 
 
 
 

Status:
 
 Resolved Reopened 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-28601) Order of job table reverse

2015-05-27 Thread l.wol...@his.de (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lars W created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Jenkins /  JENKINS-28601 
 
 
 
  Order of job table reverse  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 core 
 
 
 

Created:
 

 27/May/15 3:31 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Lars W 
 
 
 
 
 
 
 
 
 
 
After upgrading to 1.615 the initial order of the job/project table is Z-A instead of A-Z as it was before 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) 

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

2014-12-10 Thread l.wol...@his.de (JIRA)














































Lars W
 commented on  JENKINS-24352


Unneccessary line breaks in JUnit test results table since 1.576















Because there is nothing happening here, I fixed the JUnit table myself by installing the Simple Theme Plugin and adding the CSS
.bigtable td {
	white-space: nowrap
}



























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







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


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

2014-08-25 Thread l.wol...@his.de (JIRA)














































Lars W
 commented on  JENKINS-24352


Unneccessary line breaks in JUnit test results table since 1.576















Same with the tables in the side panel (build processor, build history, ...) with certain screen resolutions.



























This message is automatically generated by JIRA.
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-24030) Modernize tabBar and bigtable

2014-08-20 Thread l.wol...@his.de (JIRA)














































Lars W
 commented on  JENKINS-24030


Modernize tabBar and bigtable















Seems to me related to this change:
Since 1.576 the JUnit test result page looks ugly. Lots of unneccessary line breaks, especially in the 'duration' column.
E.g. a duration of 1 minute 19 seconds is now shown as
1 minute
19
seconds



























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







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


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

2014-08-20 Thread l.wol...@his.de (JIRA)














































Lars W
 created  JENKINS-24352


Unneccessary line breaks in JUnit test results table since 1.576















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


table.PNG



Components:


core



Created:


20/Aug/14 12:06 PM



Description:


Seems to me related to JENKINS-24030:
Since 1.576 the JUnit test result page looks ugly. Lots of unneccessary line breaks, especially in the 'duration' column.
E.g. a duration of 1 minute 19 seconds is now shown as
1 minute
19
seconds




Project:


Jenkins



Labels:


user-experience




Priority:


Major



Reporter:


Lars W

























This message is automatically generated by JIRA.
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] [matrix-combinations-parameter] (JENKINS-21851) No combinations are built in a scheduled build with Matrix Combinations Parameter

2014-02-19 Thread l.wol...@his.de (JIRA)














































Lars W
 commented on  JENKINS-21851


No combinations are built in a scheduled build with Matrix Combinations Parameter















Pull request that should fix this issue
https://github.com/jenkinsci/matrix-combinations-plugin/pull/2



























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







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


[JIRA] [matrix-combinations-parameter] (JENKINS-21851) No combinations are built in a scheduled build with Matrix Combinations Parameter

2014-02-18 Thread l.wol...@his.de (JIRA)














































Lars W
 created  JENKINS-21851


No combinations are built in a scheduled build with Matrix Combinations Parameter















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


matrix-combinations-parameter



Created:


18/Feb/14 11:08 AM



Description:


Steps to reproduce:
Create a matrix job, add one axis, add some values
Add the matrix combinations parameter
Schedule the build

When the scheduled build is started, it is built with no combinations.
Expected: scheduled builds are built with all combinations




Project:


Jenkins



Priority:


Major



Reporter:


Lars W

























This message is automatically generated by JIRA.
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-21851) No combinations are built in a scheduled build with Matrix Combinations Parameter

2014-02-18 Thread l.wol...@his.de (JIRA)














































Lars W
 commented on  JENKINS-21851


No combinations are built in a scheduled build with Matrix Combinations Parameter















The reason is probably the method createValue(StaplerRequest) in MatrixCombinationsParameterDefinition.java
which always returns 
new MatrixCombinationsParameterValue(getName(),new Boolean[]{},new String[]{})




























This message is automatically generated by JIRA.
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-21565) In case of MultipleFailureException Jenkins test results show only the last failure

2014-02-01 Thread l.wol...@his.de (JIRA)














































Lars Wolter
 updated  JENKINS-21565


In case of MultipleFailureException Jenkins test results show only the last failure
















Change By:


Lars Wolter
(01/Feb/14 5:11 PM)




Description:


IfaJUnittestfailsforexampleinthe@Testmethodandinthe@Aftermethod,JUnitthrowsaMultipleFailureExceptioncontainingbothfailures.Jenkinstestresultpageshowsonlythelastfailure(theonefromthe@Aftermethod),themoreimportantonefromthe@Testmethodisnotshown.TheJUnitxmlfilecreatedbyAntcontainstwoerror/failureelementsforthistestcase.
Theyare
Oneis
justnotshown.



























This message is automatically generated by JIRA.
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-21565) In case of MultipleFailureException Jenkins test results show only the last failure

2014-01-30 Thread l.wol...@his.de (JIRA)














































Lars Wolter
 created  JENKINS-21565


In case of MultipleFailureException Jenkins test results show only the last failure















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


junit



Created:


30/Jan/14 10:58 AM



Description:


If a JUnit test fails for example in the @Test method and in the @After method, JUnit throws a MultipleFailureException containing both failures.
Jenkins' test result page shows only the last failure (the one from the @After method), the more important one from the @Test method is not shown.
The JUnit xml file created by Ant contains two error/failure elements for this test case. They are just not shown.




Environment:


Ant 1.9.3, Java 1.7.0_51

Ubuntu 12.04 LTS




Project:


Jenkins



Priority:


Major



Reporter:


Lars Wolter

























This message is automatically generated by JIRA.
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-21252) UnsatisfiedLinkError on Startup

2014-01-07 Thread l.wol...@his.de (JIRA)














































Lars Wolter
 created  JENKINS-21252


UnsatisfiedLinkError on Startup















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Components:


core



Created:


07/Jan/14 11:31 AM



Description:


After upgrading from 1.538 - 1.546 Jenkins system log shows the following error:

Jan 07, 2014 9:54:38 AM WARNING jenkins.diagnosis.HsErrPidList 
Failed to list up hs_err_pid files
java.lang.UnsatisfiedLinkError: com.sun.jna.Native.open(Ljava/lang/String;)J
	at com.sun.jna.Native.open(Native Method)
	at com.sun.jna.NativeLibrary.getInstance(NativeLibrary.java:236)
	at com.sun.jna.Library$Handler.init(Library.java:140)
	at com.sun.jna.Native.loadLibrary(Native.java:366)
	at com.sun.jna.Native.loadLibrary(Native.java:351)
	at com.sun.akuma.CLibrary.clinit(CLibrary.java:89)
	at com.sun.akuma.JavaVMArguments.resolvePID(JavaVMArguments.java:126)
	at com.sun.akuma.JavaVMArguments.ofLinux(JavaVMArguments.java:114)
	at com.sun.akuma.JavaVMArguments.of(JavaVMArguments.java:104)
	at com.sun.akuma.JavaVMArguments.current(JavaVMArguments.java:92)
	at jenkins.diagnosis.HsErrPidList.init(HsErrPidList.java:62)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
	at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
	at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
	at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
	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.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:316)
	at hudson.ExtensionList.load(ExtensionList.java:295)
	at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248)
	at hudson.ExtensionList.iterator(ExtensionList.java:138)
	at hudson.ExtensionList.get(ExtensionList.java:129)
	at hudson.diagnosis.NullIdDescriptorMonitor.verifyId(NullIdDescriptorMonitor.java:86)
	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)
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105)
	at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
	at jenkins.model.Jenkins$7.runTask(Jenkins.java:899)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at 

[JIRA] [core] (JENKINS-18580) Error when creating a job with umlauts or workspace files with umlauts

2013-07-02 Thread l.wol...@his.de (JIRA)














































Lars Wolter
 created  JENKINS-18580


Error when creating a job with umlauts or workspace files with umlauts















Issue Type:


Bug



Affects Versions:


current



Assignee:


Unassigned


Attachments:


screenshot.PNG



Components:


core



Created:


02/Jul/13 12:05 PM



Description:


1. When creating a job with German umlauts in its name the corresponding directory in the file system has '?' instead of the umlauts.
As a consequence the build fails because of a java.nio.file.NoSuchFileException.

2. If a file name in a job's workspace contains umlauts, the file cannot be opened via Jenkins because it also has '?' instead of umlauts and cannot be found (- screenshot)

Locale is set to de_DE.UTF-8
Jenkins is started with -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8

sun.io.unicode.encoding	UnicodeLittle
sun.jnu.encoding	UTF-8
file.encoding	UTF-8
file.encoding.pkg	sun.io

But I wasn't able to get it to work




Environment:


Ubuntu 12.04.2 LTS, Jenkins standalone




Project:


Jenkins



Priority:


Major



Reporter:


Lars Wolter

























This message is automatically generated by JIRA.
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.