[JIRA] (JENKINS-61676) 1.44 -> 1.49.1 Can't connect agent and doesn't terminate instance
Title: Message Title Eli Graber created an issue Jenkins / JENKINS-61676 1.44 -> 1.49.1 Can't connect agent and doesn't terminate instance Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-25 05:31 Priority: Major Reporter: Eli Graber I recently updated my plugin from 1.44 to 1.49.1 and instances spin up, don't connect, and then don't terminate. If I wasn't looking at aws this would've cost me a lot of money (had over 100 instances running doing nothing). Everything was working for months before updating. I have an agent.jar that sits in /home/ubuntu. The log from one of the instances is below. If I had to guess I'd say that the issue is that the host is null. Also I don't know what /tmp/remoting.jar is. Testing the connection and Checking the AMI both succeed. I have a subnet ID for VPC set correctly. Root command prefix = Slave command prefix = nice -15 Slave command suffix = Remote ssh port = 22 Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: Launching instance: Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: bootstrap() Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: Getting keypair... Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: Using private key android (SHA-1 fingerprint ) Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: Authenticating as ubuntu Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: Connecting to null on port 22, with timeout 35000. Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: Connected via SSH. Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: connect fresh as root Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: Connecting to null on port 22, with timeout 35000. Mar 25, 2020 1:15:17 AM hudson.plugins.ec2.EC2Cloud INFO: Connected via
[JIRA] (JENKINS-61675) Neuxs platform plugin fail to connect nexus3
Title: Message Title Hokwang Lee created an issue Jenkins / JENKINS-61675 Neuxs platform plugin fail to connect nexus3 Issue Type: Bug Assignee: Justin Young Components: nexus-platform-plugin Created: 2020-03-25 05:28 Priority: Blocker Reporter: Hokwang Lee Hello. I have Jenkins master server which is using java11 and lts version. I installed Nexus Platform plugin for integrated with my nexus 3. I did "Test Connection", but here's error. It seems your code has problem with JAXB. Nexus Repository Manager 3.x connection failedjavax.xml.bind.JAXBException: Implementation of JAXB-API has not been found on module path or classpath. - with linked exception: [java.lang.ClassNotFoundException: com.sun.xml.internal.bind.v2.ContextFactory] at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:278) at javax.xml.bind.ContextFinder.find(ContextFinder.java:421) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:721) at javax.xml.bind.JAXBContext.newInstance(JAXBContext.java:662) at com.sonatype.nexus.api.zz.fs.a(SourceFile:33) at com.sonatype.nexus.api.zz.fs.b(SourceFile:24) at com.sonatype.nexus.api.zz.fu.handleResponse(SourceFile:54) at org.apache.http.impl.client.CloseableHttpClient.execute(SourceFile:223) at org.apache.http.impl.client.CloseableHttpClient.execute(SourceFile:165) at com.sonatype.nexus.api.zz.fo.a(SourceFile:83) at com.sonatype.nexus.api.zz.fn.getVersion(SourceFile:124) at com.sonatype.nexus.api.repository.v3.RepositoryManagerV3Client$getVersion.call(Unknown Source) at org.sonatype.nexus.ci.config.Nxrm3Configuration$DescriptorImpl.doVerifyCredentials(Nxrm3Configuration.groovy:92) at java.base/java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:710) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at
[JIRA] (JENKINS-44532) Rich rich published doesn't show non-stable text on job page
Title: Message Title Hanbing Yu commented on JENKINS-44532 Re: Rich rich published doesn't show non-stable text on job page Colin Cameron I just found a "useLastStable" parameter in the [RichTextPortlet|https://javadoc.jenkins.io/plugin/rich-text-publisher-plugin/index.html?org/korosoft/jenkins/plugin/rtp/RichTextPortlet.html] class ，but as far as I know，this class is only used for "Dashboard View" plugin. It seems like when it publishes text to the job page, it also behavors in the "useLastStable" mode，which is confusing. 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.182375.1496024813000.12467.1585111260297%40Atlassian.JIRA.
[JIRA] (JENKINS-44532) Rich rich published doesn't show non-stable text on job page
Title: Message Title Colin Cameron commented on JENKINS-44532 Re: Rich rich published doesn't show non-stable text on job page Hanbing Yu I'm sure it is a plug-in or configuration problem – sadly it's a minor problem I don't have time to go through the steps of enabling/disabling all our plugins. If I was going to do that I'd start by focusing on other post-build actions and the interaction there. I had hoped it would work with a newer version (since it did definitely work with older versions) but I've upgraded everything recently and it's still the same. 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.182375.1496024813000.12465.1585109160226%40Atlassian.JIRA.
[JIRA] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Title: Message Title Ilguiz Latypov commented on JENKINS-20356 Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service For those stumbling on this ticket searching for a similar error saying "permission denied", this may result from (domain) administrators installing Bit9 Parity CarbonBlack to white-list the commands allowed on the machine. 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.151876.1383181122000.12446.1585107000562%40Atlassian.JIRA.
[JIRA] (JENKINS-61674) Quick filler text box for Extended choice parameter
Title: Message Title An Nguyen created an issue Jenkins / JENKINS-61674 Quick filler text box for Extended choice parameter Issue Type: Improvement Assignee: vimil Components: extended-choice-parameter-plugin Created: 2020-03-25 03:13 Priority: Minor Reporter: An Nguyen Adding quick filler text box for Extended choice parameter Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-60898) Contention on fingerprint files when using Docker steps
Title: Message Title Raihaan Shouhell commented on JENKINS-60898 Re: Contention on fingerprint files when using Docker steps Thats docker pipeline plugin its shortname is docker-workflow-plugin Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204288.1580249848000.12425.1585096020177%40Atlassian.JIRA.
[JIRA] (JENKINS-60010) GCLogs are collected twice
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-60010 Re: GCLogs are collected twice We should probably prevent the Master Log Recorders to include GC Logs. The method used to retrieve the GC Logs files from the "Garbage Collection Logs" component could be made reusable, so that the "Master Log Recorders" component can find out if there are any. Also the "Master Log Recorders" has an higher ordinal and will happen first. 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.202827.1572567497000.12409.1585093260049%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60009 Jenkins / JENKINS-60009 GCLogs component should be made Java 11 compatible Change By: Allan BURDAJEWICZ 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.202826.1572566602000.12407.1585092780180%40Atlassian.JIRA.
[JIRA] (JENKINS-60009) GCLogs component should be made Java 11 compatible
Title: Message Title Allan BURDAJEWICZ updated JENKINS-60009 Jenkins / JENKINS-60009 GCLogs component should be made Java 11 compatible Change By: Allan BURDAJEWICZ Status: In Review 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.202826.1572566602000.12408.1585092780290%40Atlassian.JIRA.
[JIRA] (JENKINS-61673) Status of the task is not marked properly
Title: Message Title Dawid Malinowski updated an issue Jenkins / JENKINS-61673 Status of the task is not marked properly Change By: Dawid Malinowski Summary: Task status Status of the task is not marked properly 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.205408.1585089668000.12406.1585090020066%40Atlassian.JIRA.
[JIRA] (JENKINS-61673) Task status is not marked properly
Title: Message Title Dawid Malinowski created an issue Jenkins / JENKINS-61673 Task status is not marked properly Issue Type: Bug Assignee: Dawid Malinowski Components: delivery-pipeline-plugin Created: 2020-03-24 22:41 Priority: Minor Reporter: Dawid Malinowski If one of the tasks in pipeline workflow view will fail whole pipeline (all stages) will be marked as a successful. OceanBlue is marking this stage properly. Add Comment This message was sent by Atlassian Jira
[JIRA] (JENKINS-59405) Max retries exceeded with url: /api/python?tree=jobs%5Bname%2Ccolor%2Curl%5D
Title: Message Title Chaitanya Bapat commented on JENKINS-59405 Re: Max retries exceeded with url: /api/python?tree=jobs%5Bname%2Ccolor%2Curl%5D Did this get resolved? What was the root-cause? What was the solution? 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.201963.1568713638000.12404.1585088520120%40Atlassian.JIRA.
[JIRA] (JENKINS-61672) Filter Gerrit Change Requests
Title: Message Title Felipe Santos created an issue Jenkins / JENKINS-61672 Filter Gerrit Change Requests Issue Type: New Feature Assignee: Sam Gleske Components: scm-filter-branch-pr-plugin Created: 2020-03-24 22:08 Priority: Minor Reporter: Felipe Santos How about also filter Gerrit Change Requests as well? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61656) Unable to install latest version on Ubuntu 12.04
Title: Message Title Daniel Beck closed an issue as Won't Fix There's no bug here. Update your OS, which is even out of extended support by now. Re the archive format, dpkg changed its default behavior, and the build system apparently got updated a few months ago. Jenkins / JENKINS-61656 Unable to install latest version on Ubuntu 12.04 Change By: Daniel Beck Status: Open Closed Resolution: Won't Fix 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
[JIRA] (JENKINS-61671) support-core should manage generated files
Title: Message Title Steven Deal created an issue Jenkins / JENKINS-61671 support-core should manage generated files Issue Type: Improvement Assignee: Emilio Escobar Components: support-core-plugin Created: 2020-03-24 19:54 Priority: Minor Reporter: Steven Deal The support core plugin generates files such as in the slow-requests and deadlocks folders. However, there exists no means of pruning these files. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-59753) Error cloning remote repo
Title: Message Title
ipleten edited a comment on JENKINS-59753
Re: Error cloning remote repo
Is there any updates on that?I found that `doReload()` on job object makes that work again but it also might trigger some unneeded builds.Ugly workaround:{noformat}Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.multibranch.WorkflowMultiBranchProject.class).each { it.doReload(); };{noformat} Update: Issue happens after each Jenkins restart.
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.202476.1570810205000.12290.1585078380273%40Atlassian.JIRA.
[JIRA] (JENKINS-61670) Attribute like e.g. class gets lost from HTML code in description fields
Title: Message Title Lars created an issue Jenkins / JENKINS-61670 Attribute like e.g. class gets lost from HTML code in description fields Issue Type: Bug Assignee: Unassigned Components: antisamy-markup-formatter-plugin Created: 2020-03-24 19:13 Environment: Jenkins 2.227 Priority: Major Reporter: Lars After upgrading the markup formatter plugin from 1.8 to 2.0 HTML code in system message, job description, build description and testresult description fields loses attributes like for example class attributes. We use these HTML descriptions a lot and also use the Simple Theme Plugin to style them. Without CSS classes this is not really possible. Add Comment
[JIRA] (JENKINS-61669) Removing a template from the EC2 plugin while a job is still building causes a file leak
Title: Message Title Alex Taylor created an issue Jenkins / JENKINS-61669 Removing a template from the EC2 plugin while a job is still building causes a file leak Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2020-03-24 19:10 Priority: Major Reporter: Alex Taylor Issue: When a job is running on a template from EC2 and then you go and change or delete that template it causes a file leak of files `($INSTANCE_ID)/slave.log.*` which are the traditional log files open for agents but they are not cleaned up ever afterwards and as the agent is running it opens more and more of these file handles until eventually the whole instance crashes or the build is done (the files are not released at that point but they do not continue to increase) Steps to reproduce: 1. Create a EC2 cloud 2. Create a template within that cloud 3. Create a job which takes a long period of time and uses that template 4. Run that job 5. Delete the template 6. Observe the file handles continue to increase and you can find many file handles of the format above What I would normally expect: I think the file handles being opened is OK but they should not continue to re-open. Also they should be cleaned up when the job is done and the agent goes away I have not been able to reproduce locally with the code using hpi:run as of yet so I am not sure what is causing the leak
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title
Kalle Niemitalo commented on JENKINS-61493
Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
It looks like that is what the Bitbucket Branch Source plugin does anyway, for Bitbucket Cloud. So, fixing the "refs/pull-requests/{id}/from" problem for pull requests within the same repository in Bitbucket Server could be just a matter of removing a few instanceof BitbucketCloudApiClient checks in BitbucketGitSCMBuilder.java and BitbucketSCMFileSystem.java. Fixing it for pull requests between forks would need more changes.
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.205179.1584360231000.12273.1585076940751%40Atlassian.JIRA.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Oliver Gondža commented on JENKINS-53004 Re: checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) Thanks, Mark. Provided both git-plugin and git-client-plugin depend on jgit passing its objects between the codebases, I doubt any amount of classloader isolation is going to save us. I have not realized it is this 2 plugins that are clashing. Thanks for your recommendations. 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.192990.1534144468000.12270.1585076940652%40Atlassian.JIRA.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title
Oliver Gondža edited a comment on JENKINS-53004
Re: checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
[~markewaite], we have a customer running into this with git-client 3.0.0 and git-plugin 3.12.0. The way I understand your analysis here is, an older jgit is leaking from some other plugin so git-(client-)plugin built against jgit5 is invoking signatures that was not present in the older version that is leaking in - so the fix is to get all those plugins to versions using more or less same (major) version of jgit. I tend to agree this might be the case have here , as my Jenkins has loaded 2 older versions of jgit:{noformat}$ ls -l /proc/9972/fd/ | grep jgitlr-x--. 1 jenkins jenkins 64 Mar 24 13:30 333 -> /var/lib/jenkins/plugins/git-client/WEB-INF/lib/org.eclipse.jgit.lfs-5.5.1.201910021850-r.jarlr-x--. 1 jenkins jenkins 64 Mar 24 13:30 334 -> /var/lib/jenkins/plugins/git-client/WEB-INF/lib/org.eclipse.jgit.http.apache-5.5.1.201910021850-r.jarlr-x--. 1 jenkins jenkins 64 Mar 24 13:30 337 -> /var/lib/jenkins/plugins/git-client/WEB-INF/lib/org.eclipse.jgit.http.server-5.5.1.201910021850-r.jarlr-x--. 1 jenkins jenkins 64 Mar 24 13:30 338 -> /var/lib/jenkins/plugins/git-client/WEB-INF/lib/org.eclipse.jgit-5.5.1.201910021850-r.jarlr-x--. 1 jenkins jenkins 64 Mar 24 13:30 548 -> /var/lib/jenkins/plugins/blueocean-events/WEB-INF/lib/org.eclipse.jgit-4.5.4.201711221230-r.jarlr-x--. 1 jenkins jenkins 64 Mar 24 13:30 549 -> /var/lib/jenkins/plugins/blueocean-events/WEB-INF/lib/org.eclipse.jgit.http.server-4.5.4.201711221230-r.jarlr-x--. 1 jenkins jenkins 64 Mar 24 13:30 553 -> /var/lib/jenkins/plugins/blueocean-events/WEB-INF/lib/org.eclipse.jgit.http.apache-4.5.4.201711221230-r.jarlr-x--. 1 jenkins jenkins 64 Mar 24 13:30 764 -> /var/lib/jenkins/plugins/gitlab-plugin/WEB-INF/lib/org.eclipse.jgit-3.5.2.201411120430-r.jar{noformat}However, I was under assumption that Jenkins hierarchical classloading is here to prevent dependencies to leak from plugin to plugin (so in this case, git-plugin would get the version it requires and so will the other plugins). What makes this situation special?Thanks for any pointers!
Add Comment
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Alexey Pelykh commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist Second approach sounds really robust, yet I have no real idea what implications are 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.205179.1584360231000.12262.1585075200188%40Atlassian.JIRA.
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Erez Arbell commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hello Karl Wirth. Thank you for following this issue. I apologize but currently I can't find the time to work on this issue. I suggest you will close the issue for now. If I will encounter this issue in the future I will re-open it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190940.1527360591000.12256.1585075080224%40Atlassian.JIRA.
[JIRA] (JENKINS-61546) Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61546 Variable from parameterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205243.1584621563000.12254.1585073340207%40Atlassian.JIRA.
[JIRA] (JENKINS-61545) Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61545 Variable from paramterized pipeline build is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205242.1584621529000.12252.1585073280236%40Atlassian.JIRA.
[JIRA] (JENKINS-61554) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61554 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205251.1584621682000.12248.1585073040126%40Atlassian.JIRA.
[JIRA] (JENKINS-61550) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-61550 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205247.1584621644000.12246.1585072980166%40Atlassian.JIRA.
[JIRA] (JENKINS-61550) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61550 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205247.1584621644000.12244.1585072920650%40Atlassian.JIRA.
[JIRA] (JENKINS-61568) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61568 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205265.1584621968000.12242.1585072920560%40Atlassian.JIRA.
[JIRA] (JENKINS-61558) Parameter is not interpreted in GIT Plugin Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61558 Parameter is not interpreted in GIT Plugin Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205255.1584621821000.12240.1585072920516%40Atlassian.JIRA.
[JIRA] (JENKINS-61557) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61557 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205254.1584621792000.12238.1585072860221%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title Alex Taylor commented on JENKINS-61591 Re: Using Stage view with mixed in/out of stage actions causes the build status to be wrong Devin Nusbaum Always been a problem with declarative and stage view as far back as I can tell. It does not replicate with scripted syntax in any way I have tried locally 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.205288.1584636193000.12207.1585069740194%40Atlassian.JIRA.
[JIRA] (JENKINS-61668) Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Title: Message Title
Roman Komkov updated an issue
Jenkins / JENKINS-61668
Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Change By:
Roman Komkov
h3. Steps to reproduce * Create a Username/Password pair in Credentials both should contain dollar signs (for example _u$er_ and _pa$$word_) * Create a seed job in Jenkins * Bind this credentials pair as env variables in the job * Add "Process Job DSLs" step with the following in script: {code:java}println binding.variables.get('STASH_USERNAME')println binding.variables.get('STASH_PASSWORD){code} * Run the job and see both STASH_PASSWORD and STASH_USERNAME unmasked with two dollars: {code:java}Processing provided DSL scriptu$$erpaword{code}h3. WorkaroundIf *EnvInjectBuildWrapper* is enabled for the job, the result will be{code:java}Processing provided DSL scriptpa$word{code} As you can see, the second dollar in a pa$$word was escaped, which is also wrong.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61668) Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Title: Message Title
Roman Komkov updated an issue
Jenkins / JENKINS-61668
Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Change By:
Roman Komkov
h3. Steps to reproduce * Create a Username/Password pair in Credentials both should contain dollar signs (for example _u$er_ and _pa$$word_) * Create a seed job in Jenkins * Bind this credentials pair as env variables in the job * Add "Process Job DSLs" step with the following in script: {code:java}println binding.variables.get('STASH_USERNAME')println binding.variables.get('STASH_PASSWORD ' ){code} * Run the job and see both STASH_PASSWORD and STASH_USERNAME unmasked with two dollars: {code:java}Processing provided DSL scriptu$$erpaword{code}h3. WorkaroundIf *EnvInjectBuildWrapper* is enabled for the job, the result will be{code:java}Processing provided DSL scriptpa$word{code} As you can see, the second dollar in a pa$$word was escaped, which is also wrong.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61668) Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Title: Message Title
Roman Komkov updated an issue
Jenkins / JENKINS-61668
Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Change By:
Roman Komkov
h3. Steps to reproduce : * Create a Username/Password pair in Credentials both should contain dollar signs (for example : _u$er_ and _pa$$word_ ) * Create a seed job in Jenkins * Bind this credentials pair as env variables in the job * Add "Process Job DSLs" step with the following in script: {code:java}println binding.variables.get('STASH_USERNAME') println binding.variables.get('STASH_PASSWORD) {code} * Run the job and see both STASH_PASSWORD and STASH_USERNAME unmasked with two dollars: {code:java}Processing provided DSL scriptu$$erpaword{code}h3. WorkaroundIf *EnvInjectBuildWrapper* is enabled for the job, the result will be{code:java}Processing provided DSL scriptpa$word{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Kalle Niemitalo commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist The newer Bitbucket Server Integration plugin does not even support pull requests yet, according to JENKINS-60342. 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.205179.1584360231000.12198.1585069380327%40Atlassian.JIRA.
[JIRA] (JENKINS-61591) Using Stage view with mixed in/out of stage actions causes the build status to be wrong
Title: Message Title Devin Nusbaum commented on JENKINS-61591 Re: Using Stage view with mixed in/out of stage actions causes the build status to be wrong Is this a recent regression, or has it always been broken? 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.205288.1584636193000.12196.1585069380267%40Atlassian.JIRA.
[JIRA] (JENKINS-61668) Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Title: Message Title
Roman Komkov updated an issue
Jenkins / JENKINS-61668
Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Change By:
Roman Komkov
Steps to reproduce: # * Create a Username/Password pair in Credentials both should contain dollar signs (for example: _u$er_ and _pa$$word_ # * Create a seed job in Jenkins # * Bind this credentials pair as env variables in the job # * Add "Process Job DSLs" step with the following in script:{code:java}println binding.variables.get(' STASH_PASSWORD'){code} # Run the job and see {code:java}wrappers { credentialsBinding { usernamePassword(' STASH_USERNAME' , 'STASH_PASSWORD', 'jenkins-stash-readonly-user' ) } } {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
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title
Kalle Niemitalo edited a comment on JENKINS-61493
Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
I can think of two approaches that do not rely on Bitbucket Server updating the " / refs/pull-requests/\{id\}/from" ref: * Take the commit ID from the [webhook event payload|https://confluence.atlassian.com/bitbucketserver070/event-payload-996644369.html]. In [BSERV-8268|https://jira.atlassian.com/browse/BSERV-8268], Atlassian enabled {{uploadpack.allowReachableSHA1InWant}}, so this should work even if that commit is no longer the tip of any branch, as long as it is still reachable. However, if a user of Jenkins manually triggers a build, then I guess the webhook payload will not be available. * Query [/rest/api/1.0/projects/\{projectKey\}/repos/\{repositorySlug\}/pull-requests/\{pullRequestId\}|https://docs.atlassian.com/bitbucket-server/rest/7.0.1/bitbucket-rest.html#idp283] and get the name of the source branch from within the "fromRef" property.
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.205179.1584360231000.12189.1585069020285%40Atlassian.JIRA.
[JIRA] (JENKINS-61668) Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Title: Message Title
Roman Komkov created an issue
Jenkins / JENKINS-61668
Dollar ($) sign gets doubled in credentials if exposed as ENV and used in DSL script
Issue Type:
Task
Assignee:
Daniel Spilker
Components:
credentials-binding-plugin, job-dsl-plugin
Created:
2020-03-24 16:56
Environment:
Jenkins ver. 2.204.5 Job DSL (job-dsl): 1.77 Credentials Binding Plugin (credentials-binding): 1.21
Priority:
Minor
Reporter:
Roman Komkov
Steps to reproduce:
Create a Username/Password pair in Credentials both should contain dollar signs (for example: u$er and pa$$word
Create a seed job in Jenkins
Bind this credentials pair as env variables in the job
Add "Process Job DSLs" step with the following in script:
println binding.variables.get('STASH_PASSWORD')
Run the job and see
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title
Kalle Niemitalo commented on JENKINS-61493
Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
I can think of two approaches that do not rely on Bitbucket Server updating the "/refs/pull-requests/{id}/from" ref:
Take the commit ID from the webhook event payload. In BSERV-8268, Atlassian enabled uploadpack.allowReachableSHA1InWant, so this should work even if that commit is no longer the tip of any branch, as long as it is still reachable. However, if a user of Jenkins manually triggers a build, then I guess the webhook payload will not be available.
Query /rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/pull-requests/{pullRequestId} and get the name of the source branch from within the "fromRef" property.
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.205179.1584360231000.12185.1585068661432%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Alexey Pelykh commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist Kalle Niemitalo seems so, huge blocker will take a look on various APIs maybe it's possible to trigger that somehow otherwise 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.205179.1584360231000.12176.1585067940123%40Atlassian.JIRA.
[JIRA] (JENKINS-27570) Add environment variable for last successful build commit
Title: Message Title Morgan Christiansson commented on JENKINS-27570 Re: Add environment variable for last successful build commit This should be closed. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.161372.1427215387000.12168.1585067880272%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title
Kalle Niemitalo commented on JENKINS-61493
Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
The missing "/from" was filed two years ago as JENKINS-45997, and fixed in https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/116 by making the plugin poke the /rest/api/1.0/projects/{owner}/repos/{repo}/pull-requests/{id}/merge API, but that apparently stopped working in Bitbucket Server 7.
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.205179.1584360231000.12164.1585067820132%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Alexey Pelykh commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist Update: I can trigger appearance of the "/from" ref only by viewing the diff. Super-bad behaviour 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.205179.1584360231000.12161.1585067760164%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Alexey Pelykh commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist Seems https://jira.atlassian.com/browse/BSERV-12198?focusedCommentId=2374169 is relatede as well 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.205179.1584360231000.12158.1585067640091%40Atlassian.JIRA.
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Alexey Pelykh commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist It seems that unless non-author user actually tries to view the PR, the "/from" ref is not created. So when I just use PRs on my own - "/from" is not created whatsoever, that's seems to be a severe case Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205179.1584360231000.12156.1585067040107%40Atlassian.JIRA.
[JIRA] (JENKINS-61667) Plugin Adoption Request - docker-java-api-plugin
Title: Message Title Eric Citaire created an issue Jenkins / JENKINS-61667 Plugin Adoption Request - docker-java-api-plugin Issue Type: Task Assignee: Nicolas De Loof Components: docker-java-api-plugin Created: 2020-03-24 16:09 Priority: Minor Reporter: Eric Citaire Hi all, It seems that docker-java-api-plugin does not have any active maintainer anymore. I would like to become one, if possible. Plugin repo : https://github.com/jenkinsci/docker-java-api-plugin Pending PR : jenkinsci/docker-java-api-plugin#5 My GitHub ID : ericcitaire (https://github.com/ericcitaire) My Jenkins infrastructure ID : ericcitaire (https://issues.jenkins-ci.org/secure/ViewProfile.jspa?name=ericcitaire) Thanks in advance. Best Regards, Eric. Add Comment
[JIRA] (JENKINS-61493) Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist
Title: Message Title Alexey Pelykh commented on JENKINS-61493 Re: Lightweight checkout fails in Bitbucket Server 7.0; refs/pull-requests/*/merge does not exist Seems that on 7.1.0 "/from" are not revealed via ls-remove as well 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.205179.1584360231000.12148.1585065720133%40Atlassian.JIRA.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Ramon Leon commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head I'm facing this issue on https://ci.jenkins.io/blue/organizations/jenkins/Plugins%2Fldap-plugin/detail/PR-40/4/pipeline/ for this PR: https://github.com/jenkinsci/ldap-plugin/pull/40 I guess Olivier Lamy can give you more information Devin Nusbaum. The log shows: [2020-03-24T12:26:50.886Z] java.io.IOException: Tried to load head FlowNodes for execution Owner[Plugins/ldap-plugin/PR-40/4:Plugins/ldap-plugin/PR-40 #4] but FlowNode was not found in storage for head id:FlowNodeId 1:76 [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:672) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:533) [2020-03-24T12:26:50.886Z] at hudson.model.RunMap.retrieve(RunMap.java:225) [2020-03-24T12:26:50.886Z] at hudson.model.RunMap.retrieve(RunMap.java:57) [2020-03-24T12:26:50.886Z] at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) [2020-03-24T12:26:50.886Z] at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) [2020-03-24T12:26:50.886Z] at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) [2020-03-24T12:26:50.886Z] at hudson.model.RunMap.getById(RunMap.java:205) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:921) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:932) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getExecution(CpsStepContext.java:217) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.cps.CpsStepContext.getThreadGroupSynchronously(CpsStepContext.java:242) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.cps.CpsStepContext.access$000(CpsStepContext.java:97) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.cps.CpsStepContext$1.call(CpsStepContext.java:263) [2020-03-24T12:26:50.886Z] at org.jenkinsci.plugins.workflow.cps.CpsStepContext$1.call(CpsStepContext.java:261) [2020-03-24T12:26:50.886Z] at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) [2020-03-24T12:26:50.886Z] at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) [2020-03-24T12:26:50.886Z] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) [2020-03-24T12:26:50.886Z] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) [2020-03-24T12:26:50.886Z] at java.base/java.lang.Thread.run(Thread.java:834) [2020-03-24T12:26:50.886Z] Finished: FAILURE
[JIRA] (JENKINS-51552) Cannot replay pipelines - files are read-only
Title: Message Title Karl Wirth commented on JENKINS-51552 Re: Cannot replay pipelines - files are read-only Hi Erez Arbell - I've just been going through requalifying old jobs and still cant reproduce this problem. Are you avalable later in the week so we could have a Webex? If you are please drop an email to supp...@perforce.com for my attention so we can arrange it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190940.1527360591000.12104.1585063560291%40Atlassian.JIRA.
[JIRA] (JENKINS-60898) Contention on fingerprint files when using Docker steps
Title: Message Title Matt MacGillivray commented on JENKINS-60898 Re: Contention on fingerprint files when using Docker steps Raihaan Shouhell There is no `docker-workflow` plugin? Not sure what to do to get this fix? 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.204288.1580249848000.12099.1585063080191%40Atlassian.JIRA.
[JIRA] (JENKINS-60072) trigger on "ref-updated" generates many noisy/wrong events
Title: Message Title Olga K commented on JENKINS-60072 Re: trigger on "ref-updated" generates many noisy/wrong events I have to confirm this bug. It seems like pushing a new patchset, commenting or submitting through review generates extra ref-updated events since the NoteDB migration. E.g. me writing a comment on Gerrit: GERRIT_EVENT_TYPE = ref-updated GERRIT_REFNAME = refs/changes/11/15511/meta 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.202906.1573029895000.12097.1585062600190%40Atlassian.JIRA.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Mark Waite edited a comment on JENKINS-53004 Re: checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) [~olivergondza] sorry for the confusion caused by not having the same major version number on git client plugin and git plugin releases. Git client 3.x bundles JGit 5.x and is intended to be used by git plugin 4.x and later. Git client 2.x bundles JGit 4.x and is intended to be used by git plugin 3.x. In the case for your customer, the preferred change is probably to switch them either from git client plugin 3.0.0 to git client plugin 2.9.0 or from git plugin 3 . 12.0 to git plugin 4.2.2. You're correct that the JGit project made API breaking changes between JGit 4.x and JGit 5.x. Those API breaking changes required that we "lock-step" release the git plugin 4.x release and the git client plugin 3.x release.I'm not expert enough with the Jenkins class loader or with Java class loading to know if it is possible to have git client plugin 3.x loaded in memory with its bundled copy of JGit 5.x and still have git plugin 3.x cause the loading of JGit 4.x into memory. The git plugin depends on git client and does not declare a dependency on JGit. The git plugin relies on the git client plugin's commitment to always provide a JGit implementation.I think in your case that you want to either downgrade from git client plugin 3.0.0 to git client plugin 2.9.0 or upgrade from git plugin 3.12.0 to git plugin 4.2.2. In terms of functionality change, the downgrade from git client plugin 3.0.0 to git client plugin 2.9.0 is smaller than the change from git plugin 3.12.0 to git plugin 4.2.2. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58778) [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Title: Message Title
Christian Ciach edited a comment on JENKINS-58778
Re: [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Maybe we could do something like that as a workaround:{code:java}findFiles(glob: 'Build/rpms/*.rpm').each { rpmFile -> sshPut remote: remote, from: rpmFile.path, into: '/data/mirror/rpm-repo'}{code}This feels a bit dirty this probably has negative performance implications, because this establishes a new SSH-connection for each file.It would be great if this plugin could provide a "flatten" parameter for the sshPut-step, like the publish-over-ssh plugin: [https://wiki.jenkins.io/display/JENKINS/Publish+Over#PublishOver-Flattenfiles]Or, alternatively, allow a wildcard for the "from"-parameter of the sshPut-step, so we could use "Build/rpms/*" instead of "Build/rpms" as the source.The underlying library allow allows many kinds of "from" parameters (like Iterables), not just Strings. Maybe this jenkins plugin could be modified so that not only Strings are permitted as the "from" parameter? At least maybe allow Iterables, too?
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.201087.156473320.12069.1585061640173%40Atlassian.JIRA.
[JIRA] (JENKINS-58778) [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Title: Message Title
Christian Ciach edited a comment on JENKINS-58778
Re: [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Maybe we could do something like that as a workaround:{code:java}findFiles(glob: 'Build/rpms/*.rpm').each { rpmFile -> sshPut remote: remote, from: rpmFile.path, into: '/data/mirror/rpm-repo'}{code}This feels a bit dirty this probably has negative performance implications, because this establishes a new SSH-connection for each file.It would be great if this plugin could provide a "flatten" parameter for the sshPut-step, like the publish-over-ssh plugin: [https://wiki.jenkins.io/display/JENKINS/Publish+Over#PublishOver-Flattenfiles]Or, alternatively, allow a wildcard for the "from"-parameter of the sshPut-step, so we could use "Build/rpms/*" instead of "Build/rpms" as the source. The underlying library allow many kinds of "from" parameters (like Iterables), not just Strings. Maybe this jenkins plugin could be modified so that not only Strings are permitted as the "from" parameter? At least maybe allow Iterables, too?
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.201087.156473320.12056.1585059840211%40Atlassian.JIRA.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Mark Waite edited a comment on JENKINS-53004 Re: checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) [~olivergondza] sorry for the confusion caused by not having the same major version number on git client plugin and git plugin releases. Git client 3.x bundles JGit 5.x and is intended to be used by git plugin 4.x and later. Git client 2.x bundles JGit 4.x and is intended to be used by git plugin 3.x. In the case for your customer, the preferred change is probably to switch them either from git client plugin 3.0.0 to git client plugin2.9.0. You're correct that the JGit project made API breaking changes between JGit 4.x and JGit 5.x. Those API breaking changes required that we "lock-step" release the git plugin 4.x release and the git client plugin 3.x release.I'm not expert enough with the Jenkins class loader or with Java class loading to know if it is possible to have git client plugin 3.x loaded in memory with its bundled copy of JGit 5.x and still have git plugin 3.x cause the loading of JGit 4.x into memory. The git plugin depends on git client and does not declare a dependency on JGit. The git plugin relies on the git client plugin's commitment to always provide a JGit implementation.I think in your case that you want to either downgrade from git client plugin 3.0.0 to git client plugin 2.9.0 or upgrade from git plugin 3.12.0 to git plugin 4.2.2. In terms of functionality change, the downgrade from git client plugin 3.0.0 to git client plugin 2.9.0 is smaller than the change from git plugin 3.12.0 to git plugin 4.2.2. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Mark Waite commented on JENKINS-53004 Re: checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) Oliver Gondža sorry for the confusion caused by not having the same major version number on git client plugin and git plugin releases. Git client 3.x bundles JGit 5.x and is intended to be used by git plugin 4.x and later. Git client 2.x bundles JGit 4.x and is intended to be used by git plugin 3.x. In the case for your customer, the preferred change is probably to switch them either from git client plugin 3.0.0 to git client plugin You're correct that the JGit project made API breaking changes between JGit 4.x and JGit 5.x. Those API breaking changes required that we "lock-step" release the git plugin 4.x release and the git client plugin 3.x release. I'm not expert enough with the Jenkins class loader or with Java class loading to know if it is possible to have git client plugin 3.x loaded in memory with its bundled copy of JGit 5.x and still have git plugin 3.x cause the loading of JGit 4.x into memory. The git plugin depends on git client and does not declare a dependency on JGit. The git plugin relies on the git client plugin's commitment to always provide a JGit implementation. I think in your case that you want to either downgrade from git client plugin 3.0.0 to git client plugin 2.9.0 or upgrade from git plugin 3.12.0 to git plugin 4.2.2. In terms of functionality change, the downgrade from git client plugin 3.0.0 to git client plugin 2.9.0 is smaller than the change from git plugin 3.12.0 to git plugin 4.2.2. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received
[JIRA] (JENKINS-58778) [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Title: Message Title
Christian Ciach commented on JENKINS-58778
Re: [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Maybe we could do something like that as a workaround:
findFiles(glob: 'Build/rpms/*.rpm').each { rpmFile ->
sshPut remote: remote, from: rpmFile.path, into: '/data/mirror/rpm-repo'
}
This feels a bit dirty this probably has negative performance implications, because this establishes a new SSH-connection for each file. It would be great if this plugin could provide a "flatten" parameter for the sshPut-step, like the publish-over-ssh plugin: https://wiki.jenkins.io/display/JENKINS/Publish+Over#PublishOver-Flattenfiles Or, alternatively, allow a wildcard for the "from"-parameter of the sshPut-step, so we could use "Build/rpms/*" instead of "Build/rpms" as the source. The underlying library allow many kinds of "from" parameters (like Iterables), not just Strings. Maybe this jenkins plugin could be modified so that not only Strings are permitted as the "from" parameter? At least maybe allow Iterables, too?
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-58778) [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Title: Message Title
Christian Ciach edited a comment on JENKINS-58778
Re: [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Maybe we could do something like that as a workaround: {code:java}findFiles(glob: 'Build/rpms/*.rpm').each { rpmFile -> sshPut remote: remote, from: rpmFile.path, into: '/data/mirror/rpm-repo'}{code}This feels a bit dirty this probably has negative performance implications, because this establishes a new SSH-connection for each file.It would be great if this plugin could provide a "flatten" parameter for the sshPut-step, like the publish-over-ssh plugin: [https://wiki.jenkins.io/display/JENKINS/Publish+Over#PublishOver-Flattenfiles]Or, alternatively, allow a wildcard for the "from"-parameter of the sshPut-step, so we could use "Build/rpms/*" instead of "Build/rpms" as the source. The underlying library allow many kinds of "from" parameters (like Iterables), not just Strings. Maybe this jenkins plugin could be modified so that not only Strings are permitted as the "from" parameter? At least maybe allow Iterables, too?
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.201087.156473320.12036.1585059300344%40Atlassian.JIRA.
[JIRA] (JENKINS-58778) [ sshPut ] unable to copy only contents inside folder. put always copying full folder
Title: Message Title Christian Ciach commented on JENKINS-58778 Re: [ sshPut ] unable to copy only contents inside folder. put always copying full folder I second this request and I couldn't find a solution for this, too. 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.201087.156473320.12029.1585058640202%40Atlassian.JIRA.
[JIRA] (JENKINS-53004) checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5)
Title: Message Title Oliver Gondža commented on JENKINS-53004 Re: checkout fails due to issue with JGit 5.0.2 (in 3.0.0.beta-5) Mark Waite, we have a customer running into this with git-client 3.0.0 and git-plugin 3.12.0. The way I understand your analysis here is, an older jgit is leaking from some other plugin so git-(client-)plugin built against jgit5 is invoking signatures that was not present in the older version that is leaking in - so the fix is to get all those plugins to versions using more or less same (major) version of jgit. I tend to agree this might be the case have, as my Jenkins has loaded 2 older versions of jgit: $ ls -l /proc/9972/fd/ | grep jgit lr-x--. 1 jenkins jenkins 64 Mar 24 13:30 333 -> /var/lib/jenkins/plugins/git-client/WEB-INF/lib/org.eclipse.jgit.lfs-5.5.1.201910021850-r.jar lr-x--. 1 jenkins jenkins 64 Mar 24 13:30 334 -> /var/lib/jenkins/plugins/git-client/WEB-INF/lib/org.eclipse.jgit.http.apache-5.5.1.201910021850-r.jar lr-x--. 1 jenkins jenkins 64 Mar 24 13:30 337 -> /var/lib/jenkins/plugins/git-client/WEB-INF/lib/org.eclipse.jgit.http.server-5.5.1.201910021850-r.jar lr-x--. 1 jenkins jenkins 64 Mar 24 13:30 338 -> /var/lib/jenkins/plugins/git-client/WEB-INF/lib/org.eclipse.jgit-5.5.1.201910021850-r.jar lr-x--. 1 jenkins jenkins 64 Mar 24 13:30 548 -> /var/lib/jenkins/plugins/blueocean-events/WEB-INF/lib/org.eclipse.jgit-4.5.4.201711221230-r.jar lr-x--. 1 jenkins jenkins 64 Mar 24 13:30 549 -> /var/lib/jenkins/plugins/blueocean-events/WEB-INF/lib/org.eclipse.jgit.http.server-4.5.4.201711221230-r.jar lr-x--. 1 jenkins jenkins 64 Mar 24 13:30 553 -> /var/lib/jenkins/plugins/blueocean-events/WEB-INF/lib/org.eclipse.jgit.http.apache-4.5.4.201711221230-r.jar lr-x--. 1 jenkins jenkins 64 Mar 24 13:30 764 -> /var/lib/jenkins/plugins/gitlab-plugin/WEB-INF/lib/org.eclipse.jgit-3.5.2.201411120430-r.jar However, I was under assumption that Jenkins hierarchical classloading is here to prevent dependencies to leak from plugin to plugin (so in this case, git-plugin would get the version it requires and so will the other plugins). What makes this situation special? Thanks for any pointers! Add Comment
[JIRA] (JENKINS-61666) Outdated/vulnerable dependency (commons-io)
Title: Message Title CloudBees Foundation Security updated an issue Jenkins / JENKINS-61666 Outdated/vulnerable dependency (commons-io) Change By: CloudBees Foundation Security Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205398.1585056833000.12017.1585057620348%40Atlassian.JIRA.
[JIRA] (JENKINS-61635) Kubernetes credentials provider should attempt reconnect on KubernetesClientException's
Title: Message Title Kyle Cronin commented on JENKINS-61635 Re: Kubernetes credentials provider should attempt reconnect on KubernetesClientException's James Nord wow, sorry about all the duplicates. The form said that it failed to submit because of invalid form data so I tried different variations. 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.205344.1584977791000.12014.1585057020052%40Atlassian.JIRA.
[JIRA] (JENKINS-61666) Outdated/vulnerable dependency (commons-io)
Title: Message Title CloudBees Foundation Security created an issue Jenkins / JENKINS-61666 Outdated/vulnerable dependency (commons-io) Issue Type: Bug Assignee: Andrey Stroilov Components: google-oauth-plugin Created: 2020-03-24 13:33 Priority: Minor Reporter: CloudBees Foundation Security The plugin includes a library (commons-io) with a vulnerability. Please update it to 2.6. In addition to that, a second vulnerability is present in 2.6 on the method FileNameUtils.normalize. As the correction is planned for 2.7 but this version is not yet released, please ensure you are not using this method in your code and provide your finding in this ticket. Ticket to follow the second vulnerability: https://issues.apache.org/jira/browse/IO-559 Although the plugin may not use the dependency the way it's exploitable, it's better to avoid the buggy dependency in order to: avoid security reports warning about that avoid future risky uses of the library that may exploit the vulnerability If you like, you can use the bom approach to avoid dealing with the right version, it will take the one used by Jenkins core: https://jenkins.io/doc/developer/plugin-development/dependency-management/ Thank you. by Félix Queiruga
[JIRA] (JENKINS-61665) withAnt - automatically use correct shell
Title: Message Title
Stefan Drissen created an issue
Jenkins / JENKINS-61665
withAnt - automatically use correct shell
Issue Type:
Improvement
Assignee:
Francisco Fernández
Components:
ant-plugin, pipeline
Created:
2020-03-24 13:32
Environment:
Jenkins 2.226
Priority:
Major
Reporter:
Stefan Drissen
The declarative pipeline offers the withAnt build step. Unfortunately this only sets up the Ant environment and then uses a shell (bat / sh) to execute Ant within that environment. While the work-around as documented on https://plugins.jenkins.io/ant/ works:
withAnt(installation: 'myinstall') {
dir("scoring") {
if (isUnix()) {
sh "ant mytarget"
} else {
bat "ant mytarget"
}
}
Needing to detect the operating system for a tool that works on all operating systems is plain clunky and immediately raises the difficulty bar when migrating from freestyle jobs. Freestyle jobs allow you to simply use Ant without you having to worry about which operating system is being used.
[JIRA] (JENKINS-61663) TFS Plugin - Multibranch jobs are not being triggered
Title: Message Title Ricard F updated an issue Jenkins / JENKINS-61663 TFS Plugin - Multibranch jobs are not being triggered Change By: Ricard F Summary: TFS Plugin - Multibranch jobs are not being triggered 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.205395.158505578.12008.1585056360252%40Atlassian.JIRA.
[JIRA] (JENKINS-61664) TFS Plugin - When Build when a change is pushed to TFS/Team Services is checked globally, ALL the jenkins jobs are triggered
Title: Message Title Ricard F updated an issue Jenkins / JENKINS-61664 TFS Plugin - When Build when a change is pushed to TFS/Team Services is checked globally, ALL the jenkins jobs are triggered Change By: Ricard F Summary: TFS Plugin - When Build when a change is pushed to TFS/Team Services is checked globally, ALL the jenkins jobs are triggered 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.205396.1585056275000.12006.1585056360224%40Atlassian.JIRA.
[JIRA] (JENKINS-61664) When Build when a change is pushed to TFS/Team Services is checked globally, ALL the jenkins jobs are triggered
Title: Message Title Ricard F created an issue Jenkins / JENKINS-61664 When Build when a change is pushed to TFS/Team Services is checked globally, ALL the jenkins jobs are triggered Issue Type: Bug Assignee: redsolo Attachments: image-2020-03-24-14-21-57-448.png, image-2020-03-24-14-24-27-218.png Components: tfs-plugin Created: 2020-03-24 13:24 Environment: Jenkins 2.204.1 tfs - 5.157.1 linux + docker Labels: plugin Priority: Major Reporter: Ricard F I configured a jenkins service hooks in DevOps Azure to trigger jobs in Jenkins when a push is done to a repository. I'm using the Devops integration plugin in the Devops Azure configuration. When the option "Build when a change is pushed to TFS/Team Services" is checked globally, ALL the jenkins jobs are triggered when a push is made to andy branch or repository of the configured azure devops collection. The expected behaviour would be that only the ones with the SCM + branch pointing to the repository that receives the push should are triggered.
[JIRA] (JENKINS-52730) Specify build file name
Title: Message Title
Stefan Drissen commented on JENKINS-52730
Re: Specify build file name
Since withAnt only provides the Ant environment to ultimately shell out to ant, you can provide the buildfile with -buildfile on the ant command line:
withAnt( installation: 'Ant' ) {
bat 'ant -buildfile mybuild.xml'
}
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.192622.1532499353000.12002.1585056240208%40Atlassian.JIRA.
[JIRA] (JENKINS-61663) Multibranch jobs are not being triggered
Title: Message Title Ricard F created an issue Jenkins / JENKINS-61663 Multibranch jobs are not being triggered Issue Type: Bug Assignee: redsolo Attachments: image-2020-03-24-14-08-58-171.png, image-2020-03-24-14-14-14-763.png Components: tfs-plugin Created: 2020-03-24 13:16 Environment: Jenkins 2.204.1 tfs - 5.157.1 linux + docker Labels: plugin Priority: Major Reporter: Ricard F I configured a jenkins service hooks in DevOps Azure to trigger jobs in Jenkins when a push is done to a repository. I'm using the Devops integration plugin in the Devops Azure configuration The push does not trigger any multibranch job. The hook is working as non-mutibranch jobs are triggered. The expected behaviour would be to trigger the scan of branches and then trigger the branch which the code has been pushed.
[JIRA] (JENKINS-59971) Unable to create folder credentials for plain-credentials-plugin
Title: Message Title Krystian Marek commented on JENKINS-59971 Re: Unable to create folder credentials for plain-credentials-plugin Hello, Daniel Spilker what makes plain-credentials-plugin incompatible with job-dsl-plugin ? What would be needed to provide a fix for this ? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202775.1572343204000.11994.1585055820356%40Atlassian.JIRA.
[JIRA] (JENKINS-61662) Create credential of type StringCredentials, bound to a folder, via JobDSL plugin
Title: Message Title Krystian Marek commented on JENKINS-61662 Re: Create credential of type StringCredentials, bound to a folder, via JobDSL plugin Duplicate of https://issues.jenkins-ci.org/browse/JENKINS-59971 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.205394.1585055399000.11986.1585055580381%40Atlassian.JIRA.
[JIRA] (JENKINS-61662) Create credential of type StringCredentials, bound to a folder, via JobDSL plugin
Title: Message Title Krystian Marek closed an issue as Duplicate Jenkins / JENKINS-61662 Create credential of type StringCredentials, bound to a folder, via JobDSL plugin Change By: Krystian Marek Status: Open Closed Resolution: Duplicate 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.205394.1585055399000.11991.1585055580460%40Atlassian.JIRA.
[JIRA] (JENKINS-39053) Make shell interpreter configuration configurable per slave
Title: Message Title Arnt Witteveen commented on JENKINS-39053 Re: Make shell interpreter configuration configurable per slave I would rank this more as minor: any Jenkins with a master and slave on different platforms has to go through the trouble of getting the Shell into the path on every machine, because as indicated, the configuration setting for it applies to all machines, and my linux slaves do not understand the path C:\xxx\bash.exe, (and even if they did, they would not have a bash in that location probably...) JENKINS-38211 sounds like the same issue to me. Note that JENKINS-36804 sounds like it's close to this, because there it seems like you can override paths in the node config but not for the master node itself? (or is that bug trying to say it does not work for any node?) 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.175473.1476782678000.11989.1585055580434%40Atlassian.JIRA.
[JIRA] (JENKINS-44532) Rich rich published doesn't show non-stable text on job page
Title: Message Title Hanbing Yu commented on JENKINS-44532 Re: Rich rich published doesn't show non-stable text on job page I encounted the same problem, but it seems most people are not affected by this. Is it possible that this plugin conflicted with some other plugin? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182375.1496024813000.11983.1585055460141%40Atlassian.JIRA.
[JIRA] (JENKINS-61662) Create credential of type StringCredentials, bound to a folder, via JobDSL plugin
Title: Message Title
Krystian Marek created an issue
Jenkins / JENKINS-61662
Create credential of type StringCredentials, bound to a folder, via JobDSL plugin
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin, plain-credentials-plugin
Created:
2020-03-24 13:09
Priority:
Minor
Reporter:
Krystian Marek
https://stackoverflow.com/questions/60830533/create-credential-of-type-stringcredentials-bound-to-a-folder-via-jobdsl-plugi I'm running Jenkins 2.204.5 With plugins:
job-dsl v1.77
credentials 1.7
I'm trying to create a secret of type 'Secret Text' or 'StringCredentialsImpl' bound to a folder, using the JobDSL plugin/code. https://github.com/jenkinsci/plain-credentials-plugin/blob/master/src/main/java/org/jenkinsci/plugins/plaincredentials/impl/StringCredentialsImpl.java But despite the fact that it is mentioned as supported in https://github.com/jenkinsci/job-dsl-plugin/blob/master/job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/parameter/CredentialsParameterContext.groovy#L23 I cant see it in my dynamic viewer JENKINS_URL/plugin/job-dsl/api-viewer/index.html All I see is: {{ credentials { basicSSHUserPrivateKey {} certificateCredentialsImpl {} fileSystemServiceAccountCredential {} // OpenShift do use a dedicated authorization layer on top of Kubernetes and does not allow to access Kubernetes API using plain username/password credentials. openShiftBearerTokenCredentialImpl {} usernamePasswordCredentialsImpl {} }}} This looks like a bug, because the plain-credentials-plugin has the DataBoundConstructor Please take a look.
[JIRA] (JENKINS-59931) Print URL of uploaded resource
Title: Message Title Valentin Chareyre commented on JENKINS-59931 Re: Print URL of uploaded resource Hello Mez Pahlan Thank you for your response. I've been looking through the API docs and there isn't an API that give you want you want unfortunately That's unfortunate Maybe it's something you can ask to the [Microsoft team?|https://docs.microsoft.com/en-us/appcenter/help] Having said that, if you call that release url as a GET request you get a rather large object back that does contain a direct download url. It looks like it doesn't take you to the download page with the information about the build (release notes, hashes, etc) but will allow you to download the file from AppCenter directly. I can see about exposing that as some sort of build status badge or similar. Would you want me to look into that? That would be very nice of you. But don't bother too much. 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-59931) Print URL of uploaded resource
Title: Message Title
Valentin Chareyre edited a comment on JENKINS-59931
Re: Print URL of uploaded resource
Hello [~mezpahlan]Thank you for your response.{quote}_I've been looking through the API docs and there isn't an API that give you want you want unfortunately_{quote}That's unfortunate Maybe it's something you can ask to the [Microsoft team? [](https://docs.microsoft.com/en-us/appcenter/help) |https://docs.microsoft.com/en-us/appcenter/help] {quote}Having said that, if you call that release url as a GET request you get a rather large object back that _does_ contain a direct download url. It looks like it doesn't take you to the download page with the information about the build (release notes, hashes, etc) but will allow you to download the file from AppCenter directly. I can see about exposing that as some sort of build status badge or similar. Would you want me to look into that?{quote} That would be very nice of you. But don't bother too much.
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.202733.1571990313000.11956.1585054200585%40Atlassian.JIRA.
[JIRA] (JENKINS-59931) Print URL of uploaded resource
Title: Message Title
Valentin Chareyre edited a comment on JENKINS-59931
Re: Print URL of uploaded resource
Hello [~mezpahlan]Thank you for your response.{quote}_I've been looking through the API docs and there isn't an API that give you want you want unfortunately_{quote}That's unfortunate Maybe it's something you can ask to the [Microsoft team? | [ ]( https://docs.microsoft.com/en-us/appcenter/help )|https://docs.microsoft.com/en-us/appcenter/help ] ] {quote}Having said that, if you call that release url as a GET request you get a rather large object back that _does_ contain a direct download url. It looks like it doesn't take you to the download page with the information about the build (release notes, hashes, etc) but will allow you to download the file from AppCenter directly. I can see about exposing that as some sort of build status badge or similar. Would you want me to look into that?{quote} That would be very nice of you. But don't bother too much.
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.202733.1571990313000.11953.1585054200377%40Atlassian.JIRA.
[JIRA] (JENKINS-61520) At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error.
Title: Message Title Anda Sorina Laakso commented on JENKINS-61520 Re: At the end of Scheduled Jenkins job execution on UFT15 it is giving JNLP-4 error. Apparently the problem is here: Unable to retrieve test set folder: Node not found. I will check it out. 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.205217.1584601273000.11950.1585053660118%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Valentin Delaye commented on JENKINS-60409 Re: Form Submission Length Cap Jesse Glick Ok thanks Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203466.1575915955000.11903.1585051560677%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-61586 Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1 Change By: John Westcott Status: In Progress Resolved Resolution: Fixed Released As: 0.14.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.205283.1584626324000.11892.1585050780204%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott stopped work on JENKINS-61586 Change By: John Westcott 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.205283.1584626324000.11888.1585050720329%40Atlassian.JIRA.
[JIRA] (JENKINS-61586) Ansible Tower Plugin version 0.10.0 does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott started work on JENKINS-61586 Change By: John Westcott 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.205283.1584626324000.11890.1585050720356%40Atlassian.JIRA.
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Daniel Beck commented on JENKINS-60409 Re: Form Submission Length Cap Valentin Delaye same issue It's not. Note how the error message is completely different. You're looking for JENKINS-61409. 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.203466.1575915955000.11851.1585050060512%40Atlassian.JIRA.
[JIRA] (JENKINS-61655) SAML plugin wrong configuration
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61655 Re: SAML plugin wrong configuration To back to the previous Security realm you need a backup of the JENKINS_HOME/config.xml file, change it and restart Jenkins. If you do not have that file, the only way it is to disable security and configure the security realm again https://jenkins.io/doc/book/system-administration/security/#disabling-security 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.205385.1585025004000.11844.1585048800208%40Atlassian.JIRA.
[JIRA] (JENKINS-61661) Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided
Title: Message Title Andreas Nusser created an issue Jenkins / JENKINS-61661 Better error messages in case of an InvalidCacheLoadException when no Jira credentials are provided Issue Type: Improvement Assignee: Unassigned Components: jira-plugin Created: 2020-03-24 11:18 Environment: Jenkins 2.226 OpenJdk 1.8 CentOS Linux release 7.7.1908 (Core) Installed via YUM Plugins: Jira Plugin 3.0.13 Priority: Minor Reporter: Andreas Nusser When not configuring any credentials but a URL for the Jira Plugin, it still tries to connect to the URL. This results in a lot of InvalidCacheLoadException 2020-03-16 02:22:09.137+ [id=7306028] WARNING h.model.listeners.RunListener#report: RunListener failed com.google.common.cache.CacheLoader$InvalidCacheLoadException: CacheLoader returned null for key UCS-154. at com.google.common.cache.LocalCache$Segment.getAndRecordStats(LocalCache.java:2383) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2351) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at hudson.plugins.jira.JiraSite.getIssue(JiraSite.java:873) at hudson.plugins.jira.JiraJobAction.setAction(JiraJobAction.java:99) at hudson.plugins.jira.JiraJobAction$RunListenerImpl.onStarted(JiraJobAction.java:130) at hudson.plugins.jira.JiraJobAction$RunListenerImpl.onStarted(JiraJobAction.java:122) at
[JIRA] (JENKINS-60409) Form Submission Length Cap
Title: Message Title Valentin Delaye commented on JENKINS-60409 Re: Form Submission Length Cap Hi, I have the same issue on 2.222 (non-LTS) with websocket connection payload. I know the feature is still in beta, but I guess the 2.221. should fix the websocket layer as well. 2020-03-24 09:47:21.616+ [id=219730] INFO j.s.DefaultJnlpSlaveReceiver#channelClosed: Jetty (winstone)-219730 for * terminated: java.nio.channels.ClosedChannelException 2020-03-24 09:47:27.142+ [id=219727] WARNING j.agents.WebSocketAgents$Session#error org.eclipse.jetty.websocket.api.MessageTooLargeException: Binary message size [69632] exceeds maximum size [65536] at org.eclipse.jetty.websocket.api.WebSocketPolicy.assertValidBinaryMessageSize(WebSocketPolicy.java:128) at org.eclipse.jetty.websocket.common.message.SimpleBinaryMessage.appendFrame(SimpleBinaryMessage.java:57) at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.appendMessage(AbstractEventDriver.java:61) at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.onContinuationFrame(AbstractEventDriver.java:183) at org.eclipse.jetty.websocket.common.events.JettyListenerEventDriver.onContinuationFrame(JettyListenerEventDriver.java:255) at org.eclipse.jetty.websocket.common.events.AbstractEventDriver.incomingFrame(AbstractEventDriver.java:155) at org.eclipse.jetty.websocket.common.WebSocketSession.incomingFrame(WebSocketSession.java:322) at org.eclipse.jetty.websocket.common.extensions.ExtensionStack.incomingFrame(ExtensionStack.java:202) at org.eclipse.jetty.websocket.common.Parser.notifyFrame(Parser.java:225) at org.eclipse.jetty.websocket.common.Parser.parseSingleFrame(Parser.java:259) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:460) at org.eclipse.jetty.websocket.common.io.AbstractWebSocketConnection.onFillable(AbstractWebSocketConnection.java:441) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:311) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:103) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:117) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.runTask(EatWhatYouKill.java:336) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:313) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.tryProduce(EatWhatYouKill.java:171) at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:129) at org.eclipse.jetty.util.thread.ReservedThreadExecutor$ReservedThread.run(ReservedThreadExecutor.java:388) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:806) at org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run(QueuedThreadPool.java:938) at java.lang.Thread.run(Thread.java:748) Will try again when the 222.1 is released Thanks
[JIRA] (JENKINS-61588) Failed to convert API response to XML: INVALID_CHARACTER_ERR
Title: Message Title Romain Deldicque commented on JENKINS-61588 Re: Failed to convert API response to XML: INVALID_CHARACTER_ERR Hi, I have exactly the same issue! The script-based authentication is used with a JS script to connect through a Django interface. https://github.com/zaproxy/community-scripts/blob/master/authentication/DjangoAuthentication.js ZAP : 2.8.1 zap-plugin : 1.1.0 jenkins : 2.164.1 I'm going to follow closely the resolution. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205285.1584627511000.11798.1585047120220%40Atlassian.JIRA.
[JIRA] (JENKINS-61655) SAML plugin wrong configuration
Title: Message Title johnny kamel commented on JENKINS-61655 Re: SAML plugin wrong configuration Thank you Ivan Fernandez Calvo attached is the idp metadata, however it is a staging metadata so we might want to disable SAML altogether and revert back to logging in without SAML instead of trying to keep SAML enabled and try to rely on this metadata. I will follow up with the dev team to see if the JENKINS_HOME/saml-idp-metadata.xml is created. With the information you have so far is it possible to know how we can disable the plugin altogether to revert back to jenkins user credentials before we try at a later time to use the SAML plugin? Like you mentioned, the metadata URL may not be correct as provided 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.205385.1585025004000.11793.1585045920104%40Atlassian.JIRA.
[JIRA] (JENKINS-61655) SAML plugin wrong configuration
Title: Message Title johnny kamel updated an issue Jenkins / JENKINS-61655 SAML plugin wrong configuration Change By: johnny kamel Attachment: federationmetadata (3).xml 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.205385.1585025004000.11787.1585045500138%40Atlassian.JIRA.
[JIRA] (JENKINS-46542) External way to set default parameter values for a pipeline job
Title: Message Title
Francesco Pretto edited a comment on JENKINS-46542
Re: External way to set default parameter values for a pipeline job
This issue mentions [EnvInject|https://plugins.jenkins.io/envinject/] and {{pipeline}} in the tags so I expect the poster wants to dynamically modify the the default value of the parameters in a pipeline project, possibly stored as a {{Jenkinsfile}} in CSM, directly in the Jenkins project where it is configured. My tests show that is already possible in a similar way the user [~bentzy] is performing and precisely creating an environment with the EnvInject plugin. Try the example pipeline and setup described in this Stack Overflow [post|https://stackoverflow.com/a/60828812/213871] .
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.184860.1504106931000.11776.1585045140607%40Atlassian.JIRA.
[JIRA] (JENKINS-46542) External way to set default parameter values for a pipeline job
Title: Message Title
Francesco Pretto edited a comment on JENKINS-46542
Re: External way to set default parameter values for a pipeline job
This issue mentions [EnvInject|https://plugins.jenkins.io/envinject/] and {{pipeline}} in the tags so I expect the poster wants to dynamically modify the the default value of the parameters in a pipeline project, possibly stored as a {{Jenkinsfile}} in CSM, directly in the Jenkins project where it is configured. My tests show that is already possible in a similar way the user [~bentzy] is performing and precisely using creating an environment with the EnvInject plugin. Try the example pipeline and setup described in this Stack Overflow [post|https://stackoverflow.com/a/60828812/213871] .
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.184860.1504106931000.11774.1585045140585%40Atlassian.JIRA.
[JIRA] (JENKINS-46542) External way to set default parameter values for a pipeline job
Title: Message Title Francesco Pretto commented on JENKINS-46542 Re: External way to set default parameter values for a pipeline job This issue mentions EnvInject and pipeline in the tags so I expect the poster wants to modify the the default value of the parameters in a pipeline project, possibly stored as a Jenkinsfile in CSM, directly in the Jenkins project where it is configured. My tests show that is already possible in a similar way the user Bentzy Sagiv is performing and precisely using the EnvInject plugin. Try the example pipeline and setup described in this Stack Overflow post . 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.184860.1504106931000.11754.1585045080397%40Atlassian.JIRA.
[JIRA] (JENKINS-61655) SAML plugin wrong configuration
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-61655 Re: SAML plugin wrong configuration Could you please attach the IdP metadata? Can you check if the JENKINS_HOME/saml-ipd-metadata.xml is created? Could you check if the IdP metadata file looks like this one? https://github.com/jenkinsci/saml-plugin/blob/master/doc/TROUBLESHOOTING.md#idp-metadata The error org.pac4j.saml.exceptions.SAMLException: No idp entityId found at suggest me that EntityDescriptor section is not correct, the entityID is not set or it is incorrect. "https://www.w3.org/2001/XMLSchema-instance" xmlns="urn:oasis:names:tc:SAML:2.0:metadata" entityID="https://SAML_SERVER/idp/"> 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.205385.1585025004000.11746.1585044240143%40Atlassian.JIRA.
[JIRA] (JENKINS-61655) SAML plugin wrong configuration
Title: Message Title
Ivan Fernandez Calvo updated an issue
Jenkins / JENKINS-61655
SAML plugin wrong configuration
Change By:
Ivan Fernandez Calvo
Steps: 1- Logged in as admin to jenkins (jenkins.bre.mcd.com)2- Installed SAML plugin 1.1.53- Configured plugin with idP metadata: ([https://gasstg.mcd.com/federationmetadata/2007-06/federationmetadata.xml)] 4- Was logged out of Jenkins and now can't log back in, most likely as was testing the metadata and didn't want it to take effect Full stack trace below, when trying to access jenkins.bre.mcd.com via browserh2. Stack trace {code} org.pac4j.saml.exceptions.SAMLException: No idp entityId found at org.pac4j.saml.metadata.SAML2IdentityProviderMetadataResolver.resolve(SAML2IdentityProviderMetadataResolver.java:107) at org.pac4j.saml.client.SAML2Client.initIdentityProviderMetadataResolver(SAML2Client.java:170) at org.pac4j.saml.client.SAML2Client.internalInit(SAML2Client.java:115) at org.pac4j.core.util.InitializableWebObject.init(InitializableWebObject.java:24) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.createSAML2Client(OpenSAMLWrapper.java:153) at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:45) at org.jenkinsci.plugins.saml.SamlRedirectActionWrapper.process(SamlRedirectActionWrapper.java:30) at org.jenkinsci.plugins.saml.OpenSAMLWrapper.get(OpenSAMLWrapper.java:64) at org.jenkinsci.plugins.saml.SamlSecurityRealm.doCommenceLogin(SamlSecurityRealm.java:257) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) Caused: javax.servlet.ServletException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:797) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$2.doDispatch(MetaClass.java:219) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at
[JIRA] (JENKINS-59090) Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing
Title: Message Title Anda Sorina Laakso commented on JENKINS-59090 Re: Micro Focus UFT Jenkins plugin is marking build status as "FAILURE" even when builds are passing Will you please let me know if the tests runs are working after the upgrade of the plugin? We have a defect opened and I would like to close it soon. 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.201510.1566845071000.11722.1585042260408%40Atlassian.JIRA.
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Félix Queiruga Balado created an issue Jenkins / JENKINS-61660 Lack of spacing between setup wizard form errors Issue Type: Bug Assignee: Unassigned Attachments: Captura de pantalla 2020-03-23 a las 11.10.50.png Components: core Created: 2020-03-24 08:47 Labels: newbie-friendly Priority: Minor Reporter: Félix Queiruga Balado Introduced in 2.217+ I believe. There is no spacing between form errors on the setup wizard, as shown in the picture: There should be at least 0.5rem of spacing between them. Add Comment
