[JIRA] (JENKINS-59324) "No valid crumb was included in the request" even with valid crumb supplied - after updating
Title: Message Title Rob Ormond updated JENKINS-59324 Jenkins / JENKINS-59324 "No valid crumb was included in the request" even with valid crumb supplied - after updating Change By: Rob Ormond Status: Open Fixed but Unreleased 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201875.1568260412000.1763.1568266440159%40Atlassian.JIRA.
[JIRA] (JENKINS-59324) "No valid crumb was included in the request" even with valid crumb supplied - after updating
Title: Message Title Rob Ormond commented on JENKINS-59324 Re: "No valid crumb was included in the request" even with valid crumb supplied - after updating I now realise this is related to https://jenkins.io/doc/upgrade-guide/2.176/#upgrading-to-jenkins-lts-2-176-3 I've swapped to using API token and it is working 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.201875.1568260412000.1762.1568266380076%40Atlassian.JIRA.
[JIRA] (JENKINS-30383) SynchronousNonBlockingStepExecution should allow restart of idempotent steps
Title: Message Title Mohammad Norouzi commented on JENKINS-30383 Re: SynchronousNonBlockingStepExecution should allow restart of idempotent steps What's the workaround for this issue? How can we get our job to work? They keep throwing this exception and they fail 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.164977.1441876213000.1752.1568262540439%40Atlassian.JIRA.
[JIRA] (JENKINS-59324) "No valid crumb was included in the request" even with valid crumb supplied - after updating
Title: Message Title Rob Ormond created an issue Jenkins / JENKINS-59324 "No valid crumb was included in the request" even with valid crumb supplied - after updating Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-09-12 03:53 Environment: 2.176.3 Priority: Critical Reporter: Rob Ormond Since upgrading to 2.176.3, my previous node script to trigger a Jenkins job remotely has stopped working, I now get an error 403: No valid crumb was included in the request The steps my script is performing are: HTTP GET on https://username:password@jenkinsurl/crumbIssuer/api/json Parse output to get a crumb (this is still working, I get a crumb) HTTP POST to https://username:password@jenkinsurl/job/blah/buildWithParameters?token=blah=blah with header= 'Jenkins-Crumb': crumb from step 1 Receives response 403: No valid crumb was included in the request This started straight after the upgrade.
[JIRA] (JENKINS-57795) Orphaned EC2 instances after Jenkins restart
Title: Message Title
Raihaan Shouhell commented on JENKINS-57795
Re: Orphaned EC2 instances after Jenkins restart
From this log ``` WARNING: SlaveTemplate {ami='ami-', labels='build-yocto-persistent'} . Node stopped is neither pending, neither running, its {2}. Terminate provisioning ``` It says that the node has been stopped. Btw are you on ondemand slaves or spots
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.199745.1559315049000.1740.1568256420393%40Atlassian.JIRA.
[JIRA] (JENKINS-59320) Support plugin should log all running jobs when bundle is generated
Title: Message Title Owen Wood commented on JENKINS-59320 Re: Support plugin should log all running jobs when bundle is generated https://github.com/jenkinsci/support-core-plugin/pull/188 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.201871.1568228336000.1737.1568250300097%40Atlassian.JIRA.
[JIRA] (JENKINS-59320) Support plugin should log all running jobs when bundle is generated
Title: Message Title Owen Wood updated JENKINS-59320 Jenkins / JENKINS-59320 Support plugin should log all running jobs when bundle is generated Change By: Owen Wood 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.201871.1568228336000.1735.1568250240361%40Atlassian.JIRA.
[JIRA] (JENKINS-59323) "java.io.IOException: Read-only file system" when saving Job Configuration
Title: Message Title Asta Saidak updated an issue Jenkins / JENKINS-59323 "java.io.IOException: Read-only file system" when saving Job Configuration Change By: Asta Saidak Attempting to save a Job Configuration will error. Also prevents user from starting new jobs. Attempting to create a file manually in the same folder will result in the same error message. Stack tracejava.io.IOException: Read-only file system at java.io.UnixFileSystem.createFileExclusively(Native Method) at java.io.File.createTempFile(File.java:2024) at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:142)Caused: java.io.IOException: Failed to create a temporary file in /var/lib/jenkins/jobs/Custom_Baseline/jobs/DEPLOY_CUSTOM_vFTD at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:144) at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:109) at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:84) at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:74) at hudson.XmlFile.write(XmlFile.java:187) at hudson.model.AbstractItem.save(AbstractItem.java:601) at hudson.model.Job.save(Job.java:191) at hudson.model.AbstractProject.save(AbstractProject.java:289) at hudson.BulkChange.commit(BulkChange.java:98) at hudson.model.Job.doConfigSubmit(Job.java:1351) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:772) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) 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:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at
[JIRA] (JENKINS-59323) "java.io.IOException: Read-only file system" when saving Job Configuration
Title: Message Title Asta Saidak created an issue Jenkins / JENKINS-59323 "java.io.IOException: Read-only file system" when saving Job Configuration Issue Type: Task Assignee: Unassigned Components: core Created: 2019-09-12 00:39 Environment: Jenkins version 2.164.3 Priority: Blocker Reporter: Asta Saidak Attempting to save a Job Configuration will error. Also prevents user from starting new jobs. Stack trace java.io.IOException: Read-only file system at java.io.UnixFileSystem.createFileExclusively(Native Method) at java.io.File.createTempFile(File.java:2024) at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:142) Caused: java.io.IOException: Failed to create a temporary file in /var/lib/jenkins/jobs/Custom_Baseline/jobs/DEPLOY_CUSTOM_vFTD at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:144) at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:109) at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:84) at hudson.util.AtomicFileWriter.(AtomicFileWriter.java:74) at hudson.XmlFile.write(XmlFile.java:187) at hudson.model.AbstractItem.save(AbstractItem.java:601) at hudson.model.Job.save(Job.java:191) at hudson.model.AbstractProject.save(AbstractProject.java:289) at hudson.BulkChange.commit(BulkChange.java:98) at hudson.model.Job.doConfigSubmit(Job.java:1351) at hudson.model.AbstractProject.doConfigSubmit(AbstractProject.java:772) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.interceptor.RequirePOST$Processor.invoke(RequirePOST.java:77) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title
Andrius Štikonas edited a comment on JENKINS-53162
Re: Blueocean support for visualizing stages in parallel block in scripted pipeline
My example is the same as above. It's just that in version 1.9.0 all those bugs that prevented clicking on stages got fixed (they affected declarative pipeline too). {code:java}import org.jenkinsci.plugins.pipeline.modeldefinition.actions.ExecutionModelActionimport org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTStagesif (!currentBuild.rawBuild.getAction(ExecutionModelAction))currentBuild.rawBuild.addAction(new ExecutionModelAction(new ModelASTStages(null))) parallel ( "one": { stage("one") { stage("one-child1") {println "one-child1" } stage("one-child2") {println "one-child2" }} }, "two": {stage("two") { stage("two-child1") {println "two-child1" } stage("two-child2") {println "two-child2" }} }, "three": {stage("three") { stage("three-child1") {println "three-child1" } stage("three-child2") {println "three-child2" }} }) { code}
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.1664.1568242443907%40Atlassian.JIRA.
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title
Andrius Štikonas edited a comment on JENKINS-53162
Re: Blueocean support for visualizing stages in parallel block in scripted pipeline
My example is the same as above. It's just that in version 1.9.0 all those bugs that prevented clicking on stages got fixed (they affected declarative pipeline too). {{ {code:java} import org.jenkinsci.plugins.pipeline.modeldefinition.actions. ExecutionModelActionimport ExecutionModelActionimport org.jenkinsci.plugins.pipeline.modeldefinition.ast. ModelASTStagesif ModelASTStagesif (!currentBuild.rawBuild.getAction(ExecutionModelAction)) }} currentBuild.rawBuild.addAction(new ExecutionModelAction(new ModelASTStages(null))) {{parallel (}} {{ "one": {}} {{ stage("one") {}} { { stage("one-child1") code } }{{Unknown macro: \{ println "one-child1" }}}{{stage("one-child2") {}} {{ println "one-child2"}}{{ }}}{{ }}}{{ },}}{{ "two": {}}{{ stage("two") {}}{{ stage("two-child1")}}{{Unknown macro: \{ println "two-child1" }}}{{stage("two-child2") {}}{{ println "two-child2"}}{{ }}}{{ }}}{{ },}}{{ "three": {}}{{ stage("three") {}}{{ stage("three-child1")}}{{Unknown macro: \{ println "three-child1" }}}{{stage("three-child2") {}}{{ println "three-child2"}}{{ }}}{{ }}}{{ }}}{{ )}}{{ }}
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-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title
Andrius Štikonas edited a comment on JENKINS-53162
Re: Blueocean support for visualizing stages in parallel block in scripted pipeline
My example is the same as above. It's just that in version 1.9.0 all those bugs that prevented clicking on stages got fixed (they affected declarative pipeline too). {{ import org.jenkinsci.plugins.pipeline.modeldefinition.actions.ExecutionModelActionimport org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTStagesif (!currentBuild.rawBuild.getAction(ExecutionModelAction)) }} currentBuild.rawBuild.addAction(new ExecutionModelAction(new ModelASTStages(null))) {{ parallel ( }} {{ "one": \ { }} {{ stage("one") { }} {{ stage("one-child1") }} { {Unknown macro: \{ println "one-child1" } }}{{ stage("one-child2") \ { }} {{ println "one-child2" }} {{ } }} {{ } }} {{ }, }} {{ "two": \ { }} {{ stage("two") { }} {{ stage("two-child1") }} { {Unknown macro: \{ println "two-child1" } }}{{ stage("two-child2") \ { }} {{ println "two-child2" }} {{ } }} {{ } }} {{ }, }} {{ "three": \ { }} {{ stage("three") { }} {{ stage("three-child1") }} { {Unknown macro: \{ println "three-child1" } }}{{ stage("three-child2") \ { }} {{ println "three-child2" }} {{ } }} {{ } }} {{ } }} {{ ) }}{{ }}
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
[JIRA] (JENKINS-53162) Blueocean support for visualizing stages in parallel block in scripted pipeline
Title: Message Title
Andrius Štikonas commented on JENKINS-53162
Re: Blueocean support for visualizing stages in parallel block in scripted pipeline
My example is the same as above. It's just that in version 1.9.0 all those bugs that prevented clicking on stages got fixed (they affected declarative pipeline too). import org.jenkinsci.plugins.pipeline.modeldefinition.actions.ExecutionModelActionimport org.jenkinsci.plugins.pipeline.modeldefinition.ast.ModelASTStagesif (!currentBuild.rawBuild.getAction(ExecutionModelAction)) currentBuild.rawBuild.addAction(new ExecutionModelAction(new ModelASTStages(null))) parallel ( "one": { stage("one") { stage("one-child1") { println "one-child1" } stage("one-child2") { println "one-child2" } } }, "two": { stage("two") { stage("two-child1") { println "two-child1" } stage("two-child2") { println "two-child2" } } }, "three": { stage("three") { stage("three-child1") { println "three-child1" } stage("three-child2") { println "three-child2" } } } )
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.1466.1568242321440%40Atlassian.JIRA.
[JIRA] (JENKINS-58887) Create internal tasks and public tasks
Title: Message Title Mez Pahlan updated JENKINS-58887 Jenkins / JENKINS-58887 Create internal tasks and public tasks Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Released As: 0.5.0 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.201220.1565541319000.1464.156824199%40Atlassian.JIRA.
[JIRA] (JENKINS-58887) Create internal tasks and public tasks
Title: Message Title Mez Pahlan commented on JENKINS-58887 Re: Create internal tasks and public tasks https://github.com/jenkinsci/appcenter-plugin/pull/20 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.201220.1565541319000.1463.1568240460154%40Atlassian.JIRA.
[JIRA] (JENKINS-58887) Create internal tasks and public tasks
Title: Message Title Mez Pahlan updated JENKINS-58887 Jenkins / JENKINS-58887 Create internal tasks and public tasks Change By: Mez Pahlan Status: In Progress 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.201220.1565541319000.1462.1568240460125%40Atlassian.JIRA.
[JIRA] (JENKINS-58329) Added environment variable parsing in file path for App Center Plugin
Title: Message Title Mez Pahlan updated JENKINS-58329 Jenkins / JENKINS-58329 Added environment variable parsing in file path for App Center Plugin Change By: Mez Pahlan Status: Fixed but Unreleased Resolved Released As: 0.4.0 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.200440.156220641.1460.1568240400293%40Atlassian.JIRA.
[JIRA] (JENKINS-59322) create a job for hit run
Title: Message Title tarinipmohanty 1991 assigned an issue to tarinipmohanty 1991 Jenkins / JENKINS-59322 create a job for hit run Change By: tarinipmohanty 1991 Assignee: Pritish Panda tarinipmohanty 1991 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.201873.1568239823000.1458.1568239920127%40Atlassian.JIRA.
[JIRA] (JENKINS-59322) create a job for hit run
Title: Message Title tarinipmohanty 1991 assigned an issue to Pritish Panda Jenkins / JENKINS-59322 create a job for hit run Change By: tarinipmohanty 1991 Assignee: tarinipmohanty 1991 Pritish Panda 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.201873.1568239823000.1456.1568239860219%40Atlassian.JIRA.
[JIRA] (JENKINS-59322) create a job for hit run
Title: Message Title tarinipmohanty 1991 created an issue Jenkins / JENKINS-59322 create a job for hit run Issue Type: Story Assignee: tarinipmohanty 1991 Components: maven-plugin Created: 2019-09-11 22:10 Environment: Test Priority: Major Reporter: tarinipmohanty 1991 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59321) The git-branch-source plugin seems to have broken from 2.5.3 -> 2.5.7
Title: Message Title Steve Boardwell created an issue Jenkins / JENKINS-59321 The git-branch-source plugin seems to have broken from 2.5.3 -> 2.5.7 Issue Type: Bug Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-09-11 21:44 Environment: Jenkins: 2.176.3 Plugins: ace-editor:1.1 ansible:1.0 ant:1.10 antisamy-markup-formatter:1.6 apache-httpcomponents-client-4-api:4.5.5-3.0 artifactory:3.4.0 authentication-tokens:1.3 aws-java-sdk:1.11.594 badge:1.8 basic-branch-build-strategies:1.3.2 blueocean:1.19.0 blueocean-autofavorite:1.2.4 blueocean-bitbucket-pipeline:1.19.0 blueocean-commons:1.19.0 blueocean-config:1.19.0 blueocean-core-js:1.19.0 blueocean-dashboard:1.19.0 blueocean-display-url:2.3.0 blueocean-events:1.19.0 blueocean-executor-info:1.19.0 blueocean-git-pipeline:1.19.0 blueocean-github-pipeline:1.19.0 blueocean-i18n:1.19.0 blueocean-jira:1.19.0 blueocean-jwt:1.19.0 blueocean-personalization:1.19.0 blueocean-pipeline-api-impl:1.19.0 blueocean-pipeline-editor:1.19.0 blueocean-pipeline-scm-api:1.19.0 blueocean-rest:1.19.0 blueocean-rest-impl:1.19.0 blueocean-web:1.19.0 bouncycastle-api:2.17 branch-api:2.5.4 cloudbees-bitbucket-branch-source:2.4.6 cloudbees-folder:6.9 command-launcher:1.3 config-file-provider:3.6.2 configuration-as-code:1.30 configuration-as-code-groovy:1.1 copyartifact:1.42.1 credentials:2.3.0 credentials-binding:1.20 display-url-api:2.3.2 docker-commons:1.15 docker-workflow:1.19 durable-task:1.30 external-monitor-job:1.7 favorite:2.3.2 gatling:1.2.6 gatling-check:1.0.0 git:3.12.1 git-client:2.8.4 git-server:1.8 gitea:1.1.2 github:1.29.4 github-api:1.95 github-branch-source:2.5.7 github-oauth:0.33 gitlab-plugin:1.5.12 google-login:1.6 gradle:1.34 greenballs:1.15 handlebars:1.1.1 handy-uri-templates-2-api:2.1.7-1.0 hashicorp-vault-plugin:2.5.0 htmlpublisher:1.18 http_request:1.8.23 ivy:2.1 jackson2-api:2.9.9.1 javadoc:1.5 jdk-tool:1.3 jenkins-design-language:1.19.0 jira:3.0.9 job-dsl:1.76 jquery:1.12.4-1 jquery-detached:1.2.1 jquery-ui:1.0.2 jsch:0.1.55.1 junit:1.28 jx-resources:1.0.37 kubernetes:1.19.0 kubernetes-client-api:1.0.0 kubernetes-credentials:0.4.1 kubernetes-credentials-provider:0.12.1 ldap:1.20 localization-support:1.1 localization-zh-cn:1.0.8 lockable-resources:2.5 mailer:1.27 matrix-auth:2.4.2 matrix-project:1.14 maven-plugin:3.4 mercurial:2.8 metrics:4.0.2.6 momentjs:1.1.1 pam-auth:1.5.1 pipeline-build-step:2.9 pipeline-graph-analysis:1.10 pipeline-input-step:2.11 pipeline-milestone-step:1.3.1 pipeline-model-api:1.3.9
[JIRA] (JENKINS-58383) Disable aggregated analysis results
Title: Message Title Ulli Hafner commented on JENKINS-58383 Re: Disable aggregated analysis results Should this be something in the UI, so that an individual user can disable/hide some of the charts? Or a server side option for all users, that needs to be specified in the Jenkinsfile as a parameter? 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.200507.1562597544000.1449.1568235600330%40Atlassian.JIRA.
[JIRA] (JENKINS-58383) Disable aggregated analysis results
Title: Message Title Ulli Hafner assigned an issue to Ulli Hafner Jenkins / JENKINS-58383 Disable aggregated analysis results 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.200507.1562597544000.1443.1568235420527%40Atlassian.JIRA.
[JIRA] (JENKINS-58383) Disable aggregated analysis results
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-58383 Disable aggregated analysis results Change By: Ulli Hafner Labels: help-wanted newbie-friendly 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.200507.1562597544000.1445.1568235420561%40Atlassian.JIRA.
[JIRA] (JENKINS-26091) Marker interface for things with URL
Title: Message Title Jesse Glick commented on JENKINS-26091 Re: Marker interface for things with URL A Jenkins-specific interface to retrofit the existing duck-typed String getUrl() signature. 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.159671.1418771876000.1440.1568233800260%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Jesse Glick commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP As a plugin developer, I want a safe place to publish static assets Well, yes, but also we want admins to stop recklessly disabling CSP because of the many things that inevitably break when it is enabled and for which Googling the error message gives you bad advice. I'd imagine we should try to support all the listed suggestions from Jesse Glick Maybe I should clarify: the list is in order from easiest to configure to hardest to configure (in general). So if it is seems that merely having a nonequal host suffices for protection, then https://static.dev.mycorp.com/ would be the most attractive option as it only requires that your DNS grant for Jenkins accepts wildcards, which it may already. The code in Jenkins need not care at all which host you choose, but we need to have a canonical recommendation for the reverse proxy that is likely to be implementable. Any directory browser that requires authentication See above. Daniel Beck and I are both assuming that the feature is fully usable when the DirectoryBrowserSupport.owner is accessible only to certain authenticated users, because the static “site” is serving content only from specially constructed URLs that encode sufficient credentials. See for example what GitHub does when showing a Raw link for a file in a private repository. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working with multiple charts
Title: Message Title Ulli Hafner updated JENKINS-57857 Jenkins / JENKINS-57857 Dashboard - 'Select subset of tools' not working with multiple charts Change By: Ulli Hafner Status: In Progress 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.199818.1559728494000.1432.1568232600456%40Atlassian.JIRA.
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working with multiple charts
Title: Message Title Ulli Hafner started work on JENKINS-57857 Change By: Ulli Hafner 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.199818.1559728494000.1428.1568232600402%40Atlassian.JIRA.
[JIRA] (JENKINS-57857) Dashboard - 'Select subset of tools' not working with multiple charts
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57857 Dashboard - 'Select subset of tools' not working with multiple charts Change By: Ulli Hafner URL: https://github.com/jenkinsci/warnings-ng-plugin/pull/208 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.199818.1559728494000.1430.1568232600427%40Atlassian.JIRA.
[JIRA] (JENKINS-59114) Maven output is not colorized
Title: Message Title Eyal Goren commented on JENKINS-59114 Re: Maven output is not colorized Can you show me a sample of declarative pipeline- how it should work? I will be happy to test 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.201539.1566962562000.1426.1568232000273%40Atlassian.JIRA.
[JIRA] (JENKINS-59114) Maven output is not colorized
Title: Message Title Falko Modler commented on JENKINS-59114 Re: Maven output is not colorized Sorry, must have missed that. The formatting is a bit off, though. This actually works for me. The one main difference is that I am using withMaven and then sh "mvn ...". And my Jenkins is running on CentOS 7, yours is a Windows machine... 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.201539.1566962562000.1424.1568231640224%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Matt Sicker commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP I've read through some of the older issues related to this. So it seems like the main purpose of this feature request is to allow for the following scenario: As a plugin developer, I want a safe place to publish static assets on a separate domain so that a content security policy can be used to help prevent published content from interacting with and exploiting Jenkins itself. For example, if I wanted to publish some test results that have a fancy _javascript_-based UI, it would be nice to host that on its own domain so that it can't interact with Jenkins _javascript_ files or similar. This would also be useful to avoid a vector for exploiting XSS vulnerabilities in Jenkins. Based on how CSP works as Kalle Niemitalo mentions, we have to distinguish based on the domain name mostly, not the URL (other than the scheme and port). So I'd imagine we should try to support all the listed suggestions from Jesse Glick except for the subdirectory one. Any directory browser that requires authentication wouldn't really benefit from a separate domain name like example-cdn.com to example.com due to needing cookies for both. Static resources that are publicly available can benefit from a separate domain for CDN usage, though that seems a bit overkill for Jenkins (or maybe it isn't?). 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
[JIRA] (JENKINS-59320) Support plugin should log all running jobs when bundle is generated
Title: Message Title Owen Wood started work on JENKINS-59320 Change By: Owen Wood 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.201871.1568228336000.1417.1568228400249%40Atlassian.JIRA.
[JIRA] (JENKINS-59320) Support plugin should log all running jobs when bundle is generated
Title: Message Title Owen Wood created an issue Jenkins / JENKINS-59320 Support plugin should log all running jobs when bundle is generated Issue Type: New Feature Assignee: Owen Wood Components: support-core-plugin Created: 2019-09-11 18:58 Priority: Minor Reporter: Owen Wood There are numerous situations when Support is investigating a customer issue and needs to know what builds were running at a point in time. Today there is no way to see that. When a bundle is generated, we should write a list of all running builds to a file. Add Comment
[JIRA] (JENKINS-59319) WaitUntil step missing "initialRecurrencePeriod" option
Title: Message Title
Brendt Lucas updated an issue
Jenkins / JENKINS-59319
WaitUntil step missing "initialRecurrencePeriod" option
Change By:
Brendt Lucas
The latest release of ` {{ workflow-basic-steps ` }} was {{ 2.18 }} in June of 2019.Back in February 2019, [this commit|https://github.com/jenkinsci/workflow-basic-steps-plugin/commit/b5dce5de3124f05a7b5ccd2c64ea06345a2f9fb4] was added but is not included in the 2.18 release tag. Can anyone explain this? It looks like it was omitted for some reason.Is there any chance a new release of workflow-basic-steps can occur to include this functionality?
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-59319) WaitUntil step missing "initialRecurrencePeriod" option
Title: Message Title Brendt Lucas created an issue Jenkins / JENKINS-59319 WaitUntil step missing "initialRecurrencePeriod" option Issue Type: Bug Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2019-09-11 18:55 Environment: workflow-basic-steps:2.18 Labels: pipeline plugin Priority: Minor Reporter: Brendt Lucas The latest release of `workflow-basic-steps` was 2.18 in June of 2019. Back in February 2019, this commit was added but is not included in the 2.18 release tag. Can anyone explain this? It looks like it was omitted for some reason. Is there any chance a new release of workflow-basic-steps can occur to include this functionality? Add Comment
[JIRA] (JENKINS-26091) Marker interface for things with URL
Title: Message Title Matt Sicker commented on JENKINS-26091 Re: Marker interface for things with URL Can this use the stapler class WithWellKnownURL, or are you thinking of a Jenkins-specific interface? 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.159671.1418771876000.1411.1568227680309%40Atlassian.JIRA.
[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException
Title: Message Title Ian Williams commented on JENKINS-58940 Re: ActiveDirectory.updateUserCache uncaughtException Charles Tudor, We (the OP) do not have Prometheus or plugin permissive-script-security installed. While ldap plugin is installed, we use AD, not ldap, so the issue remains unresolved. 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.201284.1565805612000.1399.1568227440307%40Atlassian.JIRA.
[JIRA] (JENKINS-58940) ActiveDirectory.updateUserCache uncaughtException
Title: Message Title Charles Tudor commented on JENKINS-58940 Re: ActiveDirectory.updateUserCache uncaughtException We are getting a NPE when logging in. I was able to narrow down the plugins to ldap:1.20 prometheus:2.0.6 jobConfigHistory:2.24 permissive-script-security:0.5 Going back to prometheus:2.0.0 or permissive-script-security:0.4 fixes the issue. Stack trace java.lang.NullPointerException at hudson.Util.fileToPath(Util.java:1501) at hudson.model.UserIdMapper.createDirectoryForNewUser(UserIdMapper.java:145) at hudson.model.UserIdMapper.putIfAbsent(UserIdMapper.java:92) at hudson.model.User.putUserFolderIfAbsent(User.java:806) at hudson.model.User.constructUserConfigFile(User.java:802) at hudson.model.User.save(User.java:796) at hudson.model.User.addProperty(User.java:336) at hudson.security.LDAPSecurityRealm.updateUserDetails(LDAPSecurityRealm.java:835) at hudson.security.LDAPSecurityRealm.updateUserDetails(LDAPSecurityRealm.java:796) at hudson.security.LDAPSecurityRealm.loadUserByUsername(LDAPSecurityRealm.java:786) at jenkins.security.UserDetailsCache$Retriever.call(UserDetailsCache.java:172) at jenkins.security.UserDetailsCache$Retriever.call(UserDetailsCache.java:161) at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767) at com.google.common.cache.LocalCache$LoadingValueReference.loadFuture(LocalCache.java:3568) at com.google.common.cache.LocalCache$Segment.loadSync(LocalCache.java:2350) at com.google.common.cache.LocalCache$Segment.lockedGetOrLoad(LocalCache.java:2313) at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2228) Caused: com.google.common.util.concurrent.UncheckedExecutionException at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2234) at com.google.common.cache.LocalCache.get(LocalCache.java:3965) at com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4764) at jenkins.security.UserDetailsCache.loadUserByUsername(UserDetailsCache.java:127) at hudson.model.User$UserIDCanonicalIdResolver.resolveCanonicalId(User.java:1239) at hudson.model.User$CanonicalIdResolver.resolve(User.java:1180) at hudson.model.User.get(User.java:505) at hudson.model.User.getOrCreateByIdOrFullName(User.java:570) at hudson.model.User.get(User.java:551) at hudson.security.LDAPSecurityRealm.updateUserDetails(LDAPSecurityRealm.java:802) at hudson.security.LDAPSecurityRealm.updateUserDetails(LDAPSecurityRealm.java:796) at hudson.security.LDAPSecurityRealm.updateUserDetails(LDAPSecurityRealm.java:790) at hudson.security.LDAPSecurityRealm$LDAPAuthenticationManager.authenticate(LDAPSecurityRealm.java:997) at org.acegisecurity.ui.webapp.AuthenticationProcessingFilter.attemptAuthentication(AuthenticationProcessingFilter.java:74) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:252) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at
[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent
Title: Message Title
Giuseppe Valente edited a comment on JENKINS-58705
Re: Change default working dir to /home/jenkins/agent
This required a configuration change, without any changes it causes this error when using {{docker image:}}: {{Error: docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "chdir to cwd (\"/home/jenkins/agent/workspace/myjob\") set in config.json failed: permission denied": unknown. }} It should at least be release-noted.
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.200995.1564403053000.1385.1568225409909%40Atlassian.JIRA.
[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent
Title: Message Title
Giuseppe Valente edited a comment on JENKINS-58705
Re: Change default working dir to /home/jenkins/agent
This required a configuration change, without any changes it causes this error when using ` {{ docker image: ` }} : ``` {{ Error: docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "chdir to cwd (\"/home/jenkins/agent/workspace/myjob\") set in config.json failed: permission denied": unknown. }} ``` It should at least be release-noted.
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.200995.1564403053000.1383.1568225340269%40Atlassian.JIRA.
[JIRA] (JENKINS-58705) Change default working dir to /home/jenkins/agent
Title: Message Title Giuseppe Valente commented on JENKINS-58705 Re: Change default working dir to /home/jenkins/agent This required a configuration change, without any changes it causes this error when using `docker image:`: ``` Error: docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "chdir to cwd (\"/home/jenkins/agent/workspace/myjob\") set in config.json failed: permission denied": unknown. ``` It should at least be release-noted. 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.200995.1564403053000.1379.1568225100173%40Atlassian.JIRA.
[JIRA] (JENKINS-58281) Pipeline job's builds are missing randomly in bulk
Title: Message Title Ariel M updated an issue Jenkins / JENKINS-58281 Pipeline job's builds are missing randomly in bulk Change By: Ariel M Priority: Critical Blocker 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.200345.1561974734000.1377.1568223660273%40Atlassian.JIRA.
[JIRA] (JENKINS-59302) Name fields of AWS Secrets Manager Secrets are not distinct
Title: Message Title Nat Talbot updated an issue Jenkins / JENKINS-59302 Name fields of AWS Secrets Manager Secrets are not distinct Change By: Nat Talbot Environment: Running off of the feature/multiple-credential-types branch , but this should be an overall issue not specific to the branch 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.201850.1568146774000.1375.156880205%40Atlassian.JIRA.
[JIRA] (JENKINS-59302) Name fields of AWS Secrets Manager Secrets are not distinct
Title: Message Title Nat Talbot commented on JENKINS-59302 Re: Name fields of AWS Secrets Manager Secrets are not distinct Aha, looks like it was introduced by the changes, after re-installing from master. 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.201850.1568146774000.1373.1568221140254%40Atlassian.JIRA.
[JIRA] (JENKINS-59302) Name fields of AWS Secrets Manager Secrets are not distinct
Title: Message Title Nat Talbot commented on JENKINS-59302 Re: Name fields of AWS Secrets Manager Secrets are not distinct Was this introduced from the multiple-credential-types changes, or is it a separate issue? I had assumed it was a separate issue, but looking at the changes I'd guess it's related to the DescriptorImpl in AwsCredentials.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.201850.1568146774000.1371.1568220360177%40Atlassian.JIRA.
[JIRA] (JENKINS-59318) fill in user-agent with something specific to github-branch-source-plugin
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-59318 fill in user-agent with something specific to github-branch-source-plugin Issue Type: Improvement Assignee: Unassigned Components: github-branch-source-plugin Created: 2019-09-11 16:22 Priority: Minor Reporter: Josh Soref There are lots of things that use OkHttp. OkHttp okhttp#1063 provides a default user-agent, but that does make it easy to figure out what is (ab)using quotas. It's traditional for clients of libraries to fill in their own useragent (typically embedding their underlying agent w/in the field). For a general sense of how user-agents are written, please see: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent/Firefox In general, basically the syntax is: TokenA/1.1 (platform; information; ...) TokenB/2.3 ... The GitHub.com folks reported that the majority of my quota was spent by: okhttp/2.7.5 But I can't easily tell if that's: Some Scala code Sbt This jenkins plugin Some other jenkins plugin Ideally, the user-agent
[JIRA] (JENKINS-58219) Active Choices Reactive Parameter Groovy script returning String instead of List
Title: Message Title Ioannis Moutsatsos commented on JENKINS-58219 Re: Active Choices Reactive Parameter Groovy script returning String instead of List Brett Hand AC parameters have not been tested in use with Jenkinsfile and we only have experience using them in 'freestyle' type builds. Nonetheless, in these cases returning a list of Strings is required for proper display in the build form UI. The parameters are passed to the build as text with the selected options as a comma separated String. You may need to tokenize this string to return a list. Note that 'splitting' a string with Groovy returns a String[] not a list I hope this helps. And any experience with using AC parameters in jenkinsfile is always useful (for future reference). Thank you! 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.200279.1561574404000.1367.1568217300202%40Atlassian.JIRA.
[JIRA] (JENKINS-59114) Maven output is not colorized
Title: Message Title Eyal Goren commented on JENKINS-59114 Re: Maven output is not colorized You can see in the description that the mvn command contains this parameter- bat 'mvn -Dstyle.color=always clean install' 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.201539.1566962562000.1364.1568217240114%40Atlassian.JIRA.
[JIRA] (JENKINS-59188) How Can I access multiple HTML text box values separately using Active Choice Reactive Reference Parameter
Title: Message Title Ioannis Moutsatsos closed an issue as Fixed Question answered Jenkins / JENKINS-59188 How Can I access multiple HTML text box values separately using Active Choice Reactive Reference Parameter Change By: Ioannis Moutsatsos 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
[JIRA] (JENKINS-59188) How Can I access multiple HTML text box values separately using Active Choice Reactive Reference Parameter
Title: Message Title
Ioannis Moutsatsos commented on JENKINS-59188
Re: How Can I access multiple HTML text box values separately using Active Choice Reactive Reference Parameter
If you must have multiple parameters into a single Jenkins parameter 'Frontend_Merge' you can have an AC REF parameter that returns a json structure and then parse it in your build. So the 'Frontend_Merge' would return a value something like:
{
"ffchef_backend":[
"branch1",
"branch2"
],
"ffchef_frontend":[
"branch3",
"branch4"
]
}
Nonetheless, I would still recommend having a separate AC Ref for 'ffchef_backend' and another for ffchef_frontend'
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.201626.156743271.1359.1568216520183%40Atlassian.JIRA.
[JIRA] (JENKINS-59191) SPAM-Not an issue
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-59191 SPAM-Not an issue Change By: Ioannis Moutsatsos Summary: Jual Obat Kuat Asli Di Apotik Medan Dan Harganya SPAM-Not an issue Priority: Minor Trivial h1. *JUAL OBAT VIAGRA ASLI DI APOTIK CENTURY*[_*Viagra*_|https://apotektitangel.com/jual-obat-viagra-asli/] adalah salah satu obat kuat penunjang stamina ereksi yang banyak direkomendasikan oleh para dokter ahli di dunia sebagai obat disfungsi ereksi. _*Obat viagra asli*_ berbentuk pil berwarna biru dengan bentuk seperti wajik atau ketupat. Di _*indonesia*_, viagra dikenal sebagai obat yang ampuh untuk melawan disfungsi ereksi, yang artinya obat ini dapat membuat alat vital pria menjadi ereksi dengan keras dan juga tahan lama hingga hubungan seksual dengan pasangan selesai. Dengan kata lain, obat ini dianggap menjadi salah satu solusi yang membuat para pria lega dan tidak khawatir lagi dengan permasalahan seksual yang di alaminya.[!https://apotektitangel.com/wp-content/uploads/2019/04/viagra-asli.jpg|width=300,height=300!|https://apotektitangel.com/jual-obat-viagra-asli/]*Obat kuat viagra* memang salah satu obat yang banyak dicari, sebab dengan adanya obat ini dapat membantu aliran darah ke penis menjadi lancar sehingga orang yang mengkonsumsinya dapat mempertahankan ereksi. Beberapa pria memiliki permasalahan dalam ereksi, hal ini dapat memberikan pengaruh terhadap keharmonisan rumah tangga. Dimana ereksi dapat mempengaruhi ketika berhubungan badan. Tidak heran jika pria yang sulit ereksi menjadi tidak percaya diri ketika berhubungan bersama pasangan, hal inilah yang menjadi pemicu retaknya rumah tangga anda. Maka kehadiran obat ini dianggap menjadi solusi untuk anda yang memiliki permasalahan itu, namun masih banyak orang yang belum mengenal bagaimana cara kerja viagra dan siapa saja yang boleh mengkonsumsinya. Sebab terdapat beberapa aturan jika anda ingin mengkonsumsinya agar dapat bekerja dengan sangat efektif dan optimal.*Viagra asli* original pfizer usa atau yang biasa di sebut dengan _*pil biru*_ ini banyak di jual di Apotik Kimia Farma, Century, K24 di seluruh kota besar indonesia seperti Bogor, Jakarta, Tangerang, Bekasi, Depok, Semarang, Makassar, Palembang, Surabaya dan lain sebagainya.h3. *Ciri - Ciri Viagra Asli :* * Di kemas dalam 1 botol berisi 30 tablet * Rasanya sangat pahit * Tablet berwarna biru dan sangat keras * Pil berbentuk jajargenjang dengan tulisan Pfizer di bagian tengah * Tablet Viagra asli berbentuk jajargenjang dengan tulisan Pfizer di bagian
[JIRA] (JENKINS-59317) Spurious SCM change with a failed git call (e.g. network error)
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-59317 Spurious SCM change with a failed git call (e.g. network error) Change By: Mark Waite Assignee: Mark Waite 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.201868.1568210864000.1350.1568215380408%40Atlassian.JIRA.
[JIRA] (JENKINS-59191) Jual Obat Kuat Asli Di Apotik Medan Dan Harganya
Title: Message Title Ioannis Moutsatsos updated JENKINS-59191 SPAM! Jenkins / JENKINS-59191 Jual Obat Kuat Asli Di Apotik Medan Dan Harganya Change By: Ioannis Moutsatsos Status: Open Fixed but Unreleased 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. To view this discussion on the web visit
[JIRA] (JENKINS-57638) Custom ids/names not shown in origin when aggregating the report
Title: Message Title Ulli Hafner commented on JENKINS-57638 Re: Custom ids/names not shown in origin when aggregating the report This is conceptually not possible in the moment. IDs and Names are only stored for the Jenkins objects and not for the reports. I need to think in more detail about this problem to find a good 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.199568.1558606728000.1348.1568214660118%40Atlassian.JIRA.
[JIRA] (JENKINS-57638) Custom ids/names not shown in origin when aggregating the report
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57638 Custom ids/names not shown in origin when aggregating the report Change By: Ulli Hafner Summary: Custom named tools are not presenting with custom names/ ids /names not shown in origin when aggregating the report 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.199568.1558606728000.1344.1568214300291%40Atlassian.JIRA.
[JIRA] (JENKINS-57638) Custom ids/names not shown in origin when aggregating the report
Title: Message Title Ulli Hafner stopped work on JENKINS-57638 Change By: Ulli Hafner Status: In Progress Open 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.199568.1558606728000.1346.1568214300322%40Atlassian.JIRA.
[JIRA] (JENKINS-58420) Column shows "-" on failed builds
Title: Message Title Ulli Hafner updated JENKINS-58420 Jenkins / JENKINS-58420 Column shows "-" on failed builds Change By: Ulli Hafner Status: In Progress 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.200547.1562750576000.1342.1568214240592%40Atlassian.JIRA.
[JIRA] (JENKINS-59292) org.apache.commons.jelly.JellyTagException looking at Parasoft results
Title: Message Title Ulli Hafner commented on JENKINS-59292 Re: org.apache.commons.jelly.JellyTagException looking at Parasoft results Can you please try to reinstall the plugin? (Delete the warnings-ng folder and api file, and reinstall from the update manager?) 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.201836.1568099107000.1340.1568213820201%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Kalle Niemitalo commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP The frame-ancestors directive of Content-Security-Policy cannot distinguish between https://dev.mycorp.com/jenkins/ and https://dev.mycorp.com/static-jenkins/. See CSP: frame-ancestors should check origins, not URLs · Issue #311 · w3c/webappsec. The HTTP cookies set by Jenkins seem to be using HostOnly and HttpOnly, except the "screenResolution" cookie. I think this makes https://static.dev.mycorp.com/ and https://static-dev.mycorp.com/ less risky than they might otherwise be. 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.178741.1486645144000.1334.1568213220193%40Atlassian.JIRA.
[JIRA] (JENKINS-59114) Maven output is not colorized
Title: Message Title Falko Modler commented on JENKINS-59114 Re: Maven output is not colorized You have to add -Dstyle.color=always to the mvn invocation (not to MAVEN_OPTS like jansi.force). See: https://issues.jenkins-ci.org/browse/JENKINS-44543?focusedCommentId=331794=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-331794 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.201539.1566962562000.1332.1568211840302%40Atlassian.JIRA.
[JIRA] (JENKINS-46086) A changelog should be recorded for the first build of a PR
Title: Message Title Jean-Frédéric commented on JENKINS-46086 Re: A changelog should be recorded for the first build of a PR (The issue was closed as Resolved/Fixed, which based on my understanding was slightly misleading − it’s closed as duplicate of JENKINS-44849. Hopefully this is now clearer ) 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.184321.1502274268000.1325.1568211600272%40Atlassian.JIRA.
[JIRA] (JENKINS-46086) A changelog should be recorded for the first build of a PR
Title: Message Title Jean-Frédéric closed an issue as Duplicate Jenkins / JENKINS-46086 A changelog should be recorded for the first build of a PR Change By: Jean-Frédéric Status: In Progress 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.184321.1502274268000.1318.1568211542665%40Atlassian.JIRA.
[JIRA] (JENKINS-46086) A changelog should be recorded for the first build of a PR
Title: Message Title Jean-Frédéric updated JENKINS-46086 Jenkins / JENKINS-46086 A changelog should be recorded for the first build of a PR Change By: Jean-Frédéric Resolution: Fixed Status: Resolved In 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.184321.1502274268000.1309.1568211481612%40Atlassian.JIRA.
[JIRA] (JENKINS-46086) A changelog should be recorded for the first build of a PR
Title: Message Title Jean-Frédéric updated JENKINS-46086 Jenkins / JENKINS-46086 A changelog should be recorded for the first build of a PR Change By: Jean-Frédéric Status: In Review 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.184321.1502274268000.1311.1568211481679%40Atlassian.JIRA.
[JIRA] (JENKINS-59317) Spurious SCM change with a failed git call (e.g. network error)
Title: Message Title
Jim Klimov created an issue
Jenkins / JENKINS-59317
Spurious SCM change with a failed git call (e.g. network error)
Issue Type:
Improvement
Assignee:
Mark Waite
Components:
git-plugin
Created:
2019-09-11 14:07
Priority:
Minor
Reporter:
Jim Klimov
Our internal build farm's connection to the internet has its flaws, ups and downs, and sometimes during the downs we see gems like this: an effectively failed SCM poll ("Couldn't get remote head revision") is interpreted as a "Changes found" situation, and causes a build "Started by an SCM change", as the (failed) build's Polling Log says: Polling Log This page captures the polling log that triggered this build. Started on Sep 7, 2019 6:15:15 AM Using strategy: Specific revision [poll] Last Built Revision: Revision dee1deac2b8bc60039ea3cd2907afa708a967486 (release/IPM_Infra-1.4) using credential 955c217d-8133-41c2-9235-9ce3936ddca6 > git --version # timeout=10 using GIT_ASKPASS to set credentials 42ity-ci GH Token as password Setting http proxy: thunderbolt.roz.lab.etn.com:8081 > git ls-remote -h https://github.com/42ity/fty-outage.git # timeout=10 Unexpected ls-remote output line '' [poll] Couldn't get remote head revision Done. Took 23 sec Changes found In this particular situation (outage) as a result, this build fails quickly during checkout of sources with ``` ... Caused by: hudson.plugins.git.GitException: Command "git fetch --tags --progress https://github.com/42ity/fty-outage.git +refs/heads/release/IPM_Infra-1.4:refs/remotes/origin/release/IPM_Infra-1.4" returned status code 128: stdout: stderr: fatal: unable to access 'https://github.com/42ity/fty-outage.git/': The requested URL returned error: 503 ... ``` which is a reasonable outcome of a network outage (our proxy failed to fetch => 503)... however when the network comes back, the last-tried (green, long ago) revision is the same as the current HEAD, so no need to rebuild, as the branch's Git polling log says: Git Polling Log
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title
Jim Sears edited a comment on JENKINS-56750
Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Hi Anda,I'll give you the steps to recreate and then show why it is a bug.1) Create HostList in QC for 3 PCs.2) Create a Test Set in QC and add the same test 3 times. (This will create three instances of the same test.)3) Update the "Planned HostName" for each test. Assign a different PC to each test instance.4) Create a job in Jenkins using the QC Plugin and execute the Test Set.The results in the console output only shows the Test execution for one "Planned HostName" and it repeats it 3 times.The results should be one test instance for each Planned HostName.Here are the wrong results in console output: (See the [3].Run status: Job failed, total tests: 3, succeeded: 3, failures: 0, errors: 0Passed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files \ *[3]*DeleteTempFilesFailed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files \ *[3]*DeleteTempFilesPassed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files \ *[3]*DeleteTempFiles{color:#172b4d}{color} {color:#172b4d}This is what it should look like:{color}Run status: Job failed, total tests: 3, succeeded: 3, failures: 0, errors: 0Passed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files \ *[1]*DeleteTempFilesFailed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files \ *[2]*DeleteTempFilesPassed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files \ *[3]*DeleteTempFiles{color:#172b4d}{color} {color:#172b4d}The test is specific to the PC and if the results only show [3] then I can't tell if the which test passed or failed.{color}
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears commented on JENKINS-56750 Re: Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Hi Anda, I'll give you the steps to recreate and then show why it is a bug. 1) Create HostList in QC for 3 PCs. 2) Create a Test Set in QC and add the same test 3 times. (This will create three instances of the same test.) 3) Update the "Planned HostName" for each test. Assign a different PC to each test instance. 4) Create a job in Jenkins using the QC Plugin and execute the Test Set. The results in the console output only shows the Test execution for one "Planned HostName" and it repeats it 3 times. The results should be one test instance for each Planned HostName. Here are the wrong results in console output: (See the [3]. Run status: Job failed, total tests: 3, succeeded: 3, failures: 0, errors: 0 Passed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files*[3]*DeleteTempFiles Failed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files*[3]*DeleteTempFiles Passed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files*[3]*DeleteTempFiles This is what it should look like: Run status: Job failed, total tests: 3, succeeded: 3, failures: 0, errors: 0 Passed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files*[1]*DeleteTempFiles Failed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files*[2]*DeleteTempFiles Passed : Root\Automation CoE\LabMaintenance\LabMaintenance-Files*[3]*DeleteTempFiles The test is specific to the PC and if the results only show [3] then I can't tell if the which test passed or failed. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-59118) GHS MULTI Errors (Absolute Path and Illegal Char) In Warnings Next Generation Plugin
Title: Message Title Steve Kipping commented on JENKINS-59118 Re: GHS MULTI Errors (Absolute Path and Illegal Char) In Warnings Next Generation Plugin That fixed that problem too (UTF-8). Thanks again for all your support. 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.201547.1566987996000.1283.1568209500381%40Atlassian.JIRA.
[JIRA] (JENKINS-59168) Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system"
Title: Message Title Aliaksandr Kavaliou commented on JENKINS-59168 Re: Variable is not resolved in "Runtime Settings" of "LoadRunner-specific settings" of build-step "Execute Microfocus tests from file system" Great. Hope it will come into the next release which is probably happens in October. 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.201605.1567267759000.1281.1568208480180%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Jesse Glick commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP a way for Jenkins/Stapler to respond differently for a different domain (Host header) No deep surgery in Stapler is really necessary, I think. Would suffice for Jenkins to define an UnprotectedRootAction to serve the static content. Then you can configure your reverse proxy to map requests to the special domain to a path prefix of the Jenkins service. For example, this is straightforward to set up in Kubernetes using the nginx-ingress controller. As to handling non-anonymously-readable content, this can be handled in various ways. Probably something like BoundObjectTable with a one-hour expiry would suffice. (To save memory and allow links to be valid indefinitely so long as the user exists and retains access, perhaps you could support WithWellKnownURL, by encoding both a path from root to the DirectoryBrowserSupport.owner (via JENKINS-26091) and an Authentication.name in a Secret. Given a random initialization vector, I believe that is safe.) The critical question for me is what constraints are placed on the “second domain” by the non-CSP defenses built into browsers. This very much affects whether administrators will find it practical to set up such a route: the reverse proxy is just a matter of configuration, but getting a new or expanded DNS entry typically requires extra steps. For example, if Jenkins is normally served from https://dev.mycorp.com/jenkins/ then which of the following URL prefixes would be eligible for serving static content? https://dev.mycorp.com/static-jenkins/ https://static.dev.mycorp.com/ https://static-dev.mycorp.com/ https://mycorp-static.com/ https://static.mycorp.net/ Add Comment
[JIRA] (JENKINS-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Arnaud Richard commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError +1 for Andrew Ching status and solution. I initially used Windows installer to avoid Java version and configuration issues but they came back anyway! 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.192947.1533846304000.1249.1568206621168%40Atlassian.JIRA.
[JIRA] (JENKINS-58114) Remove the GAE mode from PCT
Title: Message Title Jesse Glick commented on JENKINS-58114 Re: Remove the GAE mode from PCT I do not believe this code has been used in years. Best to just delete it all. If someone ever wants to resurrect it, there is Git history. 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.200158.1561017039000.1244.1568204400482%40Atlassian.JIRA.
[JIRA] (JENKINS-58113) Remove the internal Maven mode from PCT
Title: Message Title Jesse Glick commented on JENKINS-58113 Re: Remove the internal Maven mode from PCT Agreed, this is just trouble. We should just use mvn from $PATH by default. 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.200157.1561016898000.1242.1568204340159%40Atlassian.JIRA.
[JIRA] (JENKINS-59297) File parameter causes two builds to be started
Title: Message Title Samuel Melm closed an issue as Not A Defect Turns out it's an issue with firefox Jenkins / JENKINS-59297 File parameter causes two builds to be started Change By: Samuel Melm 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. To view this discussion on the web visit
[JIRA] (JENKINS-14828) Rebuild plugin crashes when used in conjuction with Extended Choice Parameter
Title: Message Title ethorsa commented on JENKINS-14828 Re: Rebuild plugin crashes when used in conjuction with Extended Choice Parameter I run into the same problem as in JENKINS-22197: Jenkins 2.176.1 Extended Choice Parameter 0.78 Rebuilder 1.31 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.145529.1345145155000.1209.1568198220504%40Atlassian.JIRA.
[JIRA] (JENKINS-59316) Bug - java.lang.NullPointerException
Title: Message Title Sarfraaz Patel created an issue Jenkins / JENKINS-59316 Bug - java.lang.NullPointerException Issue Type: Bug Assignee: Unassigned Attachments: Screenshot 2019-09-11 at 11.29.39.png Components: core Created: 2019-09-11 10:30 Environment: Jenkins Version 2.164 Operating system Linux Labels: jenkins Priority: Blocker Reporter: Sarfraaz Patel Jenkins automatically turned on this morning and the following error message is showing. Stack trace java.lang.NullPointerException at hudson.security.TokenBasedRememberMeServices2.autoLogin(TokenBasedRememberMeServices2.java:164) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:104) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at
[JIRA] (JENKINS-59314) Jenkins CLI is not working
Title: Message Title Oliver Gondža assigned an issue to Unassigned Jenkins / JENKINS-59314 Jenkins CLI is not working Change By: Oliver Gondža Assignee: Oliver Gondža 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.201864.1568192776000.1205.1568197200149%40Atlassian.JIRA.
[JIRA] (JENKINS-59314) Jenkins CLI is not working
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59314 Jenkins CLI is not working Change By: Oliver Gondža Priority: Blocker Critical 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.201864.1568192776000.1203.1568197080397%40Atlassian.JIRA.
[JIRA] (JENKINS-59314) Jenkins CLI is not working
Title: Message Title Oliver Gondža updated an issue Jenkins / JENKINS-59314 Jenkins CLI is not working Change By: Oliver Gondža Component/s: core Component/s: cli-commander-plugin 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.201864.1568192776000.1201.1568197080371%40Atlassian.JIRA.
[JIRA] (JENKINS-59315) This agent is offline because Jenkins failed to launch the agent process on it.
Title: Message Title Sanjeev Kumar Narayanaswamy assigned an issue to Unassigned Jenkins / JENKINS-59315 This agent is offline because Jenkins failed to launch the agent process on it. Change By: Sanjeev Kumar Narayanaswamy Assignee: Sanjeev Kumar Narayanaswamy 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.201865.1568195725000.1199.1568196720071%40Atlassian.JIRA.
[JIRA] (JENKINS-59315) This agent is offline because Jenkins failed to launch the agent process on it.
Title: Message Title Sanjeev Kumar Narayanaswamy created an issue Jenkins / JENKINS-59315 This agent is offline because Jenkins failed to launch the agent process on it. Issue Type: Bug Assignee: Sanjeev Kumar Narayanaswamy Components: ssh-agent-plugin Created: 2019-09-11 09:55 Environment: Jenkins 2.38, SSh slave agent 1.26 Priority: Major Reporter: Sanjeev Kumar Narayanaswamy when ever i launch the agent i am getting below error in the console: Warning: no key algorithms provided; JENKINS-42959 disabled [03/27/19 10:36:13] [SSH] Opening SSH connection to 10.1.1.62:22. 10.1.1.62 java.io.IOException: There was a problem while connecting to 10.1.1.62:22 at com.trilead.ssh2.Connection.connect(Connection.java:834) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1324) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:831) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:820) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.net.UnknownHostException: 10.1.1.62 at java.net.InetAddress.getAllByName0(InetAddress.java:1259) at java.net.InetAddress.getAllByName(InetAddress.java:1171) at java.net.InetAddress.getAllByName(InetAddress.java:1105) at java.net.InetAddress.getByName(InetAddress.java:1055) at com.trilead.ssh2.transport.TransportManager.createInetAddress(TransportManager.java:166) at
[JIRA] (JENKINS-59302) Name fields of AWS Secrets Manager Secrets are not distinct
Title: Message Title Chris Kilding commented on JENKINS-59302 Re: Name fields of AWS Secrets Manager Secrets are not distinct Ah yes, I think this bug was introduced by accident, since my team defines all its jobs through either JobDSL or Jenkinsfiles (and not through the Web UI - where we would have noticed and caught this bug). It definitely needs fixing. 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.201850.1568146774000.1197.1568194980196%40Atlassian.JIRA.
[JIRA] (JENKINS-59313) Builds are not processed when triggered manually
Title: Message Title Stefan Mayer closed an issue as Won't Fix Misconfiguration of authorize project plugin was the problem Jenkins / JENKINS-59313 Builds are not processed when triggered manually Change By: Stefan Mayer 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
[JIRA] (JENKINS-59313) Builds are not processed when triggered manually
Title: Message Title Stefan Mayer assigned an issue to Stefan Mayer Jenkins / JENKINS-59313 Builds are not processed when triggered manually Change By: Stefan Mayer Assignee: Stefan Mayer 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.201863.1568191671000.1194.1568192820610%40Atlassian.JIRA.
[JIRA] (JENKINS-59314) Jenkins CLI is not working
Title: Message Title Akilesh DS created an issue Jenkins / JENKINS-59314 Jenkins CLI is not working Issue Type: Task Assignee: Oliver Gondža Attachments: jenkins-cli-issue.PNG Components: cli-commander-plugin Created: 2019-09-11 09:06 Priority: Blocker Reporter: Akilesh DS Requirement: We want to setup Jenkins CLI. To communicate from slave to master Jenkins. We have master(windows) and slave (master). master and slave have communicating via jnlp (HTTP) connection mode. Steps performed: Downloaded the Jenkins-cli.jar Ran command : java -jar jenkins-cli.jar -s help but we are getting below output instead of actual output. org.apache.sshd.common.util.security.AbstractSecurityProviderRegistrar getOrCreateProvider INFO: getOrCreateProvider(EdDSA) created instance of net.i2p.crypto.eddsa.EdDSASecurityProvider We tried adding the auth option, still we get the same error. **Please let us know if we are missing something in the configuration. Thanks in advance. Add Comment
[JIRA] (JENKINS-50331) JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen
Title: Message Title Pierre Beitz commented on JENKINS-50331 Re: JENKINS -Error Message:FATAL: null java.lang.StackOverflowError at com.microsoft.tfs.util.listeners.StandardListenerList$ListenerNode.addListener(StandardListen Is there an update on this issue? It looks like a duplicate of https://issues.jenkins-ci.org/browse/JENKINS-35432. It was also observed on a Jenkins 2.138.3 with TFS Plugin 5.142.0. It looks like the link shared by Allan might be helpful to cook a 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.189378.1521699501000.1187.1568192400330%40Atlassian.JIRA.
[JIRA] (JENKINS-59313) Builds are not processed when triggered manually
Title: Message Title Stefan Mayer updated an issue Jenkins / JENKINS-59313 Builds are not processed when triggered manually Change By: Stefan Mayer Environment: Google Kubernetes Engine ClusterKubernetes Version 1.12.8-gke.10Jenkins Version 2.176.3kubernetes-plugin Version 1. 18 19 . 3 0 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.201863.1568191671000.1184.1568191800077%40Atlassian.JIRA.
[JIRA] (JENKINS-59313) Builds are not processed when triggered manually
Title: Message Title
Stefan Mayer created an issue
Jenkins / JENKINS-59313
Builds are not processed when triggered manually
Issue Type:
Bug
Assignee:
Unassigned
Components:
kubernetes-plugin
Created:
2019-09-11 08:47
Environment:
Google Kubernetes Engine Cluster Kubernetes Version 1.12.8-gke.10 Jenkins Version 2.176.3 kubernetes-plugin Version 1.18.3
Labels:
kubernetes-plugin agents kubernetes
Priority:
Minor
Reporter:
Stefan Mayer
When builds are triggeres manually by the "Build Now" button, then an agent will be created, but the builds are not processed. I just get:
Started by user myuser
Running as myuser
Obtained Jenkinsfile from 95690226dba08354f99f1ef4adb30cf01fddee6d
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] readTrusted
Obtained build/jenkins/pod.yaml from 95690226dba08354f99f1ef4adb30cf01fddee6d
[Pipeline] podTemplate
[Pipeline] {
[Pipeline] node
Still waiting to schedule task
‘dr.how-jenkins-image-develop-7-90t6s-plm5r-kt00q’ is offline
If the build was triggered by a webhook, everything works as expected. The kubernetes plugin is configured as followed:
Name: Kubernetes
[JIRA] (JENKINS-59310) Revert changes for Lab Management
Title: Message Title Maria Narcisa Galan updated an issue Jenkins / JENKINS-59310 Revert changes for Lab Management Change By: Maria Narcisa Galan Labels: UFT 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.201860.1568185333000.1182.1568191620200%40Atlassian.JIRA.
[JIRA] (JENKINS-59312) Improvement: Enable variable in configuration (AppName, OwnerName...)
Title: Message Title Balthazar Frolin created an issue Jenkins / JENKINS-59312 Improvement: Enable variable in configuration (AppName, OwnerName...) Issue Type: Improvement Assignee: Mez Pahlan Components: appcenter-plugin Created: 2019-09-11 08:42 Priority: Minor Reporter: Balthazar Frolin Enable use of $variable in job configuration For fields : OwnerName AppName DistributionGroup Add Comment
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title
Daniel Beck edited a comment on JENKINS-41891
Re: Serve static files from second domain as an alternative to setting CSP
This is specifically about the functionality in {{DirectoryBrowserSupport}} that is affected by CSP from SECURITY-95 and breaks many plugins that follow the (anti)pattern of archiving a bunch of HTML files, then serving them via {{DirectoryBrowserSupport}} . We even had plugins programmatically disable CSP protection (SECURITY-309). Ideally we figure out a way for Jenkins/Stapler to respond differently for a different domain ( {{Host}} header) and implement something like github.com/githubusercontent.com on that domain.Ideally one {{DirectoryBrowserSupport}} would correspond to one random prefix (necessary since there would be no auth on the second domain to hijack), to not break relative links within a set of archived files, such as an archived set of Javadoc HTML files.
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.178741.1486645144000.1173.1568190780248%40Atlassian.JIRA.
[JIRA] (JENKINS-41891) Serve static files from second domain as an alternative to setting CSP
Title: Message Title Daniel Beck commented on JENKINS-41891 Re: Serve static files from second domain as an alternative to setting CSP This is specifically about the functionality in DirectoryBrowserSupport that is affected by CSP and breaks many plugins. Ideally we figure out a way for Jenkins/Stapler to respond differently for a different domain ( Host header) and implement something like github.com/githubusercontent.com on that domain. Ideally one DirectoryBrowserSupport would correspond to one random prefix (necessary since there would be no auth on the second domain to hijack), to not break relative links within a set of archived files, such as an archived set of Javadoc HTML files. 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.178741.1486645144000.1166.1568190420777%40Atlassian.JIRA.
[JIRA] (JENKINS-59301) Crowd 2 plugin not compatible with JDK11
Title: Message Title Ramon Leon commented on JENKINS-59301 Re: Crowd 2 plugin not compatible with JDK11 Adrien Lecharpentier Baptiste Mathus could you take a look here please 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.201849.156813782.1164.1568190420698%40Atlassian.JIRA.
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Wadeck Follonier commented on JENKINS-59167 Re: rssAll feed no longer contains Jenkins server URL, only incorrect relative path Uwe Schindler Thank you for the quick feedback! really appreciated 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.201604.1567266415000.1159.1568190360345%40Atlassian.JIRA.
[JIRA] (JENKINS-59167) rssAll feed no longer contains Jenkins server URL, only incorrect relative path
Title: Message Title Uwe Schindler commented on JENKINS-59167 Re: rssAll feed no longer contains Jenkins server URL, only incorrect relative path Just FYI, looks fine again: https://jenkins.thetaphi.de/view/Lucene-Solr/rssAll 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.201604.1567266415000.1155.1568190120224%40Atlassian.JIRA.
[JIRA] (JENKINS-38121) Patch file processing does not support UTF-8 encoding
Title: Message Title Xueqing Sun commented on JENKINS-38121 Re: Patch file processing does not support UTF-8 encoding I've encountered the same problem. I'm investigating the 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.174276.1473645004000.1153.156819140%40Atlassian.JIRA.
[JIRA] (JENKINS-55577) docker agent using a custom Dockerfile is broken with docker buildkit
Title: Message Title Michael Kriese edited a comment on JENKINS-55577 Re: docker agent using a custom Dockerfile is broken with docker buildkit This can be closed as fixed with docker-workflow-plugin 1.19 and pipeline-model-definition-plugin 1.4.0 (not yet released)https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/350 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.196741.1547472484000.1144.1568189640385%40Atlassian.JIRA.
[JIRA] (JENKINS-58565) Jenkins build not grabbing hptoolslauncher
Title: Message Title Roy Lu assigned an issue to Anda Sorina Laakso Jenkins / JENKINS-58565 Jenkins build not grabbing hptoolslauncher Change By: Roy Lu Assignee: Roy Lu Anda Sorina Laakso 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.200715.1563505716000.1141.1568189040254%40Atlassian.JIRA.
[JIRA] (JENKINS-58134) Some of the testcase status can't be parsed correctly
Title: Message Title Roy Lu resolved as Fixed Jenkins / JENKINS-58134 Some of the testcase status can't be parsed correctly Change By: Roy Lu Status: In Progress 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.200179.1561100594000.1138.1568188981233%40Atlassian.JIRA.
