[JIRA] (JENKINS-50443) Issues with JIRA Trigger Pluggin
Title: Message Title Rathishan P created an issue Jenkins / JENKINS-50443 Issues with JIRA Trigger Pluggin Issue Type: Bug Assignee: Wisen Tanasa Attachments: jenkinjobcinfig.JPG, jenkinlog.JPG, webhook.JPG Components: jira-trigger-plugin Created: 2018-03-28 05:49 Environment: Redhat Jenkisn Verison 2.109 Jira version : 7.5.0 Priority: Critical Reporter: Rathishan P I Configured a Jenkins WebHook Listener in JIRA. After this I configured JIRA Trigger plugin settings in Jenkins. But while updating an Issue in JIRA, I am getting below error in Jenkins. Please help me to reslove this issue. "Received Webhook callback with an invalid event type or a body without comment/changelog. Event type: comment_created. Event body contains: [timestamp, webhookEvent, comment]. Mar 27, 2018 10:06:47 PM FINE com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook Received Webhook callback from comment. Event type: jira:issue_updated Mar 27, 2018 10:07:37 PM WARNING java_util_logging_Logger$warning$1 call Received Webhook callback with an invalid event type or a body without comment/changelog. Event type: comment_created. Event body contains: [timestamp, webhookEvent, comment]. Mar 27, 2018 10:07:38 PM FINE com.ceilfors.jenkins.plugins.jiratrigger.webhook.JiraWebhook Received Webhook callback from comment. Event type: jira:issue_updated
[JIRA] (JENKINS-41805) Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace.
Title: Message Title Edgars Batna edited a comment on JENKINS-41805 Re: Pipeline Job-- deletedir() delete only current directory but @script and @tmp dir still there in workspace. Not even sure why these directories would even be required. There are system-wide temporary directories that should be used for this. The temporary directories, no matter what implementation detail, should not concern us users. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43016) BlueOcean editor: does not allow empty string for label on agent or node
Title: Message Title Nicolae Pascu commented on JENKINS-43016 Re: BlueOcean editor: does not allow empty string for label on agent or node Andrew Bayer I am receiving the Label param from node as being required from jenkins/blue/rest/pipeline-metadata/agentMetadata?depth=20 After talking to Vivek Pandey he said I should ping you about it. This is the full JSON response: https://gist.github.com/NicuPascu/9ed1d96d4604274683ad2ef48a0778fc Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49455) Scroll up during input step causes Proceed not to respond in Blue Ocean
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-49455 Scroll up during input step causes Proceed not to respond in Blue Ocean Change By: Michael Neale Sprint: Blue Ocean 1.5 - beta 3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50309) Sometimes Docker slaves hang in 'Waiting for next available executor' state
Title: Message Title Aleksandr Gamoskin commented on JENKINS-50309 Re: Sometimes Docker slaves hang in 'Waiting for next available executor' state Andrew, this bug could be reproduce with this issue(https://issues.jenkins-ci.org/browse/JENKINS-50317) attachments. But it's raised 2-3 times. It's rare. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50317) Pipeline job is failed with java.lang.StackOverflowError
Title: Message Title Aleksandr Gamoskin commented on JENKINS-50317 Re: Pipeline job is failed with java.lang.StackOverflowError Hello Andrew, yes, I'am sending you utils.groovy. Also I could send you workspace subdirectory but we use conan io server, cmake etc. I look forward for your response. autoloader.zip utils.groovy ^^ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50317) Pipeline job is failed with java.lang.StackOverflowError
Title: Message Title Aleksandr Gamoskin updated an issue Jenkins / JENKINS-50317 Pipeline job is failed with java.lang.StackOverflowError Change By: Aleksandr Gamoskin Attachment: autoloader.zip Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50317) Pipeline job is failed with java.lang.StackOverflowError
Title: Message Title Aleksandr Gamoskin updated an issue Jenkins / JENKINS-50317 Pipeline job is failed with java.lang.StackOverflowError Change By: Aleksandr Gamoskin Attachment: utils.groovy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50442) Adding removeBadge(icon) and removeAllBadges() methods to remove existing badges
Title: Message Title
Jean-Paul G updated an issue
Jenkins / JENKINS-50442
Adding removeBadge(icon) and removeAllBadges() methods to remove existing badges
Change By:
Jean-Paul G
The new DSL addBadge() allow to create a new badge directly from the pipeline.How to remove it later on ? In our workflow, there are several pauses waiting for user input, and at each stage we are displaying a different icons (removing previous one and adding a different one).Here a workaround:{code:java}def removeBadges(RunWrapper build, String icon = null) { List actions = build.getRawBuild().getActions() List badgeActions = build.getRawBuild().getActions(BuildBadgeAction.class) for(BuildBadgeAction action : badgeActions) { if (icon == null || action.iconPath == icon) { actions.remove(action) } }} Would need a {code} Would need a *removeBadge(icon)* {code:java} and {code} *removeAllBadges()* {code:java} methods to do it directly in the pipeline. {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50442) Adding removeBadge(icon) and removeAllBadges() methods to remove existing badges
Title: Message Title
Jean-Paul G updated an issue
Jenkins / JENKINS-50442
Adding removeBadge(icon) and removeAllBadges() methods to remove existing badges
Change By:
Jean-Paul G
The new DSL addBadge() allow to create a new badge directly from the pipeline.How to remove it later on ? In our workflow, there are several pauses waiting for user input, and at each stage we are displaying a different icons (removing previous one and adding a different one). I'm was so far doing something like Here a workaround :{code:java}def removeBadges(RunWrapper build , String icon = null ) { List actions = build.getRawBuild().getActions() List< GroovyPostbuildAction BuildBadgeAction > badgeActions = build.getRawBuild().getActions( GroovyPostbuildAction BuildBadgeAction .class) for( GroovyPostbuildAction BuildBadgeAction action : badgeActions) { if (icon == null || action.iconPath == icon) { actions.remove(action) }} {code }Would need a {code} *removeBadge(icon)* {code:java} and {code} *removeAllBadges()* {code:java} methods to do it directly in the pipeline. {code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50442) Adding removeBadge(icon) and removeAllBadges() methods to remove existing badges
Title: Message Title
Jean-Paul G created an issue
Jenkins / JENKINS-50442
Adding removeBadge(icon) and removeAllBadges() methods to remove existing badges
Issue Type:
New Feature
Assignee:
Marc Brugger
Components:
badge-plugin
Created:
2018-03-28 01:31
Environment:
jenkins 2.113 badge-plugin 1.2
Labels:
pipeline badge
Priority:
Minor
Reporter:
Jean-Paul G
The new DSL addBadge() allow to create a new badge directly from the pipeline. How to remove it later on ? In our workflow, there are several pauses waiting for user input, and at each stage we are displaying a different icons (removing previous one and adding a different one). I'm was so far doing something like:
def removeBadges(RunWrapper build) {
List actions = build.getRawBuild().getActions()
List badgeActions = build.getRawBuild().getActions(GroovyPostbuildAction.class)
for(GroovyPostbuildAction action : badgeActions) {
actions.remove(action)
}
}
Would need a removeBadge(icon) and removeAllBadges() methods to do it directly in the pipeline.
[JIRA] (JENKINS-50250) 1.13 to 1.3.1 kubernets plugin no longer able to override jnlp container
Title: Message Title Steve Berube commented on JENKINS-50250 Re: 1.13 to 1.3.1 kubernets plugin no longer able to override jnlp container I closed my own ticket because of confirmed it’s working in 1.3.1. I’ll double check it works in1.4.0 and report back Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Michael Neale commented on JENKINS-50406 Re: "Triggered Build" links broken with cloudbees-folder nice one Josh McDonald Joshua Hoblitt if it's not delivered in 30 minutes then it's free. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48437) Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-48437 Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48437) Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-48437 Change By: Allan BURDAJEWICZ Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48437) Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId
Title: Message Title Allan BURDAJEWICZ commented on JENKINS-48437 Re: Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId Proposed a PR https://github.com/jenkinsci/docker-commons-plugin/pull/68 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50250) 1.13 to 1.3.1 kubernets plugin no longer able to override jnlp container
Title: Message Title Peter Novotnak commented on JENKINS-50250 Re: 1.13 to 1.3.1 kubernets plugin no longer able to override jnlp container Why is this closed? The field doesn't even exist anymore with 1.4 which makes the plugin pretty useless... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Build userId missing for a job being built by other Jobs
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-50194 Build userId missing for a job being built by other Jobs Change By: Naresh Rayapati Attachment: TEST1JIRA.png Attachment: addCommentJob.png Attachment: buildJob.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Build userId missing for a job being built by other Jobs
Title: Message Title
Naresh Rayapati commented on JENKINS-50194
Re: Build userId missing for a job being built by other Jobs
build job:
build 'jiraComment'
jiraAddComment job:
node {
jiraAddComment comment: "testing", site: 'JIRA', idOrKey: 'TEST-1'
}
Attached screenshots for buildJob, jiraAttachment job and actual JIRA screenshot.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50006) Kubernetes agent max number of instances no longer working
Title: Message Title Peter Novotnak edited a comment on JENKINS-50006 Re: Kubernetes agent max number of instances no longer working I can dupe with 1.4. With a limit of 20 set it seems like it always stops at 281? Could just be coincidence. provisions 1:1 for number of jobs queued Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50006) Kubernetes agent max number of instances no longer working
Title: Message Title Peter Novotnak edited a comment on JENKINS-50006 Re: Kubernetes agent max number of instances no longer working I can dupe with 1.4 . With a limit of 20 set it seems like it always stops at 281? Could just be coincidence. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50006) Kubernetes agent max number of instances no longer working
Title: Message Title Peter Novotnak edited a comment on JENKINS-50006 Re: Kubernetes agent max number of instances no longer working I can dupe with 1.4 . Plugin center shows no available updates. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50006) Kubernetes agent max number of instances no longer working
Title: Message Title Peter Novotnak commented on JENKINS-50006 Re: Kubernetes agent max number of instances no longer working I can dupe with 1.4. Plugin center shows no available updates. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43947) VersionControlException: renaming: target file already exists
Title: Message Title james stevenson commented on JENKINS-43947 Re: VersionControlException: renaming: target file already exists You get this issue if a file path is too long, a lot of times its the workspace path being long, so name the folders/jobs on Jenkins really short names cause the workspace it all gets brought down to has a folder for each "Jenkins folder" then a folder for the "Jenkins job name". Hope that helps. Ill "Watch" the comment. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title Steffen Kötte closed an issue as Fixed Jenkins / JENKINS-49495 False positive for LLVM/Clang Change By: Steffen Kötte Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49495) False positive for LLVM/Clang
Title: Message Title Steffen Kötte commented on JENKINS-49495 Re: False positive for LLVM/Clang We updated the plugin and it is working correctly now - sorry for the false alarm, I thought our plugin version would be up-to-date Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50399) Skipped steps show as passed - plugins uptodate but still nothing
Title: Message Title Keith Zantow resolved as Duplicate Paul Dragoonis I think this is a dupe of JENKINS-48884, closing this because the other has more info to reproduce, feel free to watch that one, it's actively being worked on Jenkins / JENKINS-50399 Skipped steps show as passed - plugins uptodate but still nothing Change By: Keith Zantow Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-50393) P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Title: Message Title
Michael Rose commented on JENKINS-50393
Re: P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
In my case, I switched from ${JOB_NAME} to ${JOB_BASE_NAME} as a short-term fix.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37008) Jenkins vSphere cloud plugin does not expose guest info to pipeline
Title: Message Title Sebastien Hensgen commented on JENKINS-37008 Re: Jenkins vSphere cloud plugin does not expose guest info to pipeline I confirm the issue. Meanwhile is it possible to parse the text output and extract the value from it? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50393) P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Title: Message Title Michael Rose edited a comment on JENKINS-50393 Re: P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable I just ran into this problem as well. Should have looked before creating an a similar issue that occurs with pipeline jobs . Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50393) P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable
Title: Message Title Michael Rose commented on JENKINS-50393 Re: P4 Plugin update 1.8.7 breaks against workspaces using the $JOB_NAME variable I just ran into this problem as well. Should have looked before creating an issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50406) "Triggered Build" links broken with cloudbees-folder
Title: Message Title Josh McDonald updated JENKINS-50406 Fixed in master @ d508e975be5c28ebfe26bd5dc0e054771b4829df Jenkins / JENKINS-50406 "Triggered Build" links broken with cloudbees-folder Change By: Josh McDonald Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin
Title: Message Title
Michael Rose updated an issue
Jenkins / JENKINS-50441
p4sync with default client name fails with latest version of p4 plugin
Change By:
Michael Rose
This used to work:{quote}p4sync credential: 'p4integ.prod', populate: previewOnly(quiet: true, pin: env.latest_version), source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote} {{ ... p4 client -o jenkins-master- {color:#14892c} scm- promote{color}_ansible_playbooks promote_ansible_playbooks -0 + }} {{ ... p4 client -i + }} {{ P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. }} {{ Mapping '//jenkins-master- {color:#d04437} scm/ promote{color}_ansible_playbooks promote_ansible_playbooks -0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'. }} {quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin
Title: Message Title
Michael Rose updated an issue
Jenkins / JENKINS-50441
p4sync with default client name fails with latest version of p4 plugin
Change By:
Michael Rose
This used to work:{quote}p4sync credential: 'p4integ.prod', populate: previewOnly(quiet: true, pin: env.latest_version), source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote}{{... p4 client -o jenkins-master - {color:#14892c}scm-promote{color}_ansible_playbooks-0 +}}{{ ... p4 client -i +}}{{ P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.}}{{ Mapping '//jenkins-master-{color:# ff d04437 }scm/promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.}}{quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you
[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin
Title: Message Title
Michael Rose updated an issue
Jenkins / JENKINS-50441
p4sync with default client name fails with latest version of p4 plugin
Change By:
Michael Rose
This used to work:{quote}p4sync credential: 'p4integ.prod', populate: previewOnly(quiet: true, pin: env.latest_version), source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote} {{ ... p4 client -o jenkins-master - {color:#14892c}scm-promote{color}_ansible_playbooks-0 + }} {{ ... p4 client -i + }} {{ P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. }} {{ Mapping '//jenkins-master-{color:#ff}scm/promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'. }} {quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message
[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin
Title: Message Title
Michael Rose updated an issue
Jenkins / JENKINS-50441
p4sync with default client name fails with latest version of p4 plugin
Change By:
Michael Rose
This used to work:{quote}p4sync credential: 'p4integ.prod', populate: previewOnly(quiet: true, pin: env.latest_version), source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote}... p4 client o jenkins-master-{color:#14892c}scm * - * promote{color}_ansible_playbooks-0 + ... p4 client -i + P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Mapping '//jenkins-master-{color:#ff}scm * / * promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.{quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed
[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin
Title: Message Title
Michael Rose updated an issue
Jenkins / JENKINS-50441
p4sync with default client name fails with latest version of p4 plugin
Change By:
Michael Rose
This used to work:{quote}p4sync credential: 'p4integ.prod', populate: previewOnly(quiet: true, pin: env.latest_version), source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote}... p4 client - o jenkins-master-{color:#14892c}scm-promote{color}_ansible_playbooks-0 + ... p4 client -i + P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Mapping '//jenkins-master-{color:#ff}scm/promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.{quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin
Title: Message Title
Michael Rose updated an issue
Jenkins / JENKINS-50441
p4sync with default client name fails with latest version of p4 plugin
Change By:
Michael Rose
This used to work:{quote}p4sync credential: 'p4integ.prod', populate: previewOnly(quiet: true, pin: env.latest_version), source: depotSource('//foo/bar/playbooks'){quote}Now it produces the following error message:{quote}... p4 client - o jenkins-master-{color:#14892c}scm*-*promote{color}_ansible_playbooks-0 +... p4 client -i +P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.Mapping '//jenkins-master-{color:#ff}scm*/*promote{color}_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.{quote}Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the
[JIRA] (JENKINS-50441) p4sync with default client name fails with latest version of p4 plugin
Title: Message Title
Michael Rose created an issue
Jenkins / JENKINS-50441
p4sync with default client name fails with latest version of p4 plugin
Issue Type:
Bug
Assignee:
Paul Allen
Components:
p4-plugin
Created:
2018-03-27 22:12
Priority:
Minor
Reporter:
Michael Rose
This used to work:
p4sync credential: 'p4integ.prod', populate: previewOnly(quiet: true, pin: env.latest_version), source: depotSource('//foo/bar/playbooks')
Now it produces the following error message:
... p4 client o jenkins-masterscm*-*promote_ansible_playbooks-0 + ... p4 client -i + P4: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification. Mapping '//jenkins-master-scm*/*promote_ansible_playbooks-0/...' is not under '//jenkins-master-scm-promote_ansible_playbooks-0/...'.
Notice that the client name is properly replaced in the p4 client call, but not in the actual client view.
[JIRA] (JENKINS-46893) Huge amount of TcpSlaveAgentListener EOFException on Kubernetes
Title: Message Title Oleg Nenashev resolved as Not A Defect Closing according to the response Jenkins / JENKINS-46893 Huge amount of TcpSlaveAgentListener EOFException on Kubernetes Change By: Oleg Nenashev Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-47891) Bitbucket branch source plugin does not understand the new Bitbucket webhooks
Title: Message Title Andy Airey edited a comment on JENKINS-47891 Re: Bitbucket branch source plugin does not understand the new Bitbucket webhooks Still no feedback on [https://github.com/jenkinsci/bitbucket-branch-source-plugin/compare/master...kwin:bbserver-use-native-webhooks] ? We unfortunately do not have the liberty to install third-party plugins on Bitbucket Server, so it would be really great to use (and manage) the native webhooks. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47891) Bitbucket branch source plugin does not understand the new Bitbucket webhooks
Title: Message Title Andy Airey commented on JENKINS-47891 Re: Bitbucket branch source plugin does not understand the new Bitbucket webhooks Still no feedback on https://github.com/jenkinsci/bitbucket-branch-source-plugin/compare/master...kwin:bbserver-use-native-webhooks ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47077) "Periodically if not otherwise run" interval does not trigger index scan
Title: Message Title Andy Airey commented on JENKINS-47077 Re: "Periodically if not otherwise run" interval does not trigger index scan We have to scan all our multibranch pipeline repositories separately and cannot configure them (yet) as stated above... Otherwise the branch and PR jobs never get triggered. Also the new Bitbucket webhooks are not supported (JENKINS-47891) yet so we are kind of stuck as we cannot install extra plugins on Bitbucket Server. This is really annoying. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title Heiko Nardmann commented on JENKINS-50434 Re: Misbehaviour of feature: Pin the workspace to the build host Is the workspace name created only once or is that _expression_ evaluated each time? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title
Heiko Nardmann edited a comment on JENKINS-50434
Re: Misbehaviour of feature: Pin the workspace to the build host
No, the job is not restricted to one slave. That is why I added \ { \ { {{ NODE_NAME}} }} to the workspace name ...Hmmm ... time to talk about the intended behaviour of that feature {{Pin the workspace to the build host}} ...My perception is that the following activities happen (based on {{jenkins_$\{NODE_NAME}_$\{JOB_NAME}}} as the workspace name format): # initially the job {{MyJob}} runs on {{SlaveA}} => a new client spec is created with {{jenkins_SlaveA_MyJob}} # second time it runs on {{SlaveB}} => a new client spec is created with {{jenkins_SlaveB_MyJob}} # third time it runs on {{SlaveA}} again => the client spec {{jenkins_SlaveA_MyJob}} is usedMy understanding is that for each (Slave,Job) pair a dedicated client spec is created?Totally wrong?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title
Heiko Nardmann edited a comment on JENKINS-50434
Re: Misbehaviour of feature: Pin the workspace to the build host
No, the job is not restricted to one slave. That is why I added \{\{{{NODE_NAME to the workspace name ... Hmmm ... time to talk about the intended behaviour of that feature {{Pin the workspace to the build host}} ...My perception is that the following activities happen (based on {{jenkins_$\{NODE_NAME}_$\{JOB_NAME}}} as the workspace name format): # initially the job {{MyJob}} runs on {{SlaveA}} => a new client spec is created with {{jenkins_SlaveA_MyJob}} # second time it runs on {{SlaveB}} => a new client spec is created with {{jenkins_SlaveB_MyJob}} # third time it runs on {{SlaveA}} again => the client spec {{jenkins_SlaveA_MyJob}} is usedMy understanding is that for each (Slave,Job) pair a dedicated client spec is created?Totally wrong?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45970) isTrusted & loadTrusted steps
Title: Message Title Jesse Glick commented on JENKINS-45970 Re: isTrusted & loadTrusted steps Would also like a pathless isTrusted() to just check whether the whole revision is from a trusted source or not. Looks like you could currently check env.CHANGE_FORK == null to behave differently on origin vs. fork PRs, which is not as good but maybe good enough as a workaround. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50440) Jenkins builds mishandle parameters after git push notifyCommit
Title: Message Title Michael Baldwin created an issue Jenkins / JENKINS-50440 Jenkins builds mishandle parameters after git push notifyCommit Issue Type: Bug Assignee: Unassigned Components: notification-plugin Created: 2018-03-27 20:34 Labels: notifyCommit Priority: Minor Reporter: Michael Baldwin We've encountered a problem after a notifyCommit. I have multiple parameterized Jenkins jobs all configured to checkout the same branch. Each has the same parameter name, different values. When we trigger it manually? Its perfectly fine. When its triggered by git push notify? Each of the jobs is started but the parameter is duplicated. I.e., TestJob1 checks out git (master) and has parameter FIZZLE=1.0 TestJob2 checks out same git (master) and has parameter FIZZLE=2.0 TestJob3 checks out same git (master) and has parameter FIZZLE=3.0 When I do a git commit and http://acs-jenkins.us.foo.com/git/notifyCommit/?url=""> HTTP/1.1 All three jobs get triggered but Jenkins parameters show an array when you look at http://jenkins.foo.com/job/TestJob1|2|3/ /parameters each job is triggered with all three params FIZZLE=1.0 FIZZLE=2.0 FIZZLE=3.0. Our jenkins git plugin is up to-date (3.8.0). We've checked to see if someone else has reported it... Added log recorders. etc. Kinda hopin' someone has seen it. No one else has it seems
[JIRA] (JENKINS-50434) Misbehaviour of feature: Pin the workspace to the build host
Title: Message Title
Heiko Nardmann commented on JENKINS-50434
Re: Misbehaviour of feature: Pin the workspace to the build host
No, the job is not restricted to one slave. Hmmm ... time to talk about the intended behaviour of that feature Pin the workspace to the build host ... My perception is that the following activities happen (based on jenkins_${NODE_NAME}_${JOB_NAME} as the workspace name format):
initially the job MyJob runs on SlaveA => a new client spec is created with jenkins_SlaveA_MyJob
second time it runs on SlaveB => a new client spec is created with jenkins_SlaveB_MyJob
third time it runs on SlaveA again => the client spec jenkins_SlaveA_MyJob is used
My understanding is that for each (Slave,Job) pair a dedicated client spec is created? Totally wrong?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50439) Remove spurious warning when starting Jenkins
Title: Message Title Baptiste Mathus updated JENKINS-50439 Jenkins / JENKINS-50439 Remove spurious warning when starting Jenkins Change By: Baptiste Mathus Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50439) Remove spurious warning when starting Jenkins
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-50439 Remove spurious warning when starting Jenkins Issue Type: Improvement Assignee: Baptiste Mathus Components: extras-executable-war Created: 2018-03-27 20:17 Labels: essentials Priority: Minor Reporter: Baptiste Mathus On many (all?) Jenkins startups, I was seeing the following WARN: Mar 27, 2018 10:04:00 PM Main deleteWinstoneTempContents WARNING: Failed to delete the temporary Winstone file /tmp/winstone/jenkins-2.112.war After a quick look at the code, it seems like this is just because /tmp/winstone/jenkins-2.112.war can be absent. I think we can modify the code to just not log anything if the file to remove is not found. Add Comment
[JIRA] (JENKINS-50439) Remove spurious warning when starting Jenkins
Title: Message Title Baptiste Mathus started work on JENKINS-50439 Change By: Baptiste Mathus Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40143) Duplicate email with Extended E-mail Notification
Title: Message Title Dilip Mahadevappa commented on JENKINS-40143 Re: Duplicate email with Extended E-mail Notification We started to see this issue with below specs Jenkins ver. 1.651.3 Build Flow plugin 0.20 Email Extension Plugin 2.52 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46172) error when I change ssh server settings for authorization
Title: Message Title Jason Norton commented on JENKINS-46172 Re: error when I change ssh server settings for authorization Hi Łukasz Jąder, I believe it is entirely possible that this was caused by migration code changes. I have been having to edit manually to add users and have been over the code many times as I was also suspecting this to be the issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31215) cmake installation on osx: missing files & strange layout
Title: Message Title Martin Weber assigned an issue to Martin Weber Jenkins / JENKINS-31215 cmake installation on osx: missing files & strange layout Change By: Martin Weber Assignee: Martin Weber Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50418) when {branch} stage conditional regression
Title: Message Title
Andrew Bayer commented on JENKINS-50418
Re: when {branch} stage conditional regression
Probably environment name: "GIT_BRANCH", value: "origin/master" as you tried out above - there's no consistent env var for the branch across all SCMs except in the context of a multibranch Pipeline, so you do need check that Git-specific one.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50306) "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion
Title: Message Title Andrew Bayer commented on JENKINS-50306 Re: "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion Yup, it's throttle-concurrent-builds - it'd be worth knowing how you have the throttling category set up (are you saying only run X of jobs in this category across all nodes, or ...on a single node, etc), though. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47188) CmakeTool fails with no message when binaries are not available
Title: Message Title Martin Weber assigned an issue to Martin Weber Jenkins / JENKINS-47188 CmakeTool fails with no message when binaries are not available Change By: Martin Weber Assignee: Martin Weber Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50306) "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50306 "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion Change By: Andrew Bayer Component/s: throttle-concurrent-builds-plugin Component/s: workflow-durable-task-step-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50418) when {branch} stage conditional regression
Title: Message Title
Eric Nelson commented on JENKINS-50418
Re: when {branch} stage conditional regression
This one is a stand alone pipeline job. Which explains why when I checked BRANCH_NAME it also did nothing. Is there a recommendation for branch checking in stand alone pipeline jobs?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-2734) JUnit reports - setting threshold of failed tests to mark build as stable/unstable/failed
Title: Message Title Shannon Kerr commented on JENKINS-2734 Re: JUnit reports - setting threshold of failed tests to mark build as stable/unstable/failed Any plans to implement this? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-34998) Make CMake plugin compatible with pipeline
Title: Message Title Martin Weber resolved as Fixed resolved in 2.5.0 Jenkins / JENKINS-34998 Make CMake plugin compatible with pipeline Change By: Martin Weber Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50380) script-security doesn't handle a non-standard Collection without a constructor taking an array properly
Title: Message Title Andrew Bayer commented on JENKINS-50380 Re: script-security doesn't handle a non-standard Collection without a constructor taking an array properly Ok, I've got PRs up for groovy-sandbox and script-security that fix this by making sure Checker.checkedCast doesn't bother jumping through the DefaultTypeTransformation.castToType hoops if a simple clazz.cast will do the trick. Let's see what the reviewers think. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50380) script-security doesn't handle a non-standard Collection without a constructor taking an array properly
Title: Message Title Andrew Bayer started work on JENKINS-50380 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50380) script-security doesn't handle a non-standard Collection without a constructor taking an array properly
Title: Message Title Andrew Bayer updated JENKINS-50380 Jenkins / JENKINS-50380 script-security doesn't handle a non-standard Collection without a constructor taking an array properly Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50427) Libvirt Slaves Plugin needs updating to 2.x
Title: Message Title Glenn Burkhardt commented on JENKINS-50427 Re: Libvirt Slaves Plugin needs updating to 2.x I was able to fix this with the attached files. Some more work is needed to add this to the libvirt-slave release, e.g., there are unchecked type conversions in the methods added to VirtualMachineLauncher. libvirt-fix.tar.xz Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47366) Checkout in second stage sets SUCCESS on Github commit
Title: Message Title
Frank Grimes updated an issue
Jenkins / JENKINS-47366
Checkout in second stage sets SUCCESS on Github commit
Change By:
Frank Grimes
In tIn a multi-agent pipeline, 'checkout' step sets SUCCESS status to Github commit. This happens if any previous stage already published successful build result.So commit is marked as SUCCESS for some time. If later tests fail, commit status is changed for FAILURE. *This enables bad code merge from a PR and bad code deployment*.This is seen in several complex pipelines with the both pipeline default checkout and with {{checkout scm}}. Here is a minimal example, where {{junit}} or any other publishing step replaced with {{currentBuild.result = 'SUCCESS'}}:{code:java}pipeline {agent nonestages {stage('Set SUCCESS') {agent anysteps {script {currentBuild.result = 'SUCCESS'}}}stage('Checkout, test, fail') {agent anysteps {sh """sleep 60 exit 1"""}}}}{code}Here are selected lines rom a build log. Note two 'GitHub has been notified' messages:{code:java}Branch indexing06:33:50 Connecting to https://api.github.com using Obtained Jenkinsfile from 2c5c8ce94a1ba597eab4c959a4f43f505c38a77c[Pipeline] stage[Pipeline] { (Set SUCCESS)[Pipeline] nodeRunning on master in /Home/workspace/a_a_a-NZHSOOK6DLZNS5KEQNGRGFRRYDRS74EJJG6PZYDHEPRJUQRTRCDA[Pipeline] {[Pipeline] checkout...[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Checkout, test, fail)[Pipeline] nodeRunning on master in /Home/workspace/a_a_a-NZHSOOK6DLZNS5KEQNGRGFRRYDRS74EJJG6PZYDHEPRJUQRTRCDA[Pipeline] {[Pipeline] checkout > /usr/bin/git rev-parse --is-inside-work-tree # timeout=60Fetching changes from the remote Git repository... > /usr/bin/git config core.sparsecheckout # timeout=60 > /usr/bin/git checkout -f 7ce1f7ba4b355294f3fc475b9d84528eba3669cbCommit message: "Update Jenkinsfile"GitHub has been notified of this commit’s build result[Pipeline] withEnv[Pipeline] {[Pipeline] sh[a_a_a-NZHSOOK6DLZNS5KEQNGRGFRRYDRS74EJJG6PZYDHEPRJUQRTRCDA] Running shell script+ sleep 60+ exit 1[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // stage[Pipeline] End of PipelineGitHub has been notified of this commit’s build resultERROR: script returned exit code 1Finished: FAILURE{code}
[JIRA] (JENKINS-47366) Checkout in second stage sets SUCCESS on Github commit
Title: Message Title
Frank Grimes updated an issue
Jenkins / JENKINS-47366
Checkout in second stage sets SUCCESS on Github commit
Change By:
Frank Grimes
tIn In a multi-agent pipeline, 'checkout' step sets SUCCESS status to Github commit. This happens if any previous stage already published successful build result.So commit is marked as SUCCESS for some time. If later tests fail, commit status is changed for FAILURE. *This enables bad code merge from a PR and bad code deployment*.This is seen in several complex pipelines with the both pipeline default checkout and with {{checkout scm}}. Here is a minimal example, where {{junit}} or any other publishing step replaced with {{currentBuild.result = 'SUCCESS'}}:{code:java}pipeline {agent nonestages {stage('Set SUCCESS') {agent anysteps {script {currentBuild.result = 'SUCCESS'}}}stage('Checkout, test, fail') {agent anysteps {sh """sleep 60 exit 1"""}}}}{code}Here are selected lines rom a build log. Note two 'GitHub has been notified' messages:{code:java}Branch indexing06:33:50 Connecting to https://api.github.com using Obtained Jenkinsfile from 2c5c8ce94a1ba597eab4c959a4f43f505c38a77c[Pipeline] stage[Pipeline] { (Set SUCCESS)[Pipeline] nodeRunning on master in /Home/workspace/a_a_a-NZHSOOK6DLZNS5KEQNGRGFRRYDRS74EJJG6PZYDHEPRJUQRTRCDA[Pipeline] {[Pipeline] checkout...[Pipeline] withEnv[Pipeline] {[Pipeline] script[Pipeline] {[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Checkout, test, fail)[Pipeline] nodeRunning on master in /Home/workspace/a_a_a-NZHSOOK6DLZNS5KEQNGRGFRRYDRS74EJJG6PZYDHEPRJUQRTRCDA[Pipeline] {[Pipeline] checkout > /usr/bin/git rev-parse --is-inside-work-tree # timeout=60Fetching changes from the remote Git repository... > /usr/bin/git config core.sparsecheckout # timeout=60 > /usr/bin/git checkout -f 7ce1f7ba4b355294f3fc475b9d84528eba3669cbCommit message: "Update Jenkinsfile"GitHub has been notified of this commit’s build result[Pipeline] withEnv[Pipeline] {[Pipeline] sh[a_a_a-NZHSOOK6DLZNS5KEQNGRGFRRYDRS74EJJG6PZYDHEPRJUQRTRCDA] Running shell script+ sleep 60+ exit 1[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // stage[Pipeline] End of PipelineGitHub has been notified of this commit’s build resultERROR: script returned exit code 1Finished: FAILURE{code}
[JIRA] (JENKINS-50427) Libvirt Slaves Plugin needs updating to 2.x
Title: Message Title Glenn Burkhardt updated an issue Jenkins / JENKINS-50427 Libvirt Slaves Plugin needs updating to 2.x Change By: Glenn Burkhardt Attachment: libvirt-fix.tar.xz Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47834) Add the support for Remoting work dir configuration of JNLP Launcher
Title: Message Title Glenn Burkhardt commented on JENKINS-47834 Re: Add the support for Remoting work dir configuration of JNLP Launcher I was able to patch "libvirt-slave" to fix this. The "slave.jar" file on the Windows guest needed to be updated with the one generated by Jenkins 2.108. I posted the patched files on this thread: https://groups.google.com/forum/#!topic/jenkinsci-dev/w66m_3LTAxs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50306) "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion
Title: Message Title Jon B commented on JENKINS-50306 Re: "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion Indeed I am using the "Throttle Concurrent Builds Plug-in" because my monolith's main pipeline is very busy and if i don't throttle, the agent capacity would get slathered too many concurrent job runs making them all take forever. My pipeline logic is quite complex but I'm pretty sure the cause must be a flaw in the concurrent builds plugin. If you think it is essential to triage, I will create a watered down pipeline that repros this behavior but I'll hold on that until you confirm its worth my time to produce such a Jenkinsfile. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50306) "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion
Title: Message Title Jon B edited a comment on JENKINS-50306 Re: "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion Indeed I am using the "Throttle Concurrent Builds Plug-in" because my monolith's main pipeline is very busy and if i don't throttle, the agent capacity would get slathered across too many concurrent job runs making them all take forever.My pipeline logic is quite complex but I'm pretty sure the cause must be a flaw in the concurrent builds plugin. If you think it is essential to triage, I will create a watered down pipeline that repros this behavior but I'll hold on that until you confirm its worth my time to produce such a Jenkinsfile. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48494) Pass Additional attributes from Jenkins to HP Performance Center 12.53
Title: Message Title Senthilkumar Rasan commented on JENKINS-48494 Re: Pass Additional attributes from Jenkins to HP Performance Center 12.53 Is there any update on passing additional attributes to PC RTS? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50438) Mercurial clones every time to read Jenkinsfile in Multipipeline Job.
Title: Message Title Andrew Zwicky created an issue Jenkins / JENKINS-50438 Mercurial clones every time to read Jenkinsfile in Multipipeline Job. Issue Type: Bug Assignee: Unassigned Attachments: log.txt, plugins.txt, redacted_jenkinsfile.txt Components: mercurial-plugin Created: 2018-03-27 18:35 Environment: Attached plugins.txt Priority: Major Reporter: Andrew Zwicky Problem Description: My team is currently experienceing disk space issues on our master node from a multipipeline job. We have a large mercurial repository set up that is cloning the repository each time instead of referencing the hgcached repository to read the Jenkinsfile. Our repository is set up with many subrepositories that are being cloned from our server. I expect that this might have something to do with it. I see that the cached repository has all the recent reveisions, but is not updated to any of them, which might not trigger any of the subrepositories to be downloaded? Each time a new branch is pushed in our repository, this triggers a new branch build in the multipipeline job (as expected). To read the Jenkinsfile for that revision, a clone is made to the master/jobs/ folder (not expected). I was expecting the Jenkinsfile to be able to be read from the cached repository instead of cloning the repo. Am I understanding the "Repository Sharing" setting properly? We have one master node and two slave machines set up. On the two slave machines, a customWorkspace and disabledConcurrentBuilds is used to limit excessive cloning (unsure if this is the sanctioned approach, but it has
[JIRA] (JENKINS-50418) when {branch} stage conditional regression
Title: Message Title
Andrew Bayer commented on JENKINS-50418
Re: when {branch} stage conditional regression
The branch conditional is checking against the more generalized BRANCH_NAME environment variable, which is only set for multibranch Pipelines. Is this on a multibranch Pipeline or just a standalone Pipeline job?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50436) Investigate having code coverage reports archived
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50436 Investigate having code coverage reports archived Change By: Karl Shultz Summary: Investigate having code coverage reports available on archived Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50418) when {branch} stage conditional regression
Title: Message Title
Andrew Bayer assigned an issue to Andrew Bayer
Jenkins / JENKINS-50418
when {branch} stage conditional regression
Change By:
Andrew Bayer
Assignee:
Andrew Bayer
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50418) when {branch} stage conditional regression
Title: Message Title
Andrew Bayer updated an issue
Jenkins / JENKINS-50418
when {branch} stage conditional regression
Change By:
Andrew Bayer
Component/s:
pipeline-model-definition-plugin
Component/s:
pipeline
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50380) script-security doesn't handle a non-standard Collection without a constructor taking an array properly
Title: Message Title Andrew Bayer commented on JENKINS-50380 Re: script-security doesn't handle a non-standard Collection without a constructor taking an array properly So: this was introduced in script-security 1.31 as part of one of a number of security fixes relating to casting. There are actually two things going on here - first is that the logic for actually doing a sandbox-checked cast still tries to do a cast even when the target class and the class of the object to cast are exactly the same. That's obviously goofy and shouldn't happen. The second is that the logic for doing the sandbox-checked cast sees any Collection that isn't in java.util (those are handled natively by Groovy so we don't worry about them) and, rather than simply casting it, it does a new ClassInQuestion(original.toArray()). Which normally works for a Collection since most will have a constructor taking an array of objects, but doesn't work in this case, where there is no such constructor. While I do believe the cast-to-same-class case should be fixed in general, and I am not pleased with the array constructor for a Collection thing, the bigger issue here is that I don't think we should be ending up in a sandbox-checked cast in this situation in the first place. However, I can't figure out how to prevent that without reopening the casting related issues this is dealing with in the first place...so it may be that we need to accept the potentially pointless sandbox-checked cast, but ensure that said sandbox-checked cast will check at runtime if a straight Class#cast call would suffice and do that instead of handing off to Groovy's casting magic... Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49488) promotion conditions to support OR condition
Title: Message Title Rick Liu commented on JENKINS-49488 Re: promotion conditions to support OR condition Pull request prepared: https://github.com/jenkinsci/promoted-builds-plugin/pull/115 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49486) Approvers field doesn't expand variable in the build
Title: Message Title Rick Liu commented on JENKINS-49486 Re: Approvers field doesn't expand variable in the build Pull-request prepared: https://github.com/jenkinsci/promoted-builds-plugin/pull/114 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50380) script-security doesn't handle a non-standard Collection without a constructor taking an array properly
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50380 script-security doesn't handle a non-standard Collection without a constructor taking an array properly Change By: Andrew Bayer Summary: pipeline using shared library failed after upgrading Jenkins to 2.89.4.2 script-security doesn't handle a non-standard Collection without a constructor taking an array properly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50437) Environment variables using PATH+SOMETHING syntax clear the previous env var
Title: Message Title Oleg Nenashev commented on JENKINS-50437 Re: Environment variables using PATH+SOMETHING syntax clear the previous env var Hit it in my test instance Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50350) JEP-200: ConversionException: Refusing to unmarshal logPrefixCache
Title: Message Title Andrew Bayer assigned an issue to Sam Van Oort Jenkins / JENKINS-50350 JEP-200: ConversionException: Refusing to unmarshal logPrefixCache Change By: Andrew Bayer Assignee: Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50348) Why does "Pipeline: Groovy" require "Support Core"?
Title: Message Title Andrew Bayer commented on JENKINS-50348 Re: Why does "Pipeline: Groovy" require "Support Core"? The support-core dependency is optional - https://github.com/jenkinsci/workflow-cps-plugin/blob/master/pom.xml#L114 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50343) ComposedClosure not working with List.each
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-50343 ComposedClosure not working with List.each Change By: Andrew Bayer Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50343) ComposedClosure not working with List.each
Title: Message Title Andrew Bayer commented on JENKINS-50343 Re: ComposedClosure not working with List.each So I think this is something similar to JENKINS-44924 - ComposedClosure#call is calling delegate.call, but in a non-CPS context, so the old CpsCallableInvocation fun we used to have with any use of .each and friends is showing up again. I don't yet have a good answer on JENKINS-44924, but once I do, it should be easy enough to handle ComposedClosure with a CPS-specific implementation. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50437) Environment variables using PATH+SOMETHING syntax clear the previous env var
Title: Message Title Carlos Sanchez updated JENKINS-50437 Jenkins / JENKINS-50437 Environment variables using PATH+SOMETHING syntax clear the previous env var Change By: Carlos Sanchez Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50342) Provide ability to disable creation of Github Organization jobs
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50342 Provide ability to disable creation of Github Organization jobs Change By: Andrew Bayer Component/s: github-organization-folder-plugin Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49332) Jenkins unable to manage webhooks of Github organization
Title: Message Title Frank Grimes commented on JENKINS-49332 Re: Jenkins unable to manage webhooks of Github organization We're having the same problem trying to use the GitHub Branch Source Plugin. It seems to be ignoring the username in the configured username/password credentials and defaulting to the organization (Owner) value. This is completely blocking us from making use of the plugin since no WebHook registration can occur so our builds can't be triggered by PRs/etc. Any idea when this might be fixed? Also, is the priority of this really 'minor'? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50317) Pipeline job is failed with java.lang.StackOverflowError
Title: Message Title Andrew Bayer commented on JENKINS-50317 Re: Pipeline job is failed with java.lang.StackOverflowError Can you attach your utils.groovy, please? It looks like something is going wrong specifically in serialization of the program state, and given that all your work seems to actually be in that utils.groovy script, I can't tell what's going on. Also, it'd be great if you could put together a minimal reproduction case or zip up the build directory for a build that's failing like this (specifically the workflow subdirectory) so that we can see where exactly the failure is happening. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50437) Environment variables using PATH+SOMETHING syntax clear the previous env var
Title: Message Title Carlos Sanchez commented on JENKINS-50437 Re: Environment variables using PATH+SOMETHING syntax clear the previous env var Caused by the changes to KubernetesComputer.java in JENKINS-42582 https://github.com/jenkinsci/kubernetes-plugin/pull/291/files#diff-d7c591c5115c154bd8394f3479e07131 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50309) Sometimes Docker slaves hang in 'Waiting for next available executor' state
Title: Message Title Andrew Bayer commented on JENKINS-50309 Re: Sometimes Docker slaves hang in 'Waiting for next available executor' state Can you include your Jenkinsfile? Or a minimal reproduction case? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50437) Environment variables using PATH+SOMETHING syntax clear the previous env var
Title: Message Title Carlos Sanchez started work on JENKINS-50437 Change By: Carlos Sanchez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50437) Environment variables using PATH+SOMETHING syntax clear the previous env var
Title: Message Title
Carlos Sanchez created an issue
Jenkins / JENKINS-50437
Environment variables using PATH+SOMETHING syntax clear the previous env var
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-03-27 17:58
Priority:
Minor
Reporter:
Carlos Sanchez
withEnv(['PATH+MAVEN=/bin/mvn']) {
sh 'echo $PATH'
}
will set PATH to /bin/mvn ignoring previous value
Add Comment
[JIRA] (JENKINS-50307) While running in parallel for a loop, the index is wrong for each iteration
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50307 While running in parallel for a loop, the index is wrong for each iteration Change By: Andrew Bayer Component/s: workflow-cps-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50306) "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion
Title: Message Title Andrew Bayer commented on JENKINS-50306 Re: "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion Yes, when the node step is executed, it goes onto the agent. If you're seeing the build start, get to the node step, and immediately get that message, something's wrong somewhere, but there is a common case for that message, sadly, on master restart and running Pipelines resuming - often, dynamically provisioned agents no longer exist but Jenkins still tries to resume Pipelines onto the agents they were on at the time the master stopped, so things get gummed up. If that's not the situation where you're seeing this, is there any chance you could include your Jenkinsfile, or even better a minimal reproduction case? Oh, and are you using the throttle step by any chance? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50306) "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50306 "Still waiting to schedule task" indicates a flaw in the Jenkins pipelining design in my opinion Change By: Andrew Bayer Component/s: workflow-durable-task-step-plugin Component/s: pipeline Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50305) sandbox should handle normal Groovy coercions
Title: Message Title Andrew Bayer commented on JENKINS-50305 Re: sandbox should handle normal Groovy coercions I could have sworn I'd actually dealt with this somewhere, but I guess there was more involved. For the moment, you can get around this by using CharSequence in the method signature rather than String - GStringImpl implements CharSequence, so that'll work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50299) Pre-pending to PATH environment variable in declarative pipeline
Title: Message Title Andrew Bayer commented on JENKINS-50299 Re: Pre-pending to PATH environment variable in declarative pipeline So for the moment, don't worry about the warning - I still need to find a way to support PATH+EXTRA in Declarative, but PATH = '/usr/bin:$PATH' should work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
