date:20190913

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Sears edited a comment on  JENKINS-56750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.   
 

  
 
 
 
 

 
 [~aslaakso] For reference, I'm reinstalling 5.8 version to see if the error is different. I may need a second ticket for 5.8 :-0. I will update here with the error once I  5.8 has an issue and doesn ' ve captured it t start the test run .  Please see the log below.   [RouteOne Medium] $ "d:\Jenkins\.jenkins\workspace\Agile Enablement Factories\Sales And Product\1-2 Dealer Sales\RouteOne Medium\HpToolsLauncher.exe" -paramfile props13092019181324010.txt"Started..."Timeout is set to: 7200Run mode is set to: RUN_PLANNED_HOSTStarting test set executionTest set name: Demo, Test set id: 1423Number of tests in set: 5Test 1: [1]R1_AKL_CAL_BUS_LSE will run on host: *{color:#FF}{color}*Test 2: [1]R1_AKL_CAL_BUS_RET will run on host: Test 3: [1]R1_AKL_CAL_IND_LSE will run on host: Test 4: [1]R1_AKL_CAL_IND_RET will run on host: Test 5: [1]R1_AKL_CA_BUS_ERR will run on host: *{color:#FF}Problem while running TestSet: Exception from HRESULT: 0x80040459{color}*"Scheduler started at:13/09/2019 18:13:28---Test set: Demo, finished at 13/09/2019 18:13:29Run status: Job succeeded, total tests: 5, succeeded: 0, failures: 0, errors: 0, warnings: 0Unknown: Unknown: Unknown: Unknown: Unknown:    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.

2019-09-13 Thread john.mccullo...@recondotech.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Sears edited a comment on  JENKINS-56750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.   
 

  
 
 
 
 

 
 [~aslaakso] The older HP Plugin has an issue and if you built on top of that then I may not be able to use it. We are using the 5.62 because of that error so when I try your patch, I get this error.We are using HP QC 12.55.548 Patch 3. Started by user [Jim Sears|http://xdvwap1450.tfs.toyota.com:8080/user/searsj]Building on master in workspace d:\Jenkins\.jenkins\workspace\MF QC Test Set Execution\Automation CoE\TAF LAB PC Maintenance-FilesERROR: Build step failed with exceptionjava.lang.NullPointerException at com.microfocus.application.automation.tools.model.RunFromAlmModel.CreateProperties(RunFromAlmModel.java:161) at com.microfocus.application.automation.tools.model.RunFromAlmModel.getProperties(RunFromAlmModel.java:151) at com.microfocus.application.automation.tools.run.RunFromAlmBuilder.perform(RunFromAlmBuilder.java:211) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Build step 'Execute Micro Focus functional tests from Micro Focus ALM' marked build as failure[WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is used...[WS-CLEANUP] doneFinished: FAILURE  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-59372) Support cctray-xml plugin

2019-09-13 Thread cgri...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris Griego created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59372  
 
 
  Support cctray-xml plugin   
 

  
 
 
 
 

 
Issue Type: 
  Story  
 
 
Assignee: 
 Sam Gleske  
 
 
Components: 
 github-oauth-plugin  
 
 
Created: 
 2019-09-13 23:07  
 
 
Labels: 
 cc.xml cctray  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Chris Griego  
 

  
 
 
 
 

 
 The /cc.xml endpoint was removed from Jenkins core in 2.173, but the cctray-xml plugin adds it back. With the cctray-xml plugin installed and the github-oauth option enabled to allow access to the endpoint, an authentication error occurs. It may be because cctray-xml redirects /cc.xml to /cc.xml/  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-55996) jacoco: Error while reading the sourcefile!

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McCullough edited a comment on  JENKINS-55996  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jacoco: Error while reading the sourcefile!   
 

  
 
 
 
 

 
 We ran into similar looking errors with 2 multi-module projects when upgrading from 3.0.1 to 3.0.4. Also resolved by reverting to 3.0.1+*1st example*+   { noformat quote }   [JaCoCo plugin] - /jenkins/workspace/ actions revenueCycleApiService -trunk/ actions-api 278 /src/main/java  462  382  filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  [JaCoCo plugin] - /jenkins/workspace/ actions revenueCycleApiService -trunk/ actions-api 278 /src/main/java  462  382  filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  java.nio.file.AccessDeniedException: /jenkins/jobs/ actions revenueCycleApiService -trunk/builds/ 12 11 /jacoco/sources/java/ com/ .svn/entries  at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)  at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)  at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)  at java.nio.file.Files.newOutputStream(Files.java:216)  at hudson.util.IOUtils.copy(IOUtils.java:42)  at hudson.FilePath.readFromTar(FilePath.java:2579)  Caused Also :  java     Also:   hudson . io remoting . IOException Channel$CallSiteStackTrace :  Failed  Remote call  to  extract /jenkins/workspace/actions-trunk/actions-auth/src/main/  dapajenkin101  at hudson.remoting.Channel.attachCallSiteStackTrace(Channel. java /null :1743)   at hudson. FilePath remoting . readFromTar UserRequest$ExceptionResponse.retrieve ( FilePath UserRequest .java: 2589 357 )  at hudson. remoting.Channel$2.adapt(Channel.java:992)  at hudson.remoting.Channel$2.adapt(Channel.java:988)  at hudson.remoting.FutureAdapter.get(FutureAdapter.java:59)  at hudson. FilePath.copyRecursiveTo(FilePath.java: 2374 2377 )  at hudson.FilePath.copyRecursiveTo(FilePath.java:2339)  at hudson.plugins.jacoco.JacocoReportDir.saveSourcesFrom(JacocoReportDir.java:48)  at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:635)  at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79)  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)  at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1074)  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)  at hudson.model.Run.execute(Run.java:1843)  at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)  at hudson.model.ResourceController.execute(ResourceController.java:97)  at hudson.model.Executor.run(Executor.java:429) {noformat}   +*2nd example*+ {noformat} {noformat} *[JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/ java  382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  [JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  java . nio io . file.AccessDeniedException IOException :  /jenkins/jobs/revenueCycleApiService-trunk/builds/11/jacoco/sources/java/com/.svn/  This archives contains unclosed entries .   at  sun  org . nio apache . fs commons . UnixException compress . translateToIOException

[JIRA] (JENKINS-55996) jacoco: Error while reading the sourcefile!

2019-09-13 Thread john.mccullo...@recondotech.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McCullough edited a comment on  JENKINS-55996  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jacoco: Error while reading the sourcefile!   
 

  
 
 
 
 

 
 We ran into similar looking errors with 2 multi-module projects when upgrading from 3.0.1 to 3.0.4. Also resolved by reverting to 3.0.1+ * 1st example * + {noformat} [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  java.nio.file.AccessDeniedException: /jenkins/jobs/actions-trunk/builds/12/jacoco/sources/java/.svn/entries  at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)  at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)  at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)  at java.nio.file.Files.newOutputStream(Files.java:216)  at hudson.util.IOUtils.copy(IOUtils.java:42)  at hudson.FilePath.readFromTar(FilePath.java:2579) Caused: java.io.IOException: Failed to extract /jenkins/workspace/actions-trunk/actions-auth/src/main/java/null  at hudson.FilePath.readFromTar(FilePath.java:2589)  at hudson.FilePath.copyRecursiveTo(FilePath.java:2374)  at hudson.FilePath.copyRecursiveTo(FilePath.java:2339)  at hudson.plugins.jacoco.JacocoReportDir.saveSourcesFrom(JacocoReportDir.java:48)  at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:635)  at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79)  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)  at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1074)  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)  at hudson.model.Run.execute(Run.java:1843)  at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)  at hudson.model.ResourceController.execute(ResourceController.java:97)  at hudson.model.Executor.run(Executor.java:429){noformat}    +*2nd example*+ {noformat}    {noformat} *[JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  [JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  java.nio.file.AccessDeniedException: /jenkins/jobs/revenueCycleApiService-trunk/builds/11/jacoco/sources/java/com/.svn/entries  at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)  at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)  at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)  at java.nio.file.Files.newOutputStream(Files.java:216)  at hudson.util.IOUtils.copy(IOUtils.java:42)  at hudson.FilePath.readFromTar(FilePath.java:2579) Also:    Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to dapajenkin101  at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)  at

[JIRA] (JENKINS-55996) jacoco: Error while reading the sourcefile!

