[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Carlos Sanchez resolved as Fixed Jenkins / JENKINS-42582 ssh-agent not applied in kubernetes container Change By: Carlos Sanchez 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-43892) Developer would like to see all successful test results
Title: Message Title Ivan Meredith started work on JENKINS-43892 Change By: Ivan Meredith 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-49974) Error in Publishing Release note in confluence.
Title: Message Title Vatsal Harde created an issue Jenkins / JENKINS-49974 Error in Publishing Release note in confluence. Issue Type: Bug Assignee: NovaTec Consulting Components: jira-plugin, release-helper-plugin Created: 2018-03-07 07:06 Environment: jenkins version 2.89.4,java 8,Release Helper -1.3.2 Labels: jenkins jira atlassian release-plugin Priority: Blocker Reporter: Vatsal Harde ERROR: Build step failed with exception org.apache.http.client.HttpResponseException: Not Found at org.apache.http.impl.client.AbstractResponseHandler.handleResponse(AbstractResponseHandler.java:70) at org.apache.http.impl.client.BasicResponseHandler.handleResponse(BasicResponseHandler.java:66) at rocks.inspectit.releaseplugin.JsonHTTPClientWrapper.executeRequest(JsonHTTPClientWrapper.java:142) Caused: java.lang.RuntimeException at rocks.inspectit.releaseplugin.JsonHTTPClientWrapper.executeRequest(JsonHTTPClientWrapper.java:150) at rocks.inspectit.releaseplugin.JsonHTTPClientWrapper.getJson(JsonHTTPClientWrapper.java:245) at rocks.inspectit.releaseplugin.ConfluenceAccessTool.getPageIDByTitle(ConfluenceAccessTool.java:67) Caused: java.lang.RuntimeException at rocks.inspectit.releaseplugin.ConfluenceAccessTool.getPageIDByTitle(ConfluenceAccessTool.java:80) at rocks.inspectit.releaseplugin.releasenotes.ConfluenceReleaseNotesPublisher.perform(ConfluenceReleaseNotesPublisher.java:115) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at
[JIRA] (JENKINS-34002) Means of declaring a Pipeline's plugin requirements
Title: Message Title Christoph Obexer commented on JENKINS-34002 Re: Means of declaring a Pipeline's plugin requirements While commenting on JENKINS-49651 I had an idea that could make this almost automatic: Extend plugin metadata with (RPM style) Provides for pipeline symbols (& extensions,... ) they implement. With that metadata available in the Update Center a build that tries to use say the junit step could instead of failing the build be paused and the user could be prompted if they want to install the plugin that provides that step of if they want to abort the build: Pipeline execution detects unknown step / use of a global / unknown type referenced. Pipeline execution paused (like with an input step?) Query Update Center metadata if there are plugins that provide the missing references Prompt the user to install those plugins or fail the build (possibly saving ignored dependencies) User selects to install the missing plugins -> continue the pipeline execution maximum user satisfaction 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.
[JIRA] (JENKINS-34581) Please add support for Pipelines to the Powershell plugin
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-34581 Please add support for Pipelines to the Powershell plugin Change By: Michael Fowler Component/s: powershell-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-49973) Windows EXE runner should spport pipeline
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-49973 Windows EXE runner should spport pipeline Change By: Michael Fowler Labels: 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-49973) Windows EXE runner should spport pipeline
Title: Message Title Michael Fowler started work on JENKINS-49973 Change By: Michael Fowler 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-49973) Windows EXE runner should spport pipeline
Title: Message Title Michael Fowler created an issue Jenkins / JENKINS-49973 Windows EXE runner should spport pipeline Issue Type: Improvement Assignee: Michael Fowler Components: windows-exe-runner-plugin Created: 2018-03-07 06:50 Priority: Major Reporter: Michael Fowler 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-20878) Windows Command timing out running Gulp Script.
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-20878 Windows Command timing out running Gulp Script. Change By: Michael Fowler Component/s: batch-task-plugin Component/s: windows-exe-runner-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-38214) Windows EXE runner should handle token macros
Title: Message Title Michael Fowler started work on JENKINS-38214 Change By: Michael Fowler 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-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title
Christoph Obexer edited a comment on JENKINS-49651
Re: Extend plugin/update center metadata with known incompatibilities
{quote}I think we can get away with a simpler system{quote}Sure, I just think that with Requirements and Incompatible-With (aka Conflicts) you almost have everything in place to enable:* Renames* Splits* Merges So I added the RPM documentation links here to save the implementer the time to come up with compatible semantics themselves.Thinking about this some more I think Obsoletes and also handling core updates in the same resolver would net you almost everything. (IIRC KK talked about wanting to update core like the plugins)
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-49651) Extend plugin/update center metadata with known incompatibilities
Title: Message Title Christoph Obexer commented on JENKINS-49651 Re: Extend plugin/update center metadata with known incompatibilities I think we can get away with a simpler system Sure, I just think that with Requirements and Incompatible-With (aka Conflicts) you almost have everything in place to enable: Renames Splits Merges So I added the RPM documentation links here to save the implementer the time to come up with compatible semantics themselves. Thinking about this some more I think Obsoletes and also handling core updates in the same resolver would net you almost everything. (IIRC KK talked about wanting to update core like the plugins) 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-49972) Crowd SSO(Crowd 2 Plugin) not working properly with Jenkins
Title: Message Title Rohan Donthoji created an issue Jenkins / JENKINS-49972 Crowd SSO(Crowd 2 Plugin) not working properly with Jenkins Issue Type: Bug Assignee: Kanstantsin Shautsou Attachments: com.atlassian.crowd, crowd.properties, de.theit.jenkins.crowd, hudson.security, jenkins.security Components: crowd2-plugin Created: 2018-03-07 05:38 Environment: awt.toolkit sun.awt.X11.XToolkit com.sun.akuma.Daemon daemonized executable-war /usr/lib/jenkins/jenkins.war file.encoding UTF-8 file.encoding.pkg sun.io file.separator / java.awt.graphicsenv sun.awt.X11GraphicsEnvironment java.awt.headless true java.awt.printerjob sun.print.PSPrinterJob java.class.path /usr/lib/jenkins/jenkins.war java.class.version 52.0 java.endorsed.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.102-4.b14.el7.x86_64/jre/lib/endorsed java.ext.dirs /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.102-4.b14.el7.x86_64/jre/lib/ext:/usr/java/packages/lib/ext java.home /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.102-4.b14.el7.x86_64/jre java.io.tmpdir /tmp java.library.path /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.runtime.name OpenJDK Runtime Environment java.runtime.version 1.8.0_102-b14 java.specification.name Java Platform API Specification java.specification.vendor Oracle Corporation java.specification.version 1.8 java.vendor Oracle Corporation java.vendor.url http://java.oracle.com/ java.vendor.url.bug http://bugreport.sun.com/bugreport/ java.version 1.8.0_102 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.specification.name Java Virtual Machine Specification java.vm.specification.vendor Oracle Corporation java.vm.specification.version 1.8 java.vm.vendor Oracle Corporation java.vm.version 25.102-b14 JENKINS_HOME /var/lib/jenkins jna.loaded true jna.platform.library.path /usr/lib64:/lib64:/usr/lib:/lib:/usr/lib64/dyninst:/usr/lib64/mysql:/usr/lib64/iscsi jnidispatch.path /tmp/jna--1712433994/jna9092694402374080432.tmp line.separator mail.smtp.sendpartial true mail.smtps.sendpartial true os.arch amd64 os.name Linux os.version 3.10.0-514.el7.x86_64 path.separator : sun.arch.data.model 64 sun.boot.class.path
[JIRA] (JENKINS-47077) "Periodically if not otherwise run" interval does not trigger index scan
Title: Message Title Bill O'Neil commented on JENKINS-47077 Re: "Periodically if not otherwise run" interval does not trigger index scan Also seeing this issue on Jenkins ver. 2.89.4 from a clean docker install. All plugins are up to date. The timer never seems to trigger the scan but manual scans work fine. 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-48228) Layout broken after short duration not used
Title: Message Title Ricky Wu closed an issue as Fixed No happen again Jenkins / JENKINS-48228 Layout broken after short duration not used Change By: Ricky Wu 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-48274) Saving to Github/GHE requires email with user or it fails
Title: Message Title Ivan Meredith updated JENKINS-48274 Jenkins / JENKINS-48274 Saving to Github/GHE requires email with user or it fails Change By: Ivan Meredith 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-48027) Blue Ocean dashboard showing no Pipelines
Title: Message Title Ivan Meredith updated JENKINS-48027 Jenkins / JENKINS-48027 Blue Ocean dashboard showing no Pipelines Change By: Ivan Meredith 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-47655) Scrolling behaviour of streaming log
Title: Message Title Josh McDonald resolved as Duplicate Duped by (and fixed as) JENKINS-49929 Jenkins / JENKINS-47655 Scrolling behaviour of streaming log Change By: Josh McDonald 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 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-47655) Scrolling behaviour of streaming log
Title: Message Title Josh McDonald resolved as Duplicate Duped by (and fixed as) JENKINS-49929 Jenkins / JENKINS-47655 Scrolling behaviour of streaming log Change By: Josh McDonald 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 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-49929) Regression: Log fails to auto update in karaoke mode
Title: Message Title Josh McDonald updated JENKINS-49929 Fixed in master @ dd0959d4823a22c6d0eaffdcf19fbaa80fda84eb Jenkins / JENKINS-49929 Regression: Log fails to auto update in karaoke mode 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-28877) Bitbucket Plugin unable to parse Bitbucket webhook response json
Title: Message Title K C commented on JENKINS-28877 Re: Bitbucket Plugin unable to parse Bitbucket webhook response json We are using Bitbucket Server, Jenkins, and Bitbucket Plugin 1.1.8. On Bitbucket, we set up Post Webhook (with ending slash in URL), and checked "Pull request created" event. On Jenkins, project config, we set the Git clone url, and checked "Build when a change is pushed to BitBucket" and "Poll SCM". When creating a new Poll Request on Bitbucket, from the com.cloudbees.jenkins.plugins logger on Jenkins, we see JSON data logged by com.cloudbees.jenkins.plugins.BitbucketHookReceiver, but the corresponding Jenkins project is not triggered. Occasionally, we see success messages from com.cloudbees.jenkins.plugins.sshcredentials.impl.TrileadSSHPasswordAuthenticator, but we don't see any other logs. Any idea why? Thank you. 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-49971) hudson.Util.loadFile() has a race condition
Title: Message Title Daniel Trebbien commented on JENKINS-49971 Re: hudson.Util.loadFile() has a race condition https://github.com/jenkinsci/jenkins/pull/3225 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-49971) hudson.Util.loadFile() has a race condition
Title: Message Title Daniel Trebbien updated an issue Jenkins / JENKINS-49971 hudson.Util.loadFile() has a race condition Change By: Daniel Trebbien Issue Type: Improvement Bug 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-49971) hudson.Util.loadFile() has a race condition
Title: Message Title Daniel Trebbien created an issue Jenkins / JENKINS-49971 hudson.Util.loadFile() has a race condition Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-03-07 02:07 Priority: Minor Reporter: Daniel Trebbien Util.loadFile() first checks if the file exists via File.exists(). It then tries to open the file for reading. However, it is possible for the file to be deleted between the existence check and the file-open operation, in which case the method throws a FileNotFoundException rather than returning an empty string. Add Comment
[JIRA] (JENKINS-28119) Link to log of failed step
Title: Message Title Juan Pablo Bottinelli commented on JENKINS-28119 Re: Link to log of failed step Hi. Is this still being worked on? Thanks 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-32599) JENKINS_HOME/users/config.xml Results in Nameless User
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32599 Re: JENKINS_HOME/users/config.xml Results in Nameless User Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/User.java http://jenkins-ci.org/commit/jenkins/02eebecfab96fa9f9ef9844c7ebebad5fdb71c27 Log: Merge pull request #3317 from daniel-beck/JENKINS-32599 JENKINS-32599 Ignore misplaced users/config.xml file Compare: https://github.com/jenkinsci/jenkins/compare/7add30c02359...02eebecfab96 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-32599) JENKINS_HOME/users/config.xml Results in Nameless User
Title: Message Title SCM/JIRA link daemon commented on JENKINS-32599 Re: JENKINS_HOME/users/config.xml Results in Nameless User Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/model/User.java http://jenkins-ci.org/commit/jenkins/35a38f0ce69596f7aff2a4b3de14739d5cb78dbc Log: JENKINS-32599 Ignore misplaced users/config.xml file 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-49212) Windows sshInit.ps1 doesn't work on Windows Server Core
Title: Message Title Chenyang Liu resolved as Fixed Jenkins / JENKINS-49212 Windows sshInit.ps1 doesn't work on Windows Server Core Change By: Chenyang Liu Status: Open 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-49486) Approvers field doesn't expand variable in the build
Title: Message Title
Rick Liu edited a comment on JENKINS-49486
Re: Approvers field doesn't expand variable in the build
[~oleg_nenashev]Hi Oleg,If I want to develop this feature,what approach would you recommand?1. Try to bring in Token Macro plugin's {{TokenMacro.expandAll( build, listener, approval.name ) }}in File "*conditions/ManualCondition.java*" [Line118|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L118], [Line140|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L140]2.Or try something similar in File "*conditions/ParameterizedSelfPromotionCondition.java*"[Line49|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ParameterizedSelfPromotionCondition.java#L49] to use {{build.getBuildVariables()}} to cross-reference the variable
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 edited a comment on JENKINS-49486
Re: Approvers field doesn't expand variable in the build
[~oleg_nenashev]Hi Oleg,If I want to develop this feature,what approach would you recommand?1. Try to bring in Token Macro plugin's {{ TokenMacro.expandAll( build, listener, approval.name )}} in File "*conditions/ManualCondition.java*" [Line118|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L118], [Line140|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ManualCondition.java#L140]2.Or try something similar in File " * conditions/ParameterizedSelfPromotionCondition.java * "[Line49|https://github.com/jenkinsci/promoted-builds-plugin/blob/master/src/main/java/hudson/plugins/promoted_builds/conditions/ParameterizedSelfPromotionCondition.java#L49] to use {{ build.getBuildVariables() }} to cross-reference the variable
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-49451) [Logstash] Setting maxLines Parameter on logstashSend Causes Warning
Title: Message Title Jakub Bochenski resolved as Fixed Jenkins / JENKINS-49451 [Logstash] Setting maxLines Parameter on logstashSend Causes Warning Change By: Jakub Bochenski Status: Open Resolved Assignee: Jakub Bochenski Markus Winter 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-45240) Remove organization folders
Title: Message Title M Chon edited a comment on JENKINS-45240 Re: Remove organization folders I would like to be able to globally disable Github Organization Projects altogether. I do not want end users to be able to create a GO project, but still allow them to create Multibranch Pipeline projects. Should I file a separate bug for this request? E.g. If all 1000+ repos in my (GHE) org one day have a Jenkinsfile added to them, I do NOT want a job which starts scanning them and automatically building. 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-49970) After upgrade to 2.108 from 2.63, cli command didn't work anymore
Title: Message Title wgracelee closed an issue as Not A Defect It looks like when the command ran on master host (CentOS 5.11), it failed. But when it ran on other host (CentOS 5.6), it succeeded. Jenkins / JENKINS-49970 After upgrade to 2.108 from 2.63, cli command didn't work anymore Change By: wgracelee Status: Open Closed 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
[JIRA] (JENKINS-45240) Remove organization folders
Title: Message Title M Chon commented on JENKINS-45240 Re: Remove organization folders I would like to be able to globally disable Github Organization Projects altogether. I do not want end users to be able to create a GO project, but still allow them to create Multibranch Pipeline projects. Should I file a separate bug for this request? E.g. If all 1000+ repos in my org one day have a Jenkinsfile added to them, I do NOT want a job which starts scanning them and automatically building. 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-49970) After upgrade to 2.108 from 2.63, cli command didn't work anymore
Title: Message Title wgracelee created an issue Jenkins / JENKINS-49970 After upgrade to 2.108 from 2.63, cli command didn't work anymore Issue Type: Bug Assignee: Oliver Gondža Components: cli-commander-plugin Created: 2018-03-07 00:17 Environment: OS: CentOS 5.11 64b Browser: Priority: Critical Reporter: wgracelee this cli command used to work when we're using 2.68: -> java -Djavax.net.ssl.trustStore=/u/xbuild/.ssh/jenkins/jenkins3/keystore -Djavax.net.ssl.trustStorePassword=... -jar /share/pub/build/jenkins3/war/WEB-INF/jenkins-cli.jar -s https://jenkins3.eng.proofpoint.com -auth @/u/xbuild/.ssh/jenkins/jenkins3/.jenkins-cli help After upgrade to 2.108, we got the following error. Nothing was changed to the jenkins master. -> java -Djavax.net.ssl.trustStore=/u/xbuild/.ssh/jenkins/jenkins3/keystore -Djavax.net.ssl.trustStorePassword=... -jar /share/pub/build/jenkins3/war/WEB-INF/jenkins-cli.jar -s https://jenkins3.eng.proofpoint.com -auth @/u/xbuild/.ssh/jenkins/jenkins3/.jenkins-cli help java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:345) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:656) at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) at sun.net.NetworkClient.doConnect(NetworkClient.java:180) at sun.net.www.http.HttpClient.openServer(HttpClient.java:432) at
[JIRA] (JENKINS-49171) Jenkins Pipeline Documentation Readability
Title: Message Title Douglas Wooster commented on JENKINS-49171 Re: Jenkins Pipeline Documentation Readability This is one of the MAJOR barriers to entry for Pipelines. 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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Denys Digtiar edited a comment on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
[~hermain] As Mike and Jesse alluded to, the new Agent implementation was added which is based on the CLI {{ssh-agent}}. If you have a CLI available inside the docker container and use the `sshagent` inside the {{docker.inside()}} closure, your git clone should work. Looks Look for the message like "Exec ssh-agent (binary ssh-agent on a remote machine)" or any errors that mention {{ssh-agent}}
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 Oleg Nenashev Hi Oleg, If I want to develop this feature, what approach would you recommand? 1. Try to bring in Token Macro plugin's TokenMacro.expandAll( build, listener, approval.name ) in File "conditions/ManualCondition.java" Line118, Line140 2. Or try something similar in File "conditions/ParameterizedSelfPromotionCondition.java" Line49 to use build.getBuildVariables() to cross-reference the variable 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-49898) Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49898 Re: Cannot relativize 'src/it/projects' relatively to ... when using relative path for Invoker Plugin projectsDirectory Code changed in jenkins User: Cyrille Le Clerc Path: jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/publishers/InvokerRunsPublisher.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/FileUtils.java jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/util/XmlUtils.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/publishers/InvokerRunsPublisherTest.java jenkins-plugin/src/test/java/org/jenkinsci/plugins/pipeline/maven/util/FileUtilsTest.java jenkins-plugin/src/test/resources/org/jenkinsci/plugins/pipeline/maven/maven-spy-maven-invoker-plugin-integration-tests.xml http://jenkins-ci.org/commit/pipeline-maven-plugin/90d74744db7648aa5b01b47c868001bdac362511 Log: JENKINS-49898 maven-invoker-plugin add support for relative path in "reportsDirectory", "projectsDirectory" and "cloneProjectsTo" 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-36997) sshAgent {} inside docker.image().inside {} does not work with long project name
Title: Message Title
Dev Ops commented on JENKINS-36997
Re: sshAgent {} inside docker.image().inside {} does not work with long project name
Having exactly the same issue as Hermann Schweizer any explanation.
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-49969) aborting build may send multiple TERM signals
Title: Message Title Craig Sebenik created an issue Jenkins / JENKINS-49969 aborting build may send multiple TERM signals Issue Type: Bug Assignee: Unassigned Attachments: builder.py Components: core Created: 2018-03-06 22:57 Environment: OS: Docker container (jenkins/jenkins:lts) (2.73.3) Labels: abort Priority: Major Reporter: Craig Sebenik We have a custom Python script that handles building out software (and uploading artifacts). I recently added a signal handler for handling aborted jobs. But, I am seeing inconsistent signals being sent. It LOOKS like Jenkins is sometimes sending multiple TERM signals (after 1 second). Here are 2 outputs for the exact same job run about 10 minutes apart: Started by user craig Building in workspace /var/jenkins_home/jobs/test1/workspace [workspace] $ /bin/sh -xe /tmp/jenkins3014862914468653233.sh + /opt/tools/builder.py [DEBUG] MyBuilder (31) - 2 945 - Logger initialized: MyBuilder [DEBUG] MyBuilder (43) - 3 945 - Inside call. [INFO] MyBuilder (76) - 3 946 - my pid: 975 [INFO] MyBuilder (77) - 3 946 - process group: 7 [INFO] MyBuilder (79) - 3 946 - Sleeping for: 200 secs [WARNING] MyBuilder (57) - 38936 878 - Handling SIGTERM.
[JIRA] (JENKINS-49968) Core 2.110 is unable to select a branch source via the server dropdown
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-49968
Core 2.110 is unable to select a branch source via the server dropdown
Change By:
Karl Shultz
Summary:
Core 2.110 is unable to configure select a Bitbucket SCM branch source , but older versions can via the server dropdown
Priority:
Major Critical
Environment:
Jenkins core 2.110 Bitbucket ser Recommended plugins at install time
*Summary:*Starting with an empty directory for JENKINS_HOME, and running via {{java -jar jenkins.war}}, the ability to select a Bitbucket branch source for a multibranch pipeline doesn't work with core 2.110. But with core 2.109, it works fine.*Prerequisites:*Have a local Bitbucket server instance, running version 4.9.1 or a GitHub Enterprise instance , via the Atlassian SDK available . I This issue was doing this to help originally written up using Bitbucket server, but I've confirmed that it can be recreated with a customer case both Bitbucket and GitHub Enterprise .*Steps to recreate:*1. Download the 2.110 war2. Create an empty directory for your JENKINS_HOME, and export this as {{$JENKINS_HOME}}:{code:none}[kshultz@karl-fedora jenkinsWars]$ rm -rf ~/JENKINS_HOME/[kshultz@karl-fedora jenkinsWars]$ mkdir ~/JENKINS_HOME[kshultz@karl-fedora jenkinsWars]$ export JENKINS_HOME=~/JENKINS_HOME/{code}3. Go through the usual setup wizard, and choose to install suggested plugins.4. Once Jenkins is fully up and running, install bitbucket-branch-source from the Manage Plugins page. Have Jenkins reboot once installation is complete.5. Go to Manage Jenkins, and set up your Bitbucket server as follows: !image-2018-03-06-16-57-50-210.png|thumbnail! 6. Create a new Multibranch Pipeline project. Under Branch Sources, click the "Add Source" button, and select Bitbucket: !image-2018-03-06-17-00-16-320.png|thumbnail! 7. Click on the "Server" drop down. Nothing shows up - the drop down is inop. !image-2018-03-06-17-02-02-000.png|thumbnail! 8. Open your browser console and switch to the Network tab. Clear the console, reload the page, and try clicking on that drop down: !image-2018-03-06-17-05-53-668.png|thumbnail! {code:none}prototype.js:1794 XHR finished loading: POST "http://127.0.0.1:8080/$stapler/bound/4f662ac2-9cdb-49d6-bf21-975c41fe462e/render".request @ prototype.js:1794initialize @ prototype.js:1759(anonymous) @ prototype.js:470klass @ prototype.js:80proxy.(anonymous
[JIRA] (JENKINS-46336) Sidecar docker containers for declarative
Title: Message Title James Dumay commented on JENKINS-46336 Re: Sidecar docker containers for declarative Christopher Orr good eye Thank you! 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-41581) Declarative: Support for multiple docker agents run in parallel and communicating
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-41581 Declarative: Support for multiple docker agents run in parallel and communicating Change By: James Dumay 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 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-49968) Core 2.110 is unable to configure a Bitbucket SCM source, but older versions can
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-49968 Core 2.110 is unable to configure a Bitbucket SCM source, but older versions can Issue Type: Bug Assignee: Unassigned Attachments: 127.0.0.1.har, image-2018-03-06-16-57-50-210.png, image-2018-03-06-17-00-16-320.png, image-2018-03-06-17-02-02-000.png, image-2018-03-06-17-05-53-668.png Components: core Created: 2018-03-06 22:22 Environment: Jenkins core 2.110 Bitbucket ser Priority: Major Reporter: Karl Shultz Summary: Starting with an empty directory for JENKINS_HOME, and running via java -jar jenkins.war, the ability to select a Bitbucket branch source for a multibranch pipeline doesn't work with core 2.110. But with core 2.109, it works fine. Prerequisites: Have a local Bitbucket server instance, running version 4.9.1, via the Atlassian SDK. I was doing this to help with a customer case. Steps to recreate: 1. Download the 2.110 war 2. Create an empty directory for your JENKINS_HOME, and export this as $JENKINS_HOME: [kshultz@karl-fedora jenkinsWars]$ rm -rf ~/JENKINS_HOME/ [kshultz@karl-fedora jenkinsWars]$ mkdir ~/JENKINS_HOME [kshultz@karl-fedora jenkinsWars]$ export JENKINS_HOME=~/JENKINS_HOME/ 3. Go through the usual setup wizard, and choose to install suggested plugins. 4. Once
[JIRA] (JENKINS-49967) Expose the ability to use an existing p4 client (workspace)
Title: Message Title Jay Spang created an issue Jenkins / JENKINS-49967 Expose the ability to use an existing p4 client (workspace) Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2018-03-06 22:02 Priority: Minor Reporter: Jay Spang I have been using p4groovy with Jenkins pipelines for a while now, and this is becoming more and more cumbersome. In order to instantiate a p4 object (to run any sort of p4 command), you must define a workspace which p4groovy attempts to create. There doesn't seem to be a way (that I can tell) to just use an existing workspace. Here is an example of why this is cumbersome. I have a shared function called `get_latest_change()` which simply runs the command `p4 changes -m1 //depot/...`. This command doesn't need a workspace to run, but since p4groovy seems to require one, I have to manually instantiate a workspace and pass it into the function every time I want to call it (and I need to go to great pains to make sure the ws object I create matches the existing workspace so I don't accidentally change things). Add Comment
[JIRA] (JENKINS-49966) How to set parallel step results in Jenkins Pipeline?
Title: Message Title
Felyppe Rodrigues created an issue
Jenkins / JENKINS-49966
How to set parallel step results in Jenkins Pipeline?
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-03-06 21:58
Priority:
Minor
Reporter:
Felyppe Rodrigues
I'm running some tests with Jenkins Pipeline using parallelism and I noticed that Blue Ocean behaves weirdly with job results in parallel. I declared a Global Class with a variable to handle the current build status based on the parallel jobs results. It works, however the parallel steps status do not seem to be set correctly within the Blue Ocean UI. I prepared an example below to show what is going on. Here follows the pipeline definition:
pipeline {
stages {
stage('Tests') {
steps {
script {
parallel(
a: {
echo "This is branch a"
manager.build.@result = hudson.model.Result.SUCCESS
},
b: {
echo "This is branch b"
manager.build.@result = hudson.model.Result.ABORTED
},
c: {
echo "This is branch c"
manager.build.@result = hudson.model.Result.UNSTABLE
},
d: {
echo "This is branch d"
manager.build.@result = hudson.model.Result.FAILURE
try {sh "exit 1"}catch(e){echo 'failure'}
}
)
manager.build.@result = hudson.model.Result.UNSTABLE
}
}
}
}
}
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Christopher Orr commented on JENKINS-37123 Re: Support role based access Even if you define an IAM role, you still need to associate this with an IAM user, or otherwise get an access key and secret via STS, right? So in the end, the plugin would still be using an access key and secret; they'll just be short-lived — depending on how you called STS — and stop working at some point. Or what do you envision being implemented in this 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-49965) Slow performance of warnings table if there are 1000 elements
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-49965 Slow performance of warnings table if there are 1000 elements Issue Type: Bug Assignee: Ulli Hafner Components: analysis-core-plugin Created: 2018-03-06 21:53 Priority: Minor Reporter: Ulli Hafner 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
[JIRA] (JENKINS-49413) IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace
Title: Message Title Cyrille Le Clerc commented on JENKINS-49413 Re: IllegalArgumentException : Cannot relativize '...' relatively to ...' for artifacts stored outside of the workspace Jesús Lunar Pérez I think that your problem is, I have created JENKINS-46084 for your point. javydreamercsw I have discussed with Jesse Glick, a plugin cannot access to files that are outside of the workspace. It is a constraint "by design". Could you use a kind of "target" folder inside your workspace and maybe clean/delete this folder after your build? 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-49964) HOT Player throwing security exceptions
Title: Message Title jim woodlock created an issue Jenkins / JENKINS-49964 HOT Player throwing security exceptions Issue Type: Bug Assignee: Methodes Appliquees Arkea Components: openstack-heat-plugin Created: 2018-03-06 21:28 Environment: Jenkins 2.110, bouncycastle 2.16.2, command agent launcher 1.2 Priority: Blocker Reporter: jim woodlock The HOT Player no longer works, it throws 'Oops!' messages. The following trace is produced: java.lang.UnsupportedOperationException: Refusing to marshal net.sf.json.JSONObject for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:543) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) Caused: java.lang.RuntimeException: Failed to serialize com.arkea.jenkins.openstack.heat.orchestration.template.Parameter#defaultValue for class com.arkea.jenkins.openstack.heat.orchestration.template.Parameter at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at
[JIRA] (JENKINS-49963) Symbol lookup returns wrong result
Title: Message Title Daniel Spilker commented on JENKINS-49963 Re: Symbol lookup returns wrong result I think the problem is that MultiJobBuildSelector reuses a descriptor class rather than defining it's own. See https://github.com/jenkinsci/tikal-multijob-plugin/blob/jenkins-multijob-plugin-1.29/src/main/java/com/tikal/jenkins/plugins/multijob/MultiJobBuildSelector.java#L75-L79. SimpleBuildSelectorDescriptor is the base class for several descriptors in copyartifact. 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-49963) Symbol lookup returns wrong result
Title: Message Title Daniel Spilker assigned an issue to Jesse Glick Jenkins / JENKINS-49963 Symbol lookup returns wrong result Change By: Daniel Spilker Assignee: Kohsuke Kawaguchi Jesse Glick 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-49963) Symbol lookup returns wrong result
Title: Message Title Daniel Spilker created an issue Jenkins / JENKINS-49963 Symbol lookup returns wrong result Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: multijob-plugin, structs-plugin Created: 2018-03-06 21:25 Environment: core 2.107 structs 1.14 multijob 1.29 copyartifact 1.39 Priority: Major Reporter: Daniel Spilker Symbol lookup returns an descriptor for an rather unrelated class which not annotated with the given symbol name. When running the following code in Script Console, the same objects is printed each time. import org.jenkinsci.plugins.structs.SymbolLookup import hudson.plugins.copyartifact.StatusBuildSelector import com.tikal.jenkins.plugins.multijob.MultiJobBuildSelector def d1 = Jenkins.instance.getDescriptor(StatusBuildSelector) println SymbolLookup.get().find(d1.class, 'lastSuccessful') def d2 = Jenkins.instance.getDescriptor(MultiJobBuildSelector) println SymbolLookup.get().find(d2.class, 'lastSuccessful')
[JIRA] (JENKINS-42683) ci-game-plugin shall be usable from pipelines
Title: Message Title mirza zeyrek commented on JENKINS-42683 Re: ci-game-plugin shall be usable from pipelines wow! thank you very much. I'm using multibranch pipeline. Would your repository work on it ? And how can I install ? Thanks in advance Levente Fall 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-49306) Amazon EC2 fleet plugin does not allow setting minimum cluster size to '0'
Title: Message Title Christopher Orr closed an issue as Duplicate Closing in favour of the earlier instance of this bug with more watchers. I added a comment there about the workaround and a link to the PR. Jenkins / JENKINS-49306 Amazon EC2 fleet plugin does not allow setting minimum cluster size to '0' Change By: Christopher Orr Status: Open Closed 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 receiving
[JIRA] (JENKINS-42683) ci-game-plugin shall be usable from pipelines
Title: Message Title Levente Fall commented on JENKINS-42683 Re: ci-game-plugin shall be usable from pipelines I've added the pipeline support in this fork: https://github.com/peregin/ci-game-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-35438) Fleet always keeps at least one instance
Title: Message Title Christopher Orr commented on JENKINS-35438 Re: Fleet always keeps at least one instance Set the minimum cluster size to zero, and this will happen. The web UI will warn you about it needing to be a positive number, but it still works fine. See also https://github.com/jenkinsci/ec2-fleet-plugin/pull/19. 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-49962) P4 Plugin: The P4 client uses jenkins_home instead of workspace as root.
Title: Message Title
Chung Ley created an issue
Jenkins / JENKINS-49962
P4 Plugin: The P4 client uses jenkins_home instead of workspace as root.
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-03-06 21:00
Environment:
Jenkins 2.46.1, P4 Plug in 1.4.14
Priority:
Critical
Reporter:
Chung Ley
This is very strange and I hadn't been able to nail it yet since it happened inconsistently where sometimes the p4 plugin would essentially use the ${JENKINS_HOME} as the root and sometimes use the ${WORKSPACE} as the root (as far as I can tell)... The ${WORKSPACE} is what we wanted it to use. So, even within the same "job"; this will happen. Our Workspace Name within the Perforce Software is specified to be jenkins-pdkmfg-${JOBNAME}. If I looked at the console logs, or that I check the p4 client:
p4 client -o jenkins-pdkmfg-my_job_name
I would see the root defined as /proj/gde_pdk_scratch/jenkins/prod/p4/worksapce/my_job_name which is where our workspace is defined and which is what we wanted, but sometimes also as: /home/pdkmfg/tools/prod/jenkins_home which caused a lot of problems... Sometimes it would just fail; but on some occasion, our jenkins_home got wiped (I think that is because some of our jobs we set the Auto Clean or Force Sync.) What could cause P4 plugin to use JENKINS_HOME as root instead of WORKSPACE or if there is a way for me to make sure that it is using WORKSPACE. Thanks and Regards...
[JIRA] (JENKINS-49961) NPE from CpsFlowExecution.saveOwner
Title: Message Title Sam Van Oort started work on JENKINS-49961 Change By: Sam Van Oort 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-37341) Add support of z/OS USS to sh step
Title: Message Title Ramchand Venkatasamy updated an issue Jenkins / JENKINS-37341 Add support of z/OS USS to sh step Change By: Ramchand Venkatasamy We are going to use the pipeline plugin with build nodes running under z/OS Unix System Services (USS). Unfortunately, the sh step does not work out of the box on that platform because (text) files are encoded by default in IBM1047 (some EBCDIC variant) but the implementation within the durable-task-plugin seems to assume implicitly that the shell input and output is in UTF-8 or ASCII based.First experiments on top of durable-task-1.10 adding character set conversion in BourneShellScript and FileMonitoringTask to any read/write of files script.sh, pid, jenkins-result.txt and jenkins-log.txt were promising. Update : - the Script.sh file is untagged in z/OS USS , if its tagged as ASCII the script can be executed in z/OS USS. when the script is pushed it need to be tagged as ASCII. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You
[JIRA] (JENKINS-37341) Add support of z/OS USS to sh step
Title: Message Title Ramchand Venkatasamy assigned an issue to Unassigned Jenkins / JENKINS-37341 Add support of z/OS USS to sh step Change By: Ramchand Venkatasamy Priority: Minor Major Assignee: Lutz Neugebauer 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-49037) git clone does not retry if connection aborted
Title: Message Title Bart Bialek commented on JENKINS-49037 Re: git clone does not retry if connection aborted +1 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-49961) NPE from CpsFlowExecution.saveOwner
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-49961 NPE from CpsFlowExecution.saveOwner Change By: Jesse Glick Labels: regression 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-49961) NPE from CpsFlowExecution.saveOwner
Title: Message Title Jesse Glick commented on JENKINS-49961 Re: NPE from CpsFlowExecution.saveOwner The code seems wrong. WorkflowRun.onLoad sets the owner after calling setResumeBlocked. So of course it will throw an exception. 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-49908) allBuilds eagerly loads every build into memory before applying pagination
Title: Message Title Edward Yang commented on JENKINS-49908 Re: allBuilds eagerly loads every build into memory before applying pagination Thanks for confirming the issue. I am also curious: if I specify a "tree" parameter with a parameter that is only visible at depth=2 as opposed to depth=1, does Jenkins load all of "depth=2" into memory before applying the filter? I saw some empirical results which suggested this might be the case, although the signal was a bit weaker in this 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-49961) NPE from CpsFlowExecution.saveOwner
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-49961 NPE from CpsFlowExecution.saveOwner Issue Type: Bug Assignee: Sam Van Oort Components: workflow-cps-plugin Created: 2018-03-06 20:02 Priority: Minor Reporter: Jesse Glick Trunk build of Jenkins, latest plugins: java.lang.NullPointerException at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.saveOwner(CpsFlowExecution.java:1754) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.setResumeBlocked(CpsFlowExecution.java:348) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:633) at ... after restarting when there was a build of a project which I marked not for resumption. Add Comment
[JIRA] (JENKINS-49451) [Logstash] Setting maxLines Parameter on logstashSend Causes Warning
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49451 Re: [Logstash] Setting maxLines Parameter on logstashSend Causes Warning Code changed in jenkins User: Markus Winter Path: src/main/java/jenkins/plugins/logstash/LogstashNotifier.java src/main/resources/jenkins/plugins/logstash/LogstashNotifier/config.jelly http://jenkins-ci.org/commit/logstash-plugin/9dbdbba9aab1ed5ca8c295ecfcd6a40f45689f2b Log: JENKINS-49451 Fix logstash Notifier setp (#53) JENKINS-49451 add getters for fields we need getters for the fields so the UI can properly work with them add check for valid integer add clazz number which auto checks for integer 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-40997) Add way to get locked resource name in pipeline
Title: Message Title Antonio Muñiz commented on JENKINS-40997 Re: Add way to get locked resource name in pipeline Released as 2.2 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-49734) Use PauseAction while acquiring lock
Title: Message Title Antonio Muñiz resolved as Fixed Released as 2.2 Jenkins / JENKINS-49734 Use PauseAction while acquiring lock Change By: Antonio Muñiz Status: Open 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-43574) Lockable resources plugin does not take effect
Title: Message Title Antonio Muñiz resolved as Fixed Released as 2.2 Jenkins / JENKINS-43574 Lockable resources plugin does not take effect Change By: Antonio Muñiz Status: Open 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-49960) JobProperty instead of BuildWrapper
Title: Message Title Markus Winter updated an issue Jenkins / JENKINS-49960 JobProperty instead of BuildWrapper Change By: Markus Winter Summary: JobProperty instread instead of BuildWrapper 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-49960) JobProperty instread of BuildWrapper
Title: Message Title Markus Winter created an issue Jenkins / JENKINS-49960 JobProperty instread of BuildWrapper Issue Type: Improvement Assignee: Jakub Bochenski Components: logstash-plugin Created: 2018-03-06 19:34 Priority: Minor Reporter: Markus Winter With the conversion from a BuildWrapper to a ConsoleLogFilter the BuildWrapper is only used as a marker to indicate that we want to send data. A JobProperty would be the better place for this information. What needs to be checked is if we can automatically merged from BuildWrapper to JobProperty (at job loading or at first run maybe) Add Comment
[JIRA] (JENKINS-41822) msbuild warning parser with NullPointerExcetpion
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-41822 msbuild warning parser with NullPointerExcetpion Change By: Michael Fowler Component/s: warnings-plugin Component/s: msbuild-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-43356) MSBuild command fails in Jenkinsfile
Title: Message Title Michael Fowler updated an issue Jenkins / JENKINS-43356 MSBuild command fails in Jenkinsfile Change By: Michael Fowler Labels: msbuild 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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Devin Nusbaum commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Andrew Barnish To confirm, you are only seeing the error when users attempt to configure folders, but not jobs or nodes, right? 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-35422) Valgrind plugin failed to parse (String index out of range) for complex C++ trace.
Title: Message Title Johannes Ohlemacher closed an issue as Fixed Jenkins / JENKINS-35422 Valgrind plugin failed to parse (String index out of range) for complex C++ trace. Change By: Johannes Ohlemacher 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-49959) ownership-plugin 0.12.0 breaks creating new job from existing job
Title: Message Title Oleg Nenashev commented on JENKINS-49959 Re: ownership-plugin 0.12.0 breaks creating new job from existing job Yes, the logic needs to be 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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Oleg Nenashev started work on JENKINS-49744 Change By: Oleg Nenashev 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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Oleg Nenashev commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API will try to ship 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-43574) Lockable resources plugin does not take effect
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43574 Re: Lockable resources plugin does not take effect Code changed in jenkins User: Antonio Muniz Path: src/main/java/org/jenkins/plugins/lockableresources/RequiredResourcesProperty.java src/test/java/org/jenkins/plugins/lockableresources/BasicIntegrationTest.java http://jenkins-ci.org/commit/lockable-resources-plugin/67a01b44f4a995955e0888db62f927fcc740697a Log: Merge pull request #89 from krulls/master JENKINS-43574: fix construction of RequiredResourcesProperty Compare: https://github.com/jenkinsci/lockable-resources-plugin/compare/3b9717e389f7...67a01b44f4a9 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-43574) Lockable resources plugin does not take effect
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43574 Re: Lockable resources plugin does not take effect Code changed in jenkins User: krull Path: src/main/java/org/jenkins/plugins/lockableresources/RequiredResourcesProperty.java http://jenkins-ci.org/commit/lockable-resources-plugin/90bee03e8972183210ca5510f4e276bc8097cdb7 Log: JENKINS-43574: replace whitespaces with tabs 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-43574) Lockable resources plugin does not take effect
Title: Message Title SCM/JIRA link daemon commented on JENKINS-43574 Re: Lockable resources plugin does not take effect Code changed in jenkins User: krull Path: src/main/java/org/jenkins/plugins/lockableresources/RequiredResourcesProperty.java src/test/java/org/jenkins/plugins/lockableresources/BasicIntegrationTest.java http://jenkins-ci.org/commit/lockable-resources-plugin/1e440bfbbd803400065c062ae6bba9b86a7e45ac Log: JENKINS-43574: fix construction of RequiredResourcesProperty 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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Andrew Barnish commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API We are seeing the same problem when copying a job using Jenkins Web interface as we get a stack trace for users who have manage ownership but no admin permission. the stacktrace includes messages like: Caused: com.thoughtworks.xstream.converters.reflection.ObjectAccessException: Could not call com.synopsys.arc.jenkins.plugins.ownership.OwnershipDescription.readResolve() : is missing the Overall/Administer permission I can provide the full stacktrace if necessary. 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-49836) Cannot view Console logs
Title: Message Title Tomasz Wojtun assigned an issue to Oleg Nenashev Jenkins / JENKINS-49836 Cannot view Console logs Change By: Tomasz Wojtun Assignee: Oleg Nenashev 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-49958) random jenkins IO failure
Title: Message Title yacoub hossain assigned an issue to Kohsuke Kawaguchi wasn't sure who to assign to Jenkins / JENKINS-49958 random jenkins IO failure Change By: yacoub hossain Assignee: Kohsuke Kawaguchi 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-49959) ownership-plugin 0.12.0 breaks creating new job from existing job
Title: Message Title Curtis Ruck created an issue Jenkins / JENKINS-49959 ownership-plugin 0.12.0 breaks creating new job from existing job Issue Type: Bug Assignee: Oleg Nenashev Components: ownership-plugin Created: 2018-03-06 19:01 Priority: Critical Reporter: Curtis Ruck On a system with ownership-plugin 0.12.0, when trying to create a new job from an existing job, we receive "java.io.InvalidObjectException: ruckc is missing the Overall/Administer permission" when on the job, the ruckc user has inherited the permissions from the parent ACL. If ruckc gets the Manage Ownership permission directly, the issue isn't present. It appears that the Ownership permission checks need to pull job permissions and adhere to inherited permissions also. Add Comment
[JIRA] (JENKINS-24463) PyLint parse missing errors
Title: Message Title
Scott Schreckengaust commented on JENKINS-24463
Re: PyLint parse missing errors
based on Ulli Hafner's reference of Łukasz Dudek above, here is the message format, pylint command, Pipeline step and console output that worked for Jenkins to report pylint messages through the Warnings plugin: ./pylintrc contains:
msg-template={path}:{line}: [{msg_id}, {obj}] {msg} ({symbol})
Command:
pylint --rcfile=./pylintrc CODE > pylint.log
Pipeline:
step([$class: 'WarningsPublisher',
parserConfigurations: [[
parserName: 'PyLint', pattern: '**/pylint*.log'
]],
unstableTotalAll: '0',
usePreviousBuildAsReference: true
])
Console:
[WARNINGS] Parsing warnings in files '**/pylint-*.log' with parser PyLint
[WARNINGS] Searching for all files in WORKSPACE that match the pattern **/pylint-*.log
[WARNINGS] Parsing 1 file in WORKSPACE
[WARNINGS] Successfully parsed file WORKSPACE/pylint-py36.log with 2 unique warnings and 0 duplicates.
Add Comment
[JIRA] (JENKINS-34643) New release
Title: Message Title Johannes Ohlemacher closed an issue as Fixed Jenkins / JENKINS-34643 New release Change By: Johannes Ohlemacher 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-34981) Make valgrind-plugin compatible with pipeline
Title: Message Title Johannes Ohlemacher resolved as Fixed added pipeline support with version 0,28, thx Wulkop! Jenkins / JENKINS-34981 Make valgrind-plugin compatible with pipeline Change By: Johannes Ohlemacher 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
[JIRA] (JENKINS-34981) Make valgrind-plugin compatible with pipeline
Title: Message Title Johannes Ohlemacher started work on JENKINS-34981 Change By: Johannes Ohlemacher 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-49958) random jenkins IO failure
Title: Message Title yacoub hossain created an issue Jenkins / JENKINS-49958 random jenkins IO failure Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-03-06 18:13 Environment: Jenkins Master 2.89.4 windows host, issue happens on os x slave Priority: Blocker Reporter: yacoub hossain i get these random failures, seeming due to IO issues and seemingly coonfined to OS X machines. Here is an example stack; (I checked, and the file it seems to be complaining about "/Users/asm_qa/jf/workspace/dr64@tmp/secretFiles/f7e1d980-45c5-4350-b77c-a697c022f422" does exist on that slave.) please HELP! java.nio.channels.ClosedChannelException at org.jenkinsci.remoting.protocol.NetworkLayer.onRecvClosed(NetworkLayer.java:154) at org.jenkinsci.remoting.protocol.impl.NIONetworkLayer.ready(NIONetworkLayer.java:179) at org.jenkinsci.remoting.protocol.IOHub$OnReady.run(IOHub.java:721) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) Caused: hudson.remoting.ChannelClosedException: Remote call on JNLP4-connect connection from camac1.ads.autodesk.com/10.146.47.76:49613 failed. The channel is closing down or has closed down at hudson.remoting.Channel.call(Channel.java:901) at hudson.FilePath.act(FilePath.java:986) Caused: java.io.IOException: remote file operation failed: /Users/asm_qa/jf/workspace/dr64@tmp/secretFiles/f7e1d980-45c5-4350-b77c-a697c022f422 at hudson.remoting.Channel@4df50645:JNLP4-connect connection from camac1.ads.autodesk.com/10.146.47.76:49613 at hudson.FilePath.act(FilePath.java:993) at hudson.FilePath.act(FilePath.java:975) at hudson.FilePath.deleteRecursive(FilePath.java:1177) at org.jenkinsci.plugins.credentialsbinding.impl.UnbindableDir$UnbinderImpl.unbind(UnbindableDir.java:84) at
[JIRA] (JENKINS-25519) NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check problems
Title: Message Title Sam Van Oort closed an issue as Fixed Released with v.1.19 Jenkins / JENKINS-25519 NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check problems Change By: Sam Van Oort Status: Resolved Closed 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
[JIRA] (JENKINS-42683) ci-game-plugin shall be usable from pipelines
Title: Message Title mirza zeyrek commented on JENKINS-42683 Re: ci-game-plugin shall be usable from pipelines Any progress on this 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-49957) [Regression] Remove prefix and remote directory are not persisted anymore
Title: Message Title Nikolas Falco closed an issue as Fixed Jenkins / JENKINS-49957 [Regression] Remove prefix and remote directory are not persisted anymore Change By: Nikolas Falco 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-49957) [Regression] Remove prefix and remote directory are not persisted anymore
Title: Message Title
Nikolas Falco commented on JENKINS-49957
Re: [Regression] Remove prefix and remote directory are not persisted anymore
I had also try with pipeline without luck. The removePrefix is ignored.
stage('Deploy') {
sshPublisher(publishers:
[sshPublisherDesc(
configName: 'machine01.acme.com',
transfers: [
sshTransfer(execCommand: '', sourceFiles: 'target/*.tar.gz, target/db/**/*', removePrefix: 'target', remoteDirectorySDF: '~'),
sshTransfer(execCommand: 'cd ~;chmod +x *.sh;./deploy.sh', sourceFiles: 'scripts/*', removePrefix: 'scripts', remoteDirectorySDF: '~')
])]
)
}
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-49957) [Regression] Remove prefix and remote directory are not persisted anymore
Title: Message Title Nikolas Falco created an issue Jenkins / JENKINS-49957 [Regression] Remove prefix and remote directory are not persisted anymore Issue Type: Bug Assignee: Alex Earl Components: publish-over-ssh-plugin Created: 2018-03-06 17:26 Environment: Jenkins 2.89.4, Publish Over SSH 1.19 Priority: Critical Reporter: Nikolas Falco I have a freestyle job that publish over SSH some artifacts using "remove prefix" and "remote directory" valued. With the plugin version 1.17 it works great. Updating to 1.19 everytime I edit the job configuration both fields are empty also if valued (are not persistend on save) and subsequently any run fails. Before: "publish-over-ssh@1.17"> SSH: machine01.acme.com false build target/*.tar.gz,wealth/target/db/**/* target false false false false false [, ]+ 12 false false false false After: "publish-over-ssh@1.19"> SSH: "publish-over@0.21"> "publish-over-ssh@1.19"> machine01.acme.com false
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title Matthew Ludlum started work on JENKINS-42582 Change By: Matthew Ludlum Status: Reopened 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-25519) NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check problems
Title: Message Title Sam Van Oort commented on JENKINS-25519 Re: NumberFormatException from exitStatus can cause DurableTaskStep.Execution.check problems Root case turned out to be that the statusCode file was created before being written to, and could be checked while empty. 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-49954) sh inside container closure waits up to 1 minute
Title: Message Title Carlos Sanchez commented on JENKINS-49954 Re: sh inside container closure waits up to 1 minute Have you tried increasing "Max connections to Kubernetes API" in configuration? 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.
