[JIRA] (JENKINS-57364) jenkins cannot provision new agent with openstack-cloud-plugin
Title: Message Title agatha chen created an issue Jenkins / JENKINS-57364 jenkins cannot provision new agent with openstack-cloud-plugin Issue Type: Bug Assignee: Oliver Gondža Attachments: openstack-cloud-log.PNG Components: openstack-cloud-plugin Created: 2019-05-08 05:26 Environment: jenkins master OS: Red Hat Enterprise Linux Server 7.6 (Maipo) jenkins master : ver. 2.150.3 openstack-cloud-plugin: 2.45 openstack host: huracan 2.2 Priority: Minor Reporter: agatha chen I use openstack cloud plugin to provision agents, several days ago I found that it cannot create new agents. After I click "provision via OpenStack Cloud Plugin " button, it shows "provisioning started" and then nothing happened. the number of agents is not at maximum. No new instance is created on openstack host. And there are no error message from jenkins log. please check from attachment. the openstack host works fine and I can create new instances manually using same template that used in openstack cloud plugin.
[JIRA] (JENKINS-50937) GitHub Multibranch PR: unclear error message for PR with merge conflicts
Title: Message Title Liam Newman resolved as Fixed Lightweight checkout fixes this issue in v2.5.0 Jenkins / JENKINS-50937 GitHub Multibranch PR: unclear error message for PR with merge conflicts Change By: Liam Newman Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190075.1524477084000.20519.1557291420186%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Liam Newman updated JENKINS-56996 I'm going to resolve this as fixed and move forward. Christian Höltje Please comment if this is not fixed for you. Jenkins / JENKINS-56996 null permission lookup when pull-request's origin repo/branch is deleted on github Change By: Liam Newman Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198693.1555102536000.20510.1557279300687%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman updated JENKINS-57111 Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.20506.1557278640196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55363) Support different SSH providers
Title: Message Title Thai Pham commented on JENKINS-55363 Re: Support different SSH providers Ivan Fernandez Calvo, I meant to answer your previous comments, didn't mean to hijack it to get support. Anyway, how is the progress of this ticket? I can help to test it if you need a hand. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196466.154610799.20504.1557274080177%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Mike Sollanych commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records But maybe all of the failures to serialize come back to that bad commit, as opposed to whitelisting? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198924.1556132083000.20502.1557267960421%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Paul P edited a comment on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id EDIT: Looks like I spoke too soon, the problem re-appeared.I had this issue and uninstalling the plugin and re-installing it fixed it.To be specific: # backup your config.xml # uninstall the plugin # restart jenkins # re-install the plugin (I lost my configuration) # stop jenkins # replace the config.xml # start JenkinsI am using Jenkins 2.176 and ec2 plugin 1.42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.20483.1557267780450%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Mike Sollanych commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records The Broken Build plugin also generates these typical JEP-200 errors in conjunction with the Darcs plugin, so we're seeing aspects of that issue since this plugin was seemingly never update for the marshalling whitelisting change. In particular, my Java command line option of: -Dhudson.remoting.ClassFilter=org.jenkinsci.plugins.darcs.DarcsXmlSanitizer,org.jenkinsci.plugins.darcs.DarcsChangeLogParser,sun.nio.cs.UTF_8,hudson.model.AbstractBuild,hudson.model.FreeStyleBuild,hudson.util.RobustReflectionConverter is not enough to not still get hit with May 07, 2019 3:15:45 PM hudson.model.Run execute SEVERE: Failed to save build record java.io.IOException: java.lang.RuntimeException: Failed to serialize hudson.model.AbstractBuild#scm for class hudson.model.FreeStyleBuild Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198924.1556132083000.20500.1557267960390%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56403) Renaming jenkins agents persists previously named agent on restart
Title: Message Title Anish Dangi commented on JENKINS-56403 Re: Renaming jenkins agents persists previously named agent on restart Baptiste Mathus Thanks. This seems like a safe candidate for backporting to older LTS releases. Would you consider that? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197993.1551747804000.20480.1557266520270%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55639) ec2-plugin only attempts to retrieve spot instance using old id
Title: Message Title Paul P commented on JENKINS-55639 Re: ec2-plugin only attempts to retrieve spot instance using old id I had this issue and uninstalling the plugin and re-installing it fixed it. To be specific: backup your config.xml uninstall the plugin restart jenkins re-install the plugin (I lost my configuration) stop jenkins replace the config.xml start Jenkins I am using Jenkins 2.176 and ec2 plugin 1.42 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196815.1547702452000.20461.1557264600401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57363) Global configuration setting to disable trigger of downstream pipelines
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-57363 Global configuration setting to disable trigger of downstream pipelines Issue Type: Improvement Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2019-05-07 21:26 Priority: Minor Reporter: Cyrille Le Clerc Add a global configuration setting to disable trigger of downstream pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57332) PipelineMavenPluginDao#getGeneratedArtifacts() mixes artifact version and baseVersion
Title: Message Title Cyrille Le Clerc updated JENKINS-57332 Jenkins / JENKINS-57332 PipelineMavenPluginDao#getGeneratedArtifacts() mixes artifact version and baseVersion Change By: Cyrille Le Clerc Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199106.1557094938000.20457.1557264180226%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57332) PipelineMavenPluginDao#getGeneratedArtifacts() mixes artifact version and baseVersion
Title: Message Title Cyrille Le Clerc started work on JENKINS-57332 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199106.1557094938000.20456.1557264180196%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57108) Pipeline-Maven-Plugin - UNSTABLE build with downstream list of parent job
Title: Message Title
Cyrille Le Clerc commented on JENKINS-57108
Re: Pipeline-Maven-Plugin - UNSTABLE build with downstream list of parent job
This is an unexpected behaviour: org.jenkinsci.plugins.pipeline.maven.publishers.PipelineGraphPublisher records all the dependencies and generated artifacts of a pipeline. It is executed at the end of the "withMaven(){...}" wrapping step, it should not be ignored even if the maven build is a failure as long as it gracefully finishes. Please enable logs to FINER for org.jenkinsci.plugins.pipeline.maven.publishers.PipelineGraphPublisher, rerun the downstream pipeline A and see in the console of your newbuild of A the message
[withMaven] pipelineGraphPublisher - Record dependency: " + dependency.getId() + ", ignoreUpstreamTriggers: " + ignoreUpstreamTriggers"
ref: https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.6.11/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java#L172 you should also rerun the upstream pipeline and see in the pipeline build console logs the message
[withMaven] pipelineGraphPublisher - Record generated artifact:...
Ref https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.6.11/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/PipelineGraphPublisher.java#L210
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57073) Linebreak between JobName and BuildName
Title: Message Title Gustaf Lundh commented on JENKINS-57073 Re: Linebreak between JobName and BuildName If you have the possibility, please try out this PR https://github.com/jenkinsci/yet-another-build-visualizer-plugin/pull/7 Should hopefully solve your issue. The pre-built plugin binary can be found here: https://ci.jenkins.io/job/Plugins/job/yet-another-build-visualizer-plugin/job/PR-7/1/artifact/target/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198816.1555483248000.20453.1557263340109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57108) Pipeline-Maven-Plugin - UNSTABLE build with downstream list of parent job
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-57108
Pipeline-Maven-Plugin - UNSTABLE build with downstream list of parent job
Change By:
Cyrille Le Clerc
Hi, Here is my context.I have a pipeline with main steps: * mvn clean deploy * mvn test * sonar quality gateI choose to set currentBuild.result = 'UNSTABLE' if last step (quality gate from Sonar) is not OK.I want my dependencies to build automatically downstream projects when SNAPSHOT.Everything works well when quality gate is OK (means the job is SUCCESS):If my newly SUCCESSed project A contains SNAPSHOTed dependencies B, I can see on "Downstream Jobs" of this dependency B the newly build project.So, when I build this dependency B, on finished, job from project A is launched. BUT If my job from project A is UNSTABLE, it won't be referenced as a downstream Job from dependency B (so building B will no trigger A). I have to build at least once in SUCCESS (by ex. by bypassing SONAR GATE) to see it in "Downstream Jobs" of my parent project. I'd like my parent "Downstream jobs" list updated for a project that is SUCCESS or UNSTABLE. Thanks {code:groovy}def call(body) { // evaluate the body block, and collect configuration into the object def pipelineParams = [:] body.resolveStrategy = Closure.DELEGATE_FIRST body.delegate = pipelineParams body() // Get Artifactory server instance, defined in the Artifactory Plugin administration page. def artifactory = Artifactory.server "ARTIFACTORY" def scmUrl def trimOrigin = {it.startsWith('origin/') ? it.trim() - 'origin/' : it.trim() } node('maven') {try { stage('Clone sources') {// Keep only last 3 builds + disable concurrent buildsproperties([buildDiscarder(logRotator(artifactDaysToKeepStr: '',artifactNumToKeepStr: '',daysToKeepStr: '',numToKeepStr: '3')),disableConcurrentBuilds()])testFailure = falsebuildFailure = false// MULTIBRANCH: Branch is part of the context: so use BRANCH_NAMEbranchTobuild = env.BRANCH_NAMEecho "branchTobuild=${branchTobuild}"// Scm urlscmUrl = scm.getUserRemoteConfigs()[0].getUrl()// Cleanstep([$class: 'WsCleanup', cleanWhenFailure: false])// Get code from a Gitlab repositorygit branch: trimOrigin(branchTobuild), credentialsId: 'jenkins', url: scmUrlshortCommit = sh(returnStdout: true, script: "git log -n1 --pretty=format:'%H'").trim() // Get deployPathdeployPath = pipelineParams.deployPath ?: ""echo "deployPath:${deployPath}"// Is this component deployable (if not, no need to display deploy buttons in Slack)deployable = pipelineParams.isDeployable ?: trueecho "deployable:${deployable}" } stage('Maven build') {withMaven(maven: 'Maven 3.6.0', options: [junitPublisher(disabled: true)]) { try {sh
[JIRA] (JENKINS-57108) Pipeline-Maven-Plugin - UNSTABLE build with downstream list of parent job
Title: Message Title
Cyrille Le Clerc updated an issue
Jenkins / JENKINS-57108
Pipeline-Maven-Plugin - UNSTABLE build with downstream list of parent job
Change By:
Cyrille Le Clerc
Hi, Here is my context.I have a pipeline with main steps: * mvn clean deploy * mvn test * sonar quality gateI choose to set currentBuild.result = 'UNSTABLE' if last step (quality gate from Sonar) is not OK.I want my dependencies to build automatically downstream projects when SNAPSHOT.Everything works well when quality gate is OK (means the job is SUCCESS):If my newly SUCCESSed project A contains SNAPSHOTed dependencies B, I can see on "Downstream Jobs" of this dependency B the newly build project.So, when I build this dependency B, on finished, job from project A is launched. BUT If my job from project A is UNSTABLE, it won't be referenced as a downstream Job from dependency B (so building B will no trigger A). I have to build at least once in SUCCESS (by ex. by bypassing SONAR GATE) to see it in "Downstream Jobs" of my parent project. I'd like my parent "Downstream jobs" list updated for a project that is SUCCESS or UNSTABLE. Thanks {code:groovy}def call(body) { // evaluate the body block, and collect configuration into the object def pipelineParams = [:] body.resolveStrategy = Closure.DELEGATE_FIRST body.delegate = pipelineParams body() // Get Artifactory server instance, defined in the Artifactory Plugin administration page. def artifactory = Artifactory.server "ARTIFACTORY" def scmUrl def trimOrigin = {it.startsWith('origin/') ? it.trim() - 'origin/' : it.trim() } node('maven') {try { stage('Clone sources') {// Keep only last 3 builds + disable concurrent buildsproperties([buildDiscarder(logRotator(artifactDaysToKeepStr: '',artifactNumToKeepStr: '',daysToKeepStr: '',numToKeepStr: '3')),disableConcurrentBuilds()])testFailure = falsebuildFailure = false// MULTIBRANCH: Branch is part of the context: so use BRANCH_NAMEbranchTobuild = env.BRANCH_NAMEecho "branchTobuild=${branchTobuild}"// Scm urlscmUrl = scm.getUserRemoteConfigs()[0].getUrl()// Cleanstep([$class: 'WsCleanup', cleanWhenFailure: false])// Get code from a Gitlab repositorygit branch: trimOrigin(branchTobuild), credentialsId: 'jenkins', url: scmUrlshortCommit = sh(returnStdout: true, script: "git log -n1 --pretty=format:'%H'").trim() // Get deployPathdeployPath = pipelineParams.deployPath ?: ""echo "deployPath:${deployPath}"// Is this component deployable (if not, no need to display deploy buttons in Slack)deployable = pipelineParams.isDeployable ?: trueecho "deployable:${deployable}" } stage('Maven build') {withMaven(maven: 'Maven 3.6.0', options: [junitPublisher(disabled: true)]) { try {sh
[JIRA] (JENKINS-57358) NPE in SwarmScmSource#getTags
Title: Message Title Stuart Rowe assigned an issue to Paul Allen https://github.com/jenkinsci/p4-plugin/pull/98 Jenkins / JENKINS-57358 NPE in SwarmScmSource#getTags Change By: Stuart Rowe Assignee: Stuart Rowe Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199137.1557247731000.20447.1557260940401%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57358) NPE in SwarmScmSource#getTags
Title: Message Title Stuart Rowe started work on JENKINS-57358 Change By: Stuart Rowe Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199137.1557247731000.20443.1557260940311%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57358) NPE in SwarmScmSource#getTags
Title: Message Title Stuart Rowe assigned an issue to Stuart Rowe Jenkins / JENKINS-57358 NPE in SwarmScmSource#getTags Change By: Stuart Rowe Assignee: Stuart Rowe Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199137.1557247731000.20444.1557260940356%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57358) NPE in SwarmScmSource#getTags
Title: Message Title Stuart Rowe updated JENKINS-57358 Jenkins / JENKINS-57358 NPE in SwarmScmSource#getTags Change By: Stuart Rowe Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199137.1557247731000.20445.1557260940373%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57319) HockeyApp Plugin "unexpected response code from HockeyApp: 400"
Title: Message Title Mez Pahlan updated JENKINS-57319 Jenkins / JENKINS-57319 HockeyApp Plugin "unexpected response code from HockeyApp: 400" Change By: Mez Pahlan Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199088.1556870606000.20440.1557260700436%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57319) HockeyApp Plugin "unexpected response code from HockeyApp: 400"
Title: Message Title Mez Pahlan updated JENKINS-57319 Jenkins / JENKINS-57319 HockeyApp Plugin "unexpected response code from HockeyApp: 400" Change By: Mez Pahlan Status: In Review Resolved Resolution: Fixed Released As: 1.5.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199088.1556870606000.20442.1557260700475%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57319) HockeyApp Plugin "unexpected response code from HockeyApp: 400"
Title: Message Title Mez Pahlan started work on JENKINS-57319 Change By: Mez Pahlan Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199088.1556870606000.20438.1557260700396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title
Mario Jauvin updated an issue
Jenkins / JENKINS-57324
Error running maven with settings file when running multibranch pipeline with a slash in the branch
Change By:
Mario Jauvin
I configured a maven settings and global settings file in the Pipeline Maven Configuration of the folder containing the multibranch pipeline job. When I run the following stage from my Jenkins file:{quote}stage('Package') { steps { withMaven() { Unknown macro: \{ bat "mvn clean package"} } }{quote}I get this error:{quote}[ERROR] Error executing Maven. [ERROR] The specified user settings file does not exist: C:\jenkins\dctl\branchespackageFspring-boot\workspace@tmp\withMaven22e2d518\settings.xml{quote}The reason I get this error is that the folder containing the branch is called branches%2Fspring-boot and the config file provider is replacing %2 with package (I assume this is because package is the second argument to the script that is invoked)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-55813) Improve AD/LDAP attribute analysis for locked accounts
Title: Message Title Matt Sicker commented on JENKINS-55813 Re: Improve AD/LDAP attribute analysis for locked accounts Wadeck Follonier what do you mean by cover most of the usage? The usage within Jenkins plugins that may wish to impersonate a user? Or other LDAP servers? I've been starting to investigate this and have gotten somewhat confused around the current goal. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197207.1548686882000.20432.1557257880255%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57362) Not Able to Create sql deploy project (guys this urgent, please replay in a minute, otherwise ...)
Title: Message Title kemal uzun created an issue Jenkins / JENKINS-57362 Not Able to Create sql deploy project (guys this urgent, please replay in a minute, otherwise ...) Issue Type: Bug Assignee: Unassigned Components: git-plugin Created: 2019-05-07 19:37 Labels: jenkins Priority: Blocker Reporter: kemal uzun Oops! A problem occurred while processing the request. Please check our bug trackerto see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins.The users listmight be also useful in understanding what has happened. Stack trace org.apache.commons.jelly.JellyTagException: jar:file:/C:/Program%20Files%20(x86)/Jenkins/war/WEB-INF/lib/jenkins-core-2.176.jar!/lib/hudson/actions.jelly:39:70: com/cloudbees/hudson/plugins/folder/properties/FolderCredentialsProvider at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
[JIRA] (JENKINS-57361) pipelines get lost of project when renaming projects
Title: Message Title Geert Nijs created an issue Jenkins / JENKINS-57361 pipelines get lost of project when renaming projects Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-05-07 19:31 Environment: linux centos, jenkins 2.164.2 Priority: Major Reporter: Geert Nijs to reproduce: create a project a create a pipeline x, that has an " build job: 'a' entry this works rename project a to b (via advanced settings) pipeline still work, but script still has build job 'a' entry (? somewhere the id must have been saved change pipeline build job to build job 'b' -> doesn't run anymore: error: can't find b
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title
Frederico Pratas commented on JENKINS-57314
Re: P4 Sync to label after sync to head without deleting non labeled files
Hi Karl Wirth, I've also tried this kind of construction. In my case I have created a shared library (my_groovy_lib). Inside the vars/ folder I've placed a call p4SyncLabel.groovy (see in attachmentp4SyncLabel.groovy Then inside the main pipe I call:
#!/usr/bin/env groovy
@Library('my_groovy_lib') _
// Pipeline steering
pipeline {
agent {
label 'my_slave_0'
}
options {
timestamps()
}
stages {
stage('Test') {
steps{
echo 'Test'
script{
p4SyncLabel('my_p4_ticket_id', "jenkins_${NODE_NAME}_${JOB_BASE_NAME}_${EXECUTOR_NUMBER}",
"//depot/... //jenkins_${NODE_NAME}_${JOB_BASE_NAME}_${EXECUTOR_NUMBER}/...",
'head', true, false )
}
}
}
}
}
I'm getting the following output:
Started by user Frederico Pratas
Running in Durability level: MAX_SURVIVABILITY
Loading library my_groovy_lib@master
... p4 client -o jenkins_shared_lib_master_example +
... p4 info +
... p4 info +
... p4 client -o jenkins_shared_lib_master_example +
... No change in client detected.
... p4 counter change +
... p4 changes -m1 -ssubmitted //jenkins_shared_lib_master___ +
Building on Node: master
... p4 client -o jenkins_shared_lib_master_example +
... p4 info +
... p4 info +
... p4 client -o jenkins_shared_lib_master_example +
... No change in client detected.
P4 Task: establishing connection.
... server: X:1666
... node: X
P4 Task: reverting all pending and shelved revisions.
... p4 revert /var/lib/jenkins/workspace/example%40libs/sn___ +
... rm [abandoned files]
duration: (845ms)
P4 Task: cleaning workspace to match have list.
... p4 reconcile -w -f /var/lib/jenkins/workspace/example%___ +
duration: 0m 1s
P4 Task: syncing files at change: X
... p4 sync -q /var/lib/jenkins/workspace/example%40libs/s___ +
duration: 0m 4s
P4 Task: saving built changes.
Found last change X on syncID jenkins_shared_lib_NODE_NAME_example
... p4 client -o jenkins_shared_lib_master_example +
... p4 info +
... p4 info +
... p4 client -o jenkins_shared_lib_master_example +
... No change in client detected.
... p4 changes -m20 //jenkins_shared_lib_master_example/..___ +
... p4 changes -l -m1 @X +
... p4 user -o pratas +
... p4 describe -s -m51 X +
... p4 fixes -cX +
... done
[Pipeline] Start of Pipeline
[Pipeline] node
Running on my_slave_0 in /users/jenkins/workspace/example
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Test)
[Pipeline] echo
09:45:20 Test
[Pipeline] script
[Pipeline] {
[Pipeline] p4
[Pipeline] }
[Pipeline] // script
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: P4: Task Exception: Invalid credentials
Finished: FAILURE
I'm using the same credential that is used to load the library from p4, which as you can see works fine. Any ideas what is
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Frederico Pratas updated an issue Jenkins / JENKINS-57314 P4 Sync to label after sync to head without deleting non labeled files Change By: Frederico Pratas Attachment: p4SyncLabel.groovy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.20415.1557256200163%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57360) Delivery Pipeline View with Jenkins
Title: Message Title Govind Sureka created an issue Jenkins / JENKINS-57360 Delivery Pipeline View with Jenkins Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 2019-05-07 19:13 Priority: Minor Reporter: Govind Sureka We are using plugin 'Delivery Pipeline View' on Jenkins to view the jobs in downstream section. We have enabled the option 'Show Test result' options from 'Edit View' of this plugin. We are not able to get the data for 'Skipped'. Please let us know the option to get data for 'Skipped' in pipeline view dashboard. Jenkins: 2.150.1 Delivery pipeline View: 1.3.2 Add Comment
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-55287
Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head
I encountered this:{noformat}Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[DEV/Porx-07/82:DEV/Porx-07 #82] but FlowNode was not found in storage for head id:FlowNodeId 1:121 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:664) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:901) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:912) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: FAILURE {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title
Craig Rodrigues edited a comment on JENKINS-55287
Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head
I encountered this: {noformat}Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[DEV/Porx-07/82:DEV/Porx-07 #82] but FlowNode was not found in storage for head id:FlowNodeId 1:121 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:664) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:901) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:912) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: FAILURE {noformat}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Craig Rodrigues commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head I encountered this: Creating placeholder flownodes because failed loading originals. java.io.IOException: Tried to load head FlowNodes for execution Owner[DEV/Porx-07/82:DEV/Porx-07 #82] but FlowNode was not found in storage for head id:FlowNodeId 1:121 at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.initializeStorage(CpsFlowExecution.java:679) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:716) at org.jenkinsci.plugins.workflow.job.WorkflowRun.getExecution(WorkflowRun.java:664) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:526) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:57) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:501) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:483) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:381) at hudson.model.RunMap.getById(RunMap.java:205) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.run(WorkflowRun.java:901) at org.jenkinsci.plugins.workflow.job.WorkflowRun$Owner.get(WorkflowRun.java:912) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:65) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$1.computeNext(FlowExecutionList.java:57) at com.google.common.collect.AbstractIterator.tryToComputeNext(AbstractIterator.java:143) at com.google.common.collect.AbstractIterator.hasNext(AbstractIterator.java:138) at org.jenkinsci.plugins.workflow.flow.FlowExecutionList$ItemListenerImpl.onLoaded(FlowExecutionList.java:178) at jenkins.model.Jenkins.(Jenkins.java:989) at hudson.model.Hudson.(Hudson.java:85) at hudson.model.Hudson.(Hudson.java:81) at hudson.WebAppMain$3.run(WebAppMain.java:233) Finished: FAILURE Add Comment
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Andrew Bayer assigned an issue to Unassigned Jenkins / JENKINS-55287 Pipeline: Failure to load flow node: FlowNode was not found in storage for head Change By: Andrew Bayer Assignee: vjuranek Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.20356.1557253980380%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Mike Sollanych commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records Hah. We have traced this to a nasty Unicode character in a commit from 2009 - for whatever reason the SCM plugin pulls the entire history of the repo, which actually takes quite a while to run. I think Darcs has some functions for limiting this in the time domain, so if you are working on the plugin that'd be something to consider adding in. We're going to see if we can find a way to remove the byte. Darcs itself should be escaping it, e.g. as an ` ` or similar, but I suppose it's too edgy of a case for that. We upgrade Jenkins regularly and this issue reared its head as a part of the recent trust / serializer changes, but I think may have been an issue even beforehand. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198924.1556132083000.20351.1557253020145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Mario Jauvin edited a comment on JENKINS-57324 Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch For all intents and purpose you can ignore the them . I removed them as they are not important to reproducing the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.20348.1557252960111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48087) URLTrigger Plugin causes stack trace on pipeline job
Title: Message Title Juan Carlos Perez Castellanos edited a comment on JENKINS-48087 Re: URLTrigger Plugin causes stack trace on pipeline job I have also face this issue also . Freestyle project works great but pipeline fails. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186651.1510930655000.20334.1557252240384%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57359) Info upgrade version
Title: Message Title Davide Calò created an issue Jenkins / JENKINS-57359 Info upgrade version Issue Type: Improvement Assignee: Unassigned Components: xcode-plugin Created: 2019-05-07 17:51 Priority: Minor Reporter: Davide Calò Dear, there is a way to set that for each build, tool increases the version and build number in info.plist? Thanks, Davide Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-45355) Input without permissions or not logged in, shows no message
Title: Message Title Junior Junior commented on JENKINS-45355 Re: Input without permissions or not logged in, shows no message Same issue here, it only works in blue ocean Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183506.1499422981000.20313.1557251340152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman started work on JENKINS-57111 Change By: Liam Newman Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.20297.1557250020261%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51174) no message is shown in stage view and log, when user is not authorized for input step
Title: Message Title Junior Junior commented on JENKINS-51174 Re: no message is shown in stage view and log, when user is not authorized for input step Do you have any news about that Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190482.1525685439000.20307.1557250560145%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57111) Base class setChannel does not handle exceptions from onOnline call
Title: Message Title Liam Newman assigned an issue to Liam Newman Jenkins / JENKINS-57111 Base class setChannel does not handle exceptions from onOnline call Change By: Liam Newman Assignee: Liam Newman Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198858.1555612432000.20296.1557250020248%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Mario Jauvin edited a comment on JENKINS-57324 Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch For all intents you can ignore the. I will remove removed them as they are not important to reproducing the problem. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.20293.1557249600144%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title
Mario Jauvin updated an issue
Jenkins / JENKINS-57324
Error running maven with settings file when running multibranch pipeline with a slash in the branch
Change By:
Mario Jauvin
I configured a maven settings and global settings file in the Pipeline Maven Configuration of the folder containing the multibranch pipeline job. When I run the following stage from my Jenkins file:{quote}stage('Package') { steps { withMaven() { bat "mvn ${env.MAVEN_VERBOSE} clean package ${env.RELEASE_VERSION_PARAMETERS} " }} }{quote}I get this error:{quote}[ERROR] Error executing Maven. [ERROR] The specified user settings file does not exist: C:\jenkins\dctl\branchespackageFspring-boot\workspace@tmp\withMaven22e2d518\settings.xml{quote}The reason I get this error is that the folder containing the branch is called branches%2Fspring-boot and the config file provider is replacing %2 with package (I assume this is the second argument to the script that is invoked)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit
[JIRA] (JENKINS-57358) NPE in SwarmScmSource#getTags
Title: Message Title Stuart Rowe created an issue Jenkins / JENKINS-57358 NPE in SwarmScmSource#getTags Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2019-05-07 16:48 Environment: p4-plugin 1.9.7 Priority: Major Reporter: Stuart Rowe SwarmScmSource#getPathsInBranch can return null in certain cases. In the case I debugged, I had reviewed a branch from a Swarm project which still had an open review. Add Comment
[JIRA] (JENKINS-54340) CWP throws error if pom.xml is used for plugins and casc for configuration
Title: Message Title Michael Werner commented on JENKINS-54340 Re: CWP throws error if pom.xml is used for plugins and casc for configuration It looks like it fails to parse the plugins from the pom.xml. I will create a separate bug report for that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194993.1540894383000.20273.1557247140118%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwards compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title Adrien Tateno updated an issue Jenkins / JENKINS-57357 NullPointerException due to non-backwards compatibility in hudson.plugins.EC2.SlaveTemplate. Change By: Adrien Tateno Summary: NullPointerException due to non- backwars backwards compatibility in hudson.plugins.EC2.SlaveTemplate. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199136.1557244845000.20271.1557246780115%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56918) Groovy Class Files Not Copied Over To View Code Coverage
Title: Message Title
Pavol Briatka edited a comment on JENKINS-56918
Re: Groovy Class Files Not Copied Over To View Code Coverage
Hello, I think I had a similar issue. I could not see Kotlin files in Jenkins when I checked Jacoco coverage (error message: _"Error while reading the sourcefile!"_) but I managed to solve it by putting the following line to my Jenkinsfile jacoco step configuration:{code:java} sourceInclusionPattern: '**/*.*' \ {code} Now both Java and Kotlin files are showed in reports. I checked the source code for JacocoPublisher where I found that the default value for String sourceInclusionPattern is indeed \{code: set to copy only java }"**/*.java"\{code} files but you can rewrite it either in post-build actions tab in Jenkins or in your Jenkinsfile (depending on your implementation). The above mentioned implementation will include all files from your source code (defined as sourcePattern)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198593.1554476525000.20269.1557246120233%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56918) Groovy Class Files Not Copied Over To View Code Coverage
Title: Message Title
Pavol Briatka edited a comment on JENKINS-56918
Re: Groovy Class Files Not Copied Over To View Code Coverage
Hello, I think I had a similar issue. I could not see Kotlin files in Jenkins when I checked Jacoco coverage (error message: _"Error while reading the sourcefile!"_) but I managed to solve it by putting the following line to my Jenkinsfile jacoco step configuration: {code:java} sourceInclusionPattern: '**/*.*' \{code} Now both Java and Kotlin files are showed in reports. I checked the source code for JacocoPublisher where I found that the default value for String sourceInclusionPattern is indeed \{code:java} "**/*.java" \{code} but you can rewrite it either in post-build actions tab in Jenkins or in your Jenkinsfile (depending on your implementation).The above mentioned implementation will include all files from your source code (defined as sourcePattern)
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198593.1554476525000.20266.1557246000295%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title Adrien Tateno updated an issue Jenkins / JENKINS-57357 NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate. Change By: Adrien Tateno Attachment: image-2019-05-07-10-52-22-920.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199136.1557244845000.20263.1557245460108%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title
Adrien Tateno updated an issue
Jenkins / JENKINS-57357
NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Change By:
Adrien Tateno
Upon upgrading the ec2-plugin to master and restarting Jenkins, the EC2 nodes begin to fail connecting with the following exception {{ ! image- Screen Shot 2019-05-07 -10-52-22-920 at 9 . 23.19 AM. png |thumbnail ! }} This is likely due to the recent change that allows configuring the strategy for determining the hostname/IP address of the node [https://github.com/jenkinsci/ec2-plugin/pull/329].[https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility] suggests that it is necessary to define a {{readResolve()}} method when deprecating fields (in this case the boolean fields {{usePrivateDnsName connectUsingPublicIp}}) because when objects are loaded from XML their constructors are not invoked.What likely happened here, is that the newly defined {{connectionStrategy}} was null when loaded from XML, causing the hostname/IP address determination to fail at instance startup time. [~jvz][~dgarzon]
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-57357) NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title Adrien Tateno updated an issue Jenkins / JENKINS-57357 NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate. Change By: Adrien Tateno Attachment: Screen Shot 2019-05-07 at 9.23.19 AM.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199136.1557244845000.20259.1557245400824%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57161) ec2 plugin locks queue until excessWorkload is 0
Title: Message Title Adrien Tateno commented on JENKINS-57161 Re: ec2 plugin locks queue until excessWorkload is 0 Proposed fix: https://github.com/jenkinsci/ec2-plugin/pull/346 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198911.1556047726000.20257.1557245160174%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57357) NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate.
Title: Message Title Adrien Tateno created an issue Jenkins / JENKINS-57357 NullPointerException due to non-backwars compatibility in hudson.plugins.EC2.SlaveTemplate. Issue Type: Bug Assignee: FABRIZIO MANFREDI Attachments: image-2019-05-07-10-52-22-920.png Components: ec2-plugin Created: 2019-05-07 16:00 Environment: Jenkins 2.172, ec2-plugin master (likely as of 2f348aa519338aac64dd19954b0b41a62a8ea6fc) Priority: Major Reporter: Adrien Tateno Upon upgrading the ec2-plugin to master and restarting Jenkins, the EC2 nodes begin to fail connecting with the following exception This is likely due to the recent change that allows configuring the strategy for determining the hostname/IP address of the node https://github.com/jenkinsci/ec2-plugin/pull/329. https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility suggests that it is necessary to define a readResolve() method when deprecating fields (in this case the boolean fields usePrivateDnsName connectUsingPublicIp) because when objects are loaded from XML their constructors are not invoked. What likely happened here, is that the newly defined connectionStrategy was null when loaded from XML, causing the hostname/IP address determination to fail at instance startup time. Matt Sicker Daniel Garzon
[JIRA] (JENKINS-57347) Performance degradation running pipeline step sh on remote agents
Title: Message Title Nancy Robertson commented on JENKINS-57347 Re: Performance degradation running pipeline step sh on remote agents Ivan Fernandez Calvo I tried setting the property, then disconnected and reconnected my agent. It makes no measurable difference. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199122.1557175676000.20250.1557244860264%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50462) Artifacts tab presents everything as a flat list, making navigation time consuming
Title: Message Title Simon L-G commented on JENKINS-50462 Re: Artifacts tab presents everything as a flat list, making navigation time consuming Having the same issue. Is there any known workarounds other than switching to the old UI? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189521.1522249108000.20242.1557244560652%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56918) Groovy Class Files Not Copied Over To View Code Coverage
Title: Message Title Pavol Briatka commented on JENKINS-56918 Re: Groovy Class Files Not Copied Over To View Code Coverage Hello, I think I had a similar issue. I could not see Kotlin files in Jenkins when I checked Jacoco coverage (error message: "Error while reading the sourcefile!") but I managed to solve it by putting the following line to my Jenkinsfile jacoco step configuration: sourceInclusionPattern: '*/.*' Now both Java and Kotlin files are showed in reports. I checked the source code for JacocoPublisher where I found that the default value for String sourceInclusionPattern is indeed "*/.java" but you can rewrite it either in post-build actions tab in Jenkins or in your Jenkinsfile (depending on your implementation). The above mentioned implementation will include all files from your source code (defined as sourcePattern) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198593.1554476525000.20240.1557244080214%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Josh Soref commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Liam Newman: I don't think it helped Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.20170.1557243601537%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57356) Spaces in workspace path
Title: Message Title Steve Springett created an issue Jenkins / JENKINS-57356 Spaces in workspace path Issue Type: Bug Assignee: Assaf hefetz Components: snyk-security-plugin Created: 2019-05-07 15:36 Priority: Major Reporter: Steve Springett If a Jenkins workspace contains a space, execution of the Snyk plugin will fail with the following: Installing Snyk Security tool (version 'latest') Testing for known issues... > /var/lib/jenkins/tools/io.snyk.jenkins.tools.SnykInstallation/Latest_Version/node_modules/.bin/snyk test --json --severity-threshold=high --project-name=myapp-android Error result: = DEBUG INFORMATION START = [COULD NOT RUN gradle -v] >>> command: /var/lib/jenkins/workspace/myapp - android/gradlew snykResolvedDepsJson -q --build-file build.gradle --no-daemon -Dorg.gradle.parallel= -I /tmp/tmp-11153lDMTd6CV2URC-init.gradle >>> exit code: 127 >>> stdout: >>> stderr: /bin/sh: 1: /var/lib/jenkins/workspace/myapp: not found = DEBUG INFORMATION END = Add Comment
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Oleg Nenashev commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors Fine with me. OTOH I do not see any patch which would fix the problem in the recent releases Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.20162.1557243240126%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57355) Question - Unable to find an option to publish the video file
Title: Message Title Rakesh Nambiar created an issue Jenkins / JENKINS-57355 Question - Unable to find an option to publish the video file Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner-test-framework Created: 2019-05-07 15:28 Priority: Trivial Reporter: Rakesh Nambiar After the Test execution, I have the video file in the target folder. But I am not finding any suitable plug-in or option to publish it. I tried the archive option, but it wasn't useful. Please consider this as a question and advise. Add Comment
[JIRA] (JENKINS-46385) Error while clicks on 'Open' links from Slack
Title: Message Title Rakesh Nambiar commented on JENKINS-46385 Re: Error while clicks on 'Open' links from Slack Kurt Madel any thought on this, please? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184649.1503488206000.20160.1557243060323%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45018) Slave getting disconnected frequently
Title: Message Title Rakesh Nambiar commented on JENKINS-45018 Re: Slave getting disconnected frequently Any update on this, please? Oleg Nenashev did you find any solution? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183106.149803334.20158.1557243060300%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44313) Conditional Plugin - Build status NOT changing if my conditional flow PASS
Title: Message Title Rakesh Nambiar closed an issue as Fixed Closing the issue as this cannot be fixed Jenkins / JENKINS-44313 Conditional Plugin - Build status NOT changing if my conditional flow PASS Change By: Rakesh Nambiar Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.182118.149502116.20149.1557243000336%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-21336) ADMINISTER should not imply RUN_SCRIPTS
Title: Message Title Matt Sicker assigned an issue to Unassigned Jenkins / JENKINS-21336 ADMINISTER should not imply RUN_SCRIPTS Change By: Matt Sicker Assignee: Matt Sicker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152900.1389394038000.20125.1557241680930%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34313) SAXParseException from parallel SCM checkout
Title: Message Title Wolfgang Issovits commented on JENKINS-34313 Re: SAXParseException from parallel SCM checkout Is there a chance to get a new release of the plugin with this fix included? That would be great as this issue is really problematic for larger parallel pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.169867.1460993343000.20128.1557241680988%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50433) unable to load shared library from gerrit pull request branch
Title: Message Title Sorin Sbarnea updated JENKINS-50433 Closing as I am no longer using jenkins so I cannot reproduce it (or the fix) Jenkins / JENKINS-50433 unable to load shared library from gerrit pull request branch Change By: Sorin Sbarnea Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189489.1522158981000.20117.1557241440907%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56996) null permission lookup when pull-request's origin repo/branch is deleted on github
Title: Message Title Liam Newman commented on JENKINS-56996 Re: null permission lookup when pull-request's origin repo/branch is deleted on github Christian Höltje Please try this version: https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.2-rc835.5125eb8241d3/ It should make you scan not fail due to issues with one PR. NOTE: PRs that experience errors will be marked "orphaned" (and possibly deleted depending on your orphan strategy). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198693.1555102536000.20102.1557239760131%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46305) Jenkins Slave FATAL: command execution failed
Title: Message Title Ricky Tan updated an issue Jenkins / JENKINS-46305 Jenkins Slave FATAL: command execution failed Change By: Ricky Tan Comment: this was already fixed. just need to increase the ELB idle timeout value Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184561.1503206898000.20100.1557239400224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46305) Jenkins Slave FATAL: command execution failed
Title: Message Title Ricky Tan resolved as Fixed this was already fixed. just need to increase the ELB idle timeout value Jenkins / JENKINS-46305 Jenkins Slave FATAL: command execution failed Change By: Ricky Tan Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184561.1503206898000.20097.1557239340507%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46305) Jenkins Slave FATAL: command execution failed
Title: Message Title Ricky Tan commented on JENKINS-46305 Re: Jenkins Slave FATAL: command execution failed this was already fixed. just need to increase the ELB idle timeout value Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184561.1503206898000.20094.1557239340457%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Arman Tursynbekov Could you open a new issue for that, it is probably not related to this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.20028.1557238921175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub Josh Soref, Ebrahim Moshaya, Amir Barkal, David Sanftenberg, Aleksey Smyrnov Here's the updated plugin with okio (thanks Josh!). https://repo.jenkins-ci.org/incrementals/org/jenkins-ci/plugins/github-branch-source/2.5.2-rc836.bde357341ecd/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.19962.1557238861709%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Liam Newman edited a comment on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub [~synalogik], [~amirbarkal], [~dbsanfte], [~soar]If anyone is interested in trying it, I have an experimental version of the github-branch-source-plugin using okttp3. https://drive.google.com/file/d/1VreeBlIG0RCbSI80wW2BBOmcVT9ZySNW/view?usp=sharing -Removed- If you have a test/staging Jenkins on which your are comfortable trying this out it would be helpful to know if this issue would be fixed by this upgrade. The code can be seen at https://github.com/jenkinsci/github-branch-source-plugin/pull/223 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194753.1539776248000.19896.1557238801477%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Wolf Molnar commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure The slave has a custom path of toolkit and Avoid using build toolkit on Master (experimental) is checked but It still use master path. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168320.1455716302000.19891.1557238680152%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57304) Multiple "idle" entries on Build Executor Status for non-existant executors
Title: Message Title Patrick Rose commented on JENKINS-57304 Re: Multiple "idle" entries on Build Executor Status for non-existant executors It looks like they've gone now (and we're updated to 1.746). I don't know whether it was fixed by the upgrade or the fact that the system would have been rebooted. May as well close this unless you can think of a reason to keep it open? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199072.1556795988000.19885.1557238080109%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57327) changeView option ignored, not added to client spec
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-57327 changeView option ignored, not added to client spec Change By: Karl Wirth Labels: P4_SUPPORT plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199099.1557004231000.19866.1557237600361%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57354) Remove obsolete Alerts from SonarQube portlet
Title: Message Title Georg Henzler updated JENKINS-57354 Jenkins / JENKINS-57354 Remove obsolete Alerts from SonarQube portlet Change By: Georg Henzler Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199133.1557236182000.19883.1557237900402%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57309) Ensure Generic JS portlet does not XSS-encode JS
Title: Message Title Georg Henzler updated JENKINS-57309 Jenkins / JENKINS-57309 Ensure Generic JS portlet does not XSS-encode JS Change By: Georg Henzler Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199078.1556809991000.19882.1557237900391%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Wolf Molnar commented on JENKINS-32996 Re: Jenkins use different RTC Build Toolkit path as the one set in system configure Jenkins ver. 2.150.3 Team Concert Plugin 1.2.0.5 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168320.1455716302000.19881.1557237900365%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31437) attach properties to resources, inject properties at build time
Title: Message Title Emmanuel Ruhnau commented on JENKINS-31437 Re: attach properties to resources, inject properties at build time I need that too. Any update ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.166301.144683029.19853.1557237480471%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57308) Update for Sonar 6 LTS (icons, links)
Title: Message Title Georg Henzler updated JENKINS-57308 Jenkins / JENKINS-57308 Update for Sonar 6 LTS (icons, links) Change By: Georg Henzler Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199077.1556809915000.19876.1557237900274%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57343) RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir
Title: Message Title Zichuan Zou updated an issue Jenkins / JENKINS-57343 RTC: Jenkins checks out subdirs of a component instead of checking it out as one whole dir Change By: Zichuan Zou Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199118.1557152823000.19874.1557237840279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57327) changeView option ignored, not added to client spec
Title: Message Title
Karl Wirth commented on JENKINS-57327
Re: changeView option ignored, not added to client spec
Hi Aaron Miller, Strangely mine works.
checkout perforce(credential: 'JenkinsMaster',
populate: forceClean(have: false,
parallel:
[
enable: false,
minbytes: '1024',
minfiles: '1',
threads: '4'
],
pin: '',
quiet: false),
workspace: manualSpec(charset: 'none',
cleanup: false,
name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-changeview',
pinHost: false,
spec: clientSpec(allwrite: false,
backup: true,
changeView: '//depot/Project1/...@307',
clobber: true,
compress: false,
line: 'LOCAL',
locked: false,
modtime: false,
rmdir: false,
serverID: '',
streamName: '',
type: 'WRITABLE',
view: '//depot/Project1/... //jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}-changeview/...')))
You can see that '307' is the CL I have set for my 'changeview'. In the job output I see it correctly syncing 307:
P4 Task: syncing files at change: 307
... p4 sync /var/lib/jenkins/ANOTHER_SLAVE/workspace/PipelineEditor/...@307
Note - The latest CL is '363' on this path:
$ p4 changes -m1 //depot/Project1/...
Change 363 on 2019/04/08 by super@test_ws 'Submit of ./f363'
Can you please try a simple test where your checkout step is the only one in the code from a fresh job. Do you still see the same bug?
Add Comment
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Jose Valverde commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi Karl Wirth, My mistake, indeed I have my jenkins credentials on the fcredentials options not my workspace name. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.19851.1557237240134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-32996) Jenkins use different RTC Build Toolkit path as the one set in system configure
Title: Message Title Wolf Molnar reopened an issue I have this problem too. The Master is running on Linux and the slave is running on Windows. I use the RTC-BuildSystem-Toolkit-Win64-6.0.6 and the toolkit is not installed on the Master, just on the slave When I use Windows Master alone and install toolkit then it work fine, Jenkins / JENKINS-32996 Jenkins use different RTC Build Toolkit path as the one set in system configure Change By: Wolf Molnar Resolution: Cannot Reproduce Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.168320.1455716302000.19869.1557237660766%40Atlassian.JIRA.
[JIRA] (JENKINS-37508) Can't see where "Exported variables" get defined
Title: Message Title
Daniel Hoerner edited a comment on JENKINS-37508
Re: Can't see where "Exported variables" get defined
Same problem here.I have NOT installed the Tool Envoronment plugin.Added following to the Custom Tool Definition:Exported Paths: "C:\Program Files\nodejs" I using the custom tool installer durring the runtime at the Build VM (See Preparing Build machine stage) But I can not see this path when running the "set" command of Windows durring build: {code:java}// node('VS2017') {stage('Preparing Build machine...'){ tool name: 'npm 6.4.1', type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool' }echo "Current Environment:"bat 'set'}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173616.1471513906000.19846.1557236340143%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title Karl Wirth commented on JENKINS-57314 Re: P4 Sync to label after sync to head without deleting non labeled files Hi Jose Valverde, Sorry 'credential' is a typo. That should be your Jenkins credential not the workspace name. For example: def p4 = p4 (credential: 'myJenkinsCrentialName',workspace: ... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199083.1556813511000.19849.1557236640122%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37508) Can't see where "Exported variables" get defined
Title: Message Title Daniel Hoerner updated an issue Jenkins / JENKINS-37508 Can't see where "Exported variables" get defined Change By: Daniel Hoerner Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173616.1471513906000.19842.1557236220517%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57181) Jenkins ALM disconnection
Title: Message Title Govind Sureka edited a comment on JENKINS-57181 Re: Jenkins ALM disconnection I have not received the mail. Please resend it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198932.1556196435000.19834.1557236160649%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57354) Remove obsolete Alerts from SonarQube portlet
Title: Message Title Georg Henzler created an issue Jenkins / JENKINS-57354 Remove obsolete Alerts from SonarQube portlet Issue Type: Improvement Assignee: Georg Henzler Components: mashup-portlets-plugin Created: 2019-05-07 13:36 Priority: Minor Reporter: Georg Henzler Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199133.1557236182000.19839.1557236220340%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-37508) Can't see where "Exported variables" get defined
Title: Message Title
Daniel Hoerner reopened an issue
Same problem here. I have NOT installed the Tool Envoronment plugin. Added following to the Custom Tool Definition: Exported Paths: "C:\Program Files\nodejs" But I can not see this path when running the "set" command of Windows durring build:
// node('VS2017') {
stage('Preparing Build machine...')
{
tool name: 'npm 6.4.1', type: 'com.cloudbees.jenkins.plugins.customtools.CustomTool'
}
echo "Current Environment:"
bat 'set'
}
Jenkins / JENKINS-37508
Can't see where "Exported variables" get defined
Change By:
Daniel Hoerner
Resolution:
Not A Defect
Status:
Resolved Reopened
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57314) P4 Sync to label after sync to head without deleting non labeled files
Title: Message Title
Jose Valverde commented on JENKINS-57314
Re: P4 Sync to label after sync to head without deleting non labeled files
Hi Karl Wirth, I'm trying to change my job to run a P4Groovy, and I've created an example as in the link you've shared, and i'm getting the following error:
[Pipeline] End of Pipeline
ERROR: P4: Task Exception: Invalid credentials
This is my test code:
node("my_node") {
// Define workspace
def ws = [$class: 'StreamWorkspaceImpl',
charset: 'none', format: 'jenkins-${JOB_NAME}',
pinHost: false, streamName: '//my_workspace']// Create object
def p4 = p4 (credential: 'my_client', workspace: manualSpec(charset: 'none', cleanup: false, name: 'jenkins-${NODE_NAME}-${JOB_NAME}-${EXECUTOR_NUMBER}', pinHost: false, spec: clientSpec(allwrite: false, backup: true, changeView: '', clobber: true, compress: false, line: 'LOCAL', locked: false, modtime: false, rmdir: false, serverID: '', streamName: '', type: 'WRITABLE', view: 'my_workspace')))
p4.run('sync','...')
}
Please note that "my_client" is the same using in other working jobs. Is there any additional configuration needed on my job, rather then what is on the shared link (de-select groovy sandbox) ? Thanks for the help!
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite edited a comment on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error [~sebawo] when I've resolved the blocking bugs that are identified in the [git client plugin 3.0 milestone| https://github.com/jenkinsci/ git - client - plugin 3.0 / milestone /1 ] and in the [git plugin 4.0 milestone|https://github.com/jenkinsci/git-plugin/milestone/3]. You're welcome to help test the beta versions and report your results of testing the beta versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186841.1511861183000.19804.1557235441260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Sebastian Wojas when I've resolved the blocking bugs that are identified in the [git client plugin 3.0 milestone|git client plugin 3.0 milestone] and in the git plugin 4.0 milestone. You're welcome to help test the beta versions and report your results of testing the beta versions. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186841.1511861183000.19802.1557235441237%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57173) Issue with Darcs SCM plugin saving build records
Title: Message Title Sven Strittmatter commented on JENKINS-57173 Re: Issue with Darcs SCM plugin saving build records Did this issue start occuring after upgrading your Jenkins? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198924.1556132083000.19779.1557234900154%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57353) Cleanup FindBugs issues in Jenkinsfile Runner
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57353 Cleanup FindBugs issues in Jenkinsfile Runner Issue Type: Bug Assignee: Unassigned Components: jenkinsfile-runner Created: 2019-05-07 12:40 Labels: findbugs Priority: Minor Reporter: Oleg Nenashev After the update to the recent Parent POM in TODO, there are some failing FindBugs checks in Jenkinsfile Runner modules. It would be great to clean them up. Acceptance criteria: All FindBugs warnings are fixed or suppressed with a justification FindBugs failOnError is reenabled in the pom.xml Add Comment
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Sebastian Wojas edited a comment on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error [~markewaite] when you're planning to release fixed version (3.0, not beta) of git-plugin ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186841.1511861183000.19752.1557232740505%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Sebastian Wojas commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Mark Waite when you're planning to release fixed version of git-plugin ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.186841.1511861183000.19729.1557232620396%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
