[JIRA] (JENKINS-60461) GIT_COMMIT shouldn't be set when scm git failed on a wrong treeish
Title: Message Title Mark Waite commented on JENKINS-60461 Re: GIT_COMMIT shouldn't be set when scm git failed on a wrong treeish Post build jobs will need to work around the issue by detecting the failure of the predecessor job. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203539.1576154349000.7478.1576299300130%40Atlassian.JIRA.
[JIRA] (JENKINS-60461) GIT_COMMIT shouldn't be set when scm git failed on a wrong treeish
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60461 GIT_COMMIT shouldn't be set when scm git failed on a wrong treeish Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203539.1576154349000.7476.1576299180175%40Atlassian.JIRA.
[JIRA] (JENKINS-60468) Unable to add my windows machine as a Slave.
Title: Message Title
Ian Williams updated an issue
Jenkins / JENKINS-60468
Unable to add my windows machine as a Slave.
Change By:
Ian Williams
Hello Team,I am trying to add my windows machine as a slave to the jenkins but its getting failed with the error in the Screenshot. Could you please help me with this. {{java.io.IOException: Failed to connect to [ http:// 1O 10 .47.97.22: 8ø8OftcpSlaveAgentListener 8080|http: / /1o.47.97.22 : 8/]tcpSlaveAgentListener/: Connection refused: connect}} {{at org.jenkinsci.remoting.engineJnlpAgentEndpointResolver.resolve(inlpAgentEndpointResolver.java:198)}}{{at hudson.remoting.Engine.innerRun(Engine.java:523)}}{{at hudson.remoting.Engine.run(Engine.java:474)}}{{Caused by: java.net.ConnectException: Connection refused: connect}}{{ atjava at java .net.DualStackPlainSocketlmpl.waitForConnect(Native Method)}}{{ atjava at java .net.DualStackPlainSocketlmpl.socketConnect(Unknown Source)}}{{ atjava at java .net.AbstractPlainSocketlmpl.doConnect(Unknown Source)}}{{ atjava at java .net.AbstractPlainSocketlmpl.connectToAddress(Unknown Source)}}{{ atjava at java .net.AbstractPlainSocketlmpl.connect(Unknown Source)}}{{ atjava at java .net.PlainSocketlmpl.connect(Unknown Source)}}{{ atjava at java .net.Socket.connect(Unknown Source)}}{{at sun.net.NetworkClient.doConnect(Unknown Source)}}{{at sun.net.www.http.HttpClient.openServer(Unknown Source)}}{{at sun.net.www.http.HttpClientSl .run(Unknown Source)}}{{at sun.net.www.http.HttpClientSl .run(Unknown Source)}}{{ atjava at java .security.AccessController.doPrivileged(Native Method)}}{{at sun.net.www.http.HttpClient.privilegedOpenServer(Unknown Source)}}{{at sun.net.www.http.HttpClient.openServer(Unknown Source)}}{{at sun.net.www.http.HttpClient.< mit> (Unknown Source)}}{{at sun.net.www.http.HttpClient.New(Unknown Source)}}{{at sun.net.www.http.HttpClient.New(Unknown Source)}}{{at sun.netwww.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)}}{{at sun.netwww.protocolhttp.HttpURLConnection.plainConnectO(Unknown Source)}}{{at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)}}{{at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)}}{{at org.jenkinsci.remoting.engineJnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:195)}}{{... 2 more}}
[JIRA] (JENKINS-60468) Unable to add my windows machine as a Slave.
Title: Message Title
Ian Williams updated an issue
Jenkins / JENKINS-60468
Unable to add my windows machine as a Slave.
Change By:
Ian Williams
Hello Team,I am trying to add my windows machine as a slave to the jenkins but its getting failed with the error in the Screenshot. Could you please help me with this. !image-2019-12-13-08-55- {{java.io.IOException: Failed to connect to http://1O. 47 -863 . png! 97.22:8ø8OftcpSlaveAgentListener/: Connection refused: connect}}{{at org.jenkinsci.remoting.engineJnlpAgentEndpointResolver.resolve(inlpAgentEndpointResolver.java:198)}}{{at hudson.remoting.Engine.innerRun(Engine.java:523)}}{{at hudson.remoting.Engine.run(Engine.java:474)}}{{Caused by: java.net.ConnectException: Connection refused: connect}}{{atjava.net.DualStackPlainSocketlmpl.waitForConnect(Native Method)}}{{atjava.net.DualStackPlainSocketlmpl.socketConnect(Unknown Source)}}{{atjava.net.AbstractPlainSocketlmpl.doConnect(Unknown Source)}}{{atjava.net.AbstractPlainSocketlmpl.connectToAddress(Unknown Source)}}{{atjava.net.AbstractPlainSocketlmpl.connect(Unknown Source)}}{{atjava.net.PlainSocketlmpl.connect(Unknown Source)}}{{atjava.net.Socket.connect(Unknown Source)}}{{at sun.net.NetworkClient.doConnect(Unknown Source)}}{{at sun.net.www.http.HttpClient.openServer(Unknown Source)}}{{at sun.net.www.http.HttpClientSl .run(Unknown Source)}}{{at sun.net.www.http.HttpClientSl .run(Unknown Source)}}{{atjava.security.AccessController.doPrivileged(Native Method)}}{{at sun.net.www.http.HttpClient.privilegedOpenServer(Unknown Source)}}{{at sun.net.www.http.HttpClient.openServer(Unknown Source)}}{{at sun.net.www.http.HttpClient.< mit> (Unknown Source)}}{{at sun.net.www.http.HttpClient.New(Unknown Source)}}{{at sun.net.www.http.HttpClient.New(Unknown Source)}}{{at sun.netwww.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)}}{{at sun.netwww.protocolhttp.HttpURLConnection.plainConnectO(Unknown Source)}}{{at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)}}{{at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)}}{{at org.jenkinsci.remoting.engineJnlpAgentEndpointResolver.resolve(JnlpAgentEndpointResolver.java:195)}}{{... 2 more}}
Add Comment
[JIRA] (JENKINS-59191) SPAM-Not an issue
Title: Message Title Ioannis Moutsatsos updated JENKINS-59191 Jenkins / JENKINS-59191 SPAM-Not an issue Change By: Ioannis Moutsatsos Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201632.1567441959000.7470.1576286940258%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Ioannis Moutsatsos updated JENKINS-60319 Jenkins / JENKINS-60319 Reactive Parameter ignores toString Change By: Ioannis Moutsatsos Status: Fixed but Unreleased Closed Resolution: Fixed Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203316.1574954163000.7466.1576286580290%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Ioannis Moutsatsos updated JENKINS-60319 Cast Objects to String. The returned Groovy array should always be a String array Jenkins / JENKINS-60319 Reactive Parameter ignores toString Change By: Ioannis Moutsatsos Status: Open Fixed but Unreleased Assignee: Bruno P. Kinoshita Ioannis Moutsatsos Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title
Ioannis Moutsatsos commented on JENKINS-60319
Re: Reactive Parameter ignores toString
class Choice {
String tag
String branch
@Override
String toString() {
return tag + ' / ' + branch
}
}
def obj1 = new Choice(branch: '1', tag:"3")
def obj2 = new Choice(branch: '2', tag:"4")
println obj1.getClass()
return [obj1 as String, obj2 as String ]
This works as expected. It seems to me that the original array is not 'stingified' .You need to explicity cast the Choice objects to String.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google 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.203316.1574954163000.7461.1576286400415%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-60319 Reactive Parameter ignores toString Change By: Ioannis Moutsatsos Attachment: image-2019-12-13-20-19-21-140.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203316.1574954163000.7458.1576286400278%40Atlassian.JIRA.
[JIRA] (JENKINS-60319) Reactive Parameter ignores toString
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-60319 Reactive Parameter ignores toString Change By: Ioannis Moutsatsos Attachment: image-2019-12-13-20-15-51-433.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203316.1574954163000.7455.1576286160207%40Atlassian.JIRA.
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title Konrad Scherer commented on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly Something to check is the EKS user configuration and make sure the credentials available to the Jenkins user are properly configured with a Kubernetes role in EKS: https://docs.aws.amazon.com/eks/latest/userguide/add-user-role.html Only the credentials that created the EKS cluster have a proper Kubernetes role by default. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.192436.1531774635000.7444.1576285200670%40Atlassian.JIRA.
[JIRA] (JENKINS-60219) deploy-websphere-plugin does throws exception in isArtifactInstalled method
Title: Message Title Greg Vilardi closed an issue as Not A Defect Removed the inconsistent jar file. Jenkins / JENKINS-60219 deploy-websphere-plugin does throws exception in isArtifactInstalled method Change By: Greg Vilardi Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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 t
[JIRA] (JENKINS-60219) deploy-websphere-plugin does throws exception in isArtifactInstalled method
Title: Message Title Greg Vilardi commented on JENKINS-60219 Re: deploy-websphere-plugin does throws exception in isArtifactInstalled method I've resolved this issue, and wanted to document it for anyone who finds this in the future. The root cause of this issue was that there was a jar file from WebSphere Portal version 8 that was accidentally added to the Jenkins classpath when I installed the plugin. I was working with Portal 9. It would be useful (to me) to be able to have multiple versions of portal supported by the same Jenkins/plugin installation. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203192.1574211214000.7440.1576283700132%40Atlassian.JIRA.
[JIRA] (JENKINS-60219) deploy-websphere-plugin does throws exception in isArtifactInstalled method
Title: Message Title Greg Vilardi assigned an issue to Greg Vilardi Jenkins / JENKINS-60219 deploy-websphere-plugin does throws exception in isArtifactInstalled method Change By: Greg Vilardi Assignee: Greg Vilardi Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203192.1574211214000.7439.1576283640314%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux updated an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Change By: Heather Lemieux This plugin’s configuration section, within the “Manage → System Configuration” area of Jenkins, has a bug that requires us to always re-set wipes the Alternate EC2 url and region parameters. In the event that someone opens the System Configuration page and performs a “Save” without resetting these fields, Jenkins will get into a state where it’s either partially or completely unusable due to it saving a configuration with no region set, which shouldn't be allowed.Attached are two examples of what has happened when a save occurs and the fields were not set.Additionally, when you go to the configuration page and try to reset the field fields an error is returned via the plugin, and saving anyway also still results in the region not being set. A screenshot of that is included as well.In order to resolve the issue, we have to go onto the ec2 instance where jenkins is running, edit the config.xml and restart the jenkins docker container. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux updated an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Change By: Heather Lemieux Attachment: region in the config.xml is empty.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203569.1576277084000.7425.1576279860145%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux updated an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Change By: Heather Lemieux This plugin’s configuration section, within the “Manage → System Configuration” area of Jenkins, has a bug that requires us to always re-set the Alternate EC2 url and region parameters. In the event that someone opens the System Configuration page and performs a “Save” without resetting these fields, Jenkins will get into a state where it’s either partially or completely unusable due to it saving a configuration with no region set, which shouldn't be allowed.Attached are two examples of what has happened when a save occurs and the fields were not set.Additionally, when you go to the configuration page and try to reset the field an error is returned via the plugin, and saving anyway also results in the region not being set. A screenshot of that is included as well. In order to resolve the issue, we have to go onto the ec2 instance where jenkins is running, edit the config.xml and restart the jenkins docker container. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux updated an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Change By: Heather Lemieux Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203569.1576277084000.7421.1576279320354%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux updated an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Change By: Heather Lemieux This plugin’s configuration section, within the “Manage → System Configuration” area of Jenkins, has a bug that requires us to always re-set the Alternate EC2 url and region parameters. In the event that someone opens the System Configuration page and performs a “Save” without resetting these fields, Jenkins will get into a state where it’s either partially or completely unusable due to it saving a configuration with no region set, which shouldn't be allowed.Attached are two examples of what has happened when a save occurs and the fields were not set. Additionally, when you go to the configuration page and try to reset the field an error is returned via the plugin, however and saving still sets anyway also results in the region correctly not being set . A screenshot of that is included as well. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60454) Jenkins.instance is missing after restart
Title: Message Title Chun-Ta Kung commented on JENKINS-60454 Re: Jenkins.instance is missing after restart I see. Will try. Below is the os-release information. NAME="Ubuntu" VERSION="14.04.6 LTS, Trusty Tahr" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 14.04.6 LTS" VERSION_ID="14.04" Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203532.1576121478000.7417.1576278961496%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux updated an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Change By: Heather Lemieux Attachment: Screen Shot 2019-12-05 at 11.24.45 AM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203569.1576277084000.7402.1576277280146%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux updated an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Change By: Heather Lemieux Attachment: Screen Shot 2019-12-05 at 11.24.45 AM.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203569.1576277084000.7400.1576277220387%40Atlassian.JIRA.
[JIRA] (JENKINS-60482) EC2 Alternate Endpoint and Region are reset when managing jenkins configuration
Title: Message Title Heather Lemieux created an issue Jenkins / JENKINS-60482 EC2 Alternate Endpoint and Region are reset when managing jenkins configuration Issue Type: Bug Assignee: FABRIZIO MANFREDI Attachments: Configuration Page with reset field.png, Resetting field results in an error.png, Screen Shot 2019-12-05 at 11.24.45 AM.png, Screen Shot 2019-12-13 at 4.44.50 PM.png Components: ec2-plugin Created: 2019-12-13 22:44 Environment: os.name: Linux os.version: 4.14.106-79.86.amzn1.x86_64 plugin version: 1.45 java.version: 1.8.0_212 Labels: plugin configuration Priority: Minor Reporter: Heather Lemieux This plugin’s configuration section, within the “Manage → System Configuration” area of Jenkins, has a bug that requires us to always re-set the Alternate EC2 url and region parameters. In the event that someone opens the System Configuration page and performs a “Save” without resetting these fields, Jenkins will get into a state where it’s either partially or completely unusable due to it saving a configuration with no region set, which shouldn't be allowed. Attached are two examples of what has happened when a save occurs and the fields were not set. Additionally, when you go to the configuration page and try to reset the field an error is returned via the plugin, however saving still sets the region correctly . A screenshot of that is included as wel
[JIRA] (JENKINS-60481) Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options`
Title: Message Title Basil Crow updated JENKINS-60481 Jenkins / JENKINS-60481 Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options` Change By: Basil Crow Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203568.1576270896000.7394.1576276080490%40Atlassian.JIRA.
[JIRA] (JENKINS-60481) Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options`
Title: Message Title Basil Crow updated JENKINS-60481 Jenkins / JENKINS-60481 Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options` Change By: Basil Crow Status: In Review Fixed but Unreleased Assignee: Bryan Jensen Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203568.1576270896000.7396.1576276080525%40Atlassian.JIRA.
[JIRA] (JENKINS-60481) Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options`
Title: Message Title Basil Crow started work on JENKINS-60481 Change By: Basil Crow Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203568.1576270896000.7392.1576276080452%40Atlassian.JIRA.
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title Marcin Romaszewicz commented on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly Since originally filing this bug, I've been using service account based kubeconfig files without issue against EKS. It's easier than using the aws-iam-authenticator, since all you do is bake in a user token into your kubeconfig, and you can constrain it to namespaces or whatever. Doing the same with IAM credentials is more annoying. Try that route instead of directly using your IAM role for EKS. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.192436.1531774635000.7381.1576274820323%40Atlassian.JIRA.
[JIRA] (JENKINS-54578) Cannot delete last category
Title: Message Title Basil Crow updated JENKINS-54578 Jenkins / JENKINS-54578 Cannot delete last category Change By: Basil Crow Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.195362.1542034246000.7375.1576273620231%40Atlassian.JIRA.
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title
Tallis Vanek edited a comment on JENKINS-52593
Re: Support EKS authentication, or specifying a kubeconfig directly
Thanks for the summary Konrad [~kscherer] , I was able to follow along with my setup.My Jenkins master is trying to authenticate with the entire kube config tucked away in a secret. Also, I can see that my jenkins user on the master is able to run the token 'aws eks get-token' successfully.I am however running into the "Message: Unauthorized! Token may have expired! " issue, even with my Jenkins master configured to use the correct java opt{code:java}/etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=60 -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war ...{code}I'm wondering what else can be involved, and how I can verify that the cache is actually the issue. Do you have any ideas?Some info:{code:java}openjdk version "1.8.0_222"ami linux: 4.14.152-127.182.amzn2.x86_64jenkins kube plugin: org.csanchez.jenkins.plugins:kubernetes:1.22.0Jenkins: 2.208 kubectl: v1.17.0 / v1.14.8-eks-b8860faws-cli/1.16.303 Python/2.7.16 Linux/4.14.152-127.182.amzn2.x86_64 botocore/1.13.39{code}Thanks in advance.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google 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.192436.1531774635000.7360.1576
[JIRA] (JENKINS-52593) Support EKS authentication, or specifying a kubeconfig directly
Title: Message Title Tallis Vanek commented on JENKINS-52593 Re: Support EKS authentication, or specifying a kubeconfig directly Thanks for the summary Konrad, I was able to follow along with my setup. My Jenkins master is trying to authenticate with the entire kube config tucked away in a secret. Also, I can see that my jenkins user on the master is able to run the token 'aws eks get-token' successfully. I am however running into the "Message: Unauthorized! Token may have expired! " issue, even with my Jenkins master configured to use the correct java opt /etc/alternatives/java -Dcom.sun.akuma.Daemon=daemonized -Dorg.csanchez.jenkins.plugins.kubernetes.clients.cacheExpiration=60 -DJENKINS_HOME=/var/lib/jenkins -jar /usr/lib/jenkins/jenkins.war ... I'm wondering what else can be involved, and how I can verify that the cache is actually the issue. Do you have any ideas? Some info: openjdk version "1.8.0_222" ami linux: 4.14.152-127.182.amzn2.x86_64 jenkins kube plugin: org.csanchez.jenkins.plugins:kubernetes:1.22.0 Jenkins: 2.208 kubectl: v1.17.0 / v1.14.8-eks-b8860f aws-cli/1.16.303 Python/2.7.16 Linux/4.14.152-127.182.amzn2.x86_64 botocore/1.13.39 Thanks in advance. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Jennifer Jager assigned an issue to Oleg Nenashev Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Jennifer Jager Assignee: Jennifer Jager Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187698.1515697318000.7331.1576272060828%40Atlassian.JIRA.
[JIRA] (JENKINS-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Jennifer Jager assigned an issue to Unassigned Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Jennifer Jager Assignee: Jennifer Jager Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187698.1515697318000.7342.1576272061024%40Atlassian.JIRA.
[JIRA] (JENKINS-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Jennifer Jager assigned an issue to Jennifer Jager Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Jennifer Jager Assignee: Oleg Nenashev Jennifer Jager Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187698.1515697318000.7325.1576272060715%40Atlassian.JIRA.
[JIRA] (JENKINS-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Jennifer Jager assigned an issue to Jennifer Jager Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Jennifer Jager Assignee: Oleg Nenashev Jennifer Jager Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187698.1515697318000.7340.1576272060991%40Atlassian.JIRA.
[JIRA] (JENKINS-48900) Show "Full Name" on Assign Roles page?
Title: Message Title Jennifer Jager assigned an issue to Oleg Nenashev Jenkins / JENKINS-48900 Show "Full Name" on Assign Roles page? Change By: Jennifer Jager Assignee: Jennifer Jager Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187698.1515697318000.7319.1576272000271%40Atlassian.JIRA.
[JIRA] (JENKINS-60481) Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options`
Title: Message Title Bryan Jensen created an issue Jenkins / JENKINS-60481 Add @Symbol to ThrottleJobProperty to expose in declarative pipeline `options` Issue Type: Improvement Assignee: Unassigned Components: throttle-concurrent-builds-plugin Created: 2019-12-13 21:01 Environment: Jenkins 2.202, throttle-concurrent-buids-plugin 2.0.1, Pipeline: Declarative 1.5.0 Labels: plugin pipeline Priority: Minor Reporter: Bryan Jensen When using the Declarative Directive Generator for the `options` block, there's a throttle option that corresponds to the throttle step, but nothing seems to be exposed for the throttle job property. Given we prefer to define our config in code whenever possible (leaves a papertrail), it would be nice to be able to define the "Throttle Concurrent Builds" job property in our `Jenkinsfile`s as well. From what I can tell, the solution here would be very similar to what's described in https://issues.jenkins-ci.org/browse/JENKINS-50561
[JIRA] (JENKINS-60480) github is deprecating basic authentication using password
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-60480 github is deprecating basic authentication using password Issue Type: New Feature Assignee: Kirill Merkushev Components: github-api-plugin, github-branch-source-plugin, github-plugin Created: 2019-12-13 20:27 Priority: Minor Reporter: Josh Soref You recently used a password to access an endpoint through the GitHub API using okhttp/2.7.5. We will deprecate basic authentication using password to this endpoint soon: https://api.github.com/repositories/155774655 We recommend using a personal access token (PAT) with the appropriate scope to access this endpoint instead. Visit https://github.com/settings/tokens for more information. This might be just something that admins need to deal w/, but it would be helpful if there was a migration page explaining what to do from the jenkins side. (it isn't particularly obvious to me) Add Comment
[JIRA] (JENKINS-53321) Test functioning across restarts
Title: Message Title Alex Earl updated JENKINS-53321 Jenkins / JENKINS-53321 Test functioning across restarts Change By: Alex Earl Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193402.1535548072000.7258.1576265940435%40Atlassian.JIRA.
[JIRA] (JENKINS-53321) Test functioning across restarts
Title: Message Title Alex Earl commented on JENKINS-53321 Re: Test functioning across restarts Fixed via https://github.com/jenkinsci/webhook-step-plugin/pull/19 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193402.1535548072000.7256.1576265940407%40Atlassian.JIRA.
[JIRA] (JENKINS-60479) Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Title: Message Title
Matthew Brunton created an issue
Jenkins / JENKINS-60479
Building a matrix with exclusions in a declarative pipeline using a pipeline library finds no branches to run
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
p4-plugin, pipeline-model-definition-plugin
Created:
2019-12-13 19:34
Environment:
Docker image jenkins/jenkins:2.208 in a docker network with a Perforce instance (https://github.com/p4paul/helix-docker) using p4-plugin 1.10.7
Priority:
Major
Reporter:
Matthew Brunton
I have run into an issue when attempting to build a matrix in a declarative pipeline using a pipeline library through p4. If the excludes section is used, the pipeline is run successfully, but it reports that there are no branches to run. Without the excludes section, all targets in the matrix are run. To reproduce, I created a Perforce instance with Jenkins in a docker network and installed the p4-plugin 1.10.7. I then created a multibranch pipeline with a source of //testDepot/... from perforce. I created two streams and a library stream. In the first stream, I created a Jenkinsfile:
@Library('test-pipeline') _
lib()
Where the test-pipeline is a pipeline library at //testDepot/libstream/... with the pipeline code in //testDepot/libstream/vars/lib.groovy
def call()
{
pipeline
{
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Pierre Beitz commented on JENKINS-60421 Re: NPE when saving Jenkins configuration if audit console logger is added in JCASC Alexander Smirnov thanks for the feedback! I just released version 3.2 of the plugin with this fix, it should be available in the next hours, time for the update centers to refresh Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203493.1575991654000.7251.1576265220212%40Atlassian.JIRA.
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Pierre Beitz updated JENKINS-60421 Jenkins / JENKINS-60421 NPE when saving Jenkins configuration if audit console logger is added in JCASC Change By: Pierre Beitz Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203493.1575991654000.7249.1576265160454%40Atlassian.JIRA.
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-60421 NPE when saving Jenkins configuration if audit console logger is added in JCASC Change By: Pierre Beitz Labels: 3.2-fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203493.1575991654000.7247.1576265160417%40Atlassian.JIRA.
[JIRA] (JENKINS-60478) When job fails, stack trace is Null
Title: Message Title
aflat updated an issue
Jenkins / JENKINS-60478
When job fails, stack trace is Null
Change By:
aflat
Priority:
Major Minor
My pipeline script has {code}try{ jobToRun = build job: jobName, parameters: jobParameters jobStatus = jobToRun.result print "Job: ${jobName} completed, result was ${jobToRun.result}" } catch (Exception e){ println "DEBUG: error message is: " + e.message}{code}Which used to work about a month ago. Updated plugins and core, and now e.message == NULLe == org.jenkinsci.plugins.workflow.steps.FlowInterruptedExceptionThis is when $jobName != SUCCESS. A bit annoying that a build call throws an exception in the first place Changing the severity, as I can use propagate which solves all the issues I was trying to solve by catching the exception in the first place.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60478) When job fails, stack trace is Null
Title: Message Title
aflat updated an issue
Jenkins / JENKINS-60478
When job fails, stack trace is Null
Change By:
aflat
My pipeline script has {code}try{ jobToRun = build job: jobName, parameters: jobParameters jobStatus = jobToRun.result print "Job: ${jobName} completed, result was ${jobToRun.result}" } catch (Exception e){ println "DEBUG: error message is: " + e.message}{code}Which used to work about a month ago. Updated plugins and core, and now " e " .message == NULL e == org.jenkinsci.plugins.workflow.steps.FlowInterruptedExceptionThis is when $jobName != SUCCESS. A bit annoying that a build call throws an exception in the first place
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google 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-60095) Windows paths
Title: Message Title
William Hetherington edited a comment on JENKINS-60095
Re: Windows paths
Hi Ivan,I don't have a SAML configuration I can use for testing until next week, (I'm waiting on an Okta sandbox being rebuilt), but, I think this is not sufficient to fix this in Windows.{code:java}public HttpResponse doMetadata(StaplerRequest request, StaplerResponse response) {return new SamlSPMetadataWrapper(getSamlPluginConfig(), request, response).get(); }{code}I think that the path for the metadata that is being passed is incorrect. Without an active session, Jenkins does not properly redirect to Okta, when the plugin is deployed on a Windows host, and I see the following in the logs: {code:java}[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#: Using SP entity ID Jenkins-users[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Writing sp metadata to C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Attempting to create directory structure for C:\Jenkins[id=14] WARNING o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Could not construct the directory structure for SP metadata C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.c.DefaultSignatureSigningParametersProvider#build: Created signature signing parameters.{code} My guess is, the path being passed is *C:\Jenkins\saml-sp-metadata.xml* - and this is ultimately causing pac4j to properly not find the *saml-sp-metadata.xml*: (Windows paths usually want escaped \'s ?) [https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/SamlSPMetadataWrapper.java#L42-L44] Based on this failing: [https://github.com/pac4j/pac4j/blob/f82b377690f400f518145a4d543acb187d4dd4ac/pac4j-saml/src/main/java/org/pac4j/saml/metadata/SAML2ServiceProviderMetadataResolver.java#L134-L160] Do you have any thoughts here? I will try to update this issue as soon as I have Idp config for testing, some time next week.
Add Comment
[JIRA] (JENKINS-60095) Windows paths
Title: Message Title
William Hetherington edited a comment on JENKINS-60095
Re: Windows paths
Hi Ivan,I don't have a SAML configuration I can use for testing until next week, (I'm waiting on an Okta sandbox being rebuilt), but, I think this is not sufficient to fix this in Windows.{code:java}public HttpResponse doMetadata(StaplerRequest request, StaplerResponse response) {return new SamlSPMetadataWrapper(getSamlPluginConfig(), request, response).get(); }{code}I think that the path for the metadata that is being passed is incorrect. Without an active session, Jenkins does not properly redirect to Okta, when the plugin is deployed on a Windows host, and I see the following in the logs: {code:java}[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#: Using SP entity ID Jenkins-users[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Writing sp metadata to C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Attempting to create directory structure for C:\Jenkins[id=14] WARNING o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Could not construct the directory structure for SP metadata C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.c.DefaultSignatureSigningParametersProvider#build: Created signature signing parameters.{code} My guess is, the path being passed is *C:\Jenkins\saml-sp-metadata.xml* - and this is ultimately causing pac4j to properly find the *saml-sp-metadata.xml*: ( it should probably be like *C: Windows paths usually want escaped \ \Jenkins\\**saml-sp-metadata.xml* 's ?) [https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/SamlSPMetadataWrapper.java#L42-L44] Based on this failing: [https://github.com/pac4j/pac4j/blob/f82b377690f400f518145a4d543acb187d4dd4ac/pac4j-saml/src/main/java/org/pac4j/saml/metadata/SAML2ServiceProviderMetadataResolver.java#L134-L160] Do you have any thoughts here? I will try to update this issue as soon as I have Idp config for testing, some time next week.
Add Comment
[JIRA] (JENKINS-60095) Windows paths
Title: Message Title
William Hetherington edited a comment on JENKINS-60095
Re: Windows paths
Hi Ivan,I don't have a SAML configuration I can use for testing until next week, (I'm waiting on an Okta sandbox being rebuilt), but, I think this is not sufficient to fix this in Windows.{code:java}public HttpResponse doMetadata(StaplerRequest request, StaplerResponse response) {return new SamlSPMetadataWrapper(getSamlPluginConfig(), request, response).get(); }{code}I think that the path for the metadata that is being passed is incorrect. Without an active session, Jenkins does not properly redirect to Okta, when the plugin is deployed on a Windows host, and I see the following in the logs: {code:java}[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#: Using SP entity ID Jenkins-users[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Writing sp metadata to C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Attempting to create directory structure for C:\Jenkins[id=14] WARNING o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Could not construct the directory structure for SP metadata C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.c.DefaultSignatureSigningParametersProvider#build: Created signature signing parameters.{code} My guess is, the path being passed is *C:\Jenkins\saml-sp-metadata.xml* - and this is ultimately causing pac4j to properly find the *saml-sp-metadata.xml*: (it should probably be like *C:\\Jenkins\\ ** saml-sp-metadata.xml* [https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/SamlSPMetadataWrapper.java#L42-L44] Based on this failing: [https://github.com/pac4j/pac4j/blob/f82b377690f400f518145a4d543acb187d4dd4ac/pac4j-saml/src/main/java/org/pac4j/saml/metadata/SAML2ServiceProviderMetadataResolver.java#L134-L160] Do you have any thoughts here? I will try to update this issue as soon as I have Idp config for testing, some time next week.
Add Comment
[JIRA] (JENKINS-60095) Windows paths
Title: Message Title
William Hetherington edited a comment on JENKINS-60095
Re: Windows paths
Hi Ivan,I don't have a SAML configuration I can use for testing until next week, (I'm waiting on an Okta sandbox being rebuilt), but, I think this is not sufficient to fix this in Windows.{code:java}public HttpResponse doMetadata(StaplerRequest request, StaplerResponse response) {return new SamlSPMetadataWrapper(getSamlPluginConfig(), request, response).get(); }{code}I think that the path for the metadata that is being passed is incorrect. Without an active session, Jenkins does not properly redirect to Okta, when the plugin is deployed on a Windows host, and I see the following in the logs: {code:java}[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#: Using SP entity ID Jenkins-users[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Writing sp metadata to C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Attempting to create directory structure for C:\Jenkins[id=14] WARNING o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Could not construct the directory structure for SP metadata C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.c.DefaultSignatureSigningParametersProvider#build: Created signature signing parameters.{code} My guess is, the path being passed is `C:\Jenkins\saml-sp-metadata.xml` - and this is ultimately causing pac4j to properly find the `saml-sp-metadata.xml`: (it should probably be like `C:\\Jenkins\\saml-sp-metadata.xml`[https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/SamlSPMetadataWrapper.java#L42-L44] Based on this failing: [https://github.com/pac4j/pac4j/blob/f82b377690f400f518145a4d543acb187d4dd4ac/pac4j-saml/src/main/java/org/pac4j/saml/metadata/SAML2ServiceProviderMetadataResolver.java#L134-L160] Do you have any thoughts here? I will try to update this issue as soon as I have Idp config for testing, some time next week.
Add Comment
[JIRA] (JENKINS-60095) Windows paths
Title: Message Title
William Hetherington edited a comment on JENKINS-60095
Re: Windows paths
Hi Ivan,I don't have a SAML configuration I can use for testing until next week, (I'm waiting on an Okta sandbox being rebuilt), but, I think this is not sufficient to fix this in Windows.{code:java}public HttpResponse doMetadata(StaplerRequest request, StaplerResponse response) {return new SamlSPMetadataWrapper(getSamlPluginConfig(), request, response).get(); }{code}I think that the path for the metadata that is being passed is incorrect. Without an active session, Jenkins does not properly redirect to Okta, when the plugin is deployed on a Windows host, and I see the following in the logs: {code:java}[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#: Using SP entity ID Jenkins-users[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Writing sp metadata to C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Attempting to create directory structure for C:\Jenkins[id=14] WARNING o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Could not construct the directory structure for SP metadata C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.c.DefaultSignatureSigningParametersProvider#build: Created signature signing parameters.{code} My guess is, the path being passed is ` * C:\Jenkins\saml-sp-metadata.xml ` * - and this is ultimately causing pac4j to properly find the ` * saml-sp-metadata.xml ` * : (it should probably be like ` * C:\\Jenkins\\saml-sp-metadata.xml ` * [https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/SamlSPMetadataWrapper.java#L42-L44] Based on this failing: [https://github.com/pac4j/pac4j/blob/f82b377690f400f518145a4d543acb187d4dd4ac/pac4j-saml/src/main/java/org/pac4j/saml/metadata/SAML2ServiceProviderMetadataResolver.java#L134-L160] Do you have any thoughts here? I will try to update this issue as soon as I have Idp config for testing, some time next week.
Add Comment
[JIRA] (JENKINS-60095) Windows paths
Title: Message Title
William Hetherington edited a comment on JENKINS-60095
Re: Windows paths
Hi Ivan,I don't have a SAML configuration I can use for testing until next week, (I'm waiting on an Okta sandbox being rebuilt), but, I think this is not sufficient to fix this in Windows.{code:java}public HttpResponse doMetadata(StaplerRequest request, StaplerResponse response) {return new SamlSPMetadataWrapper(getSamlPluginConfig(), request, response).get(); }{code}I think that the path for the metadata that is being passed is incorrect. Without an active session, Jenkins does not properly redirect to Okta, when the plugin is deployed on a Windows host, and I see the following in the logs: {code:java}[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#: Using SP entity ID Jenkins-users[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Writing sp metadata to C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Attempting to create directory structure for C:\Jenkins[id=14] WARNING o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Could not construct the directory structure for SP metadata C:\Jenkins\saml-sp-metadata.xml[id=14] INFO o.p.s.c.DefaultSignatureSigningParametersProvider#build: Created signature signing parameters.{code} My guess is, the path being passed is `C:\Jenkins\ Windows saml-sp-metadata.xml ` - and this is ultimately causing pac4j to properly find the `saml-sp-metadata.xml`: (it should probably be like `C:\\Jenkins\\saml-sp-metadata.xml` [https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/SamlSPMetadataWrapper.java#L42-L44] Based on this failing: [https://github.com/pac4j/pac4j/blob/f82b377690f400f518145a4d543acb187d4dd4ac/pac4j-saml/src/main/java/org/pac4j/saml/metadata/SAML2ServiceProviderMetadataResolver.java#L134-L160] Do you have any thoughts here? I will try to update this issue as soon as I have Idp config for testing, some time next week.
Add Comment
[JIRA] (JENKINS-60095) Windows paths
Title: Message Title
William Hetherington commented on JENKINS-60095
Re: Windows paths
Hi Ivan, I don't have a SAML configuration I can use for testing until next week, (I'm waiting on an Okta sandbox being rebuilt), but, I think this is not sufficient to fix this in Windows.
public HttpResponse doMetadata(StaplerRequest request, StaplerResponse response) {
return new SamlSPMetadataWrapper(getSamlPluginConfig(), request, response).get();
}
I think that the path for the metadata that is being passed is incorrect. Without an active session, Jenkins does not properly redirect to Okta, when the plugin is deployed on a Windows host, and I see the following in the logs:
[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API
[id=14] INFO o.o.c.c.InitializationService#initialize: Initializing OpenSAML using the Java Services API
[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#: Using SP entity ID Jenkins-users
[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Writing sp metadata to C:\Jenkins\saml-sp-metadata.xml
[id=14] INFO o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Attempting to create directory structure for C:\Jenkins
[id=14] WARNING o.p.s.m.SAML2ServiceProviderMetadataResolver#resolve: Could not construct the directory structure for SP metadata C:\Jenkins\saml-sp-metadata.xml
[id=14] INFO o.p.s.c.DefaultSignatureSigningParametersProvider#build: Created signature signing parameters.
My guess is, the path being passed is `C:\Jenkins\Windows` - and this is ultimately causing pac4j to properly find the `saml-sp-metadata.xml`: https://github.com/jenkinsci/saml-plugin/blob/master/src/main/java/org/jenkinsci/plugins/saml/SamlSPMetadataWrapper.java#L42-L44 Based on this failing: https://github.com/pac4j/pac4j/blob/f82b377690f400f518145a4d543acb187d4dd4ac/pac4j-saml/src/main/java/org/pac4j/saml/metadata/SAML2ServiceProviderMetadataResolver.java#L134-L160 Do you have any thoughts here? I will try to update this issue as soon as I have Idp config for testing, some time next week.
Add Comment
[JIRA] (JENKINS-60095) Windows paths
Title: Message Title William Hetherington updated JENKINS-60095 Jenkins / JENKINS-60095 Windows paths Change By: William Hetherington Resolution: Fixed Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202940.1573154102000.7236.1576259820109%40Atlassian.JIRA.
[JIRA] (JENKINS-59107) User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2)
Title: Message Title Matt Sicker commented on JENKINS-59107 Re: User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2) PR to fix this open for review: https://github.com/jenkinsci/jenkins/pull/4394 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201530.1566934526000.7229.1576257180670%40Atlassian.JIRA.
[JIRA] (JENKINS-59107) User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2)
Title: Message Title Matt Sicker updated JENKINS-59107 Jenkins / JENKINS-59107 User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2) Change By: Matt Sicker Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201530.1566934526000.7227.1576257180629%40Atlassian.JIRA.
[JIRA] (JENKINS-60478) When job fails, stack trace is Null
Title: Message Title
aflat created an issue
Jenkins / JENKINS-60478
When job fails, stack trace is Null
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-12-13 17:10
Environment:
jenkins core: 2.200
Priority:
Major
Reporter:
aflat
My pipeline script has
try{
jobToRun = build job: jobName, parameters: jobParameters
jobStatus = jobToRun.result
print "Job: ${jobName} completed, result was ${jobToRun.result}"
}
catch (Exception e){
println "DEBUG: error message is: " + e.message
}
Which used to work about a month ago. Updated plugins and core, and now "e" == NULL
Add Comment
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) in your testing, please do a sync step and then an unshelve step and check both are in the jenkins changes summary page. thanks Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7219.1576255320188%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) Am on jenkins 2.176.4 with p4-plugin 1.10.6 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7211.1576255020151%40Atlassian.JIRA.
[JIRA] (JENKINS-60477) Jenkins job is over running while creating jar files
Title: Message Title Divya Ganesan created an issue Jenkins / JENKINS-60477 Jenkins job is over running while creating jar files Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2019-12-13 16:35 Environment: Prod Priority: Critical Reporter: Divya Ganesan Hi, I can see the below error in job which is used to create jar file nad the job is overrunning and occupied 99% of CPU. I have also configured the job by increasing heap size in "Invoke Ant" session by giving '-Xx1024m' . But still facing the same issue. Please suggest. "[xmlbean] warning: [options] bootstrap class path not set in conjunction with -source 1.4 [xmlbean] Exception in thread "main" java.lang.OutOfMemoryError: Java heap space" Regards, Divya Add Comment
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) [2019-12-11T16:33:23.125Z] P4 Task: unshelve review: 614492 [2019-12-11T16:33:23.127Z] (p4):cmd:... p4 unshelve -f -s614492 -cdefault [2019-12-11T16:33:23.127Z] p4 unshelve -f -s614492 -cdefault The pipeline code shows the unshelve but nothing in the summary The pipeline groovy looks like p4unshelve credential: p4_credential, resolve: 'at', shelf: ubxShelve, tidy: false, workspace: [$class: 'StreamWorkspaceImpl', charset: 'none', format: p4Workspace, pinHost: false, streamName: perforceStream] The sync steps (that does provide the changes summary), looks like checkout poll: false, scm: perforce( credential: credential_id, populate: autoClean(delete: true, modtime: true, parallel: [enable: false, minbytes: '1024', minfiles: '1', threads: '4'], pin: perforceLabel, quiet: false, replace: true, tidy: false), workspace:ws ) Add Comment
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) In the screenshot you can see my pipeline output. In this code i synced CL 614442 on 2 streams and then unshelved 614492 1) The CL 614442 appears both (for each stream) , the code doesn't create a single set of unique CLs 2) I can see no shelve CL comments Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7204.1576254540219%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert updated an issue Jenkins / JENKINS-38781 p4 unshelve not updating changes (pipeline) Change By: Morne Joubert Attachment: p4_shelve.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7198.1576254301166%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert updated an issue Jenkins / JENKINS-38781 p4 unshelve not updating changes (pipeline) Change By: Morne Joubert Attachment: p4_shelve.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7195.1576254300744%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert updated an issue Jenkins / JENKINS-38781 p4 unshelve not updating changes (pipeline) Change By: Morne Joubert Attachment: p4_shelve.png Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7201.1576254301734%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) the ticket was created 3 years ago let me check Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7192.1576253940166%40Atlassian.JIRA.
[JIRA] (JENKINS-59107) User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2)
Title: Message Title Matt Sicker started work on JENKINS-59107 Change By: Matt Sicker Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201530.1566934526000.7186.1576253230714%40Atlassian.JIRA.
[JIRA] (JENKINS-59107) User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2)
Title: Message Title Matt Sicker assigned an issue to Matt Sicker Jenkins / JENKINS-59107 User logged out after successful configuration of "Run as Specific User" (as of Jenkins 2.150.2) Change By: Matt Sicker Assignee: Wadeck Follonier Matt Sicker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201530.1566934526000.7182.1576253230543%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Karl Wirth commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) Hi Morne Joubert - Sorry I'm missing the point here. I've read the job you mention but can you describe for me exactly what you want to do and what is not working. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7178.1576252200171%40Atlassian.JIRA.
[JIRA] (JENKINS-60430) stopping a job while in reconcile will not stop the reconcile (the job itself will however stop)
Title: Message Title Karl Wirth commented on JENKINS-60430 Re: stopping a job while in reconcile will not stop the reconcile (the job itself will however stop) Hi Eric Daigneault - Thanks. For not stopping the reconcile I have tried some testing here and I think this is more a problem on the server than with p4-plugin. Perforce commands run in a loop and when the client side connection drops they need to get to a safe point in the command before they check if the network connection is still there and die if needed. This is usually when the database locks are released or at the end of processing an argument. If I kill (CTRL+C) a reconcile that takes 30 seconds run using P4 at the command line, I still see the command in p4 monitor for about 25 seconds in total. If I kill the Jenkins job I see similar timings (21 seconds approx) however I think it's easier to be accurate about the time you killed a command at the command line and more difficult to be consistent via Jenkins. So from this testing I think the command line and p4-plugin behavior is comparable. For the file handle, do you know if the file handle was released when the reconcile completed? Also why did you need to workaround it? Was killing the jobs a frequent need? I have tested here and was not able to reproduce the problem on Windows 10 but it may be related to the types/sizes of files etc. Was .Sources\Floor_Base_Interior_01.ZTL a special file? For example a symlink/junction? For the p4j*.tmp files, is it possible they were from an earlier plugib version? They used to be created and sometimes not cleaned up when using symlinks. That should have been fixed in 1.10.6: https://github.com/jenkinsci/p4-plugin/blob/master/RELEASE.md Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58865) Electric flow plugin does not return the json details of a REST call
Title: Message Title ElectricFlow ElectricCloud resolved as Fixed fixed within v 1.1.10: https://wiki.jenkins.io/display/JENKINS/CloudBees+Flow+Plugin#CloudBeesFlowPlugin-ReleaseNotes Jenkins / JENKINS-58865 Electric flow plugin does not return the json details of a REST call Change By: ElectricFlow ElectricCloud Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) What i do in my pipeline wrappers is to have P4_CHANGELIST = cl/label P4_UNSHELVESET= a,b,c Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7169.1576250520537%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Rob Echlin commented on JENKINS-60393 Re: cloudbees-folder circular dependency Sorry, I have been off sick for three days. I see you were not able to reproduce my problem with Jenkins starting. I have attached a list of plugins, obtained as a list of all the jpi files in my plugins folder. Is there a better way to get a list of plugins, as a text file? Thanks for your fast work on this ticket! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203447.1575664332000.7160.1576250520416%40Atlassian.JIRA.
[JIRA] (JENKINS-38781) p4 unshelve not updating changes (pipeline)
Title: Message Title Morne Joubert commented on JENKINS-38781 Re: p4 unshelve not updating changes (pipeline) i currently set the P4_CHANGELIST to the CL the code was synced to , and totally ignore ENV for the shelved CLs since you can unshelve 10 different change lists Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.175181.1475750631000.7157.1576250400278%40Atlassian.JIRA.
[JIRA] (JENKINS-60393) cloudbees-folder circular dependency
Title: Message Title Rob Echlin updated an issue Jenkins / JENKINS-60393 cloudbees-folder circular dependency Change By: Rob Echlin Attachment: plugins-list.txt Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203447.1575664332000.7148.1576250280815%40Atlassian.JIRA.
[JIRA] (JENKINS-60467) The file field on FileCredentialsImpl of class FileItem is not describable
Title: Message Title Jesse Glick commented on JENKINS-60467 Re: The file field on FileCredentialsImpl of class FileItem is not describable To be clear, I do not believe any patch to plain-credentials is possible, at least without a rewrite of file uploads in Stapler. configuration-as-code is just going to have to deal with what is there. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203546.1576192177000.7130.1576249980441%40Atlassian.JIRA.
[JIRA] (JENKINS-60467) The file field on FileCredentialsImpl of class FileItem is not describable
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-60467 The file field on FileCredentialsImpl of class FileItem is not describable Change By: Jesse Glick Component/s: configuration-as-code-plugin Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203546.1576192177000.7127.1576249921807%40Atlassian.JIRA.
[JIRA] (JENKINS-60467) The file field on FileCredentialsImpl of class FileItem is not describable
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-60467 The file field on FileCredentialsImpl of class FileItem is not describable Change By: Jesse Glick Assignee: Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203546.1576192177000.7125.1576249921519%40Atlassian.JIRA.
[JIRA] (JENKINS-60467) The file field on FileCredentialsImpl of class FileItem is not describable
Title: Message Title Jesse Glick commented on JENKINS-60467 Re: The file field on FileCredentialsImpl of class FileItem is not describable FileCredentialsImpl is weird. Definitely not a generally supported usage of @DataBoundConstructor. You cannot and should not attempt to export a FileItem; it is just there to handle browser file uploads. From the perspective of JCasC, ignore the file parameter and use only fileName + secretBytes (the things you actually have getters for anyway). You may need to be adding SecretBytes support to JCasC for the first time. Created by Stephen Connolly. AFAIK used only by FileCredentialsImpl and CertificateCredentialsImpl. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203546.1576192177000.7122.1576249860271%40Atlassian.JIRA.
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title Anda Sorina Laakso commented on JENKINS-53073 Re: HPLauncher Throws Error (HP PlugIn) Did you try to run the command indicated in the result file? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193067.1534441884000.7086.1576241220382%40Atlassian.JIRA.
[JIRA] (JENKINS-60476) Jenkins-agent quits when Jenkins master docker is rebooted, ending the long running task
Title: Message Title efo plo updated an issue Jenkins / JENKINS-60476 Jenkins-agent quits when Jenkins master docker is rebooted, ending the long running task Change By: efo plo Component/s: core Component/s: pipeline Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203558.1576240688000.7084.1576241160096%40Atlassian.JIRA.
[JIRA] (JENKINS-60476) Jenkins-agent quits when Jenkins master docker is rebooted, ending the long running task
Title: Message Title efo plo created an issue Jenkins / JENKINS-60476 Jenkins-agent quits when Jenkins master docker is rebooted, ending the long running task Issue Type: Bug Assignee: Unassigned Attachments: j.txt Components: pipeline Created: 2019-12-13 12:38 Labels: agent.jar Priority: Major Reporter: efo plo In our setup, we run Jenkins master in Docker and Jenkins slaves in VMs. There's an Nginx frontend to Jenkins master. When running a long task (e.g. declarative pipeline with "sleep infinity") with MAX_DURABILITY mode, the slave spawns a shell that waits for end result file to be created, while making `touch` every three seconds to the log file in `durable` folder. When the Jenkins master docker container is restarted, the slave tries to reconnect but exits after 5 minutes of Master unavailability. This may have to do with it receiving `503 Service Unavailable` from nginx. This kills the whole spawned processes tree, including the actual task. This may have to do with internal slave.jar logic, where it expects the master IP to become unavailable while rebooting, whereas in our situation the IP is available but no one is answering JLNP requests and 503 is returned by nginx. The slave is restarted later by the service (or supervisord on some slaves), but the task is already gone, so the actual promise of durability is never delivered on. The log is attached, the Jenkins master reboot happened at 21:39 or so, at 21:45 the slave process (pid 9827) has quit, killing the job with it. Also, can't find Component for slave/agent, please re-route.
[JIRA] (JENKINS-49664) ThinBackup Multi-Branch Branches Directory and SSH Key
Title: Message Title Jakob Fahrner commented on JENKINS-49664 Re: ThinBackup Multi-Branch Branches Directory and SSH Key There seems to be an PR for this on github https://github.com/jenkinsci/thin-backup-plugin/pull/15 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.188593.1519181272000.7065.1576240440253%40Atlassian.JIRA.
[JIRA] (JENKINS-48417) Ability to run Docker container in foreground mode (no detached)
Title: Message Title Antoine Duprat assigned an issue to Antoine Duprat Jenkins / JENKINS-48417 Ability to run Docker container in foreground mode (no detached) Change By: Antoine Duprat Assignee: Antoine Duprat Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187015.1512595328000.7051.1576240020279%40Atlassian.JIRA.
[JIRA] (JENKINS-60475) Atlassian Bitbucket server integration not working with Folders plugin security
Title: Message Title Tom Kostiainen created an issue Jenkins / JENKINS-60475 Atlassian Bitbucket server integration not working with Folders plugin security Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2019-12-13 12:23 Environment: Jenkins 2.190.3, Bitbucket integration 1.0.3, Folders plugin 6.10 Labels: bitbucket Priority: Major Reporter: Tom Kostiainen Using the folder plugin and configuring a pipeline job under it, a user having full access on the folder level including job configuration is not able to complete the Bitbucket config for his job. When the user selects Bitbucket as the SCM the fields for defining instance, project, credentials etc. are not shown. Saving after this will corrupt the job config. Giving the user access on the system level to manage job configurations will fix the problem. This is not optimal when wanting to limit the access using the Folders plugin.
[JIRA] (JENKINS-60474) streamline plugin-pom and support the jenkins-bom
Title: Message Title James Nord started work on JENKINS-60474 Change By: James Nord Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203556.1576237963000.7045.1576237980931%40Atlassian.JIRA.
[JIRA] (JENKINS-60474) streamline plugin-pom and support the jenkins-bom
Title: Message Title James Nord created an issue Jenkins / JENKINS-60474 streamline plugin-pom and support the jenkins-bom Issue Type: Improvement Assignee: James Nord Components: plugin-pom Created: 2019-12-13 11:52 Priority: Minor Reporter: James Nord The plugin-pom should support the jenkins-bom out of the box. Given this will be a breaking change we should also clean up the historic debt that has accrued. https://groups.google.com/forum/#!topic/jenkinsci-dev/tm3F_vgK5vA Add Comment This
[JIRA] (JENKINS-53073) HPLauncher Throws Error (HP PlugIn)
Title: Message Title MANJU GL commented on JENKINS-53073 Re: HPLauncher Throws Error (HP PlugIn) Hi Team, any updates on this issue? i have the same problem. Regards, Manju Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193067.1534441884000.7032.1576236540249%40Atlassian.JIRA.
[JIRA] (JENKINS-60473) Docker pipeline: 'absolute path' error when running docker under windows
Title: Message Title Piotr Krukowiecki updated an issue Jenkins / JENKINS-60473 Docker pipeline: 'absolute path' error when running docker under windows Change By: Piotr Krukowiecki Summary: Docker pipeline: 'absolute path' error when running docker under windows Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203554.1576235571000.7029.1576235640073%40Atlassian.JIRA.
[JIRA] (JENKINS-60473) Docker pipeline: error when running docker under windows
Title: Message Title
Piotr Krukowiecki created an issue
Jenkins / JENKINS-60473
Docker pipeline: error when running docker under windows
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-workflow-plugin
Created:
2019-12-13 11:12
Environment:
Jenkins 2.164.1 Docker Pipeline 1.21 Pipeline 2.6 Windows 10
Priority:
Major
Reporter:
Piotr Krukowiecki
I have a jenkins master on linux, a slave agent on windows 10. On the slave there is docker desktop installed. I can run commands under this docker from windows command line, for example:
docker run --rm -v c:/Users/modtest:/home/pkruk node:alpine sh -c "ls -la"
total 64
drwxr-xr-x 1 root root 4096 Dec 12 17:09 .
drwxr-xr-x 1 root root 4096 Dec 12 17:09 ..
-rwxr-xr-x 1 root root 0 Dec 12 17:09 .dockerenv
[...]
But when I try to execute following pipeline:
pipeline {
agent {
docker { image 'node:alpine' }
}
stages {
stage('Build') {
environment {
HOME = '.'
}
steps {
sh 'rm -f *.vsix'
}
post {
always {
archiveArtifacts artifacts: '*.vsix', fingerprint: true
}
}
}
}
}
[JIRA] (JENKINS-60472) Jenkins authentication with GitHub not working
Title: Message Title giby Alex created an issue Jenkins / JENKINS-60472 Jenkins authentication with GitHub not working Issue Type: Bug Assignee: Unassigned Attachments: jenkins.PNG Components: github-oauth-plugin Created: 2019-12-13 10:52 Environment: Jenkins version:- 2.190.3, Os:-Redhat 7.6, java :- openjdk:- "1.8.0_201" Connect Labels: jenkins plug-in Github authentication Priority: Major Reporter: giby Alex I am using Jenkins 2.190.3. when I tried to integrate the authentication with GitHub OAuth Plugin version 0.33. when I tried to configure the same I am getting an error like java.lang.ClassCastException: org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationTokenjava.lang.ClassCastException: org.acegisecurity.providers.anonymous.AnonymousAuthenticationToken cannot be cast to org.jenkinsci.plugins.GithubAuthenticationToken at org.jenkinsci.plugins.GithubSecurityRealm.loadGroupByGroupname(GithubSecurityRealm.java:784) at org.jenkinsci.plugins.matrixauth.AuthorizationContainerDescriptor.doCheckName(AuthorizationContainerDescriptor.java:169) at hudson.security.GlobalMatrixAuthorizationStrategy$DescriptorImpl.doCheckName(GlobalMatrixAuthorizationStrategy.java:222) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)_
[JIRA] (JENKINS-60468) Unable to add my windows machine as a Slave.
Title: Message Title prudhvikumar madithati assigned an issue to Unassigned Jenkins / JENKINS-60468 Unable to add my windows machine as a Slave. Change By: prudhvikumar madithati Assignee: prudhvikumar madithati Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203547.1576207595000.7026.1576233960522%40Atlassian.JIRA.
[JIRA] (JENKINS-60468) Unable to add my windows machine as a Slave.
Title: Message Title prudhvikumar madithati assigned an issue to prudhvikumar madithati Jenkins / JENKINS-60468 Unable to add my windows machine as a Slave. Change By: prudhvikumar madithati Assignee: prudhvikumar madithati Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203547.1576207595000.7025.1576233960232%40Atlassian.JIRA.
[JIRA] (JENKINS-60468) Unable to add my windows machine as a Slave.
Title: Message Title prudhvikumar madithati assigned an issue to Unassigned Jenkins / JENKINS-60468 Unable to add my windows machine as a Slave. Change By: prudhvikumar madithati Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203547.1576207595000.7024.1576233900341%40Atlassian.JIRA.
[JIRA] (JENKINS-60471) Jenkins polluting /tmp with thousands of TrueType font files
Title: Message Title Dirk Heinrichs created an issue Jenkins / JENKINS-60471 Jenkins polluting /tmp with thousands of TrueType font files Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-12-13 10:21 Environment: Linux (Ubuntu 18.04) Jenkins 2.190.1 Priority: Major Reporter: Dirk Heinrichs Just encountered sporadic "No space left on device" errors in the Puppet reports for our Jenkins master. It turned out that /tmp was polluted with over 8000 files of the form "+~JF*.tmp" owned by the user running Jenkins: -rw--- 1 jenkins jenkins 240456 Dec 13 11:18 +~JF9196768992512109284.tmp I deleted them to free space, but it continues to write new ones at fast pace (again 2640 files while I'm writing this).
[JIRA] (JENKINS-53295) error log should be collapsed by default too
Title: Message Title Luis Piedra-Márquez commented on JENKINS-53295 Re: error log should be collapsed by default too Certainly, having the full error log displayed by default in steps that are being retried is really annoying. It kills all the purpose of the Blue Ocean interface. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193373.1535497028000.6988.1576231020303%40Atlassian.JIRA.
[JIRA] (JENKINS-60470) Github Plugin sends build status for skipped scm builds resulting in build failed status
Title: Message Title Alexander KIRILOV created an issue Jenkins / JENKINS-60470 Github Plugin sends build status for skipped scm builds resulting in build failed status Issue Type: Bug Assignee: Kirill Merkushev Components: github-plugin, scmskip-plugin Created: 2019-12-13 09:44 Environment: Ubuntu 18 Jenkins 2.200 Github Plugin ScmSkip Plugin Priority: Major Reporter: Alexander KIRILOV Issue Description: When using ScmSkip plugin to skip a build when a certain message pattern is present like [skip ci], the github plugin will still post the status to github thus resulting in last build failed. The issue is present when your build wants to increment a version number for instance and performs a new commit with [ci skip] and the new commit is picked up by github plugin which sends the build status Add Comment
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Alexander Smirnov edited a comment on JENKINS-60421 Re: NPE when saving Jenkins configuration if audit console logger is added in JCASC Thank out you [~pierrebtz]. I tested PR 29 version and confirm that it works: no exceptions when saving Jenkins configuration, audit logs are printed in stdout. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203493.1575991654000.6982.1576229640144%40Atlassian.JIRA.
[JIRA] (JENKINS-60421) NPE when saving Jenkins configuration if audit console logger is added in JCASC
Title: Message Title Alexander Smirnov commented on JENKINS-60421 Re: NPE when saving Jenkins configuration if audit console logger is added in JCASC Thank out Pierre Beitz. I tested PR 29 version and confirm that it works: no exceptions when saving Jenkins configuration, audit logs are printed in stdout. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203493.1575991654000.6980.1576229580139%40Atlassian.JIRA.
[JIRA] (JENKINS-60454) Jenkins.instance is missing after restart
Title: Message Title Karl Wirth commented on JENKINS-60454 Re: Jenkins.instance is missing after restart Hi Chun-Ta Kung - I dont have much experience with this but I would recommend restarting the server to see if it solves the problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203532.1576121478000.6973.1576227900194%40Atlassian.JIRA.
[JIRA] (JENKINS-60193) NPE in JabberPublisherDescriptor in new install
Title: Message Title Florian Schmaus updated JENKINS-60193 Jenkins / JENKINS-60193 NPE in JabberPublisherDescriptor in new install Change By: Florian Schmaus Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203163.1574067471000.6971.1576227002544%40Atlassian.JIRA.
