[JIRA] (JENKINS-38316) Entering, then cancelling, quiet mode causes builds to hang

2019-01-04 Thread totoroliu1...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rick Liu commented on  JENKINS-38316  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Entering, then cancelling, quiet mode causes builds to hang   
 

  
 
 
 
 

 
 This still happened to Jenkins v*2.138.4* LTS  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-42893) Job-dsl-plugin support for parameterized scheduler plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker edited a comment on  JENKINS-42893  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job-dsl-plugin support for parameterized scheduler plugin   
 

  
 
 
 
 

 
 This is supported by the [ Automatically Generated Dynamic  DSL|https://github.com/jenkinsci/job-dsl-plugin/wiki/ Automatically Dynamic - Generated- DSL]:{code:java}job(String name) {  triggers {parameterizedTimerTrigger {  // follow convension of cron, schedule with name=value pairs at the end of each line.  parameterizedSpecification(String value)}  }}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-50751) Link created by naginator plugin contains comma in job numbers over 999

2019-01-04 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam commented on  JENKINS-50751  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Link created by naginator plugin contains comma in job numbers over 999   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/naginator-plugin/pull/45  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-50751) Link created by naginator plugin contains comma in job numbers over 999

2019-01-04 Thread de...@ikedam.jp (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 ikedam started work on  JENKINS-50751  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 ikedam  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53935) Tests: Introduce a "SmokeTest" category in the Core's JTH test suite

2019-01-04 Thread sharmaabhyud...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abhyudaya Sharma commented on  JENKINS-53935  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Tests: Introduce a "SmokeTest" category in the Core's JTH test suite   
 

  
 
 
 
 

 
 Hi! I'd like to work on this. Can I assign it to myself?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53468) Since 1.27 update Channel is closing or has closed down

2019-01-04 Thread j...@keyba.se (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 John Zila commented on  JENKINS-53468  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Since 1.27 update Channel is closing or has closed down   
 

  
 
 
 
 

 
 Any news here? I'm having to continue holding back my ssh-slaves plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55379) add support for warnings-ng-plugin to DSL Plugin

2019-01-04 Thread jonud...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jon Udaondo commented on  JENKINS-55379  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: add support for warnings-ng-plugin to DSL Plugin   
 

  
 
 
 
 

 
 Daniel Spilker where can I find documentation? Where have you found that code? Thank you.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54937) java.lang.IllegalStateException: Cannot delete last view

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54937  
 
 
  java.lang.IllegalStateException: Cannot delete last view   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Issue Type: 
 Task Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54942) Source details inference fails on Java 11

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54942  
 
 
  Source details inference fails on Java 11   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Issue Type: 
 Task Bug  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54510) Job dsl doesn't update script approval when job already exists

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-54510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Job dsl doesn't update script approval when job already exists   
 

  
 
 
 
 

 
 I think this is not a Job DSL issue. Job DSL does not interfere with script approval when generating pipeline jobs. The problem is probably step 6. Running the seed job again (step 7) has no effect since Job DSL will not detect a diff to the existing config and thus will not update the config. I also think that the setup is questionable. It should suffice to restore the seed job, then run the seed job to generate any other jobs. In this case the pipeline job would be created from scratch without problems.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54510) Job dsl doesn't update script approval when job already exists

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54510  
 
 
  Job dsl doesn't update script approval when job already exists   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 script-security-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54510) Job dsl doesn't update script approval when job already exists

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54510  
 
 
  Job dsl doesn't update script approval when job already exists   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Component/s: 
 job-dsl-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55261) Errors visible in UI are hidden if you use job-dsl

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55261  
 
 
  Errors visible in UI are hidden if you use job-dsl   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-52743) authenticationToken has been deprecated.

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52743  
 
 
  authenticationToken has been deprecated.   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Component/s: 
 _unsorted  
 
 
Component/s: 
 pipeline  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-52743) authenticationToken has been deprecated.

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker resolved as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52743  
 
 
  authenticationToken has been deprecated.   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-52985) Job DSL multibranchPipelineJob branchSources does not have `svn`

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is already supported by the Dynamic DSL: 

 

multibranchPipelineJob('example') {
  branchSources {
branchSource {
  source {
subversionSCMSource {
  id('a-unique-id')
  remoteBase('http://svn/svn/test_repo/trunk')
  credentialsId('svn')
}
  }
}
  }
} 
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-52985  
 
 
  Job DSL multibranchPipelineJob branchSources does not have `svn`   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed 

[JIRA] (JENKINS-53103) Pipeline does not pass environment variables to JobDsl

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 You need to update to Job DSL 1.66 or later.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53103  
 
 
  Pipeline does not pass environment variables to JobDsl   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API

2019-01-04 Thread edkar...@hotmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eduard Karlin commented on  JENKINS-54632  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: dsl job doesn't create a build step for Performance Center using Jenkins API   
 

  
 
 
 
 

 
 Hey Daniel, Thanks for all your information! I just came from vacation and trying to debug again this issue. So far not working, but I'll try a few different things. We are running so many different scripts( ant, ruby, maven and etc) using different plugins, and somehow only integration with Performance center isn't working. I tried to get a pipeline syntax, but that url finds nothing. Should I add some specific plugin for that also? http://cdlvdiw703202:8080/job/pc_pipeline/pipeline-syntax/ Problem accessing /job/pc_pipeline/pipeline-syntax/. Reason:  Not Found Thanks, Eduard.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53339) Job Resume Option in a scripted Pipeline

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53339  
 
 
  Job Resume Option in a scripted Pipeline   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 build-pipeline-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53339) Job Resume Option in a scripted Pipeline

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53339  
 
 
  Job Resume Option in a scripted Pipeline   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Assignee: 
 Daniel Spilker  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53339) Job Resume Option in a scripted Pipeline

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53339  
 
 
  Job Resume Option in a scripted Pipeline   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Component/s: 
 job-dsl-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53520) Unable to set ref specs for Github Branch Source via DSL for multibranchPipelineJob

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Use a Configure Block to add any config that is not supported by built-in DSL or Dynamic DSL.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53520  
 
 
  Unable to set ref specs for Github Branch Source via DSL for multibranchPipelineJob   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53623) Add Job DSL support for Parameter Separator Plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-53623  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Add Job DSL support for Parameter Separator Plugin
 

  
 
 
 
 

 
 This is already supported by Dynamic DSL: 

 

job('example') {
  parameters {
parameterSeparatorDefinition {
  name('separator')
  separatorStyle('')
  sectionHeader('')
  sectionHeaderStyle('')
}
  }
} 
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53623) Add Job DSL support for Parameter Separator Plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53623  
 
 
  Add Job DSL support for Parameter Separator Plugin
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53830) unexpected "category" attributed in persisted xml

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated  JENKINS-53830  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53830  
 
 
  unexpected "category" attributed in persisted xml   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53878) Can not script AWS code pipeline through Job dsl plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-53878  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can not script AWS code pipeline through Job dsl plugin   
 

  
 
 
 
 

 
 A Configure Block can be used to generate any config that is neither supported by built-in DSL or dynamic DSL.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53878) Can not script AWS code pipeline through Job dsl plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker commented on  JENKINS-53878  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Can not script AWS code pipeline through Job dsl plugin   
 

  
 
 
 
 

 
 AWSCodePipelinePublisher needs to define a DataBoundConstructor with a List constructor to be able to be used in Job DSL.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53878) Can not script AWS code pipeline through Job dsl plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53878  
 
 
  Can not script AWS code pipeline through Job dsl plugin   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Issue Type: 
 Bug Improvement  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53962) Job DSL Support without Dynamic DSL

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 It is already supported, see https://jenkinsci.github.io/job-dsl-plugin/#path/job-wrappers-buildName  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-53962  
 
 
  Job DSL Support without Dynamic DSL   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Daniel Spilker  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54345) Job-DSL RTC Build Definition

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54345  
 
 
  Job-DSL RTC Build Definition   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Issue Type: 
 Task Improvement  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54456) using repoOwner and configure block creates two organizations

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 There are two problems in your script. 
 
The node names contain double underscores in github_branch_source 
The github context has no configure method. So the configure method from an outer context is called. In this case the configure method from the organizationFolder context is called. Since the organizations method has not been completed by the time when the configure method is called, the configure method will create a new GitHubSCMNavigator node. 
 

 

organizationFolder("test org") {
  description("configured with JCasC")
  displayName("test org")

  organizations {
github {
  repoOwner("owner")
  credentialsId("1234") 
}
  }
  configure { node ->
def traits = node / navigators / "org.jenkinsci.plugins.github__branch__source.GitHubSCMNavigator" / traits
traits << "jenkins.scm.impl.trait.RegexSCMSourceFilterTrait" {
  regex("ha*")
}
traits << "org.jenkinsci.plugins.github__branch__source.TagDiscoveryTrait" {}
traits << "org.jenkinsci.plugins.github__branch__source.BranchDiscoveryTrait" {
  strategyId("3")
}
  }
  
  triggers {
periodic(30)
  }
}
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54456  
 
 
  using repoOwner and configure block creates two organizations   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-55063) Warnings 5.0 Custom Parser documentation confusing, missing info on (multibranch) pipline usage.

2019-01-04 Thread tindall21...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Christopher Tindall reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 

 
stage('Static Analysis') {
steps {
sh 'find ./ -iname *.lua | xargs luacheck -d --no-max-line-length --no-global --formatter JUnit > ./static_analysis_junit.xml || true'
recordIssues tools: [
[tool: groovyScript(parserId: 'luacheck', pattern: 'static_analysis_junit.xml', reportEncoding:'UTF-8')]
]
/* unstableNewAll: 1 */
  }
} 

 Looks like this may have broken again. Using the above pipeline code the following error is generated: 

 
java.lang.UnsupportedOperationException: must specify $class with an implementation of class io.jenkins.plugins.analysis.core.model.Tool
	at org.jenkinsci.plugins.structs.describable.DescribableModel.resolveClass(DescribableModel.java:503)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:402)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:514)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:388)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.injectSetters(DescribableModel.java:361)
	at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:284)
Caused: java.lang.IllegalArgumentException: Could not instantiate {tools=[{tool=@groovyScript(parserId=luacheck,pattern=static_analysis_junit.xml,reportEncoding=UTF-8)}]} for IssuesRecorder(aggregatingResults?: boolean, blameDisabled?: boolean, enabledForFailure?: boolean, failedNewAll?: int, failedNewHigh?: int, failedNewLow?: int, failedNewNormal?: int, failedTotalAll?: int, failedTotalHigh?: int, failedTotalLow?: int, failedTotalNormal?: int, filters?: RegexpFilter{ExcludeCategory(pattern: String) | ExcludeFile(pattern: String) | ExcludeModule(pattern: String) | ExcludePackage(pattern: String) | ExcludeType(pattern: String) | IncludeCategory(pattern: String) | IncludeFile(pattern: String) | IncludeModule(pattern: String) | IncludePackage(pattern: String) | IncludeType(pattern: String)}[], healthy?: int, id?: String, ignoreFailedBuilds?: boolean, ignoreQualityGate?: boolean, minimumSeverity?: String, name?: String, referenceJobName?: String, sourceCodeEncoding?: String, tool?: Tool{AcuCobol(id?: String, name?: String, pattern?: String, reportEncoding?: String) | Ajc(id?: String, name?: String, pattern?: String, reportEncoding?: String) | AndroidLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | AnsibleLint(id?: String, ...
String, name?: String, pattern?: String, reportEncoding?: String) | SwiftLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TagList(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TaskingVx(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TiCss(id?: String, name?: String, pattern?: String, reportEncoding?: String) | Tnsdl(id?: String, name?: String, pattern?: String, reportEncoding?: String) | TsLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | Xlc(id?: String, name?: String, pattern?: String, reportEncoding?: String) | XmlLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | YamlLint(id?: String, name?: String, pattern?: String, reportEncoding?: String) | YuiCompressor(id?: String, name?: String, pattern?: String, reportEncoding?: String) | ZptLint(id?: String, name?: String, pattern?: String, reportEncoding?: String)}[], unhealthy?: int, unstableNewAll?: int, 

[JIRA] (JENKINS-44472) Preview Pattern results

2019-01-04 Thread vishalkhanna...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vishal Khanna assigned an issue to Vishal Khanna  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-44472  
 
 
  Preview Pattern results   
 

  
 
 
 
 

 
Change By: 
 Vishal Khanna  
 
 
Assignee: 
 Vishal Khanna  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-44472) Preview Pattern results

2019-01-04 Thread vishalkhanna...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Vishal Khanna started work on  JENKINS-44472  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Vishal Khanna  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55361) DescriptorExtensionList not locking correctly, leading to deadlocks

2019-01-04 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55361  
 
 
  DescriptorExtensionList not locking correctly, leading to deadlocks   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 

  
 
 
 
 

 
 From my analysis, and some of other issues reported speaking about deadlocks (JENKINS-20988, JENKINS-21034, JENKINS-31622, JENKINS-44564, JENKINS-49038, JENKINS-50663, JENKINS-54974), the issue lies in the [DescriptorExtensionList|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/DescriptorExtensionList.java], especially in the way it acquires its load lock. The DescriptorExtensionList [getLoadLock|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/DescriptorExtensionList.java#L174] method documentation indicates that it is taking part in the real load activity, and that as such, it can lock on *this *rather than on the *singleton Lock *used by ExtensionList.However, many plugins rely on a GlobalConfiguration object, which is acquired through a code similar to the following (which is actually explicitly recommended in [GlobalConfiguration documentation|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/jenkins/model/GlobalConfiguration.java#L28]).{code:java}public static SpecificPluginConfig get() {return GlobalConfiguration.all().get(SpecificPluginConfig.class);}{code}(the *all()* method from the GlobalConfiguration is returning a *DescriptorExtensionList*)As the configuration for a plugin can be called from many places (initialization of plugin, http requests, ...), it is very easy to have at the same time a DescriptorExtensionList being instantiated, needing in return an ExtensionList, while at the same time, some injection code will have taken the ExtensionList lock and will require DescriptorExtensionList one. Of course, some other uses of DescriptorExtensionList, not related to GlobalConfiguration, can also create the same kind of issues.Taking in to account that the lock is only taken when the list is initialized for the first time (in [ensureLoaded()|https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/java/hudson/ExtensionList.java#L316]), I would say that removing the override of [getLoadLock in DescriptorExtensionList|https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/DescriptorExtensionList.java#L178] should solve the issue at a very minimal cost, or at least make the lock the same as ExtensionList for Descriptor.class  
 

  
 
 
 
 

 
 
 

   

[JIRA] (JENKINS-54924) Script Runs In Script Console But Not Job DSL

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The Job DSL engine does not use the UberClassLoader, so classes from other plugins can not be imported in Job DSL scripts. In your case hudson.plugins.shelveproject.ShelveProjectTaskdef can not be imported. Since the script does not seem to use any Job DSL API, you can use the Groovy plugin to execute the script (System Groovy Script).  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54924  
 
 
  Script Runs In Script Console But Not Job DSL   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54984) PipelineJob() publishers deprecated - how to send a notifications

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 When using Pipeline jobs, sending build notifications is part of the pipeline definition. See for example https://jenkins.io/blog/2017/02/15/declarative-notifications/  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-54984  
 
 
  PipelineJob() publishers deprecated - how to send a notifications   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55005) gerrit-trigger

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is already supported by the Dynamic DSL: 

 

job('example') {
  triggers {
gerritTrigger {
  triggerOnEvents {
commentAddedContains {
  commentAddedCommentContains('TEST')
}
  }
}
  }
} 
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55005  
 
 
  gerrit-trigger   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-55190) Support "List of parameters to check" in Throttle Concurrent Builds Plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker edited a comment on  JENKINS-55190  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support "List of parameters to check" in Throttle Concurrent Builds Plugin   
 

  
 
 
 
 

 
 This is already supported by the [Dynamic DSL|https://github.com/jenkinsci/job-dsl-plugin/wiki/Dynamic-DSL]:{code}job('example') {  properties {throttleJobProperty {   maxConcurrentTotal(4)   limitOneJobWithMatchingParams(true)  paramsToUseForLimit('TEST')}  }} {code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55190) Support "List of parameters to check" in Throttle Concurrent Builds Plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is already supported by the Dynamic DSL: 

 

job('example') {
  properties {
throttleJobProperty {
  limitOneJobWithMatchingParams(true)
  paramsToUseForLimit('TEST')
}
  }
} 
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55190  
 
 
  Support "List of parameters to check" in Throttle Concurrent Builds Plugin   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an 

[JIRA] (JENKINS-55384) Cannot add environment variables in Jenkins Folder using Job DSL

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Instead of guessing the syntax, try the built-in Job DSL API reference. See Dynamic DSL for details. 

 

folder('example') {
  properties {
folderProperties {
  properties {
stringProperty {
  key('foo')
  value('bar')
}
   }
}
  }
} 
 

  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55384  
 
 
  Cannot add environment variables in Jenkins Folder using Job DSL   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Not A Defect  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins 

[JIRA] (JENKINS-55379) add support for warnings-ng-plugin to DSL Plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker edited a comment on  JENKINS-55379  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: add support for warnings-ng-plugin to DSL Plugin   
 

  
 
 
 
 

 
 The Warnings NG plugin is already supported by the [Dynamic DSL|https://github.com/jenkinsci/job-dsl-plugin/wiki/Dynamic-DSL]:{code}job('example') {  publishers {recordIssues {  tools {checkStyle {  pattern('myproject/build/reports/checkstyle/*.xml')}  }}  }}{code}If a plugin provides {{@DataBoundConstructor}}, {{@DataBoundSetter}} and {{@Symbol}}  annotation  annotations , no further action is required.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55379) add support for warnings-ng-plugin to DSL Plugin

2019-01-04 Thread m...@daniel-spilker.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Spilker closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The Warnings NG plugin is already supported by the Dynamic DSL: 

 

job('example') {
  publishers {
recordIssues {
  tools {
checkStyle {
  pattern('myproject/build/reports/checkstyle/*.xml')
}
  }
}
  }
}
 

 If a plugin provides @DataBoundConstructor, @DataBoundSetter and @Symbol annotation, no further action is required.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55379  
 
 
  add support for warnings-ng-plugin to DSL Plugin   
 

  
 
 
 
 

 
Change By: 
 Daniel Spilker  
 
 
Status: 
 Open Closed  
 
 
Assignee: 
 Daniel Spilker  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was 

[JIRA] (JENKINS-54897) Unexpected error in launching a agent after restart

2019-01-04 Thread kuisathave...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ivan Fernandez Calvo commented on  JENKINS-54897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected error in launching a agent after restart   
 

  
 
 
 
 

 
 On the logs attached the retries are not working so the SSHLauncher should be blocked by other thread, it is possibly related to the credentials tracking issue JENKINS-49235 if you get a thread dump when the issue happens you can compare it to this troubleshooting threads-stuck-at-credentialsprovidertrackall  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55361) DescriptorExtensionList not locking correctly, leading to deadlocks

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Arnaud TAMAILLON  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55361  
 
 
  DescriptorExtensionList not locking correctly, leading to deadlocks   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Arnaud TAMAILLON  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55361) DescriptorExtensionList not locking correctly, leading to deadlocks

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick started work on  JENKINS-55361  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55361) DescriptorExtensionList not locking correctly, leading to deadlocks

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-55361  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55361  
 
 
  DescriptorExtensionList not locking correctly, leading to deadlocks   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 In  Progress  Review  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-01-04 Thread nataliem...@g.harvard.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natalie Matthews edited a comment on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
 Here you can see that I have SSH credentials set up.  !Screen Shot 2019-01-04 at 2.17.29 PM.png|thumbnail!  They show up when I use Git as a source.  !Screen Shot 2019-01-04 at 2.17.52 PM.png|thumbnail!  They do not show up when I use Bitbucket as a source  !  ! Screen Shot 2019-01-04 at 2.18.04 PM.png|thumbnail! I have this issue too. Can only use username/password credentials for Bitbucket Branch Source Plugin but I would like to use SSH. I can use SSH with git source, but I want the features of the Bitbucket Branch Source Plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-01-04 Thread nataliem...@g.harvard.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natalie Matthews edited a comment on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
  !Screen Shot 2019-01-04 at 2.17.29 PM.png|thumbnail!  !Screen Shot 2019-01-04 at 2.17.52 PM.png|thumbnail!  !Screen Shot 2019-01-04 at 2.18.04 PM.png|thumbnail!  I have this issue too. Can only use username/password credentials for Bitbucket Branch Source Plugin but I would like to use SSH. I can use SSH with git source, but I want the features of the Bitbucket Branch Source Plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-01-04 Thread nataliem...@g.harvard.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natalie Matthews updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48897  
 
 
  Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
Change By: 
 Natalie Matthews  
 
 
Attachment: 
 Screen Shot 2019-01-04 at 2.17.52 PM.png  
 
 
Attachment: 
 Screen Shot 2019-01-04 at 2.18.04 PM.png  
 
 
Attachment: 
 Screen Shot 2019-01-04 at 2.17.29 PM.png  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-01-04 Thread nataliem...@g.harvard.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natalie Matthews edited a comment on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
  !Screen Shot 2018-01-11 at 14.11.34.png|thumbnail!  I have this issue too. Can only use username/password credentials for Bitbucket Branch Source Plugin but I would like to use SSH. I can use SSH with git source, but I want the features of the Bitbucket Branch Source Plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-01-04 Thread nataliem...@g.harvard.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natalie Matthews edited a comment on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
  !Screen Shot 2018-01-11 at 14.11.34.png|thumbnail!  I have this issue too. Can only use username/password credentials for Bitbucket Branch Source Plugin but I would like to use SSH. I can use SSH with git source, but I want the features of the Bitbucket Branch Source Plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54786) Launch command should include an env var for the name of the node

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-54786  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54786  
 
 
  Launch command should include an env var for the name of the node   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Fixed but Unreleased Resolved  
 
 
Released As: 
 1.3  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-5399) Need 'run a command on master to shutdown this slave'

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-5399  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need 'run a command on master to shutdown this slave'   
 

  
 
 
 
 

 
 JENKINS-50842 sounds more promising on the face of it.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-7165) Execute a command on master to launch JNLP on slave

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-7165  
 
 
  Execute a command on master to launch JNLP on slave   
 

  
 
 
 
 

 
 This is so different from CommandLauncher it would best be done as an independent plugin.  
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Issue Type: 
 Improvement New Feature  
 
 
Component/s: 
 plugin-proposals  
 
 
Component/s: 
 command-launcher-plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-5399) Need 'run a command on master to shutdown this slave'

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-5399  
 
 
  Need 'run a command on master to shutdown this slave'   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-7165) Execute a command on master to launch JNLP on slave

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-7165  
 
 
  Execute a command on master to launch JNLP on slave   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54502) Jenkins crashed when a running build was aborted.

2019-01-04 Thread sji...@407etr.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Jiang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54502  
 
 
  Jenkins crashed when a running build was aborted.   
 

  
 
 
 
 

 
Change By: 
 Scott Jiang  
 
 
Summary: 
 Jenkins crashed when a  running  build was aborted  due to timeout .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-23110) additional ssh command before ssh command that starts agent.jar results in StreamCorruptedException: invalid stream header: 090CACED

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-23110  
 
 
  additional ssh command before ssh command that starts agent.jar results in StreamCorruptedException: invalid stream header: 090CACED   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-50842) command-launcher terminates the process

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50842  
 
 
  command-launcher terminates the process
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Assignee: 
 Jesse Glick  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54502) Jenkins crashed when a build was aborted due to timeout.

2019-01-04 Thread sji...@407etr.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Jiang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54502  
 
 
  Jenkins crashed when a build was aborted due to timeout.   
 

  
 
 
 
 

 
Change By: 
 Scott Jiang  
 

  
 
 
 
 

 
 After recently updating to version 2.149 or 2.150,  Jenkins crashed if  aborting  a  job tried to abort due to configured time out for the job. From Windows Task Manager we saw the Jenkins processes were gone, but the program being executed by the job was still  running  (instead that the program should be stopped by Jenkins abort action).[Update] Aborting a running job  build  no matter automatically or manually  crashes  resulted in  Jenkins  crashed itself .      The below shows Jenkins job log:{code:java}C:\FitNesseForAppian>start /b /wait java -jar fitnesse-standalone.jar -p 8980 -c "TransponderNewLeaseTestSuite.IntegrationTestSuite.WebServiceInitUnauthNewOopPlateNameMatchPacFulfill?test=text" Nov 06, 2018 3:45:59 PM fitnesse.ConfigurationParameter loadPropertiesINFO: No configuration file found (C:\FitNesseForAppian\plugins.properties)Bootstrapping FitNesse, the fully integrated standalone wiki and acceptance testing framework.root page: fitnesse.wiki.fs.FileSystemPage at .\FitNesseRoot#latestlogger: noneauthenticator: fitnesse.authentication.PromiscuousAuthenticatorpage factory: fitnesse.html.template.PageFactorypage theme: bootstrapExecuting command: Etr407AppianTest.TransponderManagement.TransponderNewLeaseTestSuite.IntegrationTestSuite.WebServiceInitUnauthNewOopPlateNameMatchPacFulfill?test=textStarting Test System: slim:fitnesse.slim.SlimService.Build timed out (after 3 minutes). Marking the build as aborted.{code}The above job executed a fitnesse script, but the same issue was able to reproduce from running other program, like Test Studio script. In jenkins,err.log I couldn't find any useful/related log.  Could anyone please help to investigate this annoying issue?  Environment: Windows  2012R2  2012 R2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
   

[JIRA] (JENKINS-54502) Jenkins crashed when a build was aborted due to timeout.

2019-01-04 Thread sji...@407etr.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Jiang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54502  
 
 
  Jenkins crashed when a build was aborted due to timeout.   
 

  
 
 
 
 

 
Change By: 
 Scott Jiang  
 
 
Labels: 
 Aborting Crash jenkins  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54502) Jenkins crashed when a build was aborted due to timeout.

2019-01-04 Thread sji...@407etr.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Jiang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54502  
 
 
  Jenkins crashed when a build was aborted due to timeout.   
 

  
 
 
 
 

 
Change By: 
 Scott Jiang  
 
 
Labels: 
 Crash jenkins  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54786) Launch command should include an env var for the name of the node

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-54786  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Launch command should include an env var for the name of the node   
 

  
 
 
 
 

 
 

There appear to be some things which interfere with $ and _ in the Launch command field.
 Because the launch command is tokenized by Jenkins and then exec’d as is—it does not run a Bourne shell. You can probably use something like 

 

sh -c "exec start-agent $NODE_NAME"
 

 (Note that Jenkins treats " as an indication to not tokenize the interior; it does not interpolate variables in any event. So this may look confusing.)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-48897) Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline

2019-01-04 Thread nataliem...@g.harvard.edu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Natalie Matthews commented on  JENKINS-48897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot add credentials for Bitbucket on branch sources section in Multibranch pipeline   
 

  
 
 
 
 

 
 I have this issue too. Can only use username/password credentials for Bitbucket Branch Source Plugin but I would like to use SSH. I can use SSH with git source, but I want the features of the Bitbucket Branch Source Plugin.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54502) Jenkins crashed when a build was aborted due to timeout.

2019-01-04 Thread sji...@407etr.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Scott Jiang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54502  
 
 
  Jenkins crashed when a build was aborted due to timeout.   
 

  
 
 
 
 

 
Change By: 
 Scott Jiang  
 

  
 
 
 
 

 
 After recently updating to version 2.149 or 2.150, Jenkins crashed if a job tried to abort due to configured time out for the job. From Windows Task Manager we saw the Jenkins processes were gone, but the program being executed by the job was still running (instead that the program should be stopped by Jenkins abort action).     [Update] Aborting a running job no matter automatically or manually crashes Jenkins.    The below shows Jenkins job log:{code:java}C:\FitNesseForAppian>start /b /wait java -jar fitnesse-standalone.jar -p 8980 -c "TransponderNewLeaseTestSuite.IntegrationTestSuite.WebServiceInitUnauthNewOopPlateNameMatchPacFulfill?test=text" Nov 06, 2018 3:45:59 PM fitnesse.ConfigurationParameter loadPropertiesINFO: No configuration file found (C:\FitNesseForAppian\plugins.properties)Bootstrapping FitNesse, the fully integrated standalone wiki and acceptance testing framework.root page: fitnesse.wiki.fs.FileSystemPage at .\FitNesseRoot#latestlogger: noneauthenticator: fitnesse.authentication.PromiscuousAuthenticatorpage factory: fitnesse.html.template.PageFactorypage theme: bootstrapExecuting command: Etr407AppianTest.TransponderManagement.TransponderNewLeaseTestSuite.IntegrationTestSuite.WebServiceInitUnauthNewOopPlateNameMatchPacFulfill?test=textStarting Test System: slim:fitnesse.slim.SlimService.Build timed out (after 3 minutes). Marking the build as aborted.{code}The above job executed a fitnesse script, but the same issue was able to reproduce from running other program, like Test Studio script.In jenkins,err.log I couldn't find any useful/related log. Environment: Windows 2012R2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
  

[JIRA] (JENKINS-53720) JDK11 Build Flow: FindBugs fails with RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE in some classes

2019-01-04 Thread gmo...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Gavin Mogan commented on  JENKINS-53720  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JDK11 Build Flow: FindBugs fails with RCN_REDUNDANT_NULLCHECK_WOULD_HAVE_BEEN_A_NPE in some classes   
 

  
 
 
 
 

 
 ps, upgraded blueocean (in branch) to spotbugs, it has the same issue. JDK11 produces different bytecode   https://github.com/spotbugs/spotbugs/issues/756  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54786) Launch command should include an env var for the name of the node

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated  JENKINS-54786  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54786  
 
 
  Launch command should include an env var for the name of the node   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54786) Launch command should include an env var for the name of the node

2019-01-04 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54786  
 
 
  Launch command should include an env var for the name of the node   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Issue Type: 
 Bug Improvement  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55411) Whitelist DateTimeFormatter.ofPattern(String)

2019-01-04 Thread scho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksei Zhogov commented on  JENKINS-55411  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Whitelist DateTimeFormatter.ofPattern(String)   
 

  
 
 
 
 

 
 PR to fix this: https://github.com/jenkinsci/script-security-plugin/pull/235  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55411) Whitelist DateTimeFormatter.ofPattern(String)

2019-01-04 Thread scho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksei Zhogov assigned an issue to Andrew Bayer  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55411  
 
 
  Whitelist DateTimeFormatter.ofPattern(String)   
 

  
 
 
 
 

 
Change By: 
 Aleksei Zhogov  
 
 
Assignee: 
 Aleksei Zhogov Andrew Bayer  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55411) Whitelist DateTimeFormatter.ofPattern(String)

2019-01-04 Thread scho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksei Zhogov assigned an issue to Aleksei Zhogov  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55411  
 
 
  Whitelist DateTimeFormatter.ofPattern(String)   
 

  
 
 
 
 

 
Change By: 
 Aleksei Zhogov  
 
 
Assignee: 
 Andrew Bayer Aleksei Zhogov  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55411) Whitelist DateTimeFormatter.ofPattern(String)

2019-01-04 Thread scho...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Aleksei Zhogov created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55411  
 
 
  Whitelist DateTimeFormatter.ofPattern(String)   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 script-security-plugin  
 
 
Created: 
 2019-01-04 18:55  
 
 
Environment: 
 Jenkins 2.140  Script Security Plugin 1.49  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Aleksei Zhogov  
 

  
 
 
 
 

 
 Whitelist DateTimeFormatter.ofPattern(String) since currently we have only set of constants whitelisted (BASIC_ISO_DATE, ISO_DATE_TIME...) that doesn't cover all real-life use cases  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 
 

[JIRA] (JENKINS-54897) Unexpected error in launching a agent after restart

2019-01-04 Thread rash...@synopsys.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Bob Ashforth commented on  JENKINS-54897  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unexpected error in launching a agent after restart   
 

  
 
 
 
 

 
 Can you recommend any workarounds? This is crippling a major lift-and-shift project for us.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-24483) RepositoryBrowser.getChangeSetLink exceptions from Jelly pollute log

2019-01-04 Thread liddi...@yahoo.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tyler Liddicoat commented on  JENKINS-24483  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: RepositoryBrowser.getChangeSetLink exceptions from Jelly pollute log   
 

  
 
 
 
 

 
 Thanks Mark, we had the same config issue on some of our jobs, which caused thousands of these exceptions to be thrown.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55410) Add label attribute for persistable steps to improve usability

2019-01-04 Thread soenkekue...@outlook.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sönke Küper started work on  JENKINS-55410  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Sönke Küper  
 
 
Status: 
 Open In Progress  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55410) Add label attribute for persistable steps to improve usability

2019-01-04 Thread soenkekue...@outlook.de (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Sönke Küper created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55410  
 
 
  Add label attribute for persistable steps to improve usability   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Sönke Küper  
 
 
Components: 
 workflow-durable-task-step-plugin  
 
 
Created: 
 2019-01-04 18:13  
 
 
Labels: 
 label description sh bat documentation usability  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Sönke Küper  
 

  
 
 
 
 

 
 I've added an new Attribute "label" to the durable steps, so that this is displayed within the pipeline steps view and blue ocean views instead of the technical Name "Windows Batch Script" or "Linux Shell script". We have got a lot of this and it is very hard to find the right one. With this labels this step can now display the real domain specific information for example "build manual" "copy driver files" etc. This makes the pipeline views very more comfortable to use.   See pull request https://github.com/jenkinsci/workflow-durable-task-step-plugin/pull/93  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 
 

[JIRA] (JENKINS-45141) Support multiple jira projects

2019-01-04 Thread brian.vandegri...@microsemi.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Brian Vandegriend commented on  JENKINS-45141  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Support multiple jira projects   
 

  
 
 
 
 

 
 Hi - I would be interested in this feature as well.  We use one Jira project for the actual test development and a second for software bugs/feature issues.  Thus, a failure can be attributed to either a test issue or a software bug and thus we need the ability to link a test failure to one of several Jira projects. I'm not familiar with the source code but it can be easily supported by supporting multiple items in the Project Key field and using the first one in that list for creating new issues against.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-49707) Auto retry for elastic agents after channel closure

2019-01-04 Thread jrog...@socialserve.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonathan Rogers commented on  JENKINS-49707  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Auto retry for elastic agents after channel closure   
 

  
 
 
 
 

 
 Like Amir Barkal, I would like a pipeline step to fail quickly if the Jenkins master loses its connection to the agent for the node running the step. The log mentions that hudson.remoting.ChannelClosedException was thrown. If I can catch that exception in my pipeline script, I can retry the appropriate steps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55409) VCS data not getting uploaded with Artifacts.

2019-01-04 Thread jenk...@vampyred.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Delaney updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55409  
 
 
  VCS data not getting uploaded with Artifacts.   
 

  
 
 
 
 

 
Change By: 
 Mike Delaney  
 

  
 
 
 
 

 
 Using a Jenkins scripted pipeline (in a multi branch project ; with GIT as the SCM ), and a generic  deployer  uploader , when artifacts get uploaded to Artifactory, the VCS data is not uploaded with the artifacts  but the other build environment variables are .Here is the example pipeline we use for testing this bug:{code}node('remote-node') {stage ('checkout') {checkout scm}stage ('build') {sh 'make -j12'}stage('artifactory') {def upload_spec = """{  "files":  [{  "pattern": "*.tar.gz",  "target": "embedded-build/project/branch/version/"}  ]}"""def server = Artifactory.server 'artifactory.company.com'def build_info = Artifactory.newBuildInfo()build_info.env.capture = truebuild_info.retention maxDays: 90, deleteBuildArtifacts: trueserver.upload spec: upload_spec, buildInfo: build_infoserver.publishBuildInfo build_info}}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from 

[JIRA] (JENKINS-55409) VCS data not getting uploaded with Artifacts.

2019-01-04 Thread jenk...@vampyred.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Delaney created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55409  
 
 
  VCS data not getting uploaded with Artifacts.   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Eyal Ben Moshe  
 
 
Components: 
 artifactory-plugin  
 
 
Created: 
 2019-01-04 17:59  
 
 
Environment: 
 Jenkins: 2.150.1  Jenkins Artifactory plugin: 2.16.2  Artifactory: 6.6.1   
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mike Delaney  
 

  
 
 
 
 

 
 Using a Jenkins scripted pipeline (in a multi branch project), and a generic deployer, when artifacts get uploaded to Artifactory, the VCS data is not uploaded with the artifacts. Here is the example pipeline we use for testing this bug: 

 

node('remote-node') {
stage ('checkout') {
checkout scm
}

stage ('build') {
sh 'make -j12'
}

stage('artifactory') {
def upload_spec = """{
  "files":
  [
{
  "pattern": "**/*",
  "target": "embedded-build/project/branch/version/"
}
  ]
}
"""
def server = Artifactory.server 'artifactory.company.com'
def build_info = Artifactory.newBuildInfo()

build_info.env.capture = true
build_info.retention maxDays: 90,
 deleteBuildArtifacts: true

server.upload spec: upload_spec, buildInfo: build_info
server.publishBuildInfo build_info
}
}
 

  
 

  
   

[JIRA] (JENKINS-55409) VCS data not getting uploaded with Artifacts.

2019-01-04 Thread jenk...@vampyred.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Delaney updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55409  
 
 
  VCS data not getting uploaded with Artifacts.   
 

  
 
 
 
 

 
Change By: 
 Mike Delaney  
 

  
 
 
 
 

 
 Using a Jenkins scripted pipeline (in a multi branch project), and a generic deployer, when artifacts get uploaded to Artifactory, the VCS data is not uploaded with the artifacts.Here is the example pipeline we use for testing this bug:{code}node('remote-node') {stage ('checkout') {checkout scm}stage ('build') {sh 'make -j12'}stage('artifactory') {def upload_spec = """{  "files":  [{  "pattern": "* */* .tar.gz ",  "target": "embedded-build/project/branch/version/"}  ]}"""def server = Artifactory.server 'artifactory.company.com'def build_info = Artifactory.newBuildInfo()build_info.env.capture = truebuild_info.retention maxDays: 90, deleteBuildArtifacts: trueserver.upload spec: upload_spec, buildInfo: build_infoserver.publishBuildInfo build_info}}{code}  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 

[JIRA] (JENKINS-33274) "Base build" link for first build of branch project

2019-01-04 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Reopening at James Nord's request, but I don't expect that we'll be working on this at any time in the foreseeable future.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-33274  
 
 
  "Base build" link for first build of branch project   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Resolution: 
 Won't Fix  
 
 
Status: 
 Resolved Reopened  
 
 
Assignee: 
 CloudBees Inc.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-33274) "Base build" link for first build of branch project

2019-01-04 Thread jn...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 James Nord commented on  JENKINS-33274  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Base build" link for first build of branch project   
 

  
 
 
 
 

 
 can you define worthwhile? I would say not introducing new spotbugs issues into a build is very worthwhile.   given a PR build has no comparision spotbugs will treat all issues as new, which means you have to fix every single issue, or just ignore them and hope you don;t introduce new ones (when you are starting on a non greenfield project that has say 1000 spotbugs issues and you want to ratchet them down over time, or at least not allow new issues to be introduced).   There are other use cases as well but that above is pretty worthwhile.  (you can s/spotbugs/checkstyle/) and there are likely many other use cases too that require this support.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-46619) [JDK9] Illegal reflective access from FilePath

2019-01-04 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46619  
 
 
  [JDK9] Illegal reflective access from FilePath   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 
 
Labels: 
 illegalReflectiveAccess java10_hackathon java11  scrub  triaged  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote

2019-01-04 Thread rtaya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rishabh Tayal commented on  JENKINS-53016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote   
 

  
 
 
 
 

 
 Devin Nusbaum Awesome. I will check it out.   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote

2019-01-04 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-53016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote   
 

  
 
 
 
 

 
 Rishabh Tayal Yes, that is a distinct issue, see https://github.com/jenkinsci/ansicolor-plugin/issues/139 and add any further questions there (Note that I just so happen to be releasing a fix for that distinct issue today).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote

2019-01-04 Thread rtaya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rishabh Tayal commented on  JENKINS-53016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote   
 

  
 
 
 
 

 
 Devin Nusbaum Here is the stack trace. 

 

Stack trace

java.lang.IndexOutOfBoundsException
	at hudson.MarkupText.rangeCheck(MarkupText.java:276)
	at hudson.MarkupText.addMarkup(MarkupText.java:270)
	at hudson.plugins.ansicolor.ColorConsoleAnnotator$1EmitterImpl.emitHtml(ColorConsoleAnnotator.java:74)
	at hudson.plugins.ansicolor.AnsiAttributeElement.emitClose(AnsiAttributeElement.java:42)
	at hudson.plugins.ansicolor.AnsiHtmlOutputStream.closeOpenTags(AnsiHtmlOutputStream.java:107)
	at hudson.plugins.ansicolor.AnsiHtmlOutputStream.processAttributeRest(AnsiHtmlOutputStream.java:542)
	at hudson.plugins.ansicolor.AnsiOutputStream.processEscapeCommand(AnsiOutputStream.java:358)
	at hudson.plugins.ansicolor.AnsiOutputStream.write(AnsiOutputStream.java:138)
	at hudson.plugins.ansicolor.AnsiHtmlOutputStream.write(AnsiHtmlOutputStream.java:220)
	at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:55)
	at hudson.plugins.ansicolor.ColorConsoleAnnotator.annotate(ColorConsoleAnnotator.java:91)
	at hudson.console.ConsoleAnnotator$ConsoleAnnotatorAggregator.annotate(ConsoleAnnotator.java:108)
	at hudson.console.ConsoleAnnotationOutputStream.eol(ConsoleAnnotationOutputStream.java:148)
	at hudson.console.LineTransformationOutputStream.eol(LineTransformationOutputStream.java:60)
	at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:56)
	at hudson.console.LineTransformationOutputStream.write(LineTransformationOutputStream.java:74)
	at org.apache.commons.io.output.ProxyOutputStream.write(ProxyOutputStream.java:90)
	at org.kohsuke.stapler.framework.io.LargeText$HeadMark.moveTo(LargeText.java:314)
	at org.kohsuke.stapler.framework.io.LargeText.writeLogTo(LargeText.java:229)
	at hudson.console.AnnotatedLargeText.writeHtmlTo(AnnotatedLargeText.java:169)
	at hudson.console.AnnotatedLargeText.writeLogTo(AnnotatedLargeText.java:144)
	at org.kohsuke.stapler.framework.io.LargeText.doProgressText(LargeText.java:264)
	at hudson.console.AnnotatedLargeText.doProgressiveHtml(AnnotatedLargeText.java:92)
	at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)
	at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
	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:537)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)
Caused: javax.servlet.ServletException
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:789)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)
	at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:221)
	at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)
	at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458)
	at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739)
	at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870)
	at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282)
	at 

[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote

2019-01-04 Thread dnusb...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Devin Nusbaum commented on  JENKINS-53016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote   
 

  
 
 
 
 

 
 Rishabh Tayal Please post the full stack trace you are seeing. It is very likely that the root cause of your error is different than the one addressed by this ticket.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-53016) IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote

2019-01-04 Thread rtaya...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rishabh Tayal commented on  JENKINS-53016  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: IndexOutOfBoundsException in MarkupText caused by (Model)HyperlinkNote   
 

  
 
 
 
 

 
 Devin Nusbaum I am still seeing the issue in the latest Jenkins release. I am currently on v2.156    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54305) Oracle JDK 10 not available anymore - Oracle JDK 11 is not free

2019-01-04 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon assigned an issue to Ramon Leon  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54305  
 
 
  Oracle JDK 10 not available anymore - Oracle JDK 11 is not free   
 

  
 
 
 
 

 
Change By: 
 Ramon Leon  
 
 
Assignee: 
 Ramon Leon  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-33274) "Base build" link for first build of branch project

2019-01-04 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 This is not actually that worthwhile a feature to add, in practice, and is hairier to implement than I thought two years ago when I first looked into it, so I'm closing this as won't fix.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-33274  
 
 
  "Base build" link for first build of branch project   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-54355) ClassNotFound: java.sql.Date in JDK 11 in Pipeline Utility Steps

2019-01-04 Thread adrien.lecharpent...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Adrien Lecharpentier commented on  JENKINS-54355  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ClassNotFound: java.sql.Date in JDK 11 in Pipeline Utility Steps   
 

  
 
 
 
 

 
 To check something, I just ran a simple pipeline job to read a yaml structure on jenkins/jenkins:jdk11 and I don't have the same problem at all.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-52098) Total warnings threshold from reference build

2019-01-04 Thread a...@90a.nl (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arno Moonen edited a comment on  JENKINS-52098  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Total warnings threshold from reference build   
 

  
 
 
 
 

 
 This issue is preventing is from migrating to the Warnings NG plugin.Warnings move around as code is added and the parsers will pick it up as new warnings. Might For us it might  be even better if it could check that the number of warnings per file are not increased (just thought of this while writing this comment).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-52098) Total warnings threshold from reference build

2019-01-04 Thread a...@90a.nl (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arno Moonen edited a comment on  JENKINS-52098  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Total warnings threshold from reference build   
 

  
 
 
 
 

 
 This issue is preventing is from migrating to the Warnings NG plugin.Warnings move around as code is added and the  code  parsers  will pick it up as new warnings.Might be even better if it could check that the number of warnings per file are not increased (just thought of this while writing this comment).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55408) Configure Quality Gate Thresholds per Tool in post-build action

2019-01-04 Thread a...@90a.nl (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arno Moonen created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55408  
 
 
  Configure Quality Gate Thresholds per Tool in post-build action   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Ulli Hafner  
 
 
Components: 
 warnings-ng-plugin  
 
 
Created: 
 2019-01-04 15:36  
 
 
Environment: 
 Jenkins ver. 2.150.1;  Warnings Next Generation Plugin 1.0.1  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Arno Moonen  
 

  
 
 
 
 

 
 When using the Record compiler warnings and static analysis results post-build action, we want to be able to set the Quality Gate Thresholds per configured tool. In the past we had separate post-build actions for CPD and PC-Lint. The post build action from the DRY plugin for CPD was configured in such a way that it never failed the build (only generated the report). The post build action from the Warnings plugin for PC-Lint was configured so that the total number of warnings may not increase (which is also missing in the NG plugin at the moment, see JENKINS-52098). Currently migrating from both DRY and Warnings to Warnings Next Generation does not seem possible for us, because we can only set the Quality Gate Thresholds for all the configured tools in the Post-build action.  
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-52098) Total warnings threshold from reference build

2019-01-04 Thread a...@90a.nl (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Arno Moonen commented on  JENKINS-52098  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Total warnings threshold from reference build   
 

  
 
 
 
 

 
 This issue is preventing is from migrating to the Warnings NG plugin. Warnings move around as code is added and the code will pick it up as new warnings. Might be even better if it could check that the number of warnings per file are not increased (just thought of this while writing this comment).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55407) no output after this step in console "[Pipeline] newBuildInfo [Pipeline] artifactoryMavenBuild" while building and uploading artifacts

2019-01-04 Thread yuvrajyuv...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Yuvaraj D created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55407  
 
 
  no output after this step in console "[Pipeline] newBuildInfo [Pipeline] artifactoryMavenBuild" while building and uploading artifacts   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Eyal Ben Moshe  
 
 
Components: 
 artifactory-plugin  
 
 
Created: 
 2019-01-04 15:22  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Yuvaraj D  
 

  
 
 
 
 

 
 No output after this step as it keeps on loading... [Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Upload to Artifactory)[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] tool[Pipeline] envVarsForTool[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] newBuildInfo[Pipeline] artifactoryMavenBuild   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

 

[JIRA] (JENKINS-54426) Jenkinsfile Runner fails on Java 11: NoClassDefFoundError: java.sql.Date

2019-01-04 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus commented on  JENKINS-54426  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Jenkinsfile Runner fails on Java 11: NoClassDefFoundError: java.sql.Date   
 

  
 
 
 
 

 
 I think we "simply" need to add the java.sql module ASAP. Probably we'll do that next week or so. Cc Adrien Lecharpentier  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


[JIRA] (JENKINS-55404) Wrong merge order of pull request build

2019-01-04 Thread tkucorpor...@googlemail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Thomas Kuchel assigned an issue to Antonio Muñiz  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Sorry for assignment without asking. Could you please have a short look at this issue? Thank you.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-55404  
 
 
  Wrong merge order of pull request build   
 

  
 
 
 
 

 
Change By: 
 Thomas Kuchel  
 
 
Assignee: 
 Antonio Muñiz  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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


  1   2   >