[JIRA] (JENKINS-50033) Method code too large using declarative pipelines
Title: Message Title
Ruud P created an issue
Jenkins / JENKINS-50033
Method code too large using declarative pipelines
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
_unsorted
Created:
2018-03-09 07:58
Labels:
pipeline
Priority:
Major
Reporter:
Ruud P
i got the error below when i use a lot of parallel stages , this error disappear when i just fill in a few parallel stages but of course that will not work for us. has anyone a work a round for this? we use declarative pipelines, how can i make the method shorter as i cant use dynamic stages with declarative pipelines stages { stage('Test') { parallel { stage('1') { when {_expression_ bla1}} steps {node(label: 'bla') {test('bla1', '')}}} stage('2') { when {_expression_ bla2}} steps {node(label: 'bla') {test('bla2', '')}}} stage('3') { when {_expression_ bla1}} steps {node(label: 'bla') {test('bla3', '')}}} stage(bla4') { when {_expression_ bla3}} steps {node(label: 'bla') {test('bla4', '')}}} . more as 200 Notified JIRA that a build has completed. org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! java.lang.RuntimeException: Method code too large! at groovyjarjarasm.asm.MethodWriter.a(Unknown Source) at groovyjarjarasm.asm.ClassWriter.toByteArray(Unknown Source) at org.codehaus.groovy.control.CompilationUnit$17.call(CompilationUnit.java:827) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1065) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at
[JIRA] (JENKINS-49696) Delete and re-create view if type changes
Title: Message Title Petres Andras updated an issue Jenkins / JENKINS-49696 Delete and re-create view if type changes Change By: Petres Andras Summary: Add option to delete views before Delete and re- creating them create view if type changes Job DSL does not allow for view type to be changed, throwing an exception when this is attempted. The workaround is deleting the view manually before running the seed job. It would be much nicer if the deletion would be done automatically. I A solution would like be to have an option in the plugin which forces the deletion of always delete and re-create views before regeneration when type changes . When that option (checkbox?) is checked, job-dsl-plugin deletes the view right after if detects that a view with the same name exists and creates it again instead of updating it. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-21248) Add shallow update init for submodule
Title: Message Title Fujii Hironori commented on JENKINS-21248 Re: Add shallow update init for submodule Pull request: https://github.com/jenkinsci/git-client-plugin/pull/303 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-50032) Jobs can be triggered with only Job/Read and Job/Configure
Title: Message Title Joshua Shinn updated an issue Jenkins / JENKINS-50032 Jobs can be triggered with only Job/Read and Job/Configure Change By: Joshua Shinn Summary: Jobs can be triggered with only Job/Read and Job/Configure 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-50032) Jobs can be triggered with only Job/Read
Title: Message Title Joshua Shinn created an issue Jenkins / JENKINS-50032 Jobs can be triggered with only Job/Read Issue Type: Bug Assignee: Unassigned Components: parameterized-trigger-plugin Created: 2018-03-09 04:13 Environment: Parameterized trigger plugin 2.35.2, CloudBees Role-Based Access Control Plugin 5.9 Labels: security Priority: Major Reporter: Joshua Shinn Create a job and assign an Authentication Token under Trigger builds remotely (e.g., from scripts) Create a user and only assign Job/Read and Job/Configure permission for this job. Navigate to the job as the newly created user, retrieve the build URL which contains the token. The user cannot build this job via the UI. Retrive the user's API token ($JENKINS_URL/users/$USERNAME) Go to command line and use the following curl command: curl -X POST $JENKINS_URL/job/$JOB_NAME/build?token\=$AUTHENTICATION_TOKEN -u $USER_NAME:$API_TOKEN The job will be now be built.
[JIRA] (TEST-110) test1
Title: Message Title NARAYAN IYER created an issue test / TEST-110 test1 Issue Type: Task Assignee: Kohsuke Kawaguchi Components: test2 Created: 2018-03-09 02:46 Priority: Minor Reporter: NARAYAN IYER 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
[JIRA] (JENKINS-50020) CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
Title: Message Title Andrew Bayer commented on JENKINS-50020 Re: CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage Alrightie, I’ll dig tomorrow. 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-50020) CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-50020 CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage Change By: Andrew Bayer Assignee: Sam Van Oort 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-50020) CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
Title: Message Title Sam Van Oort commented on JENKINS-50020 Re: CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage Andrew Bayer Unlikely, probably a serialization error. 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-50031) Ansible Tower 3.3 removes authtoken from API
Title: Message Title Francois Herbert created an issue Jenkins / JENKINS-50031 Ansible Tower 3.3 removes authtoken from API Issue Type: Bug Assignee: John Westcott Components: ansible-tower-plugin Created: 2018-03-09 01:39 Priority: Major Reporter: Francois Herbert Authtoken support has been removed from awx (and tower from version 3.3) so this plugin no longer authenticates when running this new version. More info regarding this change is here https://github.com/ansible/awx/blob/devel/docs/auth/session.md Add Comment
[JIRA] (JENKINS-50030) Job.getEstimatedDurationCandidates should not force loading of builds
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50030 Job.getEstimatedDurationCandidates should not force loading of builds Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-03-09 01:05 Labels: lazy-loading performance pipeline Priority: Major Reporter: Jesse Glick View/index.jelly View/sidepanel.jelly ExecutorStepExecution/PlaceholderTask/PlaceholderExecutable/executorCell.jelly has been observed to trigger build loading: at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:67) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:430) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.loadProgramAsync(CpsFlowExecution.java:527) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad(CpsFlowExecution.java:502) at org.jenkinsci.plugins.workflow.job.WorkflowRun.onLoad(WorkflowRun.java:568) at hudson.model.RunMap.retrieve(RunMap.java:224) at hudson.model.RunMap.retrieve(RunMap.java:56) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:500) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:482) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:380) - locked <...> (a hudson.model.RunMap) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:345) at jenkins.model.lazy.AbstractLazyLoadRunMap.newestBuild(AbstractLazyLoadRunMap.java:275) at
[JIRA] (JENKINS-49486) Approvers field doesn't expand variable in the build
Title: Message Title Rick Liu updated an issue Jenkins / JENKINS-49486 Approvers field doesn't expand variable in the build Change By: Rick Liu Comment: [~samsun387]test 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 Kevin Yu test 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 updated an issue
Jenkins / JENKINS-49486
Approvers field doesn't expand variable in the build
Change By:
Rick Liu
Comment:
[~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
[JIRA] (JENKINS-49942) Pending script approvals even though signatures are approved
Title: Message Title Aswini Vayyala commented on JENKINS-49942 Re: Pending script approvals even though signatures are approved Hi, I got this to working after '-Dhudson.model.ParametersAction.keepUndefinedParameters=no_security' in JAVA_OPTS as mentioned in https://wiki.jenkins.io/display/JENKINS/Permissive+Script+Security+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-49942) Pending script approvals even though signatures are approved
Title: Message Title Aswini Vayyala edited a comment on JENKINS-49942 Re: Pending script approvals even though signatures are approved Hi, I got this to working after updating '-Dhudson.model.ParametersAction.keepUndefinedParameters=no_security' in JAVA_OPTS as mentioned in [https://wiki.jenkins.io/display/JENKINS/Permissive+Script+Security+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-50020) CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
Title: Message Title Andrew Bayer assigned an issue to Sam Van Oort Sam Van Oort - looks like this might be touching stuff in the storage changes? Jenkins / JENKINS-50020 CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage 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-50007) cannot be cast to hudson.scm.SVNRevisionState
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-50007 cannot be cast to hudson.scm.SVNRevisionState Change By: Andrew Bayer Component/s: subversion-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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ellinor Crux edited a comment on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have had this same issue in Jenkins version 2.109 , violations version 0.7.11 with Freestyle jobs. I've looked at the thread dump for projects that I couldn't load and saw this: !image-2018-03-08-15-26-46-035.png|width=1222,height=149!It appears to be stuck loading something with the violations plugin. This appears to affect all the freestyle jobs that use the violations plugin on my server. 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-49174) Declarative Pipeline: GIT_* have the value 'null' when using "agent none"
Title: Message Title Andrew Bayer commented on JENKINS-49174 Re: Declarative Pipeline: GIT_* have the value 'null' when using "agent none" I'm honestly not sure where this would go in the docs? 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-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title Andrew Bayer resolved as Duplicate Jenkins / JENKINS-49662 Ability to create custom stages in parallel blocks in pipeline shared library Change By: Andrew Bayer 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-49893) Declarative directive snippet generator
Title: Message Title Andrew Bayer updated JENKINS-49893 Jenkins / JENKINS-49893 Declarative directive snippet generator 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ellinor Crux commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 I have had this same issue in Jenkins version 2.109 with Freestyle jobs. I've looked at the thread dump for projects that I couldn't load and saw this: It appears to be stuck loading something with the violations plugin. This appears to affect all the freestyle jobs that use the violations plugin on my server. 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-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title Ellinor Crux updated an issue Jenkins / JENKINS-49630 Unable to view configuration of some projects after upgrade to 2.107 Change By: Ellinor Crux Attachment: image-2018-03-08-15-26-46-035.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-46229) Support cyclomatic complexity entry point
Title: Message Title Andrew Bayer resolved as Won't Fix So I don't actually think this'd provide much value, so I'm closing this as won't fix. Jenkins / JENKINS-46229 Support cyclomatic complexity entry point Change By: Andrew Bayer Status: Open Resolved Resolution: Won't 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,
[JIRA] (JENKINS-48455) Documentation missing for Declarative dockerfile agent with alternative Dockerfile name
Title: Message Title Andrew Bayer updated JENKINS-48455 Jenkins / JENKINS-48455 Documentation missing for Declarative dockerfile agent with alternative Dockerfile name Change By: Andrew Bayer 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-48612) Inconsistent Environment Variable interpolation in Declarative k8s agent
Title: Message Title Andrew Bayer assigned an issue to Unassigned Jenkins / JENKINS-48612 Inconsistent Environment Variable interpolation in Declarative k8s agent 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-48612) Inconsistent Environment Variable interpolation in Declarative k8s agent
Title: Message Title Andrew Bayer updated an issue Jenkins / JENKINS-48612 Inconsistent Environment Variable interpolation in Declarative k8s agent Change By: Andrew Bayer Component/s: pipeline-model-definition-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-48612) Inconsistent Environment Variable interpolation in Declarative k8s agent
Title: Message Title Andrew Bayer commented on JENKINS-48612 Re: Inconsistent Environment Variable interpolation in Declarative k8s agent This is something specific to the kubernetes Declarative agent, so I'm removing pipeline-model-definition-plugin from the components. 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-49714) Set skipDefaultCheckout to false when using lightweight checkout for Jenkinsfile
Title: Message Title Andrew Bayer resolved as Won't Fix skipDefaultCheckout is unrelated to lightweight checkouts - it's for when you're entering an agent, while lightweight checkouts are run on the master in order to get the Jenkinsfile in the first place. Jenkins / JENKINS-49714 Set skipDefaultCheckout to false when using lightweight checkout for Jenkinsfile Change By: Andrew Bayer Status: Open Resolved Resolution: Won't 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"
[JIRA] (JENKINS-49643) java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79
Title: Message Title Andrew Bayer resolved as Not A Defect Jenkins / JENKINS-49643 java.lang.AbstractMethodError: org.jenkinsci.plugins.pipeline.modeldefinition.validator.ModelValidatorImpl.validateElement from Jenkins 2.79 Change By: Andrew Bayer 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49976 Re: Serialization of ModelASTValue$1 / $2 Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTValue.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/ece602dbe1af2e7c0930e36d610f8147c6bb03ac Log: [FIXED JENKINS-49976] Get rid of ModelASTValue anonymous classes 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-49976) Serialization of ModelASTValue$1 / $2
Title: Message Title Andrew Bayer updated JENKINS-49976 Merged, this'll be in Declarative 1.2.8. Jenkins / JENKINS-49976 Serialization of ModelASTValue$1 / $2 Change By: Andrew Bayer 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-50006) Kubernetes agent max number of instances no longer working
Title: Message Title Rong Shen updated an issue Jenkins / JENKINS-50006 Kubernetes agent max number of instances no longer working Change By: Rong Shen Priority: Minor Trivial 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 Rong Shen updated an issue Jenkins / JENKINS-50006 Kubernetes agent max number of instances no longer working Change By: Rong Shen Priority: Major 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-50006) Kubernetes agent max number of instances no longer working
Title: Message Title Rong Shen commented on JENKINS-50006 Re: Kubernetes agent max number of instances no longer working I have not. Version 1.3.2 did not show up in Jenkins Update Center. Probably because we are using CJT instead of regular Jenkins. I think I'll have to manual check, that will take me some time because I don't want to interfere daily testing jobs. Let me change the priority level so I can have more time to test. 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-44989) Updating JIRA-issues deadlock
Title: Message Title
Thomson Tat commented on JENKINS-44989
Re: Updating JIRA-issues deadlock
It looks like it's a combination of two things that's causing this bug. There's a bug that's causing Jenkins to see changes to it's dependencies even though there aren't any. This seems random for us. And I'm not sure how or why it thinks there's a dependency on itself? https://issues.jenkins-ci.org/browse/JENKINS-46995 i.e. Job A #300 has dependency changes in Job A #290-299. Job A #290 has dependency changes in Job A #275-289 The DefaultIssueSelector looks at all of these dependencies, which can take a really long time to finish. This recursive call doesn't have any limit on how far down the dependencies it's looking. This can end up being hundreds of builds down the chain. https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/selector/DefaultIssueSelector.java#L110 https://github.com/jenkinsci/jira-plugin/blob/master/src/main/java/hudson/plugins/jira/selector/DefaultIssueSelector.java#L135 It looks like it's a bug in the refactoring of the original issue selector. https://github.com/jenkinsci/jira-plugin/commit/2eace064c77979cab041e61d82dea47eb44cc886#diff-e381acd1474876247543cc9edc4ea09e As far as I can tell, the original code (roughly) looks like this:
findIssueIdsRecursive()
{
findIssues()
for each in dependency
findIssues()
// findIssueIdsRecursive is not called again
}
The refactoring changed it to roughly this:
addIssuesRecursive()
{
addIssuesCarriedOverFromPreviousBuild()
addIssuesFromCurrentBuild()
addIssuesFromDependentBuilds()
}
addIssuesFromDependentBuilds()
{
for each in dependency
// Looking at dependent builds of this build, along with all of its dependent builds
addIssuesRecursive()
}
When we're running into this problem, it looks like a deadlock, but it's actually just taking hours instead of minutes like it normally does. Those spikes are probably when no one noticed on our team and it finished. The smaller spikes are probably when someone noticed and we had to manually abort the thread, thinking the plugin deadlocked again.
Add Comment
[JIRA] (JENKINS-44989) Updating JIRA-issues deadlock
Title: Message Title Thomson Tat updated an issue Jenkins / JENKINS-44989 Updating JIRA-issues deadlock Change By: Thomson Tat Attachment: image-2018-03-08-14-32-54-776.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-50029) Powershell treats warnings as errors
Title: Message Title Wouter Slob commented on JENKINS-50029 Re: Powershell treats warnings as errors Thnx Sam Van Oort & Gabriel Loewen for prompt response and explanation. I'm looking forward to testing the upcoming patch. I'm not sure if it is related to the same plugin, but yesterday I've created another issue: JENKINS-49986. You might want to have a quick look at that 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-49986) Pipeline 'bat' hangs on ws with forward slash path separator
Title: Message Title Wouter Slob commented on JENKINS-49986 Re: Pipeline 'bat' hangs on ws with forward slash path separator After installing today's updates I'm now getting a NullPointerException on the first bat from my example. Output: java.lang.NullPointerException at hudson.FilePath.sibling(FilePath.java:1258) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.tempDir(FileMonitoringTask.java:237) at org.jenkinsci.plugins.durabletask.FileMonitoringTask$FileMonitoringController.(FileMonitoringTask.java:121) at org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.(WindowsBatchScript.java:94) at org.jenkinsci.plugins.durabletask.WindowsBatchScript$BatchController.(WindowsBatchScript.java:92) at org.jenkinsci.plugins.durabletask.WindowsBatchScript.doLaunch(WindowsBatchScript.java:60) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launchWithCookie(FileMonitoringTask.java:76) at org.jenkinsci.plugins.durabletask.FileMonitoringTask.launch(FileMonitoringTask.java:71) at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.start(DurableTaskStep.java:176) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:229) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:153) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:108) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:810) at groovy.lang.GroovyObjectSupport.invokeMethod(GroovyObjectSupport.java:46) at groovy.lang.MetaClassImpl.invokeMethodOnGroovyObject(MetaClassImpl.java:1278) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1172) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:48) at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:113) at com.cloudbees.groovy.cps.sandbox.DefaultInvoker.methodCall(DefaultInvoker.java:19) at WorkflowScript.run(WorkflowScript:16) at __cps.transform__(Native Method) at com.cloudbees.groovy.cps.impl.ContinuationGroup.methodCall(ContinuationGroup.java:57) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.dispatchOrArg(FunctionCallBlock.java:109) at com.cloudbees.groovy.cps.impl.FunctionCallBlock$ContinuationImpl.fixArg(FunctionCallBlock.java:82) at sun.reflect.GeneratedMethodAccessor299.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:83) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:174) at com.cloudbees.groovy.cps.Continuable$1.call(Continuable.java:163) at org.codehaus.groovy.runtime.GroovyCategorySupport$ThreadCategoryInfo.use(GroovyCategorySupport.java:122) at org.codehaus.groovy.runtime.GroovyCategorySupport.use(GroovyCategorySupport.java:261) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:163) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:174) at
[JIRA] (JENKINS-50022) Run parameter behaves differently between input step and job parameter
Title: Message Title
James Hogarth updated an issue
Jenkins / JENKINS-50022
Run parameter behaves differently between input step and job parameter
Change By:
James Hogarth
When -- - JENKINS-27295-- - was implemented there was a specific serialisation check in place that blocked RunParamaterValue from adding to the params array that provides access to the real object, rather than a string representation of it.On some recent testing if an input step is used to request a build be selected: {noformat} wah = input message: '', parameters: [run(description: '', filter: 'SUCCESSFUL', name: '', projectName: 'cme/example_02_artefact/master')]{noformat}Then the object returned is the Run object that you can then do getDisplayName or getDescription on ... If instead of an input step a build parameter is used: {noformat}properties([parameters([run(description: 'Select the version of the artifact to deploy', filter: 'SUCCESSFUL', name: 'deploy_artifact', projectName: 'cme/example_02_artefact/master')])]){noformat}Then the variable (direct or through env.foo) is just the $ JOB_URL BUILD_URL of the build selected as a string, and there's no Run object on params to access more detail about that build. These should be made consistent so that either the input step only returns the string job_url to match the build params, or the Run object itself should be accessible when using a build parameter ... naturally I'd prefer the latter as it's way more flexible.
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-38383) StackOverflow when loading a large pipeline job
Title: Message Title Sam Van Oort commented on JENKINS-38383 Re: StackOverflow when loading a large pipeline job Thomas Johansen That sounds like an issue I'm tracking that sometimes happens with performance-optimized builds with specific combinations of build agents used (noted in a couple quirks by https://issues.jenkins-ci.org/browse/JENKINS-47173) – do you have a sample of your pipeline here to reproduce with? 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-50022) Run parameter behaves differently between input step and job parameter
Title: Message Title James Hogarth commented on JENKINS-50022 Re: Run parameter behaves differently between input step and job parameter Actually having bumped into a bunch of serialization issues with the object from the input step ... I'm reversing my preference. It'd be much better for input to return the same as the build parameter ... the full url to the build (or the runId) which of course is a pure string and has no serialization issues. The Run object is otherwise irritatingly painful to deal with due to CPS concerns. 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-11760) Failed SCM poll does not notify admin/anyone of failure.
Title: Message Title
Brian Ray edited a comment on JENKINS-11760
Re: Failed SCM poll does not notify admin/anyone of failure.
We have noticed this gap after upgrading our SCM repository and putting it behind a reverse proxy. We accordingly changed the repo URL in our pipelines.But the most recent successful build prior to the URL change still has the old URL and thus polling chokes like this (BitBucket/Git, using Git plugin and JGit implementation):{noformat}ERROR: polling failed in on org.eclipse.jgit.errors.NoRemoteRepositoryException: : not found at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:479) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:290) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getHeadRev(JGitAPIImpl.java:758)Caused: hudson.plugins.git.GitException at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getHeadRev(JGitAPIImpl.java:764) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:635) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:594)Caused: java.io.IOException at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:596) at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:607) ...{noformat}I anticipated this and know how to correct it, but admins not familiar with it could conceivably go days here without noticing that branches are not building, as we have a few that are relatively slow-changing.It would be great to get notification via [email-ext|https://plugins.jenkins.io/email-ext] or other notification plugin. Or at least have a visual indicator on the job main page that the most recent poll attempt has failed.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-11760) Failed SCM poll does not notify admin/anyone of failure.
Title: Message Title Brian Ray commented on JENKINS-11760 Re: Failed SCM poll does not notify admin/anyone of failure. We have noticed this gap after upgrading our SCM repository and putting it behind reverse proxy. We accordingly change the repo URL in our pipelines. But the most recent successful build prior to the URL change still has the old URL and thus polling chokes like this (BitBucket/Git, using Git plugin and JGit implementation): ERROR: polling failed in on org.eclipse.jgit.errors.NoRemoteRepositoryException: : not found at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:479) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:290) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getHeadRev(JGitAPIImpl.java:758) Caused: hudson.plugins.git.GitException at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getHeadRev(JGitAPIImpl.java:764) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:635) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:594) Caused: java.io.IOException at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:596) at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:607) ... I anticipated this and know how to correct it, but admins not familiar with it could conceivably go days here without noticing that branches are not building, as we have a few that are relatively slow-changing. It would be great to get notification via email-ext or other notification plugin. Or at least have a visual indicator on the job main page that the most recent poll attempt has failed. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-11760) Failed SCM poll does not notify admin/anyone of failure.
Title: Message Title
Brian Ray edited a comment on JENKINS-11760
Re: Failed SCM poll does not notify admin/anyone of failure.
We have noticed this gap after upgrading our SCM repository and putting it behind reverse proxy. We accordingly change changed the repo URL in our pipelines.But the most recent successful build prior to the URL change still has the old URL and thus polling chokes like this (BitBucket/Git, using Git plugin and JGit implementation):{noformat}ERROR: polling failed in on org.eclipse.jgit.errors.NoRemoteRepositoryException: : not found at org.eclipse.jgit.transport.TransportHttp.connect(TransportHttp.java:479) at org.eclipse.jgit.transport.TransportHttp.openFetch(TransportHttp.java:290) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getHeadRev(JGitAPIImpl.java:758)Caused: hudson.plugins.git.GitException at org.jenkinsci.plugins.gitclient.JGitAPIImpl.getHeadRev(JGitAPIImpl.java:764) at hudson.plugins.git.GitSCM.compareRemoteRevisionWithImpl(GitSCM.java:635) at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:594)Caused: java.io.IOException at hudson.plugins.git.GitSCM.compareRemoteRevisionWith(GitSCM.java:596) at org.jenkinsci.plugins.workflow.job.WorkflowJob.poll(WorkflowJob.java:607) ...{noformat}I anticipated this and know how to correct it, but admins not familiar with it could conceivably go days here without noticing that branches are not building, as we have a few that are relatively slow-changing.It would be great to get notification via [email-ext|https://plugins.jenkins.io/email-ext] or other notification plugin. Or at least have a visual indicator on the job main page that the most recent poll attempt has failed.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50029) Powershell treats warnings as errors
Title: Message Title Gabriel Loewen commented on JENKINS-50029 Re: Powershell treats warnings as errors No, nothing else pending from me. Just trying to fix the bugs as quickly as I find them 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-50029) Powershell treats warnings as errors
Title: Message Title Sam Van Oort commented on JENKINS-50029 Re: Powershell treats warnings as errors Gabriel Loewen That's fine, I'll try to get someone who knows windows to do a review tomorrow and then once review is sold we can release. Do you have anything else pending though? I'd like to aim for one more rollup-release of Durable Task and then focus on longer-ranged enhancements for a bit. 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-50028) Maven Report gadget : attached artifacts of 'pom' projects are not displayed
Title: Message Title dan tran commented on JENKINS-50028 Re: Maven Report gadget : attached artifacts of 'pom' projects are not displayed i attached a sample 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-50028) Maven Report gadget : attached artifacts of 'pom' projects are not displayed
Title: Message Title dan tran updated an issue Jenkins / JENKINS-50028 Maven Report gadget : attached artifacts of 'pom' projects are not displayed Change By: dan tran Attachment: attach-sample.pom 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-50029) Powershell treats warnings as errors
Title: Message Title Gabriel Loewen assigned an issue to Gabriel Loewen Jenkins / JENKINS-50029 Powershell treats warnings as errors Change By: Gabriel Loewen Assignee: Gabriel Loewen 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-50029) Powershell treats warnings as errors
Title: Message Title
Gabriel Loewen edited a comment on JENKINS-50029
Re: Powershell treats warnings as errors
Actually, from the context of PowerShell it is an error. You are executing a native command and that command is producing what PowerShell is interpreting as an error, which is written to the error stream and then caught by the PowerShell pipeline step. You can test this out for yourself in a PowerShell session by executing that command and then checking the error history in $Error, which is a PowerShell automatic variable containing an array of errors. Normally this would be a non-fatal error, but because of an issue with how errors are handled in the PowerShell pipeline step it is treated as a fatal error and exiting.[~svanoort] I have submitted a PR that fixes this issue, [67| {color:#33} [ https://github.com/jenkinsci/durable-task-plugin/pull/67 ] {color} ] , so it should be fixed as soon as that PR is merged and a new version is cut :)
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-50029) Powershell treats warnings as errors
Title: Message Title Gabriel Loewen commented on JENKINS-50029 Re: Powershell treats warnings as errors Actually, from the context of PowerShell it is an error. You are executing a native command and that command is producing what PowerShell is interpreting as an error, which is written to the error stream and then caught by the PowerShell pipeline step. You can test this out for yourself in a PowerShell session by executing that command and then checking the error history in $Error, which is a PowerShell automatic variable containing an array of errors. Normally this would be a non-fatal error, but because of an issue with how errors are handled in the PowerShell pipeline step it is treated as a fatal error and exiting. Sam Van Oort I have submitted a PR that fixes this issue, [67|https://github.com/jenkinsci/durable-task-plugin/pull/67], so it should be fixed as soon as that PR is merged and a new version is cut 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-50029) Powershell treats warnings as errors
Title: Message Title Sam Van Oort commented on JENKINS-50029 Re: Powershell treats warnings as errors Gabriel Loewen Would you be able to take a look? You're the guru on the Powershell end of things here. 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-50029) Powershell treats warnings as errors
Title: Message Title Sam Van Oort assigned an issue to Unassigned Jenkins / JENKINS-50029 Powershell treats warnings as errors Change By: Sam Van Oort 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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title
kutzi edited a comment on JENKINS-28822
Re: Can't distinguish between durable task abort and failure in workflow plugin
I guess this is also the reason for JENKINS-43339, isn't it?This is IMO a big issue as it makes to post the _post { aborted {} } _ section in declarative pipelines largely unusable. In fact, I've not seen a single occasion when _aborted_ worked as expected. For me the _failure_ section is always triggered instead.
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-28822) Can't distinguish between durable task abort and failure in workflow plugin
Title: Message Title
kutzi commented on JENKINS-28822
Re: Can't distinguish between durable task abort and failure in workflow plugin
I guess this is also the reason for JENKINS-43339, isn't it? This is IMO a big issue as it makes to post { aborted {} } section in declarative pipelines largely unusable. In fact, I've not seen a single occasion when aborted worked as expected. For me the failure section is always triggered instead.
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-50029) Powershell treats warnings as errors
Title: Message Title
Wouter Slob updated an issue
Jenkins / JENKINS-50029
Powershell treats warnings as errors
Change By:
Wouter Slob
After upgrading to the latest Jenkins LTS & durable task plugin (v1.21) our pipelines fail on warnings.Pipeline:{code:java}node() {bat 'C:\\Python27\\python.exe -c "import warnings;warnings.warn(\'future\', FutureWarning)"'powershell 'C:\\Python27\\python.exe -c "import warnings;warnings.warn(\'future\', FutureWarning)"'}{code}{quote}Output: 2018-03-08 19:47:13 [src] Running batch script 2018-03-08 19:47:14 2018-03-08 19:47:14 d:\src>C:\Python27\python.exe -c "import warnings;warnings.warn('future', FutureWarning)" 2018-03-08 19:47:17 -c:1: FutureWarning: future [Pipeline] powershell {color:#ff}2018-03-08 19:47:18 [src] Running PowerShell script{color} {color:#ff} 2018-03-08 19:47:20 powershell.exe : -c:1: FutureWarning: future{color} {color:#ff} 2018-03-08 19:47:20 At D:\src@tmp\durable-4343e8b5\powershellWrapper.ps1:3 char:1{color} {color:#ff} 2018-03-08 19:47:20 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -File ...{color} {color:#ff} 2018-03-08 19:47:20 + ~{color} {color:#ff} 2018-03-08 19:47:20 + CategoryInfo : NotSpecified: (-c:1: FutureWarning: future:Strin g) [], RemoteException{color} {color:#ff} 2018-03-08 19:47:20 + FullyQualifiedErrorId : NativeCommandError{color} {color:#ff} 2018-03-08 19:47:20{color}{quote} This returns in "1" exit code, causing the pipeline to fail. So somehow, somewhere, the warning is transformed / interpreted as an error.
Add Comment
[JIRA] (JENKINS-50029) Powershell treats warnings as errors
Title: Message Title Wouter Slob assigned an issue to Sam Van Oort Jenkins / JENKINS-50029 Powershell treats warnings as errors Change By: Wouter Slob 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-50029) Powershell treats warnings as errors
Title: Message Title
Wouter Slob created an issue
Jenkins / JENKINS-50029
Powershell treats warnings as errors
Issue Type:
Bug
Assignee:
Unassigned
Components:
durable-task-plugin
Created:
2018-03-08 18:58
Environment:
Latest Jenkins LTS, Durable-task plugin v2.21
Priority:
Major
Reporter:
Wouter Slob
After upgrading to the latest Jenkins LTS & durable task plugin (v1.21) our pipelines fail on warnings. Pipeline:
node() {
bat 'C:\\Python27\\python.exe -c "import warnings;warnings.warn(\'future\', FutureWarning)"'
powershell 'C:\\Python27\\python.exe -c "import warnings;warnings.warn(\'future\', FutureWarning)"'
}
Output: 2018-03-08 19:47:13 [src] Running batch script 2018-03-08 19:47:14 2018-03-08 19:47:14 d:\src>C:\Python27\python.exe -c "import warnings;warnings.warn('future', FutureWarning)" 2018-03-08 19:47:17 -c:1: FutureWarning: future [Pipeline] powershell 2018-03-08 19:47:18 [src] Running PowerShell script 2018-03-08 19:47:20 powershell.exe : -c:1: FutureWarning: future 2018-03-08 19:47:20 At D:\src@tmp\durable-4343e8b5\powershellWrapper.ps1:3 char:1 2018-03-08 19:47:20 + & powershell -NoProfile -NonInteractive -ExecutionPolicy Bypass -File ... 2018-03-08 19:47:20 + ~ 2018-03-08 19:47:20 + CategoryInfo : NotSpecified: (-c:1: FutureWarning: future:Strin g) [],
[JIRA] (JENKINS-49632) Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts")
Title: Message Title Cyrille Le Clerc commented on JENKINS-49632 Re: Maven Report gadget : attached artifacts are not displayed (was "MavenLinkerPublisher - missing classifier and secondary artifacts") Close, we will follow up on the more specific JENKINS-50028 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-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse stopped work on JENKINS-49771 Change By: Max Laverse Status: In Progress Open 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-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse resolved as Fixed Jenkins / JENKINS-49771 token is never set so is constantly refreshed. Change By: Max Laverse 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-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse started work on JENKINS-49771 Change By: Max Laverse 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-49771) token is never set so is constantly refreshed.
Title: Message Title Max Laverse commented on JENKINS-49771 Re: token is never set so is constantly refreshed. I believe this is fixed in version 0.3.1. Please let me know if that's not the 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-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title Abdulla Hawara updated an issue Jenkins / JENKINS-49710 Pipelines run under heavy load sometimes hang running Docker Change By: Abdulla Hawara Labels: groo 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-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title Abdulla Hawara updated an issue Jenkins / JENKINS-49710 Pipelines run under heavy load sometimes hang running Docker Change By: Abdulla Hawara Labels: groo 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-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title Abdulla Hawara updated an issue Jenkins / JENKINS-49710 Pipelines run under heavy load sometimes hang running Docker Change By: Abdulla Hawara Component/s: durable-task-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-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title
Abdulla Hawara edited a comment on JENKINS-49710
Re: Pipelines run under heavy load sometimes hang running Docker
My *theory* about the issue:Jenkins has `*Text file busy*` error coming from `*durable*` which is used by `*pipeline nodes and processes*` plugin. This issue is easily reproducible by running any command e.g. `*sh "echo 'Hello'"*` in any jenkins job many times in parallel. This hang is caused when running a docker container using the *docker plugin* (the container will stay alive) , but when we run `*docker*` manually using *sh 'docker ...'* it never hangs, but that `*Text file busy*` error still appears because we run a lot of jobs at the same time. The container in this case will stay running forever {color:#ff}To reproduce {color}{code:java}Text file busy{code}error, please follow these steps: 1. Run Jenkins locally `docker run -p 8080:8080 -p 5:5 jenkins/jenkins:lts` ver. 2.89.4 2. install just the recommended plugins on it 3. create new pipeline projects called `*hello*` and `*hello2*` 4. put this code in ‘hello’ :{code:java}node{sh "echo 'hello'"}{code}and this in `*hello2*`:{code:java}node{sh "echo 'hello'"sleep(2)}{code}5. Create a new pipeline project called `*runner*` and put this inside:{code:java}COUNTER = 0node{def jobs = [:]// add 24 instances of the same test to run them later in parallel24.times {jobs[('runner' + COUNTER++)] = {triggerProject('hello')()}}// add 24 instances of the same test to run them later in parallel24.times {jobs[('runner' + COUNTER++)] = {triggerProject('hello2')()}}// run them all 20 times in parallel20.times {parallel jobs}}def triggerProject(jobName) {return {try{build job: jobName, parameters: [string(name: 'VALUE', value: String.valueOf(COUNTER++))]} catch (ex){println ex}}}{code}6. Go to your jenkins configurations and change the executors to `*50*` 7. try to run the runner once and if you got some sandbox exception, go to the in-procces Script Approval in the Manage Jenkins page and click approve for all commands 8. run runner again and you will see that some of `*hello*` and `*hello2*` has `*text file busy*` errorThe logs you get afterwards:{code:java}Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/hello@6[Pipeline] {[Pipeline] sh[hello@6] Running shell scriptsh: 1: /var/jenkins_home/workspace/hello@6@tmp/durable-a771d7dd/script.sh: Text file busy[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code 2Finished: FAILURE{code}
Add Comment
[JIRA] (JENKINS-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title
Abdulla Hawara edited a comment on JENKINS-49710
Re: Pipelines run under heavy load sometimes hang running Docker
My *theory* about the issue:Jenkins has `*Text file busy*` error coming from `*durable*` which is used by `*pipeline nodes and processes*` plugin. This issue is easily reproducible by running any command e.g. `*sh "echo 'Hello'"*` in any jenkins job many times in parallel. This hang is caused when running a docker container using the * docker plugin * , but when we run `*docker*` without manually using ` * sh docker ...* ` it never hangs , but that `*Text file busy*` error still appears because we run a lot of jobs at the same time. The container in this case will stay running forever {color:#ff}To reproduce {color}{code:java}Text file busy{code}error, please follow these steps: 1. Run Jenkins locally `docker run -p 8080:8080 -p 5:5 jenkins/jenkins:lts` ver. 2.89.4 2. install just the recommended plugins on it 3. create new pipeline projects called `*hello*` and `*hello2*` 4. put this code in ‘hello’ :{code:java}node{sh "echo 'hello'"}{code}and this in `*hello2*`:{code:java}node{sh "echo 'hello'"sleep(2)}{code}5. Create a new pipeline project called `*runner*` and put this inside:{code:java}COUNTER = 0node{def jobs = [:]// add 24 instances of the same test to run them later in parallel24.times {jobs[('runner' + COUNTER++)] = {triggerProject('hello')()}}// add 24 instances of the same test to run them later in parallel24.times {jobs[('runner' + COUNTER++)] = {triggerProject('hello2')()}}// run them all 20 times in parallel20.times {parallel jobs}}def triggerProject(jobName) {return {try{build job: jobName, parameters: [string(name: 'VALUE', value: String.valueOf(COUNTER++))]} catch (ex){println ex}}}{code}6. Go to your jenkins configurations and change the executors to `*50*` 7. try to run the runner once and if you got some sandbox exception, go to the in-procces Script Approval in the Manage Jenkins page and click approve for all commands 8. run runner again and you will see that some of `*hello*` and `*hello2*` has `*text file busy*` errorThe logs you get afterwards:{code:java}Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/hello@6[Pipeline] {[Pipeline] sh[hello@6] Running shell scriptsh: 1: /var/jenkins_home/workspace/hello@6@tmp/durable-a771d7dd/script.sh: Text file busy[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code 2Finished: FAILURE{code}
Add Comment
[JIRA] (JENKINS-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title
Abdulla Hawara edited a comment on JENKINS-49710
Re: Pipelines run under heavy load sometimes hang running Docker
My *theory* about the issue:Jenkins has `*Text file busy*` error coming from `*durable*` which is used by `*pipeline nodes and processes*` plugin. This issue is easily reproducible by running any command e.g. `*sh "echo 'Hello'"*` in any jenkins job many times in parallel. This hang is caused when running a docker container using the *docker plugin*, but when we run `*docker*` manually using ` *sh ' docker ... ' * ` it never hangs, but that `*Text file busy*` error still appears because we run a lot of jobs at the same time. The container in this case will stay running forever {color:#ff}To reproduce {color}{code:java}Text file busy{code}error, please follow these steps: 1. Run Jenkins locally `docker run -p 8080:8080 -p 5:5 jenkins/jenkins:lts` ver. 2.89.4 2. install just the recommended plugins on it 3. create new pipeline projects called `*hello*` and `*hello2*` 4. put this code in ‘hello’ :{code:java}node{sh "echo 'hello'"}{code}and this in `*hello2*`:{code:java}node{sh "echo 'hello'"sleep(2)}{code}5. Create a new pipeline project called `*runner*` and put this inside:{code:java}COUNTER = 0node{def jobs = [:]// add 24 instances of the same test to run them later in parallel24.times {jobs[('runner' + COUNTER++)] = {triggerProject('hello')()}}// add 24 instances of the same test to run them later in parallel24.times {jobs[('runner' + COUNTER++)] = {triggerProject('hello2')()}}// run them all 20 times in parallel20.times {parallel jobs}}def triggerProject(jobName) {return {try{build job: jobName, parameters: [string(name: 'VALUE', value: String.valueOf(COUNTER++))]} catch (ex){println ex}}}{code}6. Go to your jenkins configurations and change the executors to `*50*` 7. try to run the runner once and if you got some sandbox exception, go to the in-procces Script Approval in the Manage Jenkins page and click approve for all commands 8. run runner again and you will see that some of `*hello*` and `*hello2*` has `*text file busy*` errorThe logs you get afterwards:{code:java}Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in /var/jenkins_home/workspace/hello@6[Pipeline] {[Pipeline] sh[hello@6] Running shell scriptsh: 1: /var/jenkins_home/workspace/hello@6@tmp/durable-a771d7dd/script.sh: Text file busy[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineERROR: script returned exit code 2Finished: FAILURE{code}
Add Comment
[JIRA] (JENKINS-50023) core.ViewTest#renameJob is failling in CI
Title: Message Title Devin Nusbaum commented on JENKINS-50023 Re: core.ViewTest#renameJob is failling in CI Raul Arabaolaza Ok, thank you! Feel free to request me as a reviewer on anything. 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-50023) core.ViewTest#renameJob is failling in CI
Title: Message Title Raul Arabaolaza commented on JENKINS-50023 Re: core.ViewTest#renameJob is failling in CI Thanks @dnusbaum I can fix it without problems, your confirmation on this being intentional is the only think I need. 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-50028) Maven Report gadget : attached artifacts of 'pom' projects are not displayed
Title: Message Title Cyrille Le Clerc commented on JENKINS-50028 Re: Maven Report gadget : attached artifacts of 'pom' projects are not displayed dan tran can you provide an example of "attached artifacts" of a 'pom' type project? 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-50028) Maven Report gadget : attached artifacts of 'pom' projects are not displayed
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-50028 Maven Report gadget : attached artifacts of 'pom' projects are not displayed Change By: Cyrille Le Clerc Assignee: Alvaro Lobato Cyrille Le Clerc 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-50028) Maven Report gadget : attached artifacts of 'pom' projects are not displayed
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-50028 Maven Report gadget : attached artifacts of 'pom' projects are not displayed Issue Type: Bug Assignee: Alvaro Lobato Components: pipeline-maven-plugin Created: 2018-03-08 18:12 Priority: Minor Reporter: Cyrille Le Clerc dan tran says on JENKINS-49632 "Maven Report gadget : attached artifacts are not displayed": > "Any additional artifacts attach to a maven 'pom' module type are missing from the list Otherwise it works" Add Comment
[JIRA] (JENKINS-50023) core.ViewTest#renameJob is failling in CI
Title: Message Title Devin Nusbaum edited a comment on JENKINS-50023 Re: core.ViewTest#renameJob is failling in CI All Jobs have a name and a display name before and after the change . Previously, both the name and display name could be edited from the configure page. In JENKINS-22936 I removed the ability to change the name from the configure page, and moved it to a separate page (feel free to read the ticket for the motivation behind the change). The display name can still be edited on the configure page.All of the ATH code that does renames will have to be updated to use the new flow. I can submit a PR to fix the case you pointed out here, but I am not sure how many other tests will need to be updated. 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-50023) core.ViewTest#renameJob is failling in CI
Title: Message Title Devin Nusbaum commented on JENKINS-50023 Re: core.ViewTest#renameJob is failling in CI All Jobs have a name and a display name. Previously, both the name and display name could be edited from the configure page. In JENKINS-22936 I removed the ability to change the name from the configure page, and moved it to a separate page (feel free to read the ticket for the motivation behind the change). The display name can still be edited on the configure page. All of the ATH code that does renames will have to be updated to use the new flow. I can submit a PR to fix the case you pointed out here, but I am not sure how many other tests will need to be updated. 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Bill Hamilton commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Stephen Connolly Stephen, I did have it configured as GitHub...BUT, I also had a preceding PSL defined using Git, so they seemed to have conflicted. So I removed the preceding. I also tweaked the settings to be inline with yours. And finally I realized that one of our masters had an older version of GH Branch Source Plugin, it was 2.2.6 and needed 2.3.2. So I think we are all set, 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-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title
Abdulla Hawara commented on JENKINS-49710
Re: Pipelines run under heavy load sometimes hang running Docker
My theory about the issue: Jenkins has `Text file busy` error coming from `durable` which is used by `pipeline nodes and processes` plugin. This issue is easily reproducible by running any command e.g. `sh "echo 'Hello'"` in any jenkins job many times in parallel. This hang is caused when running a docker container using the docker plugin, but when we run `docker` without using `sh` it never hangs but that `Text file busy` error still appears because we run a lot of jobs at the same time. The container in this case will stay running forever To reproduce
Text file busy
error, please follow these steps: 1. Run Jenkins locally `docker run -p 8080:8080 -p 5:5 jenkins/jenkins:lts` ver. 2.89.4 2. install just the recommended plugins on it 3. create new pipeline projects called `hello` and `hello2` 4. put this code in ‘hello’ :
node{
sh "echo 'hello'"
}
and this in `hello2`:
node{
sh "echo 'hello'"
sleep(2)
}
5. Create a new pipeline project called `runner` and put this inside:
COUNTER = 0
node{
def jobs = [:]
// add 24 instances of the same test to run them later in parallel
24.times {
jobs[('runner' + COUNTER++)] = {triggerProject('hello')()}
}
// add 24 instances of the same test to run them later in parallel
24.times {
jobs[('runner' + COUNTER++)] = {triggerProject('hello2')()}
}
// run them all 20 times in parallel
20.times {
parallel jobs
}
}
def triggerProject(jobName) {
return {
try{
build job: jobName, parameters: [string(name: 'VALUE', value: String.valueOf(COUNTER++))]
} catch (ex){
println ex
}
}
}
6. Go to your jenkins configurations and change the executors to `50` 7. try to run the runner once and if you got some sandbox exception, go to the in-procces Script Approval in the Manage Jenkins page and click approve for all commands 8. run runner again and you will see that some of `hello` and `hello2` has `text file busy` error The logs you get afterwards:
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] node
Running on Jenkins in
[JIRA] (JENKINS-50025) On some Windows Build Agents, Batch Steps Hang
Title: Message Title Sam Van Oort commented on JENKINS-50025 Re: On some Windows Build Agents, Batch Steps Hang James Nord Has suggested the root cause here might be antivirus blocking the terminal 'move' operation. 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-34150) Pipeline Batch hangs
Title: Message Title Sam Van Oort commented on JENKINS-34150 Re: Pipeline Batch hangs Sven Brosi Steven Foster Released fix after review and testing as durable-task-plugin 1.21 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-50025) On some Windows Build Agents, Batch Steps Hang
Title: Message Title Sam Van Oort closed an issue as Done Released with v1.21 Jenkins / JENKINS-50025 On some Windows Build Agents, Batch Steps Hang Change By: Sam Van Oort Status: In Progress Closed Resolution: Done 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-50021) credentials('some-id') should support Secret Zip type of credentials
Title: Message Title
Andrew Bayer commented on JENKINS-50021
Re: credentials('some-id') should support Secret Zip type of credentials
Well, this is actually hard to do. ZipFileBinding and FileBinding actually both use FileCredentials as their type - there is, so far as I can tell, no separate credentials type for zip files. And the way CredentialsBindingHandler works in Declarative is that it keys off of the credential type. So...looks like the answer is gonna be no, this can't be done with the current architecture.
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-50027) Polling build filters in jenkinsfile broken or need guidance on what code should be
Title: Message Title Karl Wirth updated an issue Jenkins / JENKINS-50027 Polling build filters in jenkinsfile broken or need guidance on what code should be Change By: Karl Wirth Labels: P4_VERIFY 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-50027) Polling build filters in jenkinsfile broken or need guidance on what code should be
Title: Message Title
Karl Wirth created an issue
Jenkins / JENKINS-50027
Polling build filters in jenkinsfile broken or need guidance on what code should be
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-03-08 17:18
Environment:
1.8.5 1.8.6
Priority:
Blocker
Reporter:
Karl Wirth
If you use the syntax generator to create a checkout step that includes a polling build filter the following text is created:
filter: [userFilter('BUILDER'), viewFilter('''//corvus/main/workers''')],
If you try to execute this code in Pipeline (jenkinsfile or defined in job window) it will fail with error:
[Pipeline] End of Pipeline
java.lang.IllegalArgumentException: Arguments to class org.jenkinsci.plugins.p4.filters.FilterPatternListImpl have to be explicitly named
at org.jenkinsci.plugins.structs.describable.DescribableModel.instantiate(DescribableModel.java:254)
at org.jenkinsci.plugins.structs.describable.UninstantiatedDescribable.instantiate(UninstantiatedDescribable.java:167)
at org.jenkinsci.plugins.structs.describable.DescribableModel.coerce(DescribableModel.java:372)
at org.jenkinsci.plugins.structs.describable.DescribableModel.coerceList(DescribableModel.java:463)
at
[JIRA] (JENKINS-50026) Hubot Steps 2.0.0 Enhancements List
Title: Message Title
Naresh Rayapati updated an issue
Jenkins / JENKINS-50026
Hubot Steps 2.0.0 Enhancements List
Change By:
Naresh Rayapati
To track few ideas that can be implemented for a next major version. (2.0.0) * Global Configuration to support multiple hubot servers (Slack, Hipchat, MS teams and so on...) * Folder Level configuration ** Folder name as a room name ? * Build failure notifications - BuildAction to send failure notifications for every job under the folder to a chat room? * Disable Meta (Sending Job URL and Username) ? ** Instead should enable sending the message as JSON format and user would decide the format in hubot scripts? ** Custom JSON config? *** Sending Approval/Abort URLs through config *{color:# FF ff }Note: Few of the above enhancements could be non passive changes{color}*
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
[JIRA] (JENKINS-50026) Hubot Steps 2.0.0 Enhancements List
Title: Message Title Naresh Rayapati updated an issue Jenkins / JENKINS-50026 Hubot Steps 2.0.0 Enhancements List Change By: Naresh Rayapati Issue Type: New Feature Epic 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-50025) On some Windows Build Agents, Batch Steps Hang
Title: Message Title
Sam Van Oort updated an issue
Jenkins / JENKINS-50025
On some Windows Build Agents, Batch Steps Hang
Change By:
Sam Van Oort
Like the title said, two users reported in comments on [JENKINS-34150|https://issues.jenkins-ci.org/browse/JENKINS-34150] that they'd seen a recurrence of Windows batch steps hanging when upgrading durable task plugin from 1.18 to 1.20Notes: all initial tests passed in CI (including Windows), both with the durable-task plugin and with workflow-durable-task plugin upgraded to use v1.20 as a dependency. I initially identified a potential issue with the line terminator (\n vs \r\n) when running without returning a stdOut file. When testing with helpful user [~stevenfoster] this seemed to initially solve the issue on one Jenkins instance... but not on another. Both were using Windows build agents from the same Windows image. Testing showed that the final command of the batch file (move "%s.tmp" "%s" with the appropriate escaping applied) seems to have failed. The jenkins-result.txt.tmp file existed but had not been copied to jenkins-result.txt).The users's jenkins-wrap.bat file is below (with their permission): {code:none}@echo offcmd /c ""D:/jenkins/workspace/le-32QSIUVUUTA2U@tmp/durable-605bf002/jenkins-main.bat"" > "D:/jenkins/workspace/le-32QSIUVUUTA2U@tmp/durable-605bf002/jenkins-log.txt" 2>&1echo %ERRORLEVEL% > "D:/jenkins/workspace/le-32QSIUVUUTA2U@tmp/durable-605bf002/jenkins-result.txt.tmp"move "D:/jenkins/workspace/le-32QSIUVUUTA2U@tmp/durable-605bf002/jenkins-result.txt.tmp" "D:/jenkins/workspace/le-32QSIUVUUTA2U@tmp/durable-605bf002/jenkins-result.txt"{code}Running this command permitted the batch step to complete successfuly as expected:{code:none}move " D:/jenkins/workspace/le-32QSIUVUUTA2U@tmp/durable-605bf002/jenkins-result.txt " " D:/jenkins/workspace/le-32QSIUVUUTA2U@tmp/durable-605bf002/jenkins-result.txt.tmp " {code}On the system that failed, it appears that running the wrapper script directly triggered a "the System cannot find the file specified" in workspace D:\jenkins\workspace\project\dttest@tmp\durable-6b266373 (again, path listed with the user's permission). It's possible that something like https://github.com/svanoort/durable-task-plugin/commit/38fc4709fb89da12b78e79d1292298de3d5ca24e#diff-ba4605d3233e8bd08bb06dd87253e5f8 might be needed here (double-quoting) but the simpler and safer solution is to revert the changes to the Batch file durable task -- the check for a zero-length result file should protect against the issue that PR#66 resolved.
[JIRA] (JENKINS-50026) Hubot Steps 2.0.0 Enhancements List
Title: Message Title Naresh Rayapati created an issue Jenkins / JENKINS-50026 Hubot Steps 2.0.0 Enhancements List Issue Type: New Feature Assignee: Naresh Rayapati Components: hubot-steps-plugin Created: 2018-03-08 17:12 Priority: Minor Reporter: Naresh Rayapati To track few ideas that can be implemented for a next major version. (2.0.0) Global Configuration to support multiple hubot servers (Slack, Hipchat, MS teams and so on...) Folder Level configuration Folder name as a room name ? Build failure notifications Disable Meta (Sending Job URL and Username) ? Instead should enable sending the message as JSON format and user would decide the format in hubot scripts? Custom JSON config? Sending Approval/Abort URLs through config Note: Few of the above enhancements could be non passive changes
[JIRA] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Sam Van Oort closed an issue as Fixed Sven Brosi Steven Foster I'm closing THIS issue because while the result is the same this has a different cause and is resolved in JENKINS-50025. Jenkins / JENKINS-34150 Pipeline Batch hangs Change By: Sam Van Oort Status: Reopened 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
[JIRA] (JENKINS-34150) Pipeline Batch hangs
Title: Message Title Sam Van Oort commented on JENKINS-34150 Re: Pipeline Batch hangs This issue duplicates symptoms of JENKINS-50025 but the root causes are significantly different, so that is being tracked separately. 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-50025) On some Windows Build Agents, Batch Steps Hang
Title: Message Title Sam Van Oort commented on JENKINS-50025 Re: On some Windows Build Agents, Batch Steps Hang This essentially duplicates the previous issue but I'm tracking separately because the root cause is different and we want to track the investigation. 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-50025) On some Windows Build Agents, Batch Steps Hang
Title: Message Title Sam Van Oort created an issue Jenkins / JENKINS-50025 On some Windows Build Agents, Batch Steps Hang Issue Type: Bug Assignee: Sam Van Oort Components: durable-task-plugin Created: 2018-03-08 17:05 Environment: Durable-task plugin v2.20, Jenkins core irrelevant, Windows Build Agent running batch steps (some agents, not others) Labels: regression windows Priority: Major Reporter: Sam Van Oort Like the title said, two users reported in comments on JENKINS-34150 that they'd seen a recurrence of Windows batch steps hanging when upgrading durable task plugin from 1.18 to 1.20 Notes: all initial tests passed in CI (including Windows), both with the durable-task plugin and with workflow-durable-task plugin upgraded to use v1.20 as a dependency. I initially identified a potential issue with the line terminator (\n vs \r\n) when running without returning a stdOut file. When testing with helpful user Steven Foster this seemed to initially solve the issue on one Jenkins instance... but not on another. Both were using Windows build agents from the same Windows image. Testing showed that the final command of the batch file (move "%s.tmp" "%s" with the appropriate escaping applied) seems to have failed. The jenkins-result.txt.tmp file existed but had not been copied to jenkins-result.txt). The users's jenkins-wrap.bat file is below (with their permission): @echo off cmd
[JIRA] (JENKINS-50025) On some Windows Build Agents, Batch Steps Hang
Title: Message Title Sam Van Oort started work on JENKINS-50025 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-50024) Cannot run CIFs plugin
Title: Message Title
Ben Middleton created an issue
Jenkins / JENKINS-50024
Cannot run CIFs plugin
Issue Type:
Bug
Assignee:
Alex Earl
Components:
cifs-plugin
Created:
2018-03-08 17:01
Environment:
Jenkins 2.110 Job DLS 1.68 Publish over CIFS 0.9
Priority:
Critical
Reporter:
Ben Middleton
I'm trying to build DSL to run this plugin. However, when I run this:
cifsPublisher {
continueOnError(false)
failOnError(true)
alwaysPublishFromMaster(false)
masterNodeName('master')
publishers {
cifsPublisher {
configName('nl1fs02.mydomain.com')
verbose(false)
useWorkspaceInPromotion(false)
usePromotionTimestamp(false)
retry {
retries(5)
retryDelay(15)
}
label {
label('Publishing to nl1fs02')
}
transfers {
cifsTransfer {
sourceFiles('**/build/**')
excludes('')
[JIRA] (JENKINS-46283) pipeline hangs after executing sh step command
Title: Message Title
Steve Boardwell edited a comment on JENKINS-46283
Re: pipeline hangs after executing sh step command
Hi [~jglick] / [~jstancek] / [~reinholdfuereder]I think I have the cause, or at least one of the possible causes, and can reproduce the hanging agent in principle. It has to do with the parent process being killed. Why that happens I cannot say, but perhaps the OS does this when the resources are low, etc (in any dockerized agent environment for example) I also have a bit of a hacky workaround - feedback and improvements welcome :).*Disclaimer*: I'm using the exit codes calculated for bash in my solution as well as the bash built-in for finding my current directory. You'd need to take account of this if using a different shell.It's a bit of a long explanation but here goes...h3. Summary * investigated how signals can affect shell scripts * investigated the processes involved ** discovered an unexpected sibling process * found I could reproduce the behaviour by killing the parent process * scripted a workaround for the case that the parent process is missingh3. Long versionh4. Investigated what signals can do to a shell script.Using the following script I tested what signals did to a bash script. I wanted to find out: * which signals would cause a script to exit immediately * which signals would first send an EXIT signal before exiting * which signals would do nothing, etc.{noformat}[jenkins@jenkins-server] ~ $ cat /tmp/test.sh#!/bin/bashset -euo pipefaillatestSignalRc=# register all known trapstypeset -i sig=1while (( sig < 65 )); dotrap "signum=${sig};test ${sig}" "$sig"let sig=sig+1donetrap "test EXIT" "EXIT"trap "test ERR" "ERR"test() {local rc=$?if [[ "$1" != "EXIT" ]] && [[ "$1" != "ERR" ]]; then #echo "Non EXIT or ERR. Making latestSignalRc from signum '$signum'." latestSignalRc=$(( $signum + 128 ))fiecho "Got sig: ${1:-n/a}, signum: '${signum:-n/a}', rc: $rc, latestSignalRc: ${latestSignalRc:-n/a}"# Reset to a default signal handler.trap - $1unset signumif [[ "$1" != "EXIT" ]] && [[ "$1" != "ERR" ]]; then # kill process with signal kill -$1 $$else# if we receive an error, reset the EXIT trap# because we are leaving now anyway[[ "$1" == "ERR" ]] && trap - EXIT exit ${latestSignalRc:-$rc}fi}sleep 0.1if [[ "ERR" == "${1:-}" ]]; then ls /tmp/ &> /dev/nullelif [ -n "${1:-}" ]; thenkill -$1 $$fiecho "After kill..."{noformat}Testing looked something like this:{noformat}[jenkins@jenkins-server] ~ $ for i in ERR 1 2 3 6 15; do echo "-"; (/tmp/test.sh $i; echo "Exited: $?"); done-Got sig: ERR, signum: 'n/a', rc: 2, latestSignalRc: n/aExited: 2-Got sig: 1, signum: '1', rc: 0, latestSignalRc: 129Exited: 129-Got sig: 2, signum: '2', rc: 0, latestSignalRc: 130Got sig: EXIT, signum: 'n/a', rc: 0, latestSignalRc: 130Exited: 130-Got sig: 3, signum: '3', rc: 0, latestSignalRc: 131After kill...Got sig: EXIT, signum: 'n/a', rc: 0, latestSignalRc: 131Exited: 131-Got sig: 6, signum: '6', rc: 0, latestSignalRc: 134Exited: 134-Got sig: 15, signum: '15', rc: 0, latestSignalRc: 143Exited: 143{noformat}I settled on catching 1) SIGHUP 2) SIGINT 6) SIGABRT 15) SIGTERM since they (1) could be caught, and (2) caused the script to exit.h4. Investigated the processes involvedAt first I simply grep'ed the processes using derived values{noformat}node('agent') {sh '''#!/bin/bashset -euo pipefailset +xfunction onExit() {
[JIRA] (JENKINS-47502) Alphabetical Sort by Name Broken
Title: Message Title Rob Sung closed an issue as Duplicate Jenkins / JENKINS-47502 Alphabetical Sort by Name Broken Change By: Rob Sung 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 emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46283) pipeline hangs after executing sh step command
Title: Message Title
Steve Boardwell commented on JENKINS-46283
Re: pipeline hangs after executing sh step command
Hi Jesse Glick / Jan Stancek / Reinhold Füreder I think I have the cause, or at least one of the possible causes, and can reproduce the hanging agent in principle. I also have a bit of a hacky workaround - feedback and improvements welcome . Disclaimer: I'm using the exit codes calculated for bash in my solution as well as the bash built-in for finding my current directory. You'd need to take account of this if using a different shell. It's a bit of a long explanation but here goes... Summary
investigated how signals can affect shell scripts
investigated the processes involved
discovered an unexpected sibling process
found I could reproduce the behaviour by killing the parent process
scripted a workaround for the case that the parent process is missing
Long version Investigated what signals can do to a shell script. Using the following script I tested what signals did to a bash script. I wanted to find out:
which signals would cause a script to exit immediately
which signals would first send an EXIT signal before exiting
which signals would do nothing, etc.
[jenkins@jenkins-server] ~ $ cat /tmp/test.sh
#!/bin/bash
set -euo pipefail
latestSignalRc=
# register all known traps
typeset -i sig=1
while (( sig < 65 )); do
trap "signum=${sig};test ${sig}" "$sig"
let sig=sig+1
done
trap "test EXIT" "EXIT"
trap "test ERR" "ERR"
test() {
local rc=$?
if [[ "$1" != "EXIT" ]] && [[ "$1" != "ERR" ]]; then
#echo "Non EXIT or ERR. Making latestSignalRc from signum '$signum'."
latestSignalRc=$(( $signum + 128 ))
fi
echo "Got sig: ${1:-n/a}, signum: '${signum:-n/a}', rc: $rc, latestSignalRc: ${latestSignalRc:-n/a}"
# Reset to a default signal handler.
trap - $1
unset signum
if [[ "$1" != "EXIT" ]] && [[ "$1" != "ERR" ]]; then
# kill process with signal
kill -$1 $$
else
# if we receive an error, reset the EXIT trap
# because we are leaving now anyway
[[ "$1" == "ERR" ]] && trap - EXIT
exit ${latestSignalRc:-$rc}
fi
}
sleep 0.1
if [[ "ERR" == "${1:-}" ]]; then
ls /tmp/ &> /dev/null
elif [ -n "${1:-}" ]; then
kill -$1 $$
fi
echo "After kill..."
Testing looked something like this:
[jenkins@jenkins-server] ~ $ for i in
[JIRA] (JENKINS-36383) Checkbox setting (CodeReview and Suppression Report) not correctly restored on configurationpage
Title: Message Title Bue Petersen commented on JENKINS-36383 Re: Checkbox setting (CodeReview and Suppression Report) not correctly restored on configurationpage Yes Programming Research are handling the development and support themselves or with help from another company. 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.
