date:20150225















































Daniel Beck
 updated  JENKINS-26690


Build stats throws illegal argument exception on dashboard view
















Tentatively assigning to Jesse Glick as he wrote the new build number based code.

Current hypothesis is that AbstractLazyLoadRunMap.headMap(Integer) cannot handle negative arguments (as passed by Dashboard View Plugin's Build Statistics Widget when there are fewer builds/lower numbered builds than the limit of 10) since AbstractLazyLoadRunMap.COMPARATOR overflows when given o1=Integer.MAX, o2=-5.

While there's a trivial workaround (remove that widget from dashboards), I'll leave the priority due to possible severity of the core bug.





Change By:


Daniel Beck
(25/Feb/15 10:49 PM)




Assignee:


Peter Hayes
Jesse Glick





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] [workflow-plugin] (JENKINS-26307) CPS Groovy collection.find() returns Boolean
















































Jesse Glick
 resolved  JENKINS-26307 as Duplicate


CPS Groovy collection.find() returns Boolean
















Change By:


Jesse Glick
(25/Feb/15 10:33 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [workflow-plugin] (JENKINS-27076) Need ability to name workspaces















































Jesse Glick
 commented on  JENKINS-27076


Need ability to name workspaces















Anyway JENKINS-26122 is the real request, not the directory name.



























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] [workflow-plugin] (JENKINS-27076) Need ability to name workspaces
















































Jesse Glick
 resolved  JENKINS-27076 as Not A Defect


Need ability to name workspaces
















There is a dir step you can use if you want to run in a different directory.





Change By:


Jesse Glick
(25/Feb/15 10:22 PM)




Status:


Open
Resolved





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] [workflow-plugin] (JENKINS-27078) Need ability to isolate console output from threaded execution
















































Jesse Glick
 resolved  JENKINS-27078 as Duplicate


Need ability to isolate console output from threaded execution
















Change By:


Jesse Glick
(25/Feb/15 10:22 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [workflow-plugin] (JENKINS-27098) Support outputting deployments to environment-dashboard
















































Jesse Glick
 resolved  JENKINS-27098 as Not A Defect


Support outputting deployments to environment-dashboard
















Not even in @jenkinsci. Should be refiled in https://github.com/vipinsthename/environment-dashboard/issues/new I suppose.





Change By:


Jesse Glick
(25/Feb/15 10:18 PM)




Status:


Open
Resolved





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-27135) Some images are consistantly broken/not loading Jenkins ver. 1.565.2 on apache-tomcat-7.0.55

2015-02-25 Thread ygopin...@statestreet.com (JIRA)















































bergam yat
 created  JENKINS-27135


Some images are consistantly broken/not loading Jenkins ver. 1.565.2 on apache-tomcat-7.0.55















Issue Type:


Bug



Assignee:


Unassigned


Attachments:


image_fail_1.png, image_fail_2.png



Components:


core



Created:


25/Feb/15 10:17 PM



Description:


There are many random images which are broken in IE or Firefox. Its not sporadic , these images never load. Some are plugin icons and some are coverage graphs.

Coverage reports for some other projects are displaying.




Environment:


Jenkins ver. 1.565.2

OS : Red Hat Enterprise Linux Server release 6.5 (Santiago)

JDK : jdk-1.7.0-05-64

Tomcat : apache-tomcat-7.0.55




Project:


Jenkins



Priority:


Major



Reporter:


bergam yat

























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] [durable-task-plugin] (JENKINS-26105) Unkillable tasks















































Jesse Glick
 commented on  JENKINS-26105


Unkillable tasks















Current BourneShellScript specifically declines to copy stdout/stderr from the wrapper process to the build log, since doing so would consume a Thread, but this also makes diagnosis of this class of error harder. Should at a minimum allow the diagnosis to be enabled with a system property. Maybe it is possible to allocate a thread which stops listening after one second. Or maybe up to (say) five concurrent tasks in the system would get this diagnosis applied but subsequent ones would not, so that people experimenting with flow definitions would get the benefit of diagnosis but there would be little performance hit in busy production systems.



























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] [workflow-plugin] (JENKINS-27105) workflow-plugin: 'env' before 'sh' will hang 'sh'
















































Jesse Glick
 resolved  JENKINS-27105 as Duplicate


workflow-plugin: 'env' before 'sh' will hang 'sh'
















Change By:


Jesse Glick
(25/Feb/15 10:11 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [websphere-deployer-plugin] (JENKINS-21863) WebSphere deployer: deploy to cluster

2015-02-25 Thread ryr...@gmail.com (JIRA)















































Wryel Covo
 commented on  JENKINS-21863


WebSphere deployer: deploy to cluster















Hi guys, 

The implementation for clusters from Leonardo worked fine for me.

But now, I have a scenario (and other peoples can be have ...) that i need deploy one artifact in one cluster and one server in only one deploy action, example of view of "Manage Modules" in WebSphere from these application:


WebSphere:cell=webwas01-deCell01,node=IHS-WAS8,server=IHS-WAS8
WebSphere:cell=webwas01-deCell01,cluster=cluster-your-name


To accept all scenarios (it's just an idea, do not know how the implementation of the WAS plugin works) would not be better to have a textarea with this configuration instead of the fields with the information from a single server? (I imagine that even this kind of change breaks compatibility plugin too)

Thanks.



























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







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

[JIRA] [core] (JENKINS-16536) PermGen leak















































Daniel Beck
 commented on  JENKINS-16536


PermGen leak















Give it more than 64MB or whatever you have configured or is the default. Set it to 128MB and see whether it stabilizes.



























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-22519) Jenkins Build History page: Build Status table is always empty on Safari















































Daniel Beck
 commented on  JENKINS-22519


Jenkins Build History page: Build Status table is always empty on Safari















Did you submit a fix, or is this something local to your install?

If this occurs for all users who use Jenkins in French, it's definitely a bug...



























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] [websphere-deployer-plugin] (JENKINS-25896) deployed WebSphere Deployer plugin Plugin

