[JIRA] [matrix-project-plugin] (JENKINS-34758) Parameters are not passed to child jobs in multi-configuration projects

2016-05-16 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-34758 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Parameters are not passed to child jobs in multi-configuration projects  
 
 
 
 
 
 
 
 
 
 
I upgraded to Jenkins 2.4 and my matrix jobs just stopped working! 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [thinBackup] (JENKINS-12096) ThinBackup Worker Thread thread is still running. Execution aborted.

2016-03-03 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-12096 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: ThinBackup Worker Thread thread is still running. Execution aborted.  
 
 
 
 
 
 
 
 
 
 
Experience this issue as well. Jenkins 1.643 ThinBackup 1.7.4 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2016-02-02 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-24832 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed maven builds using -T are showing up as Aborted  
 
 
 
 
 
 
 
 
 
 
Any update on this one? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream

2016-01-21 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-21905 
 
 
 
  intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Priority:
 
 Major Critical 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream

2016-01-06 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-21905 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream  
 
 
 
 
 
 
 
 
 
 
experience the same issue on rhel slave Jenkins 1.643 CopyArtifacts plugin 1.36.1 
ERROR: Failed to archive artifacts: logs/*/ 17:48:30 java.io.IOException: java.io.IOException: Failed to extract xxx transfer of 21 files 17:48:30 at hudson.FilePath.readFromTar(FilePath.java:2300) 17:48:30 at hudson.FilePath.copyRecursiveTo(FilePath.java:2209) 17:48:30 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 17:48:30 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:236) 17:48:30 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) 17:48:30 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) 17:48:30 at hudson.model.Build$BuildExecution.post2(Build.java:185) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) 17:48:30 at hudson.model.Run.execute(Run.java:1763) 17:48:30 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 17:48:30 at hudson.model.ResourceController.execute(ResourceController.java:98) 17:48:30 at hudson.model.Executor.run(Executor.java:410) 17:48:30 Caused by: java.io.EOFException: Unexpected end of ZLIB input stream 17:48:30 at com.jcraft.jzlib.InflaterInputStream.fill(InflaterInputStream.java:186) 17:48:30 at com.jcraft.jzlib.InflaterInputStream.read(InflaterInputStream.java:106) 17:48:30 at org.apache.commons.compress.archivers.tar.TarArchiveInputStream.read(TarArchiveInputStream.java:614) 17:48:30 at java.io.InputStream.read(InputStream.java:101) 17:48:30 at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1792) 17:48:30 at org.apache.commons.io.IOUtils.copyLarge(IOUtils.java:1769) 17:48:30 at org.apache.commons.io.IOUtils.copy(IOUtils.java:1744) 17:48:30 at hudson.util.IOUtils.copy(IOUtils.java:40) 17:48:30 at hudson.FilePath.readFromTar(FilePath.java:2290) 17:48:30 ... 13 more 17:48:30  17:48:30 at hudson.FilePath.copyRecursiveTo(FilePath.java:2216) 17:48:30 at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:61) 17:48:30 at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:236) 17:48:30 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:78) 17:48:30 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:782) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:723) 17:48:30 at hudson.model.Build$BuildExecution.post2(Build.java:185) 17:48:30 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:668) 17:48:30 at hudson.model.Run.execute(Run.java:1763) 17:48:30 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) 17:48:30 at hudson.model.ResourceController.execute(ResourceController.java:98) 17:48:30 at hudson.model.Executor.run(Executor.java:410) 17:48:30 Caused by: java.util.concurrent.ExecutionException: java.io.IOException: This archives contains unclosed entries. 17:48:30 at hudson.remoting.Channel$2.adapt(Channel.java:813) 17:48:30 at hudson.remoting.Channel$2.adapt(Channel.java:808) 17:48:30 at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59) 17:48:30 at hudson.FilePath.copyRecursiveTo(FilePath.java:2212) 17:48:30 ... 12 more 17:48:30 Caused by: java.io.IOException: This archives contains unclosed entries. 17:48:30 at org.apache.commons.compress.archivers.tar.TarArchiveOutputStream.finish(TarArchiveOutputStream.java

[JIRA] [copyartifact-plugin] (JENKINS-21905) intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream

2016-01-06 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-21905 
 
 
 
  intermittent Failed to archive artifacts: Failed to extract caused by Unexpected end of ZLIB input stream  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Component/s:
 
 copyartifact-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [allure-plugin] (JENKINS-32224) Correct support for matrix job

2015-12-29 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32224 
 
 
 
  Correct support for matrix job  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Environment:
 
 Jenkins 1.643 Allure Report plugin 2.10 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [allure-plugin] (JENKINS-32224) Correct support for matrix job

2015-12-29 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32224 
 
 
 
  Correct support for matrix job  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Artem Eroshenko 
 
 
 

Components:
 

 allure-plugin 
 
 
 

Created:
 

 29/Dec/15 10:54 PM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Liya Katz 
 
 
 
 
 
 
 
 
 
 
I have a matrix job that runs on 2 nodes, each one runs the same set of tests and creates the report. The Allure report is shown just fine for each node build.  For the "main" build: If both nodes were successful (or unstable), the report just stuck forever on "Loading" If one of them has failed and no report was created, the "main" build report shows the successful node build report. Both are confusing  I suggest to add an option to show merged report on the main build - probably should be the default option, alternative should be not to show Allure report on the main build at all 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
  

[JIRA] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643

2015-12-29 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz closed an issue as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32219 
 
 
 
  Allure Reports are not visible after upgrading to Jenkins 1.643  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Status:
 
 Resolved Closed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643

2015-12-29 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz resolved as Fixed 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32219 
 
 
 
  Allure Reports are not visible after upgrading to Jenkins 1.643  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Status:
 
 Open Resolved 
 
 
 

Resolution:
 
 Fixed 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643

2015-12-29 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-32219 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Allure Reports are not visible after upgrading to Jenkins 1.643  
 
 
 
 
 
 
 
 
 
 
Thank you! It works. Please update Jenkins plugin wiki page with this info 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [allure-plugin] (JENKINS-32219) Allure Reports are not visible after upgrading to Jenkins 1.643

2015-12-29 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32219 
 
 
 
  Allure Reports are not visible after upgrading to Jenkins 1.643  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Artem Eroshenko 
 
 
 

Components:
 

 allure-plugin 
 
 
 

Created:
 

 29/Dec/15 3:43 PM 
 
 
 

Environment:
 

 Jenkins 1.643  Allure Report plugin 2.8 and 2.10 
 
 
 

Priority:
 
  Blocker 
 
 
 

Reporter:
 
 Liya Katz 
 
 
 
 
 
 
 
 
 
 
When trying to open Allure Report, it stuck on "Loading" forever. Same for new and old reports (those that were ok before Jenkins upgrade) 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
  

[JIRA] [maven-plugin] (JENKINS-24832) Failed maven builds using -T are showing up as Aborted

2015-12-22 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-24832 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Failed maven builds using -T are showing up as Aborted  
 
 
 
 
 
 
 
 
 
 
Experiencing the same issue with Jenkins 1.627, Maven plugin 2.12.1 It is critical because developers are not notified when builds are aborted (usually manual action) If there is a fix, why is it still not merged? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [promoted-builds-plugin] (JENKINS-32127) Promoted build should be signed as "keep forever" and not deleted automatically

2015-12-17 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32127 
 
 
 
  Promoted build should be signed as "keep forever" and not deleted automatically  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Summary:
 
 Promoted build should  not  be signed as "keep forever" and not deleted automatically 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [promoted-builds-plugin] (JENKINS-32127) Promoted build should not be signed as "keep forever" and not deleted automatically

2015-12-17 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-32127 
 
 
 
  Promoted build should not be signed as "keep forever" and not deleted automatically  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Oleg Nenashev 
 
 
 

Components:
 

 promoted-builds-plugin 
 
 
 

Created:
 

 17/Dec/15 3:40 PM 
 
 
 

Environment:
 

 Jenkins 1.627  promoted-builds-plugin 2.24 
 
 
 

Priority:
 
  Critical 
 
 
 

Reporter:
 
 Liya Katz 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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

[JIRA] [s3-plugin] (JENKINS-31556) Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off

2015-11-15 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31556 
 
 
 
  Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 
 
 
 
 
 
 
 s3-plugin version is 0.8Works fine if 'Manage artifacts' is off 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [s3-plugin] (JENKINS-31556) Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off

2015-11-15 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-31556 
 
 
 
  Directory structure is ignored when files are copied to S3 if 'Manage artifacts' is on and 'Flatten directories' is off  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Michael Watt 
 
 
 

Components:
 

 s3-plugin 
 
 
 

Created:
 

 15/Nov/15 11:17 AM 
 
 
 

Priority:
 
  Major 
 
 
 

Reporter:
 
 Liya Katz 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

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





-- 
You received

[JIRA] [maven-plugin] (JENKINS-20413) Maven plugin don't take into account maven-deploy-plugin skip option

2015-10-07 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-20413 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Maven plugin don't take into account maven-deploy-plugin skip option  
 
 
 
 
 
 
 
 
 
 
While some of my poms have property: true  (or skip=true in maven-deploy-plugin configuration) 
deploy is skipped when running maven commandline, but when using a post-build step 'Deploy artifacts to Maven repository' in Jenkins, all artifacts are deploy, skip is ignored 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-20413) Maven plugin don't take into account maven-deploy-plugin skip option

2015-10-07 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-20413 
 
 
 
  Maven plugin don't take into account maven-deploy-plugin skip option  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Priority:
 
 Minor Major 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [maven-plugin] (JENKINS-20413) Maven plugin don't take into account maven-deploy-plugin skip option

2015-10-07 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-20413 
 
 
 
  Maven plugin don't take into account maven-deploy-plugin skip option  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Component/s:
 
 maven-deployment-linker-plugin 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins

2015-06-21 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz edited a comment on  JENKINS-27282 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github Webhook not working after upgrade Jenkins and plugins  
 
 
 
 
 
 
 
 
 
 Latest git.hpi from the job workspace (https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ws/target/git.hpi) doesn't work for me with Jenkins 1.609.1I can see in the log: _Received {{Received  POST for https://github.com/xxx/vvvJun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayloadReceived POST for https://github.com/xxx/vvvJun 21, 2015 10:57:47 AM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorFailed to instantiate optional component com.cloudbees.jenkins.GitHubRepositoryNameContributor$FromMultiSCM; skippingJun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayloadPoked vvvJun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayloadPoked  vvv_  vvv}} But nothing happens, the job vvv doesn't run 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins

2015-06-21 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz edited a comment on  JENKINS-27282 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github Webhook not working after upgrade Jenkins and plugins  
 
 
 
 
 
 
 
 
 
 Latest git.hpi from the job workspace (https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ws/target/git.hpi) doesn't work for me with Jenkins 1.609.1I can see in the log: {{ Received POST for https://github.com/xxx/vvvJun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayloadReceived POST for https://github.com/xxx/vvvJun 21, 2015 10:57:47 AM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 errorFailed to instantiate optional component com.cloudbees.jenkins.GitHubRepositoryNameContributor$FromMultiSCM; skippingJun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayloadPoked vvvJun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayloadPoked vvv }} But nothing happens, the job vvv doesn't run 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins

2015-06-21 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-27282 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github Webhook not working after upgrade Jenkins and plugins  
 
 
 
 
 
 
 
 
 
 
Latest git.hpi from the job workspace (https://jenkins.ci.cloudbees.com/job/plugins/job/git-plugin/ws/target/git.hpi) doesn't work for me with Jenkins 1.609.1 I can see in the log: _Received POST for https://github.com/xxx/vvv Jun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Received POST for https://github.com/xxx/vvv Jun 21, 2015 10:57:47 AM WARNING hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error Failed to instantiate optional component com.cloudbees.jenkins.GitHubRepositoryNameContributor$FromMultiSCM; skipping Jun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked vvv Jun 21, 2015 10:57:47 AM INFO com.cloudbees.jenkins.GitHubWebHook processGitHubPayload Poked vvv_ 
But nothing happens, the job vvv doesn't run 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins

2015-06-21 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-27282 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github Webhook not working after upgrade Jenkins and plugins  
 
 
 
 
 
 
 
 
 
 
I meant from specific build you've checked..  The artifacts are not archived there. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins

2015-06-20 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-27282 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github Webhook not working after upgrade Jenkins and plugins  
 
 
 
 
 
 
 
 
 
 
Where can I download the version that works? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-22578) Nothing happens when POST to jenkins github-webhook url

2015-06-13 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-22578 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Nothing happens when POST to jenkins github-webhook url  
 
 
 
 
 
 
 
 
 
 
Had the same problem in Jenkins 1.609.1 (latest stable) with plugins: Git plugin 2.3.5 GitHub plugin 1.11.3 Git Client 1.17.1 GitHub Api 1.68 
Downgrade to the previous stable release (Jenkins 1.596.3) without changing any plugin solved the problem - it looks like core and not a plugin problem 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-22578) Nothing happens when POST to jenkins github-webhook url

2015-06-13 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-22578 
 
 
 
  Nothing happens when POST to jenkins github-webhook url  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-27282) Github Webhook not working after upgrade Jenkins and plugins

2015-06-13 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-27282 
 
 
 
  Github Webhook not working after upgrade Jenkins and plugins  
 
 
 
 
 
 
 
 
 

Change By:
 
 Liya Katz 
 
 
 

Component/s:
 
 core 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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] [git-plugin] (JENKINS-27282) Github Webhook not working after upgrade Jenkins and plugins

2015-06-13 Thread l...@tikalk.com (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Liya Katz commented on  JENKINS-27282 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Github Webhook not working after upgrade Jenkins and plugins  
 
 
 
 
 
 
 
 
 
 
Had the same problem in Jenkins 1.609.1 (latest stable) with plugins: Git plugin 2.3.5 GitHub plugin 1.11.3 Git Client 1.17.1 GitHub Api 1.68 
Downgrade to the previous stable release (Jenkins 1.596.3) without changing any plugin solved the problem - it looks like core and not a plugin problem 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-blocker-plugin] (JENKINS-26850) Add plugin parameter "Block only if job run on the same node"

2015-02-08 Thread l...@tikalk.com (JIRA)














































Liya Katz
 created  JENKINS-26850


Add plugin parameter "Block only if job run on the same node"















Issue Type:


Improvement



Assignee:


Unassigned


Components:


build-blocker-plugin



Created:


08/Feb/15 9:31 AM



Project:


Jenkins



Priority:


Critical



Reporter:


Liya Katz

























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-plugin] (JENKINS-18125) Changelog empty or contains all changes

2015-01-13 Thread l...@tikalk.com (JIRA)














































Liya Katz
 updated  JENKINS-18125


Changelog empty or contains all changes
















Change By:


Liya Katz
(13/Jan/15 9:41 AM)




Environment:


Jenkins
 LTS
 1.
509.1
595
Git plugin:
 1
 2
.
3.
4
Git client plugin 1
.
1.5.
0
GitHub API plugin 1.59GitHub Plugin 1.10GitHub Pull Request Builder 1.16-6





Priority:


Major
Blocker



























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-plugin] (JENKINS-18125) Changelog empty or contains all changes

2015-01-13 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-18125


Changelog empty or contains all changes















Do you have any estimation when it will be 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-plugin] (JENKINS-18125) Changelog empty or contains all changes

2015-01-11 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-18125


Changelog empty or contains all changes















I have a maven job that is configured to run on creating or changing of Pull Request in GitHub (Enterprise), and I would like this job to run maven build incrementally - build and run unit tests only for modules that were changed by this Pull Request.
At the moment the changelog is always empty, so build runs for all modules and takes too long.

Is there any information that can be helpful? Build 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] [git-plugin] (JENKINS-18125) Changelog empty or contains all changes

2015-01-11 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-18125


Changelog empty or contains all changes















We also need it for the incremental build, and it's really bad..



























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] [jenkins-multijob-plugin] (JENKINS-21646) ClassCastException with Maven Project

2014-02-05 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-21646


ClassCastException with Maven Project















Please add your installation details + Jenkins version + Multijob plugin version



























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







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


[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered

2013-12-17 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-20569


Polling with excluded regions don't prevent job triggered















I agree that new features should be be "promoted", but in this case they cause other important features to stop working. 
You have to mention this limitation when include/exclude regions are chosen.



























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







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


[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered

2013-12-15 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-20569


Polling with excluded regions don't prevent job triggered















Polling using workspace should be the default behavior (backward compatibility!) and "remote Polling" should be an option 



























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







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


[JIRA] [git] (JENKINS-20569) Polling with excluded regions don't prevent job triggered

2013-11-18 Thread l...@tikalk.com (JIRA)














































Liya Katz
 updated  JENKINS-20569


Polling with excluded regions don't prevent job triggered
















Change By:


Liya Katz
(19/Nov/13 7:48 AM)




Priority:


Critical
Blocker



























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







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


[JIRA] [jenkins-multijob-plugin] (JENKINS-17295) 'Disable Project' button does not appear on MultiJob job page

2013-07-29 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-17295


'Disable Project' button does not appear on MultiJob job page















In version 1.9 of the plugin there is no 'Disable Project' - which version do you use?



























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-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow

2013-06-25 Thread l...@tikalk.com (JIRA)














































Liya Katz
 updated  JENKINS-9120


RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow
















Change By:


Liya Katz
(26/Jun/13 6:41 AM)




Priority:


Minor
Critical



























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-9120) RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow

2013-06-25 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-9120


RingBufferLogHandler throws ArrayIndexOutOfBoundsException after int-overflow















Jenkins 1.511 on Centos 5.6 - same problem.
Log is full of these exceptions and Jenkins is stuck. Only restarting service solves the issue. 



























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







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


[JIRA] [core] (JENKINS-17741) After upgrade to 1.511 all JDK installation disappeared from Jenkins system configuration

2013-04-24 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-17741


After upgrade to 1.511 all JDK installation disappeared from Jenkins system configuration















by "slaves tools configuration became messed up" I mean:
we have 4 tools defined for each linux slave:
(JDK)jdk_6u24 = "/opt/jdk_6u24"
(Ant) ant1.8 = "/opt/ant1.8"
(JDK)jdk_6u31 = "/opt/jdk_6u31"
(Maven) maven3.0.3 = "/opt/maven"

After the upgrade it appeared as:
(Ant) ant1.8 = "/opt/jdk_6u24"
(Maven) maven3.0.3 = "/opt/ant1.8"

JDK installation names were removed, but the paths were mapped to the wrong tool names.




























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-17741) After upgrade to 1.511 all JDK installation disappeared from Jenkins system configuration

2013-04-24 Thread l...@tikalk.com (JIRA)














































Liya Katz
 created  JENKINS-17741


After upgrade to 1.511 all JDK installation disappeared from Jenkins system configuration















Issue Type:


Bug



Assignee:


Unassigned


Components:


core



Created:


24/Apr/13 7:07 PM



Description:


After upgrade to 1.511 all JDK installation disappeared from Jenkins system configuration. It caused all slaves tools configuration to become messed up and jobs to loose their jdk configurations as well, which caused builds to fail.

Fortunately, slaves and jobs configurations were not changed, so after defining system JDK installations again, all came back to normal.




Project:


Jenkins



Priority:


Critical



Reporter:


Liya Katz

























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







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


[JIRA] (JENKINS-14825) winstone.ClientSocketException: Failed to write to client after upgrade to 1.477

2013-03-24 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-14825


winstone.ClientSocketException: Failed to write to client after upgrade to 1.477















See these errors in jenkins log at 1.505 while GUI is stuck



























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







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


[JIRA] (JENKINS-17295) 'Disable Project' button does not appear on MultiJob job page

2013-03-20 Thread l...@tikalk.com (JIRA)














































Liya Katz
 created  JENKINS-17295


'Disable Project' button does not appear on MultiJob job page















Issue Type:


Bug



Assignee:


Unassigned


Components:


jenkins-multijob-plugin



Created:


20/Mar/13 4:57 PM



Project:


Jenkins



Priority:


Minor



Reporter:


Liya Katz

























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







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


[JIRA] (JENKINS-14336) Too many open files upon HTTP listener init or shutdown

2013-03-19 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-14336


Too many open files upon HTTP listener init or shutdown















same with Jenkins 1.505 on Centos 5.6 x86_64



























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







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


[JIRA] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result

2013-03-19 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-15518


Jenkins Cobertura-1.7 fails to get the coverage result















Downgrading to 1.7.1 has solved the problem



























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







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


[JIRA] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result

2013-03-19 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-15518


Jenkins Cobertura-1.7 fails to get the coverage result















needless to say that the /opt/jenkins/jobs/xxx/workspace/xxx/xxx/target/coverage/index.html exists..



























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







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


[JIRA] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result

2013-03-18 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-15518


Jenkins Cobertura-1.7 fails to get the coverage result















[Cobertura] Publishing Cobertura coverage report...
FATAL: Unable to find coverage results
java.io.IOException: /opt/jenkins/jobs/xxx/workspace/xxx/xxx/target/coverage/index.html is not a cobertura coverage report, please check your report pattern
	at hudson.plugins.cobertura.CoberturaPublisher$ParseReportCallable.invoke(CoberturaPublisher.java:546)
	at hudson.plugins.cobertura.CoberturaPublisher$ParseReportCallable.invoke(CoberturaPublisher.java:519)
	at hudson.FilePath.act(FilePath.java:865)
	at hudson.FilePath.act(FilePath.java:838)
	at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:337)
	at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36)
	at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814)
	at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786)
	at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:947)
	at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733)
	at hudson.model.Run.execute(Run.java:1592)
	at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477)
	at hudson.model.ResourceController.execute(ResourceController.java:88)
	at hudson.model.Executor.run(Executor.java:237)
[Cobertura] No coverage results were found using the pattern '**/target/coverage/index.html' relative to '/opt/jenkins/jobs/xxx/workspace'.  Did you enter a pattern relative to the correct directory?  Did you generate the XML report(s) for Cobertura?
[Cobertura] Skipped cobertura reports.
Build step 'Publish Cobertura Coverage Report' changed build result to FAILURE



























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







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


