[JIRA] (JENKINS-61770) Directive-Generator Omits "Extensible Choice" Parameter
Title: Message Title Tim Black created an issue Jenkins / JENKINS-61770 Directive-Generator Omits "Extensible Choice" Parameter Issue Type: Improvement Assignee: Unassigned Components: extensible-choice-parameter-plugin Created: 2020-04-01 18:10 Environment: Jenkins ver. 2.190.3 Extensible Choice 1.6.0 Extended Choice 0.78 Priority: Major Reporter: Tim Black Directive-Generator on my Jenkins instance includes "Extended Choice" and other param types just fine, but does not include "Extensible Choice" Parameter type. Is this a documentation omission, or does Extensible Choice not support pipeline (declarative)? If it doesn't support declarative pipeline and this is the reason it's not in directive generator, I would like to see a reference to the scripted pipeline syntax somewhere in the documentation. Add Comment
[JIRA] (JENKINS-28382) workflow plugin: no opton to "Wipe Out Current Workspace"
Title: Message Title Tim Black edited a comment on JENKINS-28382 Re: workflow plugin: no opton to "Wipe Out Current Workspace" I don't see how this issue duplicates JENKINS-26138 Support workspaces for Pipeline jobs.I would like the ability to get the "Workspaces" --> "Wipe Out Current Workspace" option in the UI. I'm using Jenkins v2.190.3. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162818.1431535967000.9539.1584634080287%40Atlassian.JIRA.
[JIRA] (JENKINS-28382) workflow plugin: no opton to "Wipe Out Current Workspace"
Title: Message Title Tim Black commented on JENKINS-28382 Re: workflow plugin: no opton to "Wipe Out Current Workspace" I don't see how this issue duplicates JENKINS-26138 Support workspaces for Pipeline jobs. I would like the ability to get the "Workspaces" --> "Wipe Out Current Workspace" option in the UI. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.162818.1431535967000.8217.1584396840312%40Atlassian.JIRA.
[JIRA] (JENKINS-61461) Logger suggestions don't show all results as you type
Title: Message Title Tim Black created an issue Jenkins / JENKINS-61461 Logger suggestions don't show all results as you type Issue Type: Bug Assignee: Praqma Support Components: logging-plugin Created: 2020-03-12 16:13 Environment: Deban 9/Stretch Jenkins ver. 2.190.3 openjdk version "1.8.0_232" OpenJDK Runtime Environment (build 1.8.0_232-8u232-b09-1~deb9u1-b09) OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode) Plugin Versions: OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.6 Pipeline: Nodes and Processes (workflow-durable-task-step): 2.35 ruby-runtime (ruby-runtime): 0.12 Email Extension Plugin (email-ext): 2.68 CVS Plug-in (cvs): 2.14 Maven Integration plugin (maven-plugin): 3.4 Git Pipeline for Blue Ocean (blueocean-git-pipeline): 1.21.0 Run Condition Plugin (run-condition): 1.2 Pipeline: Stage Step (pipeline-stage-step): 2.3 Ant Plugin (ant): 1.10 LDAP Plugin (ldap): 1.21 Mercurial plugin (mercurial): 2.8 Pipeline: Groovy (workflow-cps): 2.80 REST API for Blue Ocean (blueocean-rest): 1.21.0 Git client plugin (git-client): 3.2.1 i18n for Blue Ocean (blueocean-i18n): 1.21.0 PAM Authentication plugin (pam-auth): 1.6 Pipeline: Multibranch (workflow-multibranch): 2.21 Handy Uri Templates 2.x API Plugin (handy-uri-templates-2-api): 2.1.8-1.0 Bitbucket Pipeline for Blue Ocean (blueocean-bitbucket-pipeline): 1.21.0 Extended Choice Parameter Plug-In (extended-choice-parameter): 0.78 GitHub plugin (github): 1.29.5 Server Sent Events (SSE) Gateway Plugin (sse-gateway): 1.20 Office 365 Connector (Office-365-Connector): 4.12.3 Favorite (favorite): 2.3.2 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.15 Pipeline SCM API for Blue Ocean (blueocean-pipeline-scm-api): 1.21.0 Blue Ocean Pipeline Editor (blueocean-pipeline-editor): 1.21.0 Matrix Authorization Strategy Plugin (matrix-auth): 2.5 Branch API Plugin (branch-api): 2.5.5 Docker Pipeline (docker-workflow): 1.22 categorized-view (categorized-view): 1.10 bouncycastle API Plugin (bouncycastle-api): 2.17 Pipeline Utility Steps (pipeline-utility-steps): 2.5.0 Command Agent Launcher Plugin (command-launcher): 1.4 Icon Shim Plugin (icon-shim): 2.0.3 JUnit Plugin (junit): 1.28 Config File Provider Plugin (config-file-provider): 3.6.2 Matrix Project Plugin (matrix-project): 1.14 Pub-Sub "light" Bus (pubsub-light): 1.13 Plugin Usage - Plugin (plugin-usage-plugin): 1.0 Pipeline implementation for Blue Ocean (blueocean-pipeline-api-impl): 1.21.0 Dashboard for Blue Ocean (blueocean-dashboard): 1.21.0 SSH Credentials Plugin (ssh-credentials): 1.18 Pipeline: Declarative (pipeline-model
[JIRA] (JENKINS-52264) Error while running pipeline job in docker
Title: Message Title Tim Black commented on JENKINS-52264 Re: Error while running pipeline job in docker This can manifest in various ways - for me it first appeared to be this bug, and only after enabling LAUNCH_DIAGNOSTICS did we see evidence that lead us here, which was the actual culprit. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192029.153025197.5713.1583946000263%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title Tim Black commented on JENKINS-60039 Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container For me, this issue turned out to be an empty environment variable set in Jenkins global properties. This. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.5708.1583945881080%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in an error due to an unmet dependency between Durable Task and Pipeline: Nodes and Processes. So I went back to DT v1.33 since a _lot_ of plugins depend on Nodes and Processes, and I'm not immediately sure how to resolve this dependency heck.In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. UPDATE: I have changed the global durability setting to "MAX_SURVIVABILITY" from "PERFORMANCE_OPTIMIZED" and am still getting the same error.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.7036.1583427780734%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in an error due to an unmet dependency between Durable Task and Pipeline: Nodes and Processes. So I went back to DT v1.33 since I'm not immediately sure how to resolve this dependency heck.In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. UPDATE: I have changed the global durability setting to "MAX_SURVIVABILITY" from " perf optimized PERFORMANCE_OPTIMIZED " and am still getting the same error.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.7030.1583427660244%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in an error due to an unmet dependency between Durable Task and Pipeline: Nodes and Processes. So I went back to DT v1.33 since I'm not immediately sure how to resolve this dependency heck.In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. UPDATE: I have changed the global durability setting to " max durability MAX_SURVIVABILITY " from "perf optimized" and am still getting the same error.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.7024.1583427600293%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in an error due to an unmet dependency between Durable Task and Pipeline: Nodes and Processes. So I went back to DT v1.33 since I'm not immediately sure how to resolve this dependency heck.In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. UPDATE: I have changed the global durability setting to "max durability" from "perf optimized" and am still getting the same error.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202866.1572877026000.7014.1583426640243%40Atlassian.JIRA.
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
REverting Reverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below an error .UPDATE: I see on our "manage plugin" page that this error is due to an unmet dependency : " between Durable Task and Pipeline: Nodes and Processes version 2 . 35" "Durable Task Plugin version 1 So I went back to DT v1 . 29 is older than required. To fix, install version 1. 33 or later since I'm not immediately sure how to resolve this dependency heck . " Note In the meantime, I have noticed that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. __ {code:java}Running in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] End of Pipelinejava.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiblePlaybook, ansibleVault, build, checkout, emailext, emailextrecipients, findFiles, git, input, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, lock, milestone, nodesByLabel, office365ConnectorSend, parallel, properties, publishHTML, readCSV, readJSON, readManifest, readMavenPom, readProperties, readTrusted, readYaml, resolveScm, sha1, slackSend, slackUploadFile, stage, svn, tee, timestamps, tm, touch, unzip, withCredentials, writeCSV, writeJSON, writeMavenPom, writeYaml, xunit, zip] or symbols [AUnit, BoostTest, CTest, CUnit, Check, CppTest, CppUnit, Custom, FPCUnit, GoogleTest, JUnit, MSTest, MbUnit, NUnit2, NUnit3, PHPUnit, QtTest, UnitTest, Valgrind, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, authorizationMatrix, batchFile, bitbucket, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildAllBranches, buildAnyBranches, buildButton, buildChangeRequests, buildDiscarder, buildNamedBranches, buildNoneBranches, buildParameter, buildRegularBranches, buildSelector, buildTags, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, configFile, configFileProvider, copyArtifactPermission, copyArtifacts, credentials, cron, crumb, culprits, defaultView, demand, developers, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, embUnit, envInject, envVars, exact, extendedChoice, failed, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubForkDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, globalConfigFiles, gtester, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, lastCompleted, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, lastSuccessful, lastWithArtifacts, latestSavedBuild, legacy, legacySCM, list, local, location, logRotator, loggedInUsers
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below error ( . UPDATE: I see on our "manage plugin" page that this error is due to an unmet dependency: " Pipeline: Nodes and Processes version 2. 35Durable 35" "Durable Task Plugin version 1.29 is older than required. To fix, install version 1.33 or later. ) " . Note that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. __ {code:java}Running in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] End of Pipelinejava.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiblePlaybook, ansibleVault, build, checkout, emailext, emailextrecipients, findFiles, git, input, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, lock, milestone, nodesByLabel, office365ConnectorSend, parallel, properties, publishHTML, readCSV, readJSON, readManifest, readMavenPom, readProperties, readTrusted, readYaml, resolveScm, sha1, slackSend, slackUploadFile, stage, svn, tee, timestamps, tm, touch, unzip, withCredentials, writeCSV, writeJSON, writeMavenPom, writeYaml, xunit, zip] or symbols [AUnit, BoostTest, CTest, CUnit, Check, CppTest, CppUnit, Custom, FPCUnit, GoogleTest, JUnit, MSTest, MbUnit, NUnit2, NUnit3, PHPUnit, QtTest, UnitTest, Valgrind, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, authorizationMatrix, batchFile, bitbucket, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildAllBranches, buildAnyBranches, buildButton, buildChangeRequests, buildDiscarder, buildNamedBranches, buildNoneBranches, buildParameter, buildRegularBranches, buildSelector, buildTags, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, configFile, configFileProvider, copyArtifactPermission, copyArtifacts, credentials, cron, crumb, culprits, defaultView, demand, developers, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, embUnit, envInject, envVars, exact, extendedChoice, failed, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubForkDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, globalConfigFiles, gtester, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, lastCompleted, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, lastSuccessful, lastWithArtifacts, latestSavedBuild, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, modernSCM, myView, nodeProperties, nonInheriting, none, office365Con
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below error (UPDATE:I see on our "manage plugin" page that this error is due to an unmet dependency:Pipeline: Nodes and Processes version 2 . 35Durable Task Plugin version 1.29 is older than required. To fix, install version 1.33 or later.). Note that we are using PERFORMANCE_OPTIMIZED durability level for this job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. __ {code:java}Running in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] End of Pipelinejava.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiblePlaybook, ansibleVault, build, checkout, emailext, emailextrecipients, findFiles, git, input, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, lock, milestone, nodesByLabel, office365ConnectorSend, parallel, properties, publishHTML, readCSV, readJSON, readManifest, readMavenPom, readProperties, readTrusted, readYaml, resolveScm, sha1, slackSend, slackUploadFile, stage, svn, tee, timestamps, tm, touch, unzip, withCredentials, writeCSV, writeJSON, writeMavenPom, writeYaml, xunit, zip] or symbols [AUnit, BoostTest, CTest, CUnit, Check, CppTest, CppUnit, Custom, FPCUnit, GoogleTest, JUnit, MSTest, MbUnit, NUnit2, NUnit3, PHPUnit, QtTest, UnitTest, Valgrind, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, authorizationMatrix, batchFile, bitbucket, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildAllBranches, buildAnyBranches, buildButton, buildChangeRequests, buildDiscarder, buildNamedBranches, buildNoneBranches, buildParameter, buildRegularBranches, buildSelector, buildTags, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, configFile, configFileProvider, copyArtifactPermission, copyArtifacts, credentials, cron, crumb, culprits, defaultView, demand, developers, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, embUnit, envInject, envVars, exact, extendedChoice, failed, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubForkDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, globalConfigFiles, gtester, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, lastCompleted, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, lastSuccessful, lastWithArtifacts, latestSavedBuild, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, modernSCM, myView, nodeProperties, nonInheriting, none, office365ConnectorSend, office365Connect
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer \{ sh }, results in the below error. Note that we are using PERFORMANCE_OPTIMIZED durability level for this : job. That seems relevant, but I don't know enough to connect the dots. Also what seems relevant is that this behavior started after a reboot of the Jenkins master _while a job downstream of this test job was running on a_ slave. From what I've read about Durable Task plugin, its purpose is to enable nodes to manage/monitor processes running on other nodes. This smells rotten. Please enlighten me if you can connect any of these dots. __ {code:java}Running in Durability level: PERFORMANCE_OPTIMIZED[Pipeline] Start of Pipeline[Pipeline] End of Pipelinejava.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiblePlaybook, ansibleVault, build, checkout, emailext, emailextrecipients, findFiles, git, input, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, lock, milestone, nodesByLabel, office365ConnectorSend, parallel, properties, publishHTML, readCSV, readJSON, readManifest, readMavenPom, readProperties, readTrusted, readYaml, resolveScm, sha1, slackSend, slackUploadFile, stage, svn, tee, timestamps, tm, touch, unzip, withCredentials, writeCSV, writeJSON, writeMavenPom, writeYaml, xunit, zip] or symbols [AUnit, BoostTest, CTest, CUnit, Check, CppTest, CppUnit, Custom, FPCUnit, GoogleTest, JUnit, MSTest, MbUnit, NUnit2, NUnit3, PHPUnit, QtTest, UnitTest, Valgrind, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, authorizationMatrix, batchFile, bitbucket, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildAllBranches, buildAnyBranches, buildButton, buildChangeRequests, buildDiscarder, buildNamedBranches, buildNoneBranches, buildParameter, buildRegularBranches, buildSelector, buildTags, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, configFile, configFileProvider, copyArtifactPermission, copyArtifacts, credentials, cron, crumb, culprits, defaultView, demand, developers, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, embUnit, envInject, envVars, exact, extendedChoice, failed, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubForkDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, globalConfigFiles, gtester, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, lastCompleted, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, lastSuccessful, lastWithArtifacts, latestSavedBuild, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, modernSCM, myView, nodeProperties, nonInheriting, none, office365ConnectorSend, office365ConnectorWebhooks, overrideIndexTriggers, paneStatus, parameters, passed, password, pattern, permalink, permanent, pipelineTriggers, plainText, plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, quietPeriod, rate
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black commented on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
REverting DT plugin to v1.29, restarting Jenkins, and re building a test job that uses withDockerContainer { sh }, results in this:
Running in Durability level: PERFORMANCE_OPTIMIZED
[Pipeline] Start of Pipeline
[Pipeline] End of Pipeline
java.lang.NoSuchMethodError: No such DSL method 'pipeline' found among steps [ansiblePlaybook, ansibleVault, build, checkout, emailext, emailextrecipients, findFiles, git, input, jiraComment, jiraIssueSelector, jiraSearch, junit, library, libraryResource, load, lock, milestone, nodesByLabel, office365ConnectorSend, parallel, properties, publishHTML, readCSV, readJSON, readManifest, readMavenPom, readProperties, readTrusted, readYaml, resolveScm, sha1, slackSend, slackUploadFile, stage, svn, tee, timestamps, tm, touch, unzip, withCredentials, writeCSV, writeJSON, writeMavenPom, writeYaml, xunit, zip] or symbols [AUnit, BoostTest, CTest, CUnit, Check, CppTest, CppUnit, Custom, FPCUnit, GoogleTest, JUnit, MSTest, MbUnit, NUnit2, NUnit3, PHPUnit, QtTest, UnitTest, Valgrind, all, always, ant, antFromApache, antOutcome, antTarget, apiToken, architecture, archiveArtifacts, artifactManager, authorizationMatrix, batchFile, bitbucket, booleanParam, brokenBuildSuspects, brokenTestsSuspects, buildAllBranches, buildAnyBranches, buildButton, buildChangeRequests, buildDiscarder, buildNamedBranches, buildNoneBranches, buildParameter, buildRegularBranches, buildSelector, buildTags, caseInsensitive, caseSensitive, certificate, choice, choiceParam, clock, cloud, command, configFile, configFileProvider, copyArtifactPermission, copyArtifacts, credentials, cron, crumb, culprits, defaultView, demand, developers, disableConcurrentBuilds, disableResume, dockerCert, downloadSettings, downstream, dumb, durabilityHint, embUnit, envInject, envVars, exact, extendedChoice, failed, file, fileParam, filePath, fingerprint, frameOptions, freeStyle, freeStyleJob, fromScm, fromSource, git, gitBranchDiscovery, gitHubBranchDiscovery, gitHubBranchHeadAuthority, gitHubForkDiscovery, gitHubSshCheckout, gitHubTagDiscovery, gitHubTrustContributors, gitHubTrustEveryone, gitHubTrustNobody, gitHubTrustPermissions, gitParameter, gitTagDiscovery, github, githubPush, globalConfigFiles, gtester, headRegexFilter, headWildcardFilter, hyperlink, hyperlinkToModels, inheriting, inheritingGlobal, installSource, jdk, jdkInstaller, jgit, jgitapache, jnlp, jobName, lastCompleted, lastDuration, lastFailure, lastGrantedAuthorities, lastStable, lastSuccess, lastSuccessful, lastWithArtifacts, latestSavedBuild, legacy, legacySCM, list, local, location, logRotator, loggedInUsersCanDoAnything, masterBuild, maven, maven3Mojos, mavenErrors, mavenMojos, mavenWarnings, modernSCM, myView, nodeProperties, nonInheriting, none, office365ConnectorSend, office365ConnectorWebhooks, overrideIndexTriggers, paneStatus, parameters, passed, password, pattern, permalink, permanent, pipelineTriggers, plainText, plugin, pollSCM, projectNamingStrategy, proxy, queueItemAuthenticator, quietPeriod, rateLimitBuilds, recipients, regex, requestor, run, runParam, sSHLauncher, schedule, scmRetryCount, scriptApproval, scriptApprovalLink, search, security, shell, skipped, slackNotifier, slave, sourceRegexFilter, sourceWildcardFilter, specific, ssh, sshUserPrivateKey, stackTrace, standard, status, string, stringParam, swapSpace, text, textParam, tmpSpace, toolLoc
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black edited a comment on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
We're having same problem, but it's not yet clear what change caused the behavior. We are on durable task plugin v1.33, and [Jenkins ver. 2.190.3|https://jenkins.io/], however we have not updated this recently to my knowledge (and I haven't been able to find plugin update history anywhere - any advice?) . The signature of the build failures is that the `withDockerContainer` step completes successfully, and the pipeline begins to run the sh command (the first step in the `withDockerContainer` clause) and there's no apparent activity (other than the seemingly normal output in the durable task plugin loggers) for 5 minutes, then the failure message as the OP here. Here is what the durable task loggers output during those 5 minutes: ``` {code:java} Mar 05, 2020 7:03:57 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop Mar 05, 2020 7:03:57 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep still running in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop on {code} ``` After 5 minutes, I then see: ``` {code:java} Mar 05, 2020 7:05:12 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepcalling close with nl=trueMar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepJENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[101:sh]: Owner[TesiraFirmwareNG OwnerTesiraFirmwareNG /develop/42:TesiraFirmwareNG/develop #42 ] Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@722b273bMar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScriptlaunching [nohup, sh, - c, ( \ { while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859' -a \ ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt'; wait) >& - 2>&- &]Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunched taskMar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStepJENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[102:sh]: Owner[TesiraFirmwareNG OwnerTesiraFirmwareNG /develop/42:TesiraFirmwareNG/develop #42 ] Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskSteplaunching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@460eddedMar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScriptlaunching [nohup, sh, - c, ( \ { while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a
[JIRA] (JENKINS-60039) durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
Title: Message Title
Tim Black commented on JENKINS-60039
Re: durable-task v1.33 breaks sh steps in pipeline when running in a Docker container
We're having same problem, but it's not yet clear what change caused the behavior. We are on durable task plugin v1.33, however we have not updated this recently to my knowledge (and I haven't been able to find plugin update history anywhere - any advice?) The signature of the build failures is that the `withDockerContainer` step completes successfully, and the pipeline begins to run the sh command (the first step in the `withDockerContainer` clause) and there's no apparent activity (other than the seemingly normal output in the durable task plugin loggers) for 5 minutes, then the failure message as the OP here. Here is what the durable task loggers output during those 5 minutes: ``` Mar 05, 2020 7:03:57 AM FINER org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep seems to be online so using /var/lib/jenkins/workspace/TesiraFirmwareNG_develop Mar 05, 2020 7:03:57 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep still running in /var/lib/jenkins/workspace/TesiraFirmwareNG_develop on ``` After 5 minutes, I then see: ``` Mar 05, 2020 7:05:12 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep calling close with nl=true Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[101:sh]:OwnerTesiraFirmwareNG/develop/42:TesiraFirmwareNG/develop #42 Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@722b273b Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript launching [nohup, sh, c, ({ while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859' -a ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt'; sleep 3; done } & jsc=durable-97017349f4d4de030acf9aecc2fb49fa; JENKINS_SERVER_COOKIE=$$jsc 'sh' -xe '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/script.sh' > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-log.txt' 2>&1; echo $$? > '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp'; mv '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt.tmp' '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-cc6ad859/jenkins-result.txt'; wait) >& 2>&- &] Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep launched task Mar 05, 2020 7:05:14 AM FINEST org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep JENKINS-34021: DurableTaskStep.Execution.listener present in CpsStepContext[102:sh]:OwnerTesiraFirmwareNG/develop/42:TesiraFirmwareNG/develop #42 Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep launching task against hudson.remoting.LocalChannel@41a7fb38 using hudson.Launcher$LocalLauncher@460edded Mar 05, 2020 7:05:14 AM FINE org.jenkinsci.plugins.durabletask.BourneShellScript launching [nohup, sh, c, ({ while [ -d '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0' -a ! -f '/var/lib/jenkins/workspace/TesiraFirmwareNG_develop-tmp/durable-a359e9b0/jenkins-result.txt' ]; do touch '/var/lib/jenkins/workspace/TesiraF
[JIRA] (JENKINS-61315) Add documentation for declarative pipeline support.
Title: Message Title Tim Black created an issue Jenkins / JENKINS-61315 Add documentation for declarative pipeline support. Issue Type: Bug Assignee: Kristy Hughes Components: atlassian-bitbucket-server-integration-plugin Created: 2020-03-03 22:30 Environment: Bitbucket Server 6.10.1 and Jenkins 2.190.3, with Bitbucket Server Integration plugin 1.1.0. Priority: Minor Reporter: Tim Black I was under the impression (from the release notes) that this plugin offered more configurable runtime functionality through declarative pipelines than is documented. The info pages for this plugin only describe how to connect Jenkins with Bitbucket and to set up a job that uses a Bitbucket repo. It does mention that build status is automatically updated in Bitbucket once the association has been made, but there is no documentation or elaboration of where this is posted or how this status is used. Is there any support for multibranch pipeline? I would like to implement Merge Checks in Bitbucket PRs which would run the corresponding multibranch pipeline build for the hypothetically-merged branch, and would use the result as a Merge Check, preventing merges when the jenkins build is not Successful. This plugin does not appear to help with this. Am I missing something?
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Tim Black edited a comment on JENKINS-51307
Re: Declarative pipeline and docker entrypoint
[~sschuberth], regarding your comment on using `cat` as a docker command, I see in the OP and in my own pipeline examples that the `cat` command is specified at the end of `docker run` and I cannot figure out why. Any info would be helpful.For example, the following pipeline code: {code:java}docker_image.inside("") { ... }{code} results in the following docker run command, which has inserted a {{cat}} command at the end. {code:java}docker run -t -d -u 118:124 cat {code}I believe this might be the reason why when I specify a CMD and/or ENTRYPOINT in our Dockerfile, it isn't working. Perhaps this is inserted by Jenkins under some circumstance? UPDATE: I have since found this PR: [https://github.com/jenkinsci/docker-workflow-plugin/pull/116] which discussion confirms the explicit forcing of CMD to `cat`.It is still woefully unclear to me how to specify, in a Dockerfile, how to run a command every time the docker image is run, when using Jenkins/Docker "inside()" pipeline.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190642.152632149.14.1579125242406%40Atlassian.JIRA.
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Tim Black edited a comment on JENKINS-51307
Re: Declarative pipeline and docker entrypoint
[~sschuberth], regarding your comment on using `cat` as a docker command, I see in the OP and in my own pipeline examples that the `cat` command is specified at the end of `docker run` and I cannot figure out why. Any info would be helpful.For example, the following pipeline code: {code:java}docker_image.inside("") { ... }{code} results in the following docker run command, which has inserted a {{cat}} command at the end. {code:java}docker run -t -d -u 118:124 cat {code}I believe this might be the reason why when I specify a CMD and/or ENTRYPOINT in our Dockerfile, it isn't working. Perhaps this is inserted by Jenkins under some circumstance?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190642.152632149.8998.1579123680488%40Atlassian.JIRA.
[JIRA] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title
Tim Black commented on JENKINS-51307
Re: Declarative pipeline and docker entrypoint
Sebastian Schuberth, regarding your comment on using `cat` as a docker command, I see in the OP and in my own pipeline examples that the `cat` command is specified at the end of `docker run` and I cannot figure out why. Any info would be helpful. For example, the following pipeline code:
docker_image.inside("") { ... }
results in the following docker run command, which has inserted a cat command at the end.
docker run -t -d -u 118:124 cat
I believe this might be the reason why when I specify a CMD and/or ENTRYPOINT in our Dockerfile, it isn't working. Perhaps this is inserted by Jenkins under some circumstance?
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view th
[JIRA] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the
Title: Message Title Tim Black edited a comment on JENKINS-32231 Re: Rendering HTML file from build artifacts is ignoring the
[JIRA] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the
Title: Message Title Tim Black edited a comment on JENKINS-32231 Re: Rendering HTML file from build artifacts is ignoring the
[JIRA] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the
Title: Message Title Tim Black edited a comment on JENKINS-32231 Re: Rendering HTML file from build artifacts is ignoring the
[JIRA] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the
Title: Message Title Tim Black edited a comment on JENKINS-32231 Re: Rendering HTML file from build artifacts is ignoring the
[JIRA] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the
Title: Message Title Tim Black edited a comment on JENKINS-32231 Re: Rendering HTML file from build artifacts is ignoring the
[JIRA] (JENKINS-32231) Rendering HTML file from build artifacts is ignoring the
Title: Message Title Tim Black commented on JENKINS-32231 Re: Rendering HTML file from build artifacts is ignoring the
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black commented on JENKINS-6334 Re: Support for displaying changesets in submodule updates Thanks for your attention, Mark Waite. I am not a Java developer, but I've got the experience to make a positive contribution here, at least from the test and integration angle. I looked through the [Beginners Guide To Contributing|https://wiki.jenkins.io/display/JENKINS/Beginners+Guide+to+Contributing], but I'm having trouble finding information on best practices for authoring such tests and for what resources to use for running the tests. The best lead I could find there was mention of [the jenkins-infra project|https://github.com/jenkins-infra/jenkins-infra], which contains configuration management tools that I'm guessing is how tests are expected to be run. Am I on the right track? Can you point me to any better docs, or your personal suggestions? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136429.1271845294000.1807.1575584520708%40Atlassian.JIRA.
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black edited a comment on JENKINS-6334 Re: Support for displaying changesets in submodule updates +Update+I have read [~markewaite]'s comment above and see that there are no PRs related to this issue. I'd be happy to contribute as this is a high value, low-hanging fruit in my opinion.However, I am not a java developer, and from Mark's comments this task is largely that of backfilling a void of automated tests covering submodules, to justify any _consideration_ of a PR that touches submodules. This is of course most unfortunate.I wonder if [~markewaite] still feels this way, however, since [several of the recent releases show submodule changes|[https://github.com/jenkinsci/git-plugin/releases] . | [ https://github.com/jenkinsci/git-plugin/releases] ] . +Original Comment+I have updated to [Jenkins ver. 2.190.3|https://jenkins.io/], am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try [~eprstov]'s solution, but I do not see an "sbm" branch here: [https://github.com/jenkinsci/git-plugin/branches]. I'm guessing it's just gone as this is a year later, and my best bet is to use the 4.0.0 tag.Has anyone else made any progress to getting a PR submitted for [~eprstov] patch (wherever it is)? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this gr
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black edited a comment on JENKINS-6334 Re: Support for displaying changesets in submodule updates +Update+I have read [~markewaite]'s comment above and see that there are no PRs related to this issue. I'd be happy to contribute as this is a high value, low-hanging fruit in my opinion.However, I am not a java developer, and from Mark's comments this task is largely that of backfilling a void of automated tests covering submodules, to justify any _consideration_ of a PR that touches submodules. This is of course most unfortunate.I wonder if [~markewaite] still feels this way, however, since [several of the recent releases show submodule changes|[https://github.com/jenkinsci/git-plugin/releases] ] . |https://github.com/jenkinsci/git-plugin/releases] +Original Comment+I have updated to [Jenkins ver. 2.190.3|https://jenkins.io/], am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try [~eprstov]'s solution, but I do not see an "sbm" branch here: [https://github.com/jenkinsci/git-plugin/branches]. I'm guessing it's just gone as this is a year later, and my best bet is to use the 4.0.0 tag.Has anyone else made any progress to getting a PR submitted for [~eprstov] patch (wherever it is)? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group a
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black edited a comment on JENKINS-6334 Re: Support for displaying changesets in submodule updates +Update+ I have read [~markewaite]'s comment above and see that there are no PRs related to this issue. I'd be happy to contribute as this is a high value, low-hanging fruit in my opinion.However, I am not a java developer, and from Mark's comments this task is largely that of backfilling a void of automated tests covering submodules, to justify any _consideration_ of a PR that touches submodules. This is of course most unfortunate.I wonder if [~markewaite] still feels this way, however, since [several of the recent releases show submodule changes|[https://github.com/jenkinsci/git-plugin/releases]].+Original Comment+I have updated to [Jenkins ver. 2.190.3|https://jenkins.io/], am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try Yakov [~eprstov] 's solution, but I do not see an "sbm" branch here: [https://github.com/jenkinsci/git-plugin/branches]. What reference do I need to fetch to build 'm guessing it's just gone as this ? is a year later, and my best bet is to use the 4.0.0 tag. Has anyone else made any progress to getting a PR submitted for [~eprstov] patch (wherever it is)? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black commented on JENKINS-6334 Re: Support for displaying changesets in submodule updates I have updated to Jenkins ver. 2.190.3, am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try Yakov's solution, but I do not see an "sbm" branch here: https://github.com/jenkinsci/git-plugin/branches. What reference do I need to fetch to build this? Has anyone else made any progress to getting a PR submitted for Yakov's patch (wherever it is)? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136429.1271845294000.876.1575501302188%40Atlassian.JIRA.
[JIRA] (JENKINS-6334) Support for displaying changesets in submodule updates
Title: Message Title Tim Black edited a comment on JENKINS-6334 Re: Support for displaying changesets in submodule updates I have updated to [Jenkins ver. 2.190.3|https://jenkins.io/], am using Git plugin 4.0.0, Git Client Plugin 3.0.0, and have updated my multibranch pipeline job config to recursively update submodules. In the resulting build "changes" it prints the name of the changed submodule, but does not include the changelog for it. I would like to try Yakov's solution, but I do not see an "sbm" branch here: [https://github.com/jenkinsci/git-plugin/branches]. What reference do I need to fetch to build this?Has anyone else made any progress to getting a PR submitted for Yakov's [~eprstov] patch (wherever it is)? Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.136429.1271845294000.878.1575501302324%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Tim Black edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
[~peddanet] [~jglick] would you post a code example of how you invoke printThrowable, successfully? I'm having trouble finding documentation for the hudson/jenkins functions. (A link would be nice?) Would it be something like this:{code:java}node() { try { throw "error" } catch (err) { hudson.Functions.printThrowable(err) } }{code}?? Is this function available in default (open source) installations of Jenkins? Do I need to also import anything to make this work?FWIW, I also found some good examples [here|[https://code-maven.com/jenkins]]. Thanks.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182865.1497172331000.399.1571938440487%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Tim Black edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
{code:java} {code} [~peddanet] [~jglick] would you post a code example of how you invoke printThrowable, successfully? I'm having trouble finding documentation for the hudson/jenkins functions. (A link would be nice?) Would it be something like this:{code:java}node() { try { throw "error" } catch (err) { hudson.Functions.printThrowable(err) } }{code}??I also found some good examples [here|[https://code-maven.com/jenkins]]. Thanks.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182865.1497172331000.391.1571938380602%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Tim Black edited a comment on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
{code:java} {code} [~peddanet] [~jglick] would you post a code example of how you invoke printThrowable, successfully? I'm having trouble finding documentation for the hudson/jenkins functions. (A link would be nice?) Would it be something like this: {code:java} node() { try { throw "error" }catch (err) \ { hudson.Functions.printThrowable(err) } } {code }??I also found some good examples [here|[https://code-maven.com/jenkins]]. Thanks.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182865.1497172331000.389.1571938380566%40Atlassian.JIRA.
[JIRA] (JENKINS-44808) Unable to print stacktrace on jenkins pipeline
Title: Message Title
Tim Black commented on JENKINS-44808
Re: Unable to print stacktrace on jenkins pipeline
Peter Wein Jesse Glick would you post a code example of how you invoke printThrowable, successfully? I'm having trouble finding documentation for the hudson/jenkins functions. (A link would be nice?) Would it be something like this: node() { try { throw "error" } catch (err) { hudson.Functions.printThrowable(err) } } ?? I also found some good examples [here|https://code-maven.com/jenkins]. Thanks.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182865.1497172331000.374.1571938080774%40Atlassian.JIRA.