2015-02-25 Thread ryr...@gmail.com (JIRA)















































Wryel Covo
 commented on  JENKINS-25896


deployed WebSphere Deployer plugin Plugin















@raphael, can you put the complete stacktrace on txt and attach?



























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] [ghprb-plugin] (JENKINS-26591) Workflow support for GitHub Pull Requests Trigger

2015-02-25 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-26591


Workflow support for GitHub Pull Requests Trigger















Code changed in jenkins
User: Jesse Glick
Path:
 COMPATIBILITY.md
http://jenkins-ci.org/commit/workflow-plugin/a8bc736218b0cf23fdc06143e5de7ef07a9ef8b8
Log:
  JENKINS-26591 Noting.





























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] [groovy-postbuild-plugin] (JENKINS-26918) Workflow support for Groovy Postbuild

2015-02-25 Thread scm_issue_l...@java.net (JIRA)















































SCM/JIRA link daemon
 commented on  JENKINS-26918


Workflow support for Groovy Postbuild















Code changed in jenkins
User: Jesse Glick
Path:
 COMPATIBILITY.md
http://jenkins-ci.org/commit/workflow-plugin/d0342a794caa94ef663cddc86097a9730ea6ba57
Log:
  JENKINS-26918 Noting.





























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] [groovy-postbuild-plugin] (JENKINS-26918) Workflow support for Groovy Postbuild















































Jesse Glick
 updated  JENKINS-26918


Workflow support for Groovy Postbuild
















Change By:


Jesse Glick
(25/Feb/15 9:31 PM)




Summary:


Add workflow
Workflow
 support
 for Groovy Postbuild



























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] [ghprb-plugin] (JENKINS-26591) Workflow support for GitHub Pull Requests Trigger















































Jesse Glick
 updated  JENKINS-26591


Workflow support for GitHub Pull Requests Trigger
















Change By:


Jesse Glick
(25/Feb/15 9:29 PM)




Summary:


Workflow support for
GitHub Pull Requests Trigger
 Support





Labels:


workflow





Component/s:


workflow-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] [config-file-provider-plugin] (JENKINS-26247) added SimpleBuildStep implementation for workflow-plugin support.
















































Jesse Glick
 resolved  JENKINS-26247 as Duplicate


added SimpleBuildStep implementation for workflow-plugin support.
















Consolidating to JENKINS-26339.





Change By:


Jesse Glick
(25/Feb/15 9:29 PM)




Status:


Open
Resolved





Resolution:


Duplicate



























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







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

[JIRA] [config-file-provider-plugin] (JENKINS-26247) added SimpleBuildStep implementation for workflow-plugin support.















































Jesse Glick
 updated  JENKINS-26247


added SimpleBuildStep implementation for workflow-plugin support.
















Change By:


Jesse Glick
(25/Feb/15 9:28 PM)




Labels:


workflow





Component/s:


workflow-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] [workflow-plugin] (JENKINS-27134) Permission for input approval

Jesse Glick
created JENKINS-27134

Permission for input approval

Issue Type:

Improvement

Assignee:

Jesse Glick

Components:

workflow-plugin

Created:

25/Feb/15 9:21 PM

Description:

Currently the input step allows you to specify a submitter, which may be a user ID or an external group ("granted authority"). This does not work well with authorization strategies, especially those that allow you to group together users inside Jenkins, such as (but not limited to) nectar-rbac in Jenkins Enterprise by CloudBees.

Arguably the more natural approach would be for InputStep to define a new permission, "approve flow", which would be checked on the WorkflowRun (can use PermissionScope.RUN). Thus rather than specifying a submitter for a particular step you would just ensure there was an RBAC group defined on the flow job (or its folder, etc.) which granted that permission and included the people you want. Then no reference need be made to any particular AuthorizationStrategy at all; this behavior would just follow from the Jenkins authorization model.

If defined, submitter would still be consulted in case the approving user lacked the new permission. There is a potential compatibility issue in case submitter was not defined; today that means that any user (even anonymous) can approve the flow, whereas we would want the new permission to be enforced. Unfortunately Jenkins offers no way to mark a newly introduced Permission as "granted until explicitly denied", except via system property hacks; see comment in JENKINS-17200. Lacking that, the only option is to break compatibility and say that existing input steps without submitter will now reject random users from approving. The new permission could be implied by, for example, Item.CONFIGURE to minimize the impact—approval by the person who wrote the flow would still be guaranteed to work.

Project:

Jenkins

Labels:

permissions

Priority:

Minor

Reporter:

Jesse Glick

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] [svnmerge-plugin] (JENKINS-26347) Credentials not found for merge from mainline

2015-02-25 Thread ghansen...@gmail.com (JIRA)















































Greg Hansen
 commented on  JENKINS-26347


Credentials not found for merge from mainline















Sorry, didn't see that you'd asked questions. Here you go:
Run on a slave:  yes
Slave is a CentOS 5.8 machine (needed by our product build)
Protocol is HTTPS
Master is not configured to be able to run the build, it's running CentOS 6.

