[JIRA] (JENKINS-52362) Jenkins hangs due to "Running CpsFlowExecution unresponsive"
Title: Message Title Mykola Marzhan commented on JENKINS-52362 Re: Jenkins hangs due to "Running CpsFlowExecution unresponsive" downgrade to jenkins-2.140 helped me, I don't see any issues anymore. btw, the issue exists on 2.138.3 and on 2.151 versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54269) MissingVerificationStrategyAdministrativeMonitor is missing its name
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54269 Jenkins / JENKINS-54269 MissingVerificationStrategyAdministrativeMonitor is missing its name Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slave-1.29.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49235) Fingerprinting added in ssh-slaves causes memory-leak and performance issue with dynamic slaves
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-49235 Re: Fingerprinting added in ssh-slaves causes memory-leak and performance issue with dynamic slaves there is a change to try to mitigate this issue in ssh-slave-1.29.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52015) Empty credentials dropdown when creating new agent
Title: Message Title Ivan Fernandez Calvo updated JENKINS-52015 Jenkins / JENKINS-52015 Empty credentials dropdown when creating new agent Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slave-1.29.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54686 Jenkins / JENKINS-54686 Use trilead-api plugin instead trilead-ssh2 from core Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slave-1.29.0 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title
Tom Ghyselinck edited a comment on JENKINS-50548
Re: Shared Library should be allowed to declare reusable stages
Hi [~abayer],Is this really a duplicate of [ # JENKINS-49135 |https://issues.jenkins-ci.org/browse/JENKINS-49135 ]?In [PR #241|https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/241], you explicitly say that you won't support the directives {{stage}}, {{stages}}, {{steps}}, etc.and this is actually what we _do_ want here.With best regards,Tom.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50548) Shared Library should be allowed to declare reusable stages
Title: Message Title Tom Ghyselinck commented on JENKINS-50548 Re: Shared Library should be allowed to declare reusable stages Hi Andrew Bayer, Is this really a duplicate of JENKINS-49135? In PR #241, you explicitly say that you won't support the directives stage, stages, steps, etc. and this is actually what we do want here. With best regards, Tom. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54113) NullPointerException in XcodeProjectParser.listXcodeSchemes
Title: Message Title Kazuhide Takahashi updated JENKINS-54113 Release at 2.0.10. Jenkins / JENKINS-54113 NullPointerException in XcodeProjectParser.listXcodeSchemes Change By: Kazuhide Takahashi Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54414) NullPointerException when packaging IPA
Title: Message Title Kazuhide Takahashi updated JENKINS-54414 Release at 2.0.10. Jenkins / JENKINS-54414 NullPointerException when packaging IPA Change By: Kazuhide Takahashi Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39676) Cannot populate servers via groovy script
Title: Message Title
Vishwadeep Bansal edited a comment on JENKINS-39676
Re: Cannot populate servers via groovy script
hi @[~fbelzunc]Thanks for the above construct, could you also give an example to use Jenkins internal fallback user for the following construct. I am unable to enable it ({{[ActiveDirectoryInternalUsersDatabase|https://javadoc.jenkins.io/plugin/active-directory/hudson/plugins/active_directory/ActiveDirectoryInternalUsersDatabase.html] internalUsersDatabase}}) using the code also there is no example anywhere that I could find.{{[ActiveDirectorySecurityRealm|https://javadoc.jenkins.io/plugin/active-directory/hudson/plugins/active_directory/ActiveDirectorySecurityRealm.html#ActiveDirectorySecurityRealm-java.lang.String-java.util.List-java.lang.String-java.lang.String-java.lang.String-java.lang.String-hudson.plugins.active_directory.GroupLookupStrategy-boolean-java.lang.Boolean-hudson.plugins.active_directory.CacheConfiguration-java.lang.Boolean-hudson.plugins.active_directory.TlsConfiguration-hudson.plugins.active_directory.ActiveDirectoryInternalUsersDatabase-]([String|http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true] domain, [List|http://docs.oracle.com/javase/7/docs/api/java/util/List.html?is-external=true]<[ActiveDirectoryDomain|https://javadoc.jenkins.io/plugin/active-directory/hudson/plugins/active_directory/ActiveDirectoryDomain.html]> domains, [String|http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true] site, [String|http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true] bindName, [String|http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true] bindPassword, [String|http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true] server, [GroupLookupStrategy|https://javadoc.jenkins.io/plugin/active-directory/hudson/plugins/active_directory/GroupLookupStrategy.html] groupLookupStrategy, boolean removeIrrelevantGroups, [Boolean|http://docs.oracle.com/javase/7/docs/api/java/lang/Boolean.html?is-external=true] customDomain, [CacheConfiguration|https://javadoc.jenkins.io/plugin/active-directory/hudson/plugins/active_directory/CacheConfiguration.html] cache, [Boolean|http://docs.oracle.com/javase/7/docs/api/java/lang/Boolean.html?is-external=true] startTls, hudson.plugins.active_directory.TlsConfiguration tlsConfiguration, [ActiveDirectoryInternalUsersDatabase|https://javadoc.jenkins.io/plugin/active-directory/hudson/plugins/active_directory/ActiveDirectoryInternalUsersDatabase.html] internalUsersDatabase)}}
Add Comment
[JIRA] (JENKINS-39676) Cannot populate servers via groovy script
Title: Message Title Vishwadeep Bansal commented on JENKINS-39676 Re: Cannot populate servers via groovy script hi @Félix Belzunce Arcos Thanks for the above construct, could you also give an example to use Jenkins internal fallback user for the following construct. I am unable to enable it using the code also there is no example anywhere that I could find. ActiveDirectorySecurityRealm([String|http://docs.oracle.com/javase/7/docs/api/java/lang/String.html?is-external=true] domain, Listdomains, String site, String bindName, String bindPassword, String server, GroupLookupStrategy groupLookupStrategy, boolean removeIrrelevantGroups, Boolean customDomain, CacheConfiguration cache, Boolean startTls, hudson.plugins.active_directory.TlsConfiguration tlsConfiguration, ActiveDirectoryInternalUsersDatabase internalUsersDatabase) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54691) git plugins error
Title: Message Title li leo updated an issue Jenkins / JENKINS-54691 git plugins error Change By: li leo if someone input a error gitlab address in his project,when he is using the lable (build whit with parameters),then everyone who uses the same jenkins will can not open the lable(build with parameter) correctly。 when one project has wrong address,it is unreasonable to influence others. following is the logs screenshot. I hope to find a resolution for this.thank you very much! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54692) system cloud podTemplate support defaultContainer
Title: Message Title runze xia updated an issue Jenkins / JENKINS-54692 system cloud podTemplate support defaultContainer Change By: runze xia Attachment: image-2018-11-19-13-15-30-452.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54692) system cloud podTemplate support defaultContainer
Title: Message Title runze xia created an issue Jenkins / JENKINS-54692 system cloud podTemplate support defaultContainer Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-11-19 05:23 Priority: Minor Reporter: runze xia The defaultContainer setting can be supported when the kubernetes slave config is in the Jenkinsfile. Is it possible to support the same fields in the System cloud settings? In Jenkins X, a single container is usually used as the build environment. However, it is still necessary to switch from the jnlp container to the build container. If the defaultContainer is supported, this problem will be solved. Add Comment
[JIRA] (JENKINS-37225) Reproducible: Jenkins creates more and more slaves when an unrestricted job is waiting for master executor slot
Title: Message Title Philipp Garbe assigned an issue to Philipp Garbe Jenkins / JENKINS-37225 Reproducible: Jenkins creates more and more slaves when an unrestricted job is waiting for master executor slot Change By: Philipp Garbe Assignee: Jan Roehrich Philipp Garbe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54428) ECS plugin fails if task definition ARN is used
Title: Message Title Philipp Garbe resolved as Fixed Jenkins / JENKINS-54428 ECS plugin fails if task definition ARN is used Change By: Philipp Garbe Status: Reopened Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53899) Allow credentials to be used for ECS plugin
Title: Message Title Philipp Garbe commented on JENKINS-53899 Re: Allow credentials to be used for ECS plugin Another approach would be to use the new support of secrets within ECS: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54473) ECS plugin cannot start Windows containers
Title: Message Title Philipp Garbe closed an issue as Fixed Jenkins / JENKINS-54473 ECS plugin cannot start Windows containers Change By: Philipp Garbe Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54473) ECS plugin cannot start Windows containers
Title: Message Title Philipp Garbe updated JENKINS-54473 Jenkins / JENKINS-54473 ECS plugin cannot start Windows containers Change By: Philipp Garbe Status: In Review Resolved Resolution: Fixed Released As: v1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54380) Private repository authentication
Title: Message Title Philipp Garbe updated JENKINS-54380 Jenkins / JENKINS-54380 Private repository authentication Change By: Philipp Garbe Status: In Review Resolved Resolution: Fixed Released As: v1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54380) Private repository authentication
Title: Message Title Philipp Garbe closed an issue as Fixed Jenkins / JENKINS-54380 Private repository authentication Change By: Philipp Garbe Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54691) git plugins error
Title: Message Title li leo created an issue Jenkins / JENKINS-54691 git plugins error Issue Type: Bug Assignee: Mark Waite Attachments: erro.png Components: git-plugin Created: 2018-11-19 03:57 Environment: centos 7.2 jenkins ver 2.145 git version 1.8.3.1 Priority: Major Reporter: li leo if someone input a error gitlab address in his project,when he is using the lable (build whit parameters),then everyone who uses the same jenkins will can not open the lable(build with parameter) correctly。 when one project has wrong address,it is unreasonable to influence others. following is the logs screenshot. I hope to find a resolution for this.thank you very much! Add Comment
[JIRA] (JENKINS-54690) 系统配置页面报错
Title: Message Title 张 晋鹏 created an issue Jenkins / JENKINS-54690 系统配置页面报错 Issue Type: Bug Assignee: Praqma Support Components: component Created: 2018-11-19 03:04 Environment: linux Priority: Blocker Reporter: 张 晋鹏 org.apache.commons.jelly.JellyTagException: jar:file:/home/weblogic/.jenkins/war/WEB-INF/lib/jenkins-core-2.147.jar!/hudson/model/UpdateCenter/CoreUpdateMonitor/message.jelly:53:20: can't parse argument number: changelog.url at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:726) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:281) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:95) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.Ca
[JIRA] (JENKINS-35447) Symlink problem when moving Pipeline projects into folder
Title: Message Title Andrew Gray updated an issue Jenkins / JENKINS-35447 Symlink problem when moving Pipeline projects into folder Change By: Andrew Gray Environment: Jenkins ver. 2.8 running on Ubuntu 14.04 Jenkins ver. 2.138.3 running on Windows Server 2016 Datacenter Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40203) Exception while moving project
Title: Message Title Andrew Gray updated an issue Jenkins / JENKINS-40203 Exception while moving project Change By: Andrew Gray Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35447) Symlink problem when moving Pipeline projects into folder
Title: Message Title Andrew Gray updated an issue Jenkins / JENKINS-35447 Symlink problem when moving Pipeline projects into folder Change By: Andrew Gray Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35447) Symlink problem when moving Pipeline projects into folder
Title: Message Title Andrew Gray commented on JENKINS-35447 Re: Symlink problem when moving Pipeline projects into folder Is there a plan to fix this for both Linux and Windows? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54687) GCLogs should be excluded by default
Title: Message Title Owen Wood closed an issue as Fixed Jenkins / JENKINS-54687 GCLogs should be excluded by default Change By: Owen Wood Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52267) gitlab-plugin Pipeline compatibility broken with version 1.5.7
Title: Message Title Owen Mehegan resolved as Fixed Jenkins / JENKINS-52267 gitlab-plugin Pipeline compatibility broken with version 1.5.7 Change By: Owen Mehegan Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52267) gitlab-plugin Pipeline compatibility broken with version 1.5.7
Title: Message Title Owen Mehegan commented on JENKINS-52267 Re: gitlab-plugin Pipeline compatibility broken with version 1.5.7 I just released 1.5.11 which should fix this; works now when I test it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54687) GCLogs should be excluded by default
Title: Message Title Owen Wood updated JENKINS-54687 Jenkins / JENKINS-54687 GCLogs should be excluded by default Change By: Owen Wood Status: In Review Resolved Resolution: Fixed Released As: 2.51 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53732) Git plugin unit test is leaking into user's git config
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-53732 Git plugin unit test is leaking into user's git config Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54687) GCLogs should be excluded by default
Title: Message Title Owen Wood updated an issue Jenkins / JENKINS-54687 GCLogs should be excluded by default Change By: Owen Wood This can result in some rather large support bundles if GC log rotation is not configured optimally.I'm simply proposing that this component override isSelectedByDefault (to false) so that GC logs :a) aren't accidentally included by users generating support bundles b) aren't included in the automatically generated support bundles . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35447) Symlink problem when moving Pipeline projects into folder
Title: Message Title Andrew Gray commented on JENKINS-35447 Re: Symlink problem when moving Pipeline projects into folder This issue is also occurring on Windows. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54689) Incorrect display build duration time
Title: Message Title Maksim Kolesnikov updated an issue Jenkins / JENKINS-54689 Incorrect display build duration time Change By: Maksim Kolesnikov Component/s: core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54689) Incorrect display build duration time
Title: Message Title Maksim Kolesnikov updated an issue Jenkins / JENKINS-54689 Incorrect display build duration time Change By: Maksim Kolesnikov Priority: Minor Trivial Environment: Jenkins 2.138.3 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53732) Git plugin unit test is leaking into user's git config
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-53732 Git plugin unit test is leaking into user's git config Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54689) Incorrect display build duration time
Title: Message Title Maksim Kolesnikov created an issue Jenkins / JENKINS-54689 Incorrect display build duration time Issue Type: Bug Assignee: Unassigned Components: metrics-plugin Created: 2018-11-19 00:08 Priority: Minor Reporter: Maksim Kolesnikov I see an incorrect display of task execution time. For example, This run spent: 11 min waiting; 13 min build duration; 13 min total from scheduled to completion. In fact, the build was executed in just 2 minutes, but i see 13 minutes (waiting + exec time). JSON contains correct timings: "buildableTimeMillis":702663,"buildingDurationMillis":832158,"executingTimeMillis":129299. Add Comment
[JIRA] (JENKINS-52267) gitlab-plugin Pipeline compatibility broken with version 1.5.7
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-52267 gitlab-plugin Pipeline compatibility broken with version 1.5.7 Change By: Owen Mehegan Released As: 1.5. 8 11 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54688) Operating System informations are anonymized
Title: Message Title Arnaud Héritier created an issue Jenkins / JENKINS-54688 Operating System informations are anonymized Issue Type: Bug Assignee: Emilio Escobar Components: support-core-plugin Created: 2018-11-18 23:25 Priority: Major Reporter: Arnaud Héritier Due to JENKINS-21670 the Operating System informations from the master node in about.md or any nodes in nodes.md could be anonymised. Few samples : * Operating system - Name: label_short_share - Architecture: amd64 - Version: 3.10.0-862.14.4.el7.x86_64 * Operating system - Name: label_comprehensive_pest - Architecture: amd64 - Version: 3.10.0-693.21.1.el7.x86_64 * Operating system - Name: label_conservative_box - Architecture: amd64 - Version: 3.10.0-862.11.6.el7.x86_64 - Distribution: "Red Hat Enterprise label_conservative_box Server release 7.5 (Maipo)" - LSB Modules: `:core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch`
[JIRA] (JENKINS-54687) GCLogs should be excluded by default
Title: Message Title Owen Wood updated JENKINS-54687 Jenkins / JENKINS-54687 GCLogs should be excluded by default Change By: Owen Wood Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54687) GCLogs should be excluded by default
Title: Message Title Owen Wood started work on JENKINS-54687 Change By: Owen Wood Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54687) GCLogs should be excluded by default
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-54687 GCLogs should be excluded by default Issue Type: Improvement Assignee: Owen Wood Components: support-core-plugin Created: 2018-11-18 22:28 Priority: Minor Reporter: Owen Wood This can result in some rather large support bundles if GC log rotation is not configured optimally. I'm simply proposing that this component override isSelectedByDefault (to false) so that GC logs: a) aren't accidentally included by users generating support bundles b) aren't included in the automatically generated support bundles Add Comment
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 core
Title: Message Title Ivan Fernandez Calvo started work on JENKINS-54686 Change By: Ivan Fernandez Calvo Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 from core
Title: Message Title Ivan Fernandez Calvo updated an issue Jenkins / JENKINS-54686 Use trilead-api plugin instead trilead-ssh2 from core Change By: Ivan Fernandez Calvo Summary: Use trilead-api plugin instead trilead-ssh2 from core Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 core
Title: Message Title Ivan Fernandez Calvo updated JENKINS-54686 Jenkins / JENKINS-54686 Use trilead-api plugin instead trilead-ssh2 core Change By: Ivan Fernandez Calvo Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54686) Use trilead-api plugin instead trilead-ssh2 core
Title: Message Title Ivan Fernandez Calvo created an issue Jenkins / JENKINS-54686 Use trilead-api plugin instead trilead-ssh2 core Issue Type: Improvement Assignee: Ivan Fernandez Calvo Components: ssh-slaves-plugin, trilead-api-plugin Created: 2018-11-18 19:43 Priority: Minor Reporter: Ivan Fernandez Calvo Remove the dependency of the Trilead-ssh2 plugin and use the Trilead-api plugins instead, this means that ssh-slaves plugins no longer uses the trilead-ssh2 plugin provider by the Jenkins core, it will use the Trilead-api version, so now it is possible to upgrade the plugin ssh library without to upgrade the core. Add Comment
[JIRA] (JENKINS-54685) data ecomony
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-54685 data ecomony Issue Type: Improvement Assignee: Jakub Bochenski Components: logstash-plugin Created: 2018-11-18 19:07 Priority: Major Reporter: Markus Winter When sending the log line by line via the JobProperty or the pipeline logstash step, the complete data is sent every time. This data is static and never changes, so it should be sufficient to send it once at the beginning or the end. Add Comment This message was sen
[JIRA] (JENKINS-54684) ERROR: [Sun Nov 18 07:58:23 UTC 2018] Could not fetch branches from source guid
Title: Message Title Bharath Vasudevan updated an issue Jenkins / JENKINS-54684 ERROR: [Sun Nov 18 07:58:23 UTC 2018] Could not fetch branches from source guid Change By: Bharath Vasudevan Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53994) Parameters that use own descriptor to check/fill fields returns 404 in schedule release page
Title: Message Title Oleg Nenashev updated JENKINS-53994 Jenkins / JENKINS-53994 Parameters that use own descriptor to check/fill fields returns 404 in schedule release page Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Released As: Release plugin 2.10.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title Nikolas Falco closed an issue as Duplicate Jenkins / JENKINS-37443 Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline Change By: Nikolas Falco Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37443) Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-37443 Publish hangs for xUnit Plugin for (NUnit test report) in multiple-pipeline Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33440) Maven build with submodules with junit reports overwrite xunit attached reports
Title: Message Title
Nikolas Falco edited a comment on JENKINS-33440
Re: Maven build with submodules with junit reports overwrite xunit attached reports
Both maven and xunit use the junit plugin to gather and parse junit report. xunit is able to merge result, the maven maybe does not support it. It's just a case that both relies on junit plugin to represent the test trend. In your case disable the maven autopublish feature and configure xunit to discovery every {noformat} **/TEST*.xml {noformat} . This also prevent different behavior, maven does not have the same logic to mark the build based on configurable thresholds.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33440) Maven build with submodules with junit reports overwrite xunit attached reports
Title: Message Title Nikolas Falco closed an issue as Not A Defect Both maven and xunit use the junit plugin to gather and parse junit report. xunit is able to merge result, the maven maybe does not support it. It's just a case that both relies on junit plugin to represent the test trend. In your case disable the maven autopublish feature and configure xunit to discovery every */TEST.xml. This also prevent different behavior, maven does not have the same logic to mark the build based on configurable thresholds. Jenkins / JENKINS-33440 Maven build with submodules with junit reports overwrite xunit attached reports Change By: Nikolas Falco Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubs
[JIRA] (JENKINS-33440) Maven build with submodules with junit reports overwrite xunit attached reports
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-33440 Maven build with submodules with junit reports overwrite xunit attached reports Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
Title: Message Title Nikolas Falco closed an issue as Not A Defect By design total wins on new (failures in your case) and failure threshold have precedences over unstable threshold. For your case I will expect that a simple 1,2,3,4 new failures mark the build as unstable untill you exceed the threshold of total failures. Setup it with 0 new failure -> UNSTABLE 2 totale failures -> FAILED So that in your case: Run 38 has all pass. run 40 has one test failed -> "unstable" run 42 has another two test failed -> "failed" Jenkins / JENKINS-16081 xUnit plugin fails to recognize regression if total number of tests doesn't go up. Change By: Nikolas Falco Status: In Progress Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-54684) ERROR: [Sun Nov 18 07:58:23 UTC 2018] Could not fetch branches from source guid
Title: Message Title Bharath Vasudevan created an issue Jenkins / JENKINS-54684 ERROR: [Sun Nov 18 07:58:23 UTC 2018] Could not fetch branches from source guid Issue Type: Task Assignee: Unassigned Components: bitbucket-branch-source-plugin Created: 2018-11-18 11:42 Environment: Production Priority: Blocker Reporter: Bharath Vasudevan Hi, While executing the build deployment from Jenkins pipeline and even tried to scan multi-branch pipeline. we are receiving the below error that using GIT_ASKPASS to set credentials null > git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ --prune ERROR: Timeout after 10 minutes ERROR: [Sun Nov 18 07:58:23 UTC 2018] Could not fetch branches from source XXX hudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ --prune" returned status code 143: stdout: stderr: remote: Counting objects: 1096, done. Receiving objects: 61% (678/1096), 156.23 MiB | 277.00 KiB/s at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2016) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1735) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:420) at jenkins.plugins.git.AbstractGitSCMSource.doRetrieve(AbstractGitSCMSource.java:351) at jenkins.plugins.git.AbstractGitSCMSource.retrieve(AbstractGitSCMSource.java:539) at jenkins.scm.api.SCMSource._retrieve(SCMSource.java:357) at jenkins.scm.api.SCMSource.fetch(SCMSource.java:267) at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:633) at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChild
[JIRA] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
Title: Message Title Nikolas Falco commented on JENKINS-16081 Re: xUnit plugin fails to recognize regression if total number of tests doesn't go up. The configuration is quite strange, you want that if there are new test failed the build is FAILED instead if there are no new failure but some test continue to fails than the build is marked as UNSTABLE? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-16081) xUnit plugin fails to recognize regression if total number of tests doesn't go up.
Title: Message Title Nikolas Falco assigned an issue to Nikolas Falco Jenkins / JENKINS-16081 xUnit plugin fails to recognize regression if total number of tests doesn't go up. Change By: Nikolas Falco Assignee: Gregory Boissinot Nikolas Falco Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54578) Cannot delete last category
Title: Message Title Diego Agulló commented on JENKINS-54578 Re: Cannot delete last category Ready to review on GitHub. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54578) Cannot delete last category
Title: Message Title Diego Agulló updated JENKINS-54578 Jenkins / JENKINS-54578 Cannot delete last category Change By: Diego Agulló Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title
Petar Tahchiev edited a comment on JENKINS-12290
Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
I've just hit this issue :( My scenario is the following. I have several projects: - bom - platform - archetype - console - release-all The release-all is a pipeline build which calls release on each of them in the following order \ {{bom}}-> \ {{platform}}->archetype->console However because I have just one executor running release-all blocks the executor and bom is never started to release because it is waiting for the next available executor.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title
Petar Tahchiev edited a comment on JENKINS-12290
Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
I've just hit this issue :( My scenario is the following. I have several projects: - bom - platform - archetype - console - release-all The release-all is a pipeline build which calls release on each of them in the following order {{ bom }} -> {{ platform }} ->archetype->console However because I have just one executor running release-all blocks the executor and bom is never started to release because it is waiting for the next available executor.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title
Petar Tahchiev edited a comment on JENKINS-12290
Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
I've just hit this issue :( My scenario is the following. I have several projects: - bom - platform - archetype - console - release-all The release-all is a pipeline build which calls release on each of them in the following order \{{ bom }} -> \{{ platform }} ->archetype->console However because I have just one executor running release-all blocks the executor and bom is never started to release because it is waiting for the next available executor.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12290) Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor
Title: Message Title Petar Tahchiev commented on JENKINS-12290 Re: Lockup when using "trigger/call builds on other projects" and "Block until the triggered projects finish their builds" is used with only 1 executor I've just hit this issue My scenario is the following. I have several projects: - bom - platform - archetype - console - release-all The release-all is a pipeline build which calls release on each of them in the following order bom->platform->archetype->console However because I have just one executor running release-all blocks the executor and bom is never started to release because it is waiting for the next available executor. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
