[JIRA] (JENKINS-32851) Gerrit Connection Breaks on Jenkins 1.609.2 LTS
Title: Message Title Arun Mathew edited a comment on JENKINS-32851 Re: Gerrit Connection Breaks on Jenkins 1.609.2 LTS Hi All,We are too facing the same issue. Gerrit and jenkins are running behind nginx proxy with SSL enabled. RestAPI is all fine. Its able to connect to the gerrit server, but not able to post comments. Any workaround?Getting Sonar Report from: /var/lib/jenkins/workspace/ul_hybris_b2c/incremental_sonar/.sonar/sonar-report.jsonReport has loaded and contains 736 issuesConnected to Gerrit: server name: ADOP Gerrit. Change Number: 26, PatchSetNumber: 1Unable to post review: Request failed.Build step 'Post SonarQube issues as Gerrit comments' marked build as failureJenkins Version: 2.7.2Sonar-Gerrit: 1.0.6Gerrit Trigger: 2.22.0[~sbr] How did you resolve the issue [~slbr] Any workaround ? Can you pls help me too? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-32851) Gerrit Connection Breaks on Jenkins 1.609.2 LTS
Title: Message Title Arun Mathew edited a comment on JENKINS-32851 Re: Gerrit Connection Breaks on Jenkins 1.609.2 LTS Hi All,We are too facing the same issue. Gerrit and jenkins are running behind nginx proxy with SSL enabled. RestAPI is all fine. Its able to connect to the gerrit server, but not able to post comments. Any workaround?Getting Sonar Report from: /var/lib/jenkins/workspace/ul_hybris_b2c/incremental_sonar/.sonar/sonar-report.jsonReport has loaded and contains 736 issuesConnected to Gerrit: server name: ADOP Gerrit. Change Number: 26, PatchSetNumber: 1Unable to post review: Request failed.Build step 'Post SonarQube issues as Gerrit comments' marked build as failureJenkins Version: 2.7.2Sonar-Gerrit: 1.0.6Gerrit Trigger: 2.22.0 [~sbr] How did you resolve the issue? Can you pls help me too? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-32851) Gerrit Connection Breaks on Jenkins 1.609.2 LTS
Title: Message Title Arun Mathew edited a comment on JENKINS-32851 Re: Gerrit Connection Breaks on Jenkins 1.609.2 LTS Hi All,We are too facing the same issue. Gerrit and jenkins are running behind nginx proxy with SSL enabled. RestAPI is all fine. Its able to connect to the gerrit server, but not able to post comments. Any workaround?Getting Sonar Report from: /var/lib/jenkins/workspace/ul_hybris_b2c/incremental_sonar/.sonar/sonar-report.jsonReport has loaded and contains 736 issuesConnected to Gerrit: server name: ADOP Gerrit. Change Number: 26, PatchSetNumber: 1Unable to post review: Request failed.Build step 'Post SonarQube issues as Gerrit comments' marked build as failure Jenkins Version: 2.7.2Sonar-Gerrit: 1.0.6Gerrit Trigger: 2.22.0 < /td> Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-32851) Gerrit Connection Breaks on Jenkins 1.609.2 LTS
Title: Message Title Arun Mathew commented on JENKINS-32851 Re: Gerrit Connection Breaks on Jenkins 1.609.2 LTS Hi All, We are too facing the same issue. Gerrit and jenkins are running behind nginx proxy with SSL enabled. RestAPI is all fine. Its able to connect to the gerrit server, but not able to post comments. Any workaround? Getting Sonar Report from: /var/lib/jenkins/workspace/ul_hybris_b2c/incremental_sonar/.sonar/sonar-report.json Report has loaded and contains 736 issues Connected to Gerrit: server name: ADOP Gerrit. Change Number: 26, PatchSetNumber: 1 Unable to post review: Request failed. Build step 'Post SonarQube issues as Gerrit comments' marked build as failure Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-35487) Add support for Jenkins Pipeline to the cobertura-plugin
Title: Message Title Sean Flanigan commented on JENKINS-35487 Re: Add support for Jenkins Pipeline to the cobertura-plugin Should this be closed as a duplicate of JENKINS-30700? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-35367) EMail-Ext Extended Pipeline Support - Templates
Title: Message Title David van Laatum closed an issue as Fixed version 2.50 release and should be available shortly Jenkins / JENKINS-35367 EMail-Ext Extended Pipeline Support - Templates Change By: David van Laatum Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-37594) email-ext plugin can't recognize content file in workspace
Title: Message Title David van Laatum closed an issue as Cannot Reproduce Jenkins / JENKINS-37594 email-ext plugin can't recognize content file in workspace Change By: David van Laatum Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title
Sebastien Rosset updated an issue
Jenkins / JENKINS-38479
Grade Plugin: Fix Documentation of the "Root Build script" attribute
Change By:
Sebastien Rosset
The Gradle plugin has the following documentation for the "Root Build script" attribute:{quote}If your workspace has the top-level build.gradle in somewhere other than the module root directory, specify the path (relative to the module root) here, such as $\{workspace\}/parent/ instead of just $\{workspace\}. If left empty, defaults to build.gradle{quote}The doc is confusing because:1) The doc states the path is relative to the module root, but at the same time it provides an example with an absolute path - assuming $ \ {workspace \ } is expanded to an absolute path.2) The doc provides $ \ {workspace \ } as an example, is this referring to the WORKSPACE environment variable? Then shouldn't it be all caps? 3) It's not clear if the user is supposed to enter a directory name or a file name. The documentation has an example with $ \ {workspace \ }/parent/ which is a directory, but the doc also states the default is build.gradle, which is a file.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title
Sebastien Rosset updated an issue
Jenkins / JENKINS-38479
Grade Plugin: Fix Documentation of the "Root Build script" attribute
Change By:
Sebastien Rosset
The Gradle plugin has the following documentation for the "Root Build script" attribute:{quote}If your workspace has the top-level build.gradle in somewhere other than the module root directory, specify the path (relative to the module root) here, such as $ \ {workspace \ }/parent/ instead of just $ \ {workspace \ }. If left empty, defaults to build.gradle{quote}The doc is confusing because:1) The doc states the path is relative to the module root, but at the same time it provides an example with an absolute path - assuming ${workspace} is expanded to an absolute path.2) The doc provides ${workspace} as an example, is this referring to the WORKSPACE environment variable? Then shouldn't it be all caps? 3) It's not clear if the user is supposed to enter a directory name or a file name. The documentation has an example with ${workspace}/parent/ which is a directory, but the doc also states the default is build.gradle, which is a file.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title
Sebastien Rosset updated an issue
Jenkins / JENKINS-38479
Grade Plugin: Fix Documentation of the "Root Build script" attribute
Change By:
Sebastien Rosset
The Gradle plugin has the following documentation for the "Root Build script" attribute:{quote} {{ If your workspace has the top-level build.gradle in somewhere other than the module root directory, specify the path (relative to the module root) here, such as ${workspace}/parent/ instead of just ${workspace}. If left empty, defaults to build.gradle}} {quote} The doc is confusing because:1) The doc states the path is relative to the module root, but at the same time it provides an example with an absolute path - assuming ${workspace} is expanded to an absolute path.2) The doc provides ${workspace} as an example, is this referring to the WORKSPACE environment variable? Then shouldn't it be all caps? 3) It's not clear if the user is supposed to enter a directory name or a file name. The documentation has an example with ${workspace}/parent/ which is a directory, but the doc also states the default is build.gradle, which is a file.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title
Sebastien Rosset updated an issue
Jenkins / JENKINS-38479
Grade Plugin: Fix Documentation of the "Root Build script" attribute
Change By:
Sebastien Rosset
The Gradle plugin has the following documentation for the "Root Build script" attribute:{quote}If your workspace has the top-level build.gradle in somewhere other than the module root directory, specify the path (relative to the module root) here, such as ${workspace}/parent/ instead of just ${workspace}. If left empty, defaults to build.gradle {quote } } The doc is confusing because:1) The doc states the path is relative to the module root, but at the same time it provides an example with an absolute path - assuming ${workspace} is expanded to an absolute path.2) The doc provides ${workspace} as an example, is this referring to the WORKSPACE environment variable? Then shouldn't it be all caps? 3) It's not clear if the user is supposed to enter a directory name or a file name. The documentation has an example with ${workspace}/parent/ which is a directory, but the doc also states the default is build.gradle, which is a file.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title
Sebastien Rosset updated an issue
Jenkins / JENKINS-38479
Grade Plugin: Fix Documentation of the "Root Build script" attribute
Change By:
Sebastien Rosset
The Gradle plugin has the following documentation for the "Root Build script" attribute:{ quote} { { If your workspace has the top-level build.gradle in somewhere other than the module root directory, specify the path (relative to the module root) here, such as ${workspace}/parent/ instead of just ${workspace}. If left empty, defaults to build.gradle}} {quote} The doc is confusing because:1) The doc states the path is relative to the module root, but at the same time it provides an example with an absolute path - assuming ${workspace} is expanded to an absolute path.2) The doc provides ${workspace} as an example, is this referring to the WORKSPACE environment variable? Then shouldn't it be all caps? 3) It's not clear if the user is supposed to enter a directory name or a file name. The documentation has an example with ${workspace}/parent/ which is a directory, but the doc also states the default is build.gradle, which is a file.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title
Sebastien Rosset updated an issue
Jenkins / JENKINS-38479
Grade Plugin: Fix Documentation of the "Root Build script" attribute
Change By:
Sebastien Rosset
The Gradle plugin has the following documentation for the "Root Build script" attribute: {{ If your workspace has the top-level build.gradle in somewhere other than the module root directory, specify the path (relative to the module root) here, such as ${workspace}/parent/ instead of just ${workspace}. If left empty, defaults to build.gradle }} The doc is confusing because:1) The doc states the path is relative to the module root, but at the same time it provides an example with an absolute path - assuming ${workspace} is expanded to an absolute path.2) The doc provides ${workspace} as an example, is this referring to the WORKSPACE environment variable? Then shouldn't it be all caps? 3) It's not clear if the user is supposed to enter a directory name or a file name. The documentation has an example with ${workspace}/parent/ which is a directory, but the doc also states the default is build.gradle, which is a file.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title
Sebastien Rosset created an issue
Jenkins / JENKINS-38479
Grade Plugin: Fix Documentation of the "Root Build script" attribute
Issue Type:
Bug
Assignee:
wolfs
Components:
gradle-plugin
Created:
2016/Sep/24 2:58 AM
Environment:
Jenkins ver. 1.642.18.3 (CloudBees Jenkins Enterprise 15.11) Gradle Plugin Chrome Web browser
Priority:
Minor
Reporter:
Sebastien Rosset
The Gradle plugin has the following documentation for the "Root Build script" attribute: If your workspace has the top-level build.gradle in somewhere other than the module root directory, specify the path (relative to the module root) here, such as *$ {workspace}/parent/ *instead of just ${workspace} . If left empty, defaults to build.gradle The doc is confusing because: 1) The doc states the path is relative to the module root, but at the same time it provides an example with an absolute path - assuming $ {workspace} is expanded to an absolute path. 2) The doc provides ${workspace} as an example, is this referring to the WORKSPACE environment variable? Then shouldn't it be all caps? 3) It's not clear if the user is supposed to enter a directory name or a file name. The documentation has an example with $ {workspace} /parent/ which is a directory, but the doc also states the default is build.gradle, which is a file.
[JIRA] (JENKINS-38479) Grade Plugin: Fix Documentation of the "Root Build script" attribute
Title: Message Title
Sebastien Rosset updated an issue
Jenkins / JENKINS-38479
Grade Plugin: Fix Documentation of the "Root Build script" attribute
Change By:
Sebastien Rosset
The Gradle plugin has the following documentation for the "Root Build script" attribute:If your workspace has the top-level build.gradle in somewhere other than the module root directory, specify the path (relative to the module root) here, such as * ${workspace}/parent/ * instead of just ${workspace}. If left empty, * defaults to build.gradle * The doc is confusing because:1) The doc states the path is relative to the module root, but at the same time it provides an example with an absolute path - assuming ${workspace} is expanded to an absolute path.2) The doc provides ${workspace} as an example, is this referring to the WORKSPACE environment variable? Then shouldn't it be all caps? 3) It's not clear if the user is supposed to enter a directory name or a file name. The documentation has an example with ${workspace}/parent/ which is a directory, but the doc also states the default is build.gradle, which is a file.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Sean Gilhooly commented on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
I might have a different bug that has the same outcome but my script does not have any dir calls in it. With just a sh command I get this error.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-35367) EMail-Ext Extended Pipeline Support - Templates
Title: Message Title SCM/JIRA link daemon commented on JENKINS-35367 Re: EMail-Ext Extended Pipeline Support - Templates Code changed in jenkins User: David van Laatum Path: pom.xml src/main/java/hudson/plugins/emailext/AttachmentUtils.java src/main/java/hudson/plugins/emailext/EmailExtTemplateAction.java src/main/java/hudson/plugins/emailext/EmailExtTemplateActionFactory.java src/main/java/hudson/plugins/emailext/EmailRecipientUtils.java src/main/java/hudson/plugins/emailext/EmailType.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java src/main/java/hudson/plugins/emailext/GroovyScriptPath.java src/main/java/hudson/plugins/emailext/plugins/ContentBuilder.java src/main/java/hudson/plugins/emailext/plugins/CssInliner.java src/main/java/hudson/plugins/emailext/plugins/EmailToken.java src/main/java/hudson/plugins/emailext/plugins/EmailTrigger.java src/main/java/hudson/plugins/emailext/plugins/EmailTriggerDescriptor.java src/main/java/hudson/plugins/emailext/plugins/RecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/ZipDataSource.java src/main/java/hudson/plugins/emailext/plugins/content/AbstractEvalContent.java src/main/java/hudson/plugins/emailext/plugins/content/FailedTestsContent.java src/main/java/hudson/plugins/emailext/plugins/content/JellyScriptContent.java src/main/java/hudson/plugins/emailext/plugins/content/ScriptContent.java src/main/java/hudson/plugins/emailext/plugins/content/ScriptContentBuildWrapper.java src/main/java/hudson/plugins/emailext/plugins/content/StaticAnalysisUtilities.java src/main/java/hudson/plugins/emailext/plugins/content/TemplateContent.java src/main/java/hudson/plugins/emailext/plugins/content/TestCountsContent.java src/main/java/hudson/plugins/emailext/plugins/content/TriggerNameContent.java src/main/java/hudson/plugins/emailext/plugins/recipients/CulpritsRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/FailingTestSuspectsRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/FirstFailingBuildSuspectsRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/ListRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/RecipientProviderUtilities.java src/main/java/hudson/plugins/emailext/plugins/recipients/RequesterRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/recipients/UpstreamComitterRecipientProvider.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbortedTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/AbstractScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/AlwaysTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/BuildingTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FirstUnstableTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FixedTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/FixedUnhealthyTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/ImprovementTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/NotBuiltTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/NthFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildScriptTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/PreBuildTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/RegressionTrigger.java
[JIRA] (JENKINS-37188) 2nd failure emails being sent even when build is successful with job-dsl-plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37188 Re: 2nd failure emails being sent even when build is successful with job-dsl-plugin Code changed in jenkins User: David van Laatum Path: src/main/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/NthFailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/SecondFailureTrigger.java src/test/java/hudson/plugins/emailext/plugins/trigger/FirstFailureTriggerTest.java src/test/resources/hudson/plugins/emailext/plugins/trigger/oldformat.xml http://jenkins-ci.org/commit/email-ext-plugin/f75318d75a5129a0d91773906962efc24337fdcf Log: JENKINS-37188 2nd failure emails being sent even when build is successful with job-dsl-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37350) Don't use random for Filename in Save to Workspace option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-37350 Re: Don't use random for Filename in Save to Workspace option Code changed in jenkins User: Cristian Uroz Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java http://jenkins-ci.org/commit/email-ext-plugin/186435cd8139eb99656b76f60b63dd698cfa27b9 Log: JENKINS-37350 Don't use random for File name in Save to Workspace option (#138) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Abdulaziz Alfoudari commented on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Until there is a fix, a quick around is to append `cd foo &&` to each `sh` inside `dir('foo')`:
dir('foo') {
sh 'cd foo && make'
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-35227) Multi-Branch-Job with Subversion repo which contains externals fails on checkout
Title: Message Title Niels Wegner commented on JENKINS-35227 Re: Multi-Branch-Job with Subversion repo which contains externals fails on checkout This issue seems to be more related to the multibranch plugin, added that as component Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37672) multibranch pipeline with SVN additional credentials
Title: Message Title Niels Wegner commented on JENKINS-37672 Re: multibranch pipeline with SVN additional credentials This seems to be a duplicate of JENKINS-35227 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-35227) Multi-Branch-Job with Subversion repo which contains externals fails on checkout
Title: Message Title Niels Wegner updated an issue Jenkins / JENKINS-35227 Multi-Branch-Job with Subversion repo which contains externals fails on checkout Change By: Niels Wegner Labels: multibranch pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-35227) Multi-Branch-Job with Subversion repo which contains externals fails on checkout
Title: Message Title Niels Wegner updated an issue Jenkins / JENKINS-35227 Multi-Branch-Job with Subversion repo which contains externals fails on checkout Change By: Niels Wegner Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38381) Optimize log handling
Title: Message Title Jesse Glick commented on JENKINS-38381 Re: Optimize log handling Have an early draft available. Not yet trying to avoid streaming DurableTaskStep output back to the master. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-32967) Build Now/Schedule buttons fails with IE
Title: Message Title Travis Hayes commented on JENKINS-32967 Re: Build Now/Schedule buttons fails with IE Any update on this issue? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38309) Make ForkScanner return Parallel Branches in same order as others
Title: Message Title Sam Van Oort closed an issue as Fixed Released as v2.4 Jenkins / JENKINS-38309 Make ForkScanner return Parallel Branches in same order as others Change By: Sam Van Oort Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38458) Mandate consistent iteration order for DepthFirstScanner
Title: Message Title Sam Van Oort updated JENKINS-38458 Released as v2.4 Jenkins / JENKINS-38458 Mandate consistent iteration order for DepthFirstScanner Change By: Sam Van Oort Status: In Review Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37396) java.io.NotSerializableException: groovy.sql.GroovyRowResult
Title: Message Title Joe Roberts edited a comment on JENKINS-37396 Re: java.io.NotSerializableException: groovy.sql.GroovyRowResult After some testing it would appear that, in order to complete successfully, sql.close() must be the last command in the script. Anything else causes either a groovy.sql.Sql or if you remove the "sql.close" command, a groovy.sql.GroovyRowResult java.io.NotSerializableException. [Perhaps related to this?|http://stackoverflow.com/questions/37864542/jenkins-pipeline-notserializableexception-groovy-json-internal-lazymap] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37396) java.io.NotSerializableException: groovy.sql.GroovyRowResult
Title: Message Title Joe Roberts commented on JENKINS-37396 Re: java.io.NotSerializableException: groovy.sql.GroovyRowResult After some testing it would appear that, in order to complete successfully, sql.close() must be the last command in the script. Anything else causes either a groovy.sql.Sql or if you remove the "sql.close" command, a groovy.sql.GroovyRowResult java.io.NotSerializableException. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38458) Mandate consistent iteration order for DepthFirstScanner
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38458 Re: Mandate consistent iteration order for DepthFirstScanner Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/graphanalysis/DepthFirstScanner.java src/main/java/org/jenkinsci/plugins/workflow/graphanalysis/package-info.java src/test/java/org/jenkinsci/plugins/workflow/graphanalysis/FlowScannerTest.java http://jenkins-ci.org/commit/workflow-api-plugin/bcd2e30a9a3e3c9a9364c47ffec04cfe715f41fc Log: Merge pull request #16 from jenkinsci/make-depthfirstscanner-obey-ordering-JENKINS-38458 Make DepthFirstScanner obey first-last parallel branch ordering JENKINS-38458 Compare: https://github.com/jenkinsci/workflow-api-plugin/compare/85d91e8e2e09...bcd2e30a9a3e Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38478) Allow the ability to tag specified file revisions with a label
Title: Message Title Matthew Smith created an issue Jenkins / JENKINS-38478 Allow the ability to tag specified file revisions with a label Issue Type: New Feature Assignee: Unassigned Components: p4-plugin, pipeline Created: 2016/Sep/23 9:54 PM Environment: p4 plugin 1.4.6 Jenkins ver. 1.651.2 Pipeline 2.4 Labels: p4 p4-plugin label tag Priority: Major Reporter: Matthew Smith In our pipeline, we deal with checking out multiple clients on individual nodes. It appears that p4tag associates the files of the client workspace created by the first call of checkout in the job, and subsequent checkouts do not update the view associated to the label. We need to be able to attach files to a label that are outside of the build workspace. For this reason, it would be helpful if the p4 plugin had the ability to attach specific files to a label, as opposed to being stuck with the view of the first client workspace that is created.
[JIRA] (JENKINS-38457) FlowGraphTable shows parallel branches out of order
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38457 Re: FlowGraphTable shows parallel branches out of order Code changed in jenkins User: Sam Van Oort Path: src/main/java/org/jenkinsci/plugins/workflow/support/visualization/table/FlowGraphTable.java http://jenkins-ci.org/commit/workflow-support-plugin/e0676fad9646031d05bd0dba0244cc6d00d4d106 Log: Revert "[FIXED JENKINS-38457] Go back to FlowGraphWalker for now." This reverts commit a61d54906f970854ae8ea52019282e5c91bb5ef1. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38458) Mandate consistent iteration order for DepthFirstScanner
Title: Message Title Sam Van Oort commented on JENKINS-38458 Re: Mandate consistent iteration order for DepthFirstScanner Addressed with https://github.com/jenkinsci/workflow-api-plugin/pull/16 (enforcing the same semi-loony iteration order as FlowGraphWalker, but at least that makes it fully compatible). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38458) Mandate consistent iteration order for DepthFirstScanner
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-38458 Mandate consistent iteration order for DepthFirstScanner Change By: Sam Van Oort DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order). Instead we should visit the branches in order for drop-in compatibility with FlowGraphWalkerThis will, incidentally, fix JENKINS- 38381 38457 . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38458) Mandate consistent iteration order for DepthFirstScanner
Title: Message Title Sam Van Oort started work on JENKINS-38458 Change By: Sam Van Oort Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38458) Mandate consistent iteration order for DepthFirstScanner
Title: Message Title Sam Van Oort updated JENKINS-38458 Jenkins / JENKINS-38458 Mandate consistent iteration order for DepthFirstScanner Change By: Sam Van Oort Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-33510) dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Title: Message Title
Sean Gilhooly commented on JENKINS-33510
Re: dir('foo') inside "docker.image().inside{}" does not affect CWD of launched processes
Given this is cataloged as a "Minor" issue, is there a workaround for this? This appears to render this plugin unusable from what I observe. My fairly simple script:
docker.image("...").inside("--args...") {
sh "gradle build"
}
can't get anywhere:
sh: /var/jenkins_home/workspace/job@tmp/durable-b85d7f08/pid: No such file or directory
sh: /var/jenkins_home/workspace/job@tmp/durable-b85d7f08/jenkins-log.txt: No such file or directory
sh: /var/jenkins_home/workspace/job@tmp/durable-b85d7f08/jenkins-result.txt: No such file or directory
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-37394) Add @Symbol("gradle") to Gradle's ToolDescriptor
Title: Message Title
SCM/JIRA link daemon commented on JENKINS-37394
Re: Add @Symbol("gradle") to Gradle's ToolDescriptor
Code changed in jenkins User: Andrew Bayer Path: build.gradle src/main/java/hudson/plugins/gradle/Gradle.java src/main/java/hudson/plugins/gradle/GradleInstallation.java http://jenkins-ci.org/commit/gradle-plugin/eabffa3a25374d8b6e851a7ffa95aadc81c28a6b Log: [FIXED JENKINS-37394] Add @Symbol annotations for step and tool. (#35)
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-36795) hp automation tools - pipeline enabled
Title: Message Title Daniel Martin commented on JENKINS-36795 Re: hp automation tools - pipeline enabled I would also like to know if there is any tracktion on this. Currently UFT isn't fit for a Devops env, and would like to understand what is being done to correct the issues. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38477) Can't see status icon in PR
Title: Message Title Artem Stasiuk resolved as Fixed Fixed by PR https://github.com/jenkinsci/github-pr-coverage-status-plugin/pull/2 in version 1.0.9 Jenkins / JENKINS-38477 Can't see status icon in PR Change By: Artem Stasiuk Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-38477) Can't see status icon in PR
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38477 Re: Can't see status icon in PR Code changed in jenkins User: Artem Stasiuk Path: src/main/java/com/github/terma/jenkins/githubprcoveragestatus/Message.java src/test/java/com/github/terma/jenkins/githubprcoveragestatus/CompareCoverageActionTest.java src/test/java/com/github/terma/jenkins/githubprcoveragestatus/MessageTest.java http://jenkins-ci.org/commit/github-pr-coverage-status-plugin/a1d2e342bc0d5b4fe678de0533f899da86348ad4 Log: Merge pull request #2 from jenkinsci/JENKINS-38477 JENKINS-38477 fix URL for status icon for some of Jenkins Compare: https://github.com/jenkinsci/github-pr-coverage-status-plugin/compare/ba36723daa65...a1d2e342bc0d Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38477) Can't see status icon in PR
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38477 Re: Can't see status icon in PR Code changed in jenkins User: terma Path: src/main/java/com/github/terma/jenkins/githubprcoveragestatus/Message.java src/test/java/com/github/terma/jenkins/githubprcoveragestatus/CompareCoverageActionTest.java src/test/java/com/github/terma/jenkins/githubprcoveragestatus/MessageTest.java http://jenkins-ci.org/commit/github-pr-coverage-status-plugin/dfc68fdc04face8eacb23bfb00aba6d5f83c2dfb Log: JENKINS-38477 fix URL for status icon for some of Jenkins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38477) Can't see status icon in PR
Title: Message Title Artem Stasiuk started work on JENKINS-38477 Change By: Artem Stasiuk Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38477) Can't see status icon in PR
Title: Message Title Artem Stasiuk created an issue Jenkins / JENKINS-38477 Can't see status icon in PR Issue Type: Task Assignee: Artem Stasiuk Components: github-pr-coverage-status Created: 2016/Sep/23 9:21 PM Labels: plugin Priority: Major Reporter: Artem Stasiuk Copied from original GitHub https://github.com/terma/github-pr-coverage-status/pull/14 Add Comment
[JIRA] (JENKINS-38458) Mandate consistent iteration order for DepthFirstScanner
Title: Message Title Sam Van Oort updated an issue Jenkins / JENKINS-38458 Mandate consistent iteration order for DepthFirstScanner Change By: Sam Van Oort DepthFirstScanner in the graphanalysis APIs works, but the API mandates that it visit the *first* node then the branches after (but in reverse order). Instead we should visit the last first, then then others, as with ForkScanner branches in JENKINS order for drop - 38309. in compatibility with FlowGraphWalker This will, incidentally, fix JENKINS-38381 too . Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37788) Pipeline Config: Eliminate the "isConstant" AST/JSON field
Title: Message Title
Andrew Bayer commented on JENKINS-37788
Re: Pipeline Config: Eliminate the "isConstant" AST/JSON field
Aaaand yup, specifically echo('['+acmeVar.baz()+']'), which is valid by the declarative subset, doesn't work right. We do need isConstant so we can know whether the value is a literal or not. If it's not a literal, we need to know that so we can evaluate it.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-36795) hp automation tools - pipeline enabled
Title: Message Title Sandeep Moras edited a comment on JENKINS-36795 Re: hp automation tools - pipeline enabled Its been a while without any update. There Is there any traction on this issue. With more and more companies using the Jenkins Pipeline process it would be helpful if we had something with work with. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-36795) hp automation tools - pipeline enabled
Title: Message Title Sandeep Moras commented on JENKINS-36795 Re: hp automation tools - pipeline enabled Its been a while without any update. There any traction on this issue. With more and more companies using the Jenkins Pipeline process it would be helpful if we had something with work with. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37788) Pipeline Config: Eliminate the "isConstant" AST/JSON field
Title: Message Title Andrew Bayer commented on JENKINS-37788 Re: Pipeline Config: Eliminate the "isConstant" AST/JSON field This needs more discussion with Kohsuke Kawaguchi to understand what it's intended for in the first place. I'm resurrecting my month-old experiments on removing it, but I think they broke. =) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-35987) Build Status marked as Pass when Build Player is Canceled
Title: Message Title John Rodenburg commented on JENKINS-35987 Re: Build Status marked as Pass when Build Player is Canceled This again, happened. These 3 print messages are in the log... yet another passing build. 09:21:43 DisplayProgressNotification: Build Failed 09:21:43 Error building Player because scripts had compiler error 09:21:44 *** Cancelled 'Build.Player.AndroidPlayer' in 10 seconds (10379 ms) No APK was created, yet build passed. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-35987) Build Status marked as Pass when Build Player is Canceled
Title: Message Title John Rodenburg updated an issue Jenkins / JENKINS-35987 Build Status marked as Pass when Build Player is Canceled Change By: John Rodenburg Priority: Major Critical Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38285) Add extension point for declarative config sections
Title: Message Title Andrew Bayer commented on JENKINS-38285 Re: Add extension point for declarative config sections So this may not actually be viable for a few reasons: Need to know when to execute whatever script the config section contributes - i.e., how do we know "Ok, run this snippet of code for the postBuild section after stages are done and before we leave the potential node block that stages are run in"? This is the biggie that I just can't figure out an answer to. Adding validation support via moving the methods in ModelValidator to the ModelASTElement extension in question is doable enough, but not ideal. Along the same lines, contributing to the JSON schema (or more accurately, generating the JSON schema dynamically from information provided by the various config sections) is probably doable but a bit ugly conceptually. ModelParser and JSONParser, on the other hand, would need complete rewrites. I'm not sure how we'd do that yet, but given the "when to execute" problem, I don't think it's worth it for me to invest much thought on this in particular yet. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-38476) Always use "-usenonexclusivelock" option
Title: Message Title Mustafa Ulu created an issue Jenkins / JENKINS-38476 Always use "-usenonexclusivelock" option Issue Type: Improvement Assignee: Raphael CHAUMIER Components: weblogic-deployer-plugin Created: 2016/Sep/23 8:50 PM Priority: Minor Reporter: Mustafa Ulu I believe WebLogic Deployer Plugin fits the definition of "-usenonexclusivelock" option perfectly: Deployment operation uses an existing lock, already acquired by the same user, on the domain. This option is helpful in environments where multiple deployment tools are used simultaneously and one of the tools has already acquired a lock on the domain configuration. https://docs.oracle.com/cd/E13222_01/wls/docs103/deployment/wldeployer.html Add Comment
[JIRA] (JENKINS-34637) pipeline DSL: timeout() does not work if withEnv() is enclosed
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-34637 pipeline DSL: timeout() does not work if withEnv() is enclosed Change By: Jesse Glick Component/s: workflow-basic-steps-plugin Component/s: workflow-durable-task-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38380) timeout around input does not work with submitter
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38380 timeout around input does not work with submitter Change By: Jesse Glick Labels: regression Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38380) timeout around input does not work with submitter
Title: Message Title Jesse Glick commented on JENKINS-38380 Re: timeout around input does not work with submitter Smells like a regression from the fix of JENKINS-37154 to me. canCancel() should have been true if running as SYSTEM; need to check it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38380) timeout around input does not work with submitter
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38380 timeout around input does not work with submitter Change By: Jesse Glick Component/s: workflow-basic-steps-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38475) Identify path filename if path/file name too long
Title: Message Title Ian Williams created an issue Jenkins / JENKINS-38475 Identify path filename if path/file name too long Issue Type: Improvement Assignee: redsolo Components: tfs-plugin Created: 2016/Sep/23 8:21 PM Priority: Minor Reporter: Ian Williams tfs-plugin 5.1.0, Jenkins 1.651.3 Glad to see plugin now fails if any path/filename too long. But the failure message does not provide the name of the path/file causing the failure. Makes it hard to identify the culprit since it can be any one of the files in a given directory. Add to error message the offending culprit value. Bonus appreciation if it would report ALL paths/files too long rather than immediate fail on first. FATAL: hudson.remoting.ProxyException: java.lang.RuntimeException: com.microsoft.tfs.core.clients.versioncontrol.exceptions.VersionControlException: com.microsoft.tfs.core.exceptions.TECoreException: The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters. Add Comment
[JIRA] (JENKINS-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title Jesse Glick commented on JENKINS-38092 Re: workflow-multibranch plugin doesn't use credentials when indexing the branches Not sure what the issue is, but anyway you probably want to install the BitBucket Branch Source plugin and use that instead. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38092 workflow-multibranch plugin doesn't use credentials when indexing the branches Change By: Jesse Glick Labels: git multibranch pipeline plugins Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38092 workflow-multibranch plugin doesn't use credentials when indexing the branches Change By: Jesse Glick Component/s: git-plugin Component/s: bitbucket-branch-source-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-34998) Make CMake plugin compatible with pipeline
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-34998 Make CMake plugin compatible with pipeline Change By: Martin Weber Labels: he pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38092) workflow-multibranch plugin doesn't use credentials when indexing the branches
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-38092 workflow-multibranch plugin doesn't use credentials when indexing the branches Change By: Jesse Glick Component/s: bitbucket-branch-source-plugin Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38147) Allow per-job Parameters for Multi-Branch
Title: Message Title Jesse Glick commented on JENKINS-38147 Re: Allow per-job Parameters for Multi-Branch Pretty sure this is a duplicate. Anyway, in short: no plans to write such an OSS feature, though CloudBees Jenkins Platform already offers it. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-34998) Make CMake plugin compatible with pipeline
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-34998 Make CMake plugin compatible with pipeline Change By: Martin Weber Labels: he pipeline Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38402) Allow not to build anything but still create the entries
Title: Message Title Jesse Glick resolved as Cannot Reproduce Already supported, check configuration options as well as a new properties step option with today’s Branch API plugin update. Jenkins / JENKINS-38402 Allow not to build anything but still create the entries Change By: Jesse Glick Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-37575) Jenkins node keeps sending the same logs indefinitely
Title: Message Title Jesse Glick commented on JENKINS-37575 Re: Jenkins node keeps sending the same logs indefinitely Unless it is reproducible from scratch I do not expect to spend time on it since I hope to rewrite this code as part of JENKINS-38381 anyway. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title
Martin Weber edited a comment on JENKINS-38449
Re: ZipExtractionInstaller not working behind proxy
Download is handled by {code:java}hudson.FilePath.installIfNecessaryFrom(URL, TaskListener, String){code} , which is part of jenkins core. So assigning it to jenkins core, adjusting title.BTW: Why don`t you just use the _Install from cmake.org_ installer?
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-38449) ZipExtractionInstaller not working behind proxy
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-38449 ZipExtractionInstaller not working behind proxy Change By: Martin Weber Summary: Custom cmake tool installer ZipExtractionInstaller not working behind proxy Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38449) Custom cmake tool installer not working behind proxy
Title: Message Title Martin Weber commented on JENKINS-38449 Re: Custom cmake tool installer not working behind proxy Download is handled by hudson.FilePath.installIfNecessaryFrom(URL, TaskListener, String) , which is part of jenkins core. So assigning it to jenkins core, adjusting title. BTW: Why don`t you just use the Install from cmake.org installer? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38114) Share help for RunWrapper
Title: Message Title Jesse Glick updated JENKINS-38114 Jenkins / JENKINS-38114 Share help for RunWrapper Change By: Jesse Glick Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38114) Share help for RunWrapper
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38114 Re: Share help for RunWrapper Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/resources/org/jenkinsci/plugins/workflow/cps/RunWrapperBinder/help.groovy src/main/resources/org/jenkinsci/plugins/workflow/cps/RunWrapperBinder/help.jelly src/test/java/org/jenkinsci/plugins/workflow/WorkflowJobNonRestartingTest.java src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/3f343691543f31d82935affa962d121913fbe0d7 Log: Merge pull request #69 from jglick/RunWrapper-help-JENKINS-38114 JENKINS-38114 Consolidated help for RunWrapper Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/d40b3dd4c00e...3f343691543f Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38457) FlowGraphTable shows parallel branches out of order
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38457 Re: FlowGraphTable shows parallel branches out of order Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStepTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/0ca8da72d9de73ccfdc58013f12bbee843c76108 Log: Revert "JENKINS-38457 Temporarily suppressing part of test which shows the regression." This reverts commit 4798a812cd7e749c2e272d2b9bbbdb5fc3a793f3. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38114) Share help for RunWrapper
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38114 Re: Share help for RunWrapper Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/resources/org/jenkinsci/plugins/workflow/cps/RunWrapperBinder/help.groovy src/main/resources/org/jenkinsci/plugins/workflow/cps/RunWrapperBinder/help.jelly src/test/java/org/jenkinsci/plugins/workflow/WorkflowJobNonRestartingTest.java src/test/java/org/jenkinsci/plugins/workflow/cps/SnippetizerTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/f7206f4348a3b57abab16943648039920d0e3307 Log: JENKINS-38114 Consolidated help for RunWrapper. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38457) FlowGraphTable shows parallel branches out of order
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38457 Re: FlowGraphTable shows parallel branches out of order Code changed in jenkins User: Jesse Glick Path: src/test/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStepTest.java http://jenkins-ci.org/commit/workflow-cps-plugin/4798a812cd7e749c2e272d2b9bbbdb5fc3a793f3 Log: JENKINS-38457 Temporarily suppressing part of test which shows the regression. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38449) Custom cmake tool installer not working behind proxy
Title: Message Title Martin Weber updated an issue Jenkins / JENKINS-38449 Custom cmake tool installer not working behind proxy Change By: Martin Weber Component/s: core Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-29952) Allow access to environment variables as Groovy variables
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29952 Re: Allow access to environment variables as Groovy variables Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/35a074c683b757b90cf651a1e37f19c66eed4421 Log: JENKINS-29952 Updated documentation. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-29952) Allow access to environment variables as Groovy variables
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29952 Re: Allow access to environment variables as Groovy variables Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/cps/EnvActionImpl/Binder/help.jelly http://jenkins-ci.org/commit/workflow-cps-plugin/4c44cc253825da00d98bb72e7c4cb8ee06a4fbd1 Log: Merge pull request #70 from jglick/env-help JENKINS-29952 Updated documentation Compare: https://github.com/jenkinsci/workflow-cps-plugin/compare/32c98dbbe541...4c44cc253825 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38114) Share help for RunWrapper
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38114 Re: Share help for RunWrapper Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.groovy src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.html src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepConfigTest.java http://jenkins-ci.org/commit/pipeline-build-step-plugin/bc5873391a3c4180d2a36ee837f78d19bad57f05 Log: Merge pull request #7 from jglick/RunWrapper-help-JENKINS-38114 JENKINS-38114 Consolidated help for RunWrapper Compare: https://github.com/jenkinsci/pipeline-build-step-plugin/compare/d3fb488c4750...bc5873391a3c Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38114) Share help for RunWrapper
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38114 Re: Share help for RunWrapper Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.groovy src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStep/help-wait.html src/test/java/org/jenkinsci/plugins/workflow/support/steps/build/BuildTriggerStepConfigTest.java http://jenkins-ci.org/commit/pipeline-build-step-plugin/7b9d1347db63db04fb86970e62d11ed0399c60ae Log: JENKINS-38114 Consolidated help for RunWrapper. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-36883) Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time
Title: Message Title Jason Davis commented on JENKINS-36883 Re: Jobs with “Exclude Changes” Polling Filter Not Syncing Latest at Build Time Hi Paul - I agree with you that the polling filter should only prevent builds from occurring on the changes in the filter path! That feature is working wonderfully, but there’s something else going on that’s causing files in the workspace spec to be sync’ed to _different _changelist levels after the Jenkins Quiet Period - and that started happening with v1.3.9 of the plugin. Up through 1.3.8, ALL files in a workspace spec did sync to the latest CL after a Quiet Period at build start time (without @now) – but that’s not happening any longer. Please see the above example. I explain there that, right now and without the use of @now in the workspace spec or P4 label setting, non-filtered files are currently being sync'ed to latest (CL 105), while filtered files are being sync'ed to trigger level (CL 100 instead of CL 103). I’ve confirmed this by testing with the above spec in a simple Jenkins job. Just make some checkins to files both in and out of a filtered path during a Quiet Period to see that they’re not synced to the latest CL at build start time. You suggested above in the Sept. 8 comment, that the build should sync to the CL at trigger time - not the CL at start time, so that other changes don't sneak in to the changes report. Also that @now should be used as a workaround. I’m further suggesting that @now shouldn’t be required to make the filtered files sync to latest at build start, because Jenkins has a configurable Quiet Period setting, which by design is to enable Devs to submit other changes after a trigger as an "oops" measure. If @now becomes required in the P4 Plugin label field or workspace spec to sync to latest after a Quiet Period, then that prevents use of other P4 labels I might like to use, essentially states that more configuration is required to use the Jenkins Quiet Period setting, would make the P4 plugin work by differently than all other SCM plugins I’m familiar with since I started using Jenkins around 8-9 years ago (TFS, SVN, Community Perforce), and the P4 plugin itself did not have this requirement until v1.3.9. In the end, I'm first hoping that ALL the files in the workspace spec are synced to the same and latest CL at build start time like it once did (and that’s the same CL that the changes also report uses) – and second, that the build should not require @now to deal with those changes checked in during the Jenkins Quiet Period because I believe that alters what one would expect from SCM plugins when using a Quiet Period (as well as other reasons mentioned in the above comments). Add Comment
[JIRA] (JENKINS-38457) FlowGraphTable shows parallel branches out of order
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38457 Re: FlowGraphTable shows parallel branches out of order Code changed in jenkins User: Jesse Glick Path: src/main/java/org/jenkinsci/plugins/workflow/support/visualization/table/FlowGraphTable.java http://jenkins-ci.org/commit/workflow-support-plugin/a61d54906f970854ae8ea52019282e5c91bb5ef1 Log: [FIXED JENKINS-38457] Go back to FlowGraphWalker for now. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38114) Share help for RunWrapper
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38114 Re: Share help for RunWrapper Code changed in jenkins User: Jesse Glick Path: src/main/resources/org/jenkinsci/plugins/workflow/support/steps/build/RunWrapper/help.html http://jenkins-ci.org/commit/workflow-support-plugin/51fb1621a07af19d5380244474dc6e4374c2a21c Log: JENKINS-38114 Consolidated help for RunWrapper. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-19121) Build pipeline plugin no longer prompts for parameters of parameterised job
Title: Message Title DEREK LU commented on JENKINS-19121 Re: Build pipeline plugin no longer prompts for parameters of parameterised job I made some change in my local as a customized workaround. Also I created a poll request "Provide an ability to enter build notes/parameters for a Manual step in the pipeline" https://github.com/geoffbullen/build-pipeline-plugin/pull/4 Hope it can be developed and included in a formal release. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38456) Job DSL API Reference is no longer working
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38456 Re: Job DSL API Reference is no longer working Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-api-viewer/src/assets/_javascript_s/Dsl.js job-dsl-api-viewer/src/assets/_javascript_s/templates/detail.hbs job-dsl-api-viewer/src/assets/_javascript_s/templates/pluginDetail.hbs job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JobDslPlugin.groovy http://jenkins-ci.org/commit/job-dsl-plugin/f8fc5fa5f18ad7f8c2b3f6b6c051c521631b6cf2 Log: Merge pull request #921 from daspilker/JENKINS-38456 JENKINS-38456 fixed problem with embedded API viewer when a plugin is not available in the Update Center Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/44a6a12913ed...f8fc5fa5f18a Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38456) Job DSL API Reference is no longer working
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-38456 Job DSL API Reference is no longer working Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38456) Job DSL API Reference is no longer working
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38456 Re: Job DSL API Reference is no longer working Code changed in jenkins User: Daniel Spilker Path: docs/Home.md job-dsl-api-viewer/src/assets/_javascript_s/Dsl.js job-dsl-api-viewer/src/assets/_javascript_s/templates/detail.hbs job-dsl-api-viewer/src/assets/_javascript_s/templates/pluginDetail.hbs job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/JobDslPlugin.groovy http://jenkins-ci.org/commit/job-dsl-plugin/f13eb073216e180320dc5df87436cae5dff4ccae Log: fixed problem with embedded API viewer when a plugin is not available in the Update Center [FIXES JENKINS-38456] Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37598) Inaccurate aggregation of multiple xmls containing case information about the same testsuite
Title: Message Title Zoltán Haindrich commented on JENKINS-37598 Re: Inaccurate aggregation of multiple xmls containing case information about the same testsuite Jesse Glick can you take a look at the update changes? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38474) Error after updating AWS SDK to 1.11.37
Title: Message Title
Raphael Couto created an issue
Jenkins / JENKINS-38474
Error after updating AWS SDK to 1.11.37
Issue Type:
Bug
Assignee:
Andrew Fitz Gibbon
Components:
codedeploy-plugin
Created:
2016/Sep/23 6:19 PM
Environment:
Jenkins: 2.23 CodeDeploy Plugin: 1.12 AWS SDK (working): 1.10.50 AWS SDK (error): 1.11.37
Priority:
Minor
Reporter:
Raphael Couto
Error after AWS SDK update Zipping files into {filename}.zip Uploading zip to s3://{bucket}/{filename} .zip Registering revision for application ' {appname} ERROR: Step ‘Deploy an application to AWS CodeDeploy’ aborted due to exception: java.lang.NoSuchMethodError: com.amazonaws.services.codedeploy.AmazonCodeDeployClient.registerApplicationRevision(Lcom/amazonaws/services/codedeploy/model/RegisterApplicationRevisionRequest;)V at com.amazonaws.codedeploy.AWSCodeDeployPublisher.registerRevision(AWSCodeDeployPublisher.java:388) at com.amazonaws.codedeploy.AWSCodeDeployPublisher.perform(AWSCodeDeployPublisher.java:226) at hudson.tasks.BuildStepMonitor$2.perform(BuildStepMonitor.java:32) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:720) at hudson.model.Build$BuildExecution.post2(Build.java:185) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:665) at hudson.model.Run.execute(Run.java:1745) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404) Finished: FAILURE
[JIRA] (JENKINS-38179) Authentication Error with GIT Client version 2.0.0
Title: Message Title Mark Waite edited a comment on JENKINS-38179 Re: Authentication Error with GIT Client version 2.0.0 One work around might be to switch from using the command line git implementation to use the JGit implementation. In "Global Tools Configuration" (Jenkins 2.x), you select "Git" and add "JGit" as an implementation. That then adds a "Git executable" pick list to your jobs which use git. From that pick list, choose "JGit". There are authentication cases which don't work with JGit, and there are some features which are not available in JGit (shallow clone, submodule support, and others), but for those cases where it works, it works reliably.Another work around might be to assist with the evaluation of [git client plugin pull request 216|https://github.com/jenkinsci/git-client-plugin/pull/216] which adds better authentication support to JGit by using a different library for http communication.The ultimate work around is to revert to the earlier version of the git client plugin and the git plugin. Another alternative is to investigate the issue and propose a pull request to fix the issue. I spent several hours last week at the Jenkins hackfest investigating and trying to understand the root of the issue, but was unable to find a final solution. This week I've had to work for my employer, rather than working on my open source hobby (the Jenkins git plugin and git client plugin). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-38179) Authentication Error with GIT Client version 2.0.0
Title: Message Title Mark Waite commented on JENKINS-38179 Re: Authentication Error with GIT Client version 2.0.0 One work around might be to switch from using the command line git implementation to use the JGit implementation. In "Global Tools Configuration" (Jenkins 2.x), you select "Git" and add "JGit" as an implementation. That then adds a "Git executable" pick list to your jobs which use git. >From that pick list, choose "JGit". There are authentication cases which don't work with JGit, and there are some features which are not available in JGit (shallow clone, submodule support, and others), but for those cases where it works, it works reliably. Another work around might be to assist with the evaluation of git client plugin pull request 216 which adds better authentication support to JGit by using a different library for http communication. The ultimate work around is to revert to the earlier version of the git client plugin and the git plugin. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38329) Errors on activity and branches tabs
Title: Message Title Thorsten Scherler edited a comment on JENKINS-38329 Re: Errors on activity and branches tabs I having issue on my system in certain circumstances and can see related issues It happens when on a multibranch activity tab and then pressing on the branch tab. Need to pin it down some more since it does not happens all the time. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38329) Errors on activity and branches tabs
Title: Message Title Thorsten Scherler commented on JENKINS-38329 Re: Errors on activity and branches tabs I having issue on my system in certain circumstances and can see related issues Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37379) Some real-time favorite card statuses are not accurate
Title: Message Title Cliff Meyers started work on JENKINS-37379 Change By: Cliff Meyers Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37831) Favoriting on Matrix style project broken
Title: Message Title Cliff Meyers updated JENKINS-37831 Jenkins / JENKINS-37831 Favoriting on Matrix style project broken Change By: Cliff Meyers Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37842) Log truncated for freestyle after following along
Title: Message Title Thorsten Scherler updated JENKINS-37842 Jenkins / JENKINS-37842 Log truncated for freestyle after following along Change By: Thorsten Scherler Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-37842) Log truncated for freestyle after following along
Title: Message Title Thorsten Scherler commented on JENKINS-37842 Re: Log truncated for freestyle after following along Michael Neale I have fixed that in JENKINS-37753 Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38056) Duration of running Pipeline is not live
Title: Message Title Thorsten Scherler updated JENKINS-38056 Jenkins / JENKINS-38056 Duration of running Pipeline is not live Change By: Thorsten Scherler Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38179) Authentication Error with GIT Client version 2.0.0
Title: Message Title Jeff Tresselt commented on JENKINS-38179 Re: Authentication Error with GIT Client version 2.0.0 I have the same problem. Using the latest GIT Client Plugin version 2.0.0, authentication fails on my Windows slaves. Authentication does not fail on my Linux (ubuntu) slaves, only on my Windows slaves. I had to revert back to the Git client plugin v1.21.0 to get things working again. This means I also had to revert the 'Git plugin' to version 2.6.0, so I cannot use the latest Git plugin v3.0.0 either. Is there any status on this issue...? Is there any possible workaround...? Thanks Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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.