Thanks for looking at this!



























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-plugin] (JENKINS-26458) org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy

2015-02-25 Thread fherr...@todo1.com (JIRA)















































Francisco Herrera
 commented on  JENKINS-26458


org.tmatesoft.svn.core.SVNException: svn: E155021: This client is too old to work with the working copy















I got the error after updating from version 2.4.3 to 2.5. I had to downgrade to fix the problem. Subversion client is 1.7.4.



























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] [hp-application-automation-tools-plugin] (JENKINS-26419) ResultDir and TestDir build-in UFT environment variables are set to _Path of the folder in which the test is located_

2015-02-25 Thread jonathan.cliff...@fcc-fac.ca (JIRA)















































Jon Clifford
 commented on  JENKINS-26419


*ResultDir* and *TestDir* build-in UFT environment variables are set to _Path of the folder in which the test is located_















Is this possible to be fixed or to provide a work around?  We are unable to run duplicates of the same script on different slave machines since we keep getting an error that the results folder is being used.  The error in jenkins is "The process cannot access the file 'Results.xml' because it is being used by another process"



























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] [workflow-plugin] (JENKINS-26120) Safe sleep step
















































Jesse Glick
 resolved  JENKINS-26120 as Fixed


Safe sleep step
















Change By:


Jesse Glick
(25/Feb/15 8:53 PM)




Status:


In Progress
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] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

2015-02-25 Thread michael.ne...@gmail.com (JIRA)
















































Michael Neale
 resolved  JENKINS-24338 as Won't Fix


Issues with docker permissions
















Closing this as work-around seems the "correct" thing to do. 





Change By:


Michael Neale
(25/Feb/15 8:47 PM)




Status:


Open
Resolved





Resolution:


Won't Fix



























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







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

[JIRA] [docker-build-publish-plugin] (JENKINS-25689) Multiple tagging of docker images

2015-02-25 Thread michael.ne...@gmail.com (JIRA)
















































Michael Neale
 resolved  JENKINS-25689 as Fixed


Multiple tagging of docker images
















This was addressed by a few recent pull requests and other improvements. 





Change By:


Michael Neale
(25/Feb/15 8:48 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [docker-build-publish-plugin] (JENKINS-27132) Build not properly inheriting environment

2015-02-25 Thread michael.ne...@gmail.com (JIRA)















































Michael Neale
 commented on  JENKINS-27132


Build not properly inheriting environment















Not sure what you mean by environment variables - in a docker build - it can't really be parametrised by environment variables (the idea is that it runs the same, the Dockerfile is self describing). 

Can you explain more the steps you are doing? The environment from jenkins is provided the same as for a freestyle step when running the docker command - but that won't mean anything when running a docker build. 

I am probably not understanding what you are doing exactly - I gather in your image somewhere are pre-compiled assets you need to publish? what does it look like when you script it from outside? 



























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] [hue-light-plugin] (JENKINS-22048) Hue-Light plugin doesn't work with Maven jobs
















































Francis Labrie
 resolved  JENKINS-22048 as Fixed


Hue-Light plugin doesn't work with Maven jobs
















In version 1.1.





Change By:


Francis Labrie
(25/Feb/15 8:39 PM)




Status:


Open
Resolved





Resolution:


Fixed



























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







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

[JIRA] [git-client-plugin] (JENKINS-27115) GIt polling queries wrong head

2015-02-25 Thread tfo...@osrfoundation.org (JIRA)

Tully Foote
commented on JENKINS-27115

GIt polling queries wrong head

Is this the discussion from Alexander Link you are referring to? https://issues.jenkins-ci.org/browse/JENKINS-20767

When searching for that I also found related tickets: https://issues.jenkins-ci.org/browse/JENKINS-25580 and https://issues.jenkins-ci.org/browse/JENKINS-14026

I've been trying many regex invocations. Using the java regex http://www.tutorialspoint.com/java/java_regular_expressions.htm
But it does not appear that the simple regex :branch/name works. The ls-remote gets passed the entire regex including the : and fails to match anything. And then also passes the full string through to the clone which also fails.

I think I've found that I can make it work with the wildcard evaluation using */full/branch/name, based on the first link above.

I completely understand keeping backwards compatibility so as not to break existing users relying on the behavior. However, I would like to suggest adding an option which defaults to off which can disable the legacy trimming behavior to allow users the option to avoid it if they want.

It's also really frustrating that these things are not documented in the help fields. The trimming is not mentioned in the help fields, and recommending the fully qualified paths to "avoid ambiguity" without mentioning that they are actually going to be trimmed and ambiguous is very frustrating.

From finding the other related issues, it seems that I'm not the only one encountering this problem. It would be really great to get an option to disable the trimming. With or without that updating the documentation to mention the trimming and potential work around solutions would be greatly appreciated.

[JIRA] [core] (JENKINS-22519) Jenkins Build History page: Build Status table is always empty on Safari
















































Francis Labrie
 resolved  JENKINS-22519 as Not A Defect


Jenkins Build History page: Build Status table is always empty on Safari
















Forget this report, the issue was finally related to a French localization. The following string:

Click to center timeline on event


Was translated to:

Cliquer afin de centrer le calendrier sur l''événement


But this was breaking the _javascript_ code. Adding a backslash \ prefix fix the problem:

Cliquer afin de centrer le calendrier sur l\''événement






Change By:


