[JIRA] (JENKINS-59000) KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3

[asidhu11...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ahuhu uhuhuh commented on  JENKINS-59000  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: KubernetesClientException onFailure(WatchConnectionManager.java:198) on k8s v1.15.3   
 

  
 
 
 
 

 
 carlos is the problem fixed? can we download the latest plugin that has the problems 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201351.1566264399000.3544.1567227120462%40Atlassian.JIRA.

[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.

[fen.z...@yitu-inc.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 fen zhou commented on  JENKINS-58725  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.   
 

  
 
 
 
 

 
 4.0.0 AWX. 0.9.1 Ansible Tower Plugin. When I invoke Jenkins Job which has already called a Tower job, the Jenkins job gets stopped with Tower job still running. But actually, if the Tower job is stucked in one step like running a long-term progress, it will still remain running, which makes it impossible for me to call another Tower job in the same Tower project. I think one problem is I can't parallel the Tower jobs which is a normal feature of Tower (no way to change this). On the other hand, Ansible Tower Plugin doesn't notify Tower when it stops. These two features make me feel uncomfortable, and the page shows all the latter jobs wait to be scheduled. Then it will be one-century waiting without any feedback. Now, I can only stop the world with manually invoking on the Tower. But I hope there is any way to stop the Tower job without handly stopping.    
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201018.1564479331000.3541.1567221180175%40Atlassian.JIRA.

[JIRA] (JENKINS-59162) Support for statistical coverage of Java incremental code

[jiangsug...@outlook.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 ge qi created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59162  
 
 
  Support for statistical coverage of Java incremental code   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Ognjen Bubalo  
 
 
Components: 
 jacoco-plugin  
 
 
Created: 
 2019-08-31 02:07  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 ge qi  
 

  
 
 
 
 

 
 Is there any consideration for supporting statistics of incremental code coverage in java? I recently modified jacoco-plugin to achieve this goal. I modified jacoco-core and rebuilt. jar, and made no side-effect modifications on jacoco-plugin to achieve this goal. So I think this approach is feasible, and only statistical incremental code is very useful for developers or testers, which allows them to focus on the code blocks that need the most attention. In China, fast-paced code changes make us more dependent on this feature. If the developers of jacoco-plugin are willing to support this feature, I would be very grateful and would like to share our team's current practices in this area.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
   

[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash

[qinling....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Leon Qin commented on  JENKINS-54121  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Renaming jobs casue Jenkins crash   
 

  
 
 
 
 

 
 My instance also has this problem. I am not sure it is exactly the same with the issue here. But I believe it is caused by renaming. There were 2 renaming operations caused Jenkins not responding in 2 hours. Jenkins 2.176.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194748.1539771324000.3535.1567212240167%40Atlassian.JIRA.

[JIRA] (JENKINS-54121) Renaming jobs casue Jenkins crash

[qinling....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Leon Qin updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-54121  
 
 
  Renaming jobs casue Jenkins crash   
 

  
 
 
 
 

 
Change By: 
 Leon Qin  
 
 
Attachment: 
 image-2019-08-31-08-40-54-683.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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194748.1539771324000.3531.1567212060226%40Atlassian.JIRA.

[JIRA] (JENKINS-59160) Cannot Override workingDir for jnlp container

[mike_...@intuit.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Nau updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59160  
 
 
  Cannot Override workingDir for jnlp container   
 

  
 
 
 
 

 
Change By: 
 Mike Nau  
 

  
 
 
 
 

 
 With version 1.18.3 of the Jenkins Kubernetes Plugin, I am not able to override the default workingDir for the jnlp container. Here's the pod template I am using:   {code:java}agent {kubernetes {// Using a dynamic pod n ame because static labels are known to cause pod creation errors.label "mypod-${UUID.randomUUID().toString()}"defaultContainer "maven"yaml """apiVersion: v1kind: Podspec:  containers:  - name: jnlpimage: jenkins/jnlp-slave:alpineargs: ['\$(JENKINS_SECRET)', '\$(JENKINS_NAME)']workingDir: /home/jenkins/agent2  - name: mavenimage: maven:3.5.3-jdk-8command:- cattty: trueworkingDir: /home/jenkins/agent2"""}}{code}Job errors as (I have added -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true)      {code:java}sh: 1: cd: can't cd to /home/jenkins/agent/workspace/Pipeline_With_WorkingDirsh: 1: cannot create /home/jenkins/agent/workspace/Pipeline_With_WorkingDir@tmp/durable-cf37f355/jenkins-log.txt: Directory nonexistentsh: 1: cannot create /home/jenkins/agent/workspace/Pipeline_With_WorkingDir@tmp/durable-cf37f355/jenkins-result.txt.tmp: Directory nonexistentmv: cannot stat '/home/jenkins/agent/workspace/Pipeline_With_WorkingDir@tmp/durable-cf37f355/jenkins-result.txt.tmp': No such file or directoryprocess apparently never started in /home/jenkins/agent/workspace/Pipeline_With_WorkingDir@tmp/durable-cf37f355{code}It appears that the workingDir on our declared jnlp container is not being respected. If I set workingDir to /home/jenkins/agent everything works as expected.    We have a large number of existing jobs that depend on the workingDir being set to /home/jenkins. The change to default it to /home/jenkins/agent in v1.18.0 ([https://github.com/jenkinsci/kubernetes-plugin/releases/tag/kubernetes-1.18.0]) caused a lot of our jobs to start failing due to them unfortunately having references to /home/jenkins spread throughout their build & test logic. We are attempting to force the default workingDir back to /home/jenkins until we can update all our existing references to it.   
 

  
 
 
 
 

 
 
 

 
 

[JIRA] (JENKINS-59160) Cannot Override workingDir for jnlp container

[mike_...@intuit.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mike Nau created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59160  
 
 
  Cannot Override workingDir for jnlp container   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 kubernetes-plugin  
 
 
Created: 
 2019-08-30 22:36  
 
 
Environment: 
 Jenkins: 2.176.2  Jenkins Kubernetes Plugin: 1.18.3  Kubernetes: v1.13.9  Cluster OS: Amazon Linux, 64-Bit  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Mike Nau  
 

  
 
 
 
 

 
 With version 1.18.3 of the Jenkins Kubernetes Plugin, I am not able to override the default workingDir for the jnlp container. Here's the pod template I am using:   

 

agent {
kubernetes {
// Using a dynamic pod n ame because static labels are known to cause pod creation errors.
label "mypod-${UUID.randomUUID().toString()}"
defaultContainer "maven"
yaml """
apiVersion: v1
kind: Pod
spec:
  containers:
  - name: jnlp
image: jenkins/jnlp-slave:alpine
args: ['\$(JENKINS_SECRET)', '\$(JENKINS_NAME)']
workingDir: /home/jenkins/agent2
  - name: maven
image: maven:3.5.3-jdk-8
command:
- cat
tty: true
workingDir: /home/jenkins/agent2
"""
}
}
 

 Job errors as (I have added -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true)     

 

sh: 1: cd: can't cd to /home/jenkins/agent/workspace/Pipeline_With_WorkingDir
sh: 1: 

[JIRA] (JENKINS-59159) Please delete these two files so that it doesn't show up in google search

[samsun...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Yu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59159  
 
 
  Please delete these two files so that it doesn't show up in google search   
 

  
 
 
 
 

 
Change By: 
 Kevin Yu  
 

  
 
 
 
 

 
 Please help delete these two files on Jenkins Jira so that it doesn't show up in Google search anymore. It has some information regarding our company's internal information:  {code:java} '  [^  https://issues.jenkins-ci.org/secure/attachment/44565/ config-2.8.1.xml ]  '   ' https://issues.jenkins-ci.org/secure/attachment/44564/config-0.17.xml' {code}    Thank you very much  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201596.1567202985000.3525.1567203720149%40Atlassian.JIRA.

[JIRA] (JENKINS-59159) Please delete these two files so that it doesn't show up in google search

[samsun...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Yu updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59159  
 
 
  Please delete these two files so that it doesn't show up in google search   
 

  
 
 
 
 

 
Change By: 
 Kevin Yu  
 

  
 
 
 
 

 
 Please help delete these two files on Jenkins Jira so that it doesn't show up in Google search anymore. It has some information regarding our company's internal information: ' [^config-2.8.1.xml]  '  [^ ' https://issues.jenkins-ci.org/secure/attachment/44564/ config-0.17.xml ] ' Thank you very much  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201596.1567202985000.3524.1567203060063%40Atlassian.JIRA.

[JIRA] (JENKINS-59159) Please delete these two files so that it doesn't show up in google search

[samsun...@hotmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kevin Yu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59159  
 
 
  Please delete these two files so that it doesn't show up in google search   
 

  
 
 
 
 

 
Issue Type: 
  Task  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-08-30 22:09  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Kevin Yu  
 

  
 
 
 
 

 
 Please help delete these two files on Jenkins Jira so that it doesn't show up in Google search anymore. It has some information regarding our company's internal information: [^config-2.8.1.xml] [^config-0.17.xml] Thank you very much  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
  

[JIRA] (JENKINS-59158) Support running Job DSL scripts in parallel in pipeline with DISABLE or DELETE action

[daniel.carring...@hpe.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Carrington created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59158  
 
 
  Support running Job DSL scripts in parallel in pipeline with DISABLE or DELETE action   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Daniel Spilker  
 
 
Components: 
 job-dsl-plugin  
 
 
Created: 
 2019-08-30 21:40  
 
 
Environment: 
 Jenkins 1.176.2  job-dsl-plugin 1.75  
 
 
Labels: 
 pipeline performance  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Daniel Carrington  
 

  
 
 
 
 

 
 One use case for running multiple Job DSL build steps would be to accumulate jobs defined in multiple repositories. Consider a pipeline that does: 

 

  stage ("repo a") {
  checkout "our/repo-a"
  jobDsl "jobs/**/*.groovy"
  }
  stage ("repo b") {
  checkout "our/repo-b"
  jobDsl "jobs/**/*.groovy"
  }
 

 I run multiple Job DSL build steps in order to speed up the Job DSL configuration seed job. I have about 520 active jobs on my Jenkins instance, and they are all managed in a single repository. They are, thankfully, somewhat organized by project codename. My Job DSL pipeline reads something like: 

 

List folders = ['project-a', 'project-b', 'project-c', ...] // roughly 10-20 

[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-59094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Agent tunnel connection issues after ugrading Jenkins to 2.191   
 

  
 
 
 
 

 
 https://github.com/jenkinsci/jenkins/pull/4186 for a temporary regression fix until the new version of Remoting is ready  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.3518.1567198800268%40Atlassian.JIRA.

[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON

[wi...@ceilfors.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wisen Tanasa commented on  JENKINS-58987  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: issue_updated trigger handler can't find "name" field in JSON   
 

  
 
 
 
 

 
 That's ok. Is your job working now then I presume?  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201336.1566200967000.3510.1567196700116%40Atlassian.JIRA.

[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException

[wi...@ceilfors.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Wisen Tanasa commented on  JENKINS-58754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JIRA-JENKINS Integration | JsonException   
 

  
 
 
 
 

 
 Selva G The endpoint that you're trying to hit is not supposed to be hit manually, it'll be hit by JIRA automatically on issue change. If you observe that there's no job triggered, please follow the troubleshooting guide and see if you have a connectivity issue: https://github.com/jenkinsci/jira-trigger-plugin#troubleshooting  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201057.1564657212000.3505.1567195500414%40Atlassian.JIRA.

[JIRA] (TEST-22) Add a button to test ircbot configuration via web console

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-22  
 
 
  Add a button to test ircbot configuration via web console   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140322.1309275944000.3493.1567195080489%40Atlassian.JIRA.

[JIRA] (TEST-49) Integration with Serena Dimensions VRS.

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-49  
 
 
  Integration with Serena Dimensions VRS.
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164686.1440419615000.3496.1567195080528%40Atlassian.JIRA.

[JIRA] (TEST-26) Add a 'test configuration by sending message to ...' button for ircbot

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-26  
 
 
  Add a 'test configuration by sending message to ...' button for ircbot   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140320.1309275822000.3489.1567195022218%40Atlassian.JIRA.

[JIRA] (TEST-46) Issue while configuring email-ext plugin

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-46  
 
 
  Issue while configuring email-ext plugin   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.163071.1432821521000.3484.1567195021947%40Atlassian.JIRA.

[JIRA] (TEST-10) Warnings Compiler Plugin for IAR C/C++ does not report warnings

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-10  
 
 
  Warnings Compiler Plugin for IAR C/C++ does not report warnings   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.138966.1298026909000.3487.1567195022042%40Atlassian.JIRA.

[JIRA] (TEST-159) after loging throughtcmd with this java -Dhudson.model.DirectoryBrowserSupport.csp="" -jar jenkins.war there is no extent report Genrated

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-159  
 
 
  after loging throughtcmd with this java -Dhudson.model.DirectoryBrowserSupport.csp="" -jar jenkins.war there is no extent report Genrated   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195891.1543328596000.3481.1567195021584%40Atlassian.JIRA.

[JIRA] (TEST-28) Jabber plugin does not resolve xmpp DNS SRV records correctly (_xmpp-client._tcp, _xmpp-server._tcp)

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-28  
 
 
  Jabber plugin does not resolve xmpp DNS SRV records correctly (_xmpp-client._tcp, _xmpp-server._tcp)   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140715.1311933114000.3478.1567195021220%40Atlassian.JIRA.

[JIRA] (TEST-25) Add a button to test ircbot configuration via web console

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-25  
 
 
  Add a button to test ircbot configuration via web console   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140323.1309276047000.3491.1567195022513%40Atlassian.JIRA.

[JIRA] (TEST-24) Add a button to test ircbot configuration via web console

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-24  
 
 
  Add a button to test ircbot configuration via web console   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140324.1309276349000.3465.1567194961227%40Atlassian.JIRA.

[JIRA] (TEST-86) Sometimes jenkins stopped the execution on any of the test cases.

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-86  
 
 
  Sometimes jenkins stopped the execution on any of the test cases.   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168594.1456748833000.3470.1567194961326%40Atlassian.JIRA.

[JIRA] (TEST-23) ability to notify custom content

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-23  
 
 
  ability to notify custom content   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140685.1311804773000.3467.1567194961271%40Atlassian.JIRA.

[JIRA] (TEST-27) ability to notify custom content

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-27  
 
 
  ability to notify custom content   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140684.1311804739000.3463.1567194961199%40Atlassian.JIRA.

[JIRA] (TEST-40) Integration issue with HP ALM Performance Center

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-40  
 
 
  Integration issue with HP ALM Performance Center   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154691.1399046674000.3476.1567194961431%40Atlassian.JIRA.

[JIRA] (TEST-41) Master and salve mode

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-41  
 
 
  Master and salve mode   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155113.1400497007000.3473.1567194961387%40Atlassian.JIRA.

[JIRA] (TEST-20) ability to notify custom content

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-20  
 
 
  ability to notify custom content   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140681.1311804542000.3461.1567194900702%40Atlassian.JIRA.

[JIRA] (JENKINS-59157) MalformedByteSequenceException during analysis

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59157  
 
 
  MalformedByteSequenceException during analysis   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Project: 
 test Jenkins  
 
 
Key: 
 TEST JENKINS - 12 59157  
 
 
Workflow: 
 JNJira  + In-Review  
 
 
Component/s: 
 warnings-plugin  
 
 
Component/s: 
 test1  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.139076.1299077644000.3457.1567194900625%40Atlassian.JIRA.

[JIRA] (TEST-21) ability to notify custom content

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl closed an issue as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Wrong project  
 

  
 
 
 
 

 
 test /  TEST-21  
 
 
  ability to notify custom content   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Status: 
 Open Closed  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.140682.1311804574000.3459.1567194900663%40Atlassian.JIRA.

[JIRA] (JENKINS-59156) Run API test sets on HP ALM from Jenkins

[slide.o....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl moved an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59156  
 
 
  Run API test sets on HP ALM from Jenkins   
 

  
 
 
 
 

 
Change By: 
 Alex Earl  
 
 
Project: 
 test Jenkins  
 
 
Key: 
 TEST JENKINS - 47 59156  
 
 
Issue Type: 
 Patch Bug  
 
 
Workflow: 
 JNJira  + In-Review  
 
 
Component/s: 
 core  
 
 
Component/s: 
 test1  
 
 
Component/s: 
 test2  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





-- 

[JIRA] (JENKINS-58067) Explain why duplicate syncIDs are a problem

[conker...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kris Conklin commented on  JENKINS-58067  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Explain why duplicate syncIDs are a problem   
 

  
 
 
 
 

 
 I have seen these errors for a long time in my logs but this is the first time ive actually understood why, so I would agree a better error text would be very helpful.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200091.1560856096000.3441.1567193760155%40Atlassian.JIRA.

[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191

[jthomp...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jeff Thompson commented on  JENKINS-59094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Agent tunnel connection issues after ugrading Jenkins to 2.191   
 

  
 
 
 
 

 
 Dzianis Mazuronak, I had planned to have an incrementals version published to the Jenkins Artifactory repository that you could consider testing. Unfortunately, it's not fully set up for that yet, but there are changes in the works to enable it. Without that, it is definitely harder to test. I'll see if anyone else is able to perform any reviews or tests. I hope to get Remoting released early next and included in the following Jenkins weekly.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.3439.1567193460196%40Atlassian.JIRA.

[JIRA] (JENKINS-59094) Agent tunnel connection issues after ugrading Jenkins to 2.191

[dzianis.mazuro...@swisspost.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dzianis Mazuronak edited a comment on  JENKINS-59094  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Agent tunnel connection issues after ugrading Jenkins to 2.191   
 

  
 
 
 
 

 
 Here is the jenkins-slave.xml file from my windows slave xx05ws016:{code:xml}  jenkinsslave-C__projects_jenkins  Jenkins agent (jenkinsslave-C__projects_jenkins)  This service runs an agent for Jenkins automation server.  C:\Program Files (x86)\AdoptOpenJDK\jre-8.0.222.10-hotspot\bin\java.exe  -Xrs  -jar "%BASE%\slave.jar" -jnlpUrl https://tools.x.local/devjenkins/computer/x05ws016/slave-agent.jnlp -secret XXX -noCertificateCheck  rotate className="winsw.Plugins.RunawayProcessKiller.RunawayProcessKillerExtension"   id="killOnStartup">  %BASE%\jenkins_agent.pid  5000  false  {code} Unfortunately, I'll  *not*  be able to test your PR.  Compiling Jenkins from the source code is not a easy task.   
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201514.1566889039000.3433.1567193100193%40Atlassian.JIRA.

[JIRA] (JENKINS-33596) Disable DNSMultiCast & UDPBroadcastThread by default

[boa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Matt Sicker commented on  JENKINS-33596  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Disable DNSMultiCast & UDPBroadcastThread by default   
 

  
 
 
 
 

 
 I'd love to see this done purely because the tests for it are flaky on my machine. Also, this feature should be disabled by default for security hardening.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169040.1458146484000.3423.1567191660281%40Atlassian.JIRA.

[JIRA] (JENKINS-43911) Environment variables can't be used in agent configuration

[bitwise...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman stopped work on  JENKINS-43911  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Status: 
 In Progress Open  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181439.149331354.3393.1567191421750%40Atlassian.JIRA.

[JIRA] (JENKINS-59155) System hook doesn't create webhook on newly created empty projects

[parichay.barpa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Parichay Barpanda created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59155  
 
 
  System hook doesn't create webhook on newly created empty projects   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Joseph Petersen  
 
 
Components: 
 gitlab-branch-source-plugin  
 
 
Created: 
 2019-08-30 18:14  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Parichay Barpanda  
 

  
 
 
 
 

 
 Add webhook for newly created projects. It is skipping by default branch potentially missing. Project is empty.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

[JIRA] (JENKINS-59153) Link to Job sporadically broken due to null Jenkins root URL

[f.mod...@gmx.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Falko Modler commented on  JENKINS-59153  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Link to Job sporadically broken due to null Jenkins root URL   
 

  
 
 
 
 

 
 PR 54 switches from `new` to `.get()`.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201590.1567184497000.3387.1567188780186%40Atlassian.JIRA.

[JIRA] (JENKINS-59153) Link to Job sporadically broken due to null Jenkins root URL

[f.mod...@gmx.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Falko Modler edited a comment on  JENKINS-59153  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Link to Job sporadically broken due to null Jenkins root URL   
 

  
 
 
 
 

 
 [PR 54|https://github.com/jenkinsci/rocketchatnotifier-plugin/pull/54] switches from  `  {{ new ` }}  to  `  {{ .get() ` }} .  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201590.1567184497000.3389.1567188780211%40Atlassian.JIRA.

[JIRA] (JENKINS-59154) Emoji support for publisher usage

[f.mod...@gmx.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Falko Modler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59154  
 
 
  Emoji support for publisher usage   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Martin Reinhardt  
 
 
Components: 
 rocket-chat-notifier-plugin  
 
 
Created: 
 2019-08-30 17:11  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Falko Modler  
 

  
 
 
 
 

 
 I could not figure out how to set a specific emoji (like :sob: for failing builds) when using this plugin as a publisher (not as a pipeline step). Ideally, one should be able to set a specific emoji for each status (e.g. :sob: for failing builds, :ok_hand: for successful builds etc.).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

   

[JIRA] (JENKINS-59153) Link to Job sporadically broken due to null Jenkins root URL

[f.mod...@gmx.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Falko Modler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59153  
 
 
  Link to Job sporadically broken due to null Jenkins root URL   
 

  
 
 
 
 

 
Change By: 
 Falko Modler  
 

  
 
 
 
 

 
 I had very inconsistent results when testing this plugin as a publisher (not as a pipeline step)._Sporadically_, the "{{... (Open)}}" link in the message was showing up as "{{()}}".The {{null}} part is the Jenkins root URL.I don't really understand how this can happen because _both_ the "Jenkins URL" under "Jenkins Location" _and_ "Build Server URL" under "Global RocketChat Notifier Settings" are configured properly.After some research I did find the following statement regarding the usage of {{new JenkinsLocationConfiguration()}} vs {{JenkinsLocationConfiguration.get()}}:https://issues.jenkins-ci.org/browse/JENKINS-52983?focusedCommentId=347707=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-347707RC notifier is using the apparently "deprecated" {{new  JenkinsLocationConfiguration() }} approach which should be switched to {{.get()}}, AFAICS.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit 

[JIRA] (JENKINS-59153) Link to Job sporadically broken due to null Jenkins root URL

[f.mod...@gmx.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Falko Modler updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59153  
 
 
  Link to Job sporadically broken due to null Jenkins root URL   
 

  
 
 
 
 

 
Change By: 
 Falko Modler  
 

  
 
 
 
 

 
 I had very inconsistent results when testing this plugin as a publisher (not as a pipeline step)._Sporadically_, the  "  {{... (Open)}} "  link in the message was showing up as  "  {{()}} " .The {{null}} part is the Jenkins root URL.I don't really understand how this can happen because _both_ the "Jenkins URL" under "Jenkins Location" _and_ "Build Server URL" under "Global RocketChat Notifier Settings" are configured properly.After some research I did find the following statement regarding the usage of {{new JenkinsLocationConfiguration()}} vs {{JenkinsLocationConfiguration.get()}}:https://issues.jenkins-ci.org/browse/JENKINS-52983?focusedCommentId=347707=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-347707RC notifier is using the apparently "deprecated" {{new}} approach which should be switched to {{.get()}}, AFAICS.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit 

[JIRA] (JENKINS-59153) Link to Job sporadically broken due to null Jenkins root URL

[f.mod...@gmx.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Falko Modler created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59153  
 
 
  Link to Job sporadically broken due to null Jenkins root URL   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Martin Reinhardt  
 
 
Components: 
 rocket-chat-notifier-plugin  
 
 
Created: 
 2019-08-30 17:01  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Falko Modler  
 

  
 
 
 
 

 
 I had very inconsistent results when testing this plugin as a publisher (not as a pipeline step). Sporadically, the ... (Open) link in the message was showing up as (). The null part is the Jenkins root URL. I don't really understand how this can happen because both the "Jenkins URL" under "Jenkins Location" and "Build Server URL" under "Global RocketChat Notifier Settings" are configured properly. After some research I did find the following statement regarding the usage of new JenkinsLocationConfiguration() vs JenkinsLocationConfiguration.get(): https://issues.jenkins-ci.org/browse/JENKINS-52983?focusedCommentId=347707=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-347707 RC notifier is using the apparently "deprecated" new approach which should be switched to .get(), AFAICS.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

[JIRA] (JENKINS-59112) [P4 Plugin] Support Switching Between Commit and Edge Servers on Sync Tasks

[krout...@ea.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Kurt Routley updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59112  
 
 
  [P4 Plugin] Support Switching Between Commit and Edge Servers on Sync Tasks   
 

  
 
 
 
 

 
Change By: 
 Kurt Routley  
 

  
 
 
 
 

 
 Notes here from our discussion at Jenkins World.TL;DR: Would be nice to support switching from commit to edge server cleanly for sync only operations.We recently set up an edge server for our commit server. Ideally we would like to be able to update the P4Port value for the same credential used for our Pipeline jobs so that we don't need to configure all of them to point to a new credential. The jobs would be using the same workspace. There is an issue though that if we only update the P4Port value from the commit to the edge server, then the workspace is still tied to the commit server and the sync will fail. It would be nice if the P4 Plugin could handle the switch from the commit server to edge server if the P4Port value on the credential has been changed.We had discussed about using p4 reload to do this, however, this requires super permissions for the account  (if the -f force flag is used) , which our account does not have.The other possible solution we had mentioned was to: * Record the changelist the workspace is currently sync'd to on the commit server * Delete the client from the commit server * Recreate the client on the edge server * Perform a p4 flush / p4 sync -k to the changelist value * Perform a reconcile to the new changelist value being sync'd to  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira 

[JIRA] (JENKINS-52348) Windows bat steps never fail

[ma...@slonopotamus.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marat Radchenko closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-52348  
 
 
  Windows bat steps never fail   
 

  
 
 
 
 

 
Change By: 
 Marat Radchenko  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192137.1530631947000.3346.1567181410231%40Atlassian.JIRA.

[JIRA] (JENKINS-52348) Windows bat steps never fail

[ma...@slonopotamus.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marat Radchenko commented on  JENKINS-52348  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Windows bat steps never fail   
 

  
 
 
 
 

 
 This is expected behavior, read documentation on returnStatus parameter:  

Normally, a script which exits with a nonzero status code will cause the step to fail with an exception. If this option is checked, the return value of the step will instead be the status 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192137.1530631947000.3344.1567181410051%40Atlassian.JIRA.

[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step

[ma...@slonopotamus.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marat Radchenko updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59152  
 
 
  Jenkins fails to properly abort "bat" step   
 

  
 
 
 
 

 
Change By: 
 Marat Radchenko  
 

  
 
 
 
 

 
 # Windows# Jenkins 2.176.1# Create pipeline:{code}node() {  bat "ping 127.0.0.1 -n 10"}{code}# Run pipeline# Abort pipeline# View build logExpected: pipeline aborts fast and without any issuesActual (66% reproducibility):# It takes pipeline 20s to abort# Build log contains "Click here to forcibly terminate running steps" and "After 20s process did not stop", indicating that Jenkins has issues with stopping the pipeline# "Click here to forcibly terminate running steps" link is still visible even after the build has finishedIssue analysis:# There is a race condition between 2 minute timer in {{hudson.util.ProcessTree.WindowsOSProcess#killSoftly}} introduced for JENKINS-17116  by [PR#3414|https://github.com/jenkinsci/jenkins/pull/3414]  and 20s timer in {{org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep.Execution#stop}}. It is possible for {{DurableTaskStep}} to pretend that step was cancelled while it fact process is still running. Because of this race condition, it is possible to trick Jenkins into thinking that build has finished while if fact there are still processes running in workspace and potentially locking files there (this happens to us in practice).# {{org.jvnet.winp.WinProcess#sendCtrlC}} that is used in {{hudson.util.ProcessTree.WindowsOSProcess#killSoftly}} is NOT a proper way to terminate processes.  Many apps do not interpret CTRL+C as a shutdown signal. ({{cmd.exe}} being the most important one here, because running {{bat}} in pipeline involved TWO {{cmd.exe}} - one running {{jenkins-wrapper.bat}} and second running {{jenkins-main.bat}}. Why you're not using [TerminateProcess function|https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-terminateprocess] from WinAPI?# There's a race condition between gathering of process list in {{hudson.util.ProcessTree.Windows#Windows}} constructor and killing of the processes, during which build can produce new processes that will not be attempted to be killed.# Usage of {{JENKINS_NODE_COOKIE}} to find what processes to kill is unreliable because 1) processes are free to alter their environment 2) [CreateProcessA|https://docs.microsoft.com/en-us/windows/win32/api/processthreadsapi/nf-processthreadsapi-createprocessa] allows to pass custom environment variables 3) It has unpredictable order 4) It doesn't match Jenkins behavior on Linux  
 

  
 
 
 
 

 
 
 
   

[JIRA] (JENKINS-59152) Jenkins fails to properly abort "bat" step

[ma...@slonopotamus.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marat Radchenko created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59152  
 
 
  Jenkins fails to properly abort "bat" step   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 core  
 
 
Created: 
 2019-08-30 16:04  
 
 
Environment: 
 Windows  Jenkins 2.176.1  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Marat Radchenko  
 

  
 
 
 
 

 
 
 
Windows 
Jenkins 2.176.1 
Create pipeline: 

 
node() {
  bat "ping 127.0.0.1 -n 10"
}
 

 
Run pipeline 
Abort pipeline 
View build log 
 Expected: pipeline aborts fast and without any issues Actual (66% reproducibility): 
 
It takes pipeline 20s to abort 
Build log contains "Click here to forcibly terminate running steps" and "After 20s process did not stop", indicating that Jenkins has issues with stopping the pipeline 
"Click here to forcibly terminate 

[JIRA] (JENKINS-59151) Blue ocean nodes are not marked red when parallel stage fails

[davidjack...@wawanesa.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 David Jackson created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59151  
 
 
  Blue ocean nodes are not marked red when parallel stage fails   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 BlueOceanBug.PNG  
 
 
Components: 
 blueocean-plugin, pipeline  
 
 
Created: 
 2019-08-30 15:29  
 
 
Environment: 
 Jenkins 2.176.2  Blueocean 1.7.2  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 David Jackson  
 

  
 
 
 
 

 
 

 

pipeline {
agent none
stages {
stage('Stage 1') {
steps {
echo "Stage 1"
}
}
stage('Parallel Stage') {
parallel {
stage('Stage 2') {
stages {
stage ('Stage 2.1') {
steps {
echo "Stage 2.1"
}
}

stage ('Stage 2.2') {
steps {
script {
def parallelStage2 = [:]

parallelStage2['Stage 2.2.1'] = {
echo "Stage 2.2.1"
}

parallelStage2['Stage 2.2.2'] = {
echo "Stage 2.2.2"

[JIRA] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build

[christoph.lin...@dvbern.ch (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Linder edited a comment on  JENKINS-30296  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build   
 

  
 
 
 
 

 
 Can confirm this bug.Some more detail:We had a string parameter  containing  named  BRANCH  with  ' \ */feature/ \ *' ( without the quotes, at least that's  what is  visible in the GUI) and the GIT branch specifier configured to use this variable: ${BRANCH}.Some developer created the branch "feature/feature/foobar".The bug only got triggered as long as the branch with the duplicate "feature" was present. We did lots of tests with different variations of wildcards but the problem mainly got solved when we * removed the string parameter * and used this wildcard directly in branch spec:  origin/feature/**(Unfortunately, I cannot spend more time on testing this but my gut feeling tells me:  string params with wildcards would be the next thing to investigate)   
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164884.1441360857000.3332.1567176360292%40Atlassian.JIRA.

[JIRA] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build

[christoph.lin...@dvbern.ch (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Linder edited a comment on  JENKINS-30296  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build   
 

  
 
 
 
 

 
 Can confirm this bug.Some more detail:We had a string parameter containing BRANCH  '\  */feature/ \ *' (at least that's visible in the GUI) and the GIT branch specifier configured to use this variable: ${BRANCH}.Some developer created the branch "feature/feature/foobar".The bug only got triggered as long as the branch with the duplicate "feature" was present. We did lots of tests with different variations of wildcards but the problem mainly got solved when we * removed the string parameter * and used this wildcard directly in branch spec:  origin/feature/**(Unfortunately, I cannot spend more time on testing this but my gut feeling tells me:  string params with wildcards would be the next thing to investigate)   
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164884.1441360857000.3323.1567176300306%40Atlassian.JIRA.

[JIRA] (JENKINS-30296) Infinite loop (pooling changes continuously) when using "*/master" branches to build

[christoph.lin...@dvbern.ch (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Linder commented on  JENKINS-30296  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Infinite loop (pooling changes continuously) when using "*/master" branches to build   
 

  
 
 
 
 

 
 Can confirm this bug. Some more detail: We had a string parameter containing BRANCH /feature/' (at least that's visible in the GUI) and the GIT branch specifier configured to use this variable: ${BRANCH}. Some developer created the branch "feature/feature/foobar". The bug only got triggered as long as the branch with the duplicate "feature" was present.   We did lots of tests with different variations of wildcards but the problem mainly got solved when we 
 
removed the string parameter 
and used this wildcard directly in branch spec:  origin/feature/** 
 (Unfortunately, I cannot spend more time on testing this but my gut feeling tells me:  string params with wildcards would be the next thing to investigate)    
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.164884.1441360857000.3314.1567176240338%40Atlassian.JIRA.

[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing

[joshua.ya...@orasi.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Yates commented on  JENKINS-59090  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing   
 

  
 
 
 
 

 
 Anda Sorina Laakso  Can we get an update on this? this functionality is critical for the customer and the tool incorrectly marking builds as failures is a big issue.  Let us know if you need anything additional such as logs etc.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.3306.1567174500129%40Atlassian.JIRA.

[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing

[joshua.ya...@orasi.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Joshua Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59090  
 
 
  Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing   
 

  
 
 
 
 

 
Change By: 
 Joshua Yates  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201510.1566845071000.3303.1567174441576%40Atlassian.JIRA.

[JIRA] (JENKINS-55109) Unable to set credentials with CasC plugin

[fjfernan...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández updated  JENKINS-55109  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-55109  
 
 
  Unable to set credentials with CasC plugin   
 

  
 
 
 
 

 
Change By: 
 Francisco Fernández  
 
 
Status: 
 In Review Resolved  
 
 
Resolution: 
 Done  
 
 
Released As: 
 mailer-1.25  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196170.1544461944000.3297.1567173900969%40Atlassian.JIRA.

[JIRA] (JENKINS-50306) "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion

[aboumedi...@infovista.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Abdelkader Boumediene commented on  JENKINS-50306  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion   
 

  
 
 
 
 

 
 Any news about this issue ? I have this issue also. Note that if I perform "Reply" build that freezes with this error, it works fine. So issue seems occur only when Pipeline is called from another  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189348.1521600215000.3274.1567172580256%40Atlassian.JIRA.

[JIRA] (JENKINS-48791) Cannot open Job configuration

[jenkin...@kundrik.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Slavomir Kundrik commented on  JENKINS-48791  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot open Job configuration   
 

  
 
 
 
 

 
 I'm sorry if you are the wrong person but you are listed as the only maintainer for this plugin and given the low amount of update traffic I just wanted to raise it.  Looks like Oleg is looking at it 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187568.1515067009000.3268.1567169640246%40Atlassian.JIRA.

[JIRA] (JENKINS-59150) Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information

[cimpoiesgeo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 George Cimpoies updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59150  
 
 
  Jenkins LTS 2.176.x logs about the new Stapler routing rules have erroneous information   
 

  
 
 
 
 

 
Change By: 
 George Cimpoies  
 
 
Summary: 
 Upgrading to  Jenkins LTS 2.176.x  documentation has  logs about the new Stapler routing rules have  erroneous information  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201586.1567168518000.3266.1567168680161%40Atlassian.JIRA.

[JIRA] (JENKINS-59150) Upgrading to Jenkins LTS 2.176.x documentation has erroneous information

[cimpoiesgeo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 George Cimpoies created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59150  
 
 
  Upgrading to Jenkins LTS 2.176.x documentation has erroneous information   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 rsandell  
 
 
Components: 
 core, gerrit-trigger-plugin  
 
 
Created: 
 2019-08-30 12:35  
 
 
Environment: 
 Jenkins LTS 2.176.x  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 George Cimpoies  
 

  
 
 
 
 

 
 After upgrading to Jenkins LTS 2.176, the Server Status page in Gerrit Trigger section didn't display any information, showing a "Data error" message. Logs: 

 

2019-08-30 09:47:15.644+ [id=65732] WARNING j.s.s.StaplerFilteredActionListener#onGetterTrigger: New Stapler routing rules result in the URL "/gerrit-trigger/serverStatuses" no longer being allowed. If you consider it safe to use, add the following to the whitelist: "method com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement getServerStatuses". Learn more: https://jenkins.io/redirect/stapler-routing 

 The line  

 

method com.sonyericsson.hudson.plugins.gerrit.trigger.GerritManagement getServerStatuses 

 is wrong, because it doesn't work upon testing. Instead, the correct line to be added to the whitelist is  

  

[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-43758  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Parameters disappear from pipeline job after running the job   
 

  
 
 
 
 

 
 So if you're not using Job DSL, please open a separate JIRA. If you're using the properties step in Scripted Pipeline or the parameters directive in Declarative, those do try to preserve job properties and build parameters defined outside of the pipeline, but Job DSL is still going to wipe out whatever is in the properties and parameters when it runs its seed job. Also, don't ever call properties step more than once in a pipeline - you're gonna run into a bunch of potential pitfalls there.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181174.1492775896000.3242.1567167060569%40Atlassian.JIRA.

[JIRA] (JENKINS-43758) Parameters disappear from pipeline job after running the job

[andrew.ba...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-43758  
 
 
  Parameters disappear from pipeline job after running the job   
 

  
 
 
 
 

 
Change By: 
 Andrew Bayer  
 
 
Component/s: 
 job-dsl-plugin  
 
 
Component/s: 
 build-pipeline-plugin  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181174.1492775896000.3220.1567166942042%40Atlassian.JIRA.

[JIRA] (JENKINS-58212) VaultTokenCredentialBinding is not working in pipeline

[nicolas.dru...@ensc.fr (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nicolas Drufin commented on  JENKINS-58212  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: VaultTokenCredentialBinding is not working in pipeline   
 

  
 
 
 
 

 
 Joseph Petersen No this is resolved since 2.3.0. Ticket can be closed.    
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200272.1561559302000.3218.1567166280437%40Atlassian.JIRA.

[JIRA] (JENKINS-48791) Cannot open Job configuration

[jgl...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-48791  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot open Job configuration   
 

  
 
 
 
 

 
 Not sure why I am being mentioned. I do not have anything to do with this 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187568.1515067009000.3213.1567165860360%40Atlassian.JIRA.

[JIRA] (JENKINS-52613) cannot relaunch ssh agent, when node dies

[jonastonnyniel...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jonas Nielsen commented on  JENKINS-52613  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: cannot relaunch ssh agent, when node dies   
 

  
 
 
 
 

 
 You don't have to change the IP of the agent to an invalid IP and back again. It's sufficient to simply enter the configuration page of the slave and save the already existing configuration. Then you are able to relaunch the agent.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192461.1531857544000.3210.1567165500167%40Atlassian.JIRA.

[JIRA] (JENKINS-43386) Not sending mail to user with permission to view

[luckyhk....@samsung.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hokwang Lee commented on  JENKINS-43386  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Not sending mail to user with permission to view   
 

  
 
 
 
 

 
 suffering this problem, one more here.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.180626.1491465811000.3207.1567165441019%40Atlassian.JIRA.

[JIRA] (JENKINS-54326) JUnit fails on remote node after upgrading to 1.26.1

[toni....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Toni Van de Voorde commented on  JENKINS-54326  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JUnit fails on remote node after upgrading to 1.26.1   
 

  
 
 
 
 

 
 Andrey Nudko The thing is, our ami contains a java installation ... and we never had the issue before. Now I do also have another issue currently going on, so I'm not sure if there are related ... (cf https://issues.jenkins-ci.org/browse/JENKINS-59137?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel)  Currently trying something out with your comment and see if it changes anything ...  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194979.1540859482000.3179.1567164720189%40Atlassian.JIRA.

[JIRA] (JENKINS-48791) Cannot open Job configuration

[jenkin...@kundrik.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Slavomir Kundrik commented on  JENKINS-48791  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot open Job configuration   
 

  
 
 
 
 

 
 Jesse Glick I have submitted a PR for this  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187568.1515067009000.3174.1567162800259%40Atlassian.JIRA.

[JIRA] (JENKINS-48791) Cannot open Job configuration

[jenkin...@kundrik.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Slavomir Kundrik assigned an issue to Slavomir Kundrik  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-48791  
 
 
  Cannot open Job configuration   
 

  
 
 
 
 

 
Change By: 
 Slavomir Kundrik  
 
 
Assignee: 
 Slavomir Kundrik  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187568.1515067009000.3168.1567162680374%40Atlassian.JIRA.

[JIRA] (JENKINS-48791) Cannot open Job configuration

[jenkin...@kundrik.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Slavomir Kundrik started work on  JENKINS-48791  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 Slavomir Kundrik  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187568.1515067009000.3170.1567162680397%40Atlassian.JIRA.

[JIRA] (JENKINS-58236) Provide mechanism to define dynamic stages in declarative pipelines

[luckyhk....@samsung.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Hokwang Lee commented on  JENKINS-58236  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide mechanism to define dynamic stages in declarative pipelines   
 

  
 
 
 
 

 
 The number of Dockerfile is increasing more and more, so this feature is really needed and important to all users.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200297.1561627989000.3163.1567161840215%40Atlassian.JIRA.

[JIRA] (JENKINS-54326) JUnit fails on remote node after upgrading to 1.26.1

[andrey.nu...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrey Nudko commented on  JENKINS-54326  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JUnit fails on remote node after upgrading to 1.26.1   
 

  
 
 
 
 

 
 We had similar problem in EC2, and that was happening with both 1.28 and 1.24. In our case the issue was that cloud-init script was sneakily upgrading JDK in the background after agent process was launched. So agent was launched using one java installation, which is then being deleted during upgrade - and now all system jars are unavailable. A quick workaround was to add some `yum install` as node init script - that delays agent startup until update finished. We're looking to change our ami-s to avoid auto-upgrade on launch as a proper solution.  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194979.1540859482000.3157.1567161420232%40Atlassian.JIRA.

[JIRA] (JENKINS-48791) Cannot open Job configuration

[jenkin...@kundrik.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Slavomir Kundrik commented on  JENKINS-48791  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot open Job configuration   
 

  
 
 
 
 

 
 I have come across the same problem today. It turns out that you can create a tool entry on the Global Tools Configuration page but Tool Environment plugin does not have a null check for it in toolsByVar() method. 

 

private static Map toolsByVar() {
Map r = new TreeMap();
for (ToolDescriptor desc : ToolInstallation.all()) {
for (ToolInstallation inst : desc.getInstallations()) {
r.put(inst.getName().replaceAll("[^a-zA-Z0-9_]+", "_").toUpperCase(Locale.ENGLISH) + "_HOME", inst);
}
}
return r;
}
 

 inst.getName() needs to be checked for null  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187568.1515067009000.3154.1567160520221%40Atlassian.JIRA.

[JIRA] (JENKINS-50472) Doesn't work with AWS Beijing Region (cn-north-1)

[yeluo...@gmail..com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rurui Ye commented on  JENKINS-50472  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Doesn't work with AWS Beijing Region (cn-north-1)   
 

  
 
 
 
 

 
 there is multiple problem here,    
 
alterEndpointUrl is not saved after fill in 
the alterEndpointUrl is not used when connect to aws ec2 endpoint 
China aws has totally different endpoint for all services, there is no way to specify it. 
 https://docs.amazonaws.cn/en_us/general/latest/gr/rande.html#cnnorthwest_region  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189532.1522290341000.3145.1567158840917%40Atlassian.JIRA.

[JIRA] (JENKINS-50472) Doesn't work with AWS Beijing Region (cn-north-1)

[yeluo...@gmail..com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rurui Ye updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-50472  
 
 
  Doesn't work with AWS Beijing Region (cn-north-1)   
 

  
 
 
 
 

 
Change By: 
 Rurui Ye  
 
 
Priority: 
 Minor Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189532.1522290341000.3138.1567158660430%40Atlassian.JIRA.

[JIRA] (JENKINS-50472) Doesn't work with AWS Beijing Region (cn-north-1)

[yeluo...@gmail..com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rurui Ye reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 why is this closed, it's still not work and the default endpoint is different in China or in Gov,   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-50472  
 
 
  Doesn't work with AWS Beijing Region (cn-north-1)   
 

  
 
 
 
 

 
Change By: 
 Rurui Ye  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Closed Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189532.1522290341000.3133.1567155780516%40Atlassian.JIRA.

[JIRA] (JENKINS-54326) JUnit fails on remote node after upgrading to 1.26.1

[toni....@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Toni Van de Voorde commented on  JENKINS-54326  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JUnit fails on remote node after upgrading to 1.26.1   
 

  
 
 
 
 

 
 Hey guys, I'm also facing this issue (sometimes) ... are you still staying on version 1.24 ? Or the problem fixed itself with latest 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194979.1540859482000.3130.1567155600310%40Atlassian.JIRA.

[JIRA] (JENKINS-33051) Groovy Star-Dot operator not supported in sandbox

[tatu.ka...@eficode.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tatu Kairi commented on  JENKINS-33051  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Groovy Star-Dot operator not supported in sandbox   
 

  
 
 
 
 

 
 Still an issue. The following does not work in script block: 

 

// Simplified example; In reality, there are a lot of defaultArguments to pass
def defaultArguments = [
"arg1": "arg1",
"arg2": "arg2"
]  
 
 if ( my_condition ) {
doStuff(*:defaultArguments, foo: "bar")
} else {
doStuff(*:defaultArguments, foo: "cux")
} 

 

 

General error during canonicalization: java.lang.UnsupportedOperationException

java.lang.UnsupportedOperationException
	at com.cloudbees.groovy.cps.CpsTransformer.visitSpreadMapExpression(CpsTransformer.java:1207)
// etc... 

    
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168380.1455920446000.3111.1567154341380%40Atlassian.JIRA.

[JIRA] (JENKINS-59015) Ability to disable Emojis in Job Names

[o.v.nenas...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Oleg Nenashev commented on  JENKINS-59015  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Ability to disable Emojis in Job Names   
 

  
 
 
 
 

 
 There is a standard naming strategy extension point which should allow prohibiting emojis. https://jenkins.io/doc/developer/extensions/jenkins-core/#projectnamingstrategy    
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201368.1566326742000.3107.1567154280196%40Atlassian.JIRA.

[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change

[ch.fet...@gmx.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Fetzer commented on  JENKINS-59096  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Mercurial plugin stops working after password change   
 

  
 
 
 
 

 
 Anybody out there? I can't work with it currently  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201516.1566893137000.3103.1567153620068%40Atlassian.JIRA.

[JIRA] (JENKINS-59096) Mercurial plugin stops working after password change

[ch.fet...@gmx.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Fetzer updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59096  
 
 
  Mercurial plugin stops working after password change   
 

  
 
 
 
 

 
Change By: 
 Christoph Fetzer  
 
 
Priority: 
 Critical Blocker  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201516.1566893137000.3102.1567153560148%40Atlassian.JIRA.

[JIRA] (JENKINS-59126) Add compatibility test with JCasC

[fjfernan...@cloudbees.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Francisco Fernández updated  JENKINS-59126  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59126  
 
 
  Add compatibility test with JCasC   
 

  
 
 
 
 

 
Change By: 
 Francisco Fernández  
 
 
Status: 
 In Review Resolved  
 
 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201558.1567006548000.3098.1567148760165%40Atlassian.JIRA.

[JIRA] (JENKINS-57240) Only last stage data is sent to influx db from jenkins pipeline

[zyun...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 z cloud commented on  JENKINS-57240  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Only last stage data is sent to influx db from jenkins pipeline   
 

  
 
 
 
 

 
 Aleksi Simell ，According to sridatta s, in the "jenkins_data" table, each build has multiple duplicate data? Is there any way to generate a single record in the "jenkins_data" table each time, and multiple records in the "jenkins_custom_data" table?  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199003.1556612056000.3097.1567148640139%40Atlassian.JIRA.

[JIRA] (JENKINS-59149) 'Test Connection' succesfully sends a message, but build-event notifications don't get sent

[dbockste...@outlook.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Bocksteger updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59149  
 
 
  'Test Connection' succesfully sends a message, but build-event notifications don't get sent   
 

  
 
 
 
 

 
Change By: 
 Daniel Bocksteger  
 
 
Summary: 
 ' Text Test  Connection '  succesfully sends a message, but  ' build  succeed' and other -event  notifications don't get sent  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201585.1567146235000.3085.1567146360150%40Atlassian.JIRA.

[JIRA] (JENKINS-59149) 'Text Connection succesfully sends a message, but 'build succeed' and other notifications don't get sent

[dbockste...@outlook.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Daniel Bocksteger created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-59149  
 
 
  'Text Connection succesfully sends a message, but 'build succeed' and other notifications don't get sent   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Martin Reinhardt  
 
 
Attachments: 
 job_setup.png, notification.png, plugin_setup.png  
 
 
Components: 
 rocket-chat-notifier-plugin  
 
 
Created: 
 2019-08-30 06:23  
 
 
Environment: 
 Jenkins: 2.191  RocketChat Notifier Plugin: 1.4.3  OS: Windows  
 
 
Labels: 
 plugin jenkins rocketchat  
 
 
Priority: 
  Critical  
 
 
Reporter: 
 Daniel Bocksteger  
 

  
 
 
 
 

 
 We switched https to on last week and since we did, Jenkins is not posting Rocket.Chat Notifications for the specified events anymore.   Furthermore, both Test Connection buttons display "Success", the button in the Job sends out a notification as well.   What could cause the Plugin, to not send the specified notifications?  
 

  
 
 
 
 

 
 
 
  

[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException

[smkumaran8...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Selva G commented on  JENKINS-58754  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: JIRA-JENKINS Integration | JsonException   
 

  
 
 
 
 

 
 Sorry, can you elaborate more again. I don't see any connectivity issue again.  Port is listening and putting right parameter  but not sure why?.    Is that something that you can looking for any further details ?  
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201057.1564657212000.3081.1567145520175%40Atlassian.JIRA.

[JIRA] (JENKINS-58085) BlueOcean UI stuck in "Waiting for run to start"

[dmitrijs.serjog...@emergn.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Dmitry Seryogin commented on  JENKINS-58085  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: BlueOcean UI stuck in "Waiting for run to start"   
 

  
 
 
 
 

 
 

 think the simplest reproduction of that kind of issue is a Pipeline like this
 Given you meant modulo 2 rather than 0, yeah, that does reproduce the problem just right - 3rd step is sitting there with 'waiting for run to start' until the step actually completes and the node renders with the green tick.   
 

  
 
 
 
 

 
 
 

 
 
 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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200110.1560887329000.3056.1567145400652%40Atlassian.JIRA.