[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Lasse Lindqvist commented on JENKINS-56232 Re: Maven Local Repository is always seen as relative when it should be absolute The related commit is here: https://github.com/jenkinsci/pipeline-maven-plugin/commit/496eb784e2e9a0fd9e463922f6001848c2d5eda6 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57151) Some HTML Tags like "target='_blank' "are not rendered.
Title: Message Title
shubham srivastava created an issue
Jenkins / JENKINS-57151
Some HTML Tags like "target='_blank' "are not rendered.
Issue Type:
Bug
Assignee:
Ulli Hafner
Attachments:
image-2019-04-23-13-05-04-129.png, image-2019-04-23-13-08-00-903.png
Components:
core
Created:
2019-04-23 07:40
Priority:
Major
Reporter:
shubham srivastava
Hello Hafner, some HTML Tags are not supported in warning-ng plugin. i have used target='_blank' to open the HTML page in new tab, but it didn't work. when i inspect the html page, i found that target tag is not visible there. below is the code which i used issueBuilder.setMessage(""event.asCharacters().getData()""); I am attaching the screenshot of the inspect html page where the 'target' tag is not visible
Add Comment
[JIRA] (JENKINS-57151) Some HTML Tags like "target='_blank' "are not rendered.
Title: Message Title
shubham srivastava updated an issue
Jenkins / JENKINS-57151
Some HTML Tags like "target='_blank' "are not rendered.
Change By:
shubham srivastava
Hello Hafner,some HTML Tags are not supported in warning-ng plugin. i have used target='_blank' to open the HTML page in new tab, but it didn't work. when i inspect the html page, i found that target tag is not visible there.below is the code which i usedissueBuilder.setMessage(""+event.asCharacters().getData()+""); I am attaching the screenshot of the inspect html page where the 'target' tag is not visible !image-2019-04-23-13-08-00-903 . png!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57152) Implementation Of Integration Test for EclipseXmlParser
Title: Message Title shubham srivastava created an issue Jenkins / JENKINS-57152 Implementation Of Integration Test for EclipseXmlParser Issue Type: New Feature Assignee: Ulli Hafner Components: core Created: 2019-04-23 07:50 Priority: Major Reporter: shubham srivastava Hello Hafner, As of now we don't have integration test for any of the parser class. can you please add Integration Test for EclipseXMLParser class in your next release. Add Comment This message was sent by Atlassian Jira (v7.11
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Thank you Joe Mihalich. I don't see what's wrong. Could you please change the line 67 from echo $(JAVA -version) >&2 to echo $JAVA_VERSION This way, I could see what the sed _expression_ on line 60 returned in your case. Thank you for your patience. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57151) Some HTML Tags like "target='_blank' "are not rendered.
Title: Message Title Ulli Hafner resolved as Won't Fix HTML content in message and description is filtered with Jenkins RawHtmlMarkupFormatter in order to prevent XSS attacks. For details see Jenkins wiki. Jenkins / JENKINS-57151 Some HTML Tags like "target='_blank' "are not rendered. Change By: Ulli Hafner Status: Open Resolved Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57153) Allow building forks in addition to main repo and PRs
Title: Message Title Lasse Lindqvist created an issue Jenkins / JENKINS-57153 Allow building forks in addition to main repo and PRs Issue Type: New Feature Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-04-23 08:22 Priority: Minor Reporter: Lasse Lindqvist Add "Discover branches from forks" action to the plugin. In some cases the workflow is such that developers develop in their own forks and only make PRs to the main repository. In such cases we can only build after a PR has been made. This might lead to a situation where developers are forced to make work-in-progress PRs to get some tests or else run in the CI. Adding "Discover branches from forks" action to the plugin makes it possible to combine it with Named branches and Regular _expression_ to build branches the developer wants to be built. The "Trust" choice could be used here similarly to the PRs. This is as safe as building PRs since it would not be on by default and similar defensive measures could be used as can be used with PR building. Add Comment
[JIRA] (JENKINS-56856) Setup wizards handles password field wrong
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-56856 Setup wizards handles password field wrong Change By: Oliver Gondža Labels: lts 2.164.3 - candidate fixed setup-wizard Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Raphael Pionke commented on JENKINS-55202 Re: Performance Signature Plugin: JAXB API is missing with Java 11 Adrien Lecharpentier do you think, i might help to just get rid of the com.squareup.retrofit2:converter-jaxb dependency and copy those 4 classes into the dynatrace-appmon module? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Adrien Lecharpentier commented on JENKINS-55202 Re: Performance Signature Plugin: JAXB API is missing with Java 11 Raphael Pionke at this moment, I trully believe that getting ride on this dependency is the better solution. You could still be using another converter. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56889) Kubernetes creates too many slaves
Title: Message Title Tony Wen commented on JENKINS-56889 Re: Kubernetes creates too many slaves I'm having the same issue. jenkins ver 2.174, Kubernetes plugin 1.15.1. Looks like jenkins is provisioning pod continuously using over-provisioning setting. but it is not applicable here with Kubernetes plugin when each job pipeline is configured with unique pod label. Only 1 pod will be used to execute 'real' command and all others will never get used by any other build. Logs Apr 19, 2019 8:11:28 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud pro vision INFO: Excess workload after pending Kubernetes agents: 1 Apr 19, 2019 8:11:28 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud pro vision INFO: Template for label k8s-csf-cctf-test-CCTF-1-1: Kubernetes Pod Template Apr 19, 2019 8:11:28 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesClientPro vider createClient INFO: Created new Kubernetes client: kubernetes io.fabric8.kubernetes.client.Defaul tKubernetesClient@49f45b70 Apr 19, 2019 8:11:28 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class pat h? Apr 19, 2019 8:11:28 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors . Remaining excess workload: 0 Apr 19, 2019 8:11:38 AM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 2 co mputer(s) Apr 19, 2019 8:11:38 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch INFO: Created Pod: k8s-csf-cctf-test-cctf-1-1-8g2p1-5tx97 in namespace cctf Apr 19, 2019 8:11:39 AM okhttp3.internal.platform.Platform log INFO: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class pat h? Apr 19, 2019 8:11:47 AM hudson.TcpSlaveAgentListener$ConnectionHandler run INFO: Accepted JNLP4-connect connection #1 from /192.168.1.49:53436 Apr 19, 2019 8:11:58 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud pro vision INFO: Excess workload after pending Kubernetes agents: 1 Apr 19, 2019 8:11:58 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud pro vision INFO: Template for label k8s-csf-cctf-test-CCTF-1-1: Kubernetes Pod Template Apr 19, 2019 8:11:58 AM hudson.slaves.NodeProvisioner$StandardStrategyImpl apply INFO: Started provisioning Kubernetes Pod Template from kubernetes with 1 executors . Remaining excess workload: 0 Apr 19, 2019 8:12:08 AM hudson.slaves.NodeProvisioner$2 run INFO: Kubernetes Pod Template provisioning successfully completed. We have now 3 co mputer(s) Apr 19, 2019 8:12:08 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud pro vision INFO: Excess workload after pending Kubernetes agents: 1 Apr 19, 2019 8:12:08 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud pro vision INFO: Template for label k8s-csf-cctf-test-CCTF-2-1: Kubernetes Pod Template Apr 19, 2019 8:12:08 AM org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher launch IN
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Oliver Gondža commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Can someone verify the patch? I have failed to reproduce the problem using firefox-nightly-68.0a1.20190422-1 and jenkins/jenkins:2.172. Both logging in as admin and saving global config page works for me. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44692) Docker build step does not properly format output
Title: Message Title vjuranek updated JENKINS-44692 should be fixed by https://github.com/jenkinsci/docker-build-step-plugin/pull/58 https://github.com/jenkinsci/docker-build-step-plugin/pull/59 Jenkins / JENKINS-44692 Docker build step does not properly format output Change By: vjuranek Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Oliver Gondža, a normal nightly build of Firefox won't work given that it hasn't the patch from bug 1370630 included. You can pick a build from https://treeherder.mozilla.org/#/jobs?repo=try&revision=3f12e17b558a36ef5b65235d663c4e617c3d328e&searchStr=build by just clicking the `B` symbol of your platform, selecting Job Details in the lower pane, and then `target.zip`, `target.dmg`, or `target.tar.bz2`. Just extract the archive and run the binary. With such a build you should be able to see the failure without the patch in Jenkins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57118) don't need sync -f @0 command in cleanup true
Title: Message Title Paul Allen commented on JENKINS-57118 Re: don't need sync -f @0 command in cleanup true You should be able to skip the 'sync -f ...#0' step in the Global configurations options: Manage Jenkins > Global Configuration > Perforce: OnDelete Workspace Options > Uncheck 'Delete Workspace files' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56505) Performance Issue: JobDSL plugin creates folders All view with a localized name
Title: Message Title
Michael Ahern commented on JENKINS-56505
Re: Performance Issue: JobDSL plugin creates folders All view with a localized name
Daniel Spilker - so I was able to easily reproduce the issue using the LTS docker image. That is `Jenkins ver. 2.164.2` at the time of this writing. To reproduce:
docker run -p 8080:8080 -p 5:5 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts
On initial startup, install the "recommended" plugins - do not customize the list
Install the JobDSL plugin
Create a FreeStyle job CreateFolder
Configure the free style job to have an inline DSL section and provide the snippet below: {
Unknown macro: {folder('GenFolder') { displayName('GenFolder') description('GenFolder') }}
}
Save
Run the CreateFolder Job
Navigate in the Jenkins UI to the {{GenFolder}} directory (I get an error message in the UI, but this is fine)
Navigate to the Logs page: `/log/all`
You should see the following log message: JENKINS-38606 detected for AllView in com.cloudbees.hudson.plugins.folder.Folder@38aa17c8[GenFolder]; renaming view from All to all
This lines up with the expectations based on the Folder code: https://github.com/jenkinsci/cloudbees-folder-plugin/blob/e9a4d5b19e7db6021f81d2c4c8c2afa328e0d9f8/src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolder.java#L248 If you look there, the code requires that a primaryView be defined when this block of code is hit. I am not sure of the exact situation necessary, but it is fairly common in the wild. Following the code for {{ migrateLegacyPrimaryAllViewLocalizedName }}: https://github.com/jenkinsci/cloudbees-folder-plugin/blob/e9a4d5b19e7db6021f81d2c4c8c2afa328e0d9f8/src/main/java/com/cloudbees/hudson/plugins/folder/views/DefaultFolderViewHolder.java#L176 Under common conditions this will attempt to rename the view to {{ AllView.DEFAULT_VIEW_NAME }}. Checking that code: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AllView.java#L61 ... {{ AllView.DEFAULT_VIEW_NAME }} is {{ "all" }} (in lowercase).
[JIRA] (JENKINS-56505) Performance Issue: JobDSL plugin creates folders All view with a localized name
Title: Message Title
Michael Ahern edited a comment on JENKINS-56505
Re: Performance Issue: JobDSL plugin creates folders All view with a localized name
[~daspilker] - so I was able to easily reproduce the issue using the LTS docker image. That is `[Jenkins ver. 2.164.2|https://jenkins.io/]` at the time of this writing.To reproduce: # {{docker run -p 8080:8080 -p 5:5 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts}} # On initial startup, install the "recommended" plugins - do not customize the list # Install the JobDSL plugin # Create a FreeStyle job {{CreateFolder}} # Configure the free style job to have an inline DSL section and provide the snippet below: \{{folder('GenFolder') { displayName('GenFolder') description('GenFolder') }}} # Save # Run the {{CreateFolder}} Job # Navigate in the Jenkins UI to the GenFolder directory (I get an error message in the UI, but this is fine) # Navigate to the Logs page: `[/log/all|http://localhost:8080/log/all]` # You should see the following log message: {{JENKINS-38606 detected for AllView in com.cloudbees.hudson.plugins.folder.Folder@38aa17c8[GenFolder]; renaming view from All to all}} This lines up with the expectations based on the Folder code:[https://github.com/jenkinsci/cloudbees-folder-plugin/blob/e9a4d5b19e7db6021f81d2c4c8c2afa328e0d9f8/src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolder.java#L248]If you look there, the code requires that a primaryView be defined when this block of code is hit. I am not sure of the exact situation necessary, but it is fairly common in the wild. Following the code for \{{ migrateLegacyPrimaryAllViewLocalizedName }}:[https://github.com/jenkinsci/cloudbees-folder-plugin/blob/e9a4d5b19e7db6021f81d2c4c8c2afa328e0d9f8/src/main/java/com/cloudbees/hudson/plugins/folder/views/DefaultFolderViewHolder.java#L176]Under common conditions this will attempt to rename the view to {{ AllView.DEFAULT_VIEW_NAME }}. Checking that code: [https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AllView.java#L61]... {{ AllView.DEFAULT_VIEW_NAME }} is \ {{ "all" }} (in lowercase).
Add Comment
This message was sent by Atlassian
[JIRA] (JENKINS-49540) Rebuild Commit
Title: Message Title Amit Nanaware updated an issue Jenkins / JENKINS-49540 Rebuild Commit Change By: Amit Nanaware Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56505) Performance Issue: JobDSL plugin creates folders All view with a localized name
Title: Message Title Michael Ahern assigned an issue to Daniel Spilker Jenkins / JENKINS-56505 Performance Issue: JobDSL plugin creates folders All view with a localized name Change By: Michael Ahern Assignee: Michael Ahern Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56505) Performance Issue: JobDSL plugin creates folders All view with a localized name
Title: Message Title
Michael Ahern edited a comment on JENKINS-56505
Re: Performance Issue: JobDSL plugin creates folders All view with a localized name
[~daspilker] - so I was able to easily reproduce the issue using the LTS docker image. That is `[Jenkins ver. 2.164.2|https://jenkins.io/]` at the time of this writing.To reproduce: # {{docker run -p 8080:8080 -p 5:5 -v jenkins_home:/var/jenkins_home jenkins/jenkins:lts}} # On initial startup, install the "recommended" plugins - do not customize the list # Install the JobDSL plugin # Create a FreeStyle job {{CreateFolder}} # Configure the free style job to have an inline DSL section and provide the snippet below: \{{ * folder('GenFolder') \ { displayName('GenFolder') description('GenFolder') } }} * # Save # Run the {{CreateFolder}} Job # Navigate in the Jenkins UI to the GenFolder directory (I get an error message in the UI, but this is fine) # Navigate to the Logs page: `[/log/all|http://localhost:8080/log/all]` # You should see the following log message: {{JENKINS-38606 detected for AllView in com.cloudbees.hudson.plugins.folder.Folder@38aa17c8[GenFolder]; renaming view from All to all}} This lines up with the expectations based on the Folder code:[https://github.com/jenkinsci/cloudbees-folder-plugin/blob/e9a4d5b19e7db6021f81d2c4c8c2afa328e0d9f8/src/main/java/com/cloudbees/hudson/plugins/folder/AbstractFolder.java#L248]If you look there, the code requires that a primaryView be defined when this block of code is hit. I am not sure of the exact situation necessary, but it is fairly common in the wild. Following the code for \{{ migrateLegacyPrimaryAllViewLocalizedName }}:[https://github.com/jenkinsci/cloudbees-folder-plugin/blob/e9a4d5b19e7db6021f81d2c4c8c2afa328e0d9f8/src/main/java/com/cloudbees/hudson/plugins/folder/views/DefaultFolderViewHolder.java#L176]Under common conditions this will attempt to rename the view to \ {{ AllView.DEFAULT_VIEW_NAME }}. Checking that code: [https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/AllView.java#L61]... {{AllView.DEFAULT_VIEW_NAME}} is {{"all"}} (in lowercase).
Add Comment
This message was sent by
[JIRA] (JENKINS-49540) Rebuild Commit
Title: Message Title Amit Nanaware commented on JENKINS-49540 Re: Rebuild Commit Can we have same feature for pipeline job? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Daniel Beck commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Oliver Gondža AFAIUI, the behavior of Chrome is the correct one (i.e. future Firefox's), so you should be able to confirm using Chrome with a Firefox user agent string. That's how I reproduced it and worked on the fix. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated an issue Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Attachment: image-2019-04-23-11-27-12-272.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Daniel Beck commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Henrik Skupin Thanks for the link. "Save" buttons don't work on the nightly build and Jenkins 2.164.2, as expected. And they work on Jenkins 2.174, also as expected Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen commented on JENKINS-56428 Re: Timeout Exception: FATAL: Unable to generate release notes for JIRA version The fix Argh. This turned out to be a user error - apparently combined with some bad defaults. I don't know when the timeout parameters and Thread Executor Size were introduced, but it turns out that the default value of 0 (zero) isn't healthy. :-/ Adding some values greater than zero at random, worked: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen assigned an issue to Flemming Steffensen Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Assignee: Flemming Steffensen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57118) don't need sync -f @0 command in cleanup true
Title: Message Title Hokwang Lee commented on JENKINS-57118 Re: don't need sync -f @0 command in cleanup true Oh, Thank you. You can close this case! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56428) Timeout Exception: FATAL: Unable to generate release notes for JIRA version
Title: Message Title Flemming Steffensen updated JENKINS-56428 Turned out to be a user error - and some badly chosen defaults during plugin upgrade. See comments. Jenkins / JENKINS-56428 Timeout Exception: FATAL: Unable to generate release notes for JIRA version Change By: Flemming Steffensen Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56666) Maven versioning extension produces warnings
Title: Message Title Michael D commented on JENKINS-5 Re: Maven versioning extension produces warnings Hi Cyrille, sadly the extensions changed its behavior again with release 4.1.0, now there is a .git-versioned.pom.xml generated in the target folder. Would be great to have a fix for it because this is one of the best maven things I found in the last year. Kind regards, Michael Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57118) don't need sync -f @0 command in cleanup true
Title: Message Title Karl Wirth closed an issue as Not A Defect The setting is on the global configuration page. Jenkins / JENKINS-57118 don't need sync -f @0 command in cleanup true Change By: Karl Wirth Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Great to be helpful. And that sounds fantastic. So we now have to wait for the 2.174 and an upcoming LTS before we can make that change live in Firefox. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title Raphael Pionke commented on JENKINS-55202 Re: Performance Signature Plugin: JAXB API is missing with Java 11 Adrien Lecharpentier i created a new branch and added the needed classes, but with no luck. the unit tests are passing but my test instance displays the same error: Apr 23, 2019 12:37:33 PM FINE javax.xml.bindSearching jaxb.properties Apr 23, 2019 12:37:33 PM FINE javax.xml.bindChecking system property javax.xml.bind.JAXBContextFactory Apr 23, 2019 12:37:33 PM FINE javax.xml.bind not found Apr 23, 2019 12:37:33 PM FINE javax.xml.bindChecking system property javax.xml.bind.context.factory Apr 23, 2019 12:37:33 PM FINE javax.xml.bind not found Apr 23, 2019 12:37:33 PM FINE javax.xml.bindChecking system property javax.xml.bind.JAXBContext Apr 23, 2019 12:37:33 PM FINE javax.xml.bind not found Apr 23, 2019 12:37:33 PM FINE javax.xml.bindSearching META-INF/services Apr 23, 2019 12:37:33 PM FINE javax.xml.bindUnable to load:META-INF/services/javax.xml.bind.JAXBContext Apr 23, 2019 12:37:33 PM FINE javax.xml.bindTrying to create the platform default provider Apr 23, 2019 12:37:33 PM FINE javax.xml.bindUnable to find from OSGi: [javax.xml.bind.JAXBContext] java.lang.ClassNotFoundException: org.glassfish.hk2.osgiresourcelocator.ServiceLoader at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1373) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:315) at javax.xml.bind.ServiceLoaderUtil.lookupUsingOSGiServiceLoader(ServiceLoaderUtil.java:86) at javax.xml.bind.ContextFinder.find(ContextFinder.java:413) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:721) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:662) at jaxb.JaxbConverterFactory.contextForType(JaxbConverterFactory.java:85) at jaxb.JaxbConverterFactory.responseBodyConverter(JaxbConverterFactory.java:78) at retrofit2.Retrofit.nextResponseBodyConverter(Retrofit.java:328) at retrofit2.Retrofit.responseBodyConverter(Retrofit.java:311) at retrofit2.HttpServiceMethod.createResponseConverter(HttpServiceMethod.java:68) at retrofit2.HttpServiceMethod.parseAnnotations(HttpServiceMethod.java:46) at retrofit2.ServiceMethod.parseAnnotations(ServiceMethod.java:36) at retrofit2.Retrofit.loadServiceMethod(Retrofit.java:168) at retrofit2.Retrofit$1.invoke(Retrofit.java:147) at com.sun.proxy.$Proxy110.getServerLicense(Unknown Source) at de.tsystems.mms.apm.performancesignature.dynatrace.rest.DTServerConnection.getServerLicense(DTServerConnection.java:255) at de.tsystems.mms.apm.performancesignature.dynatrace.PerfSigStartRecording.perform(PerfSigStartRecording.java:83) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-53462 Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Change By: Oliver Gondža Labels: lts 2.164.3 - candidate fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55202) Performance Signature Plugin: JAXB API is missing with Java 11
Title: Message Title
Raphael Pionke edited a comment on JENKINS-55202
Re: Performance Signature Plugin: JAXB API is missing with Java 11
[~alecharp] i created a new branch and added the needed classes, but with no luck. the unit tests are passing but my test instance displays the same error: {noformat}Apr 23, 2019 12:37:33 PM FINE javax.xml.bindSearching jaxb.propertiesApr 23, 2019 12:37:33 PM FINE javax.xml.bindChecking system property javax.xml.bind.JAXBContextFactoryApr 23, 2019 12:37:33 PM FINE javax.xml.bind not foundApr 23, 2019 12:37:33 PM FINE javax.xml.bindChecking system property javax.xml.bind.context.factoryApr 23, 2019 12:37:33 PM FINE javax.xml.bind not foundApr 23, 2019 12:37:33 PM FINE javax.xml.bindChecking system property javax.xml.bind.JAXBContextApr 23, 2019 12:37:33 PM FINE javax.xml.bind not foundApr 23, 2019 12:37:33 PM FINE javax.xml.bindSearching META-INF/servicesApr 23, 2019 12:37:33 PM FINE javax.xml.bindUnable to load:META-INF/services/javax.xml.bind.JAXBContextApr 23, 2019 12:37:33 PM FINE javax.xml.bindTrying to create the platform default providerApr 23, 2019 12:37:33 PM FINE javax.xml.bindUnable to find from OSGi: [javax.xml.bind.JAXBContext]java.lang.ClassNotFoundException: org.glassfish.hk2.osgiresourcelocator.ServiceLoader at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1373) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1326) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1079) at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:315) at javax.xml.bind.ServiceLoaderUtil.lookupUsingOSGiServiceLoader(ServiceLoaderUtil.java:86) at javax.xml.bind.ContextFinder.find(ContextFinder.java:413) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:721) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:662) at jaxb.JaxbConverterFactory.contextForType(JaxbConverterFactory.java:85) at jaxb.JaxbConverterFactory.responseBodyConverter(JaxbConverterFactory.java:78) at retrofit2.Retrofit.nextResponseBodyConverter(Retrofit.java:328) at retrofit2.Retrofit.responseBodyConverter(Retrofit.java:311) at retrofit2.HttpServiceMethod.createResponseConverter(HttpServiceMethod.java:68) at retrofit2.HttpServiceMethod.parseAnnotations(HttpServiceMethod.java:46) at retrofit2.ServiceMethod.parseAnnotations(ServiceMethod.java:36) at retrofit2.Retrofit.loadServiceMethod(Retrofit.java:168) at retrofit2.Retrofit$1.invoke(Retrofit.java:147) at com.sun.proxy.$Proxy110.getServerLicense(Unknown Source) at de.tsystems.mms.apm.performancesignature.dynatrace.rest.DTServerConnection.getServerLicense(DTServerConnection.java:255) at de.tsystems.mms.apm.performancesignature.dynatrace.PerfSigStartRecording.perform(PerfSigStartRecording.java:83) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:80) at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:67) at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:834)Apr 23, 2019 12:37:33 PM FINE javax.xml.bindTrying to create the platform default provider{noformat} Here is the diff: https://github.com
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Bikash Sundaray commented on JENKINS-54115 Re: Remote Invocation of Jenkins API when using Azure AD Plugin Jie Shen I am facing issue while accessing issue. I have followed your comment on 'username (object id)' and 'username (user ID)'. But it didn't work for me. Can you please give one example how to add these to user. I can understand, this one "username (object id)" is based on autocomplete but what about 'username (user ID)', what will be user ID here. On which user, i should create API token Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Oliver Gondža commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Cool, thanks! I am backporting this to 2.164.3 to be released 2019-04-08, unless further regressions are found. Henrik Skupin, I do appreciate the effort put in making sure Jenkins is ready for the fix in Firefox. Though I am wondering if there is a chance to postpone the delivery until significant Jenkins (or what other applications are affected) userbase migrate to the fixed version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Bikash Sundaray edited a comment on JENKINS-54115 Re: Remote Invocation of Jenkins API when using Azure AD Plugin [~jieshe] I am facing issue while accessing issue API . I have followed your comment on 'username (object id)' and 'username (user ID)'. But it didn't work for me.Can you please give one example how to add these to 2 user. I can understand, this one "username (object id)" is based on autocomplete but what about 'username (user ID)', what will be user ID here.On which user, i should create API token I am making GET API call to following URL on my server (Note i have jenkins prefix to access my jenkins instance)https:api/json Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox I assume you mean 2019-05-08. We can post-pone for sure. It's not that this patch is critical, and we already waited a while for it. Do you have some stats in how long it takes for the majority of users to upgrade to the next LTS release? Will it be one week, or two? Also note that the fix will land on mozilla-central only, which means it will only be part of a nightly build. Those people are tech-aware and should upgrade their instances fast enough. Our next merge to beta is on 2019-05-13, so I would suggest to at least wait until 2019-05-14 before landing that change in Firefox Nightly (69). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Oliver Gondža edited a comment on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Cool, thanks! I am backporting this to 2.164.3 to be released - 2019-04-08 - (EDIT: 2019-05-08) , unless further regressions are found.[~whimboo], I do appreciate the effort put in making sure Jenkins is ready for the fix in Firefox. Though I am wondering if there is a chance to postpone the delivery until significant Jenkins (or what other applications are affected) userbase migrate to the fixed version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56855) MessagingException message: IOException while sending message
Title: Message Title Tero Kivisaari commented on JENKINS-56855 Re: MessagingException message: IOException while sending message Do you happen to run in AWS EC2? We bumped into a similar issue which was a bit difficult to trace and in the end concluded that it was most likely AWS throttling traffic to port 25 https://aws.amazon.com/premiumsupport/knowledge-center/ec2-port-25-throttle/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54115) Remote Invocation of Jenkins API when using Azure AD Plugin
Title: Message Title Bikash Sundaray commented on JENKINS-54115 Re: Remote Invocation of Jenkins API when using Azure AD Plugin Now working !! I am able to fix this by adding my email id as user and assigning view permission. In the API call, i am using my email ID as username and Token as Password Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56666) Maven versioning extension produces warnings due to temporary pom.xml file name '.git-versioned.pom.xml'
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-5 Maven versioning extension produces warnings due to temporary pom.xml file name '.git-versioned.pom.xml' Change By: Cyrille Le Clerc Summary: Maven versioning extension produces warnings due to temporary pom.xml file name '.git-versioned.pom.xml' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56666) maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-5 maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml' Change By: Cyrille Le Clerc Summary: Maven maven-git- versioning - extension produces causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml' Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56666) maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml'
Title: Message Title Cyrille Le Clerc commented on JENKINS-5 Re: maven-git-versioning-extension causes warnings due to temporary pom.xml file name '.git-versioned.pom.xml' Michael Düsterhus could you build and test https://github.com/jenkinsci/pipeline-maven-plugin/tree/JENKINS-5 ? Cyrille Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57144) tempBinDir is added with value '' by the code snippet generator
Title: Message Title Cyrille Le Clerc updated JENKINS-57144 3.6.10 Jenkins / JENKINS-57144 tempBinDir is added with value '' by the code snippet generator Change By: Cyrille Le Clerc Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57145) Reduce noisy logs when using withMaven inside a Docker container
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Fixed in 3.6.10 Jenkins / JENKINS-57145 Reduce noisy logs when using withMaven inside a Docker container Change By: Cyrille Le Clerc Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56232) Maven Local Repository is always seen as relative when it should be absolute
Title: Message Title Cyrille Le Clerc commented on JENKINS-56232 Re: Maven Local Repository is always seen as relative when it should be absolute Fixed in 3.6.10 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56772) Git branch with slashes are double encoded (Jenkins core and blue ocean)
Title: Message Title frederic larde commented on JENKINS-56772 Re: Git branch with slashes are double encoded (Jenkins core and blue ocean) I'm confused. It seems to work for you. I'm double checking my conf. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Daniel Beck commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Henrik Skupin We are unfamiliar with the Firefox release schedule, could you clarify what that means in terms of rolling out the change to regular users? Those who are on 66.0.3 right now? For Jenkins, based on usage statistics, 60% of LTS users are within the last 4 LTS releases (~4 months), and 50% of weekly release users are within the last 16 releases (~3.5 months). So I expect the majority of Jenkins users to be on compatible releases around August/September, and they can update no later than May (for LTS), and should already be updated (for weekly releases). From a project POV, we only consider the latest LTS and weekly releases (e.g. only those get security fixes) to be supported. Of course users may lag behind in updating, and for some setups, updating Jenkins is a big project. The question the Firefox team will need to answer is, how aggressively do they want to annoy Firefox+Jenkins users that update one but not the other. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Daniel Beck closed an issue as Fixed Jenkins / JENKINS-53462 Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Change By: Daniel Beck Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56593) Jenkins git clone fails intermittently
Title: Message Title Milind Sonawane commented on JENKINS-56593 Re: Jenkins git clone fails intermittently Thanks for the update Carlos. We suspected the same. While the JVM is requesting memory, we are not sure why it is demanding so much memory in the first place. We tried finding out using `top` command, yet there was nothing malicious or suspicious running. This is a new log we got: ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot class path? This issue was seen in issue JENKINS-53131. I guess updating the java version might help in this case, like your blog and this issue suggest. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title
Francisco Guimaraes updated an issue
Jenkins / JENKINS-57154
HTTP ERROR 403
Change By:
Francisco Guimaraes
After upgrading to github-oauth-plugin 0.32 I started to see this error in `/configureSecurity` when it tries to retrieve the name of a github user:{noformat}HTTP ERROR 403Problem accessing /descriptorByName/hudson.security.ProjectMatrixAuthorizationStrategy/checkName. Reason:Forbidden{noformat} The first user is has its name retrieved successfully but all others has the error mentioned above. See the attachment *users.png*.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title Francisco Guimaraes created an issue Jenkins / JENKINS-57154 HTTP ERROR 403 Issue Type: Bug Assignee: Sam Gleske Attachments: users.png Components: github-oauth-plugin Created: 2019-04-23 12:36 Environment: OS: Ubuntu 18.04.2 - 64 bit Java: openjdk version "1.8.0_191" github-oauth-plugin: 0.32 Jenkins: 2.164.2 Priority: Major Reporter: Francisco Guimaraes After upgrading to github-oauth-plugin 0.32 I started to see this error in `/configureSecurity` when it tries to retrieve the name of a github user: HTTP ERROR 403 Problem accessing /descriptorByName/hudson.security.ProjectMatrixAuthorizationStrategy/checkName. Reason:Forbidden The first user is has its name retrieved successfully but all others has the error mentioned above. See the attachment users.png.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title Francisco Guimaraes updated an issue Jenkins / JENKINS-57154 HTTP ERROR 403 Change By: Francisco Guimaraes Attachment: users.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title
Francisco Guimaraes updated an issue
Jenkins / JENKINS-57154
HTTP ERROR 403
Change By:
Francisco Guimaraes
After upgrading to github-oauth-plugin 0.32 I started to see this error in `/configureSecurity` when it tries to retrieve the name of a github user:{noformat}HTTP ERROR 403Problem accessing /descriptorByName/hudson.security.ProjectMatrixAuthorizationStrategy/checkName.Reason:Forbidden{noformat} The first user is has its name retrieved successfully but all others has hve the error mentioned above. See the attachment *users.png*.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title
Francisco Guimaraes updated an issue
Jenkins / JENKINS-57154
HTTP ERROR 403
Change By:
Francisco Guimaraes
After upgrading to github-oauth-plugin 0.32 I started to see this error in `/configureSecurity` when it tries to retrieve the name of a github user:{noformat}HTTP ERROR 403Problem accessing /descriptorByName/hudson.security.ProjectMatrixAuthorizationStrategy/checkName.Reason:Forbidden{noformat} The first user is has its name retrieved successfully but all others hve have the error mentioned above. See the attachment *users.png*.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title
Francisco Guimaraes updated an issue
Jenkins / JENKINS-57154
HTTP ERROR 403
Change By:
Francisco Guimaraes
After upgrading to github-oauth-plugin 0.32 I started to see this error in `/configureSecurity` when it tries to retrieve the name of a github user:{noformat}HTTP ERROR 403Problem accessing /descriptorByName/hudson.security.ProjectMatrixAuthorizationStrategy/checkName.Reason:Forbidden{noformat} The first user is has its name retrieved successfully but all others have the error mentioned above. See the attachment *users.png*.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title Francisco Guimaraes updated an issue Jenkins / JENKINS-57154 HTTP ERROR 403 Change By: Francisco Guimaraes Attachment: users.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title
Francisco Guimaraes updated an issue
Jenkins / JENKINS-57154
HTTP ERROR 403
Change By:
Francisco Guimaraes
After upgrading to github-oauth-plugin 0.32 I started to see this error in ` * /configureSecurity ` * when it tries to retrieve the name of a github user:{noformat}HTTP ERROR 403Problem accessing /descriptorByName/hudson.security.ProjectMatrixAuthorizationStrategy/checkName.Reason:Forbidden{noformat} The first user has its name retrieved successfully but all others have the error mentioned above. See the attachment *users.png*.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57154) HTTP ERROR 403
Title: Message Title
Francisco Guimaraes updated an issue
Jenkins / JENKINS-57154
HTTP ERROR 403
Change By:
Francisco Guimaraes
After upgrading to github-oauth-plugin 0.32 I started to see this error in */configureSecurity* when it tries to retrieve the name of a github user:{noformat}HTTP ERROR 403Problem accessing /descriptorByName/hudson.security.ProjectMatrixAuthorizationStrategy/checkName.Reason:Forbidden{noformat} The first user has its name retrieved successfully but all others have the error mentioned above. See the attachment *users.png*. The workaround for now is revert to 0.31.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54091) Messages with ampersands are HTML escaped
Title: Message Title Adarsh Ramamurthy commented on JENKINS-54091 Re: Messages with ampersands are HTML escaped Hi Martin Reinhardt, I'm using Rocket.Chat v2.15.0 and the Jenkins plugin is 0.5.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54091) Messages with ampersands are HTML escaped
Title: Message Title
Adarsh Ramamurthy updated an issue
Jenkins / JENKINS-54091
Messages with ampersands are HTML escaped
Change By:
Adarsh Ramamurthy
I am trying to send some messages using the Rocket.Chat notifier plugin that contains special characters such as ampersands. I use the Jenkins declarative pipeline syntax for this and the below snippet.{{rocketSend(}} {{ channel: 'notification-channel',}} {{ message: "[Click here]([http://www.example.com?param1=value1¶m2=value2¶m3=value3|http://www.example.com/?param1=value1¶m2=value2¶m3=value3])",}} {{ rawMessage: true}} {{)}}However, despite having set {{rawMessage: true}}, the messages that are received have all & characters HTML escaped into & causing any links containing query parameters in the message body to be broken.Thus in the above case, the body received will be { { code:java} [Click here]( [ http://www.example.com?param1=value1¶m2=value2¶m3=value3 |http://www.example.com/?param1=value1¶m2=value2¶m3=value3] ) {code } } instead of being { { code:java} [Click here]( [ http://www.example.com?param1=value1¶m2=value2¶m3=value3 |http://www.example.com/?param1=value1¶m2=value2¶m3=value3] ) {code } }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe
[JIRA] (JENKINS-54091) Messages with ampersands are HTML escaped
Title: Message Title
Adarsh Ramamurthy updated an issue
Jenkins / JENKINS-54091
Messages with ampersands are HTML escaped
Change By:
Adarsh Ramamurthy
I am trying to send some messages using the Rocket.Chat notifier plugin that contains special characters such as ampersands. I use the Jenkins declarative pipeline syntax for this and the below snippet.{{rocketSend(}} {{ channel: 'notification-channel',}} {{ message: "[Click here]([http://www.example.com?param1=value1¶m2=value2¶m3=value3|http://www.example.com/?param1=value1¶m2=value2¶m3=value3])",}} {{ rawMessage: true}} {{)}}However, despite having set {{rawMessage: true}}, the messages that are received have all & characters HTML escaped into & causing any links containing query parameters in the message body to be broken.Thus in the above case, the body received will be {code:java}[Click here](http://www.example.com?param1=value1¶m2=value2¶m3=value3) {code}instead of being{code:java}[Click here](http://www.example.com?param1=value1¶m2=value2¶m3=value3){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://group
[JIRA] (JENKINS-27306) unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[]
Title: Message Title Jesse Glick resolved as Duplicate I see no reason to try to support closures (lazy interpolation) inside a GString. This obscure Groovy feature can be easily replaced by the more straightforward idiom of defining a closure which returns a GString constructed using eager interpolation. So I am treating this as a duplicate of JENKINS-31314: the attempt to use this idiom ought to fail with a clear diagnostic message. Jenkins / JENKINS-27306 unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[] Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.googl
[JIRA] (JENKINS-27306) unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[]
Title: Message Title Jesse Glick resolved as Duplicate I see no reason to try to support closures (lazy interpolation) inside a GString. This obscure Groovy feature can be easily replaced by the more straightforward idiom of defining a closure which returns a GString constructed using eager interpolation. So I am treating this as a duplicate of JENKINS-31314: the attempt to use this idiom ought to fail with a clear diagnostic message. Jenkins / JENKINS-27306 unclassified new org.codehaus.groovy.runtime.GStringImpl java.lang.String java.lang.String[] Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.googl
[JIRA] (JENKINS-54091) Messages with ampersands are HTML escaped
Title: Message Title
Adarsh Ramamurthy updated an issue
Jenkins / JENKINS-54091
Messages with ampersands are HTML escaped
Change By:
Adarsh Ramamurthy
I am trying to send some messages using the Rocket.Chat notifier plugin that contains special characters such as ampersands. I use the Jenkins declarative pipeline syntax for this and the below snippet.{{rocketSend(}} {{ channel: 'notification-channel',}} {{ message: "[Click here]([http://www.example.com?param1=value1¶m2=value2¶m3=value3|http://www.example.com/?param1=value1¶m2=value2¶m3=value3])",}} {{ rawMessage: true}} {{)}}However, despite having set {{rawMessage: true}}, the messages that are received have all & characters HTML escaped into & causing any links containing query parameters in the message body to be broken.Thus in the above case, the body received will be {code:java}[Click here](http://www.example.com?param1=value1¶m2=value2¶m3=value3) {code}instead of being{code:java}[Click here](http://www.example.com?param1=value1¶m2=value2¶m3=value3){code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://group
[JIRA] (JENKINS-49006) ConcurrentModificationException in getThrottledPipelineRunsForCategory
Title: Message Title Nick Jones commented on JENKINS-49006 Re: ConcurrentModificationException in getThrottledPipelineRunsForCategory We were bitten by this today; a PR build (on a multibranch pipeline job) started freezing – appearing to still be in progress in the UI, but not assigned to any executor, and never progressing past the node step, with this in the Jenkins system log: Apr 23, 2019 7:36:18 AM WARNING jenkins.util.AtmostOneTaskExecutor$1 call null java.util.ConcurrentModificationException at java.util.TreeMap$PrivateEntryIterator.nextEntry(TreeMap.java:1211) at java.util.TreeMap$EntryIterator.next(TreeMap.java:1247) at java.util.TreeMap$EntryIterator.next(TreeMap.java:1242) at hudson.plugins.throttleconcurrents.ThrottleJobProperty.getThrottledPipelineRunsForCategory(ThrottleJobProperty.java:316) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.throttleCheckForCategoriesAllNodes(ThrottleQueueTaskDispatcher.java:283) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRunImpl(ThrottleQueueTaskDispatcher.java:256) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRun(ThrottleQueueTaskDispatcher.java:218) at hudson.plugins.throttleconcurrents.ThrottleQueueTaskDispatcher.canRun(ThrottleQueueTaskDispatcher.java:176) at hudson.model.Queue.getCauseOfBlockageForItem(Queue.java:1197) at hudson.model.Queue.maintain(Queue.java:1554) at hudson.model.Queue$1.call(Queue.java:325) at hudson.model.Queue$1.call(Queue.java:322) at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:108) at jenkins.util.AtmostOneTaskExecutor$1.call(AtmostOneTaskExecutor.java:98) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:112) at java.lang.Thread.run(Thread.java:748) I tried aborting and restarting it multiple times but it consistently behaved the same way; the only way we got it to build again was by commenting out the throttle block entirely. It would be marginally better if it had simply failed the build, but far better if this ConcurrentModificationException were not happening at all. Incidentially, this PR was a switch to use Scripted Pipeline due to JENKINS-45140, since Declarative Syntax didn't seem to throttle at all. Add Comment
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Song Koh commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. If I comment out the section of the code that Joe Mihalich posted. I am able to continue. There seems to be a disconnect between the sed script and the java -version output. Thanks for the tip, Joe. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43322) Nested view should be also searchable by name
Title: Message Title Baptiste Mathus updated JENKINS-43322 Jenkins / JENKINS-43322 Nested view should be also searchable by name Change By: Baptiste Mathus Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57001) Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun
Title: Message Title Padmapriya Balasundaram updated JENKINS-57001 Jenkins / JENKINS-57001 Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun Change By: Padmapriya Balasundaram Resolution: Duplicate Status: Fixed but Unreleased Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53462) Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox
Title: Message Title Henrik Skupin commented on JENKINS-53462 Re: Jenkins websites use non-trusted 'submit' event to start form submission when current browser is Firefox Daniel Beck thank you for bringing this up. It's actually not my job to make such a decision, so I will leave it up to the release managers to decide. I will clearly reference your last comment, so that they are aware of the situation for Jenkins users. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57155) Not able to connect to aws EKS
Title: Message Title venkatesh kristipati created an issue Jenkins / JENKINS-57155 Not able to connect to aws EKS Issue Type: Bug Assignee: Carlos Sanchez Attachments: image-2019-04-23-18-43-01-574.png Components: kubernetes-plugin Created: 2019-04-23 13:16 Environment: Kubernetes Plugin Labels: plugin kuberenetes-plugin Priority: Minor Reporter: venkatesh kristipati Hi Team, I am using jenkins kubernetes plugin for deploying and building for EKS cluster. But i am not able to use cross EKS cluster by creating a kubernetes cloud in kubernetes plugin. if there is any possibility please update me to configure that I am not able to accesses AWS EKS using jenkins kubernetes plugin. These are the below errors that are occurred while using this. !image-2019-04-23-18-43-01-574.png|thumbnail!
[JIRA] (JENKINS-57001) Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun
Title: Message Title Padmapriya Balasundaram updated an issue Jenkins / JENKINS-57001 Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun Change By: Padmapriya Balasundaram Attachment: image-2019-04-23-19-01-29-934.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57001) Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun
Title: Message Title Padmapriya Balasundaram commented on JENKINS-57001 Re: Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun Oleg Nenashev We have applied Whitelisting to the plugins( Build flow and dsl plugins) .PFA screenshot. Also can you please exactly say in which file(Path) we need to apply this whitelisting Suppress the entire whitelist by using "-Djenkins.security.ClassFilterImpl.SUPPRESS_WHITELIST=true" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57001) Build.xml is not getting saved. Failed to serialize com.cloudbees.plugins.flow.FlowRun#startJob for class com.cloudbees.plugins.flow.FlowRun
Title: Message Title Padmapriya Balasundaram started work on JENKINS-57001 Change By: Padmapriya Balasundaram Status: Reopened In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Nitya R updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Nitya R Attachment: RC0_log_v2.txt Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Nitya R commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 i have uploaded the latest log - RC0_log_v2.txt The build failed with CC_Wait_error, but it did not write the spool log multiple times like the previous version. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov updated an issue Jenkins / JENKINS-56976 WAIT ERROR even though when JESINTERFACELEVEL is 2 Change By: Alexander Shcherbakov Attachment: zos-connector-extra-space.hpi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56976) WAIT ERROR even though when JESINTERFACELEVEL is 2
Title: Message Title Alexander Shcherbakov commented on JENKINS-56976 Re: WAIT ERROR even though when JESINTERFACELEVEL is 2 forgot to add extra space for rc processing. Kindly retest. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Song Koh could you please apply what I asked in my previous comment and provide me the same output so I can see what I missed in the sed _expression_? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46124) EnvStep convert map to list
Title: Message Title jerry wiltse commented on JENKINS-46124 Re: EnvStep convert map to list Did anyone ever file a separate issue to create an overload of withEnv which takes a Map? Indeed, the overload to pass a Map would be convenient for us as well. I assumed the reason for the current signature was that Groovy's underlying string helper function "execute()" takes a String[] called envp for environment variables, so withEnv was designed in such a way that the env vars could just be passed through without a type conversion. Otherwise, I can't imagine why it was designed this way. Of note, it seems the GDSL file currently says it takes a Map, which appears to be simply incorrect. method(name: 'withEnv', type: 'Object', params: [overrides:Map, body:'Closure'], doc: 'Set environment variables') Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57085) Stack Traces with complex file names cannot be deserialized by XStream
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-57085 Stack Traces with complex file names cannot be deserialized by XStream Offhand it sounds like groovy-cps is creating poor bytecode, and XStream is also behaving poorly. Ideally both would be fixed. Probably best to focus on groovy-cps to start with, since getting fixes into upstream XStream could take a while. (We have a fork anyway, but I would rather not add to the diff.) Change By: Jesse Glick Component/s: workflow-cps-plugin Labels: pipeline xstream Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title Michał Czech commented on JENKINS-56890 Re: IOException: "cannot find current thread" Jenkins 2.164.1: 15:55:20 ERROR during Build: java.io.IOException: cannot find current thread*15:55:20* at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300)15:55:20 at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88)15:55:20 at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67)15:55:20 at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254)15:55:20 at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162)15:55:20 at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140)15:55:20 at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title William F edited a comment on JENKINS-56890 Re: IOException: "cannot find current thread" looking at the class methods where "threads" (a TreeMap) is accessed: https://github.com/jenkinsci/workflow-cps-plugin/blob/ master f610f0bcf732b13ff542dd4f716d9520988f99a7 /src/main/java/org/jenkinsci/plugins/workflow/cps/CpsThreadGroup.java# L176 L186 - L195 L205 I see that there is an attempt to ensure that all "put" calls are executed within the same thread -- but AFAICT there is no such logic for "get".Given that TreeMap is NOT a thread-safe class, if calls to "threads.put" and "threads.get" are interleaved, it is entirely possible to get "null" when invoking "get" for a key that has been "put" in another thread.Even without interleaved execution, I believe it would be possible to get such behavior simply via invoking "put" and "get" in different threads without any synchronization constructs, in terms of the Java Memory Model (but my own memory regarding the JMM is pretty hazy).In other words, from a glance, it really just looks like "threads" is being manipulated in a non-threadsafe manner. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Rohit Goel created an issue Jenkins / JENKINS-57156 p4 plugin : Invalid credentials Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-04-23 14:51 Environment: Jenkins home directory is set to /var/lib/jenkins Priority: Blocker Reporter: Rohit Goel I am trying to setup Jenkins with P4 plugin on RHEL. Jenkins is up and running but when I try to add credentials using perforce password, it fails with the below error. I believe I know the reason - there is nothing called /home/jenkins and it cannot be created as the user "home" are managed by our IT team. It seems like the plugin is trying to do something at "/home/jenkins" and fails. How can I specify some other location instead ? Apr 23, 2019 8:13:02 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connect SEVERE: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: com.perforce.p4java.exception.ConfigException: java.nio.file.AccessDeniedException: /home/jenkins Apr 23, 2019 8:13:02 PM org.jenkinsci.plugins.p4.client.ConnectionHelper INFO: P4: Unable to login: com.perforce.p4java.exception.ConnectionException: com.perforce.p4java.exception.ConfigException: java.nio.file.AccessDeniedException: /home/jenkins Apr 23, 2019 8:13:02 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Connection retry: 1 Apr 23, 2019 8:13:02 PM org.jenkinsci.plugins.p4.client.ConnectionHelper INFO: P4: Connection retry: 1 Apr 23, 2019 8:13:05 PM org.jenkinsci.plugins.p4.client.ConnectionHelper connectionRetry SEVERE: P4: Invalid credentials. Giving up... Apr 23, 2019 8:13:05 PM org.jenkinsci.plugins.p4.client.ConnectionHelper INFO: P4: Invalid credentials. Giving up...
[JIRA] (JENKINS-57157) Global Tools fail to update automatic installs
Title: Message Title Josiah Eubank created an issue Jenkins / JENKINS-57157 Global Tools fail to update automatic installs Issue Type: Bug Assignee: Sonar Team Components: sonar, workflow-basic-steps-plugin Created: 2019-04-23 14:55 Environment: Jenkins 2.173, Pipeline Basic Steps 2.15, Sonarqube Scanner for Jenkins 2.8.1 Labels: tools sonarqube update pipeline automatic-install Priority: Minor Reporter: Josiah Eubank When a tool is upgraded versions or the automatic installer is changed, Jenkins does not update the tool installed on the build agent. For example, the Sonarqube plugin installs its scanner as a Global Tool with an automatic installer from maven (populated dropdown). If you change versions, the new version does not overwrite the previous version on the build agent. Current workaround is to manually delete the tools directory from every build agent when upgrading any tools. Expected behavior: either install the tool to a version specific directory based on the source (zip file name, maven version, etc) or overwrite the generic directory with whichever version is specified in Global Tool Configuration (either upgrade or downgrade)
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Karl Wirth assigned an issue to Karl Wirth Jenkins / JENKINS-57156 p4 plugin : Invalid credentials Change By: Karl Wirth Assignee: Karl Wirth Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57156 p4 plugin : Invalid credentials Change By: Karl Wirth Attachment: image-2019-04-23-16-02-31-176.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57158) Pipeline is green but shows red in stage view
Title: Message Title Jeff Care created an issue Jenkins / JENKINS-57158 Pipeline is green but shows red in stage view Issue Type: Bug Assignee: Sam Van Oort Attachments: green_red.JPG, support_2019-04-23_14.58.31.zip Components: pipeline-stage-view-plugin Created: 2019-04-23 15:02 Priority: Minor Reporter: Jeff Care We had a build complete successfully; it shows green when viewing the details for that particular build and in the list of builds for that job. However, in the stage view for the job, that particular build shows red. Screenshot attached. Add Comment
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Karl Wirth commented on JENKINS-57156 Re: p4 plugin : Invalid credentials Hi Rohit Goel, what is 'Home directory' set to in your Jenkins setup? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57159) Improve JobConfigHistory to support managed files
Title: Message Title Tim Bradt created an issue Jenkins / JENKINS-57159 Improve JobConfigHistory to support managed files Issue Type: New Feature Assignee: Stefan Brausch Components: jobconfighistory-plugin Created: 2019-04-23 15:12 Environment: Cloudbees Core Managed Master 2.138.2.2-rolling OS unknown - whatever Cloudbees uses Job Configuration History Plugin 2.18.3 Using Chrome for web browser Priority: Major Reporter: Tim Bradt The JobConfigHistory plugin works for jobs as well as system configuration. The other primary component that serves a good chunk of our configuration is the managed files, which this plugin does not currently support, and we feel that pain. It would be extremely useful to have this. Add Comment
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Song Koh commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Sure. The output is... - Found an incorrect Java version Java version found: 110 2019-01-15 Aborting - Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Song Koh commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Just for the record, the original post already had this info... "The second problem is, the value of JAVA_VERSION after that command with java 11 installed is: "110 2019-01-15". So that command is completely broken for java 11." Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Song Koh thank you. I know it was included in the original post, but I thought I fixed it with the PR I filled. Could you please make sure you are using the same /etc/init.d/jenkins context as in https://github.com/jenkinsci/packaging/pull/117? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Rohit Goel updated an issue Jenkins / JENKINS-57156 p4 plugin : Invalid credentials Change By: Rohit Goel Attachment: image-2019-04-23-21-24-06-898.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57156) p4 plugin : Invalid credentials
Title: Message Title Rohit Goel commented on JENKINS-57156 Re: p4 plugin : Invalid credentials Hi Karl, Its set to /var/lib/jenkins. I have tried changing to some other location as well (with chmod -R 777), but no difference -Rohit Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. Hi, here's the output you requested: jmihalich@ubuntu1804-jm:~$ sudo /etc/init.d/jenkins start JAVA_VERSION = 110 Correct java version found [] Starting jenkins (via systemctl): jenkins.serviceJob for jenkins.service failed because the control process exited with error code. See "systemctl status jenkins.service" and "journalctl -xe" for details. failed! jmihalich@ubuntu1804-jm:~$ ls -la /var/lib/jenkins total 8 drwxr-xr-x 2 jenkins jenkins 4096 Apr 22 15:09 . drwxr-xr-x 36 root root 4096 Apr 23 15:49 .. I want to repeat again that, for whatever reason, after running sudo apt-get install jenkins, and it fails, the /var/lib/jenkins directory is empty. (see above). That is most likely why jetty startup is failing. Joe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56723) Add unit tests for IssueDifference
Title: Message Title Ulli Hafner updated JENKINS-56723 Jenkins / JENKINS-56723 Add unit tests for IssueDifference Change By: Ulli Hafner Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Adrien Lecharpentier commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. thank you Joe Mihalich. So the java version is correctly parsed, the sed _expression_ is correct. The problem must be after that The fact that the /var/lib/jenkins is empty is not a real surprise, as the instance didn't start once, there is no "jenkins-home" (which is the purpose of the folder). Could you please provide me the output of journalctl -xe? Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57096) The latest debian installers 2.164+ do not work with java 11.
Title: Message Title Joe Mihalich commented on JENKINS-57096 Re: The latest debian installers 2.164+ do not work with java 11. jmihalich@ubuntu1804-jm:~$ journalctl -xe – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent (ssh-agent emulation). – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (access for web browsers). – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG network certificate management daemon. – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache (restricted). – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Closed GnuPG cryptographic agent and passphrase cache. – Subject: Unit UNIT has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Reached target Shutdown. – Subject: Unit UNIT has finished start-up – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has finished starting up. – -- The start-up result is RESULT. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Starting Exit the Session... – Subject: Unit UNIT has begun start-up – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit UNIT has begun starting up. Apr 23 15:55:13 ubuntu1804-jm systemd[8863]: Received SIGRTMIN+24 from PID 8881 (kill). Apr 23 15:55:13 ubuntu1804-jm systemd[1]: user@0.service: Killing process 8881 (kill) with signal SIGKILL. Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Stopped User Manager for UID 0. – Subject: Unit user@0.service has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit user@0.service has finished shutting down. Apr 23 15:55:13 ubuntu1804-jm systemd[1]: Removed slice User Slice of root. – Subject: Unit user-0.slice has finished shutting down – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit user-0.slice has finished shutting down. Apr 23 15:55:14 ubuntu1804-jm jenkins[8814]: ...fail! Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Control process exited, code=exited status=7 Apr 23 15:55:14 ubuntu1804-jm systemd[1]: jenkins.service: Failed with result 'exit-code'. Apr 23 15:55:14 ubuntu1804-jm systemd[1]: Failed to start LSB: Start @@PRODUCTNAME@@ at boot time. – Subject: Unit jenkins.service has failed – Defined-By: systemd – Support: http://www.ubuntu.com/support – -- Unit jenkins.service has failed. – -- The result is RESULT. Apr 23 15:55:14 ubuntu1804-jm sudo[8782]: pam_unix(sudo:session): session closed for user root Apr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]: Network configuration changed, trying to establish connection. Apr 23 15:58:46 ubuntu1804-jm systemd-networkd[647]: enp0s8: DHCP: No routes received from DHCP server: No data available Apr 23 15:58:46 ubuntu1804-jm systemd-timesyncd[447]: Synchronized to time server 91.189.89.198:123