Francis Labrie
(25/Feb/15 8:11 PM)




Status:


Open
Resolved





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] [acceptance-test-harness] (JENKINS-27133) Explicitly declare tests requires properties to run

2015-02-25 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 created  JENKINS-27133


Explicitly declare tests requires properties to run















Issue Type:


Bug



Assignee:


Oliver Gondža



Components:


acceptance-test-harness



Created:


25/Feb/15 7:51 PM



Description:


Some tests integrates against existing services and are activated iff certain properties are provided.

Current implementation skip the test after Jenkins was started wasting a lot of time.




Project:


Jenkins



Priority:


Minor



Reporter:


Oliver Gondža

























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-22519) Jenkins Build History page: Build Status table is always empty on Safari















































Francis Labrie
 updated  JENKINS-22519


Jenkins Build History page: Build Status table is always empty on Safari
















Change By:


Francis Labrie
(25/Feb/15 7:54 PM)




Summary:


Jenkins Build History page: Build Status table is always empty
 on Safari





Environment:


Jenkins 1.
557
544 to 1.599
 running on OS X Server 10.9.2Web Browsers:
 All major,
 Safari 8.0.3
 on
 Mac
 OS X
 and Windows
 10
.
10.





Description:


Since Jenkins 1.544, the *Build Status* section below the timeline graphic on the *Jenkins Build History* page is always empty
 on Safari 8
.
0.3.
 See screenshot below. Build jobs appear successfully in the timeline, but nothing is shown in the *Build Status* table below.This issue is still present in current Jenkins 1.
577
599
.
 Below are the errors logged in the Safari browser Console:{code}[Log] locale set to en (common-content.js, line 98)[Error] SyntaxError: Unexpected identifier 'événement'. Expected '}' to end a object literal.	(fonction anonyme) (builds, line 153)[Error] ReferenceError: Can't find variable: displayBuilds	global code (builds, line 166)[Log] locale set to en (common-content.js, line 98)[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (__history__.html, line 0)[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (message-left.png, line 0)[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (message-right.png, line 0)[Log] locale set to en (common-content.js, line 98){code}The *Build Status* table is not empty using Firefox 36.0 on Mac OS X 10.10, and only one error is logged in the Console:{code}aucun élément trouvé start:1:1GET https://jenkins.mobile.cgi.com/view/Dashboard/__history__.html [HTTP/1.1 404 Not Found 31ms]{code}





Component/s:


dashboard-view-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] [dashboard-view-plugin] (JENKINS-18880) Build statistics does not display result with regex .* filter













































  
Francis Labrie
 edited a comment on  JENKINS-18880


Build statistics does not display result with  regex .* filter
















This problem has been fixed in the past, but since a month or two, Build statistics are still empty in the Jenkins 1.599 Dashboard Portlet when using a regular _expression_ filter like .*. It only work if I select jobs individually.



























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] [dashboard-view-plugin] (JENKINS-18880) Build statistics does not display result with regex .* filter















































Francis Labrie
 reopened  JENKINS-18880


Build statistics does not display result with  regex .* filter
















This problem has been fixed in the past, but since a month or two, Build statistics are still empty in the Jenkins 1.599 Dashboard Portlet when using a regular _expression_ filter like .*.





Change By:


Francis Labrie
(25/Feb/15 7:26 PM)




Resolution:


Fixed





Status:


Resolved
Reopened



























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







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

[JIRA] [dashboard-view-plugin] (JENKINS-18880) Build statistics does not display result with regex .* filter















































Francis Labrie
 updated  JENKINS-18880


Build statistics does not display result with  regex .* filter
















Change By:


Francis Labrie
(25/Feb/15 7:27 PM)




Attachment:


Capture d’écran 2015-02-25 à 2.23.00 PM.png



























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







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

[JIRA] [docker-build-publish-plugin] (JENKINS-27132) Build not properly inheriting environment

2015-02-25 Thread m...@apptentive.com (JIRA)

Mike Saffitz
created JENKINS-27132

Build not properly inheriting environment

Issue Type:

Bug

Assignee:

Michael Neale

Components:

docker-build-publish-plugin

Created:

25/Feb/15 7:27 PM

Description:

We're building a rails app into a Docker container, and as part of that in our Dockerfile we:

`RUN bundle exec rake assets:precompile`

This uses sprockets to compile the assets, generates a manifest file into the Docker image, and synchronizes the assets to S3 for exposure on the CDN. Asset synchronization occurs via credentials exposed in the environment of the user running the docker build command.

This works locally, but it appears that this plugin doesn't run the build command in the same environment that the jenkins user runs, nor does it respect the environment variables injected into the workspace by jenkins.

I'm not sure if this is a bug or a feature request, but either way, it'd be cool if this worked.

Project:

Jenkins

Labels:

envinject
environment
environment-variables

Priority:

Critical

Reporter:

Mike Saffitz

[JIRA] [docker-build-publish-plugin] (JENKINS-24338) Issues with docker permissions

2015-02-25 Thread m...@apptentive.com (JIRA)















































Mike Saffitz
 commented on  JENKINS-24338


Issues with docker permissions















Just a note that the solution Valeri Golubev posted fixed the issue for me.



























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







-- 
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-16536) PermGen leak

2015-02-25 Thread jburr...@navisite.com (JIRA)















































Jay Burrill
 commented on  JENKINS-16536


PermGen leak















I am seeing this in a new installation of Jenkins 1.599 on RHEL 6.3:

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

Stack trace

javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-1.599.jar!/jenkins/model/Jenkins/configure.jelly:59:84:  java.lang.OutOfMemoryError: PermGen space
	at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
	at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
	at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123)
	at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:46)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
	at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
	at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
	at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
	at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249)
	at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67)
	at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
	at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
	at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
	at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
	at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
	at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
	at org.eclipse.jetty.serv

[JIRA] [configure-job-column-plugin] (JENKINS-16744) crash when loading job configuration page

2015-02-25 Thread jburr...@navisite.com (JIRA)















































Jay Burrill
 commented on  JENKINS-16744


crash when loading job configuration page















I am seeing this error under a new installation of Jenkins on RHEL 6.3.  Is there a known solution?



























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-plugin] (JENKINS-27131) Possibility to get used logfile and line number of warning in logfile

2015-02-25 Thread nf...@gmx.de (JIRA)

nif y
created JENKINS-27131

Possibility to get used logfile and line number of warning in logfile

Issue Type:

Improvement

Assignee:

Ulli Hafner

Components:

warnings-plugin

Created:

25/Feb/15 6:46 PM

Description:

To due the fact that some log-files consists of warnings but neither information about source code file nor information about line number, it would be helpful to link to the log-file and the line number of the warning in the log-file instead.

e.g. @ groovy-script

...
String fileName = {selected log-file currently parsed}
String lineNumber = {lineNumber in log-file currently analyzed}
...
return new Warning(fileName, Integer.parseInt(lineNumber), "Dynamic Parser", "xyz Warning", message);

To work around the problem if the parser is analyzing stdout instead of a log-file, either stdout could be linked (if possible) or the problem should be handled in the groovy-script.

Project:

Jenkins

Priority:

Minor

Reporter:

nif y

[JIRA] [token-macro-plugin] (JENKINS-27130) Failed to load jobs after upgrading Jenkins

2015-02-25 Thread zc...@silver-peak.com (JIRA)















































Zuhao Chen
 created  JENKINS-27130


Failed to load jobs after upgrading Jenkins















Issue Type:


Bug



Assignee:


Kohsuke Kawaguchi



Components:


token-macro-plugin



Created:


25/Feb/15 6:17 PM



Description:


After I upgrade to the latest Jenkins and all plugins to latest version. I see bunch of there exception in logs.

SEVERE: Failed Loading job VXOA_Test_PyUnit_6.2
java.lang.NoClassDefFoundError: org/jenkinsci/plugins/tokenmacro/DataBoundTokenMacro
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:634)
at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138)
at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:756)
at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309)
at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365)
at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325)
at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
at hudson.plugins.emailext.EmailExtTemplateActionFactory.createFor(EmailExtTemplateActionFactory.java:35)
at hudson.model.AbstractProject.createTransientActions(AbstractProject.java:749)
at hudson.model.Project.createTransientActions(Project.java:235)
at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:739)
at hudson.model.AbstractProject.onLoad(AbstractProject.java:332)
at hudson.model.Project.onLoad(Project.java:95)
at hudson.model.Items.load(Items.java:279)
at jenkins.model.Jenkins$18.run(Jenkins.java:2655)
at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169)
at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282)
at jenkins.model.Jenkins$7.runTask(Jenkins.java:885)
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:1146)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.ClassNotFoundException: org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro
at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1375)
at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325)
at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078)
at java.lang.ClassLoader.loadClass(ClassLoader.java:266)
... 25 more
Feb 24, 2015 3:22:46 PM jenkins.InitReactorRunner$1 onTaskFailed




Project:


Jenkins



Priority:


Major



Reporter:


Zuhao Chen

























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] [robot-plugin] (JENKINS-20465) output.xml with date-timestamp not found

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-20465


output.xml with date-timestamp not found















Using filename output*.xml seems to work for me. I assume this is not a problem anymore?



























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







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

[JIRA] [timestamper-plugin] (JENKINS-27054) Radio buttons would be easier to click if associated text was part of a

2015-02-25 Thread paul.f....@gmail.com (JIRA)















































Paul Fee
 commented on  JENKINS-27054


Radio buttons would be easier to click if associated text was part of a 















I got the 1.5.16 update via the Manage Plugins page and confirmed that the enhancement worked as expected.  Thanks!



























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







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

[JIRA] [robot-plugin] (JENKINS-19024) Ability to set thresholds with test number in addition to percentage

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-19024


Ability to set thresholds with test number in addition to percentage















this has been open for a long time... Is someone still missing this feature currently?



























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] [robot-plugin] (JENKINS-23077) robotframework plugin throws exception on missing output-dir when the build fails

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-23077


robotframework plugin throws exception on missing output-dir when the build fails















Couldnt you do this so, that you would have robot tests a job that is executed automatically after your build job, if that passes? And so if the build fails, the robot job is never executed?

Am I missing something important?



























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] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
















































Marcelo Behera
 closed  JENKINS-11176 as Fixed


Promotion criteria "If the build is a release build" is broken and displays duplicated
















Change By:


Marcelo Behera
(25/Feb/15 5:34 PM)




Status:


Resolved
Closed



























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







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

[JIRA] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated













































  
Marcelo Behera
 edited a comment on  JENKINS-11176


Promotion criteria "If the build is a release build" is broken and displays duplicated
















In registerExtension ( ) method , the ReleasePromotionCondition class, put a test whether the instance of DescriptorImpl class had already been added to the list , preventing duplication of the object condition. Also changed the return type of the newInstance () method of PromotionCondition to ReleasePromotionCondition in DescriptorImpl class.

