[JIRA] (JENKINS-61704) jenkins pipeline job no permission to config bitbucket-server-integration plugin
Title: Message Title Martin Henschke commented on JENKINS-61704 Re: jenkins pipeline job no permission to config bitbucket-server-integration plugin Hi Roy, thanks for this report. Can you please share what plugin you are using for managing permissions, and what authorization strategy you have selected in your global security settings? Thanks, Martin 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.205529.1585279505000.7959.1586322540122%40Atlassian.JIRA.
[JIRA] (JENKINS-60972) Rename the root breadcrumb
Title: Message Title Sladyn Nunes assigned an issue to Sladyn Nunes Jenkins / JENKINS-60972 Rename the root breadcrumb Change By: Sladyn Nunes Assignee: Levi Williamson Sladyn Nunes 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.204437.1580894909000.7956.1586322420281%40Atlassian.JIRA.
[JIRA] (JENKINS-60972) Rename the root breadcrumb
Title: Message Title Levi Williamson assigned an issue to Levi Williamson Jenkins / JENKINS-60972 Rename the root breadcrumb Change By: Levi Williamson Assignee: Levi Williamson Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204437.1580894909000.7951.1586322180390%40Atlassian.JIRA.
[JIRA] (JENKINS-61607) Make number of context lines in FullTextFingerprint configurable
Title: Message Title Levi Williamson assigned an issue to Unassigned Jenkins / JENKINS-61607 Make number of context lines in FullTextFingerprint configurable Change By: Levi Williamson Assignee: Levi Williamson Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205308.1584741649000.7949.1586321880197%40Atlassian.JIRA.
[JIRA] (JENKINS-61607) Make number of context lines in FullTextFingerprint configurable
Title: Message Title Levi Williamson assigned an issue to Levi Williamson Jenkins / JENKINS-61607 Make number of context lines in FullTextFingerprint configurable Change By: Levi Williamson Assignee: Levi Williamson Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205308.1584741649000.7947.1586321461283%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Martin Henschke updated JENKINS-60274 Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Change By: Martin Henschke Status: In Review Closed Resolution: Fixed Released As: 1.1.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203264.1574715014000.7934.1586317980846%40Atlassian.JIRA.
[JIRA] (JENKINS-60274) Unable to use plugin with private Bitbucket repositories
Title: Message Title Martin Henschke updated JENKINS-60274 Jenkins / JENKINS-60274 Unable to use plugin with private Bitbucket repositories Change By: Martin Henschke Status: Closed Fixed but Unreleased 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.203264.1574715014000.7936.1586317980879%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jeff Thompson commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb The Remoting 4.2.1 release is out and available in repo.jenkins.io. The release notes are at https://github.com/jenkinsci/remoting/releases/tag/remoting-4.2.1 . I put together a PR to integrate that version into the 2.222.x LTS Jenkins branch at https://github.com/jenkinsci/jenkins/pull/4635 . 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.205063.1583801943000.7918.1586308200373%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title
Alex Gray commented on JENKINS-61779
Re: Regression: Job stuck in queue waiting forever after upgrade
I have the same issue. I'm on 2.222.1. It ONLY happened when I upgraded to 2.222.1 from 2.204.1 I have a label_expression on a matrix project set to "master_node". When I run it, it says "(pending—Waiting for next available executor on ‘master’)" Note that it says "master", not "master_node". I have no idea why it's looking for something called "master", not "master_node". I'm attaching a gif of what I see. Here are the logs that Daniel Beck requested too:
Apr 08, 2020 12:16:14 AM FINEST hudson.model.Queue
Queue.Snapshot{waitingList=[];blockedProjects=[hudson.model.Queue$BlockedItem:hudson.model.FreeStyleProject@502099a9[util-slave-manager]:152871];buildables=[hudson.model.Queue$BuildableItem:hudson.matrix.MatrixProject@598a8bc[util-check-for-container-spread]:152734, hudson.model.Queue$BuildableItem:hudson.matrix.MatrixProject@4fe1c89a[util-generate-datadog-monitors]:152745];pendings=[]} → Queue.Snapshot{waitingList=[];blockedProjects=[hudson.model.Queue$BlockedItem:hudson.model.FreeStyleProject@502099a9[util-slave-manager]:152871];buildables=[hudson.model.Queue$BuildableItem:hudson.matrix.MatrixProject@598a8bc[util-check-for-container-spread]:152734, hudson.model.Queue$BuildableItem:hudson.matrix.MatrixProject@4fe1c89a[util-generate-datadog-monitors]:152745];pendings=[]}; leftItems={152845=hudson.model.Queue$LeftItem:hudson.matrix.MatrixProject@33385024[util-check-for-low-ips]:152845, 152866=hudson.model.Queue$LeftItem:hudson.model.FreeStyleProject@2e88aabc[util-check-hung-ecs-tasks-prod-ca]:152866, 152865=hudson.model.Queue$LeftItem:hudson.model.FreeStyleProject@1c17e4db[util-check-hung-ecs-tasks-prod]:152865, 152819=hudson.model.Queue$LeftItem:hudson.model.FreeStyleProject@502099a9[util-slave-manager]:152819, 152868=hudson.model.Queue$LeftItem:ExecutorStepExecution.PlaceholderTask{runId=util-alert-jenkins-vs-jumpcloud-users#4201,label=,context=CpsStepContext[4:node]:Owner[util-alert-jenkins-vs-jumpcloud-users/4201:util-alert-jenkins-vs-jumpcloud-users #4201],cookie=f8461e2f-66d2-48fb-9acc-79bb1b98a0ad,auth=null}:152868, 152867=hudson.model.Queue$LeftItem:org.jenkinsci.plugins.workflow.job.WorkflowJob@13b79664[util-alert-jenkins-vs-jumpcloud-users]:152867, 152870=hudson.model.Queue$LeftItem:hudson.model.FreeStyleProject@188db571[util-check-hung-ecs-tasks-stage]:152870, 152872=hudson.model.Queue$LeftItem:hudson.model.FreeStyleProject@1ae51106[databases-without-termination-protection]:152872, 152869=hudson.model.Queue$LeftItem:hudson.model.FreeStyleProject@60957b04[util-check-asg-thrashing]:152869}
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title Alex Gray updated an issue Jenkins / JENKINS-61779 Regression: Job stuck in queue waiting forever after upgrade Change By: Alex Gray Attachment: master_node.gif 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.205618.158582599.7909.1586305560355%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jeff Thompson commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb I agree with Jesse. I don't see any risk to previously existing functionality for this change to better support WebSockets. I'm in the middle of preparing a 4.2.1 patch containing just the WebSockets fix over 4.2. That eliminates any concern over https://github.com/jenkinsci/remoting/pull/369 . 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.205063.1583801943000.7902.1586304660390%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Pierson Yieh edited a comment on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart We've also seen this behavior before though we're not sure how to reproduce the problem. We saw it when we'd hit our max AWS request limit and Jenkins started losing track of nodes and couldn't spin up new ones cause the orphaned nodes were still being counted towards the max instance count, but weren't showing up in the Jenkins UI.I'm able to "simulate" the "losing track of nodes" by running a groovy script on the Jenkins Master to manually remove the node for the Jenkins object. And we're looking into implementing a feature to automatically re-attach these orphaned nodes to Jenkins. Update: seems the SlaveTemplate.checkInstance() finds our orphan nodes and were able to re-attach them to the Jenkins Master. Not sure why in the past they weren't getting re-attached. 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.199745.1559315049000.7895.1586301900338%40Atlassian.JIRA.
[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Stephen Smith closed an issue as Fixed Jenkins / JENKINS-61807 "restrict where this project can be run" setting missing from job configuration Change By: Stephen Smith Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205652.1585948729000.7892.1586300640283%40Atlassian.JIRA.
[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Stephen Smith commented on JENKINS-61807 Re: "restrict where this project can be run" setting missing from job configuration Thank you, this is the route I ended up taking, and it works like a charm. This ended up being a problem of not being able to resolve old documentation from new functionality. I'll close the 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.205652.1585948729000.7890.1586300580110%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Jesse Glick commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb It is still a high-risk change due to patches under the hood of Remoting engine (JNLP4 might be potentially affected by changes) I cannot see how. None of the affected code is outside the WebSocket-specific handler method used in the -webSocket mode new in 2.222.x, except for a new method in AbstractByteBufferCommandTransport which is newly called in that modified code. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205063.1583801943000.7888.1586300340496%40Atlassian.JIRA.
[JIRA] (JENKINS-61807) "restrict where this project can be run" setting missing from job configuration
Title: Message Title Oleg Nenashev commented on JENKINS-61807 Re: "restrict where this project can be run" setting missing from job configuration Stephen Smith I assume you are trying to set this option for Pipeline jobs. "Restrict where this project can be run" exists only for Freestyle and other classic project types, for Pipeline you should use node(label) steps within your Pipeline definition. For Declarative Pipeline there is a similar "agent()" definition https://jenkins.io/doc/book/pipeline/#scripted-pipeline-fundamentals 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.205652.1585948729000.7880.1586300280116%40Atlassian.JIRA.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title Pierson Yieh commented on JENKINS-57795 Re: Orphaned EC2 instances after Jenkins restart We've also seen this behavior before though we're not sure how to reproduce the problem. We saw it when we'd hit our max AWS request limit and Jenkins started losing track of nodes and couldn't spin up new ones cause the orphaned nodes were still being counted towards the max instance count, but weren't showing up in the Jenkins UI. I'm able to "simulate" the "losing track of nodes" by running a groovy script on the Jenkins Master to manually remove the node for the Jenkins object. And we're looking into implementing a feature to automatically re-attach these orphaned nodes to Jenkins. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199745.1559315049000.7874.1586299500323%40Atlassian.JIRA.
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title Oleg Nenashev commented on JENKINS-61409 Re: Websocket connections crash if message size is greater than 64Kb Oliver Gondža JEP-222 is a pretty important feature. Even if it is experimental, it would be great to have it fixed for LTS users so that we can get more adoption and feedback from early adopters. For me backporting 4,3 is a no-go option due to removal of the deprecated code in https://github.com/jenkinsci/remoting/pull/369 . This change also adds serial version IDs, and it may lead to a funny behavior if classes are serialized over the Remoting channel. I would advice against taking the risk even in 2.222.3. CC Raihaan Shouhell who submitted a patch. At the same time https://github.com/jenkinsci/remoting/pull/373 would be considerable for 2.222.2/3 if it was released as Remoting 4.2.1. It is still a high-risk change due to patches under the hood of Remoting engine (JNLP4 might be potentially affected by changes), but personally I would give it a try for 2.222.2 assuming that extensive testing of the patch is performance for the JNLP4 mode. 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.205063.1583801943000.7866.1586298480480%40Atlassian.JIRA.
[JIRA] (JENKINS-61227) S3 publisher plugin : Make dontSetBuildResultOnFailure an Optional Field
Title: Message Title Larry Schiefer commented on JENKINS-61227 Re: S3 publisher plugin : Make dontSetBuildResultOnFailure an Optional Field Agreed. This change broke all of our multi-branch pipeline builds which are using this plugin to upload results. While we can fix it by setting this in our `Jenkinsfile`, it essentially makes CI fail for all older builds, including previous release lines which are still in maintenance mode. 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.204781.1582651987000.7863.1586296860232%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title muhammad ali commented on JENKINS-61822 Re: Unable to authorize blueocean with github Dude you made my day. I was really frustrated with this totally random issue. Downgrading github-api did the job. thanks again! 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.205672.1586165744000.7855.1586293140196%40Atlassian.JIRA.
[JIRA] (JENKINS-61838) Jenking upgrade error 2.204.2
Title: Message Title
Elek Akos updated an issue
Jenkins / JENKINS-61838
Jenking upgrade error 2.204.2
Change By:
Elek Akos
I try upgrade jenkins from ppa but i get error in Ubuntu 18.04.4: {code:java}// /var/lib/dpkg/info/jenkins.postinst: 10: /etc/default/jenkins: -Dhudson.ClassicPluginStrategy.noBytecodeTransformer=true: not founddpkg: error processing package jenkins (--configure): installed jenkins package post-installation script subprocess returned error exit status 127Errors were encountered while processing: jenkinsE: Sub-process /usr/bin/dpkg returned an error code (1){code}I restore older backup from my system and try upgrade again, but its not solve this problemThe my /etc/default/jenkins file without comments (i never edit before upgrade) {code:java}// NAME=jenkins-Dhudson.ClassicPluginStrategy.noBytecodeTransformer=trueJAVA_ARGS="-Djava.awt.headless=true"JAVA_ARGS="$JAVA_ARGS -Dhudson.ClassicPluginStrategy.noBytecodeTransformer=true"PIDFILE=/var/run/$NAME/$NAME.pidJENKINS_USER=$NAMEJENKINS_GROUP=$NAMEJENKINS_WAR=/usr/share/$NAME/$NAME.warJENKINS_HOME=/var/lib/$NAMERUN_STANDALONE=trueJENKINS_ENABLE_ACCESS_LOG="no"MAXOPENFILES=8192HTTP_PORT=8880PREFIX=/$NAMEJENKINS_ARGS="--webroot=/var/cache/$NAME/war --httpPort=$HTTP_PORT"{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61838) Jenking upgrade error 2.204.2
Title: Message Title
Elek Akos updated an issue
Jenkins / JENKINS-61838
Jenking upgrade error 2.204.2
Change By:
Elek Akos
I try upgrade jenkins from ppa but i get error in Ubuntu 18.04.4: {code:java}// /var/lib/dpkg/info/jenkins.postinst: 10: /etc/default/jenkins: -Dhudson.ClassicPluginStrategy.noBytecodeTransformer=true: not founddpkg: error processing package jenkins (--configure): installed jenkins package post-installation script subprocess returned error exit status 127Errors were encountered while processing: jenkinsE: Sub-process /usr/bin/dpkg returned an error code (1){code}I restore older backup from my system and try upgrade again, but its not solve this problem The my /etc/default/jenkins file without comments{code:java}// NAME=jenkins-Dhudson.ClassicPluginStrategy.noBytecodeTransformer=trueJAVA_ARGS="-Djava.awt.headless=true"JAVA_ARGS="$JAVA_ARGS -Dhudson.ClassicPluginStrategy.noBytecodeTransformer=true"PIDFILE=/var/run/$NAME/$NAME.pidJENKINS_USER=$NAMEJENKINS_GROUP=$NAMEJENKINS_WAR=/usr/share/$NAME/$NAME.warJENKINS_HOME=/var/lib/$NAMERUN_STANDALONE=trueJENKINS_ENABLE_ACCESS_LOG="no"MAXOPENFILES=8192HTTP_PORT=8880PREFIX=/$NAMEJENKINS_ARGS="--webroot=/var/cache/$NAME/war --httpPort=$HTTP_PORT"{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Nicolas GANDRIAU commented on JENKINS-61822 Re: Unable to authorize blueocean with github I had the same issue after upgrading my plugins and I downgraded `GitHub API` from `1.110` to `1.106` and it works now. I am able to create pipeline with blueocean. Hope that helps 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.205672.1586165744000.7850.1586291940465%40Atlassian.JIRA.
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title
muhammad ali commented on JENKINS-61822
Re: Unable to authorize blueocean with github
I have come across the same issue. I am trying to access Git enterprise and the access token just won't go through. I have been debugging the issue and this is the command that returns that error. curl -v -u admin:admin -d '{"accessToken": mytoken"}' -H "Content-Type:application/json" -XPUT http:///jenkins/blue/rest/organizations/jenkins/scm/github-enterprise/validate addition note 1: I have been using blueocean for a month now and worked just fine. The setup stopped working just 2-3 days ago. addition note 2: I have admin access for my git account so no access 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.205672.1586165744000.7838.1586291880226%40Atlassian.JIRA.
[JIRA] (JENKINS-61838) Jenking upgrade error 2.204.2
Title: Message Title Elek Akos created an issue Jenkins / JENKINS-61838 Jenking upgrade error 2.204.2 Issue Type: Bug Assignee: Unassigned Components: _unsorted Created: 2020-04-07 20:35 Environment: Ubuntu 18.04, Java 1.8.0_231 Priority: Minor Reporter: Elek Akos I try upgrade jenkins from ppa but i get error in Ubuntu 18.04.4: // /var/lib/dpkg/info/jenkins.postinst: 10: /etc/default/jenkins: -Dhudson.ClassicPluginStrategy.noBytecodeTransformer=true: not found dpkg: error processing package jenkins (--configure): installed jenkins package post-installation script subprocess returned error exit status 127 Errors were encountered while processing: jenkins E: Sub-process /usr/bin/dpkg returned an error code (1) I restore older backup from my system and try upgrade again, but its not solve this problem
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Travis Smith commented on JENKINS-61822 Re: Unable to authorize blueocean with github I'm having the same issue here running on the exact same configuration as Michael McClaren. Ubuntu 18.04 on EC2, Jenkins 2.222.1 and Blue Ocean: 1.22.0. 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.205672.1586165744000.7831.1586291280310%40Atlassian.JIRA.
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Alex Earl commented on JENKINS-61798 Re: New Windows Installer always redirects to 8080 after completing the installation I finally got a VM up and running and the XML file is correct, the launch one is not though, so that's where I need to look. 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.205642.1585912413000.7828.1586290680226%40Atlassian.JIRA.
[JIRA] (JENKINS-44681) JobDSL Folder Creation Destroys Credentials
Title: Message Title Riccardo Boettcher commented on JENKINS-44681 Re: JobDSL Folder Creation Destroys Credentials I would also favor an update / merge strategy instead of an hard override. Otherwise it becomes impossible to let users enter the credentials in the live system while maintaining the basic structure of folders via JobDSL. 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.182545.149666436.7818.1586288820362%40Atlassian.JIRA.
[JIRA] (JENKINS-61748) Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-61748
Re: Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Please take a look at [the content at the link in the error message|https://jenkins.io/redirect/pipeline-cps-method-mismatches/], specifically the section " Override Overrides of non-CPS-transformed methods". I think that in your case, if you add {{@NonCPS}} to this code, you will get the expected behavior:{code:java}@NonCPS // Add this annotationint compareTo(PriorityClosure o) { priority <=> o?.priority }{code}The reason you need to do this is that your {{PriorityClosure}} class, which is defined in a Pipeline and so all of its methods are CPS-transformed, is being passed to {{PriorityQueue}}, which is a normal Java standard library class and so is not CPS-transformed, so {{PriorityQueue.add}} is not able to call {{PriorityClosure.compareTo}} correctly.
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.205578.1585611645000.7815.1586288762261%40Atlassian.JIRA.
[JIRA] (JENKINS-61748) Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Title: Message Title
Devin Nusbaum commented on JENKINS-61748
Re: Trying to use PriorityQueue.add with custom classes winds up catching CustomClass.compareTo in scripted pipelines
Please take a look at the content at the link in the error message, specifically the section "Override of non-CPS-transformed methods". I think that in your case, if you add @NonCPS to this code, you will get the expected behavior:
@NonCPS // Add this annotation
int compareTo(PriorityClosure o) { priority <=> o?.priority }
The reason you need to do this is that your PriorityClosure class, which is defined in a Pipeline and so all of its methods are CPS-transformed, is being passed to PriorityQueue, which is a normal Java standard library class and so is not CPS-transformed, so PriorityQueue.add is not able to call PriorityClosure.compareTo correctly.
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.205578.1585611645000.7813.1586288762235%40Atlassian.JIRA.
[JIRA] (JENKINS-61785) REST API requires Job/Build permission
Title: Message Title Alex Raber commented on JENKINS-61785 Re: REST API requires Job/Build permission Thanks Juan Pablo Santos Rodríguez for the info. I also updated JENKINS-59105 with how I'm reproducing and what I've done to try to fix locally: https://issues.jenkins-ci.org/browse/JENKINS-59105?focusedCommentId=388706=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-388706 I suppose I could just create a new ticket, but it sounds like the issue is a split between these 2 tickets. 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.205624.1585839242000.7809.1586287020249%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title
Alex Raber edited a comment on JENKINS-59105
Re: Accessing Jenkins using API token does not work in group memberships
More details: I added this to JENKINS_OPS in my jenkins.sh (I'm running in k8s via docker):{{jenkins_opts_array=('-Dhudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO=true')}}^ per: [https://jenkins.io/doc/upgrade-guide/2.204/#upgrading-to-jenkins-lts-2-204-6]I then generated a new token for my user, and set up my Github repo webhook as follows: url: [https://dev-jenkins.url.gov/job/testjob/build] secret: (with admin/owner perms) application/jsonThen click apply and then click the test button from github. 403.I have also enabled and disabled the Enable proxy compatibility CSRF checkbox in Global Security.Note my testing is done in a sandbox, but the issue is impacting my production jenkins as well. I'd prefer not to roll back if possible. There are also these items in the 2.204.6 upgrade doc: {code:java}- Remove Enable Security checkbox in the Global Security configuration. (issue 40228) - Remove the ability to disable CSRF protection. Instances upgrading from older versions of Jenkins will have CSRF protection enabled and the default issuer set if they currently have it disabled. (pull 4509){code} These are not options in the UI in 2.222.1
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title
Alex Raber edited a comment on JENKINS-59105
Re: Accessing Jenkins using API token does not work in group memberships
More details: I added this to JENKINS_OPS in my jenkins.sh (I'm running in k8s via docker): ` {{ jenkins_opts_array=('-Dhudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO=true') ` }} I then generated a new token for my user, and set up my Github repo webhook as follows: url: [https://dev-jenkins.url.gov/job/testjob/build] secret: (with admin/owner perms) application/jsonThen click apply and then click the test button from github. 403.I have also enabled and disabled the Enable proxy compatibility CSRF checkbox in Global Security.Note my testing is done in a sandbox, but the issue is impacting my production jenkins as well. I'd prefer not to roll back if possible.
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.201528.1566922172000.7794.1586286600319%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title
Alex Raber edited a comment on JENKINS-59105
Re: Accessing Jenkins using API token does not work in group memberships
More details: I added this to JENKINS_OPS in my jenkins.sh (I'm running in k8s via docker):{{jenkins_opts_array=('-Dhudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO=true')}} ^ per: [https://jenkins.io/doc/upgrade-guide/2.204/#upgrading-to-jenkins-lts-2-204-6] I then generated a new token for my user, and set up my Github repo webhook as follows: url: [https://dev-jenkins.url.gov/job/testjob/build] secret: (with admin/owner perms) application/jsonThen click apply and then click the test button from github. 403.I have also enabled and disabled the Enable proxy compatibility CSRF checkbox in Global Security.Note my testing is done in a sandbox, but the issue is impacting my production jenkins as well. I'd prefer not to roll back if possible.
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.201528.1566922172000.7799.1586286600419%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title
Alex Raber edited a comment on JENKINS-59105
Re: Accessing Jenkins using API token does not work in group memberships
More details: I added this to JENKINS_OPS in my jenkins.sh (I'm running in k8s via docker): ` jenkins_opts_array=('-Dhudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO=true') ` I then generated a new token for my user, and set up my Github repo webhook as follows:url: [ https://dev-jenkins.url.gov/job/testjob/build ] secret: (with admin/owner perms)application/jsonThen click apply and then click the test button from github. 403.I have also enabled and disabled the Enable proxy compatibility CSRF checkbox in Global Security.Note my testing is done in a sandbox, but the issue is impacting my production jenkins as well. I'd prefer not to roll back if possible.
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.201528.1566922172000.7784.1586286540477%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title
Alex Raber commented on JENKINS-59105
Re: Accessing Jenkins using API token does not work in group memberships
More details: I added this to JENKINS_OPS in my jenkins.sh (I'm running in k8s via docker): jenkins_opts_array=('-Dhudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO=true') I then generated a new token for my user, and set up my Github repo webhook as follows: url: https://dev-jenkins.url.gov/job/testjob/build secret: (with admin/owner perms) application/json Then click apply and then click the test button from github. 403. I have also enabled and disabled the Enable proxy compatibility CSRF checkbox in Global Security. Note my testing is done in a sandbox, but the issue is impacting my production jenkins as well. I'd prefer not to roll back if possible.
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.201528.1566922172000.7779.1586286540417%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title
Alex Raber edited a comment on JENKINS-59105
Re: Accessing Jenkins using API token does not work in group memberships
More details: I added this to JENKINS_OPS in my jenkins.sh (I'm running in k8s via docker):`jenkins_opts_array=('-Dhudson.security.csrf.CrumbFilter.UNPROCESSED_PATHINFO=true')`I then generated a new token for my user, and set up my Github repo webhook as follows: url: [https://dev-jenkins.url.gov/job/testjob/build] secret: (with admin/owner perms) application/jsonThen click apply and then click the test button from github. 403.I have also enabled and disabled the Enable proxy compatibility CSRF checkbox in Global Security.Note my testing is done in a sandbox, but the issue is impacting my production jenkins as well. I'd prefer not to roll back if possible.
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.201528.1566922172000.7789.1586286540531%40Atlassian.JIRA.
[JIRA] (JENKINS-56594) Warnings trend graph has no y-axis legend
Title: Message Title Allan C commented on JENKINS-56594 Re: Warnings trend graph has no y-axis legend Ulli Hafner We just created a new pull request: https://github.com/jenkinsci/warnings-ng-plugin/pull/436 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 to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198216.1552902109000.7772.1586286480306%40Atlassian.JIRA.
[JIRA] (JENKINS-61819) Class jenkins.security.QueueItemAuthenticatorConfiguration was not found - Active Choice potentially not yet loaded
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-61819 Class jenkins.security.QueueItemAuthenticatorConfiguration was not found - Active Choice potentially not yet loaded Change By: Basile Chandesris Environment: Redat 7, Java 8 442 242 , Jenkins LTS 2.222.1, Active Choice plugin 2.1 (not latest) unochoice 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.205669.1586158012000.7755.1586284680323%40Atlassian.JIRA.
[JIRA] (JENKINS-61818) AUTH: IllegalStateException: Singleton is called recursively returning different results
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-61818 AUTH: IllegalStateException: Singleton is called recursively returning different results Change By: Basile Chandesris Environment: Redhat 7, Java 8 442 242 , Jenkins LTS 2.222.1, REST Remote API is used. 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.205668.1586157546000.7753.1586284680252%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Basile Chandesris updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Basile Chandesris Environment: Redhat 7, Java 8 442 242 , Jenkins 2.222.1 / 2.204.4Antisamy Markup Formatter 2.0 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.7751.1586284620694%40Atlassian.JIRA.
[JIRA] (JENKINS-61837) Build new JNLP Image alternative use
Title: Message Title Marky Jackson created an issue Jenkins / JENKINS-61837 Build new JNLP Image alternative use Issue Type: Task Assignee: Marky Jackson Components: kubernetes-plugin Created: 2020-04-07 18:19 Priority: Minor Reporter: Marky Jackson There have been a few use cases where additional functionality is needed in the JNLP agent image. This is a side task for me to build out such an image and also document how to build out additional image functionality without messing with the JNLP remoting aspect. Please ping me if you have any questions. Add Comment
[JIRA] (JENKINS-48585) must specify image in containerTemplate when inheriting
Title: Message Title Peter Loron commented on JENKINS-48585 Re: must specify image in containerTemplate when inheriting Hello. This issue from 2017(!!!) is still present. Needing to specify the image is dangerous when overriding the global template as discrepancies between the template and jobs will arise. 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.187225.1513366733000.7734.1586282040168%40Atlassian.JIRA.
[JIRA] (JENKINS-55001) Sandboxed System Groovy Scripts don't support multiple assignments (with Tuples)
Title: Message Title David Drum commented on JENKINS-55001 Re: Sandboxed System Groovy Scripts don't support multiple assignments (with Tuples) This also occurs when tabbing away from the Execute system Groovy script Build step when, I assume, Jenkins checks the script in a sandbox. It is possible to ignore the error, save the job configuration, and run the script successfully. 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.196037.1543917708000.7731.1586278440190%40Atlassian.JIRA.
[JIRA] (JENKINS-61836) Job shows Load Runner controller is still running. Can't shutdown gracefully
Title: Message Title Sara Depoy created an issue Jenkins / JENKINS-61836 Job shows Load Runner controller is still running. Can't shutdown gracefully Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-07 16:51 Environment: Windows Server 2016 Data Center Jenkins 2.222.1 Internet Explorer Java 8.241 Labels: slave jenkins Priority: Critical Reporter: Sara Depoy 21/03/2020 05:26:03 Running: E:\LoadRunner\workspace\Synmon_GAMEv3.lrs 21/03/2020 05:26:10 Test complete: E:\LoadRunner\workspace\Synmon_GAMEv3.lrs Error: Cannot close Controller gracefully, exception details: Error: The RPC server is unavailable. (Exception from HRESULT: 0x800706BA) Error: at System.RuntimeType.ForwardCallToInvokeMember(String memberName, BindingFlags flags, Object target, Int32[] aWrapperTypes, MessageData& msgData) Error: killing Controller process Run status: Job failed, total tests: 1, succeeded: 0, failures: 0, errors: 1, warnings: 0
[JIRA] (JENKINS-56255) occasionally builds the branch for a PR also
Title: Message Title Brian J Murrell commented on JENKINS-56255 Re: occasionally builds the branch for a PR also OK. So I am back. There is something more flawed than just a race between new branch and PR discovery going on here. This doesn't just happen on initial branch/PR creation (i.e Build #1) but happens on subsequent pushes to the PR/branch. If this were just a race, subsequent pushes would not fall victim to this, correct? Additionally, working from forks (as much as my users really want to do it) is actually, unworkable due to these bugs. But working from forks or not is actually quite orthogonal, as I have described above, this does not seem to merely be a race condition on new branches/forks. This doesn't seem to be "by design". This seems like an actual bug. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197825.1550941413000.7709.1586277360205%40Atlassian.JIRA.
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title Kristin Whetstone commented on JENKINS-60979 Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory Unassigning from Natasha since she was working on the plugin-installation-manager-tool and this appears to be the actual PluginManager in Jenkins proper. I've also updated the component to reflect the change. Ben, if you have a solution, feel free to make a PR! 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.204447.1580906476000.7713.1586277360260%40Atlassian.JIRA.
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title Kristin Whetstone updated an issue Jenkins / JENKINS-60979 Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory Change By: Kristin Whetstone Component/s: core Component/s: plugin-installation-manager-tool 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.204447.1580906476000.7711.1586277360233%40Atlassian.JIRA.
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title Kristin Whetstone assigned an issue to Unassigned Jenkins / JENKINS-60979 Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory Change By: Kristin Whetstone Assignee: Natasha Stopa 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.204447.1580906476000.7707.1586277120421%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title John Rocha commented on JENKINS-61779 Re: Regression: Job stuck in queue waiting forever after upgrade Having the same problem. I update about once a month and after updating from 2.204 to 2.222 I see the same issue, but I'm on Windows systems. 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.205618.158582599.7703.1586276760217%40Atlassian.JIRA.
[JIRA] (JENKINS-61779) Regression: Job stuck in queue waiting forever after upgrade
Title: Message Title John Rocha updated an issue Jenkins / JENKINS-61779 Regression: Job stuck in queue waiting forever after upgrade Change By: John Rocha Priority: Minor Blocker 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.205618.158582599.7698.1586276700335%40Atlassian.JIRA.
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Sladyn Nunes commented on JENKINS-61798 Re: New Windows Installer always redirects to 8080 after completing the installation Okay do let me know if I can help or take a look at the PR 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.205642.1585912413000.7701.1586276700436%40Atlassian.JIRA.
[JIRA] (JENKINS-37809) Throttling based on parameters does not work in Pipelines
Title: Message Title Franco Bladilo commented on JENKINS-37809 Re: Throttling based on parameters does not work in Pipelines Having the same issues not being able to throttle pipeline jobs based on parameters, has this received any attention/help/updates? This is causing a lot of pain on our internal CI. Running Jenkins jenkins-2.222.1 with latest TCB. 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.173942.1472562343000.7682.1586276640471%40Atlassian.JIRA.
[JIRA] (JENKINS-37809) Throttling based on parameters does not work in Pipelines
Title: Message Title Franco Bladilo updated JENKINS-37809 Jenkins / JENKINS-37809 Throttling based on parameters does not work in Pipelines Change By: Franco Bladilo Status: Reopened Open 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.173942.1472562343000.7666.1586276461158%40Atlassian.JIRA.
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Alex Earl commented on JENKINS-61798 Re: New Windows Installer always redirects to 8080 after completing the installation It hasn't been merged yet. It's still part of a PR. Oleg Nenashev Can you check the jenkins.xml file and see if the correct port number is in there? 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.205642.1585912413000.7662.1586276220140%40Atlassian.JIRA.
[JIRA] (JENKINS-61808) Always encrypt f:password values, not just those backed by Secret
Title: Message Title Jesse Glick updated JENKINS-61808 Jenkins / JENKINS-61808 Always encrypt f:password values, not just those backed by Secret Change By: Jesse Glick 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.205653.1585961043000.7652.1586276101065%40Atlassian.JIRA.
[JIRA] (JENKINS-61798) New Windows Installer always redirects to 8080 after completing the installation
Title: Message Title Sladyn Nunes commented on JENKINS-61798 Re: New Windows Installer always redirects to 8080 after completing the installation Maybe I could take this up, and try solving it. But I cannot find the source code for the installer CC Oleg Nenashev 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.205642.1585912413000.7650.1586274840159%40Atlassian.JIRA.
[JIRA] (JENKINS-61824) Git plugin credential lookup uses too low level API
Title: Message Title Matt Sicker commented on JENKINS-61824 Re: Git plugin credential lookup uses too low level API Likely related! I started looking at patching this yesterday, though since the affected code seemed to be a little fancier than expected, I think I may need to take a step back to examine credentials-plugin and see if there's any more APIs that needed to be updated in it to properly integrate the fancier credential resolution. This API has clearly evolved over a long period of time, so not every plugin seems to be using the most effective APIs. 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.205677.1586203717000.7646.1586274660547%40Atlassian.JIRA.
[JIRA] (JENKINS-61724) Create tests for CoverageScore (in AutoGrader)
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-61724 Create tests for CoverageScore (in AutoGrader) Change By: Ulli Hafner Assignee: Andreas Riepl 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.205550.1585338652000.7638.1586274420148%40Atlassian.JIRA.
[JIRA] (JENKINS-61724) Create tests for CoverageScore (in AutoGrader)
Title: Message Title Ulli Hafner stopped work on JENKINS-61724 Change By: Ulli Hafner Status: In Progress Open 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.205550.1585338652000.7636.1586274360297%40Atlassian.JIRA.
[JIRA] (JENKINS-61758) Test Result Summary in logs is incorrect.
Title: Message Title Barrie Sager assigned an issue to Daniel Gront Jenkins / JENKINS-61758 Test Result Summary in logs is incorrect. Change By: Barrie Sager Assignee: Roy Lu Daniel Gront 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.205595.1585676315000.7633.1586274000142%40Atlassian.JIRA.
[JIRA] (JENKINS-61758) Test Result Summary in logs is incorrect.
Title: Message Title Barrie Sager assigned an issue to Roy Lu Jenkins / JENKINS-61758 Test Result Summary in logs is incorrect. Change By: Barrie Sager Assignee: Kevin Lee Roy Lu 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.205595.1585676315000.7630.1586273940213%40Atlassian.JIRA.
[JIRA] (JENKINS-61835) Credentials cannot be selected in the job config without having administer permissinos
Title: Message Title Manuel Gonzalez created an issue Jenkins / JENKINS-61835 Credentials cannot be selected in the job config without having administer permissinos Issue Type: Bug Assignee: Unassigned Components: bitbucket-plugin Created: 2020-04-07 15:37 Environment: Bitbucket version where the issue was reproducible: 1.1.5 and 1.1.11 Jenkins version: CloudBees Jenkins Enterprise 2.190.3.2-rolling Priority: Minor Reporter: Manuel Gonzalez When configuring a freestyle job and selecting "Bitbucket Server" on "Source Code Management", the user cannot select any credentials from the dropdown menu if "administer" permissions are not granted. This has happened using Bitbucket plugin 1.1.5 and 1.1.11 with Jenkins 2.190.3.2-rolling. At the same time and same scenario, choosing git instead of bitbucket, the user was able to select credentials from the dropdown. Add Comment
[JIRA] (JENKINS-61834) Side-panel shows "IAR Compiler (C/C) Warnings"
Title: Message Title Ben Spoor created an issue Jenkins / JENKINS-61834 Side-panel shows "IAR Compiler (C/C) Warnings" Issue Type: Bug Assignee: Ulli Hafner Attachments: Screenshot.png Components: warnings-ng-plugin Created: 2020-04-07 15:32 Environment: Jenkins 2.204.2 on Windows Server 2012 R2 64-bit Warnings Next Generation Plugin io.jenkins.plugins:warnings-ng:8.1.0 Firefox 74.0 64-bits Labels: escaping warnings-ng-plugin sidepanel Priority: Minor Reporter: Ben Spoor When opening a specific run of a job the side-panel shows the IAR tool with the ++ symbols escaped. In the center the displaying is ok. See screenshot below.
[JIRA] (JENKINS-61623) Using post section in kuberenetes agents (kuberenetes-plugin)
Title: Message Title
Sami Sallmen commented on JENKINS-61623
Re: Using post section in kuberenetes agents (kuberenetes-plugin)
The post step in description is not really correct. It works if the post is on the same level as stages-section, a child to pipeline. Like this:
pipeline {
agent {
kubernetes {
yamlFile 'examples/declarative_from_yaml_file/KubernetesPod.yaml'
}
}
stages {
stage('Run maven') {
steps {
sh 'set'
sh "echo OUTSIDE_CONTAINER_ENV_VAR = ${CONTAINER_ENV_VAR}"
container('maven') {
sh 'echo MAVEN_CONTAINER_ENV_VAR = ${CONTAINER_ENV_VAR}'
sh 'mvn -version'
}
container('busybox') {
sh 'echo BUSYBOX_CONTAINER_ENV_VAR = ${CONTAINER_ENV_VAR}'
sh '/bin/busybox'
}
}
}
}
// simply adding a basic post step inside the pipeline
post {
always {
sh "echo this is a post step"
}
}
}
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-61723) Create tests for AnalysisScore (in AutoGrader)
Title: Message Title Ulli Hafner updated JENKINS-61723 Jenkins / JENKINS-61723 Create tests for AnalysisScore (in AutoGrader) Change By: Ulli Hafner Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205549.158533863.7614.1586272500223%40Atlassian.JIRA.
[JIRA] (JENKINS-61715) Improve tests for CoverageScore (in CoverageScoreTest)
Title: Message Title Ulli Hafner updated JENKINS-61715 Jenkins / JENKINS-61715 Improve tests for CoverageScore (in CoverageScoreTest) Change By: Ulli Hafner 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205541.1585329793000.7612.1586271900319%40Atlassian.JIRA.
[JIRA] (JENKINS-61719) Create tests for TestConfiguration (in TestScoreTest)
Title: Message Title Ulli Hafner updated JENKINS-61719 Jenkins / JENKINS-61719 Create tests for TestConfiguration (in TestScoreTest) Change By: Ulli Hafner 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205545.1585335461000.7610.1586271780522%40Atlassian.JIRA.
[JIRA] (JENKINS-61712) Improve tests for TestScore (in TestScoreTest)
Title: Message Title Ulli Hafner updated JENKINS-61712 Jenkins / JENKINS-61712 Improve tests for TestScore (in TestScoreTest) Change By: Ulli Hafner 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205538.1585328871000.7608.1586271780486%40Atlassian.JIRA.
[JIRA] (JENKINS-61720) Create tests for CoverageConfiguration (in CoverageScoreTest)
Title: Message Title Ulli Hafner updated JENKINS-61720 Jenkins / JENKINS-61720 Create tests for CoverageConfiguration (in CoverageScoreTest) Change By: Ulli Hafner Status: Reopened Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205546.1585336422000.7606.1586271600483%40Atlassian.JIRA.
[JIRA] (JENKINS-61713) Improve tests for PitScore (in PitScoreTest)
Title: Message Title Ulli Hafner updated JENKINS-61713 Jenkins / JENKINS-61713 Improve tests for PitScore (in PitScoreTest) Change By: Ulli Hafner 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205539.1585329712000.7604.1586271600427%40Atlassian.JIRA.
[JIRA] (JENKINS-61714) Improve tests for AnalysisScore (in AnalysisScoreTest)
Title: Message Title Ulli Hafner updated JENKINS-61714 Jenkins / JENKINS-61714 Improve tests for AnalysisScore (in AnalysisScoreTest) Change By: Ulli Hafner 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 jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205540.1585329764000.7602.1586271540246%40Atlassian.JIRA.
[JIRA] (JENKINS-61833) On "test connection" to ALM Octane - show available ALM Octane workspaces
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61833 On "test connection" to ALM Octane - show available ALM Octane workspaces Change By: Radi Berkovich Labels: 6.2.1-BETA 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.205686.1586269018000.7580.1586269080139%40Atlassian.JIRA.
[JIRA] (JENKINS-61833) On "test connection" to ALM Octane - show available ALM Octane workspaces
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-61833 On "test connection" to ALM Octane - show available ALM Octane workspaces Issue Type: New Feature Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-04-07 14:16 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-61832) Allow to disable ALM Octane configuration temporary
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-61832 Allow to disable ALM Octane configuration temporary Change By: Radi Berkovich Labels: 6.2.1-BETA 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.205685.1586268739000.7578.1586268780237%40Atlassian.JIRA.
[JIRA] (JENKINS-61832) Allow to disable ALM Octane configuration temporary
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-61832 Allow to disable ALM Octane configuration temporary Issue Type: New Feature Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2020-04-07 14:12 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you
[JIRA] (JENKINS-61822) Unable to authorize blueocean with github
Title: Message Title Michael McClaren commented on JENKINS-61822 Re: Unable to authorize blueocean with github My apologies for the confusion with my choice of terminology. What I should have said is that I validated that the token was correct by using it in bash and running git clone over https using the token. The only place that the token appears to have an issue is in the Blue ocean editor. 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.205672.1586165744000.7574.1586266680235%40Atlassian.JIRA.
[JIRA] (JENKINS-60243) Blue Ocean Input Step Json Error
Title: Message Title Christian Ciach commented on JENKINS-60243 Re: Blue Ocean Input Step Json Error This is probably a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-41662 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.203225.1574343655000.7565.1586264760277%40Atlassian.JIRA.
[JIRA] (JENKINS-60243) Blue Ocean Input Step Json Error
Title: Message Title Christian Ciach edited a comment on JENKINS-60243 Re: Blue Ocean Input Step Json Error This is probably a duplicate of https://issues.jenkins-ci.org/browse/ JENKINS-41662 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.203225.1574343655000.7567.1586264760309%40Atlassian.JIRA.
[JIRA] (JENKINS-61831) "Validate Proxy" ignores 407 AuthenticationRequired
Title: Message Title Stefan created an issue Jenkins / JENKINS-61831 "Validate Proxy" ignores 407 AuthenticationRequired Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-04-07 12:31 Environment: OS=Centos7 Java=1.8.0_51 Oracle Jenkins=2.204.2 Priority: Minor Reporter: Stefan Clicking on "Validate Proxy" results in " Failed to connect to ... 407" being displayed, but update information can be downloaded. Looking at a network trace between Jenkins and our Proxy when clicking on "Validate Proxy" GET http://updates.jenkins-ci.org/update-center.json HTTP/1.1\r\n User-Agent: Jakarta Commons-HttpClient/3.1\r\n HTTP/1.1 407 authenticationrequired\r\n Proxy-Connection: Keep-Alive\r\n Proxy-Authenticate: Negotiate\r\n Proxy-Authenticate: NTLM\r\n Proxy-Authenticate: Basic realm="***"\r\n GET http://updates.jenkins-ci.org/update-center.json HTTP/1.1\r\n User-Agent: Jakarta Commons-HttpClient/3.1\r\n Proxy-Connection: Keep-Alive\r\n Host: updates.jenkins-ci.org\r\n \r\n HTTP/1.1 407 authenticationrequired\r\n The Proxy answers with a 407, but Jenkins does not include any authentication header in it's second try. Looking at the "Check now" trace, Jenkins replies to the 407 with a proper Negotiate header: GET http://updates.jenkins-ci.org/update-center.json?id=default=2.204.2 HTTP/1.1\r\n
[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 Jesse Glick no sure why. The same search query was listing 3 plugins for me before... And now it also shows two. Direct link: https://github.com/jenkinsci/electricflow-plugin/blob/e2c149ab62e0704538f16630635584417498e560/pom.xml#L102-L105 Again, I have not spent time trying to reproduce it so far. TABLE field exists in all owasp-java-html-sanitizer versions since 2015. https://github.com/OWASP/java-html-sanitizer/commit/da2e0191fdd6fda1002f4a1b24d8446b5659768c 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.7527.1586261880166%40Atlassian.JIRA.
[JIRA] (JENKINS-61670) Attribute like e.g. class gets lost from HTML code in description fields
Title: Message Title Lars commented on JENKINS-61670 Re: Attribute like e.g. class gets lost from HTML code in description fields Why was this issue changed from "bug" to "improvement"? It worked before and is broken now and there was no need to change it. So it's a bug. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205403.1585077195000.7524.1586261580051%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Jesse Glick commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Anyway presence of another version of the library in an unrelated plugin should not cause errors. Jenkins would load each in an independent class loader. We need steps to reproduce 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.205670.1586158442000.7522.1586261340430%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Jesse Glick commented on JENKINS-61820 Re: jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Oleg Nenashev that search URL does not mention anything about a CloudBees Flow plugin. Where are you getting this from? 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.7519.1586261280256%40Atlassian.JIRA.
[JIRA] (JENKINS-61818) AUTH: IllegalStateException: Singleton is called recursively returning different results
Title: Message Title Oleg Nenashev commented on JENKINS-61818 Re: AUTH: IllegalStateException: Singleton is called recursively returning different results Basile ChandesrisHi, could you please provide a full startup log? 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.205668.1586157546000.7517.1586260860158%40Atlassian.JIRA.
[JIRA] (JENKINS-45177) Dependency error with ruby-runtime while installing Cucumber plugin blocks execution of cucumber tests
Title: Message Title Fajar Lesmana commented on JENKINS-45177 Re: Dependency error with ruby-runtime while installing Cucumber plugin blocks execution of cucumber tests https://stackoverflow.com/questions/44403642/jenkins-plugin-installation-failing 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.183298.1498654948000.7513.1586259480335%40Atlassian.JIRA.
[JIRA] (JENKINS-61725) Create tests for PitScore (in AutoGrader)
Title: Message Title Simon Schoenwiese assigned an issue to Simon Schoenwiese Jenkins / JENKINS-61725 Create tests for PitScore (in AutoGrader) Change By: Simon Schoenwiese Assignee: Simon Schoenwiese Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205551.1585338673000.7515.1586259480466%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 Basile Chandesris could you please onfirm whether you use CloudBees Flow or Timestamper plugins and, if yes, provide the versions? 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.7509.1586259360125%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 After the initial triage, it looks like there is a regression in Antisamy Markup Formatter 2.0. The reported code was added in https://github.com/jenkinsci/antisamy-markup-formatter-plugin/pull/12 , and it is the only pull request included into the release. I suspect there is another plugin which causes a binary conflict in owasp-java-html-sanitizer . It is either CloudBees Flow or old Timestamper plugin according to https://github.com/search?q=org%3Ajenkinsci+%22owasp-java-html-sanitizer%22=Code. CC Daniel Beck Jesse Glick 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.7507.1586258880149%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Oleg Nenashev Labels: jelly jelly-tag regression table 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.7503.1586258640379%40Atlassian.JIRA.
[JIRA] (JENKINS-61820) jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Oleg Nenashev Environment: Redhat 7, Java 8 442, Jenkins 2.222.1 / 2.204.4 Antisamy Markup Formatter 2.0 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.7505.1586258640400%40Atlassian.JIRA.
[JIRA] (JENKINS-61785) REST API requires Job/Build permission
Title: Message Title Juan Pablo Santos Rodríguez commented on JENKINS-61785 Re: REST API requires Job/Build permission Hi, we were able to locate what's happening, seems that efectively there's a bug introduced in latests LTS / role-strategy-plugin versions: The user id we were using on our API calls was "INETIC" (uppercased, as it is how it is set up on the active directory); this could be seen while debugging curl's request headers: "* Server auth using Basic with user 'INETIC'". Response headers told something a bit different, though: "< X-You-Are-Authenticated-As: inetic" (note user id is lowercased here). The "Manage Roles" screen assigns roles to INETIC no matter how you introduce the ID. Most probably, the user id is being fetched from the AD, which makes sense. From within the API call, being authenticated as inetic, there are no roles assigned to it, as they are assigned to INETIC. Seems that this lowercasing wasn't happening before. We've changed the API user (with its associated token) to another with a lowercased user id and our problems are gone. This wasn't happening on our previous Jenkins instance (2.204.2 LTS with role-strategy-plugin 2.14, IIRC). The issue seems to happen with newer Jenkins LTS instances + role-strategy plugin 2.15 and 2.16, don't know specifically where the bug / regression is lying.. 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 Oleg Nenashev updated an issue Jenkins / JENKINS-61820 jelly.JellyTagException: java.lang.NoClassDefFoundError: Could not initialize class hudson.markup.BasicPolicy Change By: Oleg Nenashev Component/s: antisamy-markup-formatter-plugin Component/s: core 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.7496.1586258520246%40Atlassian.JIRA.
[JIRA] (JENKINS-59105) Accessing Jenkins using API token does not work in group memberships
Title: Message Title Oleg Nenashev started work on JENKINS-59105 Change By: Oleg Nenashev 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.201528.1566922172000.7491.1586257860345%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Oleg Nenashev commented on JENKINS-61823 Re: "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 BACKPORTING NOTES: Winstone master branch includes a patch for Winstone redirects by Alex Earl: https://github.com/jenkinsci/winstone/pull/98 The fix is quite trivial, but we may not want to backport it to 2.222.x due to our experience in the past months I can prepare a release of Winstone 5.9.1 with a backport 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.205673.1586177353000.7488.1586257620182%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Change By: Oleg Nenashev Labels: lts-candidate non-trivial-lts-backporting regression 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.205673.1586177353000.7484.1586257440239%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Oleg Nenashev updated JENKINS-61823 Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Change By: Oleg Nenashev 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.205673.1586177353000.7480.1586257260978%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Oleg Nenashev started work on JENKINS-61823 Change By: Oleg Nenashev 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.205673.1586177353000.7476.1586257260699%40Atlassian.JIRA.
[JIRA] (JENKINS-61823) "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61823 "--httpKeepAliveTimeout" no longer has any effect after upgrading to 2.222.1 Change By: Oleg Nenashev Labels: lts-candidate regression 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.205673.1586177353000.7472.1586257080262%40Atlassian.JIRA.
[JIRA] (JENKINS-61830) Pipeline Maven Integration: migrate from H2 to MySQL/PostgreSQL
Title: Message Title Sebastian Apro created an issue Jenkins / JENKINS-61830 Pipeline Maven Integration: migrate from H2 to MySQL/PostgreSQL Issue Type: Task Assignee: Cyrille Le Clerc Components: h2-api-plugin, pipeline-maven-plugin Created: 2020-04-07 10:55 Environment: Pipeline Maven Integration 3.8.1 PipelineMavenPluginH2Dao - H2 1.4.199 Labels: pipeline-maven h2 Priority: Minor Reporter: Sebastian Apro Hi, We have been using the Pipeline Maven Integration plugin with the default H2 database for a while now and we are considering to switch to MySQL or PostgreSQL (as recommended). I've read the plugin wiki that describes how to configure it to use either MySQL or PostgreSQL but I could not find more information regarding how to actually migrate from H2. Does the data from the H2 database need to be migrated to the new database or can it be discarded? Would this affect the users in any way? Are there any other things to consider before switching to a new DB or can it be done "on the fly"? Any possible issues that might come up while/after the switch? Thanks and Best regards, Sebastian