2019-09-13 Thread john.mccullo...@recondotech.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McCullough edited a comment on  JENKINS-55996  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jacoco: Error while reading the sourcefile!   
 

  
 
 
 
 

 
 We ran into similar looking errors with 2 multi-module projects when upgrading from 3.0.1 to 3.0.4. Also resolved by reverting to 3.0.1+1st example+ {noformat} [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  java.nio.file.AccessDeniedException: /jenkins/jobs/actions-trunk/builds/12/jacoco/sources/java/.svn/entries  at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)  at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)  at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)  at java.nio.file.Files.newOutputStream(Files.java:216)  at hudson.util.IOUtils.copy(IOUtils.java:42)  at hudson.FilePath.readFromTar(FilePath.java:2579) Caused: java.io.IOException: Failed to extract /jenkins/workspace/actions-trunk/actions-auth/src/main/java/null  at hudson.FilePath.readFromTar(FilePath.java:2589)  at hudson.FilePath.copyRecursiveTo(FilePath.java:2374)  at hudson.FilePath.copyRecursiveTo(FilePath.java:2339)  at hudson.plugins.jacoco.JacocoReportDir.saveSourcesFrom(JacocoReportDir.java:48)  at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:635)  at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79)  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)  at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1074)  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)  at hudson.model.Run.execute(Run.java:1843)  at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)  at hudson.model.ResourceController.execute(ResourceController.java:97)  at hudson.model.Executor.run(Executor.java:429)  {noformat}    +*2nd example*+   {noformat} {noformat} * [JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  [JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  java.nio.file.AccessDeniedException: /jenkins/jobs/revenueCycleApiService-trunk/builds/11/jacoco/sources/java/com/.svn/entries  at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)  at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)  at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)  at java.nio.file.Files.newOutputStream(Files.java:216)  at hudson.util.IOUtils.copy(IOUtils.java:42)  at hudson.FilePath.readFromTar(FilePath.java:2579) Also:    Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to dapajenkin101  at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)  at

[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Sears commented on  JENKINS-56750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.   
 

  
 
 
 
 

 
 For reference, I'm reinstalling 5.8 version to see if the error is different. I may need a second ticket for 5.8 :-0. I will update here with the error once I've captured it.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.3468.1568413560212%40Atlassian.JIRA.

[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.

2019-09-13 Thread john.mccullo...@recondotech.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Sears commented on  JENKINS-56750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.   
 

  
 
 
 
 

 
 The older HP Plugin has an issue and if you built on top of that then I may not be able to use it. We are using the 5.62 because of that error so when I try your patch, I get this error. We are using HP QC 12.55.548 Patch 3.   Started by user  Jim Sears Building on master in workspace d:\Jenkins\.jenkins\workspace\MF QC Test Set Execution\Automation CoE\TAF LAB PC Maintenance-Files ERROR: Build step failed with exception java.lang.NullPointerException at com.microfocus.application.automation.tools.model.RunFromAlmModel.CreateProperties(RunFromAlmModel.java:161) at com.microfocus.application.automation.tools.model.RunFromAlmModel.getProperties(RunFromAlmModel.java:151) at com.microfocus.application.automation.tools.run.RunFromAlmBuilder.perform(RunFromAlmBuilder.java:211) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:81) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.Build$BuildExecution.build(Build.java:206) at hudson.model.Build$BuildExecution.doRun(Build.java:163) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1816) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Execute Micro Focus functional tests from Micro Focus ALM' marked build as failure [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... [WS-CLEANUP] done Finished: FAILURE  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-55996) jacoco: Error while reading the sourcefile!

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McCullough edited a comment on  JENKINS-55996  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jacoco: Error while reading the sourcefile!   
 

  
 
 
 
 

 
 We ran into similar looking errors with 2 multi-module projects when upgrading from 3.0.1 to 3.0.4. Also resolved by reverting to 3.0.1+1st example+   { {{ noformat} }}    [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  java.nio.file.AccessDeniedException: /jenkins/jobs/actions-trunk/builds/12/jacoco/sources/java/.svn/entries  at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)  at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)  at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)  at java.nio.file.Files.newOutputStream(Files.java:216)  at hudson.util.IOUtils.copy(IOUtils.java:42)  at hudson.FilePath.readFromTar(FilePath.java:2579) Caused: java.io.IOException: Failed to extract /jenkins/workspace/actions-trunk/actions-auth/src/main/java/null  at hudson.FilePath.readFromTar(FilePath.java:2589)  at hudson.FilePath.copyRecursiveTo(FilePath.java:2374)  at hudson.FilePath.copyRecursiveTo(FilePath.java:2339)  at hudson.plugins.jacoco.JacocoReportDir.saveSourcesFrom(JacocoReportDir.java:48)  at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:635)  at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79)  at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)  at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)  at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)  at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1074)  at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)  at hudson.model.Run.execute(Run.java:1843)  at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543)  at hudson.model.ResourceController.execute(ResourceController.java:97)  at hudson.model.Executor.run(Executor.java:429)   { {{ noformat} }}    +*2nd example*+  { {{ noformat} }}   [JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  [JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  java.nio.file.AccessDeniedException: /jenkins/jobs/revenueCycleApiService-trunk/builds/11/jacoco/sources/java/com/.svn/entries  at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)  at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)  at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)  at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)  at java.nio.file.Files.newOutputStream(Files.java:216)  at hudson.util.IOUtils.copy(IOUtils.java:42)  at hudson.FilePath.readFromTar(FilePath.java:2579) Also:    Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to dapajenkin101  at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)

[JIRA] (JENKINS-55996) jacoco: Error while reading the sourcefile!

2019-09-13 Thread john.mccullo...@recondotech.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McCullough edited a comment on  JENKINS-55996  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jacoco: Error while reading the sourcefile!   
 

  
 
 
 
 

 
 We ran into similar looking errors with 2 multi-module projects when upgrading from 3.0.1 to 3.0.4. Also resolved by reverting to 3.0.1  +  1st example +  2019-09-13 21:30:38.639  {{{noformat}}}   [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  2019-09-13 21:30:38.639    [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  2019-09-13 21:30:38.691    java.nio.file.AccessDeniedException: /jenkins/jobs/actions-trunk/builds/12/jacoco/sources/java/.svn/ entries2019-09-13 21:30:38.691 entries   at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) 2019-09-13 21:30:38.691    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) 2019-09-13 21:30:38.691    at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) 2019-09-13 21:30:38.691    at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214) 2019-09-13 21:30:38.691    at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434) 2019-09-13 21:30:38.691    at java.nio.file.Files.newOutputStream(Files.java:216) 2019-09-13 21:30:38.691    at hudson.util.IOUtils.copy(IOUtils.java:42) 2019-09-13 21:30:38.691    at hudson.FilePath.readFromTar(FilePath.java:2579) 2019-09-13 21:30:38.691    Caused: java.io.IOException: Failed to extract /jenkins/workspace/actions-trunk/actions-auth/src/main/java/ null2019-09-13 21:30:38.691 null   at hudson.FilePath.readFromTar(FilePath.java:2589) 2019-09-13 21:30:38.691    at hudson.FilePath.copyRecursiveTo(FilePath.java:2374) 2019-09-13 21:30:38.691    at hudson.FilePath.copyRecursiveTo(FilePath.java:2339) 2019-09-13 21:30:38.691    at hudson.plugins.jacoco.JacocoReportDir.saveSourcesFrom(JacocoReportDir.java:48) 2019-09-13 21:30:38.691    at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:635) 2019-09-13 21:30:38.691    at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79) 2019-09-13 21:30:38.691    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 2019-09-13 21:30:38.691    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741) 2019-09-13 21:30:38.691    at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) 2019-09-13 21:30:38.691    at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1074) 2019-09-13 21:30:38.691    at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) 2019-09-13 21:30:38.691    at hudson.model.Run.execute(Run.java:1843) 2019-09-13 21:30:38.691    at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) 2019-09-13 21:30:38.691    at hudson.model.ResourceController.execute(ResourceController.java:97) 2019-09-13 21:30:38.691    at hudson.model.Executor.run(Executor.java:429)  {{{noformat}}}    +*  2nd example *+  2019-09-13 21:17:55.194 {{{noformat}}}  [JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  2019-09-13 21:17:55.194    [JaCoCo plugin] - /jenkins/workspace/revenueCycleApiService-trunk/278/src/main/java 382 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception:  2019-09-13 21:17:55.292    java.nio.file.AccessDeniedException:

[JIRA] (JENKINS-55996) jacoco: Error while reading the sourcefile!

2019-09-13 Thread john.mccullo...@recondotech.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 John McCullough commented on  JENKINS-55996  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: jacoco: Error while reading the sourcefile!   
 

  
 
 
 
 

 
 We ran into similar looking errors with 2 multi-module projects when upgrading from 3.0.1 to 3.0.4. Also resolved by reverting to 3.0.1 
 
 
 
 
 
 
 
1st example 
  
  
  
 2019-09-13 21:30:38.639 [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception: 2019-09-13 21:30:38.639 [JaCoCo plugin] - /jenkins/workspace/actions-trunk/actions-api/src/main/java 462 filesERROR: Step ‘Record JaCoCo coverage report’ aborted due to exception: 2019-09-13 21:30:38.691 java.nio.file.AccessDeniedException: /jenkins/jobs/actions-trunk/builds/12/jacoco/sources/java/.svn/entries2019-09-13 21:30:38.691 at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)2019-09-13 21:30:38.691 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)2019-09-13 21:30:38.691 at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)2019-09-13 21:30:38.691 at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)2019-09-13 21:30:38.691 at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:434)2019-09-13 21:30:38.691 at java.nio.file.Files.newOutputStream(Files.java:216)2019-09-13 21:30:38.691 at hudson.util.IOUtils.copy(IOUtils.java:42)2019-09-13 21:30:38.691 at hudson.FilePath.readFromTar(FilePath.java:2579)2019-09-13 21:30:38.691 Caused: java.io.IOException: Failed to extract /jenkins/workspace/actions-trunk/actions-auth/src/main/java/null2019-09-13 21:30:38.691 at hudson.FilePath.readFromTar(FilePath.java:2589)2019-09-13 21:30:38.691 at hudson.FilePath.copyRecursiveTo(FilePath.java:2374)2019-09-13 21:30:38.691 at hudson.FilePath.copyRecursiveTo(FilePath.java:2339)2019-09-13 21:30:38.691 at hudson.plugins.jacoco.JacocoReportDir.saveSourcesFrom(JacocoReportDir.java:48)2019-09-13 21:30:38.691 at hudson.plugins.jacoco.JacocoPublisher.perform(JacocoPublisher.java:635)2019-09-13 21:30:38.691 at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:79)2019-09-13 21:30:38.691 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)2019-09-13 21:30:38.691 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)2019-09-13 21:30:38.691 at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)2019-09-13 21:30:38.691 at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:1074)2019-09-13 21:30:38.691 at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)2019-09-13 21:30:38.691 at hudson.model.Run.execute(Run.java:1843)2019-09-13 21:30:38.691 at