public static void registerExtension() {

	DescriptorExtensionList listPromotionCondition = PromotionCondition.all();

	if(!listPromotionCondition.contains(DescriptorImpl.class)){
   PromotionCondition.all().add(new DescriptorImpl());
	}
}

public ReleasePromotionCondition newInstance(StaplerRequest req, JSONObject formData) throws FormException {
return new ReleasePromotionCondition();
}





























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] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated













































  
Marcelo Behera
 edited a comment on  JENKINS-11176


Promotion criteria "If the build is a release build" is broken and displays duplicated
















In registerExtension ( ) method , the ReleasePromotionCondition class, put a test whether the instance of DescriptorImpl class had already been added to the list , preventing duplication of the object condition. Also changed the return type of the newInstance() method of PromotionCondition to ReleasePromotionCondition in DescriptorImpl class.

public static void registerExtension() {

	DescriptorExtensionList listPromotionCondition = PromotionCondition.all();

	if(!listPromotionCondition.contains(DescriptorImpl.class)){
   PromotionCondition.all().add(new DescriptorImpl());
	}
}

public ReleasePromotionCondition newInstance(StaplerRequest req, JSONObject formData) throws FormException {
return new ReleasePromotionCondition();
}





























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] [robot-plugin] (JENKINS-22603) Add support Dashboard View

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-22603


Add support Dashboard View















I havent used the dashboard view myself... Unless someone from Nokia requests this, I dont think we will have time to do this in near future. We are happy about all pull requests though!



























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] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
















































Marcelo Behera
 resolved  JENKINS-11176 as Fixed


Promotion criteria "If the build is a release build" is broken and displays duplicated
















No método registerExtension(), da classe ReleasePromotionCondition, coloquei um teste se a instância da classe DescriptorImpl já havia sido adicionada na lista, não permitindo a duplicação do objeto condição. Mudei também o tipo de retorno do método newInstance() de PromotionCondition para ReleasePromotionCondition na classe DescriptorImpl.


public static void registerExtension() {

	DescriptorExtensionList listPromotionCondition = PromotionCondition.all();

	if(!listPromotionCondition.contains(DescriptorImpl.class)){
   PromotionCondition.all().add(new DescriptorImpl());
	}
}

public ReleasePromotionCondition newInstance(StaplerRequest req, JSONObject formData) throws FormException {
return new ReleasePromotionCondition();
}







Change By:


Marcelo Behera
(25/Feb/15 5:31 PM)




Status:


In Progress
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] [robot-plugin] (JENKINS-26980) Enable configuration of "Robot Results" column in the default job list view

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-26980


Enable configuration of "Robot Results" column in the default job list view















Cheers, the pull request looks good. I think it is better to keep it by default, so that we dont change the behaviour for all the current users.



























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] [robot-plugin] (JENKINS-24281) Add option to move files during test result publishing

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-24281


Add option to move files during test result publishing















Could you elaborate why the copy is not enough? Wouldnt the files that are copied get removed later anyway?



























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] [robot-plugin] (JENKINS-23209) Provide a way to provide all warning that occurred in a test case

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-23209


Provide a way to provide all warning that occurred in a test case















Hi! There doesnt seem to be too much interesting in implementing this and no one at Nokia has requested this (our sponsor). But if you would like to make a pull request, we could then include this.



























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] [robot-plugin] (JENKINS-26245) Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)













































  
Jussi Malinen
 edited a comment on  JENKINS-26245


Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing
















Hi!

Typically during development you would use:
mvn hpi:run

that starts a local standalone jenkins with the current development code for robot plugin in use. The jobs that you create there are not removed when you run mvn clean, so you can keep on using the jobs you created once.

I think it would be easiest to work like that.



























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







-- 
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] [conditional-buildstep-plugin] (JENKINS-24242) On evaluation failure is not being honored

2015-02-25 Thread sushija...@gmail.com (JIRA)















































Jason Tsai
 commented on  JENKINS-24242


On evaluation failure is not being honored















is it possible for me to mark the status as "ABORTED" or "SKIPPED" (show a grey ball in status) instead of the default "SUCCESS"? (blue ball)




























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] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated















































Marcelo Behera
 started work on  JENKINS-11176


Promotion criteria "If the build is a release build" is broken and displays duplicated
















Change By:


Marcelo Behera
(25/Feb/15 5:22 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] [promoted-builds-plugin] (JENKINS-11176) Promotion criteria "If the build is a release build" is broken and displays duplicated
















































Marcelo Behera
 assigned  JENKINS-11176 to Marcelo Behera



Promotion criteria "If the build is a release build" is broken and displays duplicated
















Change By:


Marcelo Behera
(25/Feb/15 5:21 PM)




Assignee:


Marcelo Behera



























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] [robot-plugin] (JENKINS-26245) Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-26245


Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing















And that bug about stapler you run into, I have found it earlier and am cleaning up my fix for commit right now. It should not show up if you use mvn hpi:run.



























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] [robot-plugin] (JENKINS-26245) Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing

2015-02-25 Thread jussi.ao.mali...@gmail.com (JIRA)















































Jussi Malinen
 commented on  JENKINS-26245


Add option to show "all tests" or "critical tests" in the Listviewcolumn that shows overall passed/failed tests in project listing















Hi!

Typically during development you would use:
mvn hpi:run

that start a local standalone jenkins with the latest plugin in use. The jobs that you create there are not removed when you run mvn clean, so you can keep on using the jobs you created once.

I think it would be easiest to work like that.



























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







-- 
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-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1

2015-02-25 Thread paul.sokolov...@linaro.org (JIRA)















































Paul Sokolovsky
 updated  JENKINS-27093


Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1
















build.xml's from builds #159, #160 of the job above are attached.





Change By:


Paul Sokolovsky
(25/Feb/15 5:10 PM)




Attachment:


159-build.xml





Attachment:


160-build.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] [ec2-plugin] (JENKINS-26716) Jobs throttled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary

2015-02-25 Thread tba...@circle.com (JIRA)















































Trevor Baker
 updated  JENKINS-26716


Jobs throttled via the Throttle Concurrent Builds plugin fail to launch new ec2 provisioned slaves when necessary
















Change By:


Trevor Baker
(25/Feb/15 4:54 PM)




Description:


When concurrent jobs are throttled across categories new ec2 provisioned slaves are not launched when they are required.  The ec2 plugin should
 not
 detect that even though there may be executors available that they can not run the job(s) due to concurrent throttling.  These two plugins should interop as expected.



























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-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1

2015-02-25 Thread paul.sokolov...@linaro.org (JIRA)















































Paul Sokolovsky
 commented on  JENKINS-27093


Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1















Thanks for the replies and commits already made. So, our situation is that we have pretty busy production Jenkins system, so there's only limited experimentation can be done there, and in limited time I had to look into this issue, I traced it just to the source line in the original description above. This is also 1st time I looked into SCM polling, so I don't know how related data is stored and other details.

But job we had issues to is actually public: https://ci.linaro.org/job/trigger-linux-ltsi/ . As you can see (note: builds in question may expire in a week or two), from build #132 Feb 23, 2015 11:33:10 AM to build #161 Feb 23, 2015 1:58:09 PM , build triggered every 5 mins, which is SCM polling period for that job. But typical poll log looks like: https://ci.linaro.org/job/trigger-linux-ltsi/160/pollingLog/ (content quoted above in the original description).

Kanstantsin: The repo is public, running git command from poll log, I get the expected output (I also thought that maybe there's stray space or something gets parsed, but I confirmed it all looks ok). Will try to look up those build.xml's as a next step.


$ /usr/bin/git -c core.askpass=true ls-remote -h git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
8e63197ffe7750c94c8ea9d159ce3e46a76bfcf2	refs/heads/linux-2.6.11.y
d04a37911968d919fa842ad40fa9e9ff1dd10904	refs/heads/linux-2.6.12.y
816e9c6c226227c4862b2067aace0f450cc92635	refs/heads/linux-2.6.13.y
789f444285aedfb04af7aa3748aa52e99ac4bd8f	refs/heads/linux-2.6.14.y
f70602f4f6248735a02c61a1323c9151a33a3775	refs/heads/linux-2.6.15.y
6b0daf99dd2392b024bdca05530e4e761bc3cdae	refs/heads/linux-2.6.16.y
78ace17e51d4968ed2355e8f708d233d1cc37f6d	refs/heads/linux-2.6.17.y
299a2479bca6211f845158761920ec480f35a229	refs/heads/linux-2.6.18.y
09780ab3b26507776671900e0ed7920f297498ed	refs/heads/linux-2.6.19.y
f3815da6b4fd508cc3574399248e2e15cb8a617f	refs/heads/linux-2.6.20.y
a31a9035702124423c3aa5aa848937f165753a4f	refs/heads/linux-2.6.21.y
37579d1574f6c18f1f648201c6b0850ac94094cd	refs/heads/linux-2.6.22.y
6531868a73a6c91bf0e3e60ded7d1440ee24dfa8	refs/heads/linux-2.6.23.y
928bb8c418b5f9e96dbccc8d7eafb6635ae81548	refs/heads/linux-2.6.24.y
00935daeb04cd54a67b66c9e3babc23389251a98	refs/heads/linux-2.6.25.y
63e0e67b17dc233f93f709610971bbfadc97f75e	refs/heads/linux-2.6.26.y
bc4e1a77b06519a01e7aed1125695598e27ddeb2	refs/heads/linux-2.6.27.y
5861c853a3f529b9c6a338dd7c4a7afec397ea7a	refs/heads/linux-2.6.28.y
12010107aaf417503b7e413d84f2554080aebfe2	refs/heads/linux-2.6.29.y
0d0675cf44c85bd3c0d891845aa02f9249cd7c68	refs/heads/linux-2.6.30.y
a389e98d2c6e1900f035befe215f541436bcb0b2	refs/heads/linux-2.6.31.y
3bd0d1ad14c3566107e391732e4df658b005ad67	refs/heads/linux-2.6.32.y
86a705267a2a502a3d62ef0797e449677b25835f	refs/heads/linux-2.6.33.y
5878e067ecac4bd2320e933ec485c01190a5b881	refs/heads/linux-2.6.34.y
675f7660ffb0e1880011f6b3c4f9ac241491e3cd	refs/heads/linux-2.6.35.y
69ad303ab8321656d6144d13b2444a5595bb6581	refs/heads/linux-2.6.36.y
e396c9d8699c95d52b2abcc2d4d5f9616e839734	refs/heads/linux-2.6.37.y
4b7a6d2528bfb625cc359d89ac16439b0ec744ea	refs/heads/linux-2.6.38.y
ea0dc0dc1c1dca25e50384e300a528db57ee7de5	refs/heads/linux-2.6.39.y
5dba9ddd98cbc7ad319d687887981a0ea0062c75	refs/heads/linux-3.0.y
9bb1282f6a7754955c18be912fbc2b55d133f1b9	refs/heads/linux-3.1.y
5cfc71ce138e79ceb6250f78137dd05ba52e9d34	refs/heads/linux-3.10.y
5ee54f38171b9b3541c5e9cf9c3a9e53455fd8b4	refs/heads/linux-3.11.y
22ccf8f1a5450ac5a6bc2bb519699838017ce1ea	refs/heads/linux-3.12.y
2d20120bba8475c963a8d28dd0ffa13637fa3ad7	refs/heads/linux-3.13.y
a74f1d1204a5c892466b52ac68ee6443c1e459d7	refs/heads/linux-3.14.y
f35b5e46feabab668a44df5b33f3558629f94dfc	refs/heads/linux-3.15.y
d0335e4feea0d3f7a8af3116c5dc166239da7521	refs/heads/linux-3.16.y
bc15d4627aa8f562a1c5ec9d84076b8db25bab31	refs/heads/linux-3.17.y
a17f9bf1f7cd3412b9920577a7c0ec34cb81b233	refs/heads/linux-3.18.y
bfa76d49576599a4b9f9b7a71f23d73d6dcff735	refs/heads/linux-3.19.y
fd623507bdcee1f7a387ae86adb7a66b431dd056	refs/heads/linux-3.2.y
845720650c557a75262b629b0bc228fffcf64638	refs/heads/linux-3.3.y
28895317f9a7d726cd13fc9b5447cb5dcb5cd22c	refs/heads/linux-3.4.y
f2b152564afdf9c9917c17d1c41c1082c82067bd	refs/heads/linux-3.5.y
b2824f4e0990716407b0c0e7acee75bb6353febf	refs/heads/linux-3.6.y
356d8c6fb2a7cf49e836742738a8b9a47e77cfea	refs/heads/linux-3.7.

[JIRA] [workflow-plugin] (JENKINS-27129) More consistent use of PauseAction















































Jesse Glick
 created  JENKINS-27129


More consistent use of PauseAction















Issue Type:


Bug



Assignee:


Jesse Glick



Components:


workflow-plugin



Created:


25/Feb/15 4:24 PM



Description:


Currently PauseAction is added only by InputStep. But it makes sense to add also for SleepStep (JENKINS-26120) and WaitForConditionStep (JENKINS-25570), as well as for the proposed wait step (JENKINS-27127). This would allow visualizations to give a better picture of which flow builds and branches were active at a given time, compute running time more accurately, etc.




Project:


Jenkins



Priority:


Minor



Reporter:


Jesse Glick

























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] [other] (JENKINS-27128) Compress Build Log Plugin: Logs of Multi-configuration jobs are not compressed

