[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title
Ben M commented on JENKINS-60979
Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
IBM has granted me to cite their findings - thanks!
We have traced the modified thread context class loader to a Jenkins class that is explicitly setting a thread context class loader for some of its internal threads, but doing so to a class loader that's inappropriate for thread context operations in Liberty.
The class in question is ClassLoaderSanityThreadFactory, which appears to have been added to Jenkins 2.105 as a fix to the following issue:https://issues.jenkins-ci.org/browse/JENKINS-49206
[…]
The Jenkins thread factory mentioned above does an explicit set of the thread context class loader to its own class loader when it creates a new thread, as follows:
@OverridepublicThreadnewThread(Runnabler) { {{ Thread t = delegate.newThread(r); }} t.setContextClassLoader(ClassLoaderSanityThreadFactory.class.getClassLoader()); return t; } Liberty's thread context management, however, does not intend that application class loaders (the class loaders that would load these classes) be used as a thread context class loader - rather, it has its own ThreadContextClassLoader class that is granted extra visibility to server-level classes intended to be available to thread context class loader operations. Class loads initiated by other class loader types (such as the AppClassLoader) are not able to access packages exported with threadContext visibility, and as in this case, the load fails. The solution would be for Jenkins to either provide a switchable implementation (providing a configuration setting or system property to avoid this thread context class loader swap) or to utilize more robust logic in deciding whether to change the thread context class loader - for example, rather than immediately switching the thread context class loader to the current class' loader, it could first check to see if the existing thread context class loader can successfully load it (if it can, then that loader is adequate).
I traced the underlying issue back to the solution of another issue I had, where IBM JVM engineers found a difference between the CommonThreadPool-Implementations of Java 8 and Java 11. I shortened it a bit as well. I created threads using CompletableFuture.supplyAsync(), but I think the behaviour is the very same.
By specifying the ManagedExecutorService, you are using Libertys EE DefaultContextService, which will propagate the application classloader context
We (WAS L3: EEConcurrency) can confirm that ManagedExecutorService by default propagates the thread context class loader of the submitter thread to the task/action that is submitted to it. With CompletableFuture.supplyAsync(supplier, executor), the submitter is actually the JDK's CompletableFuture.supplyAsync implementation, which is understood to delegate to executor.execute from within the supplyAsync method, meaning that if the application invoked supplyAsync, its thread context class loader is put onto the thread that runs the Su
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title
Ben M edited a comment on JENKINS-60979
Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
IBM has granted me to cite their findings - thanks! {quote}We have traced the modified thread context class loader to a Jenkins class that is explicitly setting a thread context class loader for some of its internal threads, but doing so to a class loader that's inappropriate for thread context operations in Liberty. The class in question is ClassLoaderSanityThreadFactory, which appears to have been added to Jenkins 2.105 as a fix to the following issue:https://issues.jenkins-ci.org/browse/JENKINS-49206 […]The Jenkins thread factory mentioned above does an explicit set of the thread context class loader to its own class loader when it creates a new thread, as follows: { { code:java} @OverridepublicThreadnewThread(Runnabler) { }} {{ Thread t = delegate.newThread(r); }} {{ t.setContextClassLoader(ClassLoaderSanityThreadFactory.class.getClassLoader()); }} {{ return t; }} } { { code } }} Liberty's thread context management, however, does not intend that application class loaders (the class loaders that would load these classes) be used as a thread context class loader - rather, it has its own ThreadContextClassLoader class that is granted extra visibility to server-level classes intended to be available to thread context class loader operations. Class loads initiated by other class loader types (such as the AppClassLoader) are not able to access packages exported with threadContext visibility, and as in this case, the load fails. The solution would be for Jenkins to either provide a switchable implementation (providing a configuration setting or system property to avoid this thread context class loader swap) or to utilize more robust logic in deciding whether to change the thread context class loader - for example, rather than immediately switching the thread context class loader to the current class' loader, it could first check to see if the existing thread context class loader can successfully load it (if it can, then that loader is adequate).{quote} I traced the underlying issue back to the solution of another issue I had, where IBM JVM engineers found a difference between the CommonThreadPool-Implementations of Java 8 and Java 11. I shortened it a bit as well. I created threads using {{CompletableFuture.supplyAsync()}}, but I think the behaviour is the very same.{quote}By specifying the ManagedExecutorService, you are using Libertys EE DefaultContextService, which will propagate the application classloader contextWe (WAS L3: EEConcurrency) can confirm that ManagedExecutorService by default propagates the thread context class loader of the submitter thread to the task/action that is submitted to it. With CompletableFuture.supplyAsync(supplier, executor), the submitter is actually the JDK's CompletableFuture.supplyAsync implementation, which is understood to delegate to executor.execute from within the supplyAsync method, meaning that if the application invoked supplyAsync, its thread context class loader is put onto the thread that runs the Supplier action. This seems like a reasonable way to ensure the application's thread context class loader is used. When CompletableFuture.supplyAsync(supplier) is used without specifying any executor parameter, the supplier is documented, see [https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html#supplyAsync-java.util.function.Supplier-]to run on ForkJoinPool.commonPool() which is provided by the JDK, which is outside the control of EE Concurrency, and outside the control of Liberty as well
[JIRA] (JENKINS-60979) Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
Title: Message Title
Ben M edited a comment on JENKINS-60979
Re: Installation of Plugin fails on LibertyProfile due using the wrong SocketFactory
IBM has granted me to cite their findings - thanks! {quote}We have traced the modified thread context class loader to a Jenkins class that is explicitly setting a thread context class loader for some of its internal threads, but doing so to a class loader that's inappropriate for thread context operations in Liberty.The class in question is ClassLoaderSanityThreadFactory, which appears to have been added to Jenkins 2.105 as a fix to the following issue:https://issues.jenkins-ci.org/browse/JENKINS-49206 […]The Jenkins thread factory mentioned above does an explicit set of the thread context class loader to its own class loader when it creates a new thread, as follows:{code:java}@ OverridepublicThreadnewThread Overridepublic Thread newThread (Runnabler) { Thread t = delegate.newThread(r); }} t.setContextClassLoader(ClassLoaderSanityThreadFactory.class.getClassLoader()); return t;}{code} Liberty's thread context management, however, does not intend that application class loaders (the class loaders that would load these classes) be used as a thread context class loader - rather, it has its own ThreadContextClassLoader class that is granted extra visibility to server-level classes intended to be available to thread context class loader operations. Class loads initiated by other class loader types (such as the AppClassLoader) are not able to access packages exported with threadContext visibility, and as in this case, the load fails. The solution would be for Jenkins to either provide a switchable implementation (providing a configuration setting or system property to avoid this thread context class loader swap) or to utilize more robust logic in deciding whether to change the thread context class loader - for example, rather than immediately switching the thread context class loader to the current class' loader, it could first check to see if the existing thread context class loader can successfully load it (if it can, then that loader is adequate).{quote} I traced the underlying issue back to the solution of another issue I had, where IBM JVM engineers found a difference between the CommonThreadPool-Implementations of Java 8 and Java 11. I shortened it a bit as well. I created threads using {{CompletableFuture.supplyAsync()}}, but I think the behaviour is the very same.{quote}By specifying the ManagedExecutorService, you are using Libertys EE DefaultContextService, which will propagate the application classloader contextWe (WAS L3: EEConcurrency) can confirm that ManagedExecutorService by default propagates the thread context class loader of the submitter thread to the task/action that is submitted to it. With CompletableFuture.supplyAsync(supplier, executor), the submitter is actually the JDK's CompletableFuture.supplyAsync implementation, which is understood to delegate to executor.execute from within the supplyAsync method, meaning that if the application invoked supplyAsync, its thread context class loader is put onto the thread that runs the Supplier action. This seems like a reasonable way to ensure the application's thread context class loader is used. When CompletableFuture.supplyAsync(supplier) is used without specifying any executor parameter, the supplier is documented, see [https://docs.oracle.com/javase/8/docs/api/java/util/concurrent/CompletableFuture.html#supplyAsync-java.util.function.Supplier-]to run on ForkJoinPool.commonPool() which is provided by the JDK, which is outside the control of EE Concurrency, and outside the control of Liberty as well. Questions a
[JIRA] (JENKINS-61665) withAnt - automatically use correct shell
Title: Message Title Francisco Fernández assigned an issue to Unassigned Jenkins / JENKINS-61665 withAnt - automatically use correct shell Change By: Francisco Fernández Assignee: Francisco Fernández 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.205397.158505676.12506.1585122060254%40Atlassian.JIRA.
[JIRA] (JENKINS-48162) QUERY via REST API
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-48162 QUERY via REST API Change By: Oleg Nenashev Labels: REST newbie-friendly 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.186729.1511351618000.12509.1585123080601%40Atlassian.JIRA.
[JIRA] (JENKINS-55262) Missing content-type on serverStatuses REST API
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-55262 Missing content-type on serverStatuses REST API Change By: Oleg Nenashev Labels: newbie-friendly rest 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.196345.154522933.12517.1585123080760%40Atlassian.JIRA.
[JIRA] (JENKINS-26795) Configuration methods are not exported in REST API
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-26795 Configuration methods are not exported in REST API Change By: Oleg Nenashev Labels: REST newbie-friendly 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.160566.1423105365000.12513.1585123080651%40Atlassian.JIRA.
[JIRA] (JENKINS-15624) Rest API for view manipulation
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-15624 Rest API for view manipulation Change By: Oleg Nenashev Labels: REST newbie-friendly 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.146380.1351153786000.12511.1585123080627%40Atlassian.JIRA.
[JIRA] (JENKINS-20451) Add Copy Artefacts info to the xml Rest API
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-20451 Add Copy Artefacts info to the xml Rest API Change By: Oleg Nenashev Labels: REST newbie-friendly 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.151972.138376427.12519.1585123140221%40Atlassian.JIRA.
[JIRA] (JENKINS-33163) Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin
Title: Message Title Philip Aston commented on JENKINS-33163 Re: Add option "Use Upstream Project revision" similar to that on the legacy perforce plugin Thanks Karl Wirth. I've upgraded the plugin again; I'll send you the logs when I see the next failure. 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.168534.1456438321000.12541.1585124520352%40Atlassian.JIRA.
[JIRA] (JENKINS-46625) IOException with docker.image().inside
Title: Message Title Chris Maes commented on JENKINS-46625 Re: IOException with docker.image().inside Similar issue here. Also a big image (6.18G) with many layers (105). The problem is this works most of the time, but errors like these pop up when the host is more heavily loaded (the same image is being started multiple times in parallel at the exact same time) 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.184959.1504473315000.12548.1585125120215%40Atlassian.JIRA.
[JIRA] (JENKINS-61479) java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date
Title: Message Title Oleg Nenashev started work on JENKINS-61479 Change By: Oleg Nenashev Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205163.1584190858000.12562.1585125720288%40Atlassian.JIRA.
[JIRA] (JENKINS-61479) java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61479 java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date Change By: Oleg Nenashev Labels: fingerprints lts-candidate 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.205163.1584190858000.12560.1585125720241%40Atlassian.JIRA.
[JIRA] (JENKINS-61479) java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date
Title: Message Title Oleg Nenashev updated JENKINS-61479 Jenkins / JENKINS-61479 java.lang.ClassCastException: java.lang.Long cannot be cast to java.util.Date Change By: Oleg Nenashev Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205163.1584190858000.12564.1585125780389%40Atlassian.JIRA.
[JIRA] (JENKINS-50211) Add an option to optionally reject connections from agents with unsupported Remoting versions
Title: Message Title Sumit Sarin started work on JENKINS-50211 Change By: Sumit Sarin 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.189234.1521190142000.12573.1585125840377%40Atlassian.JIRA.
[JIRA] (JENKINS-61677) Mark PR as Needs Work when build fails
Title: Message Title Ilya Vassilevsky created an issue Jenkins / JENKINS-61677 Mark PR as Needs Work when build fails Issue Type: New Feature Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-03-25 08:52 Priority: Minor Reporter: Ilya Vassilevsky Seeing build status is certainly nice, but getting the PR marked as Needs Work is more actionable. The author will also get notified by email. Add Comment This message was sent by Atlassian Jira (v7.13.12#7
[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, well I think I've found the problem, it seems to be related to a space problem I was using in script and that's not supported by XML. I'll put a link to the part that talks about it. Ghlf! https://stackoverflow.com/questions/22440902/i-keep-getting-error-while-trying-to-create-an-xml-file 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.12590.1585127400158%40Atlassian.JIRA.
[JIRA] (JENKINS-61588) Failed to convert API response to XML: INVALID_CHARACTER_ERR
Title: Message Title Romain Deldicque started work on JENKINS-61588 Change By: Romain Deldicque 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.205285.1584627511000.12593.1585127460512%40Atlassian.JIRA.
[JIRA] (JENKINS-61588) Failed to convert API response to XML: INVALID_CHARACTER_ERR
Title: Message Title Romain Deldicque stopped work on JENKINS-61588 Change By: Romain Deldicque 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.205285.1584627511000.12596.1585127460689%40Atlassian.JIRA.
[JIRA] (JENKINS-61678) bitbucket build status notifier stopped working
Title: Message Title
Alon Hoftman created an issue
Jenkins / JENKINS-61678
bitbucket build status notifier stopped working
Issue Type:
Bug
Assignee:
Antonio Mansilla
Attachments:
b1.JPG, b2.JPG
Components:
bitbucket-build-status-notifier-plugin
Created:
2020-03-25 09:59
Labels:
plugin bitbucket
Priority:
Major
Reporter:
Alon Hoftman
we are using Bitbucket and Jenkins, we have a webhook that starts a Jenkins Job each time a Pull Request is created on bitbucket. Jenkins updates bitbucket back on the build state/status (success, failure or in progress), we use a Jenkins Plugin called bitbucketStatusNotifier. the integration was working perfect till recently it stopped working.
The credentials we use remained the same
We use the standard syntax of the Plugin commands: bitbucketStatusNotify(buildState: 'INPROGRESS' )
bitbucketStatusNotify(buildState: 'SUCCESSFUL', repoSlug: "${Trigger_Repo.split(" /")[1]}", commitId: "${Trigger_Revision}") Please advise
[JIRA] (JENKINS-61550) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Olivier Vernin assigned an issue to Mark Waite Jenkins / JENKINS-61550 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Olivier Vernin Assignee: Olivier Vernin 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.12650.1585130700345%40Atlassian.JIRA.
[JIRA] (JENKINS-61550) Parameter is not interpreted in GIT Plugin - Branch Specifier
Title: Message Title Olivier Vernin assigned an issue to Olivier Vernin Jenkins / JENKINS-61550 Parameter is not interpreted in GIT Plugin - Branch Specifier Change By: Olivier Vernin Assignee: Mark Waite Olivier Vernin 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.12647.1585130700304%40Atlassian.JIRA.
[JIRA] (JENKINS-34081) Source code checkout with multiple locations not working
Title: Message Title Joachim Mairböck commented on JENKINS-34081 Re: Source code checkout with multiple locations not working You can use "local module directory" to ensure that both parts go into different subdirectories of the workspace. 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.169585.1460025082000.12652.1585132020292%40Atlassian.JIRA.
[JIRA] (JENKINS-61679) Support for atlassian-bitbucket-server-integration
Title: Message Title Stefan Drzazga created an issue Jenkins / JENKINS-61679 Support for atlassian-bitbucket-server-integration Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2020-03-25 10:55 Environment: jenkins v2.204.5, atlassian-bitbucket-server-integration v1.1.0, job-dsl v1.77 Priority: Minor Reporter: Stefan Drzazga Please support dsl for the atlassian-bitbucket-server-integration plugin. https://plugins.jenkins.io/atlassian-bitbucket-server-integration/ Thanks in advance! Add Comment
[JIRA] (JENKINS-61680) Setting the repository browser is not possible using SubversionSCMSource
Title: Message Title Joachim Mairböck created an issue Jenkins / JENKINS-61680 Setting the repository browser is not possible using SubversionSCMSource Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: subversion-plugin Created: 2020-03-25 10:57 Priority: Trivial Reporter: Joachim Mairböck When using SubversionSCMSource (e.g. with a multibranch pipeline) instead of the classic SCM configuration (which is used by free style jobs), there is no way to configure the repository browser in Jenkins. Add Comment
[JIRA] (JENKINS-61680) Setting the repository browser is not possible using SubversionSCMSource
Title: Message Title Joachim Mairböck commented on JENKINS-61680 Re: Setting the repository browser is not possible using SubversionSCMSource Somewhat related: the checkout strategy can't be specified also (see JENKINS-41850). 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.205417.158513387.12660.1585134180130%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
Call to `/rest/api/1.0/projects/{PROJECT}/repos/{REPO}/pull-requests/19/diff` causes `/from` to appear
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.12662.1585134660146%40Atlassian.JIRA.
[JIRA] (JENKINS-61680) Setting the repository browser is not possible using SubversionSCMSource
Title: Message Title Ivan Fernandez Calvo assigned an issue to Unassigned Jenkins / JENKINS-61680 Setting the repository browser is not possible using SubversionSCMSource Change By: Ivan Fernandez Calvo Assignee: Ivan Fernandez Calvo 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.205417.158513387.12664.1585134720211%40Atlassian.JIRA.
[JIRA] (JENKINS-41850) Multibranch workflow and 'scm checkout' don't allow Svn clean before checkout
Title: Message Title Joachim Mairböck commented on JENKINS-41850 Re: Multibranch workflow and 'scm checkout' don't allow Svn clean before checkout Apparently, there is a workaround for this, by setting the WorkspaceUpdater in the Jenkinsfile: https://claasd.blogspot.com/2019/01/jenkins-how-to-use-svn-checkout.html However, this doesn't help when using the (deprecated) Multibranch Freestyle Job 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.178698.1486570799000.12666.1585134780409%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
Does Bitbucket Server ensure that the "refs/pull-requests/{id}/from" ref appears (or is updated) immediately after the diff request, or can there be a delay sometimes?
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.12675.1585135020215%40Atlassian.JIRA.
[JIRA] (JENKINS-61680) Setting the repository browser is not possible using SubversionSCMSource
Title: Message Title Joachim Mairböck commented on JENKINS-61680 Re: Setting the repository browser is not possible using SubversionSCMSource The workaround which I linked to in https://issues.jenkins-ci.org/browse/JENKINS-41850?focusedCommentId=387864&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-387864 also doesn't work here, because the RepositoryBrowser can't be set in SubversionSCM. 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.205417.158513387.12677.1585135080047%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 I'm checking manually, so no way to track the time between that. I've created a pull request, did ls-remove, made API call using Postman and re-did ls-remote to verify it appeared 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.12679.1585135140087%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 I want to try HEAD instead of GET request next time 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.12681.1585135200126%40Atlassian.JIRA.
[JIRA] (JENKINS-61681) kubernetes-plugin pod was marked offline
Title: Message Title Hokwang Lee created an issue Jenkins / JENKINS-61681 kubernetes-plugin pod was marked offline Issue Type: Bug Assignee: Unassigned Components: kubernetes-plugin Created: 2020-03-25 11:53 Priority: Critical Reporter: Hokwang Lee Hello. I expirenced error few days ago. jenkins : 2.204.5 (lts) kubernetes-plugin : 1.24.1 (latest) durable-task : 1.34 (latest) 12:03:50 job-828-v3tgl-qlflv-7xswl was marked offline: Connection was broken: java.nio.channels.ClosedChannelException 12:03:50 at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) 12:03:50 at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:142) 12:03:50 at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:795) 12:03:50 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) 12:03:50 at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) 12:03:50 at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) 12:03:50 at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) 12:03:50 at java.base/java.lang.Thread.run(Thread.java:834)
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title
Dawid Malinowski created an issue
Jenkins / JENKINS-61682
Allow to configure additional pipeline workflow task description
Issue Type:
New Feature
Assignee:
Dawid Malinowski
Components:
delivery-pipeline-plugin
Created:
2020-03-25 11:56
Priority:
Minor
Reporter:
Dawid Malinowski
I'm working on new feature which will allow to configure additional pipeline workflow task description similar as we had in regular pipeline view. Syntax would looks like this:
node {
stage('A') {
task(name: 'AA', description: 'foo') {
echo "Sparking the Big Bang..."
}
}
stage('B') {
task(name: 'BB', description: 'bar') {
echo "Cosmic inflation begins..."
}
}
}
Add Comment
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski updated an issue Jenkins / JENKINS-61682 Allow to configure additional pipeline workflow task description Change By: Dawid Malinowski Attachment: Screenshot 2020-03-25 at 12.57.27.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205419.1585137365000.12691.1585137480080%40Atlassian.JIRA.
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski commented on JENKINS-61682 Re: Allow to configure additional pipeline workflow task description 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.205419.1585137365000.12692.1585137480156%40Atlassian.JIRA.
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title
Dawid Malinowski updated an issue
Jenkins / JENKINS-61682
Allow to configure additional pipeline workflow task description
Change By:
Dawid Malinowski
I'm working on new feature which will allow to configure additional pipeline workflow task description similar as we had in regular pipeline view.Syntax would looks like this:{code}node { stage('A') { task(name: 'AA', description: 'foo') { echo "Sparking the Big Bang..." } } stage('B') { task(name: 'BB', description: 'bar') {echo "Cosmic inflation begins..." } }}{code} Task with single parameter will still be supported:{code}node { stage('A') { task('AA') { echo "Sparking the Big Bang..." } } stage('B') { task('BB') {echo "Cosmic inflation begins..." } }}{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" gr
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski updated an issue Jenkins / JENKINS-61682 Allow to configure additional pipeline workflow task description Change By: Dawid Malinowski Comment: !Screenshot 2020-03-25 at 12.57.27.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205419.1585137365000.12703.1585137660696%40Atlassian.JIRA.
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title
Dawid Malinowski updated an issue
Jenkins / JENKINS-61682
Allow to configure additional pipeline workflow task description
Change By:
Dawid Malinowski
I'm working on new feature which will allow to configure additional pipeline workflow task description similar as we had in regular pipeline view.Syntax would looks like this:{code}node { stage('A') { task(name: 'AA', description: 'foo') { echo "Sparking the Big Bang..." } } stage('B') { task(name: 'BB', description: 'bar') {echo "Cosmic inflation begins..." } }}{code}Visualisation will looks like this: !Screenshot 2020-03-25 at 12.57.27.png|thumbnail!Task with single parameter will still be supported:{code}node { stage('A') { task('AA') { echo "Sparking the Big Bang..." } } stage('B') { task('BB') {echo "Cosmic inflation begins..." } }}{code}
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title
Dawid Malinowski updated an issue
Jenkins / JENKINS-61682
Allow to configure additional pipeline workflow task description
Change By:
Dawid Malinowski
I'm working on new feature which will allow to configure additional pipeline workflow task description similar as we had in regular pipeline view.Syntax would looks like this:{code}node { stage('A') { task(name: 'AA', description: 'foo') { echo "Sparking the Big Bang..." } } stage('B') { task(name: 'BB', description: 'bar') {echo "Cosmic inflation begins..." } }}{code} Visualisation will looks like this: Task with single parameter will still be supported:{code}node { stage('A') { task('AA') { echo "Sparking the Big Bang..." } } stage('B') { task('BB') {echo "Cosmic inflation begins..." } }}{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 t
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title
Dawid Malinowski updated an issue
Jenkins / JENKINS-61682
Allow to configure additional pipeline workflow task description
Change By:
Dawid Malinowski
I'm working on new feature which will allow to configure additional pipeline workflow task description similar as we had in regular pipeline view.Syntax would looks like this:{code}node { stage('A') { task(name: 'AA', description: 'foo') { echo "Sparking the Big Bang..." } } stage('B') { task(name: 'BB', description: 'bar') {echo "Cosmic inflation begins..." } }}{code}Visualisation will looks like this: !Screenshot 2020-03-25 at 12.57.27.png|thumbnail! Task with single parameter will still be supported:{code}node { stage('A') { task('AA') { echo "Sparking the Big Bang..." } } stage('B') { task('BB') {echo "Cosmic inflation begins..." } }}{code} Similarly we can disable description appearance form edit view page. !Screenshot 2020-03-25 at 13.01.03.png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski updated an issue Jenkins / JENKINS-61682 Allow to configure additional pipeline workflow task description Change By: Dawid Malinowski Attachment: Screenshot 2020-03-25 at 13.01.03.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205419.1585137365000.12711.1585137780098%40Atlassian.JIRA.
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title
Dawid Malinowski updated an issue
Jenkins / JENKINS-61682
Allow to configure additional pipeline workflow task description
Change By:
Dawid Malinowski
I'm working on new feature which will allow to configure additional pipeline workflow task description similar as we had in regular pipeline view.Syntax would looks like this:{code}node { stage('A') { task(name: 'AA', description: 'foo') { echo "Sparking the Big Bang..." } } stage('B') { task(name: 'BB', description: 'bar') {echo "Cosmic inflation begins..." } }}{code}Visualisation will looks like this: !Screenshot 2020-03-25 at 12.57.27.png|thumbnail! Task with single parameter will still be supported:{code}node { stage('A') { task('AA') { echo "Sparking the Big Bang..." } } stage('B') { task('BB') {echo "Cosmic inflation begins..." } }}{code}Similarly we can disable description appearance form edit view page. !Screenshot 2020-03-25 at 13 12 . 01 57 . 27.png|thumbnail! !Screenshot 2020- 03 -25 at 13 . 03.23. png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski updated an issue Jenkins / JENKINS-61682 Allow to configure additional pipeline workflow task description Change By: Dawid Malinowski Attachment: Screenshot 2020-03-25 at 13.01.03.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205419.1585137365000.12713.1585137840128%40Atlassian.JIRA.
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski updated an issue Jenkins / JENKINS-61682 Allow to configure additional pipeline workflow task description Change By: Dawid Malinowski Attachment: Screenshot 2020-03-25 at 13.03.23.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205419.1585137365000.12714.1585137840179%40Atlassian.JIRA.
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title
Dawid Malinowski updated an issue
Jenkins / JENKINS-61682
Allow to configure additional pipeline workflow task description
Change By:
Dawid Malinowski
I'm working on new feature which will allow to configure additional pipeline workflow task description similar as we had in regular pipeline view.Syntax would looks like this:{code}node { stage('A') { task(name: 'AA', description: 'foo') { echo "Sparking the Big Bang..." } } stage('B') { task(name: 'BB', description: 'bar') {echo "Cosmic inflation begins..." } }}{code}Visualisation will looks like this: !Screenshot 2020-03-25 at 12.57.27.png|thumbnail! Task with single parameter will still be supported:{code}node { stage('A') { task('AA') { echo "Sparking the Big Bang..." } } stage('B') { task('BB') {echo "Cosmic inflation begins..." } }}{code}Similarly we can disable description appearance form edit view page. !Screenshot 2020-03-25 at 12.57.27.png|thumbnail! !Screenshot 2020-03-25 at 13.03.23.png|thumbnail!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61683) Add GitLab variables to environment
Title: Message Title Vincent Letarouilly created an issue Jenkins / JENKINS-61683 Add GitLab variables to environment Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2020-03-25 12:20 Environment: Jenkins 2.227 gitlab-branch-source-plugin 1.4.4 Labels: plugin environment-variables gitlab Priority: Minor Reporter: Vincent Letarouilly A great addition would be to have GitLab Webhook information available as environment variable such as: `object_kind` -> `GITLAB_OBJECT_KIND` `projectId` -> `GITLAB_PROJECT_ID` This would allow us to do different things in our scripted pipelines depending on the type of event. An easier solution would be to provide just one env variable like `GITLAB_BRANCH_TYPE` that could be either `NORMAL` / `CHANGE_REQUEST` / `TAG` While we do not plan to use `projectId` at the moment, I still think it could benefit other users of the plugin.
[JIRA] (JENKINS-42322) Docker rm/stop/... commands killed by the timeout, failing builds
Title: Message Title Chris Maes commented on JENKINS-42322 Re: Docker rm/stop/... commands killed by the timeout, failing builds Jesse Glick: thanks for the hint, this seems to help. We now have one timeout with 280 seconds... You say around 300 and more will probably not work. Has this been verified? What kind of error or so would you expect if we put a value above 300? 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.179221.1488050966000.12732.1585139221019%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 I would recommend doing the "fromRef" thing instead of testing which REST requests update "refs/pull-requests/*/from" as an undocumented side effect. 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.12780.1585139640123%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 That sounds much better, yet I'm not sure I'm qualified enough to make such PR Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205179.1584360231000.12783.1585139760129%40Atlassian.JIRA.
[JIRA] (JENKINS-61667) Plugin Adoption Request - docker-java-api-plugin
Title: Message Title Nicolas De Loof commented on JENKINS-61667 Re: Plugin Adoption Request - docker-java-api-plugin Go for 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.205399.1585066141000.12787.1585140120339%40Atlassian.JIRA.
[JIRA] (JENKINS-61667) Plugin Adoption Request - docker-java-api-plugin
Title: Message Title Nicolas De Loof assigned an issue to Unassigned Jenkins / JENKINS-61667 Plugin Adoption Request - docker-java-api-plugin Change By: Nicolas De Loof Assignee: Nicolas De Loof 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.205399.1585066141000.12785.1585140120308%40Atlassian.JIRA.
[JIRA] (JENKINS-61683) Add GitLab variables to environment
Title: Message Title
Vincent Letarouilly updated an issue
Jenkins / JENKINS-61683
Add GitLab variables to environment
Change By:
Vincent Letarouilly
A great addition would be to have GitLab Webhook information available as environment variable such as:* {{object_kind}} -> {{GITLAB_OBJECT_KIND}}* {{projectId}} -> {{GITLAB_PROJECT_ID}}This would allow us to do different things in our scripted pipelines depending on the type of event.An easier solution would be to provide just one env variable like {{GITLAB_BRANCH_TYPE}} that could be either {{NORMAL}} / {{CHANGE_REQUEST}} / {{TAG}}While we do not plan to use ` {{ projectId ` }} at the moment, I still think it could benefit other users of the plugin.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To
[JIRA] (JENKINS-61683) Add GitLab variables to environment
Title: Message Title
Vincent Letarouilly updated an issue
Jenkins / JENKINS-61683
Add GitLab variables to environment
Change By:
Vincent Letarouilly
A great addition would be to have GitLab Webhook information available as environment variable such as:* ` {{ object_kind ` }} -> ` {{ GITLAB_OBJECT_KIND ` }} * ` {{ projectId ` }} -> ` {{ GITLAB_PROJECT_ID ` }} This would allow us to do different things in our scripted pipelines depending on the type of event.An easier solution would be to provide just one env variable like ` {{ GITLAB_BRANCH_TYPE ` }} that could be either ` {{ NORMAL ` }} / ` {{ CHANGE_REQUEST ` }} / ` {{ TAG ` }} While we do not plan to use `projectId` at the moment, I still think it could benefit other users of the plugin.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send a
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski started work on JENKINS-61682 Change By: Dawid Malinowski 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.205419.1585137365000.12799.1585140420081%40Atlassian.JIRA.
[JIRA] (JENKINS-61673) Status of the task is not marked properly
Title: Message Title Dawid Malinowski commented on JENKINS-61673 Re: Status of the task is not marked properly https://github.com/Diabol/delivery-pipeline-plugin/pull/311 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.12806.1585140480450%40Atlassian.JIRA.
[JIRA] (JENKINS-61673) Status of the task is not marked properly
Title: Message Title Dawid Malinowski started work on JENKINS-61673 Change By: Dawid Malinowski 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.205408.1585089668000.12800.1585140480310%40Atlassian.JIRA.
[JIRA] (JENKINS-61673) Status of the task is not marked properly
Title: Message Title Dawid Malinowski updated JENKINS-61673 Jenkins / JENKINS-61673 Status of the task is not marked properly Change By: Dawid Malinowski 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.205408.1585089668000.12813.1585140540340%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 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. I usually see this when task is marked unstable. 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.12812.1585140540325%40Atlassian.JIRA.
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski commented on JENKINS-61682 Re: Allow to configure additional pipeline workflow task description https://github.com/Diabol/delivery-pipeline-plugin/pull/312 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.205419.1585137365000.12814.1585140660120%40Atlassian.JIRA.
[JIRA] (JENKINS-61682) Allow to configure additional pipeline workflow task description
Title: Message Title Dawid Malinowski updated JENKINS-61682 Jenkins / JENKINS-61682 Allow to configure additional pipeline workflow task description Change By: Dawid Malinowski 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.205419.1585137365000.12815.1585140660149%40Atlassian.JIRA.
[JIRA] (JENKINS-11108) Git plugin doesn't track changes between two tags
Title: Message Title Morgan Christiansson commented on JENKINS-11108 Re: Git plugin doesn't track changes between two tags This is still an issue. Also affecting GIT_PREVIOUS_COMMIT as reported in JENKINS-45900 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.141327.1316818716000.12873.1585141440203%40Atlassian.JIRA.
[JIRA] (JENKINS-45900) GIT_PREVIOUS_(SUCCESSFUL_)?COMMIT is not set when the it's tag that is checkouted
Title: Message Title Morgan Christiansson edited a comment on JENKINS-45900 Re: GIT_PREVIOUS_(SUCCESSFUL_)?COMMIT is not set when the it's tag that is checkouted This seems to still be an issue. I am unable to get changelogs working when deploying tags because I can find no way to get commit of previous build.It's most likely this line in the code: [ https://github.com/jenkinsci/git-plugin/blob/942de7ac00272c0bbad625a811a17e66713014b8/src/main/java/hudson/plugins/git/GitSCM.java#L1346 ]Also affecting build changelogs as reported in JENKINS-11108 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.184120.1501579093000.12878.1585141500272%40Atlassian.JIRA.
[JIRA] (JENKINS-45386) Validating String Parameter does not render HTML in parameter description
Title: Message Title ASHOK MOHANTY commented on JENKINS-45386 Re: Validating String Parameter does not render HTML in parameter description I am planning to go for plugin v.2.4 with Jenkins 2.164.3, so I am not going to hit this issue (am I right )!! One observation (doubt) - https://plugins.jenkins.io/validating-string-parameter/ shows V.2.4 as TBD. Is not stable OR just typo !? 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.183549.1499602291000.12896.1585144740207%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Usama Tariq commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi, If anybody get a fix of Jira Trigger Plugin, Please share the solution. Amrut dengre It's a fix at plugin side. 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.201336.1566200967000.12902.1585144980315%40Atlassian.JIRA.
[JIRA] (JENKINS-54248) readJSON exposes text data, which could contain secured things
Title: Message Title Vlad Fedosv commented on JENKINS-54248 Re: readJSON exposes text data, which could contain secured things Same issue here, in BlueOcean Jenkins ver. 2.204.5 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194890.1540466393000.12912.1585145100230%40Atlassian.JIRA.
[JIRA] (JENKINS-58987) issue_updated trigger handler can't find "name" field in JSON
Title: Message Title Amrut dengre commented on JENKINS-58987 Re: issue_updated trigger handler can't find "name" field in JSON Hi Usama Tariq, Yes. It seems so. Not sure when this would be fixed. Will comment here in case I found a solution for this. Please comment if you found any. 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.201336.1566200967000.12920.1585145160394%40Atlassian.JIRA.
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite created an issue Jenkins / JENKINS-61684 Git client plugin automated tests fail with MinGit on Windows Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2020-03-25 14:34 Environment: ci.jenkins.io Windows agents Labels: newbie-friendly Priority: Minor Reporter: Mark Waite The Git for Windows distribution includes "MinGit", a minimal git for Windows. MinGit 2.26.0 and prior do not include large file support. The absence of large file support causes the git client plugin unit tests to fail on Windows machines that have configured MinGit. Git client plugin automated tests should pass successfully on MinGit by ignoring tests that require Large File Support if it is not installed. Add Comment
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61684 Git client plugin automated tests fail with MinGit on Windows Change By: Mark Waite 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.205421.1585146861000.12930.1585147080187%40Atlassian.JIRA.
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-61684 Git client plugin automated tests fail with MinGit on Windows Change By: Mark Waite The [ Git for Windows |https://github.com/git-for-windows/git/releases/] distribution includes " [ MinGit |https://github.com/git-for-windows/git/releases/download/v2.26.0.windows.1/MinGit-2.26.0-64-bit.zip] ", a minimal git for Windows. MinGit 2.26.0 and prior do not include large file support. The absence of large file support causes the git client plugin unit tests to fail on Windows machines that have configured use MinGit.Git client plugin automated tests should pass successfully on MinGit by ignoring tests that require Large File Support if it is not installed. Download and install MinGit 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 e
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-61684
Git client plugin automated tests fail with MinGit on Windows
Change By:
Mark Waite
The [Git for Windows|https://github.com/git-for-windows/git/releases/] distribution includes "[MinGit|https://github.com/git-for-windows/git/releases/download/v2.26.0.windows.1/MinGit-2.26.0-64-bit.zip]", a minimal git for Windows. MinGit 2.26.0 and prior do not include large file support. The absence of large file support causes the git client plugin unit tests to fail on Windows machines that use MinGit.Git client plugin automated tests should pass successfully on MinGit by ignoring tests that require Large File Support if it is not installed.Download and install MinGit , configure it as the only git in your Windows path, and then run the git client plugin automated tests with the command:{noformat}C:\Users\MarkE\git\jenkins\git-client-plugin > mvn clean -Dtest=GitClientTest test{noformat}It will fail several tests and report that the command {{git lfs}} was not found. Those tests already use {{Assume}} to skip the tests if git LFS is not installed. The assumption should be extended to cover the MinGit case as well.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61684) Git client plugin automated tests fail with MinGit on Windows
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61684 Git client plugin automated tests fail with MinGit on Windows 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.205421.1585146861000.12932.1585149720065%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Stefan Drissen commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script I just ran into this migrating from one orchestration multijob + multiple freestyle jobs to one pipeline (declarative plus matrix) on Jenkins 2.226. I have multiple stages ( build / test / deploy ) with matrices inside them ( build on x y, test on x y z, deploy on x y ). My Jenkinsfile is 587 lines. 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.174127.1473169024000.12944.1585150501923%40Atlassian.JIRA.
[JIRA] (JENKINS-61658) Blue Ocean Pipeline: only first skipped cell of matrix shown as skipped
Title: Message Title
Stefan Drissen commented on JENKINS-61658
Re: Blue Ocean Pipeline: only first skipped cell of matrix shown as skipped
I just discovered that if I use the beforeAgent option on the when directive:
#!groovy
pipeline {
agent none
parameters {
booleanParam( name: 'matrix', defaultValue: true )
booleanParam( name: 'parallel', defaultValue: true )
}
stages {
stage( 'matrix' ) {
matrix {
axes {
axis {
name 'server'
values 'server-one', 'server-two'
}
}
stages {
stage( 'matrix' ) {
agent {
label "${server}"
}
when {
beforeAgent true
_expression_ { params.matrix }
}
steps {
echo "matrix ${server}"
}
}
}
}
}
stage( 'parallel' ) {
parallel {
stage( 'parallel-one' ) {
agent {
label 'server-one'
}
when {
_expression_ { params.parallel }
}
steps {
echo 'parallel-one'
}
}
stage( 'parallel-two' ) {
agent {
label 'sever-two'
}
when {
_expression_ { params.parallel }
}
steps {
echo 'parallel-two'
}
}
}
}
} // stages
} // pipeline
That the visual result is a lot better: There is still some confusion as to what is what, since the first matrix cell reports that it has been skipped, whereas the second cell reports that it was not built.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61658) Blue Ocean Pipeline: only first skipped cell of matrix shown as skipped
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-61658 Blue Ocean Pipeline: only first skipped cell of matrix shown as skipped Change By: Stefan Drissen Attachment: image-2020-03-25-17-31-20-694.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205388.1585038606000.13110.1585153920134%40Atlassian.JIRA.
[JIRA] (JENKINS-61658) Blue Ocean Pipeline: only first skipped cell of matrix shown as skipped
Title: Message Title Stefan Drissen updated an issue Jenkins / JENKINS-61658 Blue Ocean Pipeline: only first skipped cell of matrix shown as skipped Change By: Stefan Drissen Attachment: image-2020-03-25-17-31-24-907.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205388.1585038606000.13111.1585153920219%40Atlassian.JIRA.
[JIRA] (JENKINS-61609) Jenkins Openid connect plugin fails to parse groups from AD
Title: Message Title Leo L updated an issue Jenkins / JENKINS-61609 Jenkins Openid connect plugin fails to parse groups from AD Change By: Leo L 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.205311.1584794668000.13127.1585161540499%40Atlassian.JIRA.
[JIRA] (JENKINS-61609) Jenkins Openid connect plugin fails to parse groups from AD
Title: Message Title Leo L commented on JENKINS-61609 Re: Jenkins Openid connect plugin fails to parse groups from AD Added a pull request with suggestion how to address the problem. https://github.com/jenkinsci/oic-auth-plugin/pull/90 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.205311.1584794668000.13126.1585161540486%40Atlassian.JIRA.
[JIRA] (JENKINS-61609) Jenkins Openid connect plugin fails to parse groups from AD
Title: Message Title Leo L started work on JENKINS-61609 Change By: Leo L 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.205311.1584794668000.13131.1585161540576%40Atlassian.JIRA.
[JIRA] (JENKINS-61609) Jenkins Openid connect plugin fails to parse groups from AD
Title: Message Title Leo L assigned an issue to Leo L Jenkins / JENKINS-61609 Jenkins Openid connect plugin fails to parse groups from AD Change By: Leo L Assignee: Leo L 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.205311.1584794668000.13130.1585161540546%40Atlassian.JIRA.
[JIRA] (JENKINS-61294) Jenkins node disconnects frequently because of that job fails.
Title: Message Title Markus Winter commented on JENKINS-61294 Re: Jenkins node disconnects frequently because of that job fails. Fresstyle jobs will fail when the connection from master to agent is lost. Try using pipeline jobs instead. So the question is why you loose connection that frequently, maybe your network is unreliable. 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.204871.1583165063000.13139.1585162800293%40Atlassian.JIRA.
[JIRA] (JENKINS-61685) wrap: General Build Wrapper with class MaskPasswordsBuildWrapper not working
Title: Message Title
_peedus created an issue
Jenkins / JENKINS-61685
wrap: General Build Wrapper with class MaskPasswordsBuildWrapper not working
Issue Type:
Bug
Assignee:
Unassigned
Components:
mask-passwords-plugin
Created:
2020-03-25 19:18
Priority:
Major
Reporter:
_peedus
Hi, The below code prints the user and password value when shell command is executed in Jenkins pipeline.
wrap([$class: 'MaskPasswordsBuildWrapper', varPasswordPairs: [[password: 'id', var: 'clientid'], [password: 'secret', var: 'clientsecret']]]) {
sh "newman run collection.json --env-var user=${id} --env-var password=${secret}"
}
The whole purpose of the password masking is lost here NB: If one does only an echo of the above command (for instance [echo "newman run collection.json --env-var user=${id} --env-var password=${secret}"], the mask works fine. But it doesn't work in shell commands. Thanks!
Add Comment
[JIRA] (JENKINS-61686) test
Title: Message Title vijay kumar created an issue Jenkins / JENKINS-61686 test Issue Type: Task Assignee: magnayn Components: adaptiveplugin Created: 2020-03-25 19:52 Priority: Minor Reporter: vijay kumar 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 a
[JIRA] (JENKINS-20356) Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
Title: Message Title yao wei commented on JENKINS-20356 Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service Ilguiz Latypov Could you be more specific? How to know if it's the Bit9 Parity CarbonBlack causes the problem? It would be much helpful if you could share the link about "permission denied", thanks. One of the machines in my domain is failing because of this reason, the other machine works fine. 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.18.1585168742481%40Atlassian.JIRA.
[JIRA] (JENKINS-61469) Checkout fails with ERROR: Could not determine exact tip revision of
Title: Message Title Felipe Santos commented on JENKINS-61469 Re: Checkout fails with ERROR: Could not determine exact tip revision of There are two workarounds 1. Use Jenkins Job Builder to create the Multibranch Pipeline on Jenkins How-to: https://jenkins-job-builder.readthedocs.io/en/latest/project_workflow_multibranch.html#project_multibranch.gerrit_scm 2. Use Job DSL to create the Multibranch Pipeline on Jenkins Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205150.1584104936000.20.1585170420523%40Atlassian.JIRA.
[JIRA] (JENKINS-61469) Checkout fails with ERROR: Could not determine exact tip revision of
Title: Message Title
Felipe Santos updated an issue
Jenkins / JENKINS-61469
Checkout fails with ERROR: Could not determine exact tip revision of
Change By:
Felipe Santos
## h2. Short explanation : Creating Multibranch Pipelines using Gerrit as Branch Source through the UI causes the error to occur. The error is that for every new Change Request, the first build (and automatic) occurs with no problem, but if you hit Build Now to build a second, it fails with the error stated. This error doesn't happen if you use Jenkins Job Builder or Job DSL to create the Multibranch pipeline, only when created by the UI. ## h2. Long explanation : The issue is the same as the others linked (and closed) but happens using the Gerrit Code Review plugin. Seems like a fix was applied for BlueOcean, Github, Jervis, but I suppose this must also be fixed here. Every time I push a new change for review, the first build of that patchset works. But if you hit Build now on that change, the build fails. The error is:{code:java}ERROR: Could not determine exact tip revision of 01/7002801/3{code}A picture of the pipeline:!image-2020-03-13-10-08-19-925.png!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61469) Checkout fails with ERROR: Could not determine exact tip revision of
Title: Message Title
Felipe Santos updated an issue
Jenkins / JENKINS-61469
Checkout fails with ERROR: Could not determine exact tip revision of
Change By:
Felipe Santos
Hi ## Short explanation:Creating Multibranch Pipelines using Gerrit as Branch Source through the UI causes the error to occur. The error is that for every new Change Request , the first build (and automatic) occurs with no problem, but if you hit Build Now to build a second, it fails with the error stated. I This error doesn ' m experiencing this issue in one of my projects t happen if you use Jenkins Job Builder or Job DSL to create the Multibranch pipeline , using this plugin only when created by the UI . ## Long explanation: The issue is the same as the others linked (and closed) but happens using the Gerrit Code Review plugin. Seems like a fix was applied for BlueOcean, Github, Jervis, but I suppose this must also be fixed here. Every time I push a new change for review, the first build of that patchset works. But if you hit Build now on that change, the build fails. The error is:{code:java}ERROR: Could not determine exact tip revision of 01/7002801/3{code}A picture of the pipeline:!image-2020-03-13-10-08-19-925.png!
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-61469) Checkout fails with ERROR: Could not determine exact tip revision of
Title: Message Title Felipe Santos updated an issue Jenkins / JENKINS-61469 Checkout fails with ERROR: Could not determine exact tip revision of Change By: Felipe Santos Environment: Jenkins v2.225Gerrit Code Review plugin v0.4.1 Gerrit v2.14 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.205150.1584104936000.29.1585170720209%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 The proof was found in Event Viewer / Windows Logs / Application in a message from Source "Cb Protection Agent Notifier". Notification displayed for target "d:\jenkins\workspace\DIR\PROJ@tmp\jenkins-gitclient-ssh196668178943043519.bat" and process "c:\program files\git\mingw64\bin\git.exe". Cb Protection blocked an attempt by git.exe to run jenkins-gitclient-ssh196668178943043519.bat because the file is not approved. If you require access to this file, please contact your system administrator or submit an approval request. Note that approval requests are processed based on priority and arrival time. Please be patient while your request is reviewed and processed. Scroll down for diagnostic data. Source[c:\program files\git\mingw64\bin\git.exe] ProcessHash[017b2f5aa11781cd293e1c412472ed3d92d08affd945fa63bb3a633b1a98785c] ProcessPublisher[Johannes Schindelin (Valid[Yes] Trusted[Yes])] Cmd[git.exe fetch --tags --force --progress -- ssh://g...@company.tld:PORT/GROUP/PROJ.git +refs/heads/*:refs/re] ProcessFlags[WrittenFiles:HaveABInfo] KernelProcessFlags[LocalSystem:64Bit:DepEnabled:LocalAdmin] Tags[\device\harddiskvolume1\program files\git\mingw64\bin\git.exe] Target[d:\jenkins\workspace\DIR\PROJ@tmp\jenkins-gitclient-ssh196668178943043519.bat] Notifier[Block] TargetHash[3b29d2bc77bcadb27fc146d767f23d9c46fb5ab7836daa4d0e60134f1e34996b] TargetPublisher[No Publisher (Valid[No] Trusted[Ineligible:No Cert])] Media[Fixed] Device[Unapproved:0x] DeviceFlags[0x] State[Unapproved] Flags[0x0802] Object[File] Rule[File and Path Execute: Unapproved Executables] List[17] Group[100] Id[27] Server[CBPServer.COMPANY.COM:41002] Policy[MFC High Enforcement] Id[41] Version[0x] CLVersion[211507] Enforcement[20:20:20] User[NT AUTHORITY\SYSTEM] Pid[12616] Tid[12936] Computer[XX] Domain[] Agent[8.1.6.212] OS[Microsoft Windows Server 2008 R2 x64 Server Enterprise Service Pack 1 (6.1.7601)] DateTime[3/24/2020 10:03:49 PM] As a work-around I could replace the default option of using the "git" command with using "JGit" in Global Tool configuration, but because CarbonBlack disabled any other invokation of external commands, I resorted to asking the admins to correct the CarbonBlack limit. I think they added a permission one level above the particular random path to the auto-generated batch files, but I don't know their exact solution. It worked. Add Comment
[JIRA] (JENKINS-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Title: Message Title Felipe Santos commented on JENKINS-49610 Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned I suppose https://issues.jenkins-ci.org/browse/JENKINS-61469 is caused due to 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.188533.1518867464000.51.1585171320961%40Atlassian.JIRA.
[JIRA] (JENKINS-49610) The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned
Title: Message Title Felipe Santos edited a comment on JENKINS-49610 Re: The SCMSource.setOwner(owner) contract needs updating to include ensuring that an ID has been assigned I suppose think https://issues.jenkins-ci.org/browse/ JENKINS-61469 is caused due to 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.188533.1518867464000.56.1585171321033%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 edited a comment on JENKINS-20356
Re: Git CLI cannot clone on Windows using GIT_SSH to set credentials when running as a service
The proof was found in Event Viewer / Windows Logs / Application in a message from Source "Cb Protection Agent Notifier".{noformat}Notification displayed for target "d:\jenkins\workspace\DIR\PROJ@tmp\jenkins-gitclient-ssh196668178943043519.bat" and process "c:\program files\git\mingw64\bin\git.exe".Cb Protection blocked an attempt by git.exe to run jenkins-gitclient-ssh196668178943043519.bat because the file is not approved. If you require access to this file, please contact your system administrator or submit an approval request.Note that approval requests are processed based on priority and arrival time. Please be patient while your request is reviewed and processed. Scroll down for diagnostic data.Source[c:\program files\git\mingw64\bin\git.exe] ProcessHash[017b2f5aa11781cd293e1c412472ed3d92d08affd945fa63bb3a633b1a98785c] ProcessPublisher[Johannes Schindelin (Valid[Yes] Trusted[Yes])]Cmd[git.exe fetch --tags --force --progress -- ssh://g...@company.tld:PORT/GROUP/PROJ.git +refs/heads/*:refs/re]ProcessFlags[WrittenFiles:HaveABInfo]KernelProcessFlags[LocalSystem:64Bit:DepEnabled:LocalAdmin]Tags[\device\harddiskvolume1\program files\git\mingw64\bin\git.exe]Target[d:\jenkins\workspace\DIR\PROJ@tmp\jenkins-gitclient-ssh196668178943043519.bat]Notifier[Block] TargetHash[3b29d2bc77bcadb27fc146d767f23d9c46fb5ab7836daa4d0e60134f1e34996b] TargetPublisher[No Publisher (Valid[No] Trusted[Ineligible:No Cert])]Media[Fixed] Device[Unapproved:0x] DeviceFlags[0x]State[Unapproved] Flags[0x0802]Object[File]Rule[File and Path Execute: Unapproved Executables] List[17] Group[100] Id[27]Server[CBPServer.COMPANY.COM:41002]Policy[ MFC COMPANY High Enforcement] Id[41] Version[0x] CLVersion[211507]Enforcement[20:20:20]User[NT AUTHORITY\SYSTEM] Pid[12616] Tid[12936]Computer[XX] Domain[]Agent[8.1.6.212]OS[Microsoft Windows Server 2008 R2 x64 Server Enterprise Service Pack 1 (6.1.7601)]DateTime[3/24/2020 10:03:49 PM]{noformat}As a work-around I could replace the default option of using the "git" command with using "JGit" in Global Tool configuration, but because CarbonBlack disabled any other invokation of external commands, I resorted to asking the admins to correct the CarbonBlack limit. I think they added a permission one level above the particular random path to the auto-generated batch files, but I don't know their exact solution. It worked.
Add Comment
[JIRA] (JENKINS-61660) Lack of spacing between setup wizard form errors
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-61660 Lack of spacing between setup wizard form errors Change By: Oleg Nenashev Labels: newbie-friendly ux 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.205390.1585039651000.81.1585171620528%40Atlassian.JIRA.
[JIRA] (JENKINS-61686) test
Title: Message Title Oleg Nenashev closed an issue as Not A Defect Please refrain from Jira testing on a public instance for an open source project Jenkins / JENKINS-61686 test Change By: Oleg Nenashev Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://g
[JIRA] (JENKINS-61687) Exceptions due to global build discarder
Title: Message Title Daniel Beck created an issue Jenkins / JENKINS-61687 Exceptions due to global build discarder Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-25 21:51 Labels: ci.jenkins.io Priority: Minor Reporter: Daniel Beck Messages like the following are being logged on ci.jenkins.io after updating to 2.222.1. 2020-03-25 19:18:34.958+ [id=21774] WARNING j.m.BackgroundGlobalBuildDiscarder#lambda$processJob$0: An exception occurred when executing Project Build Discarder Also: java.nio.file.NoSuchFileException: /var/jenkins_home/jobs/Infra/jobs/plugin-site-api/branches/generate-data/builds/93295 -> /var/jenkins_home/jobs/Infra/jobs/plugin-site-api/branches/generate-data/builds/.93295 at java.base/sun.nio.fs.UnixException.translateToIOException(UnixException.java:92) at java.base/sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) at java.base/sun.nio.fs.UnixCopyFile.move(UnixCopyFile.java:417) at java.base/sun.nio.fs.UnixFileSystemProvider.move(UnixFileSystemProvider.java:267) at java.base/java.nio.file.Files.move(Files.java:1421) at hudson.model.Run.delete(Run.java:1621) at hudson.tasks.LogRotator.perform(LogRotator.java:166) jenkins.util.io.CompositeIOException: Failed to rotate logs for [Infra/plugin-site-api/generate-data #93295] at hudson.tasks.LogRotator.perform(LogRotator.java:223) at hudson.model.Job.logRotate(Job.java:469) at jenkins.model.JobGlobalBuildDiscarderStrategy.apply(JobGlobalBuildDiscarderStrategy.java:54) at jenkins.model.BackgroundGlobalBuildDiscarder.lambda$processJob$0(BackgroundGlobalBuildDis
[JIRA] (JENKINS-61687) Exceptions due to global build discarder
Title: Message Title Daniel Beck commented on JENKINS-61687 Re: Exceptions due to global build discarder Obvious problem is that we call the globally configured-by-default "Job Build Discarder" when a build finishes, even though it's redundant. Unclear why there seems to be a race condition here though. Run#delete looks reasonable enough. 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.205510.1585173096000.85.1585173180206%40Atlassian.JIRA.
[JIRA] (JENKINS-61687) Exceptions due to global build discarder
Title: Message Title Daniel Beck commented on JENKINS-61687 Re: Exceptions due to global build discarder https://github.com/jenkinsci/jenkins/blob/jenkins-2.222.1/core/src/main/java/hudson/model/Run.java#L1614-L1638 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.205510.1585173096000.87.1585174080199%40Atlassian.JIRA.
[JIRA] (JENKINS-61464) Gitlab and Bitbucket skip notifications trait are incompatible
Title: Message Title Parichay Barpanda started work on JENKINS-61464 Change By: Parichay Barpanda 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.205144.1584085931000.91.1585174980801%40Atlassian.JIRA.
[JIRA] (JENKINS-61464) Gitlab and Bitbucket skip notifications trait are incompatible
Title: Message Title Parichay Barpanda updated JENKINS-61464 Jenkins / JENKINS-61464 Gitlab and Bitbucket skip notifications trait are incompatible Change By: Parichay Barpanda 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.205144.1584085931000.93.1585174980841%40Atlassian.JIRA.
