[JIRA] (JENKINS-60084) The WORKSPACE variable is not correct when concurrent build
Title: Message Title hir bale updated an issue Jenkins / JENKINS-60084 The WORKSPACE variable is not correct when concurrent build Change By: hir bale Summary: The WORKSPACE variable is not corrent correct when concurrent build 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.202927.1573120749000.1540.1573803300219%40Atlassian.JIRA.
[JIRA] (JENKINS-58648) Dependency-check publisher 5.0.2 does not show Results
Title: Message Title Horst Krause edited a comment on JENKINS-58648 Re: Dependency-check publisher 5.0.2 does not show Results Same for us, when updating from DependencyCheck v4 to v5.It looks like the default path for report search was "**/dependency-check-report.xml" in v4 and has changed to "dependency-check-report.xml" in v5.We had this field empty in all our job configs. For v4 this was fine. With v5 the reports are not found any more and additionally when a job is triggered the empty report path field is changed automatically to "dependency-check-report.xml".So our solution was to change the report path in all jobs to "**/dependency-check-report.xml". Now the reports are found again. Update: I realized that [https://wiki.jenkins.io/display/JENKINS/OWASP+Dependency-Check+Plugin] announces a 5.0.2 in july which "Changed the default artifact pattern to **/dependency-check-report.xml". But we are still running 5.0.1 because the 5.0.2 is not available in our jenkins 2.190.2. So perhaps the issue creator should check if the proper version is running in his installation. And I'll investigate, why 5.0.2 is not available for us... BTW: Die report file does exist in the jobs workspace? ;) 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
[JIRA] (JENKINS-60153) NullPointerException in Build failure analyzer
Title: Message Title Vladimir Eremeev updated an issue Jenkins / JENKINS-60153 NullPointerException in Build failure analyzer Change By: Vladimir Eremeev Environment: Jenkins version 2.190.2OS: Ubuntu 18 16 .04 with all recent updatesBuild failure analyzer version: 1.24.1 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.203018.1573630888000.1534.1573803000241%40Atlassian.JIRA.
[JIRA] (JENKINS-60179) Plugin JSON format to match anchore-cli JSONs format
Title: Message Title Fred Blaise created an issue Jenkins / JENKINS-60179 Plugin JSON format to match anchore-cli JSONs format Issue Type: Improvement Assignee: Daniel Nurmi Components: anchore-container-scanner-plugin Created: 2019-11-15 07:26 Priority: Major Reporter: Fred Blaise Hi, While working with the Anchore plugin, I realized that the JSON format of the artifacts saved was not maching the "anchore-cli --json" one. While I understand the current format is used to be able to display the reports within Jenkins, maybe adding a couple other artifacts would be nice, such as for : $ anchore-cli --json evaluate check docker.io/xyz/image:latest --detail $ anchore-cli --json image vuln docker.io/xyz/image:latest all results would be added to the artifacts saved. It would be really nice to have both on-par, in order to be able to use them interchangeably with whatever automation needs that could come up (as I do). Cheers. fred cc Daniel Nurmi Add Comment
[JIRA] (JENKINS-60172) Open Tasks Scanner does not copy files to Jenkins
Title: Message Title Piotr Ławniczuk commented on JENKINS-60172 Re: Open Tasks Scanner does not copy files to Jenkins Ulli Hafner No, there were no task scanner errors in console log. Here is the log: ... 12:24:12 [MSBuild NX32 Release] -> 74 copied, 0 not in workspace, 0 not-found, 0 with I/O error 12:24:12 [MSBuild NX32 Release] Attaching ResultAction with ID 'msbuild_nx32_release' to run 'PRL/PRL.nx_dev_from_pc.BUILD #44'. 12:24:12 [MSBuild NX32 Release] Using reference build 'PRL/PRL.nx_dev_from_pc.baseline #11' to compute new, fixed, and outstanding issues 12:24:12 [MSBuild NX32 Release] Issues delta (vs. reference build): outstanding: 156, new: 0, fixed: 0 12:24:12 [MSBuild NX32 Release] No quality gates have been set - skipping 12:24:12 [MSBuild NX32 Release] Health report is disabled - skipping 12:24:12 [MSBuild NX32 Release] Created analysis result for 156 issues (found 0 new issues, fixed 0 issues) 12:24:48 [TODO Task Scanner] Attaching ResultAction with ID 'todo-task-scanner' to run 'PRL/PRL.nx_dev_from_pc.BUILD #44'. 12:24:48 [TODO Task Scanner] No valid reference build found that meets the criteria (NO_JOB_FAILURE - SUCCESSFUL_QUALITY_GATE) 12:24:48 [TODO Task Scanner] All reported issues will be considered outstanding 12:24:48 [TODO Task Scanner] No quality gates have been set - skipping 12:24:48 [TODO Task Scanner] Health report is disabled - skipping 12:24:48 [TODO Task Scanner] Created analysis result for 450 issues (found 0 new issues, fixed 0 issues) 12:24:51 Email was triggered for: Always 12:24:51 Sending email for trigger: Always 12:24:54 Sending email to: 12:24:56 Finished: SUCCESS Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-58648) Dependency-check publisher 5.0.2 does not show Results
Title: Message Title Horst Krause edited a comment on JENKINS-58648 Re: Dependency-check publisher 5.0.2 does not show Results Same for us, when updating from DependencyCheck v4 to v5.It looks like the default path for report search was "**/dependency-check-report.xml" in v4 and has changed to "dependency-check-report.xml" in v5.We had this field empty in all our job configs. For v4 this was fine. With v5 the reports are not found any more and additionally when a job is triggered the empty report path field is changed automatically to "dependency-check-report.xml".So our solution was to change the report path in all jobs to "**/dependency-check-report.xml". Now the reports are found again. Update: I realized that [https://wiki.jenkins.io/display/JENKINS/OWASP+Dependency-Check+Plugin] announces a 5.0.2 in july which "Changed the default artifact pattern to **/dependency-check-report.xml". But we are still running 5.0.1 because the 5.0.2 is not available in our jenkins 2.190.2.So perhaps the issue creator should check if the proper version is running in his installation.And I'll investigate, why 5.0.2 is not available for us... 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.200917.1563994217000.1527.1573802100141%40Atlassian.JIRA.
[JIRA] (JENKINS-58648) Dependency-check publisher 5.0.2 does not show Results
Title: Message Title Horst Krause edited a comment on JENKINS-58648 Re: Dependency-check publisher 5.0.2 does not show Results Same for us, when updating from DependencyCheck v4 to v5.It looks like the default path for report search was "**/dependency-check-report.xml" in v4 and has changed to "dependency-check-report.xml" in v5.We had this field empty in all our job configs. For v4 this was fine. With v5 the report is reports are not found any more and additionally when a job was is triggered the empty report path field is changed automatically to "dependency-check-report.xml".So our solution was to change the report path in all jobs to "**/dependency-check-report.xml". Now the reports are found again. 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.200917.1563994217000.1524.1573801800245%40Atlassian.JIRA.
[JIRA] (JENKINS-58648) Dependency-check publisher 5.0.2 does not show Results
Title: Message Title Horst Krause commented on JENKINS-58648 Re: Dependency-check publisher 5.0.2 does not show Results Same for us, when updating from DependencyCheck v4 to v5. It looks like the default path for report search was "**/dependency-check-report.xml" in v4 and has changed to "dependency-check-report.xml" in v5. We had this field empty in all our job configs. For v4 this was fine. With v5 the report is not found any more and additionally when a job was triggered the empty report path field changed to "dependency-check-report.xml". So our solution was to change the report path in all jobs to "**/dependency-check-report.xml". Now the reports are found again. 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.200917.1563994217000.1522.1573801740459%40Atlassian.JIRA.
[JIRA] (JENKINS-60178) Jenkins To build .Net application
Title: Message Title Balaganeshwaran Bala created an issue Jenkins / JENKINS-60178 Jenkins To build .Net application Issue Type: New Feature Assignee: Giuseppe Landolfi Components: slave-setup-plugin Created: 2019-11-15 05:58 Environment: Jenkins Ford Priority: Minor Reporter: Balaganeshwaran Bala Hi, I am trying to set jenkins slave in in Windows server to connect to master Jenkins in Linux to build a .Net application. Require your support Add Comment
[JIRA] (JENKINS-60115) NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Title: Message Title
Phillip Verheyden commented on JENKINS-60115
Re: NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Thanks for the response, sorry for the cloak and dagger. My pipeline script is a bit unique in that this is what my Jenkinsfile looks like in all my projects:
mavenBuild{ }
And then I have a shared library that has a `vars/mavenBuild.groovy` that has the declarative pipeline in it. Pasted below.
import com.broadleafcommerce.jenkins.DependentProject
import com.broadleafcommerce.jenkins.DependentProjectDiscoverer
import com.broadleafcommerce.jenkins.ReleaseUtils
import com.broadleafcommerce.jenkins.SonarUtils
import com.broadleafcommerce.jenkins.Utils
def call(body) {
// evaluate the body block, and collect configuration into the object
def pipelineParams = [:]
body.resolveStrategy = Closure.DELEGATE_FIRST
body.delegate = pipelineParams
body()
println "Building with Jenkinsfile settings: $pipelineParams"
Utils.abortPreviousUpstreamBuilds(currentBuild)
def extraBuildProfiles = pipelineParams.extraBuildProfiles ?: ''
def extraDeployProfiles = pipelineParams.extraDeployProfiles ?: ''
def sonarAnalysis = pipelineParams.sonarAnalysis ?: ''
def javadocsDirectories = pipelineParams.javadocsDirectories ?: []
def referenceDocsDirectories = pipelineParams.referenceDocsDirectories ?: []
def agentLabel = pipelineParams.agentLabel ?: 'maven-jdk8'
def requiresNpmrc = pipelineParams.requiresNpmrc != null ? pipelineParams.requiresNpmrc : false
def forceDeploy = pipelineParams.forceDeploy != null ? pipelineParams.forceDeploy : false
def mainBranch = Utils.isMainBranch(this)
def shouldDeploy = mainBranch || forceDeploy || params.FORCE_DEPLOY || params.IS_RELEASE_BUILD
def mavenVersion = '3.6'
pipeline {
parameters {
string(
// Disabling the classpathURLCheck is for a bug in OpenJDK that prevents Surefire from running properly
// see https://stackoverflow.com/questions/53010200/maven-surefire-could-not-find-forkedbooter-class/53016532
defaultValue: '-Xmx2048m -Djdk.net.URLClassPath.disableClassPathURLCheck=true',
name: 'MAVEN_OPTS',
description: 'JVM parameters passed to Maven as MAVEN_OPTS'
)
string(
// Disabling the classpathURLCheck is for a bug in OpenJDK that prevents Surefire from running properly
// see https://stackoverflow.com/questions/53010200/maven-surefire-could-not-find-forkedbooter-class/53016532
defaultValue: '',
name: 'MAVEN_BUILD_ARGS',
description: 'Arguments passed directly to the Maven process (like -X, -e, any extra -D arguments etc). Only applies to the build phase on CI builds, applies to _both_ release:prepare and release:perform on release builds'
)
booleanParam(
defaultValue: false,
name: 'IS_RELEASE_BUILD',
description: 'Indicate whether or not this build should be treated as a release'
+' (GA, milestone, etc) If you would like to validate the versions that are autogenerated,'
+' use VALIDATE_RELEASE_VERSION_DEFAULTS. Otherwise, current release version (in conjunction'
+' with
[JIRA] (JENKINS-59938) Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-59938 Re: Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position Indeed this is how the cascade parameter update happens. Any parameter used by an active choice reactive has to be defined upstream. There are some advanced strategies for sharing parameters independent of their sequence in the form (using an in-memory h2 database) but this is beyond the scope of most typical freestyle jobs. We have discussed this with [~kinow] as a future improvement. 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.202740.1572022411000.1514.1573784040183%40Atlassian.JIRA.
[JIRA] (JENKINS-59938) Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-59938 Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position Change By: Ioannis Moutsatsos Issue Type: Bug Improvement 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.202740.1572022411000.1511.1573783980332%40Atlassian.JIRA.
[JIRA] (JENKINS-60056) Disable plugin manager filter until page is loaded
Title: Message Title Kuan-Yu Ho assigned an issue to Kuan-Yu Ho Jenkins / JENKINS-60056 Disable plugin manager filter until page is loaded Change By: Kuan-Yu Ho Assignee: Kuan-Yu Ho 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.202887.1572952503000.1507.1573783920379%40Atlassian.JIRA.
[JIRA] (JENKINS-59938) Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position
Title: Message Title Ioannis Moutsatsos commented on JENKINS-59938 Re: Active Choices Reactive Parameter with boolean as Referenced parameters is not evaluated depending on the position Indeed this is how the cascade parameter update happens. Any parameter used by an active choice reactive has to be defined upstream. There are some advanced strategies for sharing parameters independent of their sequence in the form (using an in-memory h2 database) but this is beyond the scope of most typical freestyle jobs. 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.202740.1572022411000.1505.1573783920353%40Atlassian.JIRA.
[JIRA] (JENKINS-54052) MultibranchProject ignores quietPeriod
Title: Message Title Liam Newman closed an issue as Duplicate Jenkins / JENKINS-54052 MultibranchProject ignores quietPeriod Change By: Liam Newman Status: Open Closed Resolution: Duplicate 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.194667.1539360524000.1501.1573782960380%40Atlassian.JIRA.
[JIRA] (JENKINS-57776) Support kv2 version for vault secrets in Jenkins Pipeline
Title: Message Title sivanarayana baisani commented on JENKINS-57776 Re: Support kv2 version for vault secrets in Jenkins Pipeline yeah that would be most desirable thing to do to solve such issues with dependency between two plugins. 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.199723.1559281987000.1491.1573770600166%40Atlassian.JIRA.
[JIRA] (JENKINS-57961) Add ability to set nvm version for complete pipeline either in options or environment
Title: Message Title sivanarayana baisani commented on JENKINS-57961 Re: Add ability to set nvm version for complete pipeline either in options or environment configuring nvm version in individual box works but then if you have two pipelines which needs different versions of nvm its difficult to add nvm version of each stage for an entire pipeline where we have more than 10 applications built and deployed through a single pipeline on a single node. 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.199944.1560263593000.1487.1573770360323%40Atlassian.JIRA.
[JIRA] (JENKINS-57843) EC2 spot fleet Instances stay connected even after the cloud is deleted
Title: Message Title sivanarayana baisani closed an issue as Fixed Jenkins / JENKINS-57843 EC2 spot fleet Instances stay connected even after the cloud is deleted Change By: sivanarayana baisani Status: Open Closed Resolution: Fixed 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.199801.1559658452000.1489.1573770360348%40Atlassian.JIRA.
[JIRA] (JENKINS-58819) When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Lab
Title: Message Title sivanarayana baisani closed an issue as Cannot Reproduce Jenkins / JENKINS-58819 When a Jenkins job with no agent or wrong agent is executed, the EC2 fleet plugin is spinning up all the possible instances in all the clouds configured with different Agent Labels Change By: sivanarayana baisani Status: Open Closed Resolution: Cannot Reproduce 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.201131.1565037052000.1481.1573770120420%40Atlassian.JIRA.
[JIRA] (JENKINS-60115) NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Title: Message Title Liam Newman commented on JENKINS-60115 Re: NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0 Thanks! Yes, I would appreciate a look at your pipeline. It shouldn't be all the code in your shared library, just the whatever is in in your pipline directive. I see where the error is being thrown, but it doesn't help me understand the underlying cause. 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.202962.1573259182000.1478.1573769640237%40Atlassian.JIRA.
[JIRA] (JENKINS-57932) Unstash pipeline step hangs intermittently
Title: Message Title Megan Smith commented on JENKINS-57932 Re: Unstash pipeline step hangs intermittently As an update - from the logs it looks like the download of the blob succeeds but the "unstash" never happens. 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.199906.1560157275000.1476.1573769520256%40Atlassian.JIRA.
[JIRA] (JENKINS-57932) Unstash pipeline step hangs intermittently
Title: Message Title Megan Smith commented on JENKINS-57932 Re: Unstash pipeline step hangs intermittently Jie Shen - I am using version 0.1.4 and am seeing this fairly consistently with a build that has parallel stages - unstash of the same source.tgz in multiple stages succeeds in some stages and hangs indefinitely in others. Does not seem to be resolved. 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.199906.1560157275000.1473.1573769280202%40Atlassian.JIRA.
[JIRA] (JENKINS-59191) SPAM-Not an issue
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-59191 SPAM-Not an issue Change By: Adam Gabryś URL: https://apotektitangel.com/jual-viagra-asli-di-medan/ 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.201632.1567441959000.1469.1573767600455%40Atlassian.JIRA.
[JIRA] (JENKINS-59191) SPAM-Not an issue
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-59191 SPAM-Not an issue Change By: Adam Gabryś Labels: kuat obat viagra 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.201632.1567441959000.1465.1573767600404%40Atlassian.JIRA.
[JIRA] (JENKINS-60026)
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-60026 Change By: Adam Gabryś URL: https://www.klinikaborsiradensaleh.com 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.202851.1572666918000.1460.1573767420258%40Atlassian.JIRA.
[JIRA] (JENKINS-60026)
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-60026 Change By: Adam Gabryś Labels: aborsi jakarta jasa kandungan klinik klinikaborsi klinikradensaleh kuret menggugurkan raden saleh tempat 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.202851.1572666918000.1462.1573767420295%40Atlassian.JIRA.
[JIRA] (JENKINS-60026) Klinik Aborsi Raden Saleh | Jasa aborsi di jakarta Apa itu Klinik Raden Saleh
Title: Message Title Adam Gabryś closed an issue as Won't Fix Jenkins / JENKINS-60026 Klinik Aborsi Raden Saleh | Jasa aborsi di jakarta Apa itu Klinik Raden Saleh Change By: Adam Gabryś Status: Open Closed Resolution: Won't Fix 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.202851.1572666918000.1456.1573766940638%40Atlassian.JIRA.
[JIRA] (JENKINS-60026) Klinik Aborsi Raden Saleh | Jasa aborsi di jakarta Apa itu Klinik Raden Saleh
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-60026 Klinik Aborsi Raden Saleh | Jasa aborsi di jakarta Apa itu Klinik Raden Saleh Change By: Adam Gabryś [Klinik Raden Saleh|https://www _The message has been removed . klinikaborsiradensaleh.com/] adalah klinik aborsi jakarta yang memiliki beberapa orang dokter spesialis kandungan (SpOG). Para dokter di klinik raden saleh telah mendapatkan izin dan legalitas dari dinas kesehatan. Di klinik raden saleh ini kami menangani kasus aborsi dan menerima pasien dengan kasus pendarahan yang disebabkan oleh suatu kejadian ataupun akibat mengkonsumsi obat aborsi (obat peluntur).Klinik raden saleh juga merupakan klinik aborsi legal atau tempat aborsi legal yang mengerjakan tindakan medis bagian penyakit kandungan. Klinik raden saleh ini disebut [klinik aborsi aman|https://www.klinikaborsiradensaleh.com/] tempat rujukan pasien dari para dokter kandungan dari seluruh Indonesia. Di tempat aborsi ini pasien dengan keluhan bagian kandungan dapat memperoleh penanganan oleh dokter spesialis kandungan yang berlisensi dan sudah berpengalaman.Di [klinik aborsi legal|https://www.klinikaborsiradensaleh.com/] ini akan dilakukan pemeriksaan Usg (Ultrasonografi) ataupun pemeriksaan keadaan umum secara manual sebelum melakukan aborsi. Pemeriksaan ini harus dilakukan untuk mengetahui kondisi pasien secara langsung. Karena dari hasil pemeriksaan ini maka dokter dapat menentukan apakah pasien tersebut dapat dilakukan tindakan aborsi atau tidak. Dan setelah itu seminggu kemudian akan disarankan untuk datang kontrol kesehatan untuk memastikan apakah tindakan sebelumnya sudah tuntas atau tidak.Karena sering terjadi kondisi yang lain akibat pasien sebelumnya telah mencoba melakukan aborsi dengan cara yang lain seperti mengkonsumsi obat aborsi, berobat ke dukun atau dengan cara yang lain namun tidak berhasil. Karena hal itu akan menyebabkan berbagai macam efek samping terhadap rahim si pasien. Yang paling sering terjadi adalah sering mengalami pendarahan dan terjadinya infeksi. Pada kondisi seperti ini akan menjadi pertimbangan untuk dokter apakah tindakan aborsi dapat dilakukan atau tidak.Apabila tindakan aborsi telah selesai dilakukan maka pasien diperbolehkan pulang dan seminggu kemudian pasien datang kembali untuk kontrol ulang. Biasanya setelah selesai kontrol pasien juga boleh melakukan suntik KB di klinik raden saleh ini.Di tempat aborsi legal ini tindakan aborsi dilakukan dengan metode vakum aspirasi atau penyedotan oleh dokter spesialis kandungan. Bila dibandingakan dengan metode kuretase zaman dulu yaitu dengan alat kuret (berupa sendok pengeruk) maka metode vakum ini adalah cara yang paling efektif dan praktis. Semua tindakan medis dilakukan berdasarkan standar operasi pelaksanaan kedokteran kandungan.Bagi anda yang ingin berkonsultasi bahkan membutuhkan tindakan medis bagian kandungan boleh datang ke klinik raden saleh ini. Terutama bagi yang ingin melakukan kuretase ataupun aborsi sebelum anda mengalami pendarahan ataupun infeksi.h3. Metode
[JIRA] (JENKINS-60026)
Title: Message Title Adam Gabryś updated an issue Jenkins / JENKINS-60026 Change By: Adam Gabryś Summary: Klinik Aborsi Raden Saleh | Jasa aborsi di jakarta Apa itu Klinik Raden Saleh 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.202851.1572666918000.1458.1573766940687%40Atlassian.JIRA.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48067
Re: workspace-volume should be optional
Like many people here I pre-configure my docker images with everything including the autoinstalled contents of the [WORKDIR]/tools directory (maven, gradle, groovy, etc). This works great with the docker plugin, not so much with k8s.My current workaround is to move symlink the tools directory into the Working Directory in my ENTRYPOINT script if this is when running in k8s (my images are also used outside of k8s){code:java}NORMAL_WORKDIR=/data/jenkins-slaveif [ -n "$JENKINS_AGENT_WORKDIR" ] && [ "$JENKINS_AGENT_WORKDIR" != "$NORMAL_WORKDIR" ] ; then echo " Moving Linking preinstalled Jenkins tools into the active workdir: $JENKINS_AGENT_WORKDIR" mv ln -s $NORMAL_WORKDIR/tools $JENKINS_AGENT_WORKDIR/fi{code}(My ENTRYPOINT script is a wrapper around /usr/local/bin/jenkins-slave)
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.186628.1510853986000.1433.1573763460507%40Atlassian.JIRA.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title
Alexander Komarov edited a comment on JENKINS-48067
Re: workspace-volume should be optional
Like many people here I pre-configure my docker images with everything including the autoinstalled contents of the [ WORKDIR ] /tools directory (maven, gradle, groovy, etc). This works great with the docker plugin, not so much with k8s.My current workaround is to move tools in my ENTRYPOINT script if this is k8s (my images are also used outside of k8s){code:java}NORMAL_WORKDIR=/data/jenkins-slaveif [ -n "$JENKINS_AGENT_WORKDIR" ] && [ "$JENKINS_AGENT_WORKDIR" != "$NORMAL_WORKDIR" ] ; then echo "Moving preinstalled Jenkins tools into the active workdir: $JENKINS_AGENT_WORKDIR" mv $NORMAL_WORKDIR/tools $JENKINS_AGENT_WORKDIR/fi{code}(My ENTRYPOINT script is a wrapper around /usr/local/bin/jenkins-slave)
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.186628.1510853986000.1397.1573759740507%40Atlassian.JIRA.
[JIRA] (JENKINS-48067) workspace-volume should be optional
Title: Message Title Alexander Komarov commented on JENKINS-48067 Re: workspace-volume should be optional Like many people here I pre-configure my docker images with everything including the WORKDIR/tools directory (maven, gradle, groovy, etc). This works great with the docker plugin, not so much with k8s. My current workaround is to move tools in my ENTRYPOINT script if this is k8s (my images are also used outside of k8s) NORMAL_WORKDIR=/data/jenkins-slave if [ -n "$JENKINS_AGENT_WORKDIR" ] && [ "$JENKINS_AGENT_WORKDIR" != "$NORMAL_WORKDIR" ] ; then echo "Moving preinstalled Jenkins tools into the active workdir: $JENKINS_AGENT_WORKDIR" mv $NORMAL_WORKDIR/tools $JENKINS_AGENT_WORKDIR/ fi (My ENTRYPOINT script is a wrapper around /usr/local/bin/jenkins-slave) 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.186628.1510853986000.1379.1573759681148%40Atlassian.JIRA.
[JIRA] (JENKINS-60140) Cannot run program "powershell" when powershell 6.0 core installed
Title: Message Title Carroll Chiou closed an issue as Not A Defect Closing as this issue was resolved in workflow-durable-task-step 2.35 Jenkins / JENKINS-60140 Cannot run program "powershell" when powershell 6.0 core installed Change By: Carroll Chiou Status: Open Closed Resolution: Not A Defect 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.
[JIRA] (JENKINS-60172) Open Tasks Scanner does not copy files to Jenkins
Title: Message Title Ulli Hafner commented on JENKINS-60172 Re: Open Tasks Scanner does not copy files to Jenkins BTW: The error messages above should be also part of the console log, are they not shown there? 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.203127.1573736138000.1375.1573758480199%40Atlassian.JIRA.
[JIRA] (JENKINS-60172) Open Tasks Scanner does not copy files to Jenkins
Title: Message Title Ulli Hafner commented on JENKINS-60172 Re: Open Tasks Scanner does not copy files to Jenkins I see. Currently post processing is disabled if an error occurs. This helps to reduce subsequent errors. 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.203127.1573736138000.1373.1573757940123%40Atlassian.JIRA.
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title Hui Jun Ng commented on JENKINS-53162 Re: Blueocean support for visualizing stages in parallel block in scripted pipeline Yup I agree with Jesse Glick on that. The example Andrius Štikonas shared is a workaround instead of a fix. I would imagine a fix would be that it simply works out of the box similar to how it does for declarative 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.193173.1534855202000.1301.1573757582179%40Atlassian.JIRA.
[JIRA] (JENKINS-57401) Show path for files
Title: Message Title Ulli Hafner assigned an issue to Ulli Hafner Jenkins / JENKINS-57401 Show path for files Change By: Ulli Hafner Assignee: Ulli Hafner 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.199185.1557486222000.1298.1573757040164%40Atlassian.JIRA.
[JIRA] (JENKINS-57401) Show path for files
Title: Message Title Ulli Hafner updated JENKINS-57401 Jenkins / JENKINS-57401 Show path for files Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Fixed 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.199185.1557486222000.1290.1573756920342%40Atlassian.JIRA.
[JIRA] (JENKINS-60177) StackOverflowError After Pipeline Declarative Upgraded to 1.4.0
Title: Message Title Charles Bozarth created an issue Jenkins / JENKINS-60177 StackOverflowError After Pipeline Declarative Upgraded to 1.4.0 Issue Type: Bug Assignee: Andrew Bayer Attachments: Console Output for StackOverflowError.txt, Example Pipeline for StackOverflowError.groovy Components: pipeline-model-definition-plugin Created: 2019-11-14 18:39 Environment: Windows Server 2016 10.0.14393 N/A Build 14393 Jenkins v2.190.2 Java runtime version 1.8.0_66-b18 Priority: Minor Reporter: Charles Bozarth A multibranch pipeline began failing with a StackOverflowError after updating these plugins to 1.4.0. Rolling back to 1.3.9 resolved the issue. Pipeline: Declarative Pipeline: Declarative Extension Points API Pipeline: Model API Pipeline: Stage Tags Metadata This particular pipeline uses a when statement to bypass a block of stages. These stages are configured as sequential stages, three stages within a parent stage where the when statement is. If the stages are not skipped then the error does not occur. The pipeline is running on the master (Windows) system with no slaves defined. Attached is a simplified pipeline and the console output. I've defined the BRANCH_NAME environment variable manually to simulate
[JIRA] (JENKINS-26462) Extract Maven builder to a separate plugin
Title: Message Title
Jesse Glick commented on JENKINS-26462
Re: Extract Maven builder to a separate plugin
I think the whole hudson.tasks._maven package (and corresponding feature in pipeline-maven-plugin) would best be deprecated. With recent versions of Maven, it is better to use (for example)
ansiColor('xterm') {
withEnv(['MAVEN_OPTS=-Djansi.force=true']) { // MNG-6380
sh 'mvn -B -Dstyle.color=always -ntp clean verify'
}
}
which produces richer and better coloration than Jenkins ever did.
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.160128.1421419682000.1271.1573756622108%40Atlassian.JIRA.
[JIRA] (JENKINS-51182) Conceal console lines from Maven downloads
Title: Message Title Jesse Glick commented on JENKINS-51182 Re: Conceal console lines from Maven downloads -ntp is a bit better but has the same issue with not being to diagnose a download hang. On the other hand this is arguably something that should be implemented upstream in Maven, not in Jenkins. 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.190492.1525712272000.1266.1573756380359%40Atlassian.JIRA.
[JIRA] (JENKINS-26462) Extract Maven builder to a separate plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-26462 Extract Maven builder to a separate plugin Change By: Jesse Glick Labels: split-plugins-from-core stalled-pr 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.160128.1421419682000.1250.1573756260715%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Ivan Fernandez Calvo edited a comment on JENKINS-60176 Re: Groups are not working | SAML | Authorization Matrix Did you set up the correct group attribute in the SAML configuration? Did you check if the groups are assigned to the users? Go to people to one of the users, then to configure and check at the end of the page the groups grabbed from SAML This Jira is not a support site if you have questions please use the google groups, see https://wiki.jenkins.io/display/JENKINS/How+to+report+an+issue 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.203136.157375217.1248.1573755840119%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-60176 Re: Groups are not working | SAML | Authorization Matrix Did you set up the correct group attribute in the SAML configuration? Did you check if the groups are assigned to the users? Go to people to one of the users, then to configure and check at the end of the page the groups grabbed from SAML 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.203136.157375217.1246.1573755780170%40Atlassian.JIRA.
[JIRA] (JENKINS-60111) Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline
Title: Message Title Devin Nusbaum commented on JENKINS-60111 Re: Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline Thanks for the report! My guess for the reason for the slowdown is that when you ran builds triggered by users as the triggering user using Authorize Project Plugin, permission checks during the course of the build had to interact with your security realm and authorization strategy to figure out what permissions the user had based on your configuration. Builds that are triggered automatically run as the Jenkins SYSTEM user, which always has all permissions, and so permission checks are very quick. Maybe you could configure more aggressive caching or optimize your LDAP settings or something to improve the performance, depends on how things are configured in your instance. You could take thread dumps while the Pipeline is running slowly and see where threads are usually blocked to confirm/deny my hypothesis. I'm not sure about the warning. Perhaps the slowdown is significant enough to cause the relevant code to time out. If you aren't seeing it once you remove Authorize Project Plugin, I think you can safely ignore it. I'm going to close this issue, if you get thread dumps and think there is a bug somewhere based on that data, feel free to reopen it. 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
[JIRA] (JENKINS-60111) Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline
Title: Message Title Devin Nusbaum closed an issue as Incomplete Jenkins / JENKINS-60111 Pipeline extremely slow when triggered by a user in comparison with the time triggered pipeline Change By: Devin Nusbaum Status: Open Closed Resolution: Incomplete 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.202957.1573231443000.1243.1573755600479%40Atlassian.JIRA.
[JIRA] (JENKINS-60115) NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-60115 NullPointerException in Declarative Pipeline after upgrade from 1.3.9 to 1.4.0 Change By: Liam Newman Assignee: Andrew Bayer Liam Newman 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.202962.1573259182000.1232.1573754760239%40Atlassian.JIRA.
[JIRA] (JENKINS-60159) Multibranch pipeline - existing branch seen as first time build
Title: Message Title Mark Waite commented on JENKINS-60159 Re: Multibranch pipeline - existing branch seen as first time build I'm not aware of cases where a checkout fails and does not fail the build. Definitely provide examples of the problem in a separate issue. 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.203111.1573682442000.1229.1573753980341%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh updated an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Change By: Daljit singh Attachment: image-2019-11-14-23-07-36-764.png 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.203136.157375217.1227.1573753080203%40Atlassian.JIRA.
[JIRA] (JENKINS-60176) Groups are not working | SAML | Authorization Matrix
Title: Message Title Daljit singh created an issue Jenkins / JENKINS-60176 Groups are not working | SAML | Authorization Matrix Issue Type: Bug Assignee: Ivan Fernandez Calvo Components: saml-plugin Created: 2019-11-14 17:22 Labels: pipeline SAML2 ProjectMatrixAuthorization Priority: Minor Reporter: Daljit singh When we create a group in authorization-based matrix and assine an EMAIL address/User to a group Using the same Group in Pipeline Input with permissions It Just prompt with error message You are not the member of "TEST Group" Add Comment
[JIRA] (JENKINS-52841) RFE: restrict message body output to be JSON
Title: Message Title Ken Dreyer commented on JENKINS-52841 Re: RFE: restrict message body output to be JSON I think this feature is still important 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.192769.1533147742000.1220.1573749120247%40Atlassian.JIRA.
[JIRA] (JENKINS-59752) Add support for ephemeral OS disk
Title: Message Title Bradley Wangia commented on JENKINS-59752 Re: Add support for ephemeral OS disk Stefan Scherer this would be nice to have for many of my workloads. Was that fork useful in crafting a PR? 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.202475.1570808392000.1217.1573747980235%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance when using 'grep' Arg - this issue doesn't like being chased.Every time I do a single action like update, reboot or restart behaviour stays the same.Whenever I do simultaneous actions, something changes.This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again. Noticeable: I restarted jenkins by starting and stopping the jenkins service this time. BTW: really no support here? Where else can I get assistance? 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.201861.156818559.1214.1573747260208%40Atlassian.JIRA.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Szymon Seget updated an issue Jenkins / JENKINS-36195 Pipeline polling ignores special polling rules Change By: Szymon Seget Issue Type: Improvement Bug 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.172167.1466697529000.1115.1573746606504%40Atlassian.JIRA.
[JIRA] (JENKINS-36195) Pipeline polling ignores special polling rules
Title: Message Title Szymon Seget commented on JENKINS-36195 Re: Pipeline polling ignores special polling rules Hi, any updates? I need this feature to work. Kishore Babu Kavuru are you trying to fix it? 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.172167.1466697529000.1014.1573746542576%40Atlassian.JIRA.
[JIRA] (JENKINS-59452) Support JIRA sites that use a personal certificate during authentication
Title: Message Title Frank Refol updated an issue Jenkins / JENKINS-59452 Support JIRA sites that use a personal certificate during authentication Change By: Frank Refol Summary: Support JIRA sites that uses use a personal certificate during authentication 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.202042.1568924634000.941.1573746361742%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Pete McNab commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script This issue is three years old and has never really been addressed with anything other than vague marketing-speak and nothing definitively helpful for people who listened to the screams from Jenkins to migrate to pipelines, only to discover all the limitations. But you can happily pay Cloudbees for enterprise support and more expensive add-ons which still won't solve your problems. Give it up, find another solution. 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.174127.1473169024000.943.1573746361838%40Atlassian.JIRA.
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title Frank Refol assigned an issue to Frank Refol Jenkins / JENKINS-59452 Support JIRA sites that uses a personal certificate during authentication Change By: Frank Refol Assignee: Dan Alvizu Frank Refol 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.202042.1568924634000.940.1573746060140%40Atlassian.JIRA.
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title Frank Refol edited a comment on JENKINS-59452 Re: Support JIRA sites that uses a personal certificate during authentication Looking more into this. The following links might be helpful [https://stackoverflow.com/questions/18541813/how-do-i-pass-the-client-certificate-with-http-client/18542079]Downloaded code, [ClientCustomSSL.java| http https :// example hc . com apache.org/httpcomponents-client-ga/httpclient/examples/org/apache/http/examples/client/ClientCustomSSL.java ], referenced in above thread and attached here, [^ClientCustomSSL.java] 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.202042.1568924634000.938.1573746000190%40Atlassian.JIRA.
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title Frank Refol edited a comment on JENKINS-59452 Re: Support JIRA sites that uses a personal certificate during authentication Looking more into this. The following links might be helpful [https://stackoverflow.com/questions/18541813/how-do-i-pass-the-client-certificate-with-http-client/18542079]Downloaded code, [ClientCustomSSL.java| https http :// hc example . apache.org/httpcomponents-client-ga/httpclient/examples/org/apache/http/examples/client/ClientCustomSSL.java com ], referenced in above thread and attached here, [^ClientCustomSSL.java] 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.202042.1568924634000.936.1573746000160%40Atlassian.JIRA.
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title Frank Refol edited a comment on JENKINS-59452 Re: Support JIRA sites that uses a personal certificate during authentication Looking more into this. The following links might be helpful [https://stackoverflow.com/questions/18541813/how-do-i-pass-the-client-certificate-with-http-client/18542079]Downloaded code, [ClientCustomSSL.java| [ https://hc.apache.org/httpcomponents-client-ga/httpclient/examples/org/apache/http/examples/client/ClientCustomSSL.java] ] , referenced in above thread and attached here, [^ClientCustomSSL.java] 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.202042.1568924634000.930.1573745940311%40Atlassian.JIRA.
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title Frank Refol commented on JENKINS-59452 Re: Support JIRA sites that uses a personal certificate during authentication Looking more into this. The following links might be helpful https://stackoverflow.com/questions/18541813/how-do-i-pass-the-client-certificate-with-http-client/18542079 Downloaded code, [ClientCustomSSL.java| https://hc.apache.org/httpcomponents-client-ga/httpclient/examples/org/apache/http/examples/client/ClientCustomSSL.java], referenced in above thread and attached here, ClientCustomSSL.java 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.202042.1568924634000.928.1573745880141%40Atlassian.JIRA.
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title Scott Hebert updated JENKINS-49500 Jenkins / JENKINS-49500 In every pipeline build with triggers, a new trigger is created and the old one is stopped Change By: Scott Hebert Status: In Progress Review 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.188392.1518430561000.925.1573745760913%40Atlassian.JIRA.
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title Scott Hebert commented on JENKINS-49500 Re: In every pipeline build with triggers, a new trigger is created and the old one is stopped Created https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/362 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.188392.1518430561000.923.1573745760795%40Atlassian.JIRA.
[JIRA] (JENKINS-59452) Support JIRA sites that uses a personal certificate during authentication
Title: Message Title Frank Refol updated an issue Jenkins / JENKINS-59452 Support JIRA sites that uses a personal certificate during authentication Change By: Frank Refol Attachment: ClientCustomSSL.java 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.202042.1568924634000.920.1573745700801%40Atlassian.JIRA.
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title Scott Hebert started work on JENKINS-49500 Change By: Scott Hebert Status: Open In Progress 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.188392.1518430561000.917.1573745520690%40Atlassian.JIRA.
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title Scott Hebert assigned an issue to Scott Hebert Jenkins / JENKINS-49500 In every pipeline build with triggers, a new trigger is created and the old one is stopped Change By: Scott Hebert Assignee: Scott Hebert 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.188392.1518430561000.915.1573745520625%40Atlassian.JIRA.
[JIRA] (JENKINS-52841) RFE: restrict message body output to be JSON
Title: Message Title Scott Hebert commented on JENKINS-52841 Re: RFE: restrict message body output to be JSON Is this still an issue? 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.192769.1533147742000.912.1573745401516%40Atlassian.JIRA.
[JIRA] (JENKINS-56369) sendCIMessage - Problem accessing /pipeline-syntax/null. Reason:
Title: Message Title Scott Hebert commented on JENKINS-56369 Re: sendCIMessage - Problem accessing /pipeline-syntax/null. Reason: Tried with latest version 1.1.11 and I was able to generate a snippet. Cannot reproduce. 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.197955.155163568.890.1573745400815%40Atlassian.JIRA.
[JIRA] (JENKINS-50429) Shell command are really slower than before
Title: Message Title Thomas M commented on JENKINS-50429 Re: Shell command are really slower than before Pascal Laporte Carlos Sanchez This issue is marked as resolved, but your last comments don't look like it? I'm facing a similar problem, but I'm not using any kubernetes related plugin. Carlos Sanchez can you please suggest how I could quickly check if the workaround helps in my case as well (don't know how I could apply a hotfix in java code in an existing Jenkins installation). 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.189484.1522154059000.895.1573745401026%40Atlassian.JIRA.
[JIRA] (JENKINS-56369) sendCIMessage - Problem accessing /pipeline-syntax/null. Reason:
Title: Message Title Scott Hebert resolved as Cannot Reproduce Jenkins / JENKINS-56369 sendCIMessage - Problem accessing /pipeline-syntax/null. Reason: Change By: Scott Hebert Status: Open Resolved Resolution: Cannot Reproduce 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.197955.155163568.892.1573745400969%40Atlassian.JIRA.
[JIRA] (JENKINS-57642) Wrong parameter type and squashing its content when trigger a job
Title: Message Title Scott Hebert updated JENKINS-57642 Jenkins / JENKINS-57642 Wrong parameter type and squashing its content when trigger a job Change By: Scott Hebert Status: In Review Resolved Resolution: Fixed 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.199573.1558615641000.887.1573745160515%40Atlassian.JIRA.
[JIRA] (JENKINS-60172) Open Tasks Scanner does not copy files to Jenkins
Title: Message Title
Piotr Ławniczuk edited a comment on JENKINS-60172
Re: Open Tasks Scanner does not copy files to Jenkins
I didn't know about the info page and there were no errors in the console log.After seeing what is wrong on the info page I fixed the issue:{code:java}Error MessagesCan't read source file '\common\include\csl.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\common\include\libcdvd.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\common\include\sdmacro.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\devfont.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\libipu.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\librspu2.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\sifdev.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\kerror.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\libspu2.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\modload.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\thread.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\mcbasicx\main.c', defined encoding 'windows-1250' seems to be wrongCan't read source file '\common\include\csl.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\common\include\libcdvd.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\common\include\sdmacro.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\devfont.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\libipu.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\librspu2.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\sifdev.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\kerror.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\libspu2.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\modload.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\thread.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\mcbasicx\main.c', defined encoding 'windows-1250' seems to be wrongCan't read source file '\common\include\csl.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\common\include\libcdvd.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\common\include\sdmacro.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\devfont.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\libipu.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\librspu2.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\ee\include\sifdev.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\kerror.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\libspu2.h', defined encoding 'windows-1250' seems to be wrongCan't read source file '\iop\install\include\modload.h', defined encoding 'windows-1250' seems to be
[JIRA] (JENKINS-60172) Open Tasks Scanner does not copy files to Jenkins
Title: Message Title Piotr Ławniczuk commented on JENKINS-60172 Re: Open Tasks Scanner does not copy files to Jenkins I didn't know about the info page and there were no errors in the console log. After seeing what is wrong on the info page I fixed the issue: Error Messages Can't read source file '\common\include\csl.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\common\include\libcdvd.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\common\include\sdmacro.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\devfont.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\libipu.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\librspu2.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\sifdev.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\kerror.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\libspu2.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\modload.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\thread.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\mcbasicx\main.c', defined encoding 'windows-1250' seems to be wrong Can't read source file '\common\include\csl.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\common\include\libcdvd.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\common\include\sdmacro.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\devfont.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\libipu.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\librspu2.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\sifdev.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\kerror.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\libspu2.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\modload.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\thread.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\mcbasicx\main.c', defined encoding 'windows-1250' seems to be wrong Can't read source file '\common\include\csl.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\common\include\libcdvd.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\common\include\sdmacro.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\devfont.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\libipu.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\librspu2.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\ee\include\sifdev.h', defined encoding 'windows-1250' seems to be wrong Can't read source file '\iop\install\include\kerror.h', defined encoding 'windows-1250' seems to be wrong Can't
[JIRA] (JENKINS-60042) Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2
Title: Message Title Vincent Latombe updated JENKINS-60042 Jenkins / JENKINS-60042 Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2 Change By: Vincent Latombe Status: Fixed but Unreleased Closed Released As: kubernetes-1.21.3 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.202870.1572884599000.860.1573744200317%40Atlassian.JIRA.
[JIRA] (JENKINS-60042) Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2
Title: Message Title Vincent Latombe updated JENKINS-60042 Jenkins / JENKINS-60042 Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2 Change By: Vincent Latombe Status: In Review Fixed but Unreleased Resolution: Fixed 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.202870.1572884599000.856.1573743720429%40Atlassian.JIRA.
[JIRA] (JENKINS-60042) Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2
Title: Message Title Vincent Latombe started work on JENKINS-60042 Change By: Vincent Latombe Status: Open In Progress 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.202870.1572884599000.848.1573743600740%40Atlassian.JIRA.
[JIRA] (JENKINS-60042) Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2
Title: Message Title Vincent Latombe updated JENKINS-60042 Jenkins / JENKINS-60042 Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2 Change By: Vincent Latombe Status: In Progress Review 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.202870.1572884599000.853.1573743601043%40Atlassian.JIRA.
[JIRA] (JENKINS-60042) Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2
Title: Message Title Vincent Latombe assigned an issue to Evan Bluhm Jenkins / JENKINS-60042 Pod Template Delete Button Missing From Config Page - Jenkins Version 2.190.2 Change By: Vincent Latombe Assignee: Evan Bluhm 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.202870.1572884599000.844.1573743600681%40Atlassian.JIRA.
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer edited a comment on JENKINS-59311 Re: Poor performance when using 'grep' Arg - this issue doesn't like being chased.Every time I do a single action like update, reboot or restart behaviour stays the same.Whenever I do simultaneous actions, something changes.This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again. BTW: really no support here? Where else can I get assistance? 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.201861.156818559.841.1573743540317%40Atlassian.JIRA.
[JIRA] (JENKINS-33348) Deleting job under git failed, leaving a poisened commit queue
Title: Message Title Kiril Mitov commented on JENKINS-33348 Re: Deleting job under git failed, leaving a poisened commit queue Using version 0.0.10 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.168753.145730564.840.1573743540273%40Atlassian.JIRA.
[JIRA] (JENKINS-60175) To be able to define test cases in hierarchy folder
Title: Message Title Sergio Cuenca created an issue Jenkins / JENKINS-60175 To be able to define test cases in hierarchy folder Issue Type: Improvement Assignee: Maria Narcisa Galan Attachments: Request for change for the plugin 1.docx Components: hp-application-automation-tools-plugin Created: 2019-11-14 14:57 Labels: test ALM Priority: Major Reporter: Sergio Cuenca Request for change for the plugin: Micro Focus Application Automation Tools Currently the configuration for this plugin has the parameter “Test Folder” and it is defined as follows: The path of the test folder that will contain the uploaded test. The path doesn't include the Root test folder (Subject). For example, sampletestfolder\subfolder means, the tests will be uploaded to test folder named 'subfolder', which is under the test folder named 'sampletestfolder', and 'sampletestfolder' is under the root test folder 'Subject'. The configuration of this parameter does NOT allow to upload tests cases in different subfolders. Let me explain it with an example: Our current project structure is someone like that: Root/ Automated tests/ Module 1/ Test A
[JIRA] (JENKINS-33348) Deleting job under git failed, leaving a poisened commit queue
Title: Message Title Kiril Mitov commented on JENKINS-33348 Re: Deleting job under git failed, leaving a poisened commit queue Tried installing and uninstalling the SCM Configuration plugin. The following status "SCM Sync status : Thu Nov 14 16:43:51 EET 2019 : Delete jobs/is docker BuildTo remove this message, please click here" is still shown. Can not sync to scm configuration. 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.168753.145730564.835.1573743360587%40Atlassian.JIRA.
[JIRA] (JENKINS-60174) To be able to inform test version executed
Title: Message Title Sergio Cuenca created an issue Jenkins / JENKINS-60174 To be able to inform test version executed Issue Type: Improvement Assignee: Maria Narcisa Galan Attachments: Request for change for the plugin 2.docx Components: hp-application-automation-tools-plugin Created: 2019-11-14 14:55 Labels: versioning Priority: Major Reporter: Sergio Cuenca Request for change for the plugin: Micro Focus Application Automation Tools Currently the plugin allows to use Junit standard XML files in order to upload test results to ALM. The current XML structure does NOT allow to indicate the test version executed. We need to be able to indicate the test version executen within the XML file uploaded in ALM. Let me explain it with an example: Changes file Changes Test Set 2.293 8.293 ChangesManagement List changes 4.0 false 0 0.576 The tag testVersion is a non-supported
[JIRA] (JENKINS-59311) Poor performance when using 'grep'
Title: Message Title Christoph Fetzer commented on JENKINS-59311 Re: Poor performance when using 'grep' Arg - this issue doesn't like being chased. Every time I do a single action like update, reboot or restart behaviour stays the same. Whenever I do simultaneous actions, something changes. This time: update of Script security 166->1.67 and restart of jenkins (without reboot) due to hanging job fragments made the build fast again. 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.201861.156818559.832.1573743360530%40Atlassian.JIRA.
[JIRA] (JENKINS-33348) Deleting job under git failed, leaving a poisened commit queue
Title: Message Title
Kiril Mitov edited a comment on JENKINS-33348
Re: Deleting job under git failed, leaving a poisened commit queue
I would like to reopen it. I currently have the following log : [deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during remove : The git command failed.{color:#aa}Nov 14, 2019 4:19:05 PM{color} {color:#aa}SEVERE{color} {color:#aa}hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy{color}[deleteHierarchy] Problem during
[JIRA] (JENKINS-60173) Jenkins Crashing Every few minutes
Title: Message Title
Justin Seiser updated an issue
Jenkins / JENKINS-60173
Jenkins Crashing Every few minutes
Change By:
Justin Seiser
Jenkins has started crashing every few minutes, throwing this error. {code:java} 2019-11-14 13:59:17.832+ [id=104] SEVERE h.i.i.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler#uncaughtException: A thread (Thread-22/104) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.2019-11-14 13:59:17.832+ [id=104] SEVERE h.i.i.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler#uncaughtException: A thread (Thread-22/104) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.java.lang.ClassNotFoundException: org.joda.time.format.DateTimeFormat at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1383) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1083) at java.lang.ClassLoader.loadClass(ClassLoader.java:351)Caused: java.lang.NoClassDefFoundError: org/joda/time/format/DateTimeFormat at com.amazonaws.auth.internal.AWS4SignerUtils.(AWS4SignerUtils.java:27) at com.amazonaws.auth.internal.AWS4SignerRequestParams.(AWS4SignerRequestParams.java:99) at com.amazonaws.auth.AWS4Signer.sign(AWS4Signer.java:225) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1209) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1055) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.sqs.AmazonSQSClient.doInvoke(AmazonSQSClient.java:1740) at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:1716) at com.amazonaws.services.sqs.AmazonSQSClient.executeGetQueueAttributes(AmazonSQSClient.java:1013) at com.amazonaws.services.sqs.AmazonSQSClient.getQueueAttributes(AmazonSQSClient.java:989) at com.amazonaws.services.sqs.buffered.ReceiveQueueBuffer.spawnMoreReceiveTasks(ReceiveQueueBuffer.java:312) at com.amazonaws.services.sqs.buffered.ReceiveQueueBuffer.receiveMessageAsync(ReceiveQueueBuffer.java:150) at com.amazonaws.services.sqs.buffered.QueueBuffer.receiveMessage(QueueBuffer.java:171) at com.amazonaws.services.sqs.buffered.QueueBuffer.receiveMessageSync(QueueBuffer.java:188) at
[JIRA] (JENKINS-60173) Jenkins Crashing Every few minutes
Title: Message Title Justin Seiser commented on JENKINS-60173 Re: Jenkins Crashing Every few minutes If I disable the plugin, and attempt to re-enable, i get. 2019-11-14 14:38:46.960+ [id=12] WARNING o.e.j.s.h.ContextHandler$Context#log: Error while serving https://jenkins.cicd.idautocloud.com/descriptorByName/com.ribose.jenkins.plugin.awscodecommittrigger.SQSTriggerQueue/fillUrlItemsjava.lang.ClassNotFoundException: org.joda.time.format.DateTimeFormat at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1383) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1083) at java.lang.ClassLoader.loadClass(ClassLoader.java:351)Caused: java.lang.NoClassDefFoundError: org/joda/time/format/DateTimeFormat at com.amazonaws.auth.internal.AWS4SignerUtils.(AWS4SignerUtils.java:27) at com.amazonaws.auth.internal.AWS4SignerRequestParams.(AWS4SignerRequestParams.java:99) at com.amazonaws.auth.AWS4Signer.sign(AWS4Signer.java:225) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1209) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1055) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:743) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:717) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:699) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:667) at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:649) at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:513) at com.amazonaws.services.sqs.AmazonSQSClient.doInvoke(AmazonSQSClient.java:1740) at com.amazonaws.services.sqs.AmazonSQSClient.invoke(AmazonSQSClient.java:1716) at com.amazonaws.services.sqs.AmazonSQSClient.executeListQueues(AmazonSQSClient.java:1185) at com.amazonaws.services.sqs.AmazonSQSClient.listQueues(AmazonSQSClient.java:1162) at com.amazonaws.services.sqs.AmazonSQSClient.listQueues(AmazonSQSClient.java:1197) at com.amazonaws.services.sqs.buffered.AmazonSQSBufferedAsyncClient.listQueues(AmazonSQSBufferedAsyncClient.java:350) at com.ribose.jenkins.plugin.awscodecommittrigger.SQSTriggerQueue$DescriptorImpl.doFillUrlItems(SQSTriggerQueue.java:380) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)Caused: java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at
[JIRA] (JENKINS-26535) DescribableHelper does not handle wildcards well
Title: Message Title Jesse Glick commented on JENKINS-26535 Re: DescribableHelper does not handle wildcards well Gunter Grodotzki please use the Link system in JIRA to keep track of these things. 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.160203.1421868708000.811.1573742521717%40Atlassian.JIRA.
[JIRA] (JENKINS-60164) Silk Performer Test Build error out with Master node
Title: Message Title Chandrakumar Sekar commented on JENKINS-60164 Re: Silk Performer Test Build error out with Master node Yes, I have right access to the directory, i.e. my ID has full control to the directory where the script are placed. When i run this through Master - Salve config build (Silk Performer test) is success and failing only if i choose Master configuration. Yes, We have plan to update the Silk Performer version to 19.5 by early 2020 till then we will be using the 17.5 version. 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.203116.1573715258000.807.1573742160165%40Atlassian.JIRA.
[JIRA] (JENKINS-33348) Deleting job under git failed, leaving a poisened commit queue
Title: Message Title Kiril Mitov commented on JENKINS-33348 Re: Deleting job under git failed, leaving a poisened commit queue like to reopen it. I currently have the following log [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. Nov 14, 2019 4:19:05 PM SEVERE hudson.plugins.scm_sync_configuration.SCMManipulator deleteHierarchy [deleteHierarchy] Problem during remove : The git command failed. The last commit in the repo is Author: Date: Tue Oct 29 14:43:06 2019 +0200 ` And today we are 14 November In the same time th SCM status says SCM Sync status : Last operation @ Thu Nov 14 16:18:52 EET 2019 which is incorrect and sometimes there is an error in
[JIRA] (JENKINS-60173) Jenkins Crashing Every few minutes
Title: Message Title Justin Seiser created an issue Jenkins / JENKINS-60173 Jenkins Crashing Every few minutes Issue Type: Bug Assignee: Phuong Huynh Components: aws-codecommit-trigger-plugin Created: 2019-11-14 14:23 Environment: Jenkins v2.203 Priority: Minor Reporter: Justin Seiser Jenkins has started crashing every few minutes, throwing this error. 2019-11-14 13:59:17.832+ [id=104] SEVERE h.i.i.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler#uncaughtException: A thread (Thread-22/104) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.2019-11-14 13:59:17.832+ [id=104] SEVERE h.i.i.InstallUncaughtExceptionHandler$DefaultUncaughtExceptionHandler#uncaughtException: A thread (Thread-22/104) died unexpectedly due to an uncaught exception, this may leave your Jenkins in a bad way and is usually indicative of a bug in the code.java.lang.ClassNotFoundException: org.joda.time.format.DateTimeFormat at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1383) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1336) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1083) at java.lang.ClassLoader.loadClass(ClassLoader.java:351)Caused: java.lang.NoClassDefFoundError: org/joda/time/format/DateTimeFormat at com.amazonaws.auth.internal.AWS4SignerUtils.(AWS4SignerUtils.java:27) at com.amazonaws.auth.internal.AWS4SignerRequestParams.(AWS4SignerRequestParams.java:99) at com.amazonaws.auth.AWS4Signer.sign(AWS4Signer.java:225) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1209) at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1055) at
[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title Jason Pyeron commented on JENKINS-60093 Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character got it, but we have not yet reproduced the condition where the ESC char was emitted. 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.202938.1573148951000.798.1573740960659%40Atlassian.JIRA.
[JIRA] (JENKINS-60159) Multibranch pipeline - existing branch seen as first time build
Title: Message Title Thomas Minke commented on JENKINS-60159 Re: Multibranch pipeline - existing branch seen as first time build Mark Waite, one other thing: we have another issue at the moment regarding Git checkout. Sometimes the checkout fails with an error message, without failing the build. This results in a deployment of the code without updating. I will create a separate issue for this, but it might be related. 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.203111.1573682442000.796.1573740360169%40Atlassian.JIRA.
[JIRA] (JENKINS-60172) Open Tasks Scanner does not copy files to Jenkins
Title: Message Title Ulli Hafner commented on JENKINS-60172 Re: Open Tasks Scanner does not copy files to Jenkins Well, actually open tasks are linked to the sources in general, see example. Can you provide some more details? What errors are reported in your open tasks info page? See https://ci.jenkins.io/job/Plugins/job/warnings-ng-plugin/job/master/667/open-tasks/info/? 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.203127.1573736138000.792.1573740180273%40Atlassian.JIRA.
[JIRA] (JENKINS-60159) Multibranch pipeline - existing branch seen as first time build
Title: Message Title Thomas Minke commented on JENKINS-60159 Re: Multibranch pipeline - existing branch seen as first time build Hi Mark Waite, thanks for your quick response. I'm looking for more info to reproduce this issue, but I'm afraid I've got very little. Today, 4 out of 5 builds show as 'first-time' in the console logs, and 1 shows a changelog. These builds were both after branch merges and direct commits. Nothing irregular in the Git repository as far as I can see. The Jenkinsfile was not changed in all of the builds. We use a static agent with one SSH slave. All 5 builds that I started today ran on this SSH slave. Do you have any hints which information would be relevant for reproducing or debugging? 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.203111.1573682442000.793.1573740180286%40Atlassian.JIRA.
[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-60093 WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character Change By: Cyrille Le Clerc Attachment: image-2019-11-14-14-45-10-102.png 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.202938.1573148951000.782.1573739160588%40Atlassian.JIRA.
[JIRA] (JENKINS-60093) WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Title: Message Title
Cyrille Le Clerc commented on JENKINS-60093
Re: WARNING Exception parsing the Jenkins Maven Event Spy logs due to An invalid XML character
Jason Pyeron as Devin Nusbaum has said, can you please collect the log file using the FAQ entry "How do I capture the log file generated by the Jenkins Maven Event Spy" https://wiki.jenkins.io/display/JENKINS/Pipeline+Maven+Plugin#PipelineMavenPlugin-HowdoIcapturethelogfilegeneratedbytheJenkinsMavenEventSpy The build script will look like
withMaven() {
sh "mvn verify"
writeFile file: '.archive-jenkins-maven-event-spy-logs', text: ''
} // will discover the marker file ".archive-jenkins-maven-event-spy-log" and will archive the maven event spy log file maven-spy-log
A log file with the output of the "Jenkins Maven Event Spy"" will be added to the archived artifacts of your build. It will look like:
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.202938.1573148951000.786.1573739160879%40Atlassian.JIRA.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Upgrade the two plugins together. Git plugin 3.x might work with git client plugin 3.0.0, but you'll be the first (and possibly only) person to test that configuration. It is intended that git plugin 4.0.0 and git client plugin 3.0.0 upgrade together. It is much better to travel with large groups of people in this case. Large groups of people have tested git client plugin 3.0.0 with git plugin 4.0.0. I'm not aware of anyone that has tested git client plugin 3.0.0 with git plugin 3.x releases. 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.186841.1511861183000.729.1573736761868%40Atlassian.JIRA.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title ASHOK MOHANTY commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Can I only upgrade git-client plugin to v3.0.0 (right now we have git plugin v3.9.1) !? OR we should upgrade git client plugin 3.0.0 and git plugin 4.0.0 together !! 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.186841.1511861183000.727.1573736221135%40Atlassian.JIRA.