2015-02-25 Thread vda...@vizrt.com (JIRA)















































Valentin David
 created  JENKINS-27128


Compress Build Log Plugin: Logs of Multi-configuration jobs are not compressed















Issue Type:


Bug



Assignee:


Daniel Beck



Components:


other



Created:


25/Feb/15 4:14 PM



Description:


After enabling the plugin, and enabling compression in the multi-configuration job, new build of jobs get only the main log file compressed on the filesystem. Logs for each combination are left uncompressed on the filesystem.

Tested with version 1.0 of the plugin with Jenkins 1.599 on Debian Jessie.

Note: component compress-buildlog-plugin is not available, so it is filed under other.




Project:


Jenkins



Priority:


Minor



Reporter:


Valentin David

























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-client-plugin] (JENKINS-27093) Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1

2015-02-25 Thread gentoo.inte...@gmail.com (JIRA)













































  
Kanstantsin Shautsou
 edited a comment on  JENKINS-27093


Spurious gits scm poll change detection with git-plugin 2.3.5 & git-client-plugin 1.16.1
















Hi, Paul, could you provide two consecutive build.xml files (you can cut any private info) that were triggered and the result of manual run for git command from polling log?



























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







-- 
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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be

2015-02-25 Thread lorelei.mccol...@gmail.com (JIRA)















































Lorelei McCollum
 commented on  JENKINS-27126


New Scroll bar in Jenkins Build history is showing when shouldn't be















Chrome 40 no description is set
no custom JS or CSS running, none of those themes



























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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be















































Daniel Beck
 commented on  JENKINS-27126


New Scroll bar in Jenkins Build history is showing when shouldn't be















What web browser is this? What is the description used, if any? Any custom JS/CSS running for Jenkins (e.g. Simple Theme Plugin, Greasemonkey)?



























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-27126) New Scroll bar in Jenkins Build history is showing when shouldn't be















































Daniel Beck
 updated  JENKINS-27126


New Scroll bar in Jenkins Build history is showing when shouldn't be
















Change By:


Daniel Beck
(25/Feb/15 3:49 PM)




Labels:


user-experience





Assignee:


Tom FENNELLY



























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] [compress-artifacts-plugin] (JENKINS-27042) java.util.zip.ZipException thrown when reading artifacts from archive larger than 4G

2015-02-25 Thread ogon...@gmail.com (JIRA)















































Oliver Gondža
 commented on  JENKINS-27042


java.util.zip.ZipException thrown when reading artifacts from archive larger than 4G















Fixed in https://github.com/jenkinsci/compress-artifacts-plugin/pull/5



























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] [workflow-plugin] (JENKINS-27127) wait/notify steps