[JIRA] (JENKINS-62030) Dependency-Check Publisher is not showing any detailed finding in table
Title: Message Title Rovindra Kumar closed an issue as Fixed Checked and resolved the issue Jenkins / JENKINS-62030 Dependency-Check Publisher is not showing any detailed finding in table Change By: Rovindra Kumar Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-62030) Dependency-Check Publisher is not showing any detailed finding in table
Title: Message Title Rovindra Kumar updated an issue Jenkins / JENKINS-62030 Dependency-Check Publisher is not showing any detailed finding in table Change By: Rovindra Kumar Summary: Dependency-Check Publisher is not showing any detailed finding in table for findings Environment: Jenkins Version:- 2.222.1Java Version:- 1.8Dependency-Check Version:- 5.1.1OWASP Dependency check 5.3.2 Using as a Build step. Attachment: image-2020-04-24-10-35-52-644.png Hi Team, I have installed dependency check plugins and it is successfully analyzing the project but Dependency Result publisher is showing dependency trends in graph but not showing any finding in table for checking which files are having vulnerabilities.It is successfully creating the xml report in root folder but seems publisher is not working correctly.We are blocked and not able to see the results. Add Comment This message was sent by Atlassian
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title
Charles Smith commented on JENKINS-61356
Re: Unable to connect to slave via Launch Agent mode(SSH)
Matt Sicker Yes it's confirmed. The 61356-key still has the "BEGIN PRIVATE KEY" header after attempting to change the format to RFC4716:
$ ls -l total 8 rw--. 1 jenkins jenkins 3272 Apr 23 18:33 61356-key rw--. 1 jenkins jenkins 3272 Apr 23 18:33 61356-key.pem $ grep "BEGIN\ PRIVATE\ KEY" 61356-key BEGIN PRIVATE KEY $ date Thu Apr 23 22:58:12 EDT 2020 $ ssh-keygen -f 61356-key -p -m RFC4716 Enter new passphrase (empty for no passphrase): Enter same passphrase again: Your identification has been saved with the new passphrase. $ ls -l total 8 rw--. 1 jenkins jenkins 3272 Apr 23 22:58 61356-key rw--. 1 jenkins jenkins 3272 Apr 23 18:33 61356-key.pem $ grep "BEGIN\ PRIVATE\ KEY" 61356-key BEGIN PRIVATE KEY ${code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16823.1587698160172%40Atlassian.JIRA.
[JIRA] (JENKINS-62038) xcode-integration plugin not compatible with jdk11, complains about jaxb missing
Title: Message Title mee kwan created an issue Jenkins / JENKINS-62038 xcode-integration plugin not compatible with jdk11, complains about jaxb missing Issue Type: Bug Assignee: Unassigned Components: xcode-plugin Created: 2020-04-24 01:54 Environment: java 11 on centos7 openjdk 11.0.6 2020-01-14 LTS OpenJDK Runtime Environment 18.9 (build 11.0.6+10-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.6+10-LTS, mixed mode, sharing) jenkins 2.222.1 Priority: Major Reporter: mee kwan 21:28:03 Test Suite 'xxxTests' passed at 2020-04-22 21:28:03.142.FATAL: Implementation of JAXB-API has not been found on module path or classpath.21:28:03 Test Suite 'xxx2Tests' started at 2020-04-22 21:28:03.142FATAL: Implementation of JAXB-API has not been found on module path or classpath.21:28:03 2020-04-22 21:28:03.159719+1000 NVivo[92061:44567393] nw_path_close_fd Failed to close guarded necp fd 8 [9: Bad file descriptor]FATAL: Implementation of JAXB-API has not been found on module path or classpath.21:28:06 Build step 'Xcode' marked build as failure
[JIRA] (JENKINS-62037) EC2 Node with job lost during master restart with maxTotalUses
Title: Message Title Nigel Armstrong created an issue Jenkins / JENKINS-62037 EC2 Node with job lost during master restart with maxTotalUses Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-04-24 01:12 Environment: EC2-Plugin: 1.49.1 Priority: Major Reporter: Nigel Armstrong I have a build running on an ec2 slave (with maxTotalUses set to 1). Then jenkins master is restarted. When the jenkins master comes back up it reconnects the node then disposes of them because EC2RetentionStrategy#taskAccepted: maxTotalUses drained - suspending agent i-, but it should not because these nodes are still in use with the previous build. Add Comment
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Well I'll be damned. Seems like this fips version just doesn't let you use the old format. Could you try exporting it in the RFC4716 format? ssh-keygen -f 61356-key -p -m RFC4716 and save without a password. Check the updated key file and make sure it has a "BEGIN OPENSSH PRIVATE KEY" header instead of "BEGIN PRIVATE KEY". If it still has the BEGIN PRIVATE KEY, then it really seems locked down to a single key format, period. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16816.1587684480160%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title
Andrey Babushkin updated an issue
Jenkins / JENKINS-59910
Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Change By:
Andrey Babushkin
Investigating a spike in builds queue size we've found out that TcpSlaveAgent listener thread was dead with the following logs:{code:java}2019-10-23 09:02:17.236+ [id=200815]SEVERE h.TcpSlaveAgentListener$ConnectionHandler#lambda$new$0: Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread[TCP agent connection handler #1715 with /10.125.100.99:47700,5,main]java.lang.UnsupportedOperationException: Network layer is not supposed to call isSendOpenat org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:730)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.isSendOpen(SSLEngineFilterLayer.java:237)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer.isSendOpen(ConnectionHeadersFilterLayer.java:514)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.doSend(ProtocolStack.java:690)at org.jenkinsci.remoting.protocol.ApplicationLayer.write(ApplicationLayer.java:157)at org.jenkinsci.remoting.protocol.impl.ChannelApplicationLayer.start(ChannelApplicationLayer.java:230)at org.jenkinsci.remoting.protocol.ProtocolStack.init(ProtocolStack.java:201)at org.jenkinsci.remoting.protocol.ProtocolStack.access$700(ProtocolStack.java:106)at org.jenkinsci.remoting.protocol.ProtocolStack$Builder.build(ProtocolStack.java:554)at org.jenkinsci.remoting.engine.JnlpProtocol4Handler.handle(JnlpProtocol4Handler.java:153)at jenkins.slaves.JnlpSlaveAgentProtocol4.handle(JnlpSlaveAgentProtocol4.java:203)at hudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:271)2019-10-23 09:02:17.237+ [id=200815]WARNING hudson.TcpSlaveAgentListener$1#run: Connection handler failed, restarting listenerjava.lang.UnsupportedOperationException: Network layer is not supposed to call isSendOpenat org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:730)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.isSendOpen(ProtocolStack.java:738)at org.jenkinsci.remoting.protocol.FilterLayer.isSendOpen(FilterLayer.java:340)at org.jenkinsci.remoting.protocol.impl.SSLEngineFilterLayer.isSendOpen(SSLEngineFilterLayer.java:237)at
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker I'm unable to get this to work using the 61356-key private key. To replicate: I ran the following to convert the key to PEM format(61356-key.pem): jenkins@dbis-admin:/var/lib/jenkins/.ssh/test $ openssl rsa -in 61356-key -out 61356-key.pem -outform PEM writing RSA key jenkins@dbis-admin:/var/lib/jenkins/.ssh/test $ ls -l total 8 -rw---. 1 jenkins jenkins 3272 Apr 23 18:33 61356-key -rw---. 1 jenkins jenkins 3272 Apr 23 18:33 61356-key.pem Then, copied(selected) the new key in vi format and pasted it into the SSH credential key box. I launch the build agent and get the same PEM error. Both the original private key and pem file are the same exact (i.e. no changes to the BEGIN PRIVATE KEY headers.) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16812.1587682320261%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin updated an issue Jenkins / JENKINS-59910 Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Change By: Andrey Babushkin Environment: Official Docker image based on jenkins/jenkins:2. 190 204 . 1 5 -jdk11Both with and without Nginx 1.17.6 as reverse proxyUbuntu 18.04 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.16805.1587682260312%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin updated an issue Jenkins / JENKINS-59910 Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Change By: Andrey Babushkin Environment: Official Docker image jenkins/jenkins:2.190.1-jdk11 No HTTPS enabled Both with and without Nginx 1.17.6 as reverse proxy Ubuntu 18.04 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.16804.1587682260297%40Atlassian.JIRA.
[JIRA] (JENKINS-59910) Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread
Title: Message Title Andrey Babushkin commented on JENKINS-59910 Re: Nodes can't connect to master after Uncaught exception in TcpSlaveAgentListener ConnectionHandler Thread Nope it DID occur and still occur sometimes, we on Jenkins 2.204.5 now. Jesse Glick could you please give me some hints of how to debug this further to find the root cause? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202661.1571866437000.16808.1587682260378%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Take your original private key (or any of the private keys you've created through ssh-keygen) and use the openssl command to convert its format to PEM. Then try that PEM key in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16800.1587680580244%40Atlassian.JIRA.
[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty
Title: Message Title Nicolas Forney commented on JENKINS-44849 Re: Changeset for first run of generated job is empty Wayne Warren your workaround works only if you are always branching from master. In our team developers often branch from other developers branch or from a develop branch. And with Git there is no way to really know from which branch a branch as been created (they are only tags). I really wish Jenkins will be able to tell me which commit are affected on the first build. But apparently this issue has been open for years without any progress. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182912.1497360024000.16779.1587680280447%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker Thanks for the new information. Just to confirm with you: 1.) Do you want me to use the ssh-keygen or openssl command to generate the public key? I've already created the key.pem file with the openssl genrsa command? 2.) Do you want me to run openssl rsa -in private.key -out private.pem -outform PEM to change the private key format to pem and then extract the public key from the converted pem file? Sorry I want to make sure that I do this right. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16775.1587679320163%40Atlassian.JIRA.
[JIRA] (JENKINS-61955) No valid crumb was included in the request
Title: Message Title Kevin Sheehan commented on JENKINS-61955 Re: No valid crumb was included in the request Tomcat 9.0.34 works fine. That pretty much confirms regression in Tomcat 9.0.31. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205838.1587157651000.16773.1587678900180%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Jesse Glick updated JENKINS-61787 Jenkins / JENKINS-61787 jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 1.29 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205626.1585843138000.16771.1587678720119%40Atlassian.JIRA.
[JIRA] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Kamil Mackow commented on JENKINS-43820 Re: Stage name must be a string literal Just chiming in to voice my support for Brian J Murrell as I ran into the same limitation with matrix stages myself and do not see the proposed workaround as a viable one in these scenarios. Responding with "conscious design decision" and no other explanation is a cop out and, given the very valid nature of the responses here, I would challenge you to defend the statement Andrew Bayer. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181338.1493122184000.16733.1587677640911%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Looking at trilead, I see that RSAKeyAlgorithm only supports SHA1, and it doesn't even support aes-128/256-gcm, so it seems somewhat dated in algorithm support as it is. I'm kind of wondering why this library is the default rather than Apache SSHD (which was used for some other SSH functionality in Jenkins). I see there's support for the old pem file format and the new openssh (RFC 4716) format, but no explicit support for PKCS#8. Could you try out the other formats for the same key to see if it works? If it doesn't, then I think we have some missing crypto primitives here. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16729.1587675300198%40Atlassian.JIRA.
[JIRA] (JENKINS-62036) Issue parsers display incorrect data when message or description contains HTML
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-62036 Issue parsers display incorrect data when message or description contains HTML Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2020-04-23 20:16 Priority: Minor Reporter: Matt Sicker All issue parsers in analysis-model extend IssueParser which need to parse a stream into a Report made up of Issue instances (among other thing). These Issue instances are usually created by extracting text from the console log or other log files. I haven't looked through all 100+ times it is used, but in the vast majority of cases, IssueBuilder.setMessage() is invoked with regex match groups, and those contents are treated as raw HTML (using the Unescaped class). Based on the various issue parsers I've used and looked at, they don't seem to expect HTML, though they can make use of it. Thanks to the use of the OWASP Markup Formatter, nothing malicious can be injected, but any supported HTML and special characters will be interpreted as such when parsed from the console log. Add Comment
[JIRA] (JENKINS-62035) Tabular report no longer sortable
Title: Message Title Ioannis Moutsatsos created an issue Jenkins / JENKINS-62035 Tabular report no longer sortable Issue Type: Bug Assignee: Unassigned Components: summary_report-plugin Created: 2020-04-23 20:08 Environment: Jenkins 2.222.1, summary_report-plugin v1.15 Labels: reporting summary css Priority: Minor Reporter: Ioannis Moutsatsos After upgrading Jenkins to v2.222.1 reports with sortable columns are no longer sortable. I have noticed that now a different CSS stylesheet is loaded when one inspects the table headers. The CSS for elements with class="sortheader" is now loaded from http://yourJenkinsServer/static/98e8fbe5/jsbundles/base-styles-v2.css while previously was loading from http://yourJenkinsServer/static/166f2f84/css/style.css Add Comment
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Alright, I've done some digging, and here's what I've found. The key you attached (61356) is encoded in PKCS#8 which can be seen by the "BEGIN PRIVATE KEY" header. What is usually used in SSH is PKCS#1 (i.e., no special encoding apparently) which has the header "BEGIN RSA PRIVATE KEY". The former format encodes the algorithm in the base64 data while the latter is more of a naked format with the algorithm in the header. I've also seen "BEGIN OPENSSH PRIVATE KEY" which appears to be the newer format which is used by ed25519 and other ciphers. One workaround you could try (in production, too!) would be to convert your private key to the old PEM format. You can use openssl rsa -in private.key -out private.pem -outform PEM to convert the key encoding format which should be supported by trilead. If that doesn't work, then we may have an interesting problem. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16722.1587672480257%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) And I meant to try and see if the RSA keys generated from openssl are decoded properly by Jenkins compared to the ones being generated via ssh-keygen. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16718.1587671400178%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) You can convert an existing key with ssh-keygen -p -f private_key_file -m pem Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16714.1587671340290%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker Thanks for the updates. How do you want me to extract the public key from the pem file? Using ssh-keygen: ssh-keygen-y -f key.pem > key.pub Or using openssl: openssl rsa -in key.pem -pubout -out pubkey.pem Note that when using openssl, the public key doesn't have the standard ssh-rsa heading that normal ssh public keys use. The fips-patched version of OpenSSH makes sense. I've attached a test keypair earlier that you can try and test with to see if the issue can be replicated. I'm not using that keypair. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Based on version differences, it seems like your fips-patched version of OpenSSH is likely what's causing the issue. There might be a missing SSH key format being supported by trilead? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16703.1587669360148%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) In fact, I wonder if that's the issue. It says the PEM is of an unknown type, but an SSH private key is usually encoded via RFC4716 rather than PEM (which ssh-keygen(1) says is the "legacy" format). There's also PCKS8. Version: OpenSSH_8.1p1, LibreSSL 2.7.3 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16699.1587669300164%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Matt Sicker commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Can you try generating a key using openssl genrsa -out private.pem 4096 and see if that works? I wonder if there's been some sort of key format change in ssh-keygen. I really wish this were using OpenSSH, but it's not. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16697.1587669000346%40Atlassian.JIRA.
[JIRA] (JENKINS-53094) Option to expand variables in yamlFile
Title: Message Title Julian Wilkinson edited a comment on JENKINS-53094 Re: Option to expand variables in yamlFile Yeah... this would make declarative jenkinsfiles a lot cleaner :) +1 + I don't think it's uncommon to need to use a value from previous stages in new pods Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193089.153451049.16687.1587667560525%40Atlassian.JIRA.
[JIRA] (JENKINS-53094) Option to expand variables in yamlFile
Title: Message Title Julian Wilkinson commented on JENKINS-53094 Re: Option to expand variables in yamlFile Yeah... this would make declarative jenkinsfiles a lot cleaner +1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.193089.153451049.16673.1587667260244%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker Ivan Fernandez Calvo Hello All - Just checking for any more responses or updates on this? Where to go from here? How to test if erroneous characters are being added to the priv key section of that plugin? Any more information would be appreciated. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.16669.1587666720143%40Atlassian.JIRA.
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg commented on JENKINS-62034 Re: Matrix stages reported skipped instead of actual status. Also reproduced on Jenkins 2.231 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205925.1587662025000.16662.1587663360053%40Atlassian.JIRA.
[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Antonio Schepis updated an issue Jenkins / JENKINS-58754 JIRA-JENKINS Integration | JsonException Change By: Antonio Schepis Attachment: image-2020-04-23-19-30-03-175.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201057.1564657212000.16656.1587663060403%40Atlassian.JIRA.
[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Antonio Schepis commented on JENKINS-58754 Re: JIRA-JENKINS Integration | JsonException Hello, i have the same error. I've created a new webhook with check on issue created and updated. On jenkins I created a job with trigger "Build when a issue is updated on Jira" On jenkins log i found the same error: Selva G do you solved you problem? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201057.1564657212000.16660.1587663060466%40Atlassian.JIRA.
[JIRA] (JENKINS-21099) Don't give useless build time estimates by considering failed builds' durations
Title: Message Title Adam Brousseau commented on JENKINS-21099 Re: Don't give useless build time estimates by considering failed builds' durations +1 for this. Also related, perhaps needs a separate issue. For pipeline builds, I would like to see estimates take into account what stage the build is in. We use a "queue" stage at the start of a build for the time spent waiting for a machine. Queue time can range from seconds to hours and that really throws off the estimates for the remainder of the build. Even though the remaining stages are generally consistent for execution times. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152661.138748788.16641.1587662940320%40Atlassian.JIRA.
[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Antonio Schepis updated an issue Jenkins / JENKINS-58754 JIRA-JENKINS Integration | JsonException Change By: Antonio Schepis Attachment: image-2020-04-23-19-25-28-810.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201057.1564657212000.16638.1587662760244%40Atlassian.JIRA.
[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Antonio Schepis updated an issue Jenkins / JENKINS-58754 JIRA-JENKINS Integration | JsonException Change By: Antonio Schepis Attachment: image-2020-04-23-19-24-11-129.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201057.1564657212000.16634.1587662700333%40Atlassian.JIRA.
[JIRA] (JENKINS-58754) JIRA-JENKINS Integration | JsonException
Title: Message Title Antonio Schepis updated an issue Jenkins / JENKINS-58754 JIRA-JENKINS Integration | JsonException Change By: Antonio Schepis Attachment: image-2020-04-23-19-18-38-929.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201057.1564657212000.16627.1587662340230%40Atlassian.JIRA.
[JIRA] (JENKINS-62033) swarm-client -disableSslVerification does not skip searching subject alternative names
Title: Message Title Brian Farrell updated an issue Jenkins / JENKINS-62033 swarm-client -disableSslVerification does not skip searching subject alternative names Change By: Brian Farrell When running the following command line: /usr/bin/java -jar /tmp/swarm-client.3.19.jar \ -disableSslVerification \ -deleteExistingClients \ -disableClientsUniqueId \ -showHostName \ -noRetryAfterConnected \ -executors=7 \ -labels 'blftest' \ -master https://myjenkins.example.com \ -username jenkins \ -passwordEnvVariable ADMIN_PSW I received the following outputApr 23, 2020 6:58:15 PM hudson.plugins.swarm.Client logArgumentsINFO: Client invoked with: -deleteExistingClients true -disableClientsUniqueId true -disableSslVerification true -executors 7 -labels [blftest] -master https://myjenkins.example.com -noRetryAfterConnected true -passwordEnvVariable ADMIN_PSW -showHostName true -username * Apr 23, 2020 6:58:15 PM hudson.plugins.swarm.Client runINFO: Discovering Jenkins masterApr 23, 2020 6:58:15 PM hudson.plugins.swarm.Client runSEVERE: IOException occurredjavax.net.ssl.SSLPeerUnverifiedException: Certificate for doesn't match any of the subject alternative names: [ingress.local] at shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:507) at shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:437) at shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:384) at shaded.org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) at shaded.org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) at shaded.org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) at shaded.org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at shaded.org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) at shaded.org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) at shaded.org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at shaded.org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at shaded.org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at hudson.plugins.swarm.SwarmClient.discoverFromMasterUrl(SwarmClient.java:142) at hudson.plugins.swarm.Client.run(Client.java:150) at hudson.plugins.swarm.Client.main(Client.java:128)javax.net.ssl.SSLPeerUnverifiedException: Certificate for doesn't match any of the subject alternative names: [ingress.local] at shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.verifyHostname(SSLConnectionSocketFactory.java:507) at shaded.org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:437) at
[JIRA] (JENKINS-62033) swarm-client -disableSslVerification does not skip searching subject alternative names
Title: Message Title Brian Farrell created an issue Jenkins / JENKINS-62033 swarm-client -disableSslVerification does not skip searching subject alternative names Issue Type: Bug Assignee: Unassigned Components: swarm-plugin Created: 2020-04-23 17:12 Environment: Jenkins 2.222.1 swarm-client 3.4 up through 3.19 Priority: Minor Reporter: Brian Farrell When running the following command line: Add Comment
[JIRA] (JENKINS-62034) Matrix stages reported skipped instead of actual status.
Title: Message Title John Malmberg created an issue Jenkins / JENKINS-62034 Matrix stages reported skipped instead of actual status. Issue Type: Bug Assignee: Unassigned Attachments: Jenkinsfile, Jenkins_matrix_skip_bug.PNG Components: pipeline Created: 2020-04-23 17:13 Environment: CentOS Linux release 7.5.1804 (Core) jenkins.noarch 2.222.1-1.1 java-1.8.0-openjdk.i686 1:1.8.0.181-3.b13.el7_5 Blue Ocean 1.23.0 Labels: pipeline matrix Priority: Major Reporter: John Malmberg A matrix job where some stages are excluded is showing some of the stages as "skipped" in the Blue Ocean UI, or as having no steps in the traditional UI. The logs are showing that the steps have been run as expected. Even if a step fails in a stage, it does not show up in the UI. This makes the Jenkins Web UI useless for tracking the progress of a Matrix job. Attached is a Jenkinsfile that reproduces the problem with a single stage in the Matrix step. If more stages are added to the step, some of those additional stages are not shown on the web UI. This looks similar to: https://issues.jenkins-ci.org/browse/JENKINS-53816
[JIRA] (JENKINS-62032) "Check now" button not inheriting body font-family
Title: Message Title J A created an issue Jenkins / JENKINS-62032 "Check now" button not inheriting body font-family Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-23 15:32 Priority: Trivial Reporter: J A In the Update Manager, the button (which is actually a stylised hyperlink) is no inheriting the body's font-family, making it look different to the other buttons in this component. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62031) "Page not found" on jobs created by Gitlab Branch Source
Title: Message Title Rodrigo Carvalho Silva updated an issue Jenkins / JENKINS-62031 "Page not found" on jobs created by Gitlab Branch Source Change By: Rodrigo Carvalho Silva Attachment: jenkins-blue-ocean-gitlab-branch-source.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205922.1587655512000.16597.1587655620131%40Atlassian.JIRA.
[JIRA] (JENKINS-62031) "Page not found" on jobs created by Gitlab Branch Source
Title: Message Title Rodrigo Carvalho Silva created an issue Jenkins / JENKINS-62031 "Page not found" on jobs created by Gitlab Branch Source Issue Type: Bug Assignee: Parichay Barpanda Components: blueocean-plugin, gitlab-branch-source-plugin Created: 2020-04-23 15:25 Priority: Minor Reporter: Rodrigo Carvalho Silva Hi! I'm testing Blue Ocean Plugin and Gitlab Branch Source Plugin but I get "Page not found (404)" when I try to open any job created by Gitlab Branch Source Plugin. We use a lot of subgroups on Gitlab and maybe this is the reason. One example is: Job path on classic view: https://myjenkins/jenkins/job/group-giltlab-branch-source/job/subgroup%20%252F%20project/ Job path on Blue Ocean view (get error): https://myjenkins/jenkins/blue/organizations/jenkins/group-giltlab-branch-source%2Fsubgroup%20%252F%20project/activity Blue Ocean version: 1.23.0 Gitlab Branch Source version: 1.4.6 Jenkins Version: 2.204.2 Regards! Add Comment
[JIRA] (JENKINS-62004) Parameterized Remote Trigger expects case-sensitive http headers
Title: Message Title KaiHsiang Chang updated JENKINS-62004 Reviewed PR and merged. Jenkins / JENKINS-62004 Parameterized Remote Trigger expects case-sensitive http headers Change By: KaiHsiang Chang Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-57695) Jira issue not created when jenkins build failed
Title: Message Title
Armin Müller commented on JENKINS-57695
Re: Jira issue not created when jenkins build failed
I'm afraid this (still) doesn't work for me. Jenkine 2.222.1, Plugin 3.0.15, self-hosted Jira 8.5.4: {{Jira REST createIssue error: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors= {assignee=expected Object containing a 'name' property}, errorMessages=[]}]}}} {{RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={assignee=expected Object containing a 'name' property} , errorMessages=[]}]}}} {{ at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient$2.apply(AbstractAsynchronousRestClient.java:176)}} {{... }} Caused: java.util.concurrent.ExecutionException {{ at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)}} {{ at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)}} {{ at io.atlassian.util.concurrent.Promises$OfStage.get(Promises.java:357)}} {{ at com.atlassian.jira.rest.client.internal.async.DelegatingPromise.get(DelegatingPromise.java:106)}} {{ at hudson.plugins.jira.JiraRestService.createIssue(JiraRestService.java:306)}} {{ at hudson.plugins.jira.JiraSession.createIssue(JiraSession.java:412)}} {{ at hudson.plugins.jira.JiraCreateIssueNotifier.createJiraIssue(JiraCreateIssueNotifier.java:204)}} {{ at hudson.plugins.jira.JiraCreateIssueNotifier.currentBuildResultFailure(JiraCreateIssueNotifier.java:357)}} {{ at hudson.plugins.jira.JiraCreateIssueNotifier.perform(JiraCreateIssueNotifier.java:159)}} {{ at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)}} {{ at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:741)}} {{ at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690)}} {{ at hudson.model.Build$BuildExecution.post2(Build.java:186)}} {{ at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635)}} {{ at hudson.model.Run.execute(Run.java:1881)}} {{ at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)}} {{ at hudson.model.ResourceController.execute(ResourceController.java:97)}} {{ at hudson.model.Executor.run(Executor.java:428)}} Any idea what could cause this?
Add Comment
[JIRA] (JENKINS-60969) Unwanted job interaction if using global pipeline libraries
Title: Message Title Daniel Estermann commented on JENKINS-60969 Re: Unwanted job interaction if using global pipeline libraries Tried to reproduce. Unsuccessfully so far... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.16578.1587654120222%40Atlassian.JIRA.
[JIRA] (JENKINS-60969) Unwanted job interaction if using global pipeline libraries
Title: Message Title Daniel Estermann assigned an issue to Daniel Estermann Jenkins / JENKINS-60969 Unwanted job interaction if using global pipeline libraries Change By: Daniel Estermann Assignee: Daniel Estermann Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204432.1580891884000.16576.1587654120191%40Atlassian.JIRA.
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated
Title: Message Title Vincent Latombe assigned an issue to Vincent Latombe Jenkins / JENKINS-59340 Pipeline hangs when Agent pod is Terminated Change By: Vincent Latombe Assignee: Vincent Latombe Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201891.1568335765000.16567.1587652620773%40Atlassian.JIRA.
[JIRA] (JENKINS-59340) Pipeline hangs when Agent pod is Terminated
Title: Message Title Vincent Latombe started work on JENKINS-59340 Change By: Vincent Latombe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201891.1568335765000.16572.1587652620835%40Atlassian.JIRA.
[JIRA] (JENKINS-60530) Adding gitlab MR comment from Jenkinsfile does not work
Title: Message Title André Camilo commented on JENKINS-60530 Re: Adding gitlab MR comment from Jenkinsfile does not work I think it would be a great if we could use all gitlab-plugin actions with gitlab-branch-source jobs. Would this be difficult? (I also need the addGitLabMRComment above all other actions from gitlab-plugin) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203631.1576689781000.16558.1587649500299%40Atlassian.JIRA.
[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-58503
Symbols for Extensions
Change By:
Mark Waite
Its currently possible to use the following dsl below when checking out code in a declarative pipeline:{noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ $class: 'RelativeTargetDirectory', relativeTargetDir: 'some-dir' ]] )){noformat} It would be nice if it could support a richer dsl rather than the current $class syntax for extensions. e.g. something like: {noformat}checkout( git( branches: [[name: '*/master']], extensions: [[ relativeTargetDir('some-dir') ]] )){noformat} This could be something i could help contribute if its acceptable?! h2. Implementation Process* List existing symbol definitions from configuration as code matched with {{$Class}} samples for that symbol (create a checklist of symbols to create)* Select a symbol and add a test for the symbol as a {{$Class}} form* Add the symbol* Add a test that uses the symbol instead of the {{$Class}} form* Confirm symbol appears in Pipeline syntax generator* Confirm symbol appears in Configuration as Code* Confirm configuration as code can still read previous configuration files* Write help for the symbol, assure it is clear, correct, complete, and visible in the online Pipeline syntax
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62030) Dependency-Check Publisher is not showing any table for findings
Title: Message Title Rovindra Kumar updated an issue Jenkins / JENKINS-62030 Dependency-Check Publisher is not showing any table for findings Change By: Rovindra Kumar Environment: Jenkins Version:- 2.222.1Java Version:- 1.8Dependency-Check Version:- 5.1.1 OWASP Dependency check 5.3.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205921.1587648804000.16555.1587649200060%40Atlassian.JIRA.
[JIRA] (JENKINS-62030) Dependency-Check Publisher is not showing any table for findings
Title: Message Title Rovindra Kumar updated an issue Jenkins / JENKINS-62030 Dependency-Check Publisher is not showing any table for findings Change By: Rovindra Kumar Environment: Jenkins Version:- 2.222.1Java Version:- openjdk 11 1 . 0.7 8 Dependency-Check Version:- 5.1.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205921.1587648804000.16554.1587649140062%40Atlassian.JIRA.
[JIRA] (JENKINS-62030) Dependency-Check Publisher is not showing any table for findings
Title: Message Title Rovindra Kumar created an issue Jenkins / JENKINS-62030 Dependency-Check Publisher is not showing any table for findings Issue Type: Bug Assignee: Unassigned Attachments: image-2020-04-23-19-00-48-298.png Components: dependency-check-jenkins-plugin Created: 2020-04-23 13:33 Environment: Jenkins Version:- 2.222.1 Java Version:- openjdk 11.0.7 Dependency-Check Version:- 5.1.1 Priority: Blocker Reporter: Rovindra Kumar Hi Team, I have installed dependency check plugins and it is successfully analyzing the project but Dependency Result publisher is showing dependency trends in graph but not showing any table for checking which files are having vulnerabilities. It is successfully creating the xml report in root folder but seems publisher is not working correctly. We are blocked and not able to see the results.
[JIRA] (JENKINS-59610) Build failure causes are deleted when saving Jenkins global configuration.
Title: Message Title Christoph Vogtländer commented on JENKINS-59610 Re: Build failure causes are deleted when saving Jenkins global configuration. I just noticed that the configuration was removed in my instance a while back. Just wanted to drop a note that if you happen to have the "build configuration history" plug-in installed, a backup of build-failure-analyzer.xml exists and can be restored to the exact version before the broken update (go to https:///jobConfigHistory/history?name=build-failure-analyzer) Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202251.1569939008000.16534.1587647340414%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-59192 configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Change By: Dominik Bartholdi Component/s: config-file-provider-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.16531.1587646800614%40Atlassian.JIRA.
[JIRA] (JENKINS-59192) configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-59192 configFileProvider fail after kubernetes plugin update to 1.18.3 on structured pipelines Change By: Dominik Bartholdi Component/s: config-file-provider-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201633.1567448335000.16527.1587646800415%40Atlassian.JIRA.
[JIRA] (JENKINS-61787) jenkins.model.Jenkins loaded from parser callable via TestNameTransformer
Title: Message Title Michael Mrozek commented on JENKINS-61787 Re: jenkins.model.Jenkins loaded from parser callable via TestNameTransformer Not sure if this helps at all, but this can happen when you run out of memory/disk space on the agent. I was hitting the same stack trace after an agent had run out of disk space, even after I freed up some, and this comment got me to try disconnecting/reconnecting it, which fixed it for me Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205626.1585843138000.16498.1587644700112%40Atlassian.JIRA.
[JIRA] (JENKINS-62029) "worksoft Certify process Runner" Build console output error
Title: Message Title Ritapratim Das created an issue Jenkins / JENKINS-62029 "worksoft Certify process Runner" Build console output error Issue Type: Bug Assignee: LakshmiSusmitha Checka Attachments: Jenkins_process_runner_error.jpg Components: worksoft-certify-process-runner-plugin Created: 2020-04-23 10:45 Environment: Jenkins ver. 2.222.1 worksoftcertifyprocessrunner 1.1-SNAPSHOT (private-12/14/2016 10:22-Susmitha007) Priority: Major Reporter: Ritapratim Das "worksoft Certify process Runner" Build console output error: Actual Result or Observation: After completing the execution, Invalid Layout or Invalid record-set message is showing in the build console. That means jenkins build is not able to run the worksoft process due to not finding proper layout or recordset and instead of that it is showing "success" message in build console output and Build is showing blue color (Success). Expected Result: If build console output is displaying message like "Invalid Layout" or "Invalid Record-set" then the build should not be showing pass in the console output. It should show fail message and build color as Red. Kindly fix this issue.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title
Stefan Drissen commented on JENKINS-56086
Re: Tabs missing in configuration page after adding plot to freestyle job
I can confirm that the _javascript_ error is gone, but that the layout is still sub-optimal (even on the initial load the panels are extending past their containers). Also someone seems to have left some debug code behind in configure.js which is repeatedly spamming the console:
console.log("dynWidth=" + dynamicViewPortWidth + ", statWidth=" + staticViewPortWidth);
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16470.1587638400421%40Atlassian.JIRA.
[JIRA] (JENKINS-27208) Make Log Parser Plugin compatible with Workflow
Title: Message Title
Stefan Müller edited a comment on JENKINS-27208
Re: Make Log Parser Plugin compatible with Workflow
There seems to be an error in the snippet generated for {{logParser}} in the Pipeline Syntax page. I generated the snippet{code:groovy}logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false{code}which gives me the error{code:none}WorkflowScript: 73: Missing required parameter: "projectRulePath" @ line 73, column 13. logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false ^{code}Adding{code:none}, projectRulePath: ''{code}to the end of the snippet fixes this error.In addition, why is the path in the {{logParser}} call instead of the name of the rule, as specified in a none-pipeline job or in the snippet generator itself? This will be hell for me if the drive location of the global log parser rule ever changes...Thanks.PS: I know it's a lot of work to keep this stuff up-to-date, but IMHO, further documentation is needed (not just for this plugin). E. g. there is an option {{showGraphs}} (https://jenkins.io/doc/pipeline/steps/log-parser/) with no explanation. I tried it, hoping it might give me maybe parsing on step level, and found no effect.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-27208) Make Log Parser Plugin compatible with Workflow
Title: Message Title
Stefan Müller edited a comment on JENKINS-27208
Re: Make Log Parser Plugin compatible with Workflow
There seems to be an error in the snippet generated for {{logParser}} in the Pipeline Syntax page. I generated the snippet{code:groovy}logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false{code}which gives me the error{code:none}WorkflowScript: 73: Missing required parameter: "projectRulePath" @ line 73, column 13. logParser parsingRulesPath: 'D:\\Jenkins_Log_Parser_Files\\my_global_parse_rule', useProjectRule: false ^{code}Adding{code:none}, projectRulePath: ''{code}to the end of the snippet fixes this error.In addition, why is the path in the {{logParser}} call instead of the name of the rule, as specified in a none-pipeline job or in the snippet generator itself? This will be hell for me if the drive location of the global log parser rule ever changes...Thanks.PS: Up I know it's a lot of work to keep this stuff up -to-date , but IMHO, further documentation is always useful. ;- needed (not just for this plugin ) . E. g. there is an option {{showGraphs}} with no explanation. I tried it, hoping it might give me maybe parsing on step level, and found no effect.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-47858) ERROR: RocketChat notification failed in login sequence
Title: Message Title Jukka-Pekka Kohtala edited a comment on JENKINS-47858 Re: ERROR: RocketChat notification failed in login sequence By looking rocket.chat rest-api guide about login [https://rocket.chat/docs/developer-guides/rest-api/authentication/login/]Seems to me that RocketChat plugin is expecting response to be array but it's not coming as array object .Tested also our server with curl and it's not responding with array. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186370.1510056281000.16437.1587635880251%40Atlassian.JIRA.
[JIRA] (JENKINS-47858) ERROR: RocketChat notification failed in login sequence
Title: Message Title Jukka-Pekka Kohtala edited a comment on JENKINS-47858 Re: ERROR: RocketChat notification failed in login sequence By looking rocket.chat rest-api guide about login[https://rocket.chat/docs/developer-guides/rest-api/authentication/login/]Seems to me that client RocketChat plugin is expecting response to be array but it's not coming as array.Tested also our server with curl and it's not responding with array. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186370.1510056281000.16430.1587635700215%40Atlassian.JIRA.
[JIRA] (JENKINS-47858) ERROR: RocketChat notification failed in login sequence
Title: Message Title Jukka-Pekka Kohtala commented on JENKINS-47858 Re: ERROR: RocketChat notification failed in login sequence By looking rocket.chat rest-api guide about login https://rocket.chat/docs/developer-guides/rest-api/authentication/login/ Seems to me that client is expecting response to be array but it's not coming as array. Tested also our server with curl and it's not responding with array. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186370.1510056281000.16423.1587635640213%40Atlassian.JIRA.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Pedro Gutierrez updated an issue Jenkins / JENKINS-56086 Tabs missing in configuration page after adding plot to freestyle job Change By: Pedro Gutierrez Attachment: otherStylesBreakAfterF5.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16415.1587635340304%40Atlassian.JIRA.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Pedro Gutierrez commented on JENKINS-56086 Re: Tabs missing in configuration page after adding plot to freestyle job Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16419.1587635340409%40Atlassian.JIRA.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Pedro Gutierrez updated an issue Jenkins / JENKINS-56086 Tabs missing in configuration page after adding plot to freestyle job Change By: Pedro Gutierrez Attachment: otherStylesBreakAfterF5.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16411.1587635280475%40Atlassian.JIRA.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Pedro Gutierrez edited a comment on JENKINS-56086 Re: Tabs missing in configuration page after adding plot to freestyle job Same problem hereI can't see, however, the same js error reported by Stefan Drissen.Surprisingly, when I refresh the page (F5, many times) navigation tabs reappear but then other styles in the page break. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16407.1587635280367%40Atlassian.JIRA.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Pedro Gutierrez edited a comment on JENKINS-56086 Re: Tabs missing in configuration page after adding plot to freestyle job Same problem hereI can't see, however, the same js error reported by Stefan Drissen.Surprisingly, when I refresh the page (F5, many times) navigation tabs reappear but then other styles in the page break. !otherStylesBreakAfterF5.PNG|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16404.1587635220251%40Atlassian.JIRA.
[JIRA] (JENKINS-23477) git plugin sparse checkout path field does not expand variables
Title: Message Title jlpinardon edited a comment on JENKINS-23477 Re: git plugin sparse checkout path field does not expand variables I'd really like to be able to use variable with sparse checkout. It would be a great help in having more generic jobs and so on...Please, can we have some update on this ? I am not at all a java dev, and I don't want to be hurtful, but 6 years to find a fix seems to me a very long time :(... Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155700.1403067217000.16382.1587635160565%40Atlassian.JIRA.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Pedro Gutierrez commented on JENKINS-56086 Re: Tabs missing in configuration page after adding plot to freestyle job Same problem here I can't see, however, the same js error reported by Stefan Drissen. Surprisingly, when I refresh the page (F5, many times) navigation tabs reappear but then other styles in the page break. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16399.1587635160774%40Atlassian.JIRA.
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Pedro Gutierrez updated an issue Jenkins / JENKINS-56086 Tabs missing in configuration page after adding plot to freestyle job Change By: Pedro Gutierrez Attachment: otherStylesBreakAfterF5.PNG Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16375.1587634860305%40Atlassian.JIRA.
[JIRA] (JENKINS-61725) Create tests for PitScore (in AutoGrader)
Title: Message Title Simon Schoenwiese commented on JENKINS-61725 Re: Create tests for PitScore (in AutoGrader) Danke für die nette Rückfrage. Ich habe zuerst Tests für die falsche Klasse geschrieben und bin jetzt dabei, doch die richtige Klasse zu testen. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205551.1585338673000.16378.1587634860356%40Atlassian.JIRA.
[JIRA] (JENKINS-23477) git plugin sparse checkout path field does not expand variables
Title: Message Title jlpinardon commented on JENKINS-23477 Re: git plugin sparse checkout path field does not expand variables I'd really like to be able to use variable with sparse checkout. It would be a great help in having more generic jobs and so on... Please, can we have some update on this ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.155700.1403067217000.16358.1587634800527%40Atlassian.JIRA.
[JIRA] (JENKINS-62028) Jenkins pipeline fails to properly abort loop
Title: Message Title
Christian Werner updated an issue
Jenkins / JENKINS-62028
Jenkins pipeline fails to properly abort loop
Change By:
Christian Werner
# Linux - Debian # Jenkins 2.204.2 # Create pipeline:{code:java}pipeline { agent any stages { stage('Ping') { steps { script { for (def i = 0; i < 500; i++) { echo "currentResult: ${currentBuild.currentResult}" sh "ping 127.0.0.1 -c 1"} } } } }}{code}# run pipeline# Abort pipeline# View build logExpected: pipeline aborts Actual:# The pipeline gets resumed, without interruption# updated code to see the expected behauvior{code}pipeline { agent any stages { stage('Ping') { steps { script { for (def i = 0; i < 500; i++) {if (currentBuild.rawBuild.getActions(jenkins.model.InterruptedBuildAction.class).isEmpty()) {echo "currentResult: ${currentBuild.currentResult}"} else {echo "ABORTED"error("aborted")} sh "ping 127.0.0.1 -c 1" } } } } }}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-62028) Jenkins pipeline fails to properly abort loop
Title: Message Title
Christian Werner created an issue
Jenkins / JENKINS-62028
Jenkins pipeline fails to properly abort loop
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-04-23 09:09
Priority:
Major
Reporter:
Christian Werner
Linux - Debian
Jenkins 2.204.2
Create pipeline:
pipeline {
agent any stages {
stage('Ping') {
steps {
script {
for (def i = 0; i < 500; i++) {
echo "currentResult: ${currentBuild.currentResult}"
sh "ping 127.0.0.1 -c 1"
}
}
}
}
}
}
run pipeline
Abort pipeline
View build log Expected: pipeline aborts Actual:
The pipeline gets resumed, without interruption
updated code to see the expected behauvior
[JIRA] (JENKINS-42655) Active choices parameters not rendering after dsl generation
Title: Message Title
Frank Schullerer commented on JENKINS-42655
Re: Active choices parameters not rendering after dsl generation
Hi Helen, I changed it later to a "Execute Shell" command and within I execute curl:
curl -k --user ':' --data-urlencode "script=$(< /home/jenkins/reloadJobs.groovy)" https://127.0.0.1:9443/scriptText
Nowadays, we have to authenticate to Jenkins via ID and API-Token. My /home/jenkins/reloadJobs.groovy script on file system contains the Code:
for (def job : Jenkins.instance.getItems())
{ job.doReload() }
I hope it works for you too! Frank
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179605.1489140109000.16338.1587632340569%40Atlassian.JIRA.
[JIRA] (JENKINS-47858) ERROR: RocketChat notification failed in login sequence
Title: Message Title Jukka-Pekka Kohtala reopened an issue Hi, Reopening issue as i have similar output pressing "Test connection" from Configure Jenkins. Jenkins version: 2.222.1 RocketChat plugin version: 1.4.8 RocketChat server: 2.4.11 Client error - Could not send message org.json.JSONException: A JSONArray text must start with '[' at 1 [character 2 line 1] at org.json.JSONTokener.syntaxError(JSONTokener.java:433) at org.json.JSONArray.(JSONArray.java:106) at org.json.JSONArray.(JSONArray.java:145) at com.mashape.unirest.http.JsonNode.(JsonNode.java:48) Caused: java.lang.RuntimeException at com.mashape.unirest.http.JsonNode.(JsonNode.java:51) at com.mashape.unirest.http.HttpResponse.(HttpResponse.java:95) Caused: java.lang.RuntimeException at com.mashape.unirest.http.HttpResponse.(HttpResponse.java:106) at com.mashape.unirest.http.HttpClientHelper.request(HttpClientHelper.java:139) Caused: com.mashape.unirest.http.exceptions.UnirestException at com.mashape.unirest.http.HttpClientHelper.request(HttpClientHelper.java:143) at com.mashape.unirest.request.BaseRequest.asJson(BaseRequest.java:68) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatBasicCallAuthentication.doAuthentication(RocketChatBasicCallAuthentication.java:49) Caused: jenkins.plugins.rocketchatnotifier.rocket.errorhandling.RocketClientException: Please check if the server API https://rocket.chat.com/api/v1/login is correct: (Login-Error 1) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatBasicCallAuthentication.doAuthentication(RocketChatBasicCallAuthentication.java:51) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientCallBuilder.buildCall(RocketChatClientCallBuilder.java:95) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientCallBuilder.buildCall(RocketChatClientCallBuilder.java:85) at jenkins.plugins.rocketchatnotifier.rocket.RocketChatClientImpl.getChannels(RocketChatClientImpl.java:95) at jenkins.plugins.rocketchatnotifier.RocketClientImpl.(RocketClientImpl.java:30) at jenkins.plugins.rocketchatnotifier.RocketChatNotifier$DescriptorImpl.doTestConnection(RocketChatNotifier.java:618) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:248) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at
[JIRA] (JENKINS-62027) I am unable to view the log.html or report.html file because of javascript error messages
Title: Message Title Michael Gärtner created an issue Jenkins / JENKINS-62027 I am unable to view the log.html or report.html file because of _javascript_ error messages Issue Type: Bug Assignee: jpiironen Attachments: image-2020-04-23-10-39-15-028.png, image-2020-04-23-10-43-01-175.png, Reports_XML_and_HTML.zip Components: robot-plugin Created: 2020-04-23 08:50 Environment: I am using Jenkins ver. 2.222.1 and the latest version of robot-plugin. On a Windows x64 Server Priority: Critical Reporter: Michael Gärtner I am unable to view the log.html or report.html file because of _javascript_ error messages. I am using Google Chrome to view the Jenkins Dashboard. see atached screen shots Add Comment
[JIRA] (JENKINS-62009) Warnings Next Generation generates java.lang.IllegalAccessError
Title: Message Title David Riemens updated an issue Jenkins / JENKINS-62009 Warnings Next Generation generates java.lang.IllegalAccessError Change By: David Riemens Issue Type: New Feature Bug Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205901.1587557641000.16323.1587631620206%40Atlassian.JIRA.
[JIRA] (JENKINS-42655) Active choices parameters not rendering after dsl generation
Title: Message Title Helen edited a comment on JENKINS-42655 Re: Active choices parameters not rendering after dsl generation [~franksch77] Could you please share more information about how you got this working as a post build step? I can execute the script in the script console and it works. However when I try to automate the process, it does not seem to work as expected. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.179605.1489140109000.16321.1587631560460%40Atlassian.JIRA.
[JIRA] (JENKINS-62008) Expose P4_CLIENT, P4_USER and P4_PORT as the environment variables P4CLIENT, P4USER and P4PORT for scripts
<<< text/html; charset="UTF-8": Unrecognized >>>
[JIRA] (JENKINS-56086) Tabs missing in configuration page after adding plot to freestyle job
Title: Message Title Pedro Gutierrez updated an issue Jenkins / JENKINS-56086 Tabs missing in configuration page after adding plot to freestyle job Change By: Pedro Gutierrez Environment: at least Jenkins 2. 121.2 to 2. 150.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197514.1549889434000.16298.1587631320612%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Labels: P4_SUPPORT P4_DOC jenkins plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16269.1587629640210%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth commented on JENKINS-61943 Re: Jenkins2, P4 Plugin: Error must create client ' to access local files Hi David Rodriguez - Aha. Another Jenkins feature I never knew about. Thanks. Great that it's now working and thanks for correcting the typos in the other job. Yes I agree this should be documented so passed this job to our doc team. I'm going to suggest the following wording, but they will tweak it as needed to match the documentation standards and correct grammar: Note that when using build steps such as 'Execute Shell' the standard Perforce variables P4PORT, P4USER and P4CLIENT are not set in the environment. This is to ensure the plugin does not overwrite variables on preconfigured build environments. If a build step needs access to these values the variables P4_PORT, P4_USER and P4_CLIENT can be used. For example in a shell script: export P4CLIENT=$P4_CLIENT To make the standard variables accessible by default they can be set in the 'Global properties' section on the Jenkins 'Configure System' page. For example: Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Attachment: image-2020-04-23-08-59-08-936.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16263.1587628800209%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Attachment: image-2020-04-23-08-57-39-950.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16260.1587628680199%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Karl Wirth Attachment: image-2020-04-23-08-55-54-786.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16257.1587628560215%40Atlassian.JIRA.
[JIRA] (JENKINS-62026) jenkins quits when executing a shell script halfway through
Title: Message Title
jiayu yu updated an issue
Jenkins / JENKINS-62026
jenkins quits when executing a shell script halfway through
Change By:
jiayu yu
This is the execution script：{code:java} 1 #!/bin/bash 2 Variable () { 3 #. /etc/init.d/functions 4 FileHome="/home/wwwroot" 5 FileJar="jar.ngrok.wangoon.cn" 6 FileBak="bak.ngrok.wangoon.cn" 7 JarName="wms-amazon-api-1.0.0.jar" 8 Date=`date "+%Y-%m-%d-%H:%M:%S"` 9 Pid=`ps -ef|grep ${JarName}|grep -v grep|awk '{print $2}'` 10 Wc=`ps -ef|grep ${JarName}|grep -v grep|wc -l` 11 [[ ! -d ${FileHome}/${FileJar} ]] && mkdir ${FileHome}/${FileJar} 12 [[ ! -d ${FileHome}/${FileBak} ]] && mkdir ${FileHome}/${FileBak} 13 Xms="128m" 14 Xmx="1024m" 15 } 16 Variable 17 18 Kill () { 19 kill -9 ${Pid} 20 } 21 22 Start () { 23 #find ${FileJar} -name "*.jar" -mtime +7|xargs rm -f 24 rm -f ${FileHome}/${FileJar}/${JarName} 25 mv ${FileHome}/${FileBak}/${JarName} ${FileHome}/${FileJar}/${JarName} 26 27 if [ ${Wc} == 1 ] 28 then 29 Kill && echo "进程已杀死！！！" 30 nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 & 31 echo "nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 &" 32 else 33 nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 & 34 echo "nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 &" 35 fi 36 } 37 Start{code} This is the execution result：{code:java}SSH: EXEC: STDOUT/STDERR from command [bash -x /root/shell/WMS-Amazon-Api.sh] ...+ Variable+ FileHome=/home/wwwroot+ FileJar=jar.ngrok.wangoon.cn+ FileBak=bak.ngrok.wangoon.cn+ JarName=wms-amazon-api-1.0.0.jar++ date +%Y-%m-%d-%H:%M:%S+ Date=2020-04-23-07:39:59++ ps -ef++ grep wms-amazon-api-1.0.0.jar++ grep -v grep++ awk '{print $2}'+ Pid=7975++ ps -ef++ grep wms-amazon-api-1.0.0.jar++ grep -v grep++ wc -l+ Wc=1+ [[ ! -d /home/wwwroot/jar.ngrok.wangoon.cn ]]+ [[ ! -d /home/wwwroot/bak.ngrok.wangoon.cn ]]+ Xms=128m+ Xmx=1024m+ Start+ rm -f /home/wwwroot/jar.ngrok.wangoon.cn/wms-amazon-api-1.0.0.jar+ mv /home/wwwroot/bak.ngrok.wangoon.cn/wms-amazon-api-1.0.0.jar /home/wwwroot/jar.ngrok.wangoon.cn/wms-amazon-api-1.0.0.jar+ '[' 1 == 1 ']'+ Kill+ kill -9 7975SSH: EXEC: completed after 200 msSSH: Disconnecting configuration [Technology-192.168.1.215] ...SSH: Transferred 1 file(s)Finished: SUCCESS{code} The ones after the red word are not executed. Is this a script issue or a hardware issue?
[JIRA] (JENKINS-62026) jenkins quits when executing a shell script halfway through
Title: Message Title
jiayu yu updated an issue
Jenkins / JENKINS-62026
jenkins quits when executing a shell script halfway through
Change By:
jiayu yu
This is the execution script： {code:java} 1 #!/bin/bash 2 Variable () { 3 #. /etc/init.d/functions 4 FileHome="/home/wwwroot" 5 FileJar="jar.ngrok.wangoon.cn" 6 FileBak="bak.ngrok.wangoon.cn" 7 JarName="wms-amazon-api-1.0.0.jar" 8 Date=`date "+%Y-%m-%d-%H:%M:%S"` 9 Pid=`ps -ef|grep ${JarName}|grep -v grep|awk '{print $2}'` 10 Wc=`ps -ef|grep ${JarName}|grep -v grep|wc -l` 11 [[ ! -d ${FileHome}/${FileJar} ]] && mkdir ${FileHome}/${FileJar} 12 [[ ! -d ${FileHome}/${FileBak} ]] && mkdir ${FileHome}/${FileBak} 13 Xms="128m" 14 Xmx="1024m" 15 } 16 Variable 17 18 Kill () { 19 kill -9 ${Pid} 20 } 21 22 Start () { 23 #find ${FileJar} -name "*.jar" -mtime +7|xargs rm -f 24 rm -f ${FileHome}/${FileJar}/${JarName} 25 mv ${FileHome}/${FileBak}/${JarName} ${FileHome}/${FileJar}/${JarName} 26 27 if [ ${Wc} == 1 ] 28 then 29 Kill && echo "进程已杀死！！！" 30 nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 & 31 echo "nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 &" 32 else 33 nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 & 34 echo "nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 &" 35 fi 36 } 37 Start{code} This is the execution result： {code:java}SSH: EXEC: STDOUT/STDERR from command [bash -x /root/shell/WMS-Amazon-Api.sh] ...+ Variable+ FileHome=/home/wwwroot+ FileJar=jar.ngrok.wangoon.cn+ FileBak=bak.ngrok.wangoon.cn+ JarName=wms-amazon-api-1.0.0.jar++ date +%Y-%m-%d-%H:%M:%S+ Date=2020-04-23-07:39:59++ ps -ef++ grep wms-amazon-api-1.0.0.jar++ grep -v grep++ awk '{print $2}'+ Pid=7975++ ps -ef++ grep wms-amazon-api-1.0.0.jar++ grep -v grep++ wc -l+ Wc=1+ [[ ! -d /home/wwwroot/jar.ngrok.wangoon.cn ]]+ [[ ! -d /home/wwwroot/bak.ngrok.wangoon.cn ]]+ Xms=128m+ Xmx=1024m+ Start+ rm -f /home/wwwroot/jar.ngrok.wangoon.cn/wms-amazon-api-1.0.0.jar+ mv /home/wwwroot/bak.ngrok.wangoon.cn/wms-amazon-api-1.0.0.jar /home/wwwroot/jar.ngrok.wangoon.cn/wms-amazon-api-1.0.0.jar+ '[' 1 == 1 ']'+ Kill+ kill -9 7975SSH: EXEC: completed after 200 msSSH: Disconnecting configuration [Technology-192.168.1.215] ...SSH: Transferred 1 file(s)Finished: SUCCESS{code}
[JIRA] (JENKINS-62026) jenkins quits when executing a shell script halfway through
Title: Message Title
jiayu yu updated an issue
Jenkins / JENKINS-62026
jenkins quits when executing a shell script halfway through
Change By:
jiayu yu
jenkins quits when executing a shell script halfway through, {code:java} 1 #!/bin/bash 2 Variable () { 3 #. /etc/init.d/functions 4 FileHome="/home/wwwroot" 5 FileJar="jar.ngrok.wangoon.cn" 6 FileBak="bak.ngrok.wangoon.cn" 7 JarName="wms-amazon-api-1.0.0.jar" 8 Date=`date "+%Y-%m-%d-%H:%M:%S"` 9 Pid=`ps -ef|grep ${JarName}|grep -v grep|awk '{print $2}'` 10 Wc=`ps -ef|grep ${JarName}|grep -v grep|wc -l` 11 [[ ! -d ${FileHome}/${FileJar} ]] && mkdir ${FileHome}/${FileJar} 12 [[ ! -d ${FileHome}/${FileBak} ]] && mkdir ${FileHome}/${FileBak} 13 Xms="128m" 14 Xmx="1024m" 15 } 16 Variable 17 18 Kill () { 19 kill -9 ${Pid} 20 } 21 22 Start () { 23 #find ${FileJar} -name "*.jar" -mtime +7|xargs rm -f 24 rm -f ${FileHome}/${FileJar}/${JarName} 25 mv ${FileHome}/${FileBak}/${JarName} ${FileHome}/${FileJar}/${JarName} 26 27 if [ ${Wc} == 1 ] 28 then 29 Kill && echo "进程已杀死！！！" 30 nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 & 31 echo "nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 &" 32 else 33 nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 & 34 echo "nohup java -jar -Xms${Xms} -Xmx${Xmx} ${FileHome}/${FileJar}/${JarName} >/dev/null 2>&1 &" 35 fi 36 } 37 Start{code} This is the execution result：
Add Comment
This message was sent by Atlassian
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Kevin Williamson updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Kevin Williamson Priority: Critical Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16248.1587627360839%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Kevin Williamson assigned an issue to Kevin Williamson Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Kevin Williamson Assignee: Karl Wirth Kevin Williamson Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16246.1587627360782%40Atlassian.JIRA.
[JIRA] (JENKINS-61943) Jenkins2, P4 Plugin: Error must create client ' to access local files
Title: Message Title Kevin Williamson updated an issue Jenkins / JENKINS-61943 Jenkins2, P4 Plugin: Error must create client ' to access local files Change By: Kevin Williamson Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205823.1587087277000.16243.1587627360674%40Atlassian.JIRA.
[JIRA] (JENKINS-62026) jenkins quits when executing a shell script halfway through
Title: Message Title jiayu yu created an issue Jenkins / JENKINS-62026 jenkins quits when executing a shell script halfway through Issue Type: Task Assignee: jiayu yu Components: shell-script-scm-plugin Created: 2020-04-23 07:32 Environment: Linux Priority: Major Reporter: jiayu yu jenkins quits when executing a shell script halfway through, Add Comment
[JIRA] (JENKINS-45315) bfa cannot connect to mongodb using SSL
Title: Message Title Tim Jacomb updated JENKINS-45315 Jenkins / JENKINS-45315 bfa cannot connect to mongodb using SSL Change By: Tim Jacomb Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183455.1499264665000.16234.1587627060982%40Atlassian.JIRA.
[JIRA] (JENKINS-45315) bfa cannot connect to mongodb using SSL
Title: Message Title Tim Jacomb assigned an issue to Tomas Westling Jenkins / JENKINS-45315 bfa cannot connect to mongodb using SSL Change By: Tim Jacomb Assignee: Tim Jacomb Tomas Westling Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183455.1499264665000.16237.1587627061216%40Atlassian.JIRA.
[JIRA] (JENKINS-62010) add possibility to define iterations mode for uft tests in mtbx format
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-62010 add possibility to define iterations mode for uft tests in mtbx format Change By: Radi Berkovich Summary: add possibility to define iterations mode for uft tests in mtbx format Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205903.1587563222000.16230.1587626040076%40Atlassian.JIRA.