[JIRA] (JENKINS-57377) Have Aggregate Trend Chart display as first item among warning analysis

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57377  
 
 
  Have Aggregate Trend Chart display as first item among warning analysis   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
URL: 
 https://github.com/jenkinsci/warnings-ng-plugin/pull/211  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199158.1557352086000.3447.1568411340599%40Atlassian.JIRA.

[JIRA] (JENKINS-58383) Disable aggregated analysis results

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58383  
 
 
  Disable aggregated analysis results   
 

  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
URL: 
 https://github.com/jenkinsci/warnings-ng-plugin/pull/211  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200507.1562597544000.3442.1568411340523%40Atlassian.JIRA.

[JIRA] (JENKINS-58383) Disable aggregated analysis results

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner started work on  JENKINS-58383  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200507.1562597544000.3445.1568411340562%40Atlassian.JIRA.

[JIRA] (JENKINS-57377) Have Aggregate Trend Chart display as first item among warning analysis

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ulli Hafner started work on  JENKINS-57377  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Ulli Hafner  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199158.1557352086000.3439.1568411160299%40Atlassian.JIRA.

[JIRA] (JENKINS-33639) Unable to connect TFS server with The SOAP endpoint could not be contacted

2019-09-13 Thread k.vik...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikhna Raj edited a comment on  JENKINS-33639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect TFS server with The SOAP endpoint could not be contacted   
 

  
 
 
 
 

 
 I'm still facing this issue. FATAL: com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint [http://servername-tfs1:8080/tfs/Services/v1.0/Registration.asmx|http://pwg-tfs1:8080/tfs/Services/v1.0/Registration.asmx] could not be contacted.  HTTP status: 404 I'm trying to connect from my localhost Jenkins. Updated the default Jenkins port 8080 to a different one.Not sure if I configured the right credentials for TFS in Jenkins ?  Could anyone please help me with this issue ?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169087.1458286876000.3431.1568406000328%40Atlassian.JIRA.

[JIRA] (JENKINS-33639) Unable to connect TFS server with The SOAP endpoint could not be contacted

2019-09-13 Thread k.vik...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Vikhna Raj commented on  JENKINS-33639  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to connect TFS server with The SOAP endpoint could not be contacted   
 

  
 
 
 
 

 
 I'm still facing this issue.  FATAL: com.microsoft.tfs.core.exceptions.TECoreException: The SOAP endpoint  http://servername-tfs1:8080/tfs/Services/v1.0/Registration.asmx could not be contacted. HTTP status: 404  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169087.1458286876000.3422.1568405760323%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

2019-09-13 Thread lostinberlin2...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Boardwell edited a comment on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 Can confirm that setting all 3 fields and {{configureByUrl}} to true works with the job-dsl plugin.Some strange happenings going on with job-dsl though.* Leaving {{repoOwner}} or {{repository}} blank and they will be missing from the {{repositoryUrl}} in the generated jobs config page.  Infact  In fact,  the {{repositoryUrl}} is overwritten, regardless of what you put in there.* The {{configuredByUrl}} is also disregarded it seems. The "Repository HTTPS URL" is always activated in the generated job , regardless of the boolean value .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3419.1568405160119%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

2019-09-13 Thread lostinberlin2...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Boardwell edited a comment on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 Can confirm that setting all 3 fields and {{configureByUrl}} to true works with the job-dsl plugin .Some strange happenings going on with job-dsl though.* Leaving {{repoOwner}} or {{repository}} blank and they will be missing from the {{repositoryUrl}} in the generated jobs config page. Infact the {{repositoryUrl}} is overwritten, regardless of what you put in there.* The {{configuredByUrl}} is also disregarded it seems. The "Repository HTTPS URL" is always activated in the generated job.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3417.1568404980159%40Atlassian.JIRA.

[JIRA] (JENKINS-59371) NV insight report in Jenkins

2019-09-13 Thread clab...@massmutual.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 craig labrie created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59371  
 
 
  NV insight report in Jenkins   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Daniel Danan  
 
 
Components: 
 micro-focus-performance-center-integration-plugin  
 
 
Created: 
 2019-09-13 19:44  
 
 
Priority: 
  Major  
 
 
Reporter: 
 craig labrie  
 

  
 
 
 
 

 
 From: Daniel Danan  Sent: Wednesday, July 31, 2019 9:47 AM To: Jerry Smith ; Aliza Salomon ; Labrie, Craig  Cc: Khatib, Canaan ; Peter Inglehart ; Ganapathy, Shriram Ramachandra ; Christian Pruitt  Subject: RE: “Mass Mutual” discussion re using NV Insight Reports in CI/CD pipeline   Hi,     I reviewed the Jenkins plugin and in order to download the result of a Run to Jenkins build artifact, a specific PC REST API command is being used (you can see it from this link: https://admhelp.microfocus.com/pc/en/all/api_refs/Performance_Center_REST_API/Performance_Center_REST_API.htm#HTML_Results_Report.htm%3FTocPath%3DResources%7C_18).       Unfortunately, PC REST does not expose a command allowing to download any file related to a Run as I was wrongly expecting which would have allowed me to download the NV Insight report (I was under the assumption that PC RES allows it, mainly because I am also familiar with the ALM REST which does allow it and I confused between them).   So in order to have the Jenkins plugin allowing the download of NV Insight report, there is a need to have the PC REST modified to provide a command allowing it. Since the limitation is not in the Jenkins plugin, I would suggest for this request to be reported as an enhancement request on Performance Center product so it can be handled correctly as we need to have first the PC REST to be modified (a patch or hotfix provided) and then and only then the Jenkins plugin can be modified to use this new command.

[JIRA] (JENKINS-59265) MicroFocus Plug-in - Would like some changes made

2019-09-13 Thread ckha...@massmutual.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Canaan Khatib commented on  JENKINS-59265  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MicroFocus Plug-in - Would like some changes made   
 

  
 
 
 
 

 
 Daniel Danan Any update on this ticket?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201763.1567802896000.3413.1568403420174%40Atlassian.JIRA.

[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data

2019-09-13 Thread awiddersh...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Widdersheim commented on  JENKINS-57528  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins in Docker does not install detached plugins when there is no UC data   
 

  
 
 
 
 

 
 Er, I'm sorry. The https://plugins.jenkins.io/pam-auth plugin is the one with the security issue. 

 

jenkins_1  | INFO: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/pam-auth.jpi
jenkins_1  | WARNING: Created /var/jenkins_home/plugins/pam-auth/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
jenkins_1  | INFO: Took 0ms for Loading plugin PAM Authentication plugin v1.1 (pam-auth) by pool-6-thread-4
jenkins_1  | INFO: Took 0ms for Initializing plugin pam-auth by pool-6-thread-1  

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3406.1568402940436%40Atlassian.JIRA.

[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data

2019-09-13 Thread awiddersh...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Widdersheim commented on  JENKINS-57528  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins in Docker does not install detached plugins when there is no UC data   
 

  
 
 
 
 

 
 Some logs: 

 

jenkins_1  | INFO: Loading a detached plugin as a dependency: /var/jenkins_home/plugins/ldap.jpi
jenkins_1  | WARNING: Created /var/jenkins_home/plugins/ldap/WEB-INF/lib/classes.jar; update plugin to a version created with a newer harness
jenkins_1  | INFO: Took 0ms for Loading plugin LDAP Plugin v1.11 (ldap) by pool-6-thread-24
jenkins_1  | INFO: Took 0ms for Initializing plugin ldap by pool-6-thread-18 
 

 The latest version is 1.20 according to my UI.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3398.1568402580305%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

2019-09-13 Thread lostinberlin2...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Boardwell commented on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 Can confirm that setting all 3 fields and configureByUrl to true works with the job-dsl plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3395.1568402460167%40Atlassian.JIRA.

[JIRA] (JENKINS-59306) Allow fetching of more tags

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-59306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow fetching of more tags   
 

  
 
 
 
 

 
 It sounds like you want every workspace to have the complete history, rather than using the multibranch pipeline default of a narrow history limited to a specific branch for the workspace dedicated to that branch.The breadth of the history which is included in a workspace is controlled by the git {{refspec}}.  The multibranch pipeline default is to fetch only the history for the exact branch being built in that workspace.  You can change that behavior in scripted Pipeline by adding a custom {{refspec}} in the {{checkout}} step which includes all branches.  You can change that behavior in declarative Pipeline by using {{skipDefaultCheckout}} and then performing the checkout with the same technique you would use for scripted Pipeline. The "copy the entire history" behavior is the standard behavior for Freestyle jobs and was the initial behavior for multibranch jobs.  One of the lead developers realized that significant time and space savings were possible in a multibranch context by acknowledging that most multibranch Pipeline jobs are building a single branch without consulting anything from other branches.When multibranch implemented that optimization, some of the tests for the git plugin and git client plugin had to be adapted.  They assumed the Freestyle project default of including the entire repository history in every workspace.  Welcome to the elite club of multibranch Pipelines that want the full history in every workspace.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message

[JIRA] (JENKINS-57694) BuildChooser logs a missing descriptor message

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57694  
 
 
  BuildChooser logs a missing descriptor message   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199629.1558925594000.3393.1568401980155%40Atlassian.JIRA.

[JIRA] (JENKINS-59306) Allow fetching of more tags

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-59306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59306  
 
 
  Allow fetching of more tags   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201854.1568157936000.3385.1568401440238%40Atlassian.JIRA.

[JIRA] (JENKINS-59306) Allow fetching of more tags

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-59306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow fetching of more tags   
 

  
 
 
 
 

 
 It sounds like you want every workspace to have the complete history, rather than using the multibranch pipeline default of a narrow history limited to a specific branch for the workspace dedicated to that branch. The breadth of the history which is included in a workspace is controlled by the git refspec. The multibranch pipeline default is to fetch only the history for the exact branch being built in that workspace. You can change that behavior in scripted Pipeline by adding a custom refspec in the checkout step which includes all branches. You can change that behavior in declarative Pipeline by using skipDefaultCheckout and then performing the checkout with the same technique you would use for scripted Pipeline.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201854.1568157936000.3383.1568401380154%40Atlassian.JIRA.

[JIRA] (JENKINS-59306) Allow fetching of more tags

2019-09-13 Thread bryce.scho...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Bryce Schober commented on  JENKINS-59306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow fetching of more tags   
 

  
 
 
 
 

 
 Mark Waite, I have the "Fetch tags" behavior enabled, but it doesn't actually match my use-case, which is looking for deeper history than just the most recent tag parent of the current branch.  It does fetch all of the tag refs, but it doesn't fetch any additional pieces of the commit graph. My use case would require that it also fetch enough additional commit-graph history to be able to determine the ancestry from the current branch back to every tag. This is because my use case is a multi-product repository, with tags using a "namespace" prefix along the lines of "product_foo-vN.N.N". This combines with the fact that our build pipeline builds the latest version of every product in the same job. We ultimately use a git describe HEAD --tags --match 'product_foo-v*' to determine the tag parentage of the current branch for that part of our full version string. So our clone would have to go all the way back to the oldest supported product's most recent version, which in the worst case could be almost the entire repository history - not really something that we should be doing in a regular build cycle. All this has led me to realize that our dynamic multi-product versioning based git tags isn't really a practical solution, and given our current repository structure and usage, we should just back off to manually-maintained per-product version numbers, as is normally done in most any packaging system. All that said, it is still true that while there exists a behavior to fetch all tags, it doesn't really leave the user with "usable" tags without the commit graph necessary to trace the branch back to them.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-59131) TypeError: null is not an object (evaluating 'run.causes.length')

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 A fix for this issue was released in Blue Ocean Plugin version 1.19.0.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-59131  
 
 
  TypeError: null is not an object (evaluating 'run.causes.length')   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 Open Resolved  
 
 
Assignee: 
 Kevin Ushey  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 blue-ocean 1.19.0  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

2019-09-13 Thread lostinberlin2...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Boardwell commented on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 Btw, with the current jenkins:lts it isn't possible to create a multibranch-pipeline without installing the "Cloudbees Credentials Plugin". The configuration page of the job doesn't load (spinning disk) with the logs showing: 

 
Sep 13, 2019 6:34:54 PM org.eclipse.jetty.server.handler.ContextHandler$Context log
WARNING: Error while serving http://localhost:8080/job/test-pipeline/contextMenu
java.lang.reflect.InvocationTargetException
	at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400)
	at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)
	at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212)
	at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145)
	at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535)
...
...
	at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126)
	at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:366)
	at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:765)
	at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:683)
	at java.lang.Thread.run(Thread.java:748)
Caused by: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.176.3.jar!/lib/hudson/actions.jelly:39:70:  com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider
	at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289)
	at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
	at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
...
...
	at jenkins.model.ModelObjectWithContextMenu$ContextMenu.from(ModelObjectWithContextMenu.java:193)
	at hudson.model.Actionable.doContextMenu(Actionable.java:360)
	at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
	at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
	... 77 more
Caused by: java.lang.NoClassDefFoundError: com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider
	at java.lang.Class.getDeclaringClass0(Native Method)
	at java.lang.Class.getDeclaringClass(Class.java:1235)
	at java.lang.Class.getEnclosingClass(Class.java:1277)
	at com.cloudbees.plugins.credentials.CredentialsStore.(CredentialsStore.java:102)
...
...
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:97)
	at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
	at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95)
	at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147)
	at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269)
	... 117 more
 

 Would it be possible to add the "Cloudbees Credentials Plugin" plugin as a dependency?

[JIRA] (JENKINS-59306) Allow fetching of more tags

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite edited a comment on  JENKINS-59306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow fetching of more tags   
 

  
 
 
 
 

 
 I'm not understanding precisely what you are trying to do.If you want a multibranch pipeline build automatically created for every tag in the repostiory, then this [stackoverflow article|https://stackoverflow.com/questions/47146616/is-there-a-way-to-automatically-build-tags-using-the-multibranch-pipeline-jenkin] probably provides what you need.If you want each workspace to include all the tags that are defined in the remote repository, then you likely need to enable the "Fetch tags" behaviour in the " [ Advanced clone options |https://github.com/jenkinsci/git-plugin/blob/master/README.md#advanced-clone-behaviours] ".If neither of those is what you want, it is probably best to ask the mailing list for help.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201854.1568157936000.3375.1568399880117%40Atlassian.JIRA.

[JIRA] (JENKINS-59370) post { unsuccessful {}} doesn't fire without a success {}

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59370  
 
 
  post { unsuccessful {}} doesn't fire without a success {}   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 pipeline  
 
 
Created: 
 2019-09-13 18:36  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Brian J Murrell  
 

  
 
 
 
 

 
 If I have a: 

 
post {
  unsuccessful {
println("unsuccessful")
  }
}  

 without also having a success block in there, the unsuccessful block fails to run as if it were just not there. Since empty stages are not allowed I had to write a noop() step in a pipeline library that does nothing in order to have a: 

 
  success { noop() } 

 in my post stage so that the unsuccessful stage would run.

[JIRA] (JENKINS-59306) Allow fetching of more tags

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-59306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow fetching of more tags   
 

  
 
 
 
 

 
 I'm not understanding precisely what you are trying to do. If you want a multibranch pipeline build automatically created for every tag in the repostiory, then this stackoverflow article probably provides what you need. If you want each workspace to include all the tags that are defined in the remote repository, then you likely need to enable the "Fetch tags" behaviour in the "Advanced clone options". If neither of those is what you want, it is probably best to ask the mailing list for help.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201854.1568157936000.3363.1568399640799%40Atlassian.JIRA.

[JIRA] (JENKINS-59306) Allow fetching of more tags

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59306  
 
 
  Allow fetching of more tags   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Assignee: 
 Mark Waite  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201854.1568157936000.3365.1568399640869%40Atlassian.JIRA.

[JIRA] (JENKINS-57563) Script Security: Add JCasC support to ScriptApproval

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated  JENKINS-57563  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 A fix for this issue has been released in Script Security Plugin version 1.64. Here is an example of what the JCasC configuration might look like: 

 

security:
  scriptApproval:
approvedSignatures:
- staticMethod java.lang.String format java.lang.String java.lang.Object[]
- method java.lang.String indexOf int
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57563  
 
 
  Script Security: Add JCasC support to ScriptApproval
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 script-security 1.64  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira

[JIRA] (JENKINS-59369) Priority Sorter should allows a job can belong to multiple Groups

2019-09-13 Thread nhatk...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 NhatKhai Nguyen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59369  
 
 
  Priority Sorter should allows a job can belong to multiple Groups   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 prioritysorter-plugin  
 
 
Created: 
 2019-09-13 18:29  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 NhatKhai Nguyen  
 

  
 
 
 
 

 
 I have a need for job that can be execute on more than one of the Group. For example use case: I have following jobs: 
 
JobA1, JobA2, JobA3 can only run on agent label with A1, A2 
JobB1, JobB2 can only run on agent label with A1, A3 
JobC1 can only run on agent label with A2, A3 
 When start: 1) All agents are free 2) JobA1, JobB1, JobC1 on demand -> Jenkins assign JobA1 to A1, JobB1 to A3, JobC1 to A2 3) While busy, JobA2 on wait (priority 10) 4) While busy, JobB2 on wait (priority 1) 5) While busy, JobA2 on wait (priority 5) 6) JobA1 done --> Jenkins assign JobB2 to A1 7) JobC1 done --> Jenkins assign JobA2 to A2 8) JobB1 done --> Jenkins assign JobA3 to A3

[JIRA] (JENKINS-59327) No credentials specified Multibranch Pipeline - Branch script

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite commented on  JENKINS-59327  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: No credentials specified Multibranch Pipeline - Branch script   
 

  
 
 
 
 

 
 I'm not sure I understand the steps you took to see the problem. Many users are using credentials to checkout multibranch pipeline repositories and operate with them regularly. You said in the first step: 

1 - Create Multibranch Job without specified git credentials with script-path where is a script.
 If I take that statement literally, meaning that you defined a multibranch job accessing a private repository without providing git credentials, then I would expect that to fail. The multibranch pipeline definition must have credentials in order to discover the branches in the repository and the Jenkinsfile in the root directory of each branch. If credentials are not provided, then the branches cannot be detected and the Jenkinsfile cannot be read from the root directory of the branch. If that is not what you did, please describe the configuration in more detail. I test very frequently with private multibranch repositories from different hosting providers and using different forms and they work as expected.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web

[JIRA] (JENKINS-57650) anchore plugin isn't respecting engineRetries

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty resolved as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Adam Chou, engineRetries is how long (in seconds) the plugin will wait for anchore engine to complete analysis. Technically, it's the number of polling attempts spaced at 1 second intervals. A polling attempt is where the plugin checks the status of the image analysis in anchore engine. So a value of 700 instructs the plugin to wait for 700 seconds or 11+ minutes for the image analysis to complete. If you expect the analysis to take longer, say 1 hour, bump engineRetries to 6000  Docs for engineRetries attribute in the plugin help are incorrect. It should be addressed in the next release  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57650  
 
 
  anchore plugin isn't respecting engineRetries   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-59327) No credentials specified Multibranch Pipeline - Branch script

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59327  
 
 
  No credentials specified Multibranch Pipeline - Branch script   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 Hi Team,When I am creating Multibranch Pipeline job which executes another pipeline job as a branch apparently it's not reading git credentials in branch. So in a branch which is a pipeline script, I have stage stage('git checkout') \{stage('git checkout') {steps { git credentialsId: 'My credentials', poll: false, url: 'mygit.git' }}But it's falling on Windows machine with the following error. When I create just a simple pipeline job with the same stage it's working as should.From test which I did when I specified credentials in a multibranch job which is managing my script in the branch then it's working. So apparently git credentials from the stage are ignored.Steps to Reproduce:1. Create Multibranch Job without specified git credentials with script-path where is a script.2. In a script create step with git checkout and specified credentials3. Run the branch script and it should fail.4. Add in Multibranch configuration credentials and run branch script it should work. {noformat} No credentials specifiedNo credentials  specifiedWiping  specifiedWiping  out workspace first.  Cloning the remote Git  repositoryCloning  repositoryCloning  with configured refspecs honoured and without  tagsERROR  tagsERROR : Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --no-tags --force --progress MyRepo.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:  stdout:   stderr: mygitserver: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:655) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed:

[JIRA] (JENKINS-59327) No credentials specified Multibranch Pipeline - Branch script

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59327  
 
 
  No credentials specified Multibranch Pipeline - Branch script   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 

  
 
 
 
 

 
 Hi Team,When I am creating Multibranch Pipeline job which executes another pipeline job as a branch apparently it's not reading git credentials in branch. So in a branch which is a pipeline script, I have stage stage('git checkout') \{stage('git checkout') {steps { git credentialsId: 'My credentials', poll: false, url: 'mygit.git' }}But it's falling on Windows machine with the following error. When I create just a simple pipeline job with the same stage it's working as should.From test which I did when I specified credentials in a multibranch job which is managing my script in the branch then it's working. So apparently git credentials from the stage are ignored.  Steps to Reproduce:1. Create Multibranch Job without specified git credentials with script-path where is a script.2. In a script create step with git checkout and specified credentials3. Run the branch script and it should fail.4. Add in Multibranch configuration credentials and run branch script it should work.No credentials specifiedNo credentials specifiedWiping out workspace first.Cloning the remote Git repositoryCloning with configured refspecs honoured and without tagsERROR: Error cloning remote repo 'origin'hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --no-tags --force --progress MyRepo.git +refs/heads/*:refs/remotes/origin/*" returned status code 128:stdout: stderr: mygitserver: Permission denied (publickey).fatal: Could not read from remote repository.Please make sure you have the correct access rightsand the repository exists. at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:655) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Unknown Source) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

2019-09-13 Thread lostinberlin2...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Steve Boardwell commented on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 Hi Liam Newman, thanks for the quick response. Are you saying that the github configuration needs owner, repository, and repositoryUrl? I would have thought that, from the looks of the variables, it was either/or with the configuredByUrl determining whether to use the repositoryUrl. re: Job DSL  This was correctly shown in the jobDSL API Viewer - it was more of an Info with a view to maybe adding the information á la 'breaking change for any dsl job definitions'. Or was there anything else you think I could ask from the job-dsl-plugin?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3343.1568397840219%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman edited a comment on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 [~lostinberlin]For the JobDSL syntax change, you are correct - the underlying data representation changed.  The JobDSL syntax is reflecting that.  Could you open a separate issue for that? Maybe something to fix on the JobDSL side or as a symbol annotation in this plugin.As for the exception, it looks like this only happens if you try to save a blank job, right? That shouldn't be the case. It should be a validation error (not an explosion), but this is specific to a case that is not a valid job, right?   It likely means we're not validating everything we should.    <
 /td> 
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3341.1568397660131%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman edited a comment on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 [~lostinberlin]For the JobDSL syntax change, you are correct - the underlying data representation changed.  The JobDSL syntax is reflecting that.  Could you open a separate issue for that? Maybe something to fix on the JobDSL side or as a symbol annotation in this plugin.As for the exception, it looks like this only happens if you try to save a blank job, right? That shouldn't be the case. It should be a validation error (not an explosion), but this is specific to a case that is not a valid job, right?     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3339.1568397600206%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman edited a comment on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 [~lostinberlin]For the JobDSL syntax change, you are correct - the underlying data representation changed.  The JobDSL syntax is reflecting that.  Could you open a separate issue for that? Maybe something to fix on the JobDSL side or as a symbol annotation in this plugin.As for the exception, it looks like this only happens if you try to save a blank job  but also for an invalid URL. , right?     That shouldn't be the case. It should be a validation error , but  (  not an explosion .   It does also result in a Jenkins error webpage with ), but  this  message: {{java.lang.IllegalArgumentException: Repository URL must  is specific to a case that is  not  be empty at org.jenkinsci.plugins.github_branch_source.GitHubRepositoryInfo.forRepositoryUrl(GitHubRepositoryInfo.java:84) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.(GitHubSCMSource.java:336) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678)}}  a valid job, right?    This should be a validation error      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman edited a comment on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 [~lostinberlin]For the JobDSL syntax change, you are correct - the underlying data representation changed.  The JobDSL syntax is reflecting that.  Could you open a separate issue for that? Maybe something to fix on the JobDSL side or as a symbol annotation in this plugin.As for the exception, it looks like this only happens if you try to save a blank job, right? That shouldn't be the case. It should be a validation error (not an explosion), but this is specific to a case that is not a valid job, right?     
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3337.1568397540211%40Atlassian.JIRA.

[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen

2019-09-13 Thread awa...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alejandro Jurado Walls edited a comment on  JENKINS-50331  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen   
 

  
 
 
 
 

 
 I am seeing this issue  too . An update would be appreciated.Environment where this issue is observed:Jenkins 2.164.3TFS Plug-in: 5.133.0   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.3328.1568397420613%40Atlassian.JIRA.

[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen

2019-09-13 Thread awa...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alejandro Jurado Walls commented on  JENKINS-50331  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen   
 

  
 
 
 
 

 
 I am seeing this issue. An update would be appreciated. Environment where this issue is observed: Jenkins 2.164.3 TFS Plug-in: 5.133.0    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189378.1521699501000.3320.1568397420494%40Atlassian.JIRA.

[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data

2019-09-13 Thread awiddersh...@hotmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Widdersheim commented on  JENKINS-57528  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins in Docker does not install detached plugins when there is no UC data   
 

  
 
 
 
 

 
 Jesse Glick I am not seeing the detached plugins being updated. At last when using the Docker container. I'm able to replicate with the https://plugins.jenkins.io/purge-build-queue-plugin# which pulls in LDAP 1.0 for example.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3312.1568397300249%40Atlassian.JIRA.

[JIRA] (JENKINS-57650) anchore plugin isn't respecting engineRetries

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty assigned an issue to Swathi Gangisetty  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57650  
 
 
  anchore plugin isn't respecting engineRetries   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Assignee: 
 Daniel Nurmi Swathi Gangisetty  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199581.1558657756000.3309.1568397120288%40Atlassian.JIRA.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report fails due to missing javascript and css

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43075  
 
 
  Anchore plugin compatibility in context mode, report fails due to missing _javascript_ and css
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180185.1490290276000.3306.1568397060127%40Atlassian.JIRA.

[JIRA] (JENKINS-43075) Anchore plugin compatibility in context mode, report fails due to missing javascript and css

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-43075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Anchore plugin compatibility in context mode, report fails due to missing _javascript_ and css
 

  
 
 
 
 

 
 Closing the ticket as the issue cannot be reproduced after the above commit  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180185.1490290276000.3305.156839751%40Atlassian.JIRA.

[JIRA] (JENKINS-23743) Failure on Git Polling Log when using Linux Master and Windows Slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-23743  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-23743  
 
 
  Failure on Git Polling Log when using Linux Master and Windows Slave   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156130.1404999348000.3300.1568396880638%40Atlassian.JIRA.

[JIRA] (JENKINS-23743) Failure on Git Polling Log when using Linux Master and Windows Slave

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Waite updated  JENKINS-23743  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-23743  
 
 
  Failure on Git Polling Log when using Linux Master and Windows Slave   
 

  
 
 
 
 

 
Change By: 
 Mark Waite  
 
 
Status: 
 Fixed but Unreleased Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156130.1404999348000.3302.1568396880663%40Atlassian.JIRA.

[JIRA] (JENKINS-59063) anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty assigned an issue to Swathi Gangisetty  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59063  
 
 
  anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items   
 

  
 
 
 
 

 
Change By: 
 Swathi Gangisetty  
 
 
Assignee: 
 Daniel Nurmi Swathi Gangisetty  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201422.1566551844000.3293.1568396700558%40Atlassian.JIRA.

[JIRA] (JENKINS-59063) anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items

Title: Message Title


 
 
 
 

 
 
 

 
   
 Swathi Gangisetty commented on  JENKINS-59063  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: anchore plugin: Add a new option for setting builds to "UNSTABLE" for "WARN" items   
 

  
 
 
 
 

 
 Hello Bernhard Kaszt, apologies for the late response. I think flagging the build as unstable is a good idea. Especially when anchore engine (policy check op) produces a warn result. I'll add this to our backlog for next release. If you've already made the changes to the plugin to do this, please submit a PR and I'd be happy to merge it in. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201422.1566551844000.3290.1568396700499%40Atlassian.JIRA.

[JIRA] (JENKINS-23743) Failure on Git Polling Log when using Linux Master and Windows Slave

2019-09-13 Thread peter.rica...@gmail.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 peter ricardo commented on  JENKINS-23743  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure on Git Polling Log when using Linux Master and Windows Slave   
 

  
 
 
 
 

 
 The issue has been resolved by updating the client version 'git' on the slave. It went back to work after this update. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156130.1404999348000.3287.1568396460229%40Atlassian.JIRA.

[JIRA] (JENKINS-59368) Can upload from non-maven projects or not?

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59368  
 
 
  Can upload from non-maven projects or not?   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Suresh Kumar  
 
 
Components: 
 nexus-artifact-uploader-plugin  
 
 
Created: 
 2019-09-13 17:28  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Brian J Murrell  
 

  
 
 
 
 

 
 Right at the top of the wiki page for the Nexus Artifact Uploader it states: 

This plugin goal is to upload artifacts generated from non-maven projects to Nexus
 But a question was asked: 

How do I set a GroupId for a raw repository? 
I can not find a Nexus 3 setting to add a GroupId to a raw repository, and this plugin requires a GroupId to be specified.
 Which was answered with: 

Plugin supports only Maven type repositories in Nexus.
 So I am just trying to square that answer with the statement from the top of the wiki: 

This plugin goal is to upload artifacts generated from non-maven projects to Nexus
 before I expend time to dive in and try to use it.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman commented on  JENKINS-59321  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
 Steve Boardwell For the JobDSL syntax change, you are correct - the underlying data representation changed.  The JobDSL syntax is reflecting that.  Could you open a separate issue for that? Maybe something to fix on the JobDSL side or as a symbol annotation in this plugin. As for the exception, it looks like this only happens if you try to save a blank job but also for an invalid URL.  That shouldn't be the case. It should be a validation error, but not an explosion.    It does also result in a Jenkins error webpage with this message:  java.lang.IllegalArgumentException: Repository URL must not be empty at org.jenkinsci.plugins.github_branch_source.GitHubRepositoryInfo.forRepositoryUrl(GitHubRepositoryInfo.java:84) at org.jenkinsci.plugins.github_branch_source.GitHubSCMSource.(GitHubSCMSource.java:336) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at org.kohsuke.stapler.RequestImpl.invokeConstructor(RequestImpl.java:529) at org.kohsuke.stapler.RequestImpl.instantiate(RequestImpl.java:784) at org.kohsuke.stapler.RequestImpl.access$200(RequestImpl.java:83) at org.kohsuke.stapler.RequestImpl$TypePair.convertJSON(RequestImpl.java:678)     This should be a validation error      
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI

2019-09-13 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-59145  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI   
 

  
 
 
 
 

 
 Please provide a complete Jenkins log from (and including) startup sequence to when you hit this issue.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201579.156710687.3275.1568394480469%40Atlassian.JIRA.

[JIRA] (JENKINS-51440) Configure alternative context for each Tomcat container

2019-09-13 Thread jul...@beti.name (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julien Béti commented on  JENKINS-51440  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Configure alternative context for each Tomcat container   
 

  
 
 
 
 

 
 Hello, I'm not sure the work done in JENKINS-3624 covers the requirement here. JENKINS-3624 focuses on manager path whereas this patch adds the possibility to have a different application's context path for each container. The important change in my PR the TomcatAdapater#redeployFile override Would you accept an updated PR to achieve this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190796.1526817852000.3277.1568394480497%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Summary: 
 The git github -branch-source plugin  seems to have broken from 2.5.3 -> 2.5.7  throws InvocationTargetException when creating  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3268.1568394300246%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) github-branch-source plugin throws InvocationTargetException when creating

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  github-branch-source plugin throws InvocationTargetException when creating   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Component/s: 
 job-dsl-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3270.1568394300277%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) The git-branch-source plugin seems to have broken from 2.5.3 -> 2.5.7

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  The git-branch-source plugin seems to have broken from 2.5.3 -> 2.5.7   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Summary: 
 The git-branch-source plugin  JobDSL syntax breaking change (  seems to have broken from 2.5.3 -> 2.5.7 )  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3266.1568394240299%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) git-branch-source plugin JobDSL syntax breaking change (2.5.3 -> 2.5.7)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  git-branch-source plugin JobDSL syntax breaking change (2.5.3 -> 2.5.7)   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Labels: 
 pipeline-triaged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3264.1568393940130%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) git-branch-source plugin JobDSL syntax breaking change (2.5.3 -> 2.5.7)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  git-branch-source plugin JobDSL syntax breaking change (2.5.3 -> 2.5.7)   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Summary: 
 git-branch-source plugin JobDSL syntax breaking change  Description The git-branch-source plugin seems to have broken with the latest update  ( from  2.5.3 -> 2.5.7)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3262.1568393880443%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) git-branch-source plugin JobDSL syntax breaking change Description The git-branch-source plugin seems to have broken with the latest update (from 2.5.3 -> 2.5.7)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  git-branch-source plugin JobDSL syntax breaking change Description The git-branch-source plugin seems to have broken with the latest update (from 2.5.3 -> 2.5.7)   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Summary: 
 git-branch-source plugin JobDSL syntax breaking changeDescription The git-branch-source plugin seems to have broken with the latest update (from 2.5.3 -> 2.5.7)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3260.1568393880403%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) git-branch-source plugin JobDSL syntax breaking change

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  git-branch-source plugin JobDSL syntax breaking change
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Summary: 
 git-branch-source plugin JobDSL syntax breaking change
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3258.1568393880378%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) git-branch-source plugin JobDSL syntax breaking change

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  git-branch-source plugin JobDSL syntax breaking change   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Component/s: 
 job-dsl-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3253.1568393760394%40Atlassian.JIRA.

[JIRA] (JENKINS-59321) git-branch-source plugin JobDSL syntax breaking change

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59321  
 
 
  git-branch-source plugin JobDSL syntax breaking change   
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Summary: 
 The  git-branch-source plugin  seems to have broken from 2.5.3 -> 2.5.7  JobDSL syntax breaking change  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201872.1568238258000.3251.1568393760366%40Atlassian.JIRA.

[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data

2019-09-13 Thread db...@cloudbees.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-57528  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkins in Docker does not install detached plugins when there is no UC data   
 

  
 
 
 
 

 
 Fun fact: When greenballs was last released in 2015, 1.638 was the current weekly release, not 1.440 (released 2011). So the implied dependencies to… 
 
external-monitor-job 
ldap 
pam-auth 
mailer 
matrix-auth 
windows-slaves 
antisamy-markup-formatter 
matrix-project 
junit 
 i.e. roughly 2/3 of all its dependencies, were basically the maintainer's choice.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3237.1568393280421%40Atlassian.JIRA.

[JIRA] (JENKINS-59319) WaitUntil step missing "initialRecurrencePeriod" option

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum edited a comment on  JENKINS-59319  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: WaitUntil step missing "initialRecurrencePeriod" option   
 

  
 
 
 
 

 
 The original commit was from February, but it was not merged until June, see [the merge commit| [ https://github.com/jenkinsci/workflow-basic-steps-plugin/commit/d08ce2e5c52700f0899ed3e41d684dc78045ad34] ] . I'll try to release workflow-basic-steps soon (in the next two weeks or so) to pick up the change.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201870.1568228118000.3201.1568391360408%40Atlassian.JIRA.

[JIRA] (JENKINS-59319) WaitUntil step missing "initialRecurrencePeriod" option

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59319  
 
 
  WaitUntil step missing "initialRecurrencePeriod" option   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201870.1568228118000.3203.1568391360435%40Atlassian.JIRA.

[JIRA] (JENKINS-59319) WaitUntil step missing "initialRecurrencePeriod" option

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-59319  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: WaitUntil step missing "initialRecurrencePeriod" option   
 

  
 
 
 
 

 
 The original commit was from February, but it was not merged until June, see [the merge commit|https://github.com/jenkinsci/workflow-basic-steps-plugin/commit/d08ce2e5c52700f0899ed3e41d684dc78045ad34]. I'll try to release workflow-basic-steps soon (in the next two weeks or so) to pick up the change.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201870.1568228118000.3199.1568391360380%40Atlassian.JIRA.

[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever

Title: Message Title

Devin Nusbaum edited a comment on JENKINS-59083

Re: Builds stuck on "is already in progress" forever

Ok, at least one way that this could be happening should be fixed as of Pipeline: Job Plugin 2. 34 35 . If you end up finding this ticket when running Pipeline: Job Plugin 2. 34 35 or higher because you are seeing the following error in your logs, please file a new ticket, and include the full stack trace:{code :java }java.lang.IllegalStateException: trying to open a build log on … after it has completed{code} EDIT: Note that if you are not running Pipeline: Groovy Plugin 2.74 or later, you will see this error message for one case that has already been fixed, so I would recommend upgrading to Pipeline: Job Groovy Plugin 2. 35 74 or newer which will automatically update Pipeline: Groovy Plugin as well later .

Add Comment

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.3192.1568389140221%40Atlassian.JIRA.

[JIRA] (JENKINS-59083) Builds stuck on "is already in progress" forever

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59083  
 
 
  Builds stuck on "is already in progress" forever   
 

  
 
 
 
 

 
Change By: 
 Devin Nusbaum  
 
 
Released As: 
 workflow-job 2. 34 35  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201473.1566824316000.3189.1568389020391%40Atlassian.JIRA.

[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Sears updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56750  
 
 
  Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.   
 

  
 
 
 
 

 
Change By: 
 Jim Sears  
 
 
Comment: 
 Hi [~aslaakso], I've got the HPI file. I'm not familiar with HPI extension. Can you please tell me what or where this file is supposed to go or how to install on the Jenkins server?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.3172.1568386263047%40Atlassian.JIRA.

[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jim Sears commented on  JENKINS-56750  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.   
 

  
 
 
 
 

 
 Hi Anda Sorina Laakso, I've got the HPI file. I'm not familiar with HPI extension. Can you please tell me what or where this file is supposed to go or how to install on the Jenkins server?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198392.1553542192000.3160.1568385600242%40Atlassian.JIRA.

[JIRA] (JENKINS-59367) Windows node issue : 403 Uncategorized

2019-09-13 Thread nicolas.roui...@socgen.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas Rouillé updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59367  
 
 
  Windows node issue : 403 Uncategorized   
 

  
 
 
 
 

 
Change By: 
 Nicolas Rouillé  
 

  
 
 
 
 

 
 Hi Hello ,Jenkins ver. 2.176.3Jenkins Server and Windows node  java version:{quote}C:\windows\system32>java -versionjava version "1.8.0_91"Java(TM) SE Runtime Environment (build 1.8.0_91-b15)Java HotSpot(TM) 64-Bit Server VM (build 25.91-b15, mixed mode){quote}Windows node : Windows 7 Entreprise Service Pack 1Issue with node :{quote}C:\windows\system32>java -jar D:\jenkins_slave\slave.jar -jnlpUrl [http://mydomain/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp|http://integrationcontinue.assu.socgen/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp] -secret mySecretKeyForW7NodeHere -workDir "d:\jenkins_slave"sept. 13, 2019 2:06:09 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDirINFOS: Using d:\jenkins_slave\remoting as a remoting work directoryBoth error and output logs will be printed to d:\jenkins_slave\remotingFailing to obtain [http://mydomain/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp?encrypt=true|http://integrationcontinue.assu.socgen/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp?encrypt=true]java.io.IOException: Failed to load [http://|http://integrationcontinue.assu.socgen/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp?encrypt=true] [mydomain|http://integrationcontinue.assu.socgen/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp?encrypt=true] [/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp?encrypt=true|http://integrationcontinue.assu.socgen/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp?encrypt=true]: 403 Uncategorized    at hudson.remoting.Launcher.parseJnlpArguments(Launcher.java:496)    at hudson.remoting.Launcher.run(Launcher.java:322)    at hudson.remoting.Launcher.main(Launcher.java:283)Waiting 10 seconds before retry{quote} The log files are empty.All other Windows nodes are working properly.Does anyone have an idea of the problem?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment

[JIRA] (JENKINS-59367) Windows node issue : 403 Uncategorized

2019-09-13 Thread nicolas.roui...@socgen.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas Rouillé updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59367  
 
 
  Windows node issue : 403 Uncategorized   
 

  
 
 
 
 

 
Change By: 
 Nicolas Rouillé  
 
 
Summary: 
 Windows node  issur  issue  : 403 Uncategorized  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201918.1568384698000.3157.1568384940117%40Atlassian.JIRA.

[JIRA] (JENKINS-59276) HTML files containing scalar vector graphics (.svg files) are not displaying properly in Jenkins

2019-09-13 Thread hk...@mathworks.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hussain Khan commented on  JENKINS-59276  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: HTML files containing scalar vector graphics (.svg files) are not displaying properly in Jenkins   
 

  
 
 
 
 

 
 Is there any workaround for this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201776.1568010115000.3156.1568384760255%40Atlassian.JIRA.

[JIRA] (JENKINS-59367) Windows node issur : 403 Uncategorized

2019-09-13 Thread nicolas.roui...@socgen.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas Rouillé created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59367  
 
 
  Windows node issur : 403 Uncategorized   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-09-13 14:24  
 
 
Labels: 
 slave windows  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Nicolas Rouillé  
 

  
 
 
 
 

 
 Hi, Jenkins ver. 2.176.3 Jenkins Server and Windows node  java version: 

C:\windows\system32>java -version java version "1.8.0_91" Java(TM) SE Runtime Environment (build 1.8.0_91-b15) Java HotSpot(TM) 64-Bit Server VM (build 25.91-b15, mixed mode)
 Windows node : Windows 7 Entreprise Service Pack 1 Issue with node : 

C:\windows\system32>java -jar D:\jenkins_slave\slave.jar -jnlpUrl http://mydomain/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp -secret mySecretKeyForW7NodeHere -workDir "d:\jenkins_slave" 
sept. 13, 2019 2:06:09 PM org.jenkinsci.remoting.engine.WorkDirManager initializeWorkDir 
INFOS: Using d:\jenkins_slave\remoting as a remoting work directory 
Both error and output logs will be printed to d:\jenkins_slave\remoting 
Failing to obtain http://mydomain/jenkins/computer/HML%20poste%20A10/slave-agent.jnlp?encrypt=true 
java.io.IOException: Failed to load http:// mydomain

[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data

2019-09-13 Thread jgl...@cloudbees.com (JIRA)

Title: Message Title

Jesse Glick commented on JENKINS-57528

Re: Jenkins in Docker does not install detached plugins when there is no UC data

disabling them because they aren't actually used but are pulling in ancient versions with tons of security warnings
I am not aware of which ancient versions or security warnings you are referring to here. All detached plugins are expected to be updated in tandem with security advisories. If you see differently, please file a bug report (or a patch). CC Daniel Beck

I don't see any point in re-releasing the plugin or upgrading core requirements
See discussion in JENKINS-28942. My standing proposal would require the plugin to be re-released, with metadata indicating the most recent core version against which it has been successfully tested, but would not require the minimum core version to be changed.

Add Comment

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3150.1568383380632%40Atlassian.JIRA.

[JIRA] (JENKINS-57537) catchError - Expecting "class hudson.model.Result" for parameter "buildResult"

Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-57537  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: catchError - Expecting "class hudson.model.Result" for parameter "buildResult"   
 

  
 
 
 
 

 
 Andrew Mullens Yes, this issue is fixed, see this comment. Make sure you are passing a String to catchError and not an object of type Result. If that still isn't working for you, please post an extract from your Jenkinsfile showing how you are using catchError.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199445.1558161153000.3143.1568383380503%40Atlassian.JIRA.

[JIRA] (JENKINS-57537) catchError - Expecting "class hudson.model.Result" for parameter "buildResult"

2019-09-13 Thread wamc...@yahoo.com (JIRA)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Mullens commented on  JENKINS-57537  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: catchError - Expecting "class hudson.model.Result" for parameter "buildResult"   
 

  
 
 
 
 

 
 Hello, Did anyone ever solve this issue for Declarative pipeline? The catchError still give the same error.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199445.1558161153000.3134.1568383020512%40Atlassian.JIRA.

[JIRA] (JENKINS-43982) Show stage view for individual jobs

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-43982  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Show stage view for individual jobs   
 

  
 
 
 
 

 
 Pity that the PR for this is stagnating.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181517.1493721583000.3108.1568380920833%40Atlassian.JIRA.

[JIRA] (JENKINS-58604) Full Stage View only showing one

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell commented on  JENKINS-58604  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Full Stage View only showing one   
 

  
 
 
 
 

 
 This really is quite hideous because this is really the only alternative to Blue Ocean[1] to seeing the individual stages in pipeline jobs. Mark Hermon Can you expand a bit on your findings? [1]Blue Ocean is too big, bloated and network heavy with it's constant refreshes to be effectively usable.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200764.1563816065000.3104.1568380500141%40Atlassian.JIRA.

[JIRA] (JENKINS-58604) Full Stage View only showing one

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell assigned an issue to Sam Van Oort  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58604  
 
 
  Full Stage View only showing one   
 

  
 
 
 
 

 
Change By: 
 Brian J Murrell  
 
 
Assignee: 
 Brian J Murrell Sam Van Oort  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200764.1563816065000.3101.1568380260430%40Atlassian.JIRA.

[JIRA] (JENKINS-58604) Full Stage View only showing one

Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian J Murrell assigned an issue to Brian J Murrell  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58604  
 
 
  Full Stage View only showing one   
 

  
 
 
 
 

 
Change By: 
 Brian J Murrell  
 
 
Assignee: 
 Sam Van Oort Brian J Murrell  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200764.1563816065000.3099.1568380260406%40Atlassian.JIRA.

[JIRA] (JENKINS-57528) Jenkins in Docker does not install detached plugins when there is no UC data

2019-09-13 Thread rasp...@gmail.com (JIRA)

Title: Message Title

Krzysztof Malinowski commented on JENKINS-57528

Re: Jenkins in Docker does not install detached plugins when there is no UC data

I got that. But plugins may have or may have not used them, as there was no possibility to declare. If core will keep reinstantiating them, we will never be able to get rid of this functionality which was unused. For instance, I may be using Green Balls that only changes icon colors, but it incorporates 14 implied plugins. I am pretty sure it does not use LDAP, JDK installer or Windows agents, yet they keep getting installed, because of the time that the plugin was released, they were part of Jenkins. I don't see any point in re-releasing the plugin or upgrading core requirements as the functionality is quite simple and seems complete, so there is no point in artificial release. I would like to get rid of the functionality I don't need though to reduce the bloat, but the core does not want to let it go. I really believe it should be maintained by people maintaining their Docker images. At least there should be an option I could set to say: 'Yes, I know what I'm doing, thank you.'

Add Comment

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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199434.155810265.3088.1568379240349%40Atlassian.JIRA.

[JIRA] (JENKINS-59366) Reduce test time under 20 minutes for StageViewTest (21 min)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59366  
 
 
  Reduce test time under 20 minutes for StageViewTest (21 min)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2019-09-13 12:46  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oliver Gondža  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are

[JIRA] (JENKINS-59363) Reduce test time under 20 minutes for WorkflowPluginTest (35 min)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59363  
 
 
  Reduce test time under 20 minutes for WorkflowPluginTest (35 min)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2019-09-13 12:45  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oliver Gondža  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are

[JIRA] (JENKINS-59364) Reduce test time under 20 minutes for SubversionPluginTest (31 min)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59364  
 
 
  Reduce test time under 20 minutes for SubversionPluginTest (31 min)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2019-09-13 12:45  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oliver Gondža  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are

[JIRA] (JENKINS-59365) Reduce test time under 20 minutes for NodeLabelParameterPluginTest (26 min)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59365  
 
 
  Reduce test time under 20 minutes for NodeLabelParameterPluginTest (26 min)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2019-09-13 12:45  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oliver Gondža  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because

[JIRA] (JENKINS-59360) Reduce test time under 20 minutes for FtpPublishPluginTest (43 min)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59360  
 
 
  Reduce test time under 20 minutes for FtpPublishPluginTest (43 min)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2019-09-13 12:44  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oliver Gondža  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are

[JIRA] (JENKINS-59361) Reduce test time under 20 minutes for CIFSPublishPluginTest (42 min)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59361  
 
 
  Reduce test time under 20 minutes for CIFSPublishPluginTest (42 min)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2019-09-13 12:44  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oliver Gondža  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you

[JIRA] (JENKINS-59362) Reduce test time under 20 minutes for GradlePluginTest (38 min)

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oliver Gondža created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59362  
 
 
  Reduce test time under 20 minutes for GradlePluginTest (38 min)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Oliver Gondža  
 
 
Components: 
 acceptance-test-harness  
 
 
Created: 
 2019-09-13 12:44  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Oliver Gondža  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
You received this message because you are

[JIRA] (JENKINS-59359) Reduce test time under 20 minutes for WarningsNextGenerationPluginTest (46 min)