[JIRA] (JENKINS-41377) Polling has not run yet, although received push event

[peng...@yahoo.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ed Peng commented on  JENKINS-41377  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Polling has not run yet, although received push event
 

  
 
 
 
 

 
 Point 2 from this comment worked for me: https://github.com/jenkinsci/bitbucket-push-and-pull-request-plugin/issues/19#issuecomment-489326391 

2. Did you trigger for the first time the job manually? That's necessary if you are using a pipeline job.
    
 

  
 
 
 
 

 
 
 

 
 
 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.178159.148527334.10458.1565229480354%40Atlassian.JIRA.

[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation

[ol...@apache.org (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Olivier Lamy commented on  JENKINS-58684  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Linux max task resource exhaustion after excessive timer thread creation   
 

  
 
 
 
 

 
 I wonder how many users do you have using BlueOcean UI guys when the problem happen?    
 

  
 
 
 
 

 
 
 

 
 
 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.200967.156416397.10455.1565228940523%40Atlassian.JIRA.

[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version

[m...@basilcrow.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow commented on  JENKINS-58716  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure to check out specified tag for incremental version   
 

  
 
 
 
 

 
 I got a prototype of this working with CHANGE_FORK as follows: 

 
diff --git a/git-changelist-maven-extension/src/main/java/io/jenkins/tools/incrementals/git_changelist_maven_extension/Main.java b/git-changelist-maven-extension/src/main/java/io/jenkins/tools/incrementals/git_changelist_maven_extension/Main.java
index 9e9220a..bd17830 100644
--- a/git-changelist-maven-extension/src/main/java/io/jenkins/tools/incrementals/git_changelist_maven_extension/Main.java
+++ b/git-changelist-maven-extension/src/main/java/io/jenkins/tools/incrementals/git_changelist_maven_extension/Main.java
@@ -137,6 +137,15 @@ public class Main extends AbstractMavenLifecycleParticipant {
 } else {
 log.info("Declining to override the `changelist` or `scmTag` properties");
 }
+String changeFork = System.getenv("CHANGE_FORK");
+if (changeFork != null) {
+if (!props.containsKey("gitHubOrg")) {
+log.info("Setting: -DgitHubOrg=" + changeFork);
+props.setProperty("gitHubOrg", changeFork);
+} else {
+log.info("Declining to override the `gitHubOrg` property");
+}
+}
 } else {
 log.debug("Skipping Git version setting unless run with -Dset.changelist");
 }
 

 This prototype helped me understand that CHANGE_FORK would work if we used two properties in the POM (say, gitHubOrg and gitHubProject), but it CHANGE_FORK wouldn't work if we used one property in the POM (say, gitHubRepo). That's because we'd need to set that property in git-changelist-maven-extension, and at the time git-changelist-maven-extension is running we only have access to the incomplete information in CHANGE_FORK and not the complete information from the parsed POM. So I think we have a choice: either continue this Knuthian yak shave into implementing a CHANGE_FORK_FULL solution for JENKINS-58450, settle for imperfection with CHANGE_FORK and two POM properties, or give up. If you're willing to review and merge the PRs, I'm down to continue the yak shave. What do you think?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  

[JIRA] (JENKINS-58851) Create VMs in specific range of Public IPs

[jie...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58851  
 
 
  Create VMs in specific range of Public IPs   
 

  
 
 
 
 

 
Change By: 
 Jie Shen  
 
 
Comment: 
 Thanks for your suggestion. I will figure out whether it is suitable to achieve this for 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.201166.1565191769000.10442.1565227440261%40Atlassian.JIRA.

[JIRA] (JENKINS-58851) Create VMs in specific range of Public IPs

[jie...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen commented on  JENKINS-58851  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Create VMs in specific range of Public IPs   
 

  
 
 
 
 

 
 Thanks for your suggestion. I will figure out whether it is suitable to achieve this for 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.201166.1565191769000.10440.1565227380161%40Atlassian.JIRA.

[JIRA] (JENKINS-58851) Create VMs in specific range of Public IPs

[jie...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen commented on  JENKINS-58851  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Create VMs in specific range of Public IPs   
 

  
 
 
 
 

 
 Thanks for your suggestion. I will figure out whether it is suitable to achieve this for 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.201166.1565191769000.10439.1565227380150%40Atlassian.JIRA.

[JIRA] (JENKINS-58851) Create VMs in specific range of Public IPs

[jie...@microsoft.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jie Shen assigned an issue to Jie Shen  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58851  
 
 
  Create VMs in specific range of Public IPs   
 

  
 
 
 
 

 
Change By: 
 Jie Shen  
 
 
Assignee: 
 Azure DevOps Jie Shen  
 

  
 
 
 
 

 
 
 

 
 
 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.201166.1565191769000.10436.1565227260270%40Atlassian.JIRA.

[JIRA] (JENKINS-58855) Structure job execute shell script.sh has no effect,but the console display is normal success

[564492...@qq.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 LI BINBIN created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58855  
 
 
  Structure job execute shell script.sh has no effect,but the console display is normal success   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 nobody  
 
 
Attachments: 
 1565226313(1).png  
 
 
Components: 
 shell-script-scm-plugin  
 
 
Created: 
 2019-08-08 01:15  
 
 
Priority: 
  Blocker  
 
 
Reporter: 
 LI BINBIN  
 

  
 
 
 
 

 
 I use jenkins structure a java job,the shell script have one sentence was not implemented successfully:"sh /root/.jenkins/workspace/aaa.sh start" aaa.sh contents are in the attachment. But the jenkins console successfully execute aaa.sh So I'm confused. By the way,it is effective to use XShell execute aaa.sh  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 

[JIRA] (JENKINS-58854) Cannot configure SonarQube plugin with JCasC

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sven-Hendrik Haase updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58854  
 
 
  Cannot configure SonarQube plugin with JCasC   
 

  
 
 
 
 

 
Change By: 
 Sven-Hendrik Haase  
 

  
 
 
 
 

 
 The most recent version of JCasC that works with SonarQube is 1.23. Anything after that results in{noformat}SEVERE: Failed ConfigurationAsCode.initjava.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296) at jenkins.model.Jenkins$5.runTask(Jenkins.java:1095) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) ... 8 moreCaused by: io.jenkins.plugins.casc.ConfiguratorException: unclassified: error configuring 'unclassified' with class io.jenkins.plugins.casc.impl.configurators.GlobalConfigurationCategoryConfigurator configurator at io.jenkins.plugins.casc.ConfigurationAsCode.invokeWith(ConfigurationAsCode.java:652) at io.jenkins.plugins.casc.ConfigurationAsCode.checkWith(ConfigurationAsCode.java:684) at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:668) at io.jenkins.plugins.casc.ConfigurationAsCode.configureWith(ConfigurationAsCode.java:567) at io.jenkins.plugins.casc.ConfigurationAsCode.configure(ConfigurationAsCode.java:280) at io.jenkins.plugins.casc.ConfigurationAsCode.init(ConfigurationAsCode.java:272) ... 13 moreCaused by: io.jenkins.plugins.casc.ConfiguratorException: triggers is required to configure class hudson.plugins.sonar.SonarInstallation at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.tryConstructor(DataBoundConfigurator.java:134) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.instance(DataBoundConfigurator.java:77) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:268) at io.jenkins.plugins.casc.impl.configurators.DataBoundConfigurator.check(DataBoundConfigurator.java:101) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:345) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:288) at io.jenkins.plugins.casc.BaseConfigurator.configure(BaseConfigurator.java:353) at io.jenkins.plugins.casc.BaseConfigurator.check(BaseConfigurator.java:288) at 

[JIRA] (JENKINS-58854) Cannot configure SonarQube plugin with JCasC

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sven-Hendrik Haase created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58854  
 
 
  Cannot configure SonarQube plugin with JCasC   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ewelina Wilkosz  
 
 
Components: 
 configuration-as-code-plugin, sonar  
 
 
Created: 
 2019-08-07 23:23  
 
 
Labels: 
 jcasc-compatibility  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Sven-Hendrik Haase  
 

  
 
 
 
 

 
 The most recent version of JCasC that works with SonarQube is 1.23. Anything after that results in 

 
SEVERE: Failed ConfigurationAsCode.init
java.lang.Error: java.lang.reflect.InvocationTargetException
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110)
	at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:175)
	at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:296)
	at jenkins.model.Jenkins$5.runTask(Jenkins.java:1095)
	at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:214)
	at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.reflect.InvocationTargetException
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104)
	... 8 more
Caused by: io.jenkins.plugins.casc.ConfiguratorException: unclassified: error 