[JIRA] (JENKINS-15518) Jenkins Cobertura-1.7 fails to get the coverage result

2013-03-17 Thread l...@tikalk.com (JIRA)














































Liya Katz
 reopened  JENKINS-15518


Jenkins Cobertura-1.7 fails to get the coverage result
















Got this error after upgrade to 1.8





Change By:


Liya Katz
(17/Mar/13 2:37 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/groups/opt_out.
 
 


[JIRA] (JENKINS-16941) Git publisher post build action fails on slave agent - unable to serialize

2013-03-17 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-16941


Git publisher post build action fails on slave agent - unable to serialize















same problem with 1.3.0:
build has failed on rebase
Downgrade to 1.1.26 has solved the problem



























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







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


[JIRA] (JENKINS-15956) Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded

2013-02-13 Thread l...@tikalk.com (JIRA)















































Liya Katz
 resolved  JENKINS-15956 as Fixed


Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded
















verified





Change By:


Liya Katz
(13/Feb/13 3:59 PM)




Status:


Open
Resolved





Fix Version/s:


current





Resolution:


Fixed



























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







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


[JIRA] (JENKINS-14473) Jenkins server memory leak

2012-12-03 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-14473


Jenkins server memory leak















Upgrading to 1.492 (from 1.473) has solved this problem for us.



























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






[JIRA] (JENKINS-15956) Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded

2012-11-28 Thread l...@tikalk.com (JIRA)














































Liya Katz
 created  JENKINS-15956


Backward compatability: after upgrade from 1.5 to 1.7 child job parameters are not loaded















Issue Type:


Bug



Assignee:


Roni Licht



Components:


jenkins-multijob-plugin



Created:


28/Nov/12 3:39 PM



Environment:


MultiJob version 1.7




Project:


Jenkins



Priority:


Critical



Reporter:


Liya Katz

























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






[JIRA] (JENKINS-14204) jenkins-multijob-plugin - The MultiJob shouldn't consume an executor

2012-11-20 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-14204


jenkins-multijob-plugin - The MultiJob shouldn't consume an executor















MultiJob should consume an executer since it can have steps that are not MultiJob phases



























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






[JIRA] (JENKINS-14204) jenkins-multijob-plugin - The MultiJob shouldn't consume an executor

2012-11-20 Thread l...@tikalk.com (JIRA)















































Liya Katz
 resolved  JENKINS-14204 as Not A Defect


jenkins-multijob-plugin - The MultiJob shouldn't consume an executor
















Change By:


Liya Katz
(20/Nov/12 12:10 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






[JIRA] (JENKINS-15646) Not all the jobs are displayed all the time

2012-10-28 Thread l...@tikalk.com (JIRA)














































Liya Katz
 created  JENKINS-15646


Not all the jobs are displayed all the time















Issue Type:


Bug



Affects Versions:


current



Assignee:


Christian Pelster



Components:


walldisplay



Created:


28/Oct/12 9:27 AM



Description:


Since upgrade to 0.15 (from 0.12) not all the jobs are displayed all the time. For example, If there are 5 jobs in the view, sometimes it shows one, sometimes three, sometimes all.
The plugin is configured to display all jobs.
Tried to configure 'Active this month' (all jobs run at least daily), didn't help.




Project:


Jenkins



Priority:


Critical



Reporter:


Liya Katz

























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






[JIRA] (JENKINS-13000) Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin (0.2) are not detected by the remote-trigger hook functionality

2012-07-03 Thread l...@tikalk.com (JIRA)














































Liya Katz
 commented on  JENKINS-13000


Git repositories (git plugin 1.1.15) used within Jenkins multiple SCMs plugin (0.2) are not detected by the remote-trigger hook functionality















It seems to be a limitation of the MultiSCM plugin - see https://wiki.jenkins-ci.org/display/JENKINS/Multiple+SCMs+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