[JIRA] (JENKINS-58503) Symbols for Extensions
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-58503 Symbols for Extensions Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200643.1563227792000.10010.1586832240158%40Atlassian.JIRA.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title Mark Waite commented on JENKINS-61711 Re: Git plugin global config incorrectly reports git not in PATH Rishabh Budhouliya I was concerned that the problem might be specific to my Docker image, so I tested a fresh download of Jenkins 2.222.1 run as a war file on my Ubuntu 18.04 computer. Steps in this test were: Download Jenkins 2.222.1 war file $ wget http://mirrors.jenkins.io/war-stable/2.222.1/jenkins.war Run war file $ java -jar jenkins.war Connect to the Jenkins instance on port 8080 with a web browser Enter the random admin password for Jenkins Create a user account in Jenkins Choose to install selected plugins from the install wizard, select "None", then select only the git plugin Complete the install wizard, watch the plugins as they install Open "Manage Jenkins" and the "Global Tool Configuration" page Review the "git" configured for the Default git tool, confirm that it reports that "git" cannot be found, even though there is a git installed in /usr/bin on my computer Thanks again for investigating! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title
Mark Waite edited a comment on JENKINS-61711
Re: Git plugin global config incorrectly reports git not in PATH
[~rishabhbudhouliya] thanks very much for investigating and for trying to duplicate the problem. I should have provided a precise set of steps that will duplicate the problem. The steps are:# Install and enable the git LFS extension (if not already installed)# Install Docker# Clone my [docker-lfs repository|https://github.com/MarkEWaite/docker-lfs] {{$ git clone https://github.com/MarkEWaite/docker-lfs.git}}# Change to the cloned directory {{$ cd docker-lfs}}# Checkout the lts branch {{$ git checkout -b lts -t origin/lts}}# Remove the master branch {{$ git branch -D --delete master}}# Checkout the lts-with-plugins branch {{$ git checkout -b lts-with-plugins -t origin/lts-with-plugins}}# Build the lts-with-plugins image {{$ ./docker_build.py}}# Run the lts-with-plugins image {{$ ./docker_run.py --clean --quiet}}# Open the newly started Jenkins in a web browser on port 8080# Open "Manage Jenkins"# Open "Global Tool Configuration"# Scroll down to show the git tool configuration# Wait briefly while Jenkins checks for existence of the git tool, not that there is a red warning below that field which reports the tool is not available
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title
Mark Waite edited a comment on JENKINS-61711
Re: Git plugin global config incorrectly reports git not in PATH
[~rishabhbudhouliya] thanks very much for investigating and for trying to duplicate the problem. I should have provided a precise set of steps that will duplicate the problem. The steps are:# Install and enable the git LFS extension (if not already installed)# Install Docker# Clone my [docker-lfs repository|https://github.com/MarkEWaite/docker-lfs] {{$ git clone https://github.com/MarkEWaite/docker-lfs.git}}# Change to the cloned directory {{$ cd docker-lfs}}# Checkout the lts branch {{$ git checkout -b lts -t origin/lts}}# Remove the master branch {{$ git branch -D --delete master}}# Checkout the lts-with-plugins branch {{$ git checkout -b lts-with-plugins -t origin/lts-with-plugins}}# Build the lts-with-plugins image {{$ ./docker_build.py}}# Run the lts-with-plugins image {{$ ./docker_run.py --clean --quiet}}# Open the newly started Jenkins in a web browser on port 8080# Open "Manage Jenkins"# Open "Global Tool Configuration"# Scroll down to show the git tool configuration# Wait briefly while Jenkins checks for existence of the git tool, not note that there is a red warning below that field which reports the tool is not available
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title
Mark Waite edited a comment on JENKINS-61711
Re: Git plugin global config incorrectly reports git not in PATH
[~rishabhbudhouliya] thanks very much for investigating and for trying to duplicate the problem. I should have provided a precise set of steps that will duplicate the problem. The steps are:# Install and enable the git LFS extension (if not already installed)# Install Docker# Clone my [docker-lfs repository|https://github.com/MarkEWaite/docker-lfs] {{$ git clone https://github.com/MarkEWaite/docker-lfs.git}}# Checkout the lts branch {{$ git checkout - b lts -t origin/lts}}# Remove the master branch {{$ git branch -D --delete master}}# Checkout the lts- with-plugins branch {{$ git checkout -b lts-with-plugins -t origin/lts-with-plugins}}# Build the lts-with-plugins image {{$ ./docker_build.py}}# Run the lts-with-plugins image {{$ ./docker_run.py --clean --quiet}}# Open the newly started Jenkins in a web browser on port 8080# Open "Manage Jenkins"# Open "Global Tool Configuration"# Scroll down to show the git tool configuration# Wait briefly while Jenkins checks for existence of the git tool, not that there is a red warning below that field which reports the tool is not available
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title Mark Waite commented on JENKINS-61711 Re: Git plugin global config incorrectly reports git not in PATH Rishabh Budhouliya thanks very much for investigating and for trying to duplicate the problem. I should have provided a precise set of steps that will duplicate the problem. The steps are: Install and enable the git LFS extension (if not already installed) Install Docker Clone my docker-lfs repository $ git clone https://github.com/MarkEWaite/docker-lfs.git Checkout the lts-with-plugins branch $ git checkout -b lts-with-plugins -t origin/lts-with-plugins Build the lts-with-plugins image $ ./docker_build.py Run the lts-with-plugins image $ ./docker_run.py --clean --quiet Open the newly started Jenkins in a web browser on port 8080 Open "Manage Jenkins" Open "Global Tool Configuration" Scroll down to show the git tool configuration Wait briefly while Jenkins checks for existence of the git tool, not that there is a red warning below that field which reports the tool is not available Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title Rishabh Budhouliya edited a comment on JENKINS-61711 Re: Git plugin global config incorrectly reports git not in PATH Hi [~markewaite]. I was trying to reproduce this bug and I can't figure out a way to do it. I'd like to know if this is a windows or a linux machine.As it can be seen, the environment variable ` * PATH ` * is being used to find the git executable and depending upon the OS, it will try to append * PATH + "git" * and try to check if that exists. Since you have mentioned that the git executable _does_ exist on the path, it doesn't make sense to me how could the ` FormValidation validateExecutable` _validateExecutable_ can't find it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205537.1585325185000.9978.1586813400751%40Atlassian.JIRA.
[JIRA] (JENKINS-61711) Git plugin global config incorrectly reports git not in PATH
Title: Message Title Rishabh Budhouliya commented on JENKINS-61711 Re: Git plugin global config incorrectly reports git not in PATH Hi Mark Waite. I was trying to reproduce this bug and I can't figure out a way to do it. I'd like to know if this is a windows or a linux machine. As it can be seen, the environment variable `PATH` is being used to find the git executable and depending upon the OS, it will try to append PATH + "git" and try to check if that exists. Since you have mentioned that the git executable does exist on the path, it doesn't make sense to me how could the `FormValidation validateExecutable` can't find it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205537.1585325185000.9969.1586813340177%40Atlassian.JIRA.
[JIRA] (JENKINS-61888) Connection terminated for Windows slave
Title: Message Title Rishitha Kokku created an issue Jenkins / JENKINS-61888 Connection terminated for Windows slave Issue Type: Task Assignee: Emilio Escobar Components: windows-slaves-plugin Created: 2020-04-13 21:07 Priority: Blocker Reporter: Rishitha Kokku The Windows slave launching is failing with the below error Inbound agent connected from prodproxy_proxy1_1.jenkins_prod/172.192.17.170 Remoting version: 3.36.1 This is a Windows agent NOTE: Relative remote path resolved to: C:\Users\rkokku\Desktop\APVED51593.Ms.ds.uhc.com ERROR: Connection terminated java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795) Caused: hudson.remoting.ChannelClosedException: Channel "hudson.remoting.Channel@afa23fe:JNLP4-connect connection from prodproxy_proxy1_1.jenkins_prod/172.192.17.170:47378": Remote call on JNLP4-connect connection from prodproxy_proxy1_1.jenkins_prod/172.192.17.170:47378 failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:948) at jenkins.util.SystemProperties$AgentCopier.preOnline(SystemProperties.java:134) at
[JIRA] (JENKINS-60976) JCasC export doesn't work with Custom Tools plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-60976 JCasC export doesn't work with Custom Tools plugin Change By: Oleg Nenashev Labels: jcasc-compatibility Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.20.1580900198000.9963.1586809740333%40Atlassian.JIRA.
[JIRA] (JENKINS-37694) link to archived build artifacts is hidden until pipeline has finished
Title: Message Title Eugene G commented on JENKINS-37694 Re: link to archived build artifacts is hidden until pipeline has finished Thank you, Christopher Head, it works! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173822.1472152728000.9948.1586808060823%40Atlassian.JIRA.
[JIRA] (JENKINS-30680) Make Custom Tools compatible with Pipeline
Title: Message Title Michael Lasevich commented on JENKINS-30680 Re: Make Custom Tools compatible with Pipeline out of curiosity, what is wrong with just using it via current "tool" step support? Why do we need a custom step for this? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.165285.1443461181000.9911.1586805720680%40Atlassian.JIRA.
[JIRA] (JENKINS-60976) JCasC export doesn't work with Custom Tools plugin
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-60976 JCasC export doesn't work with Custom Tools plugin Change By: Tim Jacomb Component/s: configuration-as-code-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.20.1580900198000.9902.1586805360502%40Atlassian.JIRA.
[JIRA] (JENKINS-60976) JCasC export doesn't work with Custom Tools plugin
Title: Message Title Tim Jacomb assigned an issue to Unassigned Jenkins / JENKINS-60976 JCasC export doesn't work with Custom Tools plugin Change By: Tim Jacomb Assignee: Ewelina Wilkosz Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.20.1580900198000.9907.1586805360642%40Atlassian.JIRA.
[JIRA] (JENKINS-60889) Add example global config to Readme and wiki pages
Title: Message Title Markus Winter commented on JENKINS-60889 Re: Add example global config to Readme and wiki pages Three arguments why I don't like this: I think the preferred way to configure a Jenkins instance is by using the configuration as code plugin nowadays. It isn't hard to configure your Jenkins in the UI and then look up the generated XML in JENKINS_HOME that is not specific to this plugin but can be used for any plugin It is another place you have to keep in sync in the docs which you will probably easy forget to update Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204277.1580207843000.9898.1586804520180%40Atlassian.JIRA.
[JIRA] (JENKINS-61887) Use IAM Role field is populated properly when loading the configuration page.
Title: Message Title Mark Ketchum started work on JENKINS-61887 Change By: Mark Ketchum Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205757.1586800842000.9895.1586804040158%40Atlassian.JIRA.
[JIRA] (JENKINS-61887) Use IAM Role field is populated properly when loading the configuration page.
Title: Message Title Mark Ketchum updated JENKINS-61887 Fixed here, awaiting merge. https://github.com/jenkinsci/s3-plugin/pull/128 Jenkins / JENKINS-61887 Use IAM Role field is populated properly when loading the configuration page. Change By: Mark Ketchum Status: In Progress Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-41558) Memory leak in Jenkins stage view
Title: Message Title Devin Nusbaum commented on JENKINS-41558 Re: Memory leak in Jenkins stage view Here are some notes from when a few developers looked into this a few months back: Whenever Stage View receives an event, it re-renders the entire table. When that happens, all of the DOM nodes from the last render pass should become unreachable and be garbage collected, but right now, that does not happen, because there are a bunch of references to those nodes from the page-wide instance of JQuery (definitely via event listeners, but also via other JQuery-internal paths which we did not fully understand), so the old nodes are retained forever, causing the memory leak. We did not see an obvious or easy way to fix this, but we are not _javascript_ experts, so maybe someone with more experience in the area would be able to quickly figure out how to fix it. Maybe we need to modify all event listener registration so that the listeners are stored at the top level and can be cleared out when an event is received before re-rendering the table, maybe the version of JQuery being used needs to be updated, maybe both, etc. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178372.1485779454000.9887.1586803381906%40Atlassian.JIRA.
[JIRA] (JENKINS-57206) Support draft pull requests from GitHub
Title: Message Title Jordan Jennings commented on JENKINS-57206 Re: Support draft pull requests from GitHub Draft PRs working here as well now. Maybe a complete coincidence, but as soon as we upgraded after the fix for JENKINS-54126 was released everything has been working as expected. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198963.1556379411000.9818.1586803020338%40Atlassian.JIRA.
[JIRA] (JENKINS-61887) Use IAM Role field is populated properly when loading the configuration page.
Title: Message Title
Mark Ketchum updated an issue
Jenkins / JENKINS-61887
Use IAM Role field is populated properly when loading the configuration page.
Change By:
Mark Ketchum
After upgrading to version 0.11.5 from 0.11.3, the current state of the Use IAM Role field is not preserved. This means it is set to false every time the Jenkins configuration is saved from https://jenkins/configure. Looks to be a side effect from this commit: https://github.com/jenkinsci/s3-plugin/commit/ee92830bc670b1ab70d19b34fa2ee1a3e0dac12c Jobs attempting to publish to s3 will have this error after saving the Jenkings configuration without modifying the Amazon S3 profiles section:{code}ERROR: Failed to upload filescom.amazonaws.services.s3.model.AmazonS3Exception: The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential. (Service: Amazon S3; Status Code: 400; Error Code: AuthorizationHeaderMalformed; Request ID: 0DA8BA8E16511839; S3 Extended Request ID: +O1juVW903Ay7gNmlzIoLxnVGUXZwcChRUriu1forYHfU9nv+BXOXy5zOvRCkbFPk1NHrCQ9ybc=), S3 Extended Request ID: +O1juVW903Ay7gNmlzIoLxnVGUXZwcChRUriu1forYHfU9nv+BXOXy5zOvRCkbFPk1NHrCQ9ybc= at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1799) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1383) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1359) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1139) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:796) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:764) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:738) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:698) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:680) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:544) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:524) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5052) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4998) at com.amazonaws.services.s3.AmazonS3Client.initiateMultipartUpload(AmazonS3Client.java:3574) at com.amazonaws.services.s3.transfer.internal.UploadCallable.initiateMultipartUpload(UploadCallable.java:362) at com.amazonaws.services.s3.transfer.internal.UploadCallable.uploadInParts(UploadCallable.java:178) at com.amazonaws.services.s3.transfer.internal.UploadCallable.call(UploadCallable.java:121) at com.amazonaws.services.s3.transfer.internal.UploadMonitor.call(UploadMonitor.java:143) at com.amazonaws.services.s3.transfer.internal.UploadMonitor.call(UploadMonitor.java:48) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
[JIRA] (JENKINS-61887) Use IAM Role field is populated properly when loading the configuration page.
Title: Message Title
Mark Ketchum updated an issue
Jenkins / JENKINS-61887
Use IAM Role field is populated properly when loading the configuration page.
Change By:
Mark Ketchum
After upgrading to version 0.11.5 from 0.11.3, the current state of the Use IAM Role field is not preserved. This means it is set to false every time the Jenkins configuration is saved from https://jenkins/configure. Looks to be a side effect from this commit: https://github.com/jenkinsci/s3-plugin/commit/ee92830bc670b1ab70d19b34fa2ee1a3e0dac12c Jobs attempting to publish to s3 will have this error after saving the Jenkings configuration without modifying the Amazon S3 profiles section:{code}ERROR: Failed to upload filescom.amazonaws.services.s3.model.AmazonS3Exception: The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential. (Service: Amazon S3; Status Code: 400; Error Code: AuthorizationHeaderMalformed; Request ID: 0DA8BA8E16511839; S3 Extended Request ID: +O1juVW903Ay7gNmlzIoLxnVGUXZwcChRUriu1forYHfU9nv+BXOXy5zOvRCkbFPk1NHrCQ9ybc=), S3 Extended Request ID: +O1juVW903Ay7gNmlzIoLxnVGUXZwcChRUriu1forYHfU9nv+BXOXy5zOvRCkbFPk1NHrCQ9ybc= at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1799) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1383) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1359) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1139) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:796) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:764) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:738) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:698) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:680) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:544) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:524) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5052) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4998) at com.amazonaws.services.s3.AmazonS3Client.initiateMultipartUpload(AmazonS3Client.java:3574) at com.amazonaws.services.s3.transfer.internal.UploadCallable.initiateMultipartUpload(UploadCallable.java:362) at com.amazonaws.services.s3.transfer.internal.UploadCallable.uploadInParts(UploadCallable.java:178) at com.amazonaws.services.s3.transfer.internal.UploadCallable.call(UploadCallable.java:121) at com.amazonaws.services.s3.transfer.internal.UploadMonitor.call(UploadMonitor.java:143) at com.amazonaws.services.s3.transfer.internal.UploadMonitor.call(UploadMonitor.java:48) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
[JIRA] (JENKINS-61887) Use IAM Role field is populated properly when loading the configuration page.
Title: Message Title
Mark Ketchum updated an issue
Jenkins / JENKINS-61887
Use IAM Role field is populated properly when loading the configuration page.
Change By:
Mark Ketchum
After upgrading to version 0.11.5 from 0.11.3, the current state of the Use IAM Role field is not preserved. This means it is set to false every time the Jenkins configuration is saved from https://jenkins/configure.Looks to be a side effect from this commit: https://github.com/jenkinsci/s3-plugin/commit/ee92830bc670b1ab70d19b34fa2ee1a3e0dac12c Jobs attempting to publish to s3 will have this error after saving the Jenkings configuration without modifying the Amazon S3 profiles section:{code}ERROR: Failed to upload filescom.amazonaws.services.s3.model.AmazonS3Exception: The authorization header is malformed; a non-empty Access Key (AKID) must be provided in the credential. (Service: Amazon S3; Status Code: 400; Error Code: AuthorizationHeaderMalformed; Request ID: 0DA8BA8E16511839; S3 Extended Request ID: +O1juVW903Ay7gNmlzIoLxnVGUXZwcChRUriu1forYHfU9nv+BXOXy5zOvRCkbFPk1NHrCQ9ybc=), S3 Extended Request ID: +O1juVW903Ay7gNmlzIoLxnVGUXZwcChRUriu1forYHfU9nv+BXOXy5zOvRCkbFPk1NHrCQ9ybc= at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleErrorResponse(AmazonHttpClient.java:1799) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleServiceErrorResponse(AmazonHttpClient.java:1383) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1359) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1139) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:796) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:764) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:738) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:698) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:680) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:544) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:524) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5052) at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:4998) at com.amazonaws.services.s3.AmazonS3Client.initiateMultipartUpload(AmazonS3Client.java:3574) at com.amazonaws.services.s3.transfer.internal.UploadCallable.initiateMultipartUpload(UploadCallable.java:362) at com.amazonaws.services.s3.transfer.internal.UploadCallable.uploadInParts(UploadCallable.java:178) at com.amazonaws.services.s3.transfer.internal.UploadCallable.call(UploadCallable.java:121) at com.amazonaws.services.s3.transfer.internal.UploadMonitor.call(UploadMonitor.java:143) at com.amazonaws.services.s3.transfer.internal.UploadMonitor.call(UploadMonitor.java:48) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
[JIRA] (JENKINS-61887) Use IAM Role field is populated properly when loading the configuration page.
Title: Message Title Mark Ketchum created an issue Jenkins / JENKINS-61887 Use IAM Role field is populated properly when loading the configuration page. Issue Type: Bug Assignee: Mark Ketchum Components: s3-plugin Created: 2020-04-13 18:00 Environment: Jenkins ver. 2.222.1 0.11.5 Priority: Minor Reporter: Mark Ketchum After upgrading to version 0.11.5 from 0.11.3, the current state of the Use IAM Role field is not preserved. This means it is set to false every time the Jenkins configuration is saved from https://jenkins/configure. Looks to be a side effect from this commit: https://github.com/jenkinsci/s3-plugin/commit/ee92830bc670b1ab70d19b34fa2ee1a3e0dac12c Add Comment
[JIRA] (JENKINS-61886) Merge Conflicts should cause a failed status notification to be sent to Github
Title: Message Title Thomas Wunderlich created an issue Jenkins / JENKINS-61886 Merge Conflicts should cause a failed status notification to be sent to Github Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2020-04-13 17:51 Priority: Minor Reporter: Thomas Wunderlich When a github PR has merge conflicts, the build fails in Jenkins but the build status is not sent to Github. What would be preferred is that when there's a build failure, even if it's caused by a merge conflict it should be sent to github as a failed build Current Console output Pull request #7185 updated11:14:42 Connecting to https://api.github.com using XX/** (Github credentials to use with multi-branch pipeline jobs)ERROR: Pull request 7185 : Not mergeable at 7f6888e4b84674f7218ae4b4673c671039402c52+3a8a37fcc703e389c16ffd9ff5493c180ba54a72 (NOT_MERGEABLE) Finished: FAILURE Add Comment
[JIRA] (JENKINS-61848) hudson.AbortException: Ansible playbook execution failed
Title: Message Title Mark Waite closed an issue as Not A Defect Please don't use the Jenkins issue tracker to submit questions. The Jenkins user mailing list and chat channels are much better suited for questions and answers. More people read those locations and more people can help in those locations. Jenkins / JENKINS-61848 hudson.AbortException: Ansible playbook execution failed Change By: Mark Waite Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google
[JIRA] (JENKINS-61846) E200015: authentication cancelled
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Insufficient information to duplicate the problem. Jenkins / JENKINS-61846 E200015: authentication cancelled Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61881) Jenkins build failing due to failure of creation of docker container(ppwershell failure)
Title: Message Title Mark Waite commented on JENKINS-61881 Re: Jenkins build failing due to failure of creation of docker container(ppwershell failure) Please provide instructions that another person can follow to duplicate the error. As described in the initial issue report, this appears to be more of a request for help diagnosing "what changed?" rather than an issue report due to something in a specific release of Jenkins or one of its plugins. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205751.1586784187000.9800.1586800140232%40Atlassian.JIRA.
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title Alex Earl assigned an issue to Unassigned Jenkins / JENKINS-59198 NullPointerException in hudson.util.Secret$1.convert Change By: Alex Earl Assignee: Alex Earl Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201641.1567478279000.9793.1586797980216%40Atlassian.JIRA.
[JIRA] (JENKINS-49644) API does not return all running builds
Title: Message Title Mike Yang commented on JENKINS-49644 Re: API does not return all running builds This seems to be working again in `2.222.1`. And I think it was still broken as of `2.204`. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188570.1519124859000.9781.1586797800223%40Atlassian.JIRA.
[JIRA] (JENKINS-56694) Logstash-plugin Send arbitrary data to random targets
Title: Message Title Markus Winter commented on JENKINS-56694 Re: Logstash-plugin Send arbitrary data to random targets implementing an arbitrary endpoint would only work es but not for the other implementations. So this doesn't make sense in this plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198332.1553296008000.9778.1586796960125%40Atlassian.JIRA.
[JIRA] (JENKINS-59110) Logstash plugin: Not working for Pipeline jobs when 'Enabled Globally'
Title: Message Title Markus Winter commented on JENKINS-59110 Re: Logstash plugin: Not working for Pipeline jobs when 'Enabled Globally' opened https://github.com/jenkinsci/logstash-plugin/pull/93 that enables global logging for pipeline Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201535.1566943198000.9774.1586796720266%40Atlassian.JIRA.
[JIRA] (JENKINS-54537) Scripted Pipeline does not work due to tags
Title: Message Title
Isabel G. commented on JENKINS-54537
Re: Scripted Pipeline does not work due to tags
Hello, we have the same warnings. Do anyone know if will someone release a new plugin version soon? Infra:
Jenkins 2.204.6
Rundeck plugin 3.6.7
Rundeck instance: 2.11.3-1
Type of Job: multibranch pipeline
We see a lot of warnings in the logs like: Apr 07, 2020 1:51:50 PM WARNING org.jenkinsci.plugins.structs.describable.DescribableModel uninstantiate2 Cannot create control version of class org.jenkinsci.plugins.rundeck.RundeckNotifier using {includeRundeckLogs=true, jobId=xxx, options= pipelineURL=https://... idTicket=999 estadoDespliegue="" rundeckURL="" , rundeckInstance=XXX, shouldFailTheBuild=true, shouldWaitForRundeckJob=true, tags=[], tailLog=false} java.lang.ClassCastException: org.jenkinsci.plugins.rundeck.RundeckNotifier.tags expects class java.lang.String but received class java.util.ArrayList Apr 07, 2020 1:51:50 PM WARNING org.jenkinsci.plugins.structs.describable.DescribableModel uninstantiate2 Cannot create control version of class org.jenkinsci.plugins.workflow.steps.CoreStep using {delegate=$RundeckNotifier(includeRundeckLogs=true,jobId=xxx, options= pipelineURL=https://... idTicketOTRS=999 estadoDespliegue="" rundeckURL="" ,rundeckInstance=XXX,shouldFailTheBuild=true,shouldWaitForRundeckJob=true,tags=[],tailLog=false)} java.lang.ClassCastException: org.jenkinsci.plugins.rundeck.RundeckNotifier.tags expects class java.lang.String but received class java.util.ArrayList
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-57206) Support draft pull requests from GitHub
Title: Message Title Thomas Wunderlich commented on JENKINS-57206 Re: Support draft pull requests from GitHub I'll note that draft PRs are currently building for me, so this may have been fixed and can likely be closed. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198963.1556379411000.9757.1586796180284%40Atlassian.JIRA.
[JIRA] (JENKINS-60424) logstash-plugin does not work with ElasticSearch 7
Title: Message Title Markus Winter commented on JENKINS-60424 Re: logstash-plugin does not work with ElasticSearch 7 I don't see a problem with ES7. Just tried it out locally using http://localhost:9200/jenkins/_doc Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203496.1575996102000.9755.1586795580257%40Atlassian.JIRA.
[JIRA] (JENKINS-61134) An UI relocation of Select All button for plugin update
Title: Message Title Allan C updated an issue Jenkins / JENKINS-61134 An UI relocation of Select All button for plugin update Change By: Allan C Summary: Unable to select all plugins An UI relocation of Select All button for plugin update Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204656.1582055073000.9750.1586795280195%40Atlassian.JIRA.
[JIRA] (JENKINS-61885) setting the system property hudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO to true is no use to disable csrf
Title: Message Title zhao ying created an issue Jenkins / JENKINS-61885 setting the system property hudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO to true is no use to disable csrf Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2020-04-13 16:26 Environment: centos 7.x jenkins 2.230 Priority: Critical Reporter: zhao ying http request show ``` Error 403 No valid crumb was included in the request ``` and following https://jenkins.io/security/advisory/2020-03-25/#SECURITY-1774 to disable this security fix by setting the system property hudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO to true. but still show Error 403 No valid crumb was included in the request Add Comment
[JIRA] (JENKINS-61884) JENKINS-9876
Title: Message Title Eashwar Alluri created an issue Jenkins / JENKINS-61884 JENKINS-9876 Issue Type: New Feature Assignee: Bruno P. Kinoshita Components: active-choices-plugin Created: 2020-04-13 16:25 Environment: DEV Priority: Minor Reporter: Eashwar Alluri Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61883) Can't access JSONObject entries
Title: Message Title
Roman Donchenko created an issue
Jenkins / JENKINS-61883
Can't access JSONObject entries
Issue Type:
Bug
Assignee:
Unassigned
Components:
script-security-plugin
Created:
2020-04-13 16:19
Environment:
Jenkins 2.190.1 Script Security plugin 1.71
Priority:
Minor
Reporter:
Roman Donchenko
Try executing this pipeline:
def o = readJSON text: '{"foo": "bar"}'
for (entry in o) {
echo entry.class.toString()
echo "$entry.key -> $entry.value"
}
The output is:
class org.apache.commons.collections.map.ListOrderedMap$ListOrderedMapEntry
Scripts not permitted to use method org.apache.commons.collections.KeyValue getKey. Administrators can decide whether to approve or reject this signature.
The reason for that is that readJSON returns a net.sf.json.JSONObject, whose entry class is org.apache.commons.collections.map.ListOrderedMap.ListOrderedMapEntry, which implements org.apache.commons.collections.KeyValue, whose members are not whitelisted. It would be nice if you could do at least one of these: 1. Whitelist org.apache.commons.collections.KeyValue getKey and getValue. 2. Make it so that the existing whitelist entries for java.util.Map.Entry getKey and
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title Basil Crow commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Hi John, can you please open a new issue with as much information as possible, ideally including the steps to reproduce the issue from scratch. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.9744.1586791500126%40Atlassian.JIRA.
[JIRA] (JENKINS-61882) JCasC GitOps support
Title: Message Title Anders Hammar updated an issue Jenkins / JENKINS-61882 JCasC GitOps support Change By: Anders Hammar Use case:We would like to handle our Jenkins' configuration through GitOps. The idea is that the config file(s) are stored in a git repo and JCasC reloads these when updated , without downtime . This could be handled by polling the repo or possible via webhook.It would be great if this would be supported by the plugin. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205752.1586791192000.9742.1586791440224%40Atlassian.JIRA.
[JIRA] (JENKINS-61882) JCasC GitOps support
Title: Message Title Anders Hammar created an issue Jenkins / JENKINS-61882 JCasC GitOps support Issue Type: New Feature Assignee: Ewelina Wilkosz Components: configuration-as-code-plugin Created: 2020-04-13 15:19 Environment: n/a Priority: Minor Reporter: Anders Hammar Use case: We would like to handle our Jenkins' configuration through GitOps. The idea is that the config file(s) are stored in a git repo and JCasC reloads these when updated. This could be handled by polling the repo or possible via webhook. It would be great if this would be supported by the plugin. Add Comment
[JIRA] (JENKINS-61843) Timestamp missing for trailing lines in view as plain text mode.
Title: Message Title John Rocha commented on JENKINS-61843 Re: Timestamp missing for trailing lines in view as plain text mode. Good Morning Basil Crow. I noticed that I am also having this problem on Linux systems even with your patch applied. How do you want me to proceed? Open a new JIRA or update this one? If updating, what information do you need? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205703.1586369761000.9738.1586790840121%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title
Ramon Leon edited a comment on JENKINS-61820
Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
What I expect is that *antisamy-markup-formatter.hpi* (2.0) has the jar * owasp-java-html-sanitizer.jar* with MANIFEST.MF:{code:java}Manifest-Version: 1.0Created-By: 1.6.0_26 (Apple Inc.){code}instead of * owasp-java-html-sanitizer-20191001.1.jar * with MANIFEST.MF:{code:java}Manifest-Version: 1.0Bnd-LastModified: 1570026235032Build-Jdk: 10.0.1Built-By: msamuelBundle-Description: Takes third-party HTML and produces HTML that is s afe to embed inyour web application.Fast and easy to configur e.Bundle-DocURL: https://owasp.orgBundle-License: http://www.apache.org/licenses/LICENSE-2.0.txtBundle-ManifestVersion: 2Bundle-Name: OWASP Java HTML SanitizerBundle-SymbolicName: com.googlecode.owasp-java-html-sanitizerBundle-Vendor: OWASPBundle-Version: 20191001.1.0Created-By: Apache Maven Bundle PluginExport-Package: org.owasp.html;uses:="com.google.common.base,com.googl e.common.collect,javax.annotation";version="20191001.1.0",org.owasp.h tml.examples;uses:="com.google.common.base,org.owasp.html";version="2 0191001.1.0"Import-Package: com.google.common.base;version="[27.1,28)",com.google. common.collect;version="[27.1,28)",com.google.common.io;version="[27. 1,28)",javax.annotation;version="[3.0,4)",org.owasp.html,org.owasp.ht ml.examplesRequire-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.6))"Tool: Bnd-3.5.0.201709291849{code}But better to check all plugins with an owasp library inside, as Oleg said.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy What I expect is that antisamy-markup-formatter.hpi (2.0) has the jar * owasp-java-html-sanitizer.jar* with MANIFEST.MF: Manifest-Version: 1.0 Created-By: 1.6.0_26 (Apple Inc.) instead of owasp-java-html-sanitizer-20191001.1.jar with MANIFEST.MF: Manifest-Version: 1.0 Bnd-LastModified: 1570026235032 Build-Jdk: 10.0.1 Built-By: msamuel Bundle-Description: Takes third-party HTML and produces HTML that is s afe to embed inyour web application.Fast and easy to configur e. Bundle-DocURL: https://owasp.org Bundle-License: http://www.apache.org/licenses/LICENSE-2.0.txt Bundle-ManifestVersion: 2 Bundle-Name: OWASP Java HTML Sanitizer Bundle-SymbolicName: com.googlecode.owasp-java-html-sanitizer Bundle-Vendor: OWASP Bundle-Version: 20191001.1.0 Created-By: Apache Maven Bundle Plugin Export-Package: org.owasp.html;uses:="com.google.common.base,com.googl e.common.collect,javax.annotation";version="20191001.1.0",org.owasp.h tml.examples;uses:="com.google.common.base,org.owasp.html";version="2 0191001.1.0" Import-Package: com.google.common.base;version="[27.1,28)",com.google. common.collect;version="[27.1,28)",com.google.common.io;version="[27. 1,28)",javax.annotation;version="[3.0,4)",org.owasp.html,org.owasp.ht ml.examples Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.6))" Tool: Bnd-3.5.0.201709291849 But better to check all plugins with an owasp library inside, as Oleg said. Add Comment
[JIRA] (JENKINS-61881) Jenkins build failing due to failure of creation of docker container(ppwershell failure)
Title: Message Title Manoj R updated an issue Jenkins / JENKINS-61881 Jenkins build failing due to failure of creation of docker container(ppwershell failure) Change By: Manoj R powershell.exe : docker-compose : Cannot create container for service xxx: mkdir At C:\Jenkins\workspace\bootROM_pipeline\feature\C2000BROM-251-initial-design-rev3@tmp\durable-0d0b5812\powershellWrapper.ps1:3 char:1 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ... + ~ + CategoryInfo : NotSpecified: (docker-compose ...bootrom: mkdir :String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError C:\windows\system32\config\systemprofile: Cannot create a file when that file already exists. At C:\Jenkins\workspace\bootROM_pipeline\feature\C2000BROM-251-initial-design-rev3@tmp\durable-0d0b5812\powershellScrip t.ps1:1 char:1 + docker-compose run --rm bash -l -c "cd /project; ./ ... + ~ + CategoryInfo : NotSpecified: (Cannot create c...already exists.:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError (Note this was working fine) All the previous builds when I rebuild I am seeing this error Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61794) how to pass multiple credentials to ansible tower from jenkins job
Title: Message Title Lakshmi Prasanna Damineni commented on JENKINS-61794 Re: how to pass multiple credentials to ansible tower from jenkins job Hi John, Thanks for your reply, it is working fine please ignore this issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205637.1585897505000.9721.1586787660280%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Oleg Nenashev commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy The easiest way to find root cause is to go through all plugin archives using ZIP tool and to find all plugins including the owasp-java-html-sanitizer JAR. Once it is done, all plugins can be manually checked for versions of the library. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9718.1586787540222%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon edited a comment on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Sorry [~based3] I don't see any further path to investigate this issue. The only reason I can think about is some manipulation of hpi plugin files changing the owasp-java-html-sanitizer jar; adding the old one, without the Sanitizer.TABLES field, instead of the new one with this field. Please feel free to reopen if you find reproduction steps we can follow. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9711.1586786820476%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon updated JENKINS-61820 Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Ramon Leon Status: In Progress Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9715.1586786820530%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Sorry Basile Chandesris I don't see any further path to investigate this issue. The only reason I can think about is some manipulation of hpi plugin files changing the owasp-java-html-sanitizer jar; adding the old one, without the Sanitizer.TABLES field, instead of the new one with this field. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9705.1586786760284%40Atlassian.JIRA.
[JIRA] (JENKINS-61794) how to pass multiple credentials to ansible tower from jenkins job
Title: Message Title John Westcott commented on JENKINS-61794 Re: how to pass multiple credentials to ansible tower from jenkins job The plugin should already support adding multiple credentials back to tower. Try using a comma separated list of credential IDs or names. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205637.1585897505000.9703.1586786580191%40Atlassian.JIRA.
[JIRA] (JENKINS-61881) Jenkins build failing due to failure of creation of docker container(ppwershell failure)
Title: Message Title Manoj R created an issue Jenkins / JENKINS-61881 Jenkins build failing due to failure of creation of docker container(ppwershell failure) Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2020-04-13 13:23 Environment: Windows docker + PowerShell Priority: Major Reporter: Manoj R powershell.exe : docker-compose : Cannot create container for service xxx: mkdir At C:\Jenkins\workspace\bootROM_pipeline\feature\C2000BROM-251-initial-design-rev3@tmp\durable-0d0b5812\powershellWrapper.ps1:3 char:1 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -Comm ... + ~ + CategoryInfo : NotSpecified: (docker-compose ...bootrom: mkdir :String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError C:\windows\system32\config\systemprofile: Cannot create a file when that file already exists. At C:\Jenkins\workspace\bootROM_pipeline\feature\C2000BROM-251-initial-design-rev3@tmp\durable-0d0b5812\powershellScrip t.ps1:1 char:1 + docker-compose run --rm bash -l -c "cd /project; ./ ... + ~ + CategoryInfo : NotSpecified: (Cannot create c...already exists.:String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError (Note this was working fine)
[JIRA] (JENKINS-61803) Configure Global Security should accept both entries: default and per project
Title: Message Title Ron Gebauer commented on JENKINS-61803 Re: Configure Global Security should accept both entries: default and per project Maxime Hochet the order is also important. You need to set the per project base before default … because otherwise always default is used. I also do not understand why I can prioritize 2 options … but it seems this is is the case. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205647.1585920015000.9700.1586783640212%40Atlassian.JIRA.
[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-40517 Allow changing delimiter in log output Change By: Pierre Beitz Labels: 3.4-fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177193.1481911536000.9692.1586783160971%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz updated JENKINS-11048 Jenkins / JENKINS-11048 Broken link in help text of Audit Trail plugin configuration Change By: Pierre Beitz Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141258.1316451512000.9690.1586783160881%40Atlassian.JIRA.
[JIRA] (JENKINS-27975) Audit trail should log query string as well
Title: Message Title Pierre Beitz updated JENKINS-27975 Jenkins / JENKINS-27975 Audit trail should log query string as well Change By: Pierre Beitz Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162172.1429183811000.9698.1586783220279%40Atlassian.JIRA.
[JIRA] (JENKINS-27975) Audit trail should log query string as well
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-27975 Audit trail should log query string as well Change By: Pierre Beitz Labels: 3.4-fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162172.1429183811000.9696.1586783220252%40Atlassian.JIRA.
[JIRA] (JENKINS-11048) Broken link in help text of Audit Trail plugin configuration
Title: Message Title Pierre Beitz updated an issue Jenkins / JENKINS-11048 Broken link in help text of Audit Trail plugin configuration Change By: Pierre Beitz Labels: 3.4-fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.141258.1316451512000.9687.1586783160743%40Atlassian.JIRA.
[JIRA] (JENKINS-40517) Allow changing delimiter in log output
Title: Message Title Pierre Beitz updated JENKINS-40517 Jenkins / JENKINS-40517 Allow changing delimiter in log output Change By: Pierre Beitz Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.177193.1481911536000.9694.1586783161022%40Atlassian.JIRA.
[JIRA] (JENKINS-61788) jclouds single-use slave never cleaned up
Title: Message Title Major Hayden commented on JENKINS-61788 Re: jclouds single-use slave never cleaned up Thanks for the quick fix. I'll try to get a look at this as soon as I can. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205628.1585853221000.9684.1586782740391%40Atlassian.JIRA.
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title
Basile Chandesris edited a comment on JENKINS-59198
Re: NullPointerException in hudson.util.Secret$1.convert
I faced the same issue on a 2.222.1 server, Redhat 7, Java 8 242,with Splunk plugin - 1.9.2 - in the stacktraceand I have also email-ext-plugin - 2.69 - on the server,while testing the Plugins proxy setup(In the context of JENKINS-61820, after the manual failed update). As I found: jenkins.security.SuspiciousRequestFilte, maybe,a side effect of SECURITY-1774 / CVE-2020-2160 fix:[https://jenkins.io/security/advisory/2020-03-25/]will check disabling:_As an additional safeguard, semicolon ({{;}}) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property {{jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath}} to {{true}}_java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris edited a comment on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Sorry, here the list.We have two private plugins: jobpersistqueue, orchestrate (I will try to take time to update them).The plugins installed by the unarchive as new /plugins folder on 2.222.1:ace-editor 1.1 trueansicolor 0.6.3 trueant 1.8 falseantisamy-markup-formatter 2.0 trueapache-httpcomponents-client-4-api 4.5.10-2.0 trueauthentication-tokens 1.3 trueauthorize-project 1.3.0 truebasic-branch-build-strategies 1.3.2 trueblueocean 1.22.0 trueblueocean-autofavorite 1.2.4 trueblueocean-bitbucket-pipeline 1.22.0 trueblueocean-commons 1.22.0 trueblueocean-config 1.22.0 trueblueocean-core-js 1.22.0 trueblueocean-dashboard 1.22.0 trueblueocean-display-url 2.3.1 trueblueocean-events 1.22.0 trueblueocean-git-pipeline 1.22.0 trueblueocean-github-pipeline 1.22.0 trueblueocean-i18n 1.22.0 trueblueocean-jira 1.22.0 trueblueocean-jwt 1.22.0 trueblueocean-personalization 1.22.0 trueblueocean-pipeline-api-impl 1.22.0 trueblueocean-pipeline-editor 1.22.0 trueblueocean-pipeline-scm-api 1.22.0 trueblueocean-rest 1.22.0 trueblueocean-rest-impl 1.22.0 trueblueocean-web 1.22.0 truebouncycastle-api 2.18 truebranch-api 2.5.5 truebuild-pipeline-plugin 1.5.8 truebuild-timeout 1.19.1 truecloudbees-bitbucket-branch-source 2.7.0 truecloudbees-folder 6.12 truecommand-launcher 1.4 falsecompact-columns 1.10 falseconditional-buildstep 1.3.6 truecredentials 2.3.5 truecredentials-binding 1.21 truedisplay-url-api 2.3.2 truedocker-commons 1.16 truedocker-workflow 1.23 truedurable-task 1.34 trueemail-ext 2.69 trueexternal-monitor-job 1.7 falsefavorite 2.3.2 truegit 4.2.2 truegit-client 3.2.1 truegit-server 1.9 truegithub 1.29.5 truegithub-api 1.110 truegithub-branch-source 2.6.0 trueglobal-build-stats 1.5 truegroovy 2.2 truehandlebars 1.1.1 truehandy-uri-templates-2-api 2.1.8-1.0 truehtmlpublisher 1.22 truejackson2-api 2.10.3 truejavadoc 1.5 truejdk-tool 1.4 falsejenkins-design-language 1.22.0 truejira 3.0.15 truejob-dsl 1.77 truejobpersistqueue 1.0-SNAPSHOT true - PRIVATEjquery 1.12.4-1 truejquery-detached 1.2.1 truejquery-ui 1.0.2 truejsch 0.1.55.2 truejunit 1.28 trueldap 1.22 truelockable-resources 2.7 truemailer 1.31 truemask-passwords 2.13 truematrix-auth 2.5 truematrix-project 1.14 truemaven-plugin 3.5 truemercurial 2.9 truemomentjs 1.1.1 trueorchestrate 1.1 true - PRIVATEpam-auth 1.5.1 falseparameterized-trigger 2.36 truepipeline-build-step 2.12 truepipeline-graph-analysis 1.10 truepipeline-input-step 2.11 truepipeline-milestone-step 1.3.1 truepipeline-model-api 1.6.0 truepipeline-model-declarative-agent 1.1.1 truepipeline-model-definition 1.6.0 truepipeline-model-extensions 1.6.0 truepipeline-rest-api 2.13 truepipeline-stage-step 2.3 truepipeline-stage-tags-metadata 1.6.0 truepipeline-stage-view 2.13 truepipeline-utility-steps 2.5.0 trueplain-credentials 1.7 truepreSCMbuildstep 0.3 truepubsub-light 1.13 truerebuild 1.31 trueresource-disposer 0.14 truerole-strategy 2.16 truerun-condition 1.3 truescm-api 2.6.3 truescript-security 1.71 truesplunk-devops 1.9.2 truesse-gateway 1.23 truessh-agent 1.19 truessh-credentials 1.18.1 truessh-slaves 1.31.1 truestructs 1.20 truetimestamper 1.11.2 truetoken-macro 2.12 truetrilead-api 1.0.6 trueuno-choice 2.2.2 truevariant 1.3 truewindows-slaves 1.0 falseworkflow-aggregator 2.6 trueworkflow-api 2.40 trueworkflow-basic-steps 2.19 trueworkflow-cps 2.80 trueworkflow-cps-global-lib 2.16 trueworkflow-durable-task-step 2.35 trueworkflow-job 2.38 trueworkflow-multibranch 2.21 trueworkflow-scm-step 2.10 trueworkflow-step-api 2.22
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Sorry, here the list. We have two private plugins: jobpersistqueue, orchestrate (I will try to take time to update them). The plugins installed by the unarchive as new /plugins folder on 2.222.1: ace-editor 1.1 true ansicolor 0.6.3 true ant 1.8 false antisamy-markup-formatter 2.0 true apache-httpcomponents-client-4-api 4.5.10-2.0 true authentication-tokens 1.3 true authorize-project 1.3.0 true basic-branch-build-strategies 1.3.2 true blueocean 1.22.0 true blueocean-autofavorite 1.2.4 true blueocean-bitbucket-pipeline 1.22.0 true blueocean-commons 1.22.0 true blueocean-config 1.22.0 true blueocean-core-js 1.22.0 true blueocean-dashboard 1.22.0 true blueocean-display-url 2.3.1 true blueocean-events 1.22.0 true blueocean-git-pipeline 1.22.0 true blueocean-github-pipeline 1.22.0 true blueocean-i18n 1.22.0 true blueocean-jira 1.22.0 true blueocean-jwt 1.22.0 true blueocean-personalization 1.22.0 true blueocean-pipeline-api-impl 1.22.0 true blueocean-pipeline-editor 1.22.0 true blueocean-pipeline-scm-api 1.22.0 true blueocean-rest 1.22.0 true blueocean-rest-impl 1.22.0 true blueocean-web 1.22.0 true bouncycastle-api 2.18 true branch-api 2.5.5 true build-pipeline-plugin 1.5.8 true build-timeout 1.19.1 true cloudbees-bitbucket-branch-source 2.7.0 true cloudbees-folder 6.12 true command-launcher 1.4 false compact-columns 1.10 false conditional-buildstep 1.3.6 true credentials 2.3.5 true credentials-binding 1.21 true display-url-api 2.3.2 true docker-commons 1.16 true docker-workflow 1.23 true durable-task 1.34 true email-ext 2.69 true external-monitor-job 1.7 false favorite 2.3.2 true git 4.2.2 true git-client 3.2.1 true git-server 1.9 true github 1.29.5 true github-api 1.110 true github-branch-source 2.6.0 true global-build-stats 1.5 true groovy 2.2 true handlebars 1.1.1 true handy-uri-templates-2-api 2.1.8-1.0 true htmlpublisher 1.22 true jackson2-api 2.10.3 true javadoc 1.5 true jdk-tool 1.4 false jenkins-design-language 1.22.0 true jira 3.0.15 true job-dsl 1.77 true jobpersistqueue 1.0-SNAPSHOT true - PRIVATE jquery 1.12.4-1 true jquery-detached 1.2.1 true jquery-ui 1.0.2 true jsch 0.1.55.2 true junit 1.28 true ldap 1.22 true lockable-resources 2.7 true mailer 1.31 true mask-passwords 2.13 true matrix-auth 2.5 true matrix-project 1.14 true maven-plugin 3.5 true mercurial 2.9 true momentjs 1.1.1 true orchestrate 1.1 true - PRIVATE pam-auth 1.5.1 false parameterized-trigger 2.36 true pipeline-build-step 2.12 true pipeline-graph-analysis 1.10 true pipeline-input-step 2.11 true pipeline-milestone-step 1.3.1 true pipeline-model-api 1.6.0 true pipeline-model-declarative-agent 1.1.1 true pipeline-model-definition 1.6.0 true pipeline-model-extensions 1.6.0 true pipeline-rest-api 2.13 true pipeline-stage-step 2.3 true pipeline-stage-tags-metadata 1.6.0 true pipeline-stage-view 2.13 true pipeline-utility-steps 2.5.0 true plain-credentials 1.7 true preSCMbuildstep 0.3 true pubsub-light 1.13 true rebuild 1.31 true resource-disposer 0.14 true role-strategy 2.16 true run-condition 1.3 true scm-api 2.6.3 true script-security 1.71 true splunk-devops 1.9.2 true sse-gateway 1.23 true ssh-agent 1.19 true ssh-credentials 1.18.1 true ssh-slaves 1.31.1 true structs 1.20 true timestamper 1.11.2 true token-macro 2.12 true trilead-api 1.0.6 true uno-choice 2.2.2 true variant 1.3 true windows-slaves 1.0 false workflow-aggregator 2.6 true workflow-api 2.40 true workflow-basic-steps 2.19 true workflow-cps 2.80 true workflow-cps-global-lib 2.16 true workflow-durable-task-step
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title
Basile Chandesris edited a comment on JENKINS-59198
Re: NullPointerException in hudson.util.Secret$1.convert
I faced the same issue on a 2.222.1 server, Redhat 7, Java 8 242,with Splunk plugin in the stacktrace and I have also email-ext-plugin on the server,while testing the Plugins proxy setup(In the context of ENKINS JENKINS -61820, after the manual failed update). As I found: jenkins.security.SuspiciousRequestFilte, maybe,a side effect of SECURITY-1774 / CVE-2020-2160 fix:[https://jenkins.io/security/advisory/2020-03-25/]will check disabling:_As an additional safeguard, semicolon ({{;}}) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property {{jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath}} to {{true}}_java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title
Basile Chandesris edited a comment on JENKINS-59198
Re: NullPointerException in hudson.util.Secret$1.convert
I faced the same issue on a 2.222.1 server, Redhat 7, Java 8 242,with Splunk plugin in the stacktrace and I have also email-ext-plugin on the server ,while testing the Plugins proxy setup (In the context of ENKINS-61820, after the manual failed update) . As I found: jenkins.security.SuspiciousRequestFilte, maybe,a side effect of SECURITY-1774 / CVE-2020-2160 fix:[https://jenkins.io/security/advisory/2020-03-25/]will check disabling:_As an additional safeguard, semicolon ({{;}}) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property {{jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath}} to {{true}}_java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title
Basile Chandesris edited a comment on JENKINS-59198
Re: NullPointerException in hudson.util.Secret$1.convert
I faced the same issue on a 2.222.1 server , Redhat 7, Java 8 242, with Splunk plugin in the stacktrace,while testing the Plugins proxy setup. Maybe As I found: jenkins.security.SuspiciousRequestFilte , maybe, a side effect of SECURITY-1774 / CVE-2020-2160 fix:[https://jenkins.io/security/advisory/2020-03-25/]will check disabling:_As an additional safeguard, semicolon ({{;}}) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property {{jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath}} to {{true}}_java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title
Basile Chandesris edited a comment on JENKINS-59198
Re: NullPointerException in hudson.util.Secret$1.convert
I faced the same issue on a 2.222.1 server with Splunk plugin in the stacktrace : , maybe while testing the Plugins proxy setup.Maybe, a side effect of SECURITY-1774 / CVE-2020-2160 fix:[https://jenkins.io/security/advisory/2020-03-25/]will check with disabling : As _As an additional safeguard, semicolon ({{;}}) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property {{jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath}} to {{true}} _ java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at
[JIRA] (JENKINS-61880) `GlobalCredentialsConfiguration` JCasC compatibility
Title: Message Title Antonio Muñiz started work on JENKINS-61880 Change By: Antonio Muñiz Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205750.1586780064000.9642.1586780220084%40Atlassian.JIRA.
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-59198 NullPointerException in hudson.util.Secret$1.convert Change By: Basile Chandesris Labels: 2.222.1 Splunk Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201641.1567478279000.9637.1586780160775%40Atlassian.JIRA.
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-59198 NullPointerException in hudson.util.Secret$1.convert Change By: Basile Chandesris Component/s: splunk-devops-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201641.1567478279000.9631.1586780160472%40Atlassian.JIRA.
[JIRA] (JENKINS-61880) `GlobalCredentialsConfiguration` JCasC compatibility
Title: Message Title Antonio Muñiz assigned an issue to Antonio Muñiz Jenkins / JENKINS-61880 `GlobalCredentialsConfiguration` JCasC compatibility Change By: Antonio Muñiz Assignee: Antonio Muñiz Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205750.1586780064000.9641.1586780160893%40Atlassian.JIRA.
[JIRA] (JENKINS-61880) `GlobalCredentialsConfiguration` JCasC compatibility
Title: Message Title Antonio Muñiz created an issue Jenkins / JENKINS-61880 `GlobalCredentialsConfiguration` JCasC compatibility Issue Type: Bug Assignee: Unassigned Components: credentials-plugin Created: 2020-04-13 12:14 Priority: Major Reporter: Antonio Muñiz Extensions of `GlobalCredentialsConfiguration` are JCasC compatible out of the box, however the yaml for them is quite ugly. For example: ? '' : cyberArkGlobalConfiguration: The empty string node comes from the `GlobalCredentialsConfiguration` category, which does not have a proper Symbol. Add Comment
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title
Basile Chandesris edited a comment on JENKINS-59198
Re: NullPointerException in hudson.util.Secret$1.convert
I faced the same issue on a 2.222.1 server with Splunk plugin in the stacktrace: maybe a side effect of SECURITY-1774 / CVE-2020-2160 fix: [https://jenkins.io/security/advisory/2020-03-25/]will check with:As an additional safeguard, semicolon ({{;}}) characters in the path part of a URL are now banned by default. Administrators can disable this protection by setting the system property {{jenkins.security.SuspiciousRequestFilter.allowSemicolonsInPath}} to {{true}} java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at
[JIRA] (JENKINS-59198) NullPointerException in hudson.util.Secret$1.convert
Title: Message Title Basile Chandesris reopened an issue I faced the same issue on a 2.222.1 server with Splunk plugin in the stacktrace: java.lang.NullPointerException at hudson.util.Secret$1.convert(Secret.java:306) at hudson.util.Secret$1.convert(Secret.java:304) at org.kohsuke.stapler.AnnotationHandler.convert(AnnotationHandler.java:66) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:74) at org.kohsuke.stapler.QueryParameter$HandlerImpl.parse(QueryParameter.java:62) at org.kohsuke.stapler.AnnotationHandler.handle(AnnotationHandler.java:91) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:204) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:755) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1617) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at com.splunk.splunkjenkins.WebPostAccessLogger.doFilter(WebPostAccessLogger.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.security.ResourceDomainFilter.doFilter(ResourceDomainFilter.java:76) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at jenkins.telemetry.impl.UserLanguages$AcceptLanguageFilter.doFilter(UserLanguages.java:128) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:153) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1604) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:118) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at
[JIRA] (JENKINS-60712) Copied managed config file should be removed when block ends
Title: Message Title Nikolas Falco updated JENKINS-60712 Jenkins / JENKINS-60712 Copied managed config file should be removed when block ends Change By: Nikolas Falco Status: Fixed but Unreleased Closed Released As: 1.3.5 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203960.157858259.9615.1586778780285%40Atlassian.JIRA.
[JIRA] (JENKINS-61879) There were errors checking the update sites: NullPointerException: null issue when we open Manage Plugins UI
Title: Message Title Filipe Roque updated an issue Jenkins / JENKINS-61879 There were errors checking the update sites: NullPointerException: null issue when we open Manage Plugins UI Change By: Filipe Roque Component/s: core Component/s: plugin-usage-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205747.1586769731000.9612.1586774580172%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy I've just done the steps I commented, no errors found. Jenkins 2.204.4 with Timestamper 1.11.1 and OWASP Markup Formatter 1.8: A job with a table in its description: The table and html escaped: Updated to Jenkins 2.222.1: Updated the plugin versions: Description shown as expected: And no errors on console. Sorry Basile Chandesris maybe I missed some step or it's something related with your environment, most likely changed jar (owasp dependency) in an unexpected way, but it's weird someone did so. If you could give us some steps to reproduce the problem it would help to find out the issue. In other case I'm sorry we will close this ticket as cannot reproduce. To be clear, I don't doubt there could be a potential issue here, it's just that without a way to reproduce it or any extra valuable information, we cannot do too much for now. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9606.1586773320668%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon started work on JENKINS-61820 Change By: Ramon Leon Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9608.1586773320736%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Ramon Leon Attachment: Screenshot from 2020-04-13 12-00-47.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9599.1586772300422%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Ramon Leon Attachment: Screenshot from 2020-04-13 12-00-18.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9597.1586772300381%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Ramon Leon Attachment: Screenshot from 2020-04-13 11-59-15.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9591.1586772240661%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Ramon Leon Attachment: Screenshot from 2020-04-13 11-58-52.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9589.1586772240429%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Ramon Leon Attachment: Screenshot from 2020-04-13 11-44-58.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9581.1586772180514%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Ramon Leon Attachment: Screenshot from 2020-04-13 11-47-55.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205670.1586158442000.9583.1586772180563%40Atlassian.JIRA.
[JIRA] (JENKINS-58557) Separate @jenkinsci-specific archetype
Title: Message Title Tim Jacomb updated JENKINS-58557 Jenkins / JENKINS-58557 Separate @jenkinsci-specific archetype Change By: Tim Jacomb Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200707.1563467181000.9575.1586771700325%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Change By: Pierre Beitz Assignee: prakash raj Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205746.1586766048000.9573.1586771460123%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title prakash raj assigned an issue to prakash raj Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Change By: prakash raj Assignee: Pierre Beitz prakash raj Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205746.1586766048000.9571.1586771340138%40Atlassian.JIRA.
[JIRA] (JENKINS-58557) Separate @jenkinsci-specific archetype
Title: Message Title Tim Jacomb assigned an issue to Tim Jacomb Jenkins / JENKINS-58557 Separate @jenkinsci-specific archetype Change By: Tim Jacomb Assignee: Tim Jacomb Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200707.1563467181000.9565.1586771280542%40Atlassian.JIRA.
[JIRA] (JENKINS-58557) Separate @jenkinsci-specific archetype
Title: Message Title Tim Jacomb started work on JENKINS-58557 Change By: Tim Jacomb Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200707.1563467181000.9567.1586771280572%40Atlassian.JIRA.
[JIRA] (JENKINS-51254) Incrementalify plugin archetypes
Title: Message Title Tim Jacomb closed an issue as Duplicate Jenkins / JENKINS-51254 Incrementalify plugin archetypes Change By: Tim Jacomb Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190579.1525984033000.9561.1586770800245%40Atlassian.JIRA.
[JIRA] (JENKINS-58040) listing of available archetypes not working
Title: Message Title Tim Jacomb closed an issue as Cannot Reproduce Jenkins / JENKINS-58040 listing of available archetypes not working Change By: Tim Jacomb Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200060.1560760521000.9559.1586770743063%40Atlassian.JIRA.
[JIRA] (JENKINS-60290) Maven Archetypes "Hello World Plugin" Generates Broken Code
Title: Message Title Tim Jacomb commented on JENKINS-60290 Re: Maven Archetypes "Hello World Plugin" Generates Broken Code Kylie Auld you need to run mvn install once, that you generate the class, it's used for localisation, https://jenkins.io/doc/developer/internationalization/i18n-source-code/ I've just generated this via archetype and it compiled fine for me Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203282.1574791855000.9548.1586770742909%40Atlassian.JIRA.
[JIRA] (JENKINS-60290) Maven Archetypes "Hello World Plugin" Generates Broken Code
Title: Message Title Tim Jacomb updated JENKINS-60290 Jenkins / JENKINS-60290 Maven Archetypes "Hello World Plugin" Generates Broken Code Change By: Tim Jacomb Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203282.1574791855000.9554.1586770742985%40Atlassian.JIRA.
[JIRA] (JENKINS-60290) Maven Archetypes "Hello World Plugin" Generates Broken Code
Title: Message Title Tim Jacomb updated JENKINS-60290 Jenkins / JENKINS-60290 Maven Archetypes "Hello World Plugin" Generates Broken Code Change By: Tim Jacomb Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203282.1574791855000.9552.1586770742958%40Atlassian.JIRA.
[JIRA] (JENKINS-60290) Maven Archetypes "Hello World Plugin" Generates Broken Code
Title: Message Title Tim Jacomb closed an issue as Not A Defect Jenkins / JENKINS-60290 Maven Archetypes "Hello World Plugin" Generates Broken Code Change By: Tim Jacomb Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203282.1574791855000.9556.1586770743020%40Atlassian.JIRA.
[JIRA] (JENKINS-60290) Maven Archetypes "Hello World Plugin" Generates Broken Code
Title: Message Title Tim Jacomb edited a comment on JENKINS-60290 Re: Maven Archetypes "Hello World Plugin" Generates Broken Code [~kylie_a] you need to run mvn install once, that you will generate the class, it's used for localisation, https://jenkins.io/doc/developer/internationalization/i18n-source-code/I've just generated this via archetype and it compiled fine for me Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203282.1574791855000.9550.1586770742934%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz commented on JENKINS-61878 Re: Improve the queue/cancelItem endpoint API documentation prakash raj not sure if you assigned to yourself by mistake, but I took back the task as there is already a PR fixing it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205746.1586766048000.9546.1586770560143%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title Pierre Beitz assigned an issue to Pierre Beitz Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Change By: Pierre Beitz Assignee: prakash raj Pierre Beitz Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205746.1586766048000.9544.1586770500141%40Atlassian.JIRA.
[JIRA] (JENKINS-61878) Improve the queue/cancelItem endpoint API documentation
Title: Message Title prakash raj assigned an issue to prakash raj Jenkins / JENKINS-61878 Improve the queue/cancelItem endpoint API documentation Change By: prakash raj Assignee: Pierre Beitz prakash raj Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205746.1586766048000.9542.1586770200184%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Ramon Leon commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Hi Basile Chandesris I cannot figure out a clear path to reproduce the problem. Please tell me the steps you did to go to this status. I will try to: start with a 2.204.4 Jenkins instance Install antisamy 1.8 and timestamper 1.11.1 Create some content there with tables (job descriptions) Upgrade to 2.222.1 Upgrade to antisamy 2.0 and timestamper 1.11.2 Both plugins use the owasp-java-html-sanitizer library to sanitize the output, but it shouldn't be a problem because each plugin has its own class loading mechanism. Please correct my steps with yours if it's not accurate, or even better, give us a reproduction steps to be able to debug the problem. Also I cannot see the list of plugins before and after, I just wanted the list of plugins you were using. I guess the ones I will use are fine. Thank you. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email