[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only

[j.sp...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jay Spang commented on  JENKINS-51552  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cannot replay pipelines - files are read-only   
 

  
 
 
 
 

 
 What happens if you changer `allwrite: false` in the client definition to be true?  
 

  
 
 
 
 

 
 
 

 
 
 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.190940.1527360591000.10319.1565217180205%40Atlassian.JIRA.

[JIRA] (JENKINS-58853) nexusPublisher hangs when uploading multiple large files to Nexus 3

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Pbc pbc created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58853  
 
 
  nexusPublisher hangs when uploading multiple large files to Nexus 3   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Justin Young  
 
 
Components: 
 nexus-platform-plugin  
 
 
Created: 
 2019-08-07 22:25  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Pbc pbc  
 

  
 
 
 
 

 
 Looks like something might be wrong with nexusPublisher when running on a build agent. The upload gets stuck if I try to upload multiple artifacts over a few MB in size to a Nexus 3 repo, and only if the build is aborted it throws an IOException (see the build log with the stacktrace below). How to reproduce: 
 
it must run on a jenkins agent, in my setup the agent is connected via ssh and runs jdk 1.8u181 (using an agent is important - if you run it on master it works fine) 
OS does not seem to matter (it fails both linux and windows agents) 
you must upload 2 files at the same time in one package to a maven2 hosted repository (on a Nexus 3 repo) 
file size seems to matter, for the small files (20KB) it always works, for the large ones it fails (2 files about 3.8 MB each) 
there are no errors on the Nexus 3 logs 
i was also able to reproduce it by setting up everything with 3 containers: nexus3, jenkins and one agent container based on ubuntu:18.04 
 Sample Pipeline   

 

node('slave') {
// 2 large size (around 3.8 MB each) -- gets stuck
 nexusPublisher 

[JIRA] (JENKINS-51519) GitHub Organization should allow skipping archived repositories

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Chris K commented on  JENKINS-51519  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: GitHub Organization should allow skipping archived repositories   
 

  
 
 
 
 

 
 This would be very useful for my team.  
 

  
 
 
 
 

 
 
 

 
 
 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.190897.152715431.10311.1565216220308%40Atlassian.JIRA.

[JIRA] (JENKINS-53775) FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin

[m...@basilcrow.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow commented on  JENKINS-53775  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: FileNotFoundException for program.dat when running a Pipeline Job concurrently with the Job DSL plugin   
 

  
 
 
 
 

 
 I've been running with the new syntax described in my previous comment for about a month, and this issue hasn't occurred again. Previously it occurred almost every time I deployed changes to a Job DSL 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.194284.1537930113000.10302.1565212800260%40Atlassian.JIRA.

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

[egraeb...@palantir.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Elliot Graebert edited a comment on  JENKINS-58085  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 I'm also running into the same issue, which I also commented on here: https://issues.jenkins-ci.org/browse/JENKINS-49131This issue is  SUPER bad  very frustrating, as it makes the entire CI pipeline look like it's hung .  
 

  
 
 
 
 

 
 
 

 
 
 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.10278.1565211001431%40Atlassian.JIRA.

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

[egraeb...@palantir.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Elliot Graebert edited a comment on  JENKINS-58085  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 I'm also running into the same issue, which I also commented on here: https://issues.jenkins-ci.org/browse/JENKINS-49131This issue is very frustrating, as it makes the entire CI pipeline look like it's hung.  Jenkins 2.187 and Blue Ocean 1.18.0  
 

  
 
 
 
 

 
 
 

 
 
 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.10280.1565211001478%40Atlassian.JIRA.

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

[egraeb...@palantir.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Elliot Graebert commented on  JENKINS-58085  
 

  
 
 
 
 

 
 
  
 
 
 
 

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

  
 
 
 
 

 
 I'm also running into the same issue, which I also commented on here: https://issues.jenkins-ci.org/browse/JENKINS-49131 This issue is SUPER bad.  
 

  
 
 
 
 

 
 
 

 
 
 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.10244.1565210940532%40Atlassian.JIRA.

[JIRA] (JENKINS-58852) Identical Name and ID share same stdout values

[marshall.adr...@sifive.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marshall Adrian created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58852  
 
 
  Identical Name and ID share same stdout values   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 jenkins_web_result_1.png, jenkins_web_result_2.png, junitResults.xml.png, results.rtf, results.xml.png  
 
 
Components: 
 junit-plugin  
 
 
Created: 
 2019-08-07 20:02  
 
 
Environment: 
 Jenkins Ver: 2.176.2 Junit Plugin Ver: 1.28  
 
 
Labels: 
 plugin junit-plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Marshall Adrian  
 

  
 
 
 
 

 
 If I have a result.xml that has two records in it that have the same ID and same NAME, when Junit parses it the resulting junitResult.xml merges those two results together and has some fields that they share and then different 'cases' for specific fields that are not shared. These cases have fields that differentiate the two tests. The issue is that the stdout field is being stored as a merged value instead of an test/case specific value. SO then when you browse to the results on jenkins webpage you are not seeing the correct stdout for each test. This occurs because we have multiple different XMLs that are parsed together and each XML ID starts at 0.  
 

  
 
 
 
   

[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58643  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CPS Mismatches on cpsScript.InvokeMethod   
 

  
 
 
 
 

 
 No, to the patch in the comment by Devin Nusbaum in 2019-08-01.  
 

  
 
 
 
 

 
 
 

 
 
 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.200910.1563983113000.10237.1565207760287%40Atlassian.JIRA.

[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58716  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure to check out specified tag for incremental version   
 

  
 
 
 
 

 
 I suppose that makes sense, yes.  
 

  
 
 
 
 

 
 
 

 
 
 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.201008.1564430335000.10234.1565207700462%40Atlassian.JIRA.

[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-39874  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Abilty to disable pipeline-replay in Job Configuration.   
 

  
 
 
 
 

 
 Ben Langfeld it is either a bug or a misconfiguration. Better to file as a separate (but Link’d) issue with complete, self-contained steps to reproduce from scratch.  
 

  
 
 
 
 

 
 
 

 
 
 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.176488.1479513265000.10233.1565207700427%40Atlassian.JIRA.

[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.

[b...@langfeld.me (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Langfeld commented on  JENKINS-39874  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Abilty to disable pipeline-replay in Job Configuration.   
 

  
 
 
 
 

 
 Jesse Glick I havn't granted that permission either. There must be some other in this set that permits replays.  
 

  
 
 
 
 

 
 
 

 
 
 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.176488.1479513265000.10219.1565207400213%40Atlassian.JIRA.

[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.

[b...@langfeld.me (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Langfeld updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-39874  
 
 
  Abilty to disable pipeline-replay in Job Configuration.   
 

  
 
 
 
 

 
Change By: 
 Ben Langfeld  
 
 
Attachment: 
 Screenshot 2019-08-07 at 16.48.12.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.176488.1479513265000.10211.1565207340352%40Atlassian.JIRA.

[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version

[m...@basilcrow.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Basil Crow commented on  JENKINS-58716  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure to check out specified tag for incremental version   
 

  
 
 
 
 

 
 

Yes, modulo my comment in JENKINS-58450.
 Your comments there sound reasonable to me, but since I'm neither implementing nor reviewing those changes, I don't want to be blocked on them. Are you OK with moving forward with the existing CHANGE_FORK environment variable for this bug, and then using the new CHANGE_FORK_FULL variable in a separate change if and when it becomes available?  
 

  
 
 
 
 

 
 
 

 
 
 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.201008.1564430335000.10209.1565206680129%40Atlassian.JIRA.

[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod

[ey...@jfrog.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eyal Ben Moshe commented on  JENKINS-58643  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CPS Mismatches on cpsScript.InvokeMethod   
 

  
 
 
 
 

 
 Jesse Glick, To which patch are you referring to? Is it my above suggestion? If so, we'll start working on a pull request.  
 

  
 
 
 
 

 
 
 

 
 
 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.200910.1563983113000.10203.1565206560234%40Atlassian.JIRA.

[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58620  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: MPL shared library logic execution caused CPS mismatch warning   
 

  
 
 
 
 

 
 

there is a way to move such messages into the jenkins master log
 No, this would hide the critical diagnostic information from the people writing Pipelines who are normally responsible for making mistakes here. The first step is to have a PR up with an addition to the existing @Ignore’d test case demonstrating the problem using the shortest possible script, possibly something like one of the above examples. In that case, a fix in groovy-cps is likely possible.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58716  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failure to check out specified tag for incremental version   
 

  
 
 
 
 

 
 Yes, modulo my comment in JENKINS-58450.  
 

  
 
 
 
 

 
 
 

 
 
 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.201008.1564430335000.10198.1565205240182%40Atlassian.JIRA.

[JIRA] (JENKINS-58450) CHANGE_FORK doesn't point to the user/repo when the fork name differs from the upstream name

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58450  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CHANGE_FORK doesn't point to the user/repo when the fork name differs from the upstream name   
 

  
 
 
 
 

 
 For consistency, a variable should always include both the account/organization and the repository name, even in the normal case that the fork has the same name as the original repository. Since CHANGE_FORK has been only an account/organization for over two years now, we would risk breaking existing scripts by changing its meaning now. Would need to introduce a new variable name, which means 
 
(scm-api) introducing String SCMHeadOrigin.Fork.getFullName(), I guess defaulting to null 
(branch-api) making BranchNameContributor bind it when set, say to CHANGE_FORK_FULL 
(github-branch-source et al.) overriding the new method in, e.g., PullRequestSCMHead 
  
 

  
 
 
 
 

 
 
 

 
 
 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.200582.156287771.10196.1565205180123%40Atlassian.JIRA.

[JIRA] (JENKINS-37862) Extract build symlink handling to a plugin

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-37862  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Extract build symlink handling to a plugin   
 

  
 
 
 
 

 
 

Will Jenkins remove all the symlinks from existing builds after the upgrade?
 No. See release notes for a script to do this manually if you care.  
 

  
 
 
 
 

 
 
 

 
 
 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.174000.1472663694000.10194.1565204760360%40Atlassian.JIRA.

[JIRA] (JENKINS-58847) After renaming project logs of runs prior to rename are not found

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Won't Fix  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 By design, the log stream names are human-readable and map directly to Jenkins job names. Using the unique-id plugin would make them opaque, reducing ease of transition between Jenkins and external tools. (For the same reason, we decided that JCloudsArtifactManager would not encode its S3 blob name.) Remember you can change a job’s display name without actually renaming it. If JEP-207 were pushed forward, there would be a marker in a build.xml that a particular logging system were used for this build. At that point, we could also add an ItemListener that, upon seeing a job be moved or renamed, would add an extra field to all of its historical build records noting the redirect. Alternately, the log stream name could be unconditionally written when the build is started, at the cost of some redundancy in the normal case. (The log group name is system configuration, and while it might change after first use, it is not expected that the master is able to access arbitrary log groups.)  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58847  
 
 
  After renaming project logs of runs prior to rename are not found   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Fix  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 
   

[JIRA] (JENKINS-58846) Dependency-Check Trend chart doesn't appears on DSL pipelines jobs

[lga...@cayan.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Lukasz Gawel commented on  JENKINS-58846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Dependency-Check Trend chart doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
 We're seeing the same issue. JenkinsFile:   dependencyCheck additionalArguments: '-scan ./*/packages//.dll --scan ./*/.js --format HTML --format XML --suppression OwaspSupression.xml', odcInstallation: 'Dependency-Check-5.2.1' dependencyCheck additionalArguments: '-scan ./*/packages//.dll --scan ./*/.js --format HTML --format XML --suppression OwaspSupression.xml', odcInstallation: 'Dependency-Check-5.2.1' dependencyCheckPublisher failedNewCritical: 1, failedNewHigh: 1, failedNewLow: 1, failedNewMedium: 1, failedTotalCritical: 0, failedTotalHigh: 2, failedTotalLow: 0, failedTotalMedium: 10, pattern: ''  
 

  
 
 
 
 

 
 
 

 
 
 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.201161.1565179135000.10184.1565204100153%40Atlassian.JIRA.

[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition

[egraeb...@palantir.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Elliot Graebert edited a comment on  JENKINS-49131  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
 

  
 
 
 
 

 
 Hey folks, I'm seeing this, and it wasn't directly tied. The symptom is very similar: steps don't get populated until after the stage is done. It really ruins the Blue Ocean experience , as people just see blank stages .  If those stages indicated a problem downstream that needs investigation, they have to check the artifact logs to figure it out.  Jenkins 2.187 and Blue Ocean 1.18.0  
 

  
 
 
 
 

 
 
 

 
 
 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.187966.1516792618000.10166.1565204040431%40Atlassian.JIRA.

[JIRA] (JENKINS-49131) Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition

[egraeb...@palantir.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Elliot Graebert commented on  JENKINS-49131  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Steps are not shown up in Blue Ocean when one of parallel stages is skipped due to "when" condition
 

  
 
 
 
 

 
 Hey folks, I'm seeing this, and it wasn't directly tied. The symptom is very similar: steps don't get populated until after the stage is done. It really ruins the Blue Ocean experience.   Jenkins 2.187 and Blue Ocean 1.18.0  
 

  
 
 
 
 

 
 
 

 
 
 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.187966.1516792618000.10164.1565203980782%40Atlassian.JIRA.

[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-39874  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Abilty to disable pipeline-replay in Job Configuration.   
 

  
 
 
 
 

 
 Ben Langfeld there is a Run/Replay permission that is normally implied by Job/Configure but can be independently granted; perhaps whoever set up authorization did so.  
 

  
 
 
 
 

 
 
 

 
 
 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.176488.1479513265000.10140.1565203680253%40Atlassian.JIRA.

[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-58643  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CPS Mismatches on cpsScript.InvokeMethod   
 

  
 
 
 
 

 
 The patch above seems like the safest and more general fix, if it indeed works. Needs testing.  
 

  
 
 
 
 

 
 
 

 
 
 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.200910.1563983113000.10134.1565203620322%40Atlassian.JIRA.

[JIRA] (JENKINS-58447) Cloud Foundry Plugin Error - Unable to upload to docker application

[mark....@willowtreeapps.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mark Han commented on  JENKINS-58447  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Cloud Foundry Plugin Error - Unable to upload to docker application   
 

  
 
 
 
 

 
 Seeing this exact same issue.  
 

  
 
 
 
 

 
 
 

 
 
 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.200579.1562858624000.10132.1565203380289%40Atlassian.JIRA.

[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed

[tp...@rediker.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 tom peck commented on  JENKINS-58810  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed   
 

  
 
 
 
 

 
 We had this issue recently, I was able to fix it by deleting the "Bitbucket Endpoints" entry in the configure system page on jenkins.  Then I recreated them and it started working again.  We also changed our site's certificate recently, that's probably related.  
 

  
 
 
 
 

 
 
 

 
 
 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.201122.1565008163000.10127.1565200140177%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns commented on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 WOW. By iterating through the various checkName URLs, I've found a particular role name that logs me out. Not all roles do this  https://jenkins/descriptor/com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy/checkName?value=%5Bjsmith%5D (was not originally jsmith, but something similarly simple). I need to investigate why this is happening but jeeez.  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10125.1565199000434%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns commented on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 By disabling calls to the checkName endpoint, I was able to avoid being logged out. Somehow the https://jenkins/descriptor/com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy/checkName?value= is invalidating my sessions.  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10103.1565197500424%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns edited a comment on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 By disabling calls to the checkName endpoint, I was able to avoid being logged out.  Somehow the  https://jenkins/descriptor/com.michelin.cio.hudson.plugins.rolestrategy.RoleBasedAuthorizationStrategy/checkName?value= is invalidating my sessions. Obviously this still leaves the assign roles page broken   
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10111.1565197500694%40Atlassian.JIRA.

[JIRA] (JENKINS-49443) PowerShell Core has renamed the binary from powershell to pwsh

[jtmo...@kahalamgmt.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 JT Moree commented on  JENKINS-49443  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: PowerShell Core has renamed the binary from powershell to pwsh   
 

  
 
 
 
 

 
 Is there no push to get native powershell core in jenkins?   Why is there a two trackers for this plugin?  Is anyone paying attention to either? Based on the linked patch pwsh would be used on all platforms but our jenkins install still natively calls powershell.  We are jumping through hoops to try to get the correct code to run.  Embedded calls through two different powershells and then on to sql are a real PITA.  
 

  
 
 
 
 

 
 
 

 
 
 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.188328.1518022334000.10098.1565197320126%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns edited a comment on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 After seeing the above issue, that I'm considered anonymous when submitting the assignRoles, I did an additional experiment.* view assignRoles page* view page that doesn't require authenticationI see that I'm logged out!  Just viewing the assignRoles page *with _javascript_ enabled* seems to invalidate my session.As it's when _javascript_ is enabled only that logs me out, I can only conclude that an AJAX request triggered by the page is invalidating my session?Looking at dev tools I just see a lot of checkName calls (all returning 200), and then a failed ajaxBuildQueue and ajaxExecutors pair of requests, followed by more succesful checkName calls.  When I test the unauthenticated page in another tab, it looks like my session is invalidated. Response from the ajax call?  "No valid crumb was included in the request"  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10091.1565196960614%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns edited a comment on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 After seeing the above issue, that I'm considered anonymous when submitting the assignRoles, I did an additional experiment.* view assignRoles page* view page that doesn't require authenticationI see that I'm logged out!  Just viewing the assignRoles page *with _javascript_ enabled* seems to invalidate my session.As it's when _javascript_ is enabled only that logs me out, I can only conclude that an AJAX request triggered by the page is invalidating my session? Looking at dev tools I just see a lot of checkName calls (all returning 200), and then a failed ajaxBuildQueue and ajaxExecutors pair of requests, followed by more succesful checkName calls.  When I test the unauthenticated page in another tab, it looks like my session is invalidated.  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10083.1565196900260%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns commented on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 After seeing the above issue, that I'm considered anonymous when submitting the assignRoles, I did an additional experiment. 
 
view assignRoles page 
view page that doesn't require authentication 
 I see that I'm logged out! Just viewing the assignRoles page with _javascript_ enabled seems to invalidate my session. As it's when _javascript_ is enabled only that logs me out, I can only concluded an AJAX request is invalidating my session?  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10067.1565196540850%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns edited a comment on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 After seeing the above issue, that I'm considered anonymous when submitting the assignRoles, I did an additional experiment.* view assignRoles page* view page that doesn't require authenticationI see that I'm logged out!  Just viewing the assignRoles page *with _javascript_ enabled* seems to invalidate my session.As it's when _javascript_ is enabled only that logs me out, I can only  concluded  conclude that  an AJAX request  triggered by the page  is invalidating my session?  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10075.1565196541063%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns edited a comment on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 I'm also seeing this issue. I initially saw the no valid crumb error as well, I believe this is caused by the plugin incorrectly redirecting you via _javascript_ to reauthenticate with your provider (mine is Github Enterprise) which kills the session.  I think this is hiding the root cause.To try and simplify things, I disabled CSRF.  *(removed debug from disabling _javascript_, I  know  now  see that the page requires _javascript_ in order to pass the json form data)*Using developer tools, I can see the assignSubmit response has the following headers:{noformat}content-encoding: gzipcontent-type: text/html;charset=utf-8date: Wed, 07 Aug 2019 16:37:41 GMTserver: nginx/1.13.8status: 403strict-transport-security: max-age=15724800; includeSubDomains;vary: Accept-Encodingx-content-type-options: nosniffx-hudson: 1.395x-hudson-cli-port: 5x-jenkins: 2.164.1x-jenkins-cli-port: 5x-jenkins-cli2-port: 5x-jenkins-session: efedebfbx-required-permission: hudson.model.Hudson.Administerx-you-are-authenticated-as: anonymousx-you-are-in-group-disabled: JENKINS-39402: use -Dhudson.security.AccessDeniedException2.REPORT_GROUP_HEADERS=true or use /whoAmI to diagnose{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10059.1565196361093%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns edited a comment on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 I'm also seeing this issue. I initially saw the no valid crumb error as well, I believe this is caused by the plugin incorrectly redirecting you via _javascript_ to reauthenticate with your provider (mine is Github Enterprise) which kills the session.  I think this is hiding the root cause.To try and simplify things, I disabled  _javascript_, and I disabled  CSRF.  *(removed debug from disabling _javascript_, I know see that the page requires _javascript_ in order to pass the json form data)* Using developer tools, I can see the assignSubmit response has the following headers:{noformat}content-encoding: gzipcontent-type: text/html;charset=utf-8date: Wed, 07 Aug 2019 16:37:41 GMTserver: nginx/1.13.8status: 403strict-transport-security: max-age=15724800; includeSubDomains;vary: Accept-Encodingx-content-type-options: nosniffx-hudson: 1.395x-hudson-cli-port: 5x-jenkins: 2.164.1x-jenkins-cli-port: 5x-jenkins-cli2-port: 5x-jenkins-session: efedebfbx-required-permission: hudson.model.Hudson.Administerx-you-are-authenticated-as: anonymousx-you-are-in-group-disabled: JENKINS-39402: use -Dhudson.security.AccessDeniedException2.REPORT_GROUP_HEADERS=true or use /whoAmI to diagnose{noformat}  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10051.1565196360935%40Atlassian.JIRA.

[JIRA] (JENKINS-58849) Logstash plugin: requires insecure "mask-passwords"

[bochenski.kuba+jenk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski commented on  JENKINS-58849  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Logstash plugin: requires insecure "mask-passwords"   
 

  
 
 
 
 

 
 Please try upgrading the plugin to latest version, as old versions depended on mask-passwords  
 

  
 
 
 
 

 
 
 

 
 
 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.201164.1565189042000.10048.1565196120097%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns edited a comment on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 I'm also seeing this issue. I initially saw the no valid crumb error as well, I believe this is caused by the plugin incorrectly redirecting you via _javascript_ to reauthenticate with your provider (mine is Github Enterprise) which kills the session.  I think this is hiding the root cause.To try and simplify things, I disabled _javascript_, and I disabled CSRF.   * ( removing removed  debug from disabling _javascript_, I know see that the page requires _javascript_ in order to pass the json form data) *  
 

  
 
 
 
 

 
 
 

 
 
 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.199247.1557753306000.10041.1565196000272%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns edited a comment on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 I'm also seeing this issue. I initially saw the no valid crumb error as well, I believe this is caused by the plugin incorrectly redirecting you via _javascript_ to reauthenticate with your provider (mine is Github Enterprise) which kills the session.  I think this is hiding the root cause.To try and simplify things, I disabled _javascript_, and I disabled CSRF.   When doing that  (removing debug from disabling _javascript_,  I  get  know see that  the  following error when submitting the assingRoles  page :!image-2019-08-07-17-25-17-212.png!The content being posted (according  requires _javascript_ in order  to  chrome developer tools) looks to be a lot less than I would expect for  pass  the  complexity of the assign roles matrixes:{noformat}[authenticated]: on[admin]: on[admin]: on[admin]: on[extended-read]: on[admin]: on[admin]: on[admin]: on[anonymous]: on_.: [project1-write]: on[project1-admin]: on[project1-admin]: on[project1-write]: on[project2-write]: on[project2-admin]: on[project3-write]: on[project3-admin]: on[project4-write]: on[project4-admin]: on[project5-write]: on[project5-admin]: on[project6-read]: on[project6-write]: on[project6-admin]: on[project6-admin]: on[project6-write]: on[project1-admin]: on[project1-write]: on[project6-admin]: on[project6-write]: on[project7-write]: on[project7-admin]: on[project6-team-admin]: on[project8-write]: on[project8-admin]: on[project9-write]: on[project9-admin]: on_.: _.: Submit: Savecore:apply:{noformat}  json form data)  
 

  
 
 
 
 

 
 
 

 
 
 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-58843) Error 404 resource not found

[marcia.ro...@wedotechnologies.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marcia Rocha commented on  JENKINS-58843  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Error 404 resource not found   
 

  
 
 
 
 

 
 this error starts happening after we've upgraded from 2.179 to 2.187 you already had this type of error recorded in old jenkin version - https://issues.jenkins-ci.org/browse/JENKINS-22358 Please, could you analyse if this a jenkins bug? thanks    
 

  
 
 
 
 

 
 
 

 
 
 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.201158.1565175731000.10030.1565195760132%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns commented on  JENKINS-57434  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Unable to add or edit roles   
 

  
 
 
 
 

 
 I'm also seeing this issue.  I initially saw the no valid crumb error as well, I believe this is caused by the plugin incorrectly redirecting you via _javascript_ to reauthenticate with your provider (mine is Github Enterprise) which kills the session.  I think this is hiding the root cause. To try and simplify things, I disabled _javascript_, and I disabled CSRF.  When doing that I get the following error when submitting the assingRoles page:  The content being posted (according to chrome developer tools) looks to be a lot less than I would expect for the complexity of the assign roles matrixes: 

 
[authenticated]: on
[admin]: on
[admin]: on
[admin]: on
[extended-read]: on
[admin]: on
[admin]: on
[admin]: on
[anonymous]: on
_.: 
[project1-write]: on
[project1-admin]: on
[project1-admin]: on
[project1-write]: on
[project2-write]: on
[project2-admin]: on
[project3-write]: on
[project3-admin]: on
[project4-write]: on
[project4-admin]: on
[project5-write]: on
[project5-admin]: on
[project6-read]: on
[project6-write]: on
[project6-admin]: on
[project6-admin]: on
[project6-write]: on
[project1-admin]: on
[project1-write]: on
[project6-admin]: on
[project6-write]: on
[project7-write]: on
[project7-admin]: on
[project6-team-admin]: on
[project8-write]: on
[project8-admin]: on
[project9-write]: on
[project9-admin]: on
_.: 
_.: 
Submit: Save
core:apply: 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-41497) Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries

[jenk...@mockies.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Christoph Vogtländer commented on  JENKINS-41497  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Poll SCM and Timer triggers include "Changes" for a Pipeline for any/all Shared Libraries   
 

  
 
 
 
 

 
 I'm also affected by this issue running Jenkins ver. 2.176.2 with "Pipeline: Shared Groovy Libraries" version 2.14 I just recently switched to shared libs from internal workflowLibs.git. I added a global shared library using Subversion defined with "Load implicitly: true", "Allow default version to be overridden: true" and "Include @Library changes in job recent changes: true". After the global library was used in the build for the first time, subsequent builds are now triggered whenever something changes in the global library. I was not able to resolve this by simply deactivating "Include @Library changes in job recent changes". Still, builds were triggered for every commit in the shared lib. Only after a Jenkins restart ("Include @Library changes in job recent changes" is still false) the job is no longer triggered. Why are polling and changelog bound to each other in shared libraries in the first place? In the "checkout" step these are two different options (or am I misreading something?). In my case, the project that is triggered does NOT poll the SCM but is configured to only react on push notifications. So, this might be a different issue? Should I open a new bug report?  
 

  
 
 
 
 

 
 
 

 
 
 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.178297.1485467365000.9946.1565195581560%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57434  
 
 
  Unable to add or edit roles   
 

  
 
 
 
 

 
Change By: 
 Nick Johns  
 
 
Attachment: 
 image-2019-08-07-17-25-15-036.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.199247.1557753306000.9930.1565195160636%40Atlassian.JIRA.

[JIRA] (JENKINS-57434) Unable to add or edit roles

[nick.jo...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Johns updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-57434  
 
 
  Unable to add or edit roles   
 

  
 
 
 
 

 
Change By: 
 Nick Johns  
 
 
Attachment: 
 image-2019-08-07-17-25-17-212.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.199247.1557753306000.9938.1565195160742%40Atlassian.JIRA.

[JIRA] (JENKINS-49997) Pipeline Declarative post unsuccessful block

[jrh...@netconsonance.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jo Rhett commented on  JENKINS-49997  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Declarative post unsuccessful block
 

  
 
 
 
 

 
 It would be really awesome if the documentation at https://jenkins.io/doc/book/pipeline/syntax/#post-conditions mentioned which states unsuccessful includes, so that we don't have to search to find this issue   
 

  
 
 
 
 

 
 
 

 
 
 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.188994.1520441679000.9923.1565193660320%40Atlassian.JIRA.

[JIRA] (JENKINS-58643) CPS Mismatches on cpsScript.InvokeMethod

[ey...@jfrog.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Eyal Ben Moshe commented on  JENKINS-58643  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CPS Mismatches on cpsScript.InvokeMethod   
 

  
 
 
 
 

 
 Devin Nusbaum and Jesse Glick, Can we perhaps add support for an optional variable, which can be set by pipeline steps, to indicate the step name? This should resolve the "false mismatch warning" issue. Many pipelines out there are built and reply on the Artifactory pipeline APIs, so the solution we come up with cannot break the APIs. We'd be glad to create a PR, but we first need to know you're okay with this approach. Looking forward to your feedback. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 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.200910.1563983113000.9894.1565192220215%40Atlassian.JIRA.

[JIRA] (JENKINS-58851) Create VMs in specific range of Public IPs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sebastian Martinez created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58851  
 
 
  Create VMs in specific range of Public IPs   
 

  
 
 
 
 

 
Issue Type: 
  New Feature  
 
 
Assignee: 
 Azure DevOps  
 
 
Components: 
 azure-vm-agents-plugin  
 
 
Created: 
 2019-08-07 15:29  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Sebastian Martinez  
 

  
 
 
 
 

 
 It would be useful to be able to specify a range of IP of the VMs in AZURE vía this plugin.  As an option: Azure has the feature to implement something called "Public IP address prefix".  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent 

[JIRA] (JENKINS-58849) Logstash plugin: requires insecure "mask-passwords"

[ty...@tylercipriani.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tyler Cipriani reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58849  
 
 
  Logstash plugin: requires insecure "mask-passwords"   
 

  
 
 
 
 

 
Change By: 
 Tyler Cipriani  
 
 
Resolution: 
 Cannot Reproduce  
 
 
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.201164.1565189042000.9892.1565191800514%40Atlassian.JIRA.

[JIRA] (JENKINS-58849) Logstash plugin: requires insecure "mask-passwords"

[ty...@tylercipriani.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tyler Cipriani commented on  JENKINS-58849  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Logstash plugin: requires insecure "mask-passwords"   
 

  
 
 
 
 

 
 In the Jenkins UI "This plugin cannot be uninstalled it has one or more dependents Logstash" when I hover over "Uninstall" for "Mask Passwords 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.201164.1565189042000.9888.1565191560203%40Atlassian.JIRA.

[JIRA] (JENKINS-57126) Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH

[ray.kivi...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ray Kivisto closed an issue as Duplicate  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Closing, as per https://github.com/jenkinsci/ssh-slaves-plugin/pull/134#issuecomment-513543680  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-57126  
 
 
  Support alternative drive letters for Windows ssh agents using PowerShell/Win32-OpenSSH   
 

  
 
 
 
 

 
Change By: 
 Ray Kivisto  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Duplicate  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-58849) Logstash plugin: requires insecure "mask-passwords"

[bochenski.kuba+jenk...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Jakub Bochenski closed an issue as Cannot Reproduce  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 The dependency you link to is only used in test (as can be seen by it's scope). I fail to see why it would be a problem. Please reopen if I'm missing something  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-58849  
 
 
  Logstash plugin: requires insecure "mask-passwords"   
 

  
 
 
 
 

 
Change By: 
 Jakub Bochenski  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Cannot Reproduce  
 

  
 
 
 
 

 
 
 

 
 
 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.201164.1565189042000.9875.1565190900232%40Atlassian.JIRA.

[JIRA] (JENKINS-39874) Abilty to disable pipeline-replay in Job Configuration.

[b...@langfeld.me (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Ben Langfeld commented on  JENKINS-39874  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Abilty to disable pipeline-replay in Job Configuration.   
 

  
 
 
 
 

 
 I have users who do not have Job/Configure, cannot access the job configuration, but can use Replay. Is there some other permission which grants this? Should this ticket be re-opened?  
 

  
 
 
 
 

 
 
 

 
 
 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.176488.1479513265000.9867.1565190720317%40Atlassian.JIRA.

[JIRA] (JENKINS-58850) Steps from post actions are not visible when used with parallel stages

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Buicescu created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58850  
 
 
  Steps from post actions are not visible when used with parallel stages   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 image-2019-08-07-17-51-34-871.png, image-2019-08-07-17-51-57-772.png, log-parallel.txt, log-sequential.txt  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2019-08-07 15:02  
 
 
Environment: 
 EC2 node: Linux ip-172-31-39-47 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux   Jenkins ver. 2.176.2   Blue Ocean: 1.18.1 (all plugins are up to date)   Chrome: Version 75.0.3770.142 (Official Build) (64-bit)  
 
 
Labels: 
 blueocean blueocean-ui  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Alex Buicescu  
 

  
 
 
 
 

 
 I'm using declarative pipeline and the steps from the post actions are not visible when there are parallel stages inside stages directive, but they are shown when there are only sequential stages in jenkinsfile. The actions from post are executed because I can see them in the log file, but the steps are simply not visible. You can see from the following 2 jenkinsfiles that only in the 2nd one the echo "hi from post" step is visible 1) This jenkinsfile is not working properly (uses parallel stages) (see attachment log-parallel.txt for logs): 

 
 

[JIRA] (JENKINS-34545) Assigning roles is case sensitive, and it shouldn't be

[daniel.pa...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 D Pasto commented on  JENKINS-34545  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Assigning roles is case sensitive, and it shouldn't be   
 

  
 
 
 
 

 
 I verified the workaround of assigning the user multiple times to each role:  JoeUser, joeuser, Joeuser, JOEUSER It doesn't display right since the LDAP lookup doesn't like the duplication, and it wouldn't scale well, but it does work - I can login with the most common capitalization patterns and get the right permissions  
 

  
 
 
 
 

 
 
 

 
 
 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.170162.1462223259000.9839.1565189100512%40Atlassian.JIRA.

[JIRA] (JENKINS-58849) Logstash plugin: requires insecure "mask-passwords"

[ty...@tylercipriani.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Tyler Cipriani created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58849  
 
 
  Logstash plugin: requires insecure "mask-passwords"   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jakub Bochenski  
 
 
Components: 
 logstash-plugin, mask-passwords-plugin  
 
 
Created: 
 2019-08-07 14:44  
 
 
Labels: 
 security plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Tyler Cipriani  
 

  
 
 
 
 

 
 The mask-passwords plugin contains CVE-2019-10370 for which there is no released fix; however, the Logstash plugin depends on this plugin:   https://github.com/jenkinsci/logstash-plugin/blob/master/pom.xml#L162  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

[JIRA] (JENKINS-58843) Error 404 resource not found

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rui Oliveira updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58843  
 
 
  Error 404 resource not found   
 

  
 
 
 
 

 
Change By: 
 Rui Oliveira  
 

  
 
 
 
 

 
 Sometimes users complaint that when accessing jenkins an error happens 404 not found.This is the error from tomcat localhost access logs:172.25.1.123 - - [07/Aug/2019:10:21:16 +0100] "POST /j_acegi_security_check HTTP/1.1" 302 - 172.25.1.123 - - [07/Aug/2019:10:21:16 +0100] "GET /;jsessionid=8BD2593C17E0A692DCCE0EE1BF10A239 HTTP/1.1" 404 1047 This happened when upgraded to [Jenkins ver. 2.187.|https://jenkins.io/]  Users also say that after cleaning cache the problem stops but the next day trying to login again and the problem starts again.  
 

  
 
 
 
 

 
 
 

 
 
 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.201158.1565175731000.9805.1565187120403%40Atlassian.JIRA.

[JIRA] (JENKINS-58211) ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Mariusz Gronczewski commented on  JENKINS-58211  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ArtifactDeployer fails with java.lang.NoClassDefFoundError: Could not initialize class org.jruby.ext.posix.Linux64HeapFileStat   
 

  
 
 
 
 

 
 Still present in 2.187/1.2  
 

  
 
 
 
 

 
 
 

 
 
 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.200271.1561558166000.9798.1565187060458%40Atlassian.JIRA.

[JIRA] (JENKINS-58843) Error 404 resource not found

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rui Oliveira updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58843  
 
 
  Error 404 resource not found   
 

  
 
 
 
 

 
Change By: 
 Rui Oliveira  
 

  
 
 
 
 

 
 Sometimes users complaint that when accessing jenkins an error happens 404 not found.This is the error from tomcat localhost access logs:172.25.1.123 - - [07/Aug/2019:10:21:16 +0100] "POST /j_acegi_security_check HTTP/1.1" 302 -172.25.1.123 - - [07/Aug/2019:10:21:16 +0100] "GET /;jsessionid=8BD2593C17E0A692DCCE0EE1BF10A239 HTTP/1.1" 404 1047 This happened when upgraded to [Jenkins ver. 2.187.|https://jenkins.io/] Also now we have https working for jenkins with this conf in web.xml:  Protected Context /*CONFIDENTIAL      
 

  
 
 
 
 

 
 
 

 
 
 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.201158.1565175731000.9795.1565187060378%40Atlassian.JIRA.

[JIRA] (JENKINS-56989) Default pty to false for sshCommand

[erik-...@rieksen.net (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Erik-Jan Rieksen commented on  JENKINS-56989  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default pty to false for sshCommand   
 

  
 
 
 
 

 
 Naresh Rayapati with "remote.pty: true" added the build works as expected. Without pty true (after the latest plugin update) the build times out after 10 minutes (as configured) at sshCommand. Both the jenkins server and the SSH server to which is connected run Ubuntu.  

 

def remote = [:]
remote.name = 'ommitted'
remote.host = 'ommitted'
remote.user = 'ommitted'
remote.password = 'ommitted'
remote.allowAnyHosts = truepipeline {
 agent any
 options {
   timeout(time: 10)
   disableConcurrentBuilds()
 }
 stages {   stage('Clone repository') {
 steps {
   checkout scm
 }
   }   stage('Build') {
 when {
   anyOf {
 branch 'development'
 branch 'master'
   }
 }
 steps {
   echo 'Testing & Building...'
   sh 'mvn -B clean package'
 }
   }   stage('Build docker image') {
 when {
   anyOf {
 branch 'development'
 branch 'master'
   }
 } steps {
   echo 'Building docker image...'
   sh 'docker login -u ommitted'
   sh 'docker build -t="ommitted" .'
 }
   }   stage('Push docker image') {
 when {
   anyOf {
 branch 'development'
 branch 'master'
   }
 } steps {
   echo 'Pushing docker image...'
   sh 'docker push ommitted'
 }
   }   stage('Deploy') {
 when {
   anyOf {
 branch 'development'
 branch 'master'
   }
 }
 steps {
   echo 'Deploying...'
   sshCommand remote: remote, sudo: true, command: "sudo sh update.sh"
 }
   }
 }
}
 

 Jenkins log 

 

Executing command on ommitted[ommitted]: sudo sh update.sh sudo: true
Cancelling nested steps due to timeout
d997b761-0e4a-4707-a205-d71cc489b9bc
 

  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  

[JIRA] (JENKINS-56989) Default pty to false for sshCommand

[naresh.rayap...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Naresh Rayapati commented on  JENKINS-56989  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Default pty to false for sshCommand   
 

  
 
 
 
 

 
 Erik-Jan Rieksen Can you post a bit of your pipeline code?, pty: true is only required for few of the platforms/ssh-agents like SSH on Linux.  Note: pty: true is not an option for sshCommand but for the actual remote.   
 

  
 
 
 
 

 
 
 

 
 
 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.198683.1555059312000.9789.1565186100380%40Atlassian.JIRA.

[JIRA] (JENKINS-58848) Getting Message: Exception has been thrown by the target of an invocation message while running jobs through jenkins in remote machine

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Stalin Vanama created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58848  
 
 
  Getting Message: Exception has been thrown by the target of an invocation message while running jobs through jenkins in remote machine   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Daniel Gront  
 
 
Components: 
 hp-application-automation-tools-plugin  
 
 
Created: 
 2019-08-07 13:52  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Stalin Vanama  
 

  
 
 
 
 

 
 Getting Message: Exception has been thrown by the target of an invocation message while running jobs through jenkins in remote machine  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
  

[JIRA] (JENKINS-58846) Dependency-Check Trend chart doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58846  
 
 
  Dependency-Check Trend chart doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
Change By: 
 vassil marjunits  
 
 
Summary: 
 Dependency-Check Trend  graph  chart  doesn't appears on DSL pipelines jobs  
 

  
 
 
 
 

 
 Dependency-Check Trend  graph  chart  doesn't appears on DSL pipelines jobs As it works with freestyle jobs.!dsl-pipeline.png|thumbnail!    
 

  
 
 
 
 

 
 
 

 
 
 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.201161.1565179135000.9784.1565185440218%40Atlassian.JIRA.

[JIRA] (JENKINS-35229) Plugin manager Updates never completes

[julien.bred...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Julien Bréda commented on  JENKINS-35229  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Plugin manager Updates never completes   
 

  
 
 
 
 

 
 The use of checkUpdates or checkUpdatesServer depends on a configuration in /configureSecurity/ : Plugin Manager > Use browser for metadata download. When unchecked, checkUpdatesServer is used, which solved my problem.  
 

  
 
 
 
 

 
 
 

 
 
 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.170922.1464679741000.9767.1565184720978%40Atlassian.JIRA.

[JIRA] (JENKINS-27940) Consider using jUnit output from FitNesse

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 jaruzafa commented on  JENKINS-27940  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Consider using jUnit output from FitNesse   
 

  
 
 
 
 

 
 Starting Fitnesse-plugin 1.28 you have ** the capability to generate junit reports too  
 

  
 
 
 
 

 
 
 

 
 
 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.162136.142903045.9762.1565184720833%40Atlassian.JIRA.

[JIRA] (JENKINS-27940) Consider using jUnit output from FitNesse

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 jaruzafa closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-27940  
 
 
  Consider using jUnit output from FitNesse   
 

  
 
 
 
 

 
Change By: 
 jaruzafa  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-45719) Description for a pipeline run is not compatible and cannot be disabled

[thibaut.lelev...@myscript.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Thibaut LE LEVIER commented on  JENKINS-45719  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Description for a pipeline run is not compatible and cannot be disabled   
 

  
 
 
 
 

 
 Any update on this? It's also a need for us  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-40165) Please release new version fitnesse plugin( enable SSL needed)

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 jaruzafa closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed: Fitnesse-plugin 1.24  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-40165  
 
 
  Please release new version fitnesse plugin( enable SSL needed)   
 

  
 
 
 
 

 
Change By: 
 jaruzafa  
 
 
Status: 
 Open Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-41514) FitNesse Plugin should be usable in a Jenkinsfile

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 jaruzafa closed an issue as Fixed  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Fixed in 1.24  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-41514  
 
 
  FitNesse Plugin should be usable in a Jenkinsfile   
 

  
 
 
 
 

 
Change By: 
 jaruzafa  
 
 
Status: 
 In Progress Closed  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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

[JIRA] (JENKINS-58822) Failed to send out e-mail

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-58822  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to send out e-mail   
 

  
 
 
 
 

 
 You probably need to follow this https://support.google.com/accounts/answer/185833  
 

  
 
 
 
 

 
 
 

 
 
 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.201134.1565077475000.9704.1565182560270%40Atlassian.JIRA.

[JIRA] (JENKINS-58822) Failed to send out e-mail

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alex Earl commented on  JENKINS-58822  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Failed to send out e-mail   
 

  
 
 
 
 

 
 You need to determine why the authentication is failing. As I mentioned before, did you check the webpage that Google's mail server is sending in the exception?  
 

  
 
 
 
 

 
 
 

 
 
 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.201134.1565077475000.9688.1565182080580%40Atlassian.JIRA.

[JIRA] (JENKINS-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits edited a comment on  JENKINS-58846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
 My pipeline: pipeline {agent anyoptions  {  { ansiColor('xterm')  buildDiscarder(logRotator(numToKeepStr: '20'))  disableConcurrentBuilds()  timestamps()  }  tools  {  { jdk 'openjdk-11'  }stages{stage('Checkout some java source') {steps  {  { git url: 'https://github.com/bmuschko/whats-new-in-java-11.git', branch: 'master'  }  }stage('maven build') {steps  {  { sh 'mvn clean install -Dmaven.test.skip -X'  sh 'ls -alt'  sh 'ls -alt target'  }  }stage ('OWASP Dependency-Check Vulnerabilities') {steps  {  //See the additional arguments options https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html   {  dependencyCheck additionalArguments: '', odcInstallation: 'owasp-nexus'      dependencyCheckPublisher pattern: '**/dependency-check-report.xml'      sh 'ls -alt'  }  }}post {always  {  { //clean up job workspace  cleanWs()  }  }}  
 

  
 
 
 
 

 
 
 

 
 
 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.201161.1565179135000.9685.1565180280056%40Atlassian.JIRA.

[JIRA] (JENKINS-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits edited a comment on  JENKINS-58846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
 My pipeline:   pipeline { agent any options  {   ansiColor('xterm')   buildDiscarder(logRotator(numToKeepStr: '20'))   disableConcurrentBuilds()   timestamps()   }  tools  {   jdk 'openjdk-11'   }stages{ stage('Checkout some java source') { steps  {   git url: 'https://github.com/bmuschko/whats-new-in-java-11.git', branch: 'master'   }  }stage('maven build') { steps  {   sh 'mvn clean install -Dmaven.test.skip -X'   sh 'ls -alt'   sh 'ls -alt target'   }  } stage ('OWASP Dependency-Check Vulnerabilities') { steps  {   //See the additional arguments options https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html          dependencyCheck additionalArguments: '', odcInstallation: 'owasp-nexus'     dependencyCheckPublisher pattern: '**/dependency-check-report.xml'     sh 'ls -alt'   }  }} post { always  {   //clean up job workspace   cleanWs()   }  } }  
 

  
 
 
 
 

 
 
 

 
 
 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.201161.1565179135000.9684.1565179980140%40Atlassian.JIRA.

[JIRA] (JENKINS-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits commented on  JENKINS-58846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
 My pipeline: pipeline { agent any options  { ansiColor('xterm') buildDiscarder(logRotator(numToKeepStr: '20')) disableConcurrentBuilds() timestamps() } tools  { jdk 'openjdk-11' } stages{ stage('Checkout some java source') { steps  { git url: 'https://github.com/bmuschko/whats-new-in-java-11.git', branch: 'master' } } stage('maven build') { steps  { sh 'mvn clean install -Dmaven.test.skip -X' sh 'ls -alt' sh 'ls -alt target' } } stage ('OWASP Dependency-Check Vulnerabilities') { steps  { //See the additional arguments options https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html   dependencyCheck additionalArguments: '', odcInstallation: 'owasp-nexus'   dependencyCheckPublisher pattern: '**/dependency-check-report.xml'   sh 'ls -alt' } } } post { always  { //clean up job workspace cleanWs() } } }  
 

  
 
 
 
 

 
 
 

 
 
 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.201161.1565179135000.9682.1565179920084%40Atlassian.JIRA.

[JIRA] (JENKINS-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits edited a comment on  JENKINS-58846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
 My pipeline:  pipeline {agent anyoptions  {  { ansiColor('xterm')  buildDiscarder(logRotator(numToKeepStr: '20'))  disableConcurrentBuilds()  timestamps()  }  tools  {  { jdk 'openjdk-11'  }stages{stage('Checkout some java source') {steps  {  { git url: 'https://github.com/bmuschko/whats-new-in-java-11.git', branch: 'master'  }  }stage('maven build') {steps  {  { sh 'mvn clean install -Dmaven.test.skip -X'  sh 'ls -alt'  sh 'ls -alt target'  }  }stage ('OWASP Dependency-Check Vulnerabilities') {steps  {  { //See the additional arguments options https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html     dependencyCheck additionalArguments: '', odcInstallation: 'owasp-nexus'    dependencyCheckPublisher pattern: '**/dependency-check-report.xml'    sh 'ls -alt'  }  }}post {always  {  { //clean up job workspace  cleanWs()  }  }}  
 

  
 
 
 
 

 
 
 

 
 
 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.201161.1565179135000.9683.1565179920104%40Atlassian.JIRA.

[JIRA] (JENKINS-58847) After renaming project logs of runs prior to rename are not found

[m.win...@sap.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Markus Winter created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58847  
 
 
  After renaming project logs of runs prior to rename are not found   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jesse Glick  
 
 
Components: 
 pipeline-cloudwatch-logs-plugin  
 
 
Created: 
 2019-08-07 12:05  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Markus Winter  
 

  
 
 
 
 

 
 Without verifying this, I think if the project gets renamed or moved, the logs will no longer be found. Reason is that the logStreamNameBase is basically the projects fullName, that changes on rename or move. A solution would be to use the unique id plugin  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

   

[JIRA] (JENKINS-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58846  
 
 
  Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
Change By: 
 vassil marjunits  
 

  
 
 
 
 

 
 Dependency-Check Trend graph doesn't appears on DSL pipelines jobs As it works with freestyle jobs. !dsl-pipeline.png|thumbnail!    
 

  
 
 
 
 

 
 
 

 
 
 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.201161.1565179135000.9679.1565179381451%40Atlassian.JIRA.

[JIRA] (JENKINS-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58846  
 
 
  Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
Change By: 
 vassil marjunits  
 

  
 
 
 
 

 
 Dependency-Check Trend graph doesn't appears on DSL pipelines jobs Its  As it  works with freestyle jobs.   
 

  
 
 
 
 

 
 
 

 
 
 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.201161.1565179135000.9678.1565179381128%40Atlassian.JIRA.

[JIRA] (JENKINS-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits commented on  JENKINS-58846  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
 

 

pipeline {pipeline {    agent any    options {        ansiColor('xterm')        buildDiscarder(logRotator(numToKeepStr: '20'))        disableConcurrentBuilds()        timestamps()    }    tools {        jdk 'openjdk-11'     }
    stages{        stage('Checkout some java source') {            steps {                git url: 'https://github.com/bmuschko/whats-new-in-java-11.git', branch: 'master'            }        }        
        stage('maven build') {            steps {                    sh 'mvn clean install -Dmaven.test.skip -X'                    sh 'ls -alt'                    sh 'ls -alt target'                }            }        // Enable OWASP Dependecy Vulnerabilities Check        stage ('OWASP Dependency-Check Vulnerabilities') {            steps {                //See the additional arguments options https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html dependencyCheck additionalArguments: '', odcInstallation: 'owasp-nexus'              dependencyCheckPublisher pattern: '**/dependency-check-report.xml'              sh 'ls -alt'            }        }
    }        post {    always {        //clean up job workspace        cleanWs()    }  } }
 

  
 

  
 
 
 
 

 
 
 

 
 
 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-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58846  
 
 
  Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
Change By: 
 vassil marjunits  
 
 
Comment: 
 {code:java}pipeline {pipeline {    agent any    options {        ansiColor('xterm')        buildDiscarder(logRotator(numToKeepStr: '20'))        disableConcurrentBuilds()        timestamps()    }    tools {        jdk 'openjdk-11'     }    stages{        stage('Checkout some java source') {            steps {                git url: 'https://github.com/bmuschko/whats-new-in-java-11.git', branch: 'master'            }        }                stage('maven build') {            steps {                    sh 'mvn clean install -Dmaven.test.skip -X'                    sh 'ls -alt'                    sh 'ls -alt target'                }            }        // Enable OWASP Dependecy Vulnerabilities Check        stage ('OWASP Dependency-Check Vulnerabilities') {            steps {                //See the additional arguments options https://jeremylong.github.io/DependencyCheck/dependency-check-cli/arguments.html dependencyCheck additionalArguments: '', odcInstallation: 'owasp-nexus'               dependencyCheckPublisher pattern: '**/dependency-check-report.xml'               sh 'ls -alt'            }        }    }        post {    always {        //clean up job workspace        cleanWs()    }  } }{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 

[JIRA] (JENKINS-58846) Dependency-Check Trend graph doesn't appears on DSL pipelines jobs

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 vassil marjunits created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58846  
 
 
  Dependency-Check Trend graph doesn't appears on DSL pipelines jobs   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Attachments: 
 dsl-pipeline.png  
 
 
Components: 
 dependency-check-jenkins-plugin  
 
 
Created: 
 2019-08-07 11:58  
 
 
Environment: 
 OWASP Dependency-Check Plugin 5.0.2  Jenkins ver. 2.176.2 on Linux Ubuntu 1804   
 
 
Labels: 
 plugin pipeline  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 vassil marjunits  
 

  
 
 
 
 

 
 Dependency-Check Trend graph doesn't appears on DSL pipelines jobs Its works with freestyle jobs.    
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
   

[JIRA] (JENKINS-58845) Jenkins Docker Desktop git ssh temporary credentials file bad permissions

[fabian.kopatsc...@yahoo.de (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Fabian Kopatschek created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58845  
 
 
  Jenkins Docker Desktop git ssh temporary credentials file bad permissions   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 credentials-binding-plugin  
 
 
Created: 
 2019-08-07 11:33  
 
 
Environment: 
 Windows 10 + Docker Desktop  jenkins/jenkins docker image  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Fabian Kopatschek  
 

  
 
 
 
 

 
 Hi, i have the following error message when trying to access my gitlab server via ssh from my jenkins:   

 

stdout: 
stderr: @@@
@ WARNING: UNPROTECTED PRIVATE KEY FILE!  @
@@@
Permissions 0555 for '/var/jenkins_home/caches/git-0aa16db65c903d3ced737f801b217112@tmp/jenkins-gitclient-ssh2425211278542515051.key' are too open.
It is required that your private key files are NOT accessible by others.
This private key will be ignored.
Load key "/var/jenkins_home/caches/git-0aa16db65c903d3ced737f801b217112@tmp/jenkins-gitclient-ssh2425211278542515051.key": bad permissions
Permission denied (publickey).
fatal: Could not read from remote repository.

 

 My environment is the following: Host System: Windows 10 Docker Desktop 2.1.0 with Linux based containers Jenkins Docker Container: jenkins/jenkins and jenkins/jenkins:lts   I've a similar setup running with a linux for Docker and there isn't the same problem. For testing purposes i've installed the latest beta version (3.0.0-beta10) of the 

[JIRA] (JENKINS-58844) Post view creation illegal null pointer

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Yash Bagarka created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58844  
 
 
  Post view creation illegal null pointer
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 vjuranek  
 
 
Components: 
 groovy-plugin, nested-view-plugin  
 
 
Created: 
 2019-08-07 11:25  
 
 
Environment: 
 DEV  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Yash Bagarka  
 

  
 
 
 
 

 
 Hi, Getting below illegal exception while accessing the views created by Groovy.   

 

org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/hudson/model/View/index.jelly:42:43:  org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/lib/hudson/projectView.jelly:67:24:  java.lang.NullPointerExceptionorg.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/hudson/model/View/index.jelly:42:43:  org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/war/WEB-INF/lib/jenkins-core-2.176.2.jar!/lib/hudson/projectView.jelly:67:24:  java.lang.NullPointerException at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at 

[JIRA] (JENKINS-58843) Error 404 resource not found

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Rui Oliveira created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58843  
 
 
  Error 404 resource not found   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Félix Belzunce Arcos  
 
 
Components: 
 active-directory-plugin  
 
 
Created: 
 2019-08-07 11:02  
 
 
Environment: 
 Windows  
 
 
Labels: 
 404 secutiry HTTPS  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Rui Oliveira  
 

  
 
 
 
 

 
 Sometimes users complaint that when accessing jenkins an error happens 404 not found. This is the error from tomcat localhost access logs: 172.25.1.123 - - [07/Aug/2019:10:21:16 +0100] "POST /j_acegi_security_check HTTP/1.1" 302 - 172.25.1.123 - - [07/Aug/2019:10:21:16 +0100] "GET /;jsessionid=8BD2593C17E0A692DCCE0EE1BF10A239 HTTP/1.1" 404 1047   This happened when upgraded to Jenkins ver. 2.187. Also now we have https working for jenkins with this conf in web.xml:  Protected Context /*CONFIDENTIAL        
 

  
 
 
 
 

 
 
 

 
 
 Add 

[JIRA] (JENKINS-58842) Error assuming IAM role in Jenkins (es_ES)

[y...@diegomunozbeltran.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Diego Muñoz created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58842  
 
 
  Error assuming IAM role in Jenkins (es_ES)   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Jan Roehrich  
 
 
Components: 
 amazon-ecs-plugin, aws-credentials-plugin  
 
 
Created: 
 2019-08-07 10:58  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Diego Muñoz  
 

  
 
 
 
 

 
 While using amazon-ecs-plugin and aws-credentials-plugin, we are trying to assume an IAM role to describe ECS clusters. We noticed this in logs: 

 

Exception searching clusters for credentials=Test, regionName=eu-west-1:com.amazonaws.services.securitytoken.model.AWSSecurityTokenServiceException: 1 validation error detected: Value 'Jenkins ' at 'roleSessionName' failed to satisfy constraint: Member must satisfy regular _expression_ pattern: [\w+=,.@-]* (Service: AWSSecurityTokenService; Status Code: 400; Error Code: ValidationError; Request ID: 20e28d0c-b8ff-11e9-8b33-4d7def127bc0)
 

 Looks like roleSessionName is wrong, as it includes a whitespace which breaks the assumeRole action. It doesn't happen in other languages. Forcing Jenkins to use en_GB locales (Using locale plugin for example) fixes it. This is the Jenkins file which contains the bad property  
 

  
 
 
 
 

 
 
 

[JIRA] (JENKINS-58789) Timestamps disappear without any reason inside podTemplate

[sergio.merin...@gmail.com (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Sergio Merino updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58789  
 
 
  Timestamps disappear without any reason inside podTemplate   
 

  
 
 
 
 

 
Change By: 
 Sergio Merino  
 
 
Comment: 
 As workaround, adding "timestamps{}" inside podTemplate works. But I was expecting, that configuring it at the higher level would be enough  
 

  
 
 
 
 

 
 
 

 
 
 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.201099.1564764393000.9660.1565173380137%40Atlassian.JIRA.

[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds

[rav...@bluewin.ch (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Marc Würth commented on  JENKINS-58826  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: "Aggregated Analysis Results" does not get updated after a few dozen builds   
 

  
 
 
 
 

 
 Ulli Hafner It is a multibranch pipeline project, so I found the file for the last successful here: /var/lib/jenkins/jobs/PROJECT/branches/trunk/builds/121 (the newest build) 

 
# grep io.jenkins.plugins.analysis.core.model build.xml















 

 I even compared the file with its siblings from previous builds (before the bug) and other branches (working). I haven't found significant differences, just updated references and such.    
 

  
 
 
 
 

 
 
 

 
 
 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.201139.1565095677000.9658.1565173020143%40Atlassian.JIRA.

[JIRA] (JENKINS-58838) Browsers not launching through Jenkins

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Martinez assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58838  
 
 
  Browsers not launching through Jenkins   
 

  
 
 
 
 

 
Change By: 
 Victor Martinez  
 
 
Assignee: 
 Victor Martinez  
 

  
 
 
 
 

 
 
 

 
 
 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.201153.1565154142000.9656.1565172601562%40Atlassian.JIRA.

[JIRA] (JENKINS-58838) Browsers not launching through Jenkins

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Martinez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58838  
 
 
  Browsers not launching through Jenkins   
 

  
 
 
 
 

 
Change By: 
 Victor Martinez  
 
 
Component/s: 
 jenkinslint-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.201153.1565154142000.9652.1565172601295%40Atlassian.JIRA.

[JIRA] (JENKINS-58838) Browsers not launching through Jenkins

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

Title: Message Title


 
 
 
 

 
 
 

 
   
 Victor Martinez updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58838  
 
 
  Browsers not launching through Jenkins   
 

  
 
 
 
 

 
Change By: 
 Victor Martinez  
 
 
Priority: 
 Major Minor  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

  
 

   





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