[JIRA] (JENKINS-55103) Oops after update to 2.150.1 LTS on main page
Title: Message Title Florian Eidenhammer updated an issue Jenkins / JENKINS-55103 Oops after update to 2.150.1 LTS on main page Change By: Florian Eidenhammer Component/s: matrix-project-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55131) CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty
Title: Message Title Daniel Beck commented on JENKINS-55131 Re: CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty Depending on what project it is, the decision to discard plugin data may be very different, so this gives admins an opportunity to restore it. The presentation isn't ideal I think (personally I would prefer grouping by the kind of data, rather than the project, to be able to easily dismiss trivial things like disk usage metadata), but I'm not sure there's a great option working for everyone. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50368) Allow status of last finished build
Title: Message Title Thomas Döring assigned an issue to Thomas Döring Jenkins / JENKINS-50368 Allow status of last finished build Change By: Thomas Döring Assignee: Antonio Muñiz Thomas Döring Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55136) Log an error when ssh private key is empty
Title: Message Title Vince Murphy commented on JENKINS-55136 Re: Log an error when ssh private key is empty After reading the java code I looked through my logs for this log message and did eventually find it. ``` SECURITY-440: Migrating FileOnMasterPrivateKeySource to DirectEntryPrivateKeySource ``` But I don't think that is enough information in this context (ie the log file, with no knowledge of the code). What does it mean, anyway? The private key has been migrated for me? (it wasn't - is that a separate issue to look at?) I should take steps to migrate the private key? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55136) Log an error when ssh private key is empty
Title: Message Title Vince Murphy commented on JENKINS-55136 Re: Log an error when ssh private key is empty Forgot to add - the workaround for us was: Jenkins->Credentials->click on affected credential id->Update Paste the private key contents into the field provided Update the description so it no longer mentions file:/var/lib/jenkins/.ssh/jenkins Save Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55136) Log an error when ssh private key is empty
Title: Message Title
Vince Murphy created an issue
Jenkins / JENKINS-55136
Log an error when ssh private key is empty
Issue Type:
Improvement
Assignee:
Devin Nusbaum
Components:
ssh-credentials-plugin
Created:
2018-12-12 06:18
Environment:
jenkins 2.150.1 ssh-credentials-plugin 1.14 ssh-slaves-plugin 1.29.1 java /usr/lib/jvm/java-8-oracle/jre/lib/amd64 We have one master, with a handful of SSH slaves. All running Debian Linux, of various versions (wheezy on master, jessie & stretch on slaves).
Priority:
Minor
Reporter:
Vince Murphy
This is fallout from the fix for SECURITY-440 (see https://jenkins.io/security/advisory/2018-06-25/ ) We upgraded to ensure that fix was installed back in June. For some reason it did not affect us until after upgrading to ssh-slaves 1.29.1 (from 1.28) We used to have the SSH private key that the master uses to log into the slaves, in $JENKINS_HOME/.ssh/jenkins - ie. not one of the names that jenkins searches for by default. When the master tries to connect to the client, it fails and there's no clue given as to why. This is the log I get when I try to reconnect to a node affected by this issue: ``` SSHLauncher{host='fiasco', port=22, credentialsId='', jvmOptions='', javaPath='/usr/lib/jvm/java-8-openjdk-amd64/bin/java', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.KnownHostsFileKeyVerificationStrategy, tcpNoDelay=true, trackCredentials=true} [12/11/18 10:33:49] [SSH] Opening SSH connection to fiasco:22. [12/11/18 10:33:49] [SSH] SSH host key matches key in Known Hosts file. Connection will be allowed. [12/11/18 10:33:49] [SSH] Authentication failed. Authentication failed. [12/11/18 10:33:49] Launch fai
[JIRA] (JENKINS-55135) Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Title: Message Title
Alan Uthoff updated an issue
Jenkins / JENKINS-55135
Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Change By:
Alan Uthoff
Note: I have a windows 10 build node hooked up to the same Jenkins server over ssh and it works fine and connects without any issuesThe Mac node where working before I update Jenkins and the ssh-slaves-plugin but, I am not sure the version number that caused the nodes to stop workingI can scp a file from the jenkins computer from to the mac slaves from the command line manual with no issueError Log Below:SSHLauncher{host=' 242 141 . 231 128 . 8 110 . 254 86 ', port=22, credentialsId='d6a51f71-c020-4c49-af41-71d00db7e235', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=false, trackCredentials=true}[12/11/18 23:29:57] [SSH] Opening SSH connection to 242 141 . 231 128 . 8 110 . 254 86 :22.[12/11/18 23:29:57] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.[12/11/18 23:29:58] [SSH] Authentication successful.[12/11/18 23:29:58] [SSH] The remote user's environment is:BASH=/bin/bashBASH_ARGC=()BASH_ARGV=()BASH_EXECUTION_STRING=setBASH_LINENO=()BASH_SOURCE=()BASH_VERSINFO=([0]="3" [1]="2" [2]="57" [3]="1" [4]="release" [5]="x86_64-apple-darwin18")BASH_VERSION='3.2.57(1)-release'DIRSTACK=()EUID=501GROUPS=()HOME=/Users/jenkinsHOSTNAME=Swordpoint-Mac-Mini.localHOSTTYPE=x86_64IFS=$' \t\n'LOGNAME=jenkinsMACHTYPE=x86_64-apple-darwin18MAIL=/var/mail/jenkinsOPTERR=1OPTIND=1OSTYPE=darwin18PATH=/usr/bin:/bin:/usr/sbin:/sbinPPID=19839PS4='+ 'PWD=/Users/jenkinsSHELL=/bin/bashSHELLOPTS=braceexpand:hashall:interactive-commentsSHLVL=1SSH_CLIENT='242.231.8.254 46374 22'SSH_CONNECTION='242.231.8.254 46374 10.10.1.234 22'TERM=dumbTMPDIR=/var/folders/r5/b9fff5ts2dq5yvhfhyfdv7dmgn/T/UID=501USER=jenkins_=bash[12/11/18 23:29:58] [SSH] Checking java version of /Users/jenkins/.jenkins/jdk/bin/javaCouldn't figure out the Java version of /Users/jenkins/.jenkins/jdk/bin/javabash: /Users/jenkins/.jenkins/jdk/bin/java: No such file or directory[12/11/18 23:29:58] [SSH] Checking java version of java[12/11/18 23:29:59] [SSH] java -version returned 1.8.0_181.[12/11/18 23:29:59] [SSH] Starting sftp client.[12/11/18 23:29:59] [SSH] Copying latest remoting.jar...java.io.IOException: Could not copy remoting.jar into '/Users/jenkins/.jenkins' on agent at hudson.plugins.sshslaves.SSHLauncher.copyAgentJar(SSHLauncher.java:1109) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:128) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:866) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:833) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.Thre
[JIRA] (JENKINS-55135) Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Title: Message Title
Alan Uthoff updated an issue
Jenkins / JENKINS-55135
Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Change By:
Alan Uthoff
Note: I have a windows 10 build node hooked up to the same Jenkins server over ssh and it works fine and connects without any issues The Mac node where working before I update Jenkins and the ssh-slaves-plugin but, I am not sure the version number that caused the nodes to stop working I can scp a file from the jenkins computer from to the mac slaves from the command line manual with no issue Error Log Below:SSHLauncher{host='242.231.8.254', port=22, credentialsId='d6a51f71-c020-4c49-af41-71d00db7e235', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=false, trackCredentials=true}[12/11/18 23:29:57] [SSH] Opening SSH connection to 242.231.8.254:22.[12/11/18 23:29:57] [SSH] WARNING: SSH Host Keys are not being verified. Man-in-the-middle attacks may be possible against this connection.[12/11/18 23:29:58] [SSH] Authentication successful.[12/11/18 23:29:58] [SSH] The remote user's environment is:BASH=/bin/bashBASH_ARGC=()BASH_ARGV=()BASH_EXECUTION_STRING=setBASH_LINENO=()BASH_SOURCE=()BASH_VERSINFO=([0]="3" [1]="2" [2]="57" [3]="1" [4]="release" [5]="x86_64-apple-darwin18")BASH_VERSION='3.2.57(1)-release'DIRSTACK=()EUID=501GROUPS=()HOME=/Users/jenkinsHOSTNAME=Swordpoint-Mac-Mini.localHOSTTYPE=x86_64IFS=$' \t\n'LOGNAME=jenkinsMACHTYPE=x86_64-apple-darwin18MAIL=/var/mail/jenkinsOPTERR=1OPTIND=1OSTYPE=darwin18PATH=/usr/bin:/bin:/usr/sbin:/sbinPPID=19839PS4='+ 'PWD=/Users/jenkinsSHELL=/bin/bashSHELLOPTS=braceexpand:hashall:interactive-commentsSHLVL=1SSH_CLIENT='242.231.8.254 46374 22'SSH_CONNECTION='242.231.8.254 46374 10.10.1.234 22'TERM=dumbTMPDIR=/var/folders/r5/b9fff5ts2dq5yvhfhyfdv7dmgn/T/UID=501USER=jenkins_=bash[12/11/18 23:29:58] [SSH] Checking java version of /Users/jenkins/.jenkins/jdk/bin/javaCouldn't figure out the Java version of /Users/jenkins/.jenkins/jdk/bin/javabash: /Users/jenkins/.jenkins/jdk/bin/java: No such file or directory[12/11/18 23:29:58] [SSH] Checking java version of java[12/11/18 23:29:59] [SSH] java -version returned 1.8.0_181.[12/11/18 23:29:59] [SSH] Starting sftp client.[12/11/18 23:29:59] [SSH] Copying latest remoting.jar...java.io.IOException: Could not copy remoting.jar into '/Users/jenkins/.jenkins' on agent at hudson.plugins.sshslaves.SSHLauncher.copyAgentJar(SSHLauncher.java:1109) at hudson.plugins.sshslaves.SSHLauncher.access$400(SSHLauncher.java:128) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:866) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:833) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecuto
[JIRA] (JENKINS-55135) Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Title: Message Title Alan Uthoff updated an issue Jenkins / JENKINS-55135 Can Not Connect Mac Slave Over SSH - error copying remoting.jar. Change By: Alan Uthoff Environment: Jenkins LTS 2.150.1 : running on Ubuntu Server 18.4 LTS : OpenJDK 1.8.0_191-8u191-b12-0ubuntu0.18.04.1-b12 SSH Slaves Plugin 1.29.1Mac SlavesOne running Mac 10.13.6java version "1.8.0_181"Java(TM) SE Runtime Environment (build 1.8.0_181-b13)Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)One running Mac 10.14java version "1.8.0_181"Java(TM) SE Runtime Environment (build 1.8.0_181-b13)Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)One running Mac 10.14 Java java version "11.0.1" 2018-10-16 LTSJava(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55135) Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Title: Message Title
Alan Uthoff created an issue
Jenkins / JENKINS-55135
Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Issue Type:
Bug
Assignee:
Ivan Fernandez Calvo
Components:
ssh-slaves-plugin
Created:
2018-12-12 06:02
Environment:
Jenkins LTS 2.150.1 : running on Ubuntu 18.0 : OpenJDK 1.8.0_191-8u191-b12-0ubuntu0.18.04.1-b12 SSH Slaves Plugin 1.29.1 Mac Slaves One running Mac 10.13.6 java version "1.8.0_181" Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) One running Mac 10.14 java version "1.8.0_181" Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode) One running Mac 10.14 Java java version "11.0.1" 2018-10-16 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
Priority:
Major
Reporter:
Alan Uthoff
Note: I have a windows 10 build node hooked up to the same Jenkins server over ssh and it works fine and connects without any issues The Mac node where working before I update Jenkins and the ssh-slaves-plugin but, I am not sure the version number that caused the nodes to stop working Error Log Below: SSHLauncher {host='242.231.8.254', port=22, credentialsId='d6a51f71-c020-4c49-af41-71d00db7e235', jvmOptions='', javaPath='', prefixStartSlaveCmd='', suffixStartSlaveCmd='', launchTimeoutSeconds=210, maxNumRetries=10, retryWaitTime=15, sshHostKeyVerificationStrategy=hudson.plugins.sshslaves.verifiers.NonVerifyingKeyVerificationStrategy, tcpNoDelay=false, trackCredentials=true} [12/11/18 23:29:57] [SSH] Opening SSH connection to 242.231.8.254:22. [12/11/18 23:29:57] [SSH] WARNING: SSH Host Keys are not being verified.
[JIRA] (JENKINS-55135) Can Not Connect Mac Slave Over SSH - error copying remoting.jar.
Title: Message Title Alan Uthoff updated an issue Jenkins / JENKINS-55135 Can Not Connect Mac Slave Over SSH - error copying remoting.jar. Change By: Alan Uthoff Environment: Jenkins LTS 2.150.1 : running on Ubuntu 18. 0 4 LTS : OpenJDK 1.8.0_191-8u191-b12-0ubuntu0.18.04.1-b12 SSH Slaves Plugin 1.29.1Mac SlavesOne running Mac 10.13.6java version "1.8.0_181"Java(TM) SE Runtime Environment (build 1.8.0_181-b13)Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)One running Mac 10.14java version "1.8.0_181"Java(TM) SE Runtime Environment (build 1.8.0_181-b13)Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)One running Mac 10.14 Java java version "11.0.1" 2018-10-16 LTSJava(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS)Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55124) Use Jenkins Credentials for Performance Center username/password
Title: Message Title Daniel Gront updated an issue Jenkins / JENKINS-55124 Use Jenkins Credentials for Performance Center username/password Change By: Daniel Gront Labels: PerformanceCenter Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55124) Use Jenkins Credentials for Performance Center username/password
Title: Message Title Daniel Gront assigned an issue to Daniel Danan Jenkins / JENKINS-55124 Use Jenkins Credentials for Performance Center username/password Change By: Daniel Gront Assignee: Daniel Gront Danan Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55124) Use Jenkins Credentials for Performance Center username/password
Title: Message Title Daniel Gront commented on JENKINS-55124 Re: Use Jenkins Credentials for Performance Center username/password Daniel Danan, in v5.6 PC is using credentials, am I wrong? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54881) Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration
Title: Message Title Vishal Agrawal edited a comment on JENKINS-54881 Re: Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration Update - my Jenkins' (2.150) job build just finished and unfortunately the stash PR still show the following - *[✓ BUILD SUCCESS]( PLEASE SET JENKINS ROOT URL FROM GLOBAL CONFIGURATION job/* The configuration file looks to be correct and has globalConfig section with Jenkins URL. Hello Jakub,Your fix seems to have updated the job config.xml and reverted the to previous values correctly.Thanks a ton for your help!Vishal Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54881) Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration
Title: Message Title Vishal Agrawal edited a comment on JENKINS-54881 Re: Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration Update - my Jenkins' (2.150) job build just finished and unfortunately the stash PR still show the following - ` *[✓ BUILD SUCCESS]( PLEASE SET JENKINS ROOT URL FROM GLOBAL CONFIGURATION job/* ` Hello Jakub,Your fix seems to have updated the job config.xml and reverted the to previous values correctly.Thanks a ton for your help!Vishal Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54881) Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration
Title: Message Title Vishal Agrawal edited a comment on JENKINS-54881 Re: Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration Update - my Jenkins' (2.150) job build just finished and unfortunately the stash PR still show the following - ```*[✓ BUILD SUCCESS]( PLEASE SET JENKINS ROOT URL FROM GLOBAL CONFIGURATION job/*``` Hello Jakub,Your fix seems to have updated the job config.xml and reverted the to previous values correctly.Thanks a ton for your help!Vishal Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54881) Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration
Title: Message Title Vishal Agrawal edited a comment on JENKINS-54881 Re: Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration Update - my Jenkins' (2.150) job build just finished and unfortunately the stash PR still show the following - ` `` *[✓ BUILD SUCCESS]( PLEASE SET JENKINS ROOT URL FROM GLOBAL CONFIGURATION job/* ` `` Hello Jakub,Your fix seems to have updated the job config.xml and reverted the to previous values correctly.Thanks a ton for your help!Vishal Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54881) Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration
Title: Message Title Vishal Agrawal commented on JENKINS-54881 Re: Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration Hello Jakub, Your fix seems to have updated the job config.xml and reverted the to previous values correctly. Thanks a ton for your help! Vishal Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55092) linter for Jenkinsfile doesn't detect misspelled parameter names
Title: Message Title
Dylan Nicholson edited a comment on JENKINS-55092
Re: linter for Jenkinsfile doesn't detect misspelled parameter names
``` {{ return sh(scrip: "./myScript.sh", returnStatus: true) != 0 ``` }} Doesn't detect that "scrip" is misspelled.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55092) linter for Jenkinsfile doesn't detect misspelled parameter names
Title: Message Title Dylan Nicholson commented on JENKINS-55092 Re: linter for Jenkinsfile doesn't detect misspelled parameter names ```return sh(scrip: "./myScript.sh", returnStatus: true) != 0``` Doesn't detect that "scrip" is misspelled. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55131) CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty
Title: Message Title Josh Soref commented on JENKINS-55131 Re: CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty I'm wondering if it makes sense to report the same class multiple times. I understand that it is in fact in the project multiple times, but I question the value of that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51998) Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller
Title: Message Title Samuel Gabriel commented on JENKINS-51998 Re: Pipeline serialization fails on Java 11: java.lang.NoClassDefFoundError: Could not initialize class org.jboss.marshalling.river.RiverMarshaller Oleg Nenashev Thank you Oleg will check it out. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55134) InputAction No page found 'sidepanel.jelly' for class
Title: Message Title Bryce McHugh created an issue Jenkins / JENKINS-55134 InputAction No page found 'sidepanel.jelly' for class Issue Type: Bug Assignee: Unassigned Components: pipeline-input-step-plugin Created: 2018-12-12 01:21 Environment: Jenkins ver. 2.138.2 pipeline-input-step-plugin 2.8 workflow-api 2.32 workflow-step-api 2.16 workflow-support 2.22 Priority: Minor Reporter: Bryce McHugh Clicking the Input link in a job after a Jenkins restart is causing this stack trace. org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/plugins/pipeline-input-step/WEB-INF/lib/pipeline-input-step.jar!/org/jenkinsci/plugins/workflow/support/steps/input/InputAction/index.jelly:7:57: No page found 'sidepanel.jelly' for class org.jenkinsci.plugins.workflow.support.steps.input.InputAction at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:124) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) 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 org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at
[JIRA] (JENKINS-55133) Debian Buster private keys rejected for ssh agents
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-55133
Debian Buster private keys rejected for ssh agents
Change By:
Mark Waite
Summary:
Debian Buster ("testing") private keys rejected for ssh agents
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55133) Debian Buster ("testing") private keys rejected for ssh agents
Title: Message Title
Mark Waite created an issue
Jenkins / JENKINS-55133
Debian Buster ("testing") private keys rejected for ssh agents
Issue Type:
Bug
Assignee:
Ivan Fernandez Calvo
Components:
ssh-slaves-plugin
Created:
2018-12-11 23:35
Environment:
Jenkins 2.150.1 ssh-slaves 1.29.1 Docker image from my docker-lfs repository
Priority:
Minor
Reporter:
Mark Waite
The ssh-slaves plugin won't connect a Debian Buster ("testing") agent using a private key generated on Debian Buster. Debian Buster will be Debian 10 when released in Q1 2019 or Q2 2019. It will connect to a Debian Buster agent using a private key generated on Ubuntu 16 or Debian 9, but not with a key generated on Debian Buster. The same problem exists for ed25519 private keys and for rsa private keys. The message is Unknown Cipher: aes256-ctr and the stack trace reported by the ssh-slaves plugin is:
[12/11/18 16:26:08] [SSH] SSH host key matches key seen previously for this host. Connection will be allowed.
ERROR: SSH authentication failed
java.lang.IllegalArgumentException: Unknown Cipher: aes256-ctr
at com.trilead.ssh2.signature.OpenSshCertificateDecoder$SshCipher.getInstance(OpenSshCertificateDecoder.java:207)
at com.trilead.ssh2.signature.OpenSshCertificateDecoder.createKeyPair(OpenSshCertificateDecoder.java:77)
at com.trilead.ssh2.crypto.PEMDecoder.decodeKeyPair(PEMDecoder.java:493)
at com.trilead.ssh2.auth.AuthenticationManager.authenticatePublicKey(AuthenticationManager.java:225)
at com.trilead.ssh2.Connection.authenticateWithPublicKey(Connection.java:483)
at com.cloudbees.jenkins.plugins.sshcredentials.impl.Tr
[JIRA] (JENKINS-54199) Error loading Blue Ocean for Project
Title: Message Title Andrei Muresianu commented on JENKINS-54199 Re: Error loading Blue Ocean for Project +1 [Error] Error fetching page – TypeError: undefined is not an object (evaluating 'result.toLowerCase')[Error] Error fetching page – TypeError: undefined is not an object (evaluating 'result.toLowerCase')TypeError: undefined is not an object (evaluating 'result.toLowerCase')getI18nTitle — blueocean-core-js.js:54379render — blueocean-core-js.js:53687_renderValidatedComponentWithoutOwnerOrContext — jenkins-design-language.js:49621_renderValidatedComponent — jenkins-design-language.js:49644performInitialMount — jenkins-design-language.js:49184mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420mountChildren — jenkins-design-language.js:54382_createInitialChildren — jenkins-design-language.js:50508mountComponent — jenkins-design-language.js:50327mountComponent — jenkins-design-language.js:55420performInitialMount — jenkins-design-language.js:49193mountComponent — jenkins-design-language.js:49080mountComponent — jenkins-design-language.js:55420updateChildren — jenkins-design-language.js:48743_reconcilerUpdateChildren — jenkins-design-language.js:54357_updateChildren — jenkins-design-language.js:54456updateChildren — jenkins-design-language.js:54443_updateDOMChildren — jenkins-design-language.js:50747updateComponent — jenkins-design-language.js:50565receiveComponent — jenkins-design-language.js:50527receiveComponent — jenkins-design-language.js:55499updateChildren — jenkins-design-language.js:48731_reconcilerUpdateChildren — jenkins-design-language.js:54357_updateChildren — jenkins-design-language.js:54456updateChildren — jenkins-design-language.js:54443_updateDOMChildren — jenkins-design-language.js:50747updateComponent — jenkins-design-language.js:50565receiveComponent — jenkins-design-language.js:50527receiveComponent — jenkins-design-language.js:55499_updateRenderedComponent — jenkins-design-language.js
[JIRA] (JENKINS-54199) Error loading Blue Ocean for Project
Title: Message Title Andrei Muresianu updated an issue Jenkins / JENKINS-54199 Error loading Blue Ocean for Project Change By: Andrei Muresianu Attachment: Screenshot 2018-12-11 at 22.30.27.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title
Manuel Cardenas edited a comment on JENKINS-55070
Re: "Jenkins.instance is missing" error when restarting Jenkins
[~danielbeck] , we have seen this issue in a non windows installation, Centos 7.x * OpenJDK 64-Bit Server VM 25.161-b14 The complete context: We are upgrading Jenkins from 2.138.3.1 to 2.138.4.3 using a war file. Once that we use the new war file, the service is not able to start. We can see the trace below. {code:java}Dec 11, 2018 3:22:10 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /login java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) ... ec Dec 11, 2018 3:22:42 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /tcpSlaveAgentListener/ java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:36) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:58) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:531) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at org.eclipse.jetty.util.t
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title
Manuel Cardenas edited a comment on JENKINS-55070
Re: "Jenkins.instance is missing" error when restarting Jenkins
[~danielbeck] , we have seen this issue in a non windows installation, Centos 7.x * OpenJDK 64-Bit Server VM 25.161-b14 {code:java}Dec 11, 2018 3:22:10 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /login java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) ...ec 11, 2018 3:22:42 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /tcpSlaveAgentListener/ java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:36) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:58) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:531) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:168) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:126) at org.eclipse.jetty.util.thread.Reserved
[JIRA] (JENKINS-55070) "Jenkins.instance is missing" error when restarting Jenkins
Title: Message Title Manuel Cardenas commented on JENKINS-55070 Re: "Jenkins.instance is missing" error when restarting Jenkins Daniel Beck , we have seen this issue in a non windows installation, Centos 7.x Dec 11, 2018 3:22:10 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /login java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) ... ec 11, 2018 3:22:42 PM org.eclipse.jetty.server.HttpChannel handleException WARNING: /tcpSlaveAgentListener/ java.lang.IllegalStateException: Jenkins.instance is missing. Read the documentation of Jenkins.getInstanceOrNull to see what you are doing wrong. at jenkins.model.Jenkins.get(Jenkins.java:758) at hudson.init.impl.InstallUncaughtExceptionHandler.lambda$init$0(InstallUncaughtExceptionHandler.java:36) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:77) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:58) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:82) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:524) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595) at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1317) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564) at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1219) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:531) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:333) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:310) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKi
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Justin Rainwater commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline It's "resolved" because they're not gonna do anything about it. Regardless of how essential it may be. Our team has rolled our own solution which gets the job done despite requiring a ton of work. There's a reason Mr. Glick is suggesting everyone use Jenkins less. https://www.youtube.com/watch?v=Zeqc6--0eQw Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Dylan Nicholson commented on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline Agreed, this is an essential feature. This shouldn't be marked as "Resolved" at all. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38877) Build History by Node doesn't work with Pipeline
Title: Message Title Dylan Nicholson edited a comment on JENKINS-38877 Re: Build History by Node doesn't work with Pipeline Agreed, this is an essential feature. This shouldn't be marked as "Resolved" at all. And it makes perfect sense to be able to see the pipeline stages that ran on each node as jobs, especially with any info about whether they failed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48960) Org folders repository folder never runs scans on repository
Title: Message Title Stephen Connolly commented on JENKINS-48960 Re: Org folders repository folder never runs scans on repository There are two periodic scans "configured". One is user configurable, namely the one at the org folder level. The other is not currently configurable, namely the one at the branch folder level. Now the way this is designed is on the basis that you will set up webhooks because "polling must die" to quote a blog post from KK ages back. So the periodic scanning is more to cover two cases: 1. To allow controlled pruning of orphaned items. For technical reasons, the code was actually written originally to allow multiple sources in the same org folder. So you could have one source be a github organization and another be a bitbucket team. Then if you moved a repository from the bitbucket team to the github organization the multibranch project would still stay there. This was to mirror the fact that a multibranch project can have multiple sources. However this was too confusing, so we locked the org folders to one source only. In any case, because there originally could be (and for a multibranch project there still can be) multiple things that can claim ownership of a child name, we cannot decide if an event that a name has been deleted by one source will actually result in the deletion of the child. We have to ask all the candidate sources in the priority order: "is this yours?" until we get someone answering "yes"... So the orphaned item strategy only runs with a full scan. This also allows the orphaned item strategy to correctly decide the order in which orphans should be removed. 2. Events may be dropped or lost. We should find those changes eventually. The scan fills that gap. If you have webhooks set up correctly then you only need scanning say once per day or less frequently. All the cron triggers store a random offset as a transient field. This random offset is used to decide when in the `H` portion of a trigger rule to actually pick. The periodic folder trigger converts the times into rules like H * * * * (for hourly) or H H * * * (for daily) so this transient field is important that it remain consistent. What I think is happening is that the org folder scan is resetting the transient field. So if your org folder is scanning every 5 minutes, you will have a 5 in 60 chance that the transient gets reset to a value in the next 5 minutes. Of course we have two H's for the daily scan that the multibranch has. So basically if my theory that the transient is getting reset is correct then there is a 1 in 288 chance that the transient will have a value resulting in a scan during the next 5 minutes... and then the transient gets reset again. Each 5 minute interval gas a 287 in 288 chance of not scanning... so we are naïvely looking at the probability of a multibranch project not scanning being (287/288)^288 = 0.36... it's actually worse, because that is actually the probability of it checking whether a scan is due... and if the transient field for H is being cleared then so too will this one: https://github.com/jenkinsci/cloudbees-folder-plugin/blob/23367538c5c6b405a3ba63d8033ca459aa2f65a0/src/main/java/com/cloudbees/hudson/plugins/folder/computed/PeriodicFolderTrigger.java#L71 and so if we win the 63% lottery then one of those will run through to initialize lastTriggered to a random value https://github.com/jenkinsci/cloudbees-folder-plugin/blob/23367538c5c6b405a3ba63d8033ca459aa2f65a0/src/main/java/com/cloudbees/hudson/plugins/folder/computed/PeriodicFolderTrigger.java#L211-L217 So if my theory is correct then you would expect:
[JIRA] (JENKINS-34313) Exceptions by parallel SCM checkout
Title: Message Title Shannon Kerr commented on JENKINS-34313 Re: Exceptions by parallel SCM checkout Aaron Dietz Thank you. I've been testing with this all day today and so far so good. Hopefully your solution works until this ticket gets a proper resolution. Thank you 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55132) SECURITY-595 fix should always allow getters with StaplerRequest argument
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-55132 SECURITY-595 fix should always allow getters with StaplerRequest argument Change By: Daniel Beck Labels: security security-595 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55132) SECURITY-595 fix should always allow getters with StaplerRequest argument
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-55132 SECURITY-595 fix should always allow getters with StaplerRequest argument Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-12-11 21:13 Priority: Minor Reporter: Daniel Beck The fix for SECURITY-595 should always allow getters with StaplerRequest argument, as they're clearly intended to be routable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55131) CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty
Title: Message Title Daniel Beck closed an issue as Fixed This is working as intended. Discard unreadable data. Jenkins / JENKINS-55131 CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty Change By: Daniel Beck Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53603) VMs are created without being added to the Jenkins nodes list
Title: Message Title
Francis Bolduc edited a comment on JENKINS-53603
Re: VMs are created without being added to the Jenkins nodes list
Environment: Jenkins 2.155, google-compute-engine-plugin 1.0.7I've have the same issue here. In the jenkins configure page, I've setup a "Instance Configuration"; in "labels", I've type "gce-label"In my Jenkinsfile or pipeline configuration, I specified something like this :{code:java}pipeline {agent {label 'gce-label||vmware-label'}stages {stage('Test') {steps {echo 'Yeah'}}}} {code}If I execute a build with this pipeline above, what will happened is that the google cloud engine plugin will provision VMs until it capped the capacity or quota and wait indefinitely and the nodes are not added to jenkins... It can wait beyond 30 minutes...But if I replay this build and modify the label in the pipeline by using below (and kills all VMs){code:java}label 'gce-label'{code}The Build 2 will provision the VM in GCE, will be added correctly to jenkins and will execute the pipeline. And then, the Build 1 will execute as well.I did have a stacktrace but not sure at what jenkins version I was (between 2.153 and 2.155) when I found this:{code:java}Dec 11, 2018 10:41:52 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud provisionINFO: Provisioning node from config com.google.jenkins.plugins.computeengine.InstanceConfiguration@322cd0be for excess workload of 1 units of label 'gce-label||vmware-label'Dec 11, 2018 10:41:52 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud availableNodeCapacityINFO: Found capacity for 10 nodes in cloud GCE SlavesDec 11, 2018 10:41:54 AM hudson.triggers.SafeTimerTask runSEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@2cc40d7e failedjava.lang.ClassCastException: hudson.model.labels.LabelExpression$Or cannot be cast to hudson.model.labels.LabelAtom at jenkins.model.Jenkins.getLabelAtom(Jenkins.java:1947) at hudson.model.Label.parse(Label.java:612) at hudson.model.Node.getAssignedLabels(Node.java:304) at hudson.model.Slave.(Slave.java:196) at hudson.slaves.AbstractCloudSlave.(AbstractCloudSlave.java:51) at com.google.jenkins.plugins.computeengine.ComputeEngineInstance.(ComputeEngineInstance.java:56) at com.google.jenkins.plugins.computeengine.InstanceConfiguration.provision(InstanceConfiguration.java:308) at com.google.jenkins.plugins.computeengine.ComputeEngineCloud.provision(ComputeEngineCloud.java:159) at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715) at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320) at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61) at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.runAndReset(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source){code} I've seen something similar to this:{code:java}SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@1251ecc0 failedjava.lang.ClassCastException{code} Might
[JIRA] (JENKINS-53603) VMs are created without being added to the Jenkins nodes list
Title: Message Title
Francis Bolduc commented on JENKINS-53603
Re: VMs are created without being added to the Jenkins nodes list
Environment: Jenkins 2.155, google-compute-engine-plugin 1.0.7 I've have the same issue here. In the jenkins configure page, I've setup a "Instance Configuration"; in "labels", I've type "gce-label" In my Jenkinsfile or pipeline configuration, I specified something like this :
pipeline {
agent {
label 'gce-label||vmware-label'
}
stages {
stage('Test') {
steps {
echo 'Yeah'
}
}
}
}
If I execute a build with this pipeline above, what will happened is that the google cloud engine plugin will provision VMs until it capped the capacity or quota and wait indefinitely and the nodes are not added to jenkins... It can wait beyond 30 minutes... But if I replay this build and modify the label in the pipeline by using below (and kills all VMs)
label 'gce-label'
The Build 2 will provision the VM in GCE, will be added correctly to jenkins and will execute the pipeline. And then, the Build 1 will execute as well. I did have a stacktrace but not sure at what jenkins version I was (between 2.153 and 2.155) when I found this:
Dec 11, 2018 10:41:52 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud provision
INFO: Provisioning node from config com.google.jenkins.plugins.computeengine.InstanceConfiguration@322cd0be for excess workload of 1 units of label 'gce-label||vmware-label'
Dec 11, 2018 10:41:52 AM com.google.jenkins.plugins.computeengine.ComputeEngineCloud availableNodeCapacity
INFO: Found capacity for 10 nodes in cloud GCE Slaves
Dec 11, 2018 10:41:54 AM hudson.triggers.SafeTimerTask run
SEVERE: Timer task hudson.slaves.NodeProvisioner$NodeProvisionerInvoker@2cc40d7e failed
java.lang.ClassCastException: hudson.model.labels.LabelExpression$Or cannot be cast to hudson.model.labels.LabelAtom
at jenkins.model.Jenkins.getLabelAtom(Jenkins.java:1947)
at hudson.model.Label.parse(Label.java:612)
at hudson.model.Node.getAssignedLabels(Node.java:304)
at hudson.model.Slave.(Slave.java:196)
at hudson.slaves.AbstractCloudSlave.(AbstractCloudSlave.java:51)
at com.google.jenkins.plugins.computeengine.ComputeEngineInstance.(ComputeEngineInstance.java:56)
at com.google.jenkins.plugins.computeengine.InstanceConfiguration.provision(InstanceConfiguration.java:308)
at com.google.jenkins.plugins.computeengine.ComputeEngineCloud.provision(ComputeEngineCloud.java:159)
at hudson.slaves.NodeProvisioner$StandardStrategyImpl.apply(NodeProvisioner.java:715)
at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:320)
at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:61)
at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:809)
at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72)
at jenkins.s
[JIRA] (JENKINS-55131) CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55131 CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-12-11 20:51 Priority: Minor Reporter: Josh Soref I ran across a project that looked like this: '1.1' encoding='UTF-8'?> Blah false "disk-usage@0.28"/> "disk-usage@0.28"/> I recently disabled the disk usage plugin which results in: /jenkins/administrativeMonitor/OldData/manage Type Name Error hudson.model.FreeStyleProject blah CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty, CannotResolveClassException: hudson.plugins.disk_usage.DiskUsageProperty
[JIRA] (JENKINS-55130) Rewrite OldDataMonitor configure text
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55130 Rewrite OldDataMonitor configure text Issue Type: Bug Assignee: Josh Soref Components: core Created: 2018-12-11 20:22 Priority: Minor Reporter: Josh Soref The text implies that there's a "save" button and that there are "files" that will be listed in the table, both of these are absolutely wrong. It also didn't do a good job of noting a common cause of items in the table are plugins (e.g. I disabled the diskspaceusage plugin and got a huge number of rows). Add Comment
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Guru Vamsi CHINTALA edited a comment on JENKINS-55106 Re: Build stuck on final "exit 0" We are seeing the same issue in regular builds and pull requests, build stucks on exit 0 for 10 more than 5 minutes and reports the status. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55106) Build stuck on final "exit 0"
Title: Message Title Guru Vamsi CHINTALA commented on JENKINS-55106 Re: Build stuck on final "exit 0" We are seeing the same issue in regular builds and pull requests, build stucks on exit 0 for 10 minutes and reports the status. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34313) Exceptions by parallel SCM checkout
Title: Message Title
Aaron Dietz commented on JENKINS-34313
Re: Exceptions by parallel SCM checkout
Shannon Kerr Just try your luck with the lock at first.
lock ("end_lock") {
echo "end lock"
}
This is the least time consuming way. If that does not work:
lock ("end_lock") {
echo "end lock"
sleep time: (50 + random.nextInt(400)) // hopefully enough time
}
It might be enough to have one lock for each node (as you did show), but it could also be necessary to synchronize all jobs as some files are written back to the master. I hope this helps Greetings from Germany Aaron
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55129) Create a 'Label' option for Shell Scripts
Title: Message Title Nicholas Amorim updated an issue Jenkins / JENKINS-55129 Create a 'Label' option for Shell Scripts Change By: Nicholas Amorim There have been various issues that were marked 'Resolved' or 'Closed', but don't have an explicit solution on how to create a name for various Shell Scripts. Being able to name a sh command rather than multiple 'Shell Scripts' would be much more informative, rather than shuffling searching through the Shell Scripts steps to figure out what is actually happening.I am aware of the shell commands that are below a certain character range that show up , for example: "npm install - Shell Script", but this is useless for commands that are much lengthier longer , in which just 'Shell Script' is displayed.Closed Issues:https://issues.jenkins-ci.org/browse/JENKINS-36933https://issues.jenkins-ci.org/browse/JENKINS-37324 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55129) Create a 'Label' option for Shell Scripts
Title: Message Title Nicholas Amorim updated an issue Jenkins / JENKINS-55129 Create a 'Label' option for Shell Scripts Change By: Nicholas Amorim There have been various issues that were marked 'Resolved' or 'Closed', but don't have an explicit solution on how to create a name for various Shell Scripts. Being able to name a sh command rather than multiple 'Shell Scripts' would be much more informative, rather than shuffling through the Shell Scripts to figure out what is actually happening. I am aware of the shell commands that are below a certain character range that show up "npm install - Shell Script", but this is useless for commands that are much lengthier, in which 'Shell Script' is displayed. Closed Issues:https://issues.jenkins-ci.org/browse/JENKINS-36933https://issues.jenkins-ci.org/browse/JENKINS-37324 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55129) Create a 'Label' option for Shell Scripts
Title: Message Title Nicholas Amorim updated an issue Jenkins / JENKINS-55129 Create a 'Label' option for Shell Scripts Change By: Nicholas Amorim Attachment: shell-script.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Jose Blas Camacho Taboada updated JENKINS-52735 Jenkins / JENKINS-52735 checkoutToSubdirectory() ignored on first commit of new branch Change By: Jose Blas Camacho Taboada Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55129) Create a 'Label' option for Shell Scripts
Title: Message Title Nicholas Amorim created an issue Jenkins / JENKINS-55129 Create a 'Label' option for Shell Scripts Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2018-12-11 19:41 Priority: Major Reporter: Nicholas Amorim There have been various issues that were marked 'Resolved' or 'Closed', but don't have an explicit solution on how to create a name for various Shell Scripts. Being able to name a sh command rather than multiple 'Shell Scripts' would be much more informative, rather than shuffling through the Shell Scripts to figure out what is actually happening. Closed Issues: https://issues.jenkins-ci.org/browse/JENKINS-36933 https://issues.jenkins-ci.org/browse/JENKINS-37324 Add Comment
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Jose Blas Camacho Taboada stopped work on JENKINS-52735 Change By: Jose Blas Camacho Taboada Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55128) Email-Ext CC's users whose email address starts with 'cc'
Title: Message Title Keith Johnson created an issue Jenkins / JENKINS-55128 Email-Ext CC's users whose email address starts with 'cc' Issue Type: Bug Assignee: David van Laatum Components: email-ext-plugin Created: 2018-12-11 19:39 Environment: Jenkins 2.138.4 Email-Ext 2.63 Priority: Minor Reporter: Keith Johnson I noticed that any user whose email starts with 'cc' ends up getting put in the CC field of the email. For example, if I have a build that is sending emails to cct...@example.org, it ends up always CC'ing cct...@example.org and never putting that as a TO address. Add Comment
[JIRA] (JENKINS-49280) pipeline docker agent configuration is inconsistent
Title: Message Title Jose Blas Camacho Taboada stopped work on JENKINS-49280 Change By: Jose Blas Camacho Taboada Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title
Daniel Danan commented on JENKINS-54632
Re: dsl job doesn't create a build step for Performance Center using Jenkins API
Hi Eduard, Please look at the attached file 'used_dsl_script.txt'. I used it in a job having a "Process Job DSLs" build step configured to run a provided DSL Script (see attached configuring dsl script.png file). I then run the job and it passes (see attached "running job.png"). When i look at the list of jobs in my jenkins environment, I do see 6 additional jobs created by running this build (see attached file "additional jobs created.png"). When i review one of the jobs supposed to contain the configuration of one of the test executions, it looks OK (see attached file "Configuration of scenario 1 job created by DSL script.png"). I didn't try to run it (and in any case it would have failed as i provided wrong input data in the tests array defined in the dsl script) but i believe those scenario jobs would have been OK. I used the web site https://job-dsl.herokuapp.com/ to verify that DSL was indeed creating the config.xml according to what was expected. I am not sure how much reliable it is but it helped me overcome some errors while trying to find the correct syntax. Basically, the script should contain the following section for correctly creating the build step (in your case, please modify the bold section in the following script): configure { project -> project / builders << 'com.microfocus.application.automation.tools.run.PcBuilder' (plugin: 'hp-application-automation-tools-plugin@5.5.3-beta-SNAPSHOT') { 'HTTPSProtocol' 'false' 'addRunToTrendReport' 'ASSOCIATED' 'almDomain' 'MYDOMAIN' 'almProject' 'MYPROJECT' 'autoTestInstanceID' 'MANUAL' 'credentialsId' '98dce5e1-91e9-4299-85a0-c306059f6034' 'credentialsProxyId' '' 'description' test.description 'pcServerName' 'MYPCSERVER' 'postRunAction' 'COLLATE_AND_ANALYZE' 'proxyOutURL' '' 'retry' 'NO_RETRY' 'retryDelay' '5' 'retryOccurrences' '3' 'serverAndPort' 'http://MyJenkinsServer:8080' 'statusBySLA' 'false' 'testId' test.testId 'testInstanceId' test.testInstanceId 'timeslotDurationHours' test.hours 'timeslotDurationMinutes' test.minutes 'trendReportId' '' 'vudsMode' 'false' } } Give it a try. If you need to figure out which values to use for fields such as 'credentialsId', 'serverAndPort' or anything else, help yourself with pipeline syntax in your Jenkins server: /job/pc_pipeline/pipeline-syntax/, "select pcBuild: Execute performance test using Performance Center", provide the values you would usually provide to have correct input, then press the "Generate Pipeline Script" button and base on the generated script to provide values to your DSL script. regards, Daniel
Add Comment
[JIRA] (JENKINS-54632) dsl job doesn't create a build step for Performance Center using Jenkins API
Title: Message Title Daniel Danan updated an issue Jenkins / JENKINS-54632 dsl job doesn't create a build step for Performance Center using Jenkins API Change By: Daniel Danan Attachment: configuring dsl script.png Attachment: running job.png Attachment: used_dsl_script.txt Attachment: additional jobs created.png Attachment: Configuration of scenario 1 job created by DSL script.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47604) blue ocean URL redirection converting %2F to %252F%
Title: Message Title Nicholas Geyer reopened an issue I believe JENKINS-47535 resolved this issue for multi-branch Git repositories, but it is still an issue for anything else that has a forward slash in its display name. If you have a pipeline that is a job with children, then the pipeline for one of the youngest generations of children will have a display name with forward slashes showing the hierarchy. This is converted to %2F for URLs, but afterwards it is rewritten again to %252F. Please contact me if you need more information. Jenkins / JENKINS-47604 blue ocean URL redirection converting %2F to %252F% Change By: Nicholas Geyer Resolution: Duplicate Status: Closed Reopened Assignee: James Dumay Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-51191) hudson.remoting.Channel$CallSiteStackTrace: Remote call to
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Closing for lack of sufficient diagnostics and information to reproduce after no response for quite a while. Jenkins / JENKINS-51191 hudson.remoting.Channel$CallSiteStackTrace: Remote call to Change By: Jeff Thompson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52690) Agent failing after start FileSystemException Operation not permitted
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Closing for lack of sufficient diagnostics and information to reproduce after no response for quite a while. Jenkins / JENKINS-52690 Agent failing after start FileSystemException Operation not permitted Change By: Jeff Thompson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52790) FATAL: java.io.IOException: Unexpected EO - runs OK soon after
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Closing for lack of sufficient diagnostics and information to reproduce after no response for quite a while. Jenkins / JENKINS-52790 FATAL: java.io.IOException: Unexpected EO - runs OK soon after Change By: Jeff Thompson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48865) JNLP Agents/Slaves Disconnecting Unpredictably
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Closing for lack of sufficient diagnostics and information to reproduce after no response for quite a while. Jenkins / JENKINS-48865 JNLP Agents/Slaves Disconnecting Unpredictably Change By: Jeff Thompson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44132) Random JNLP Agent disconnect
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Closing for lack of sufficient diagnostics and information to reproduce after no response for quite a while. Jenkins / JENKINS-44132 Random JNLP Agent disconnect Change By: Jeff Thompson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48895) Channels closed exception after upgrade Jenkins version 2.90
Title: Message Title Jeff Thompson closed an issue as Cannot Reproduce Closing for lack of sufficient diagnostics and information to reproduce after no response for quite a while. Jenkins / JENKINS-48895 Channels closed exception after upgrade Jenkins version 2.90 Change By: Jeff Thompson 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. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title Cyrille Le Clerc commented on JENKINS-53305 Re: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; Devin Nusbaum I am seeing the bug at the moment with the Pipeline Step API 2.16. I'll try to bump soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-53305
javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Change By:
Cyrille Le Clerc
Hello * Jenkins 2.121.2 (official Docker image) * Mailer Plugin 1.21 Sometimes pipelines in Jenkins fails with next exception: {noformat}javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="=_Part_232_854096954.1535491539067" at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:896) at javax.activation.DataHandler.writeTo(DataHandler.java:317) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099)Caused: javax.mail.MessagingException: IOException while sending message; nested exception is: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="=_Part_232_854096954.1535491539067" at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1141) at javax.mail.Transport.send0(Transport.java:195) at javax.mail.Transport.send(Transport.java:124) at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:142) at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:128) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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){noformat} Example of pipeline:{ { code} node { }} mail(to: "x...@example.com", subject: "test", body: "test") {{ } }} {code} Settings: * SMTP server: mail.example.com * Default user e-mail suffix: @example.com Restart of Jenkins temporary solve the issue. Please fix the bug.Thank you
[JIRA] (JENKINS-53305) javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-53305
javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed;
Change By:
Cyrille Le Clerc
Hello * Jenkins 2.121.2 (official Docker image) * Mailer Plugin 1.21 Sometimes pipelines in Jenkins fails with next exception: {noformat} javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="=_Part_232_854096954.1535491539067" at javax.activation.ObjectDataContentHandler.writeTo(DataHandler.java:896) at javax.activation.DataHandler.writeTo(DataHandler.java:317) at javax.mail.internet.MimeBodyPart.writeTo(MimeBodyPart.java:1476) at javax.mail.internet.MimeMessage.writeTo(MimeMessage.java:1772) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1099)Caused: javax.mail.MessagingException: IOException while sending message; nested exception is: javax.activation.UnsupportedDataTypeException: no object DCH for MIME type multipart/mixed; boundary="=_Part_232_854096954.1535491539067" at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:1141) at javax.mail.Transport.send0(Transport.java:195) at javax.mail.Transport.send(Transport.java:124) at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:142) at org.jenkinsci.plugins.workflow.steps.MailStep$MailStepExecution.run(MailStep.java:128) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) 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) {noformat} Example of pipeline:{{node {}}mail(to: "x...@example.com", subject: "test", body: "test") {{}}} Settings: * SMTP server: mail.example.com * Default user e-mail suffix: @example.com Restart of Jenkins temporary solve the issue. Please fix the bug.Thank you
[JIRA] (JENKINS-33310) Jenkins Pipeline (Workflow) support for HockeyApp plugin
Title: Message Title Shilpa Gollamudi commented on JENKINS-33310 Re: Jenkins Pipeline (Workflow) support for HockeyApp plugin I currently upload mobile packages to HockeyApp via Jenkins. I am now trying to do this using Jenkins pipeline. can someone provide a snippet of how i can upload mobile build packages to HockeyApp using Jenkins pipeline? Documentation is not very clear. I tried using Jenkins Snippet generator, but it is still not providing all my needs. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55127) Parallel Input stages are not individually selectable in Blue Ocean
Title: Message Title
Alex Taylor created an issue
Jenkins / JENKINS-55127
Parallel Input stages are not individually selectable in Blue Ocean
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-12-11 18:22
Environment:
Jenkins LTS 2.138.x.x BO plugins 1.8.2
Priority:
Minor
Reporter:
Alex Taylor
Issue: I have a pipeline script with parallel steps and each one has its own input that needs to be approved. Those inputs are not individually approvable when selecting their node icons which means I need to approve them all in order from top to bottom for all the stages to move forward Steps to reproduce: Create a new job with the following script
pipeline {
agent none
stages{
stage('Parallel Steps') {
parallel {
stage('BranchA'){
stages{
stage('InputA'){
agent any
input {
message "Should we continue?"
ok "Yes, we should."
}
steps {
echo "Approved A"
}
}
stage('DeployA'){
agent any
steps {
echo "Deploying A"
}
}
}
}
stage('BranchB'){
stages{
stage('InputB'){
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-52735 checkoutToSubdirectory() ignored on first commit of new branch Change By: Vivek Pandey Labels: triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49280) pipeline docker agent configuration is inconsistent
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-49280 pipeline docker agent configuration is inconsistent Change By: Vivek Pandey Labels: triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52735) checkoutToSubdirectory() ignored on first commit of new branch
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-52735 checkoutToSubdirectory() ignored on first commit of new branch Change By: Vivek Pandey Labels: triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49142) Be able to customize checkout as "options" in declarative pipeline
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-49142 Be able to customize checkout as "options" in declarative pipeline Change By: Vivek Pandey Labels: triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49280) pipeline docker agent configuration is inconsistent
Title: Message Title Vivek Pandey updated an issue Jenkins / JENKINS-49280 pipeline docker agent configuration is inconsistent Change By: Vivek Pandey Labels: triaged-2018-11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50547) Add support to Gerrit Trigger for WIP and Private changes (new in Gerrit 2.15)
Title: Message Title mike bayer commented on JENKINS-50547 Re: Add support to Gerrit Trigger for WIP and Private changes (new in Gerrit 2.15) > I have "Exclude Drafts" selected in my trigger configuration, and it appears that also applies to WIP changes in Gerrit 2.15 (i.e., WIP changes are not triggered). i just tried that locally here and WIP changes are triggered even with "exclude drafts" set. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53824) GitHubCommitStatusSetter not working as expected with GHE
Title: Message Title Karl Penzhorn commented on JENKINS-53824 Re: GitHubCommitStatusSetter not working as expected with GHE I have the exact same issue. Not with public Github repos, though... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54881) Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration
Title: Message Title Jakub Bochenski commented on JENKINS-54881 Re: Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration You can try my fix before it's released https://ci.jenkins.io/job/Plugins/job/stashnotifier-plugin/job/PR-211/3/artifact/target/stashNotifier.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54854) Warning when trigger spent to much time in a cron execution
Title: Message Title
Oliver Gondža updated an issue
Jenkins / JENKINS-54854
Warning when trigger spent to much time in a cron execution
Change By:
Oliver Gondža
It would be nice make a warning to a log when {{Trigger}} spends too much time in Cron trigger. It ssually means a malfunction or other issue in a plug-in and timers initiated by defined crontab(s) aren't working correctly (at least when expected). Given Jenkins cron task design, trigger taking more than 60 seconds to complete can prevent task scheduled for the next minute to run on time.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55126) PerfPublisher shows HTML tags ("") instead of rendered output
Title: Message Title
Justin Vallon created an issue
Jenkins / JENKINS-55126
PerfPublisher shows HTML tags ("") instead of rendered output
Issue Type:
Bug
Assignee:
Eugene Schava
Components:
perfpublisher-plugin
Created:
2018-12-11 16:58
Environment:
Jenkins 2.150.1, PerfPublisher 8.05
Priority:
Minor
Reporter:
Justin Vallon
Upgraded from Jenkins 2.60.1 to 2.150.1, and now have a problem with PerfPublisher display, where it is showing html-text on the web-page. For example, in the build page, next to the graph icon for the publisher is the literal text ... PerfPub 8.05 was installed before the upgrade, and has no pending upgrade. The "Matrix build test report" (from left-hand icon bar) page shows (literal) ...
Add Comment
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title John Mellor commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update Thanks Steve, but I still do not have enough context. I do not have that section in the job configs like you do. What plugin provides that configuration section? Screenshot of what I see attached. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title John Mellor updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api update Change By: John Mellor Attachment: Screenshot from 2018-12-11 11-54-26.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54881) Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration
Title: Message Title Vishal Agrawal commented on JENKINS-54881 Re: Stash Notifier Plugin doesn't set the Jenkins Root URL in stash though Jenkins URL is set in Jenkins Location in Global System Configuration Is there a workaround to this issue other than downgrade to 2.138.3? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55125) NPE in splitCauses
Title: Message Title Bertrand Roussel updated an issue Jenkins / JENKINS-55125 NPE in splitCauses Change By: Bertrand Roussel Priority: Major Blocker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48960) Org folders repository folder never runs scans on repository
Title: Message Title
James Hardwick edited a comment on JENKINS-48960
Re: Org folders repository folder never runs scans on repository
If it's any help, I had to setup a fresh Jenkins server for a new project. Again using GitHub Organization plugin to scan a repository for all available branches containing a Jenkinsfile. The repository scan worked the first time as expected, and then immediately started reproducing the original issue as described here. So, pretty easy to setup and reproduce as far as I can tell. I ended up just creating a job that contains [~tario]'s console script but instead as a pipeline script, so when the scan interval occasionally resets for whatever reason, I could just run the job and it's fixed. A la...{code:java}node { for (f in Jenkins.instance.getAllItems(jenkins.branch.MultiBranchProject.class)) {if (f.parent instanceof jenkins.branch.OrganizationFolder) { f.addTrigger(new com.cloudbees.hudson.plugins.folder.computed.PeriodicFolderTrigger("5m"));} }}{code}[~stephenconnolly] I'm looking back and trying to understand your original request but not sure it makes sense. Can you break that down with a bit more detail as to just what exactly *should* be happening?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48960) Org folders repository folder never runs scans on repository
Title: Message Title
James Hardwick commented on JENKINS-48960
Re: Org folders repository folder never runs scans on repository
If it's any help, I had to setup a fresh Jenkins server for a new project. Again using GitHub Organization plugin to scan a repository for all available branches containing a Jenkinsfile. The repository scan worked the first time as expected, and then immediately started reproducing the original issue as described here. So, pretty easy to setup and reproduce as far as I can tell. I ended up just creating a job that contains Patrick Ruckstuhl's console script but instead as a pipeline script, so when the scan interval occasionally resets for whatever reason, I could just run the job and it's fixed. A la...
node {
for (f in Jenkins.instance.getAllItems(jenkins.branch.MultiBranchProject.class)) {
if (f.parent instanceof jenkins.branch.OrganizationFolder) {
f.addTrigger(new com.cloudbees.hudson.plugins.folder.computed.PeriodicFolderTrigger("5m"));
}
}
}
Stephen Connolly I'm looking back and trying to understand your original request but not sure it makes sense. Can you break that down with a bit more detail as to just what exactly should be happening?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55110) BFA 1.21.0 fails to create a failure cause / scan jobs
Title: Message Title
Bertrand Roussel updated an issue
Jenkins / JENKINS-55110
BFA 1.21.0 fails to create a failure cause / scan jobs
Change By:
Bertrand Roussel
After upgrading BFA to the latest version (1.21.0), the plugin can not add a new failure cause with this error. In addition, it cannot detect failure causes in any jobs. I can still see the list of failure causes,{ noformat quote }A problem occurred while processing the request. Please check [our bug tracker|https://jenkins.io/redirect/issue-tracker] to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. [The users list|https://jenkins.io/redirect/users-mailing-list] might be also useful in understanding what has happened.h2. Stack tracecom.fasterxml.jackson.databind.exc.InvalidTypeIdException: Could not resolve type id 'com.sonyericsson.jenkins.plugins.bfa.model.indication.BuildLogIndication' as a subtype of [simple type, class com.sonyericsson.jenkins.plugins.bfa.model.indication.Indication]: no such class found at [Source: de.undercouch.bson4jackson.io.LittleEndianInputStream@2db3c4b0; pos: 141] (through reference chain: com.sonyericsson.jenkins.plugins.bfa.model.FailureCause["indications"]->java.util.ArrayList[0]) at com.fasterxml.jackson.databind.exc.InvalidTypeIdException.from(InvalidTypeIdException.java:43) at com.fasterxml.jackson.databind.DeserializationContext.invalidTypeIdException(DeserializationContext.java:1635) at com.fasterxml.jackson.databind.DeserializationContext.handleUnknownTypeId(DeserializationContext.java:1187) at com.fasterxml.jackson.databind.jsontype.impl.ClassNameIdResolver._typeFromId(ClassNameIdResolver.java:53) at com.fasterxml.jackson.databind.jsontype.impl.ClassNameIdResolver.typeFromId(ClassNameIdResolver.java:44) at com.fasterxml.jackson.databind.jsontype.impl.TypeDeserializerBase._findDeserializer(TypeDeserializerBase.java:156) at com.fasterxml.jackson.databind.jsontype.impl.AsPropertyTypeDeserializer._deserializeTypedForId(AsPropertyTypeDeserializer.java:113) at com.fasterxml.jackson.databind.jsontype.impl.AsPropertyTypeDeserializer.deserializeTypedFromObject(AsPropertyTypeDeserializer.java:97) at com.fasterxml.jackson.databind.deser.AbstractDeserializer.deserializeWithType(AbstractDeserializer.java:254) at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:288) at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:245) at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:27) at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:530) at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeWithErrorWrapp
[JIRA] (JENKINS-55110) BFA 1.21.0 fails to create a failure cause / scan jobs
Title: Message Title
Bertrand Roussel updated an issue
Jenkins / JENKINS-55110
BFA 1.21.0 fails to create a failure cause / scan jobs
Change By:
Bertrand Roussel
After upgrading BFA to the latest version (1.21.0), the plugin can not add a new failure cause with this error. In addition, it cannot detect failure causes in any jobs. I can still see the list of failure causes, ``` {noformat} A problem occurred while processing the request. Please check [our bug tracker|https://jenkins.io/redirect/issue-tracker] to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. [The users list|https://jenkins.io/redirect/users-mailing-list] might be also useful in understanding what has happened.h2. Stack tracecom.fasterxml.jackson.databind.exc.InvalidTypeIdException: Could not resolve type id 'com.sonyericsson.jenkins.plugins.bfa.model.indication.BuildLogIndication' as a subtype of [simple type, class com.sonyericsson.jenkins.plugins.bfa.model.indication.Indication]: no such class found at [Source: de.undercouch.bson4jackson.io.LittleEndianInputStream@2db3c4b0; pos: 141] (through reference chain: com.sonyericsson.jenkins.plugins.bfa.model.FailureCause["indications"]->java.util.ArrayList[0]) at com.fasterxml.jackson.databind.exc.InvalidTypeIdException.from(InvalidTypeIdException.java:43) at com.fasterxml.jackson.databind.DeserializationContext.invalidTypeIdException(DeserializationContext.java:1635) at com.fasterxml.jackson.databind.DeserializationContext.handleUnknownTypeId(DeserializationContext.java:1187) at com.fasterxml.jackson.databind.jsontype.impl.ClassNameIdResolver._typeFromId(ClassNameIdResolver.java:53) at com.fasterxml.jackson.databind.jsontype.impl.ClassNameIdResolver.typeFromId(ClassNameIdResolver.java:44) at com.fasterxml.jackson.databind.jsontype.impl.TypeDeserializerBase._findDeserializer(TypeDeserializerBase.java:156) at com.fasterxml.jackson.databind.jsontype.impl.AsPropertyTypeDeserializer._deserializeTypedForId(AsPropertyTypeDeserializer.java:113) at com.fasterxml.jackson.databind.jsontype.impl.AsPropertyTypeDeserializer.deserializeTypedFromObject(AsPropertyTypeDeserializer.java:97) at com.fasterxml.jackson.databind.deser.AbstractDeserializer.deserializeWithType(AbstractDeserializer.java:254) at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:288) at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:245) at com.fasterxml.jackson.databind.deser.std.CollectionDeserializer.deserialize(CollectionDeserializer.java:27) at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:530) at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeWithErrorWrappin
[JIRA] (JENKINS-55125) NPE in splitCauses
Title: Message Title
Bertrand Roussel updated an issue
Jenkins / JENKINS-55125
NPE in splitCauses
Change By:
Bertrand Roussel
Not sure what is happening but we have this issue:{noformat}SEVERE: Could not scan build BuildJob #224java.lang.NullPointerExceptionat com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.splitCauses(BuildFailureScanner.java:360)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findIndications(BuildFailureScanner.java:279)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findCauses(BuildFailureScanner.java:236)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.scan(BuildFailureScanner.java:162)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.scanIfNotScanned(BuildFailureScanner.java:138)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.onCompleted(BuildFailureScanner.java:117)at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211)at hudson.model.Run.execute(Run.java:1855)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429){noformat}This appears to be because of null 'causes' that is being dereferenced. Note that the job is a pipeline (groovy) job.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55125) NPE in splitCauses
Title: Message Title
Bertrand Roussel updated an issue
Jenkins / JENKINS-55125
NPE in splitCauses
Change By:
Bertrand Roussel
Not sure what is happening but we have this issue:{noformat}SEVERE: Could not scan build BuildJob #224java.lang.NullPointerExceptionat com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.splitCauses(BuildFailureScanner.java:360)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findIndications(BuildFailureScanner.java:279)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findCauses(BuildFailureScanner.java:236)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.scan(BuildFailureScanner.java:162)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.scanIfNotScanned(BuildFailureScanner.java:138)at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.onCompleted(BuildFailureScanner.java:117)at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211)at hudson.model.Run.execute(Run.java:1855)at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)at hudson.model.ResourceController.execute(ResourceController.java:97)at hudson.model.Executor.run(Executor.java:429){noformat} This appears to be because of null 'causes' that is being dereferenced.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55125) NPE in splitCauses
Title: Message Title Bertrand Roussel created an issue Jenkins / JENKINS-55125 NPE in splitCauses Issue Type: Bug Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2018-12-11 16:03 Environment: Jenkins 2.150.1 BFA 1.21.0 Priority: Major Reporter: Bertrand Roussel Not sure what is happening but we have this issue: SEVERE: Could not scan build BuildJob #224 java.lang.NullPointerException at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.splitCauses(BuildFailureScanner.java:360) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findIndications(BuildFailureScanner.java:279) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.findCauses(BuildFailureScanner.java:236) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.scan(BuildFailureScanner.java:162) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.scanIfNotScanned(BuildFailureScanner.java:138) at com.sonyericsson.jenkins.plugins.bfa.BuildFailureScanner.onCompleted(BuildFailureScanner.java:117) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211) at hudson.model.Run.execute(Run.java:1855) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Steve Mason edited a comment on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update [~alt_jmellor] That section is "GitHub Organisation", you want to add the "Change requests" strategy under the "Build strategies" section. See this screenshot: !image-2018-12-11-15-41-20-455.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46431) Multibranch pipelines should always show changes
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-46431 Re: Multibranch pipelines should always show changes nice input about this one https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/jenkinsci-users/Ew-7R2rToDQ/THz_c0z7BgAJ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Steve Mason commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update John Mellor That section is "GitHub Organisation", you want to add the "Change requests" strategy under "Build strategies" See this screenshot: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55124) Use Jenkins Credentials for Performance Center username/password
Title: Message Title Jeff Kilgore created an issue Jenkins / JENKINS-55124 Use Jenkins Credentials for Performance Center username/password Issue Type: Improvement Assignee: Daniel Gront Components: hp-application-automation-tools-plugin Created: 2018-12-11 15:41 Environment: HP Application Automation Tools 5.1 CloudBees Priority: Minor Reporter: Jeff Kilgore When configuring an automated performance test in Jenkins, users should be able to use the Jenkins Credentials to supply the username/password fields in the configuration. We use a single PC service account to execute CI Performance Tests, and we do not necessarily want to hand out those credentials to our contractors who configure those tests. It would be more secure to setup a Jenkins Credential, and use that. Also, this would alleviate issue of when the account password expires; we would only need to update the password for the jenkins credential, instead of having to update multiple (near 100) jenkins jobs. Add Comment
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Steve Mason updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api update Change By: Steve Mason Attachment: image-2018-12-11-15-41-20-455.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Steve Mason updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api update Change By: Steve Mason Comment: [~alt_jmellor] you want the section "Build strategies" - that section is under "GitHub Organisation" higher up. I've tried to squeeze everything onto the same screenshot here: !image-2018-12-11-15-36-45-141.png! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Steve Mason commented on JENKINS-54864 Re: github multibranch builds fail to build with latest branch api update John Mellor you want the section "Build strategies" - that section is under "GitHub Organisation" higher up. I've tried to squeeze everything onto the same screenshot here: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54864) github multibranch builds fail to build with latest branch api update
Title: Message Title Steve Mason updated an issue Jenkins / JENKINS-54864 github multibranch builds fail to build with latest branch api update Change By: Steve Mason Attachment: image-2018-12-11-15-36-45-141.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55123) Kubernetes plugin does not respect 'no_proxy' environment variable.
Title: Message Title Dax Games created an issue Jenkins / JENKINS-55123 Kubernetes plugin does not respect 'no_proxy' environment variable. Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-12-11 15:36 Environment: Jenkins ver. 2.150.1 Jenkins Plugins: ace-editor 1.1 true analysis-core 1.95 true ant 1.9 true antisamy-markup-formatter 1.5 true apache-httpcomponents-client-4-api 4.5.5-3.0 true async-http-client 1.9.40.0 true authentication-tokens 1.3 true badge 1.6 true basic-branch-build-strategies 1.1.1 true blueocean 1.9.0 true blueocean-autofavorite 1.2.2 true blueocean-bitbucket-pipeline 1.9.0 true blueocean-commons 1.9.0 true blueocean-config 1.9.0 true blueocean-core-js 1.9.0 true blueocean-dashboard 1.9.0 true blueocean-display-url 2.2.0 true blueocean-events 1.9.0 true blueocean-git-pipeline 1.9.0 true blueocean-github-pipeline 1.9.0 true blueocean-i18n 1.9.0 true blueocean-jira 1.9.0 true blueocean-jwt 1.9.0 true blueocean-personalization 1.9.0 true blueocean-pipeline-api-impl 1.9.0 true blueocean-pipeline-editor 1.9.0 true blueocean-pipeline-scm-api 1.9.0 true blueocean-rest 1.9.0 true blueocean-rest-impl 1.9.0 true blueocean-web 1.9.0 true bouncycastle-api 2.17 true branch-api 2.1.2 true build-monitor-plugin 1.12+build.201809061734 true build-name-setter 1.6.9 true build-pipeline-plugin 1.5.8 true build-timeout 1.19 true build-with-parameters 1.4 true ccm 3.2 true checkstyle 3.50 true clone-workspace-scm 0.6 true cloudbees-bitbucket-branch-source 2.2.15 true cloudbees-folder 6.7 true clover 4.10.0 true cobertura 1.13 true code-coverage-api 1.0.4 true command-launcher 1.2 true conditional-buildstep 1.3.6 true config-file-provider 3.4.1 true configurationslicing 1.47 true copyartifact 1.41 true credentials 2.1.18 true credentials-binding 1.17 true cucumber-reports 4.2.2 true description-setter 1.10 true disk-usage 0.28 true display-url-api 2.3.0 true docker-build-publish 1.3.2 true docker-build-step 2.2 true docker-commons 1.13 true docker-custom-build-environment 1.7.3 true docker-java-api 3.0.14 true docker-plugin 1.1.5 true docker-slaves 1.0.7 true docker-workflow 1.17 true dockerhub-notification 2.3.0 true durable-task 1.28 true email-ext 2.63 true external-monitor-job 1.7 true favorite 2.3.2 true findbugs 4.72 true ghprb 1.42.0 true git 3.9.1 true git-client 2.7.4 true git-parameter 0.9.6 true git-server 1.7 true github 1.29.3 true github-api 1.95 true github-branch-source 2.4.1 true github-oauth 0.31 true github-organization-folder 1.6 true gradle 1.29 true gravatar 2.1 tr
[JIRA] (JENKINS-55015) Include Custom Message has stopped work with DSL
Title: Message Title Emil Wypych commented on JENKINS-55015 Re: Include Custom Message has stopped work with DSL Seems it has been fixed in 2.6 – Marcis Liepins could you please confirm? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55122) Evaluate flaky tests
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-55122 Evaluate flaky tests Issue Type: Task Assignee: Baptiste Mathus Components: core Created: 2018-12-11 15:32 Labels: testing Priority: Major Reporter: Jesse Glick Tracking some flaky tests being ignored in CI. In general, you can just search for usages of @Ignore in the jenkinsci/jenkins repository. Add Comment
