[JIRA] (JENKINS-56018) ATH Docker image should not be using Module patches starting from 2.163

2019-02-10 Thread manuelramonleonjime...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Ramon Leon updated  JENKINS-56018  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56018  
 
 
  ATH Docker image should not be using Module patches starting from 2.163   
 

  
 
 
 
 

 
Change By: 
 Ramon Leon  
 
 
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-56048) Configuring Sonar Quality gate through programmatic (init.d scripts)

2019-02-10 Thread santoshrahu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 goru santosh assigned an issue to SCM/JIRA link daemon  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56048  
 
 
  Configuring Sonar Quality gate through programmatic (init.d scripts)
 

  
 
 
 
 

 
Change By: 
 goru santosh  
 
 
Assignee: 
 Erina Gomi SCM/JIRA link daemon  
 

  
 
 
 
 

 
 
 

 
 
 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-56048) Configuring Sonar Quality gate through programmatic (init.d scripts)

2019-02-10 Thread santoshrahu...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 goru santosh assigned an issue to Erina Gomi  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56048  
 
 
  Configuring Sonar Quality gate through programmatic (init.d scripts)
 

  
 
 
 
 

 
Change By: 
 goru santosh  
 
 
Assignee: 
 Rafael Ramos Erina Gomi  
 

  
 
 
 
 

 
 
 

 
 
 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-56045) Not able to upgrade the jenkins version from 1.58 to 2.121 | Error - java.lang.NoSuchMethodError: com.google.common.util.concurrent

2019-02-10 Thread abdulhar...@live.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abdul Haris commented on  JENKINS-56045  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not able to upgrade the jenkins version from 1.58 to 2.121 | Error - java.lang.NoSuchMethodError: com.google.common.util.concurrent   
 

  
 
 
 
 

 
 Please help me to fix this error! Appreciate your time..  
 

  
 
 
 
 

 
 
 

 
 
 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-56045) Not able to upgrade the jenkins version from 1.58 to 2.121 | Error - java.lang.NoSuchMethodError: com.google.common.util.concurrent

2019-02-10 Thread abdulhar...@live.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Abdul Haris updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56045  
 
 
  Not able to upgrade the jenkins version from 1.58 to 2.121 | Error - java.lang.NoSuchMethodError: com.google.common.util.concurrent   
 

  
 
 
 
 

 
Change By: 
 Abdul Haris  
 
 
Priority: 
 Minor Critical  
 

  
 
 
 
 

 
 
 

 
 
 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-56076) Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin

2019-02-10 Thread ddigt...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Denys Digtiar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56076  
 
 
  Git Client plugin's CLI implementation does not interoperate with Kubernetes plugin   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Mark Waite  
 
 
Attachments: 
 consoleText.txt  
 
 
Components: 
 git-client-plugin, git-plugin  
 
 
Created: 
 2019-02-11 06:24  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Denys Digtiar  
 

  
 
 
 
 

 
 When `checkout` or `git` steps run inside the Kubernetes plugin's `container` block the Git CLI is expected to be executed on the specified container but it is not. It is executed in the jnlp container disregarding the `container` step. Below is a test Pipeline. It relies on the custom docker image (duemir/jenkins-jnlp-agent:alpine-no-git) which is based on the `jenkins/jnlp-slave:alpine` Dockerfile but with `git` installation removed. The Console Output is attached.  Env: Jenkins 2.138.4 Git plugin 3.9.1  Git Client plugin 2.7.3  Kuberentes plugin 1.12.8  

 

pipeline {
  agent {
kubernetes {
  cloud 'kubernetes'
  label 'custom-jnlp-without-git'
  yaml """
kind: Pod
apiVersion: v1
spec:
  containers:
  - name: jnlp
image: duemir/jenkins-jnlp-agent:alpine-no-git
imagePullPolicy: Always
args: ['\$(JENKINS_SECRET)', '\$(JENKINS_NAME)']
  - name: worker
image: jenkins/slave:latest
imagePullPolicy: Always
tty: true
command:
- /bin/sh
args:
- -c
- cat
"""
}
  }
  stages {
stage('Run') {
  steps {
sh '''
echo This runs on jnlp container
git --version || true
'''
   container('worker') {
  sh '''
  echo This runs on jnlp-slave container
 

[JIRA] (JENKINS-56075) Script based authentication unable to load authentication script file

2019-02-10 Thread prad...@pexus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pradeep Nambiar commented on  JENKINS-56075  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Script based authentication unable to load authentication script file   
 

  
 
 
 
 

 
 The same  issue happens with the released version of ZAP 2.7.0 also.  
 

  
 
 
 
 

 
 
 

 
 
 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-55388) multibranch pipeline deleting history and building unexpectedly

2019-02-10 Thread h...@bodidata.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hai Nguyen commented on  JENKINS-55388  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: multibranch pipeline deleting history and building unexpectedly   
 

  
 
 
 
 

 
 I had the same bug too, I don't remember the multi branch plugin version at the first time I saw this bug, but that's when I'm using Blue Ocean 1.0.0, and now, I'm using Blue Ocean 1.7.0 and this one is still happening.  This morning, all my repositories and all branches in each repository are starting again from build #1, all at the same time, all history is also deleted. This is not the first time I have this problem. Usually this happens when I change my configuration (like only build branches that match my wildcard), but also so many times it starts building unexpectedly like now.   
 

  
 
 
 
 

 
 
 

 
 
 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-55388) multibranch pipeline deleting history and building unexpectedly

2019-02-10 Thread h...@bodidata.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hai Nguyen commented on  JENKINS-55388  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: multibranch pipeline deleting history and building unexpectedly   
 

  
 
 
 
 

 
 I had the same bug too, I don't remember the multi branch plugin version at the first time I saw this bug, but that's when I'm using Blue Ocean 1.0.0, and now, I'm using Blue Ocean 1.7.0 and this one is still happening.  This morning, all my repositories and all branches in each repository are starting again from build #1, all at the same time, all history is also deleted. This is not the first time I have this problem. Usually this happens when I change my configuration (like only build branches that match my wildcard), but also so many times it starts building unexpectedly like now.   
 

  
 
 
 
 

 
 
 

 
 
 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-55388) multibranch pipeline deleting history and building unexpectedly

2019-02-10 Thread h...@bodidata.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Hai Nguyen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55388  
 
 
  multibranch pipeline deleting history and building unexpectedly   
 

  
 
 
 
 

 
Change By: 
 Hai Nguyen  
 
 
Attachment: 
 ci.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-56075) Script based authentication unable to load authentication script file

2019-02-10 Thread prad...@pexus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Pradeep Nambiar created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56075  
 
 
  Script based authentication unable to load authentication script file   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Goran Sarenkapa  
 
 
Components: 
 zap-plugin  
 
 
Created: 
 2019-02-11 01:54  
 
 
Environment: 
 Jenkins Version: Jenkins ver. 2.121.1  Latest - zap-plugin  Windows 7 x64  ZAP - Weekly Build : ZAP_D-2019-01-28   
 
 
Priority: 
  Major  
 
 
Reporter: 
 Pradeep Nambiar  
 

  
 
 
 
 

 
 Trying to use the Script based authentication for zap-plugin to scan a site. I created the _javascript_ based authentication script and saved it using the GUI. Created a Jenkins job to use the official owasp zap plugin. In the configuration I was able to find the authentication script in the drop down list and was able to configure and save successfully. When running the job, I get error unable to load the script with the following stack trace:   [ZAP Jenkins Plugin] LOAD SCRIPT FOR AUTHENTICATION 5428 [ZAP-ProxyThread-6] ERROR org.zaproxy.zap.authentication.ScriptBasedAuthenticationMethodType - Unable to find script while loading Script Based Authentication Method for name: MyAuth.js 5430 [ZAP-ProxyThread-6] WARN org.zaproxy.zap.extension.api.API - Bad request to API endpoint [/xml/authentication/action/setAuthenticationMethod/] from [127.0.0.1]: No script with the provided name has been found (script_not_found) : MyAuth.js at org.zaproxy.zap.authentication.ScriptBasedAuthenticationMethodType$1.handleAction(ScriptBasedAuthenticationMethodType.java:751) at org.zaproxy.zap.extension.authentication.AuthenticationAPI.handleApiAction(AuthenticationAPI.java:179) at org.zaproxy.zap.extension.api.API.handleApiRequest(API.java:449) at org.parosproxy.paros.core.proxy.ProxyThread.processHttp(ProxyThread.java:456) at 

[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step

2019-02-10 Thread jmcdon...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Josh McDonald commented on  JENKINS-38339  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: UI for downstream jobs launched with 'build' step   
 

  
 
 
 
 

 
 Still trying to figure this one out, but it's definitely a bug, and only seems to affect declarative pipelines, which makes for a nice test case of the same pipeline in both declarative and original pipeline versions.  
 

  
 
 
 
 

 
 
 

 
 
 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-56074) [assignIssue] Set an issue to Unassigned

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati commented on  JENKINS-56074  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [assignIssue] Set an issue to Unassigned   
 

  
 
 
 
 

 
 Fixed and merged to master, not yet released, pending release.   
 

  
 
 
 
 

 
 
 

 
 
 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-8012) Missing jsch-0.1.31.jar when using sftp in ivysettings

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-8012  
 
 
  Missing jsch-0.1.31.jar when using sftp in ivysettings   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Released As: 
 1.14  
 

  
 
 
 
 

 
 
 

 
 
 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-56074) [assignIssue] Set an issue to Unassigned

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati updated  JENKINS-56074  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56074  
 
 
  [assignIssue] Set an issue to Unassigned   
 

  
 
 
 
 

 
Change By: 
 Naresh Rayapati  
 
 
Status: 
 In Review 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-34192) Integrate with the config file provider plugin

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34192  
 
 
  Integrate with the config file provider plugin   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Released As: 
 1.27  
 

  
 
 
 
 

 
 
 

 
 
 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-56074) [assignIssue] Set an issue to Unassigned

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati started work on  JENKINS-56074  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Naresh Rayapati  
 
 
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-41129) Ivy plugin throws NPE if no project settings defined

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41129  
 
 
  Ivy plugin throws NPE if no project settings defined   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Released As: 
 1.27.1  
 

  
 
 
 
 

 
 
 

 
 
 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-56074) [assignIssue] Set an issue to Unassigned

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati updated  JENKINS-56074  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56074  
 
 
  [assignIssue] Set an issue to Unassigned   
 

  
 
 
 
 

 
Change By: 
 Naresh Rayapati  
 
 
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-41129) Ivy plugin throws NPE if no project settings defined

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-41129  
 
 
  Ivy plugin throws NPE if no project settings defined   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Released As: 
 1.27.1  
 

  
 
 
 
 

 
 
 

 
 
 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-37046) Wrong Ivy XML file is being looked for

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-37046  
 
 
  Wrong Ivy XML file is being looked for   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Released As: 
 1.27  
 

  
 
 
 
 

 
 
 

 
 
 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-35139) Config Files - Custom is duplicated by Ivy

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-35139  
 
 
  Config Files - Custom is duplicated by Ivy   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Released As: 
 1.27  
 

  
 
 
 
 

 
 
 

 
 
 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-40959) Exception in IvyJob XMLConfigProvider: No Such Method Found

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-40959  
 
 
  Exception in IvyJob XMLConfigProvider: No Such Method Found   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Released As: 
 1.27  
 

  
 
 
 
 

 
 
 

 
 
 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-56074) [assignIssue] Set an issue to Unassigned

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati commented on  JENKINS-56074  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: [assignIssue] Set an issue to Unassigned   
 

  
 
 
 
 

 
 PR: https://github.com/jenkinsci/jira-steps-plugin/pull/85  
 

  
 
 
 
 

 
 
 

 
 
 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-56074) [assignIssue] Set an issue to Unassigned

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56074  
 
 
  [assignIssue] Set an issue to Unassigned   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Naresh Rayapati  
 
 
Components: 
 jira-steps-plugin  
 
 
Created: 
 2019-02-10 22:08  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Naresh Rayapati  
 

  
 
 
 
 

 
 Allow 'null' as assignee to set the issue to 'unassigned'.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  

[JIRA] (JENKINS-46314) Module descriptor recomputation is not properly synchronized

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-46314  
 
 
  Module descriptor recomputation is not properly synchronized   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.28  
 

  
 
 
 
 

 
 
 

 
 
 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-56072) Jenkins Job failed - pipeline-maven-plugin

2019-02-10 Thread clecl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Cyrille Le Clerc assigned an issue to Cyrille Le Clerc  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56072  
 
 
  Jenkins Job failed - pipeline-maven-plugin   
 

  
 
 
 
 

 
Change By: 
 Cyrille Le Clerc  
 
 
Assignee: 
 Alvaro Lobato Cyrille Le Clerc  
 

  
 
 
 
 

 
 
 

 
 
 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-47778) Ivy Project Jenkins Global Configuration does not separate next section

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe resolved as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-47778  
 
 
  Ivy Project Jenkins Global Configuration does not separate next section   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 
 
Status: 
 In Progress Resolved  
 
 
Resolution: 
 Fixed  
 
 
Released As: 
 1.28  
 

  
 
 
 
 

 
 
 

 
 
 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-56073) Configuration-as-Code compatibility

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56073  
 
 
  Configuration-as-Code compatibility   
 

  
 
 
 
 

 
Change By: 
 René Scheibe  
 

  
 
 
 
 

 
 Currently the plugin doesn't support [JCasC ]( | https://jenkins.io/projects/jcasc/ ) ] .When an Artifactory server is configured in the global config, the JCasC export fails as follows{code :java }unclassified: artifactoryBuilder: artifactoryServers: "FAILED TO EXPORT org.jfrog.hudson.ArtifactoryBuilder$DescriptorImpl#artifactoryServers:\ \ \nio.jenkins.plugins.casc.ConfiguratorException: Can't read attribute 'serverId'\ \ from org.jfrog.hudson.ArtifactoryServer@12d71b12\n\tat io.jenkins.plugins.casc.Attribute._getValue(Attribute.java:252)\n\ \tat io.jenkins.plugins.casc.Attribute.getValue(Attribute.java:174)\n\tat io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:236)\n\ \tat io.jenkins.plugins.casc.Attribute.describe(Attribute.java:192)\n\tat io.jenkins.plugins.casc.BaseConfigurator.compare(BaseConfigurator.java:387)\n\ \tat io.jenkins.plugins.casc.impl.configurators.DescriptorConfigurator.describe(DescriptorConfigurator.java:61)\n\ \tat io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:105)\n\ \tat io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.lambda$describe$6(GlobalConfigurationCategoryConfigurator.java:98)\n\ \tat java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)\n\ \tat java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)\n\ \tat java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)\n\ \tat java.util.Iterator.forEachRemaining(Iterator.java:116)\n\tat java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)\n\ \tat java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)\n\ \tat java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)\n\ \tat java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)\n\ \tat java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)\n\ \tat java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)\n\ \tat java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)\n\ \tat io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:98)\n\ \tat io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:32)\n\ \tat io.jenkins.plugins.casc.ConfigurationAsCode.export(ConfigurationAsCode.java:411)\n\ \tat io.jenkins.plugins.casc.ConfigurationAsCode.doExport(ConfigurationAsCode.java:401)\n\ ...{code}    
 

  
 
 
  

[JIRA] (JENKINS-56073) Configuration-as-Code compatibility

2019-02-10 Thread rene.sche...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 René Scheibe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56073  
 
 
  Configuration-as-Code compatibility   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Eyal Ben Moshe  
 
 
Components: 
 artifactory-plugin  
 
 
Created: 
 2019-02-10 21:16  
 
 
Labels: 
 configuration-as-code jcasc-compatibility  
 
 
Priority: 
  Major  
 
 
Reporter: 
 René Scheibe  
 

  
 
 
 
 

 
 Currently the plugin doesn't support [JCasC](https://jenkins.io/projects/jcasc/). When an Artifactory server is configured in the global config, the JCasC export fails as follows 

 

unclassified:
 artifactoryBuilder:
 artifactoryServers: "FAILED TO EXPORT org.jfrog.hudson.ArtifactoryBuilder$DescriptorImpl#artifactoryServers:\
 \ \nio.jenkins.plugins.casc.ConfiguratorException: Can't read attribute 'serverId'\
 \ from org.jfrog.hudson.ArtifactoryServer@12d71b12\n\tat io.jenkins.plugins.casc.Attribute._getValue(Attribute.java:252)\n\
 \tat io.jenkins.plugins.casc.Attribute.getValue(Attribute.java:174)\n\tat io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.describe(DataBoundConfigurator.java:236)\n\
 \tat io.jenkins.plugins.casc.Attribute.describe(Attribute.java:192)\n\tat io.jenkins.plugins.casc.BaseConfigurator.compare(BaseConfigurator.java:387)\n\
 \tat io.jenkins.plugins.casc.impl.configurators.DescriptorConfigurator.describe(DescriptorConfigurator.java:61)\n\
 \tat io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.describe(GlobalConfigurationCategoryConfigurator.java:105)\n\
 \tat io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator.lambda$describe$6(GlobalConfigurationCategoryConfigurator.java:98)\n\
 \tat 

[JIRA] (JENKINS-55769) Tag match filter shows more entries than direct command (git tag -l "$tagFilter")

2019-02-10 Thread klim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas edited a comment on  JENKINS-55769  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Tag match filter shows more entries than direct command (git tag -l "$tagFilter")   
 

  
 
 
 
 

 
 HI,I changed help description in the plugin on this field{quote}This parameter is used to get tag from git. If is blank, parameter is set to "*". Properly is executed command: git ls-remote -t  "*" or git ls-remote -t  "$tagFilter" [git-ls-remote|https://git-scm.com/docs/git-ls-remote.html] documentation.{quote} In git documentation{quote}…​      When unspecified, all references, after filtering done with --heads and --tags, are shown. When …​ are specified, only references matching the          given patterns are displayed.{quote}  
 

  
 
 
 
 

 
 
 

 
 
 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-55769) Tag match filter shows more entries than direct command (git tag -l "$tagFilter")

2019-02-10 Thread klim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas commented on  JENKINS-55769  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Tag match filter shows more entries than direct command (git tag -l "$tagFilter")   
 

  
 
 
 
 

 
 HI, I changed help description in the plugin on this field 

This parameter is used to get tag from git. If is blank, parameter is set to "*". Properly is executed command: git ls-remote -t  "*" or git ls-remote -t  "$tagFilter" git-ls-remote documentation.
  In git documentation 

…​     When unspecified, all references, after filtering done with --heads and --tags, are shown. When …​ are specified, only references matching the        given patterns are displayed.
  
 

  
 
 
 
 

 
 
 

 
 
 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-55769) Tag match filter shows more entries than direct command (git tag -l "$tagFilter")

2019-02-10 Thread klim...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Boguslaw Klimas updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55769  
 
 
  Tag match filter shows more entries than direct command (git tag -l "$tagFilter")   
 

  
 
 
 
 

 
Change By: 
 Boguslaw Klimas  
 
 
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-49394) Allow to specify visibility on addComment

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati commented on  JENKINS-49394  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow to specify visibility on addComment   
 

  
 
 
 
 

 
 PR: https://github.com/jenkinsci/jira-steps-plugin/pull/86  Thank you https://github.com/benjidea for the PR.   
 

  
 
 
 
 

 
 
 

 
 
 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-49394) Allow to specify visibility on addComment

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati updated  JENKINS-49394  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-49394  
 
 
  Allow to specify visibility on addComment   
 

  
 
 
 
 

 
Change By: 
 Naresh Rayapati  
 
 
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-49394) Allow to specify visibility on addComment

2019-02-10 Thread naresh.rayap...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati started work on  JENKINS-49394  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Naresh Rayapati  
 
 
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-56046) FATAL: Remote call on Slave failed

2019-02-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-56046  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FATAL: Remote call on Slave failed
 

  
 
 
 
 

 
 Most likely you are running a master or one of its agents with Java 11. Java 11 is not supported in your Jenkins version, please update to the latest weekly. https://jenkins.io/blog/2018/12/14/java11-preview-availability/    
 

  
 
 
 
 

 
 
 

 
 
 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-56046) FATAL: Remote call on Slave failed

2019-02-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56046  
 
 
  FATAL: Remote call on Slave failed
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Labels: 
 java11  
 

  
 
 
 
 

 
 
 

 
 
 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-56046) FATAL: Remote call on Slave failed

2019-02-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56046  
 
 
  FATAL: Remote call on Slave failed
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 core  
 
 
Component/s: 
 _unsorted  
 

  
 
 
 
 

 
 
 

 
 
 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-56057) UpdateSiteWarningsConfiguration should be confirgurable via JCasC

2019-02-10 Thread db...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Beck commented on  JENKINS-56057  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: UpdateSiteWarningsConfiguration should be confirgurable via JCasC   
 

  
 
 
 
 

 
 Realistically it's probably time to disable the SECURITY-248 warning for newer versions anyway. IIRC it was intended as a temporary measure to ensure users who had previously updated saw it due to the large time delay, but it's been a year now.  
 

  
 
 
 
 

 
 
 

 
 
 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-56039) Eternal loading while creating new Multibranch Pipeline

2019-02-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56039  
 
 
  Eternal loading while creating new Multibranch Pipeline   
 

  
 
 
 
 

 
Change By: 
 Oleg Nenashev  
 
 
Component/s: 
 pipeline  
 
 
Component/s: 
 workflow-multibranch-plugin  
 
 
Component/s: 
 _unsorted  
 

  
 
 
 
 

 
 
 

 
 
 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API

2019-02-10 Thread o.v.nenas...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-55829  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API   
 

  
 
 
 
 

 
 You just need to import the classes   import org.kohsuke.accmod.Restricted; import org.kohsuke.accmod.restrictions.NoExternalUse;    
 

  
 
 
 
 

 
 
 

 
 
 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-56072) Jenkins Job failed - pipeline-maven-plugin

2019-02-10 Thread sharon.mordec...@sap.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 sharon mordechai created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56072  
 
 
  Jenkins Job failed - pipeline-maven-plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Alvaro Lobato  
 
 
Components: 
 pipeline-maven-plugin  
 
 
Created: 
 2019-02-10 15:55  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 sharon mordechai  
 

  
 
 
 
 

 
 When I'm trying to run groovy script I'm getting:   ERROR: [withMaven] WARNING Exception executing Maven reporter 'Pipeline Graph Publisher' / org.jenkinsci.plugins.pipeline.maven.publishers.PipelineGraphPublisher. Please report a bug associated for the component 'pipeline-maven-plugin' at https://issues.jenkins-ci.org org.jenkinsci.plugins.pipeline.maven.util.RuntimeSqlException: org.h2.jdbc.JdbcSQLException: NULL not allowed for column "JENKINS_MASTER_ID"; SQL statement: INSERT INTO JENKINS_JOB(FULL_NAME) VALUES  [23502-196]  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[JIRA] (JENKINS-56071) Workflow job support

2019-02-10 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56071  
 
 
  Workflow job support   
 

  
 
 
 
 

 
Change By: 
 Jakub Bochenski  
 
 
Summary: 
 Stash Pull Request Builder Plugin crash Workflow job support  
 
 
Issue Type: 
 Bug New Feature  
 
 
Priority: 
 Blocker Major  
 
 
Assignee: 
 Jakub Bochenski  
 

  
 
 
 
 

 
 
 

 
 
 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-56071) Workflow job support

2019-02-10 Thread bochenski.kuba+jenk...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56071  
 
 
  Workflow job support   
 

  
 
 
 
 

 
Change By: 
 Jakub Bochenski  
 

  
 
 
 
 

 
 The plugin doesn't work with pipeline jobs.  PRs are welcome   C.f. https://github.com/jenkinsci/stash-pullrequest-builder-plugin/pull/21 ---I am trying to use the plugin (version 1.7.0), I receive the error- WARNING: stashpullrequestbuilder.stashpullrequestbuilder.StashBuildTrigger.run() failed for org.jenkinsci.plugins.workflow.job.WorkflowJobJava.lang.NullPointerExceptionat stashpullrequestbuilder.stashpullrequestbuilder.StashBuildTrigger.run(StashBuildTrgger.java:295) Any idea what is wrong? I have configured all the Mandatory parameters- Cron, Host, Credentials, Project and Repository Name. and in the advanced- I specified only one branch in the "Build PR targetting only these branches"   
 

  
 
 
 
 

 
 
 

 
 
 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API

2019-02-10 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah edited a comment on  JENKINS-55829  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API   
 

  
 
 
 
 

 
 Can If possible can  we just remove @Restricted(NoExternalUse.class) and try?  I know it's not the correct way but if possible.  
 

  
 
 
 
 

 
 
 

 
 
 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-55829) Expose AbstractCIBase#disabledAdministrativeMonitors as internal API

2019-02-10 Thread nisshah1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nisarg Shah commented on  JENKINS-55829  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Expose AbstractCIBase#disabledAdministrativeMonitors as internal API   
 

  
 
 
 
 

 
 Can we just remove @Restricted(NoExternalUse.class) and try?  
 

  
 
 
 
 

 
 
 

 
 
 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-56068) Code Coverage not being pushed to ALM Octane

2019-02-10 Thread eeman...@microfocus.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 eli Emanuel assigned an issue to eli Emanuel  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56068  
 
 
  Code Coverage not being pushed to ALM Octane   
 

  
 
 
 
 

 
Change By: 
 eli Emanuel  
 
 
Assignee: 
 Radi Berkovich eli Emanuel  
 

  
 
 
 
 

 
 
 

 
 
 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-50462) Artifacts tab presents everything as a flat list, making navigation time consuming

2019-02-10 Thread liyati...@java.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 liyatikal commented on  JENKINS-50462  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Artifacts tab presents everything as a flat list, making navigation time consuming   
 

  
 
 
 
 

 
 Very annoying, have to go back to the "regular" view in order to view artifacts  
 

  
 
 
 
 

 
 
 

 
 
 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-56071) Stash Pull Request Builder Plugin crash

2019-02-10 Thread eyalg1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eyal Goren created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56071  
 
 
  Stash Pull Request Builder Plugin crash   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jakub Bochenski  
 
 
Components: 
 stash-pullrequest-builder-plugin  
 
 
Created: 
 2019-02-10 11:25  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 Eyal Goren  
 

  
 
 
 
 

 
 I am trying to use the plugin (version 1.7.0), I receive the error-   WARNING: stashpullrequestbuilder.stashpullrequestbuilder.StashBuildTrigger.run() failed for org.jenkinsci.plugins.workflow.job.WorkflowJob Java.lang.NullPointerException at stashpullrequestbuilder.stashpullrequestbuilder.StashBuildTrigger.run(StashBuildTrgger.java:295)   Any idea what is wrong?   I have configured all the Mandatory parameters- Cron, Host, Credentials, Project and Repository Name. and in the advanced- I specified only one branch in the "Build PR targetting only these branches"    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 

[JIRA] (JENKINS-56070) bitbucket source branch plugin does not support the Copy Artifacts plugin

2019-02-10 Thread eyalg1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Eyal Goren created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-56070  
 
 
  bitbucket source branch plugin does not support the Copy Artifacts plugin   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 bitbucket-branch-source-plugin  
 
 
Created: 
 2019-02-10 11:17  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Eyal Goren  
 

  
 
 
 
 

 
 Currently for jobs that are created from bitbucket source branch plugin we can not assign permissions for other projects to copy their artifacts  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira 

[JIRA] (JENKINS-47591) Allow each Kubernetes slave pod to use unique Persistent Volume / Storage

2019-02-10 Thread jenkins...@carlossanchez.eu (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Carlos Sanchez commented on  JENKINS-47591  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Allow each Kubernetes slave pod to use unique Persistent Volume / Storage   
 

  
 
 
 
 

 
 That's a different issue, and you can only use pwc templates with statefulsets  
 

  
 
 
 
 

 
 
 

 
 
 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-55957) Remove JAXB dependency from job-import plugin

2019-02-10 Thread bat...@batmat.net (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Baptiste Mathus updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55957  
 
 
  Remove JAXB dependency from job-import plugin   
 

  
 
 
 
 

 
Change By: 
 Baptiste Mathus  
 

  
 
 
 
 

 
 Starting with Java 9+, JAXB has been removed from the JDK. So it's a good thing to try and break/remove the dependency against from plugins who do not really use JAXB for its core feature (object de/serialization). (only used in tests for this plugin, so nothing critical) h3. Acceptance criteria:* https://github.com/jenkinsci/job-import-plugin/search?q=javax.xml.bind_q=javax.xml.bind should yield nothing :)  
 

  
 
 
 
 

 
 
 

 
 
 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.