[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer edited a comment on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules If shallow clone for the submodule is activated this error happens on my side. It has to be a clean build. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3894.1574190360170%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules If shallow clone for the submodule is activated this error happens on my side. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.3886.1574188860258%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules Ok it looks like something which is configured on the multibranch configuration is causing this error. I removed now all advanced options apart from Advanced sub-modules behaviours from a copy of the original jobs and it works. I will have a look tomorrow, what is causing this error. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2946.1574113620195%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Mark Waite commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules I attempted to duplicate the problem using a multibranch pipeline and was unsuccessful. My guess is that the issue is either somehow specific to the multibranch pipeline configuration you are using or is connected to an existing workspace from a prior build of the same job which is being reused by the pipeline job. If you run the same multibranch pipeline job in parallel, does the failure happen on all the jobs running in parallel, or only on the first job that was started? When multiple jobs run in parallel, Jenkins allocates a new workspace for the parallel jobs so that they will not collide with running jobs,. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2927.1574112840203%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules Looks like this is somehow project type related. The log above is from a multibranch pipeline. If i use a freestyle project the submodules are handled without a problem. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2911.1574112000186%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-60204 git plugin 4.0.0 can not handle submodules Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203175.1574103532000.2836.1574106960226%40Atlassian.JIRA.
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title
Mark Waite edited a comment on JENKINS-60204
Re: git plugin 4.0.0 can not handle submodules
The message seems to match with a [stackoverflow question|https://stackoverflow.com/questions/40987847/unable-to-find-current-origin-master-revision-in-submodule-path], though I'm not sure how to apply the recommended solution from stackoverflow in the case of the git plugin. The git plugin does not allow user control of the specific git commands and does not provide direct access to {{git pull}}The message in the stack trace is:{noformat}hudson.plugins.git.GitException: Command "git submodule update --remote impl/tool_protec" returned status code 1:stdout: stderr: fatal: Needed a single revisionUnable to find current origin/development revision in submodule path 'impl/tool_protec'{noformat}Can you provide enough details so that someone else can duplicate the problem you're seeing? I use submodules in many different tests and they all work as expected with both git plugin 3.12 and 4.0. I'm sure that means there is something missing from my set of tests, but I don't know what that is until I can duplicate the problem you're seeing.If you'd like to provide a test case as a pull request to my repository jenkins-bugs repository on the [JENKINS-60204 branch|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-60204/README.md] , you're welcome to do that . Otherwise, detailed steps and configuration settings that will duplicate the problem will be sufficient.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Mark Waite commented on JENKINS-60204 Re: git plugin 4.0.0 can not handle submodules The message seems to match with a stackoverflow question, though I'm not sure how to apply the recommended solution from stackoverflow in the case of the git plugin. The git plugin does not allow user control of the specific git commands and does not provide direct access to git pull The message in the stack trace is: hudson.plugins.git.GitException: Command "git submodule update --remote impl/tool_protec" returned status code 1: stdout: stderr: fatal: Needed a single revision Unable to find current origin/development revision in submodule path 'impl/tool_protec' Can you provide enough details so that someone else can duplicate the problem you're seeing? I use submodules in many different tests and they all work as expected with both git plugin 3.12 and 4.0. I'm sure that means there is something missing from my set of tests, but I don't know what that is until I can duplicate the problem you're seeing. If you'd like to provide a test case as a pull request to my repository jenkins-bugs repository on the JENKINS-60204 branch. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and
[JIRA] (JENKINS-60204) git plugin 4.0.0 can not handle submodules
Title: Message Title Benjamin Brummer created an issue Jenkins / JENKINS-60204 git plugin 4.0.0 can not handle submodules Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-11-18 18:58 Environment: Jenkins 2.190.2 git-plugin 4.0.0 Priority: Major Reporter: Benjamin Brummer git-plugin 3.12 works without any problem. > git submodule update --remote impl/tool_protec # timeout=10 Error when executing always post condition: org.jenkinsci.plugins.workflow.steps.MissingContextVariableException: Required context class hudson.FilePath is missing Perhaps you forgot to surround the code with a step that provides this, such as: node at org.jenkinsci.plugins.workflow.steps.StepDescriptor.checkContextAvailability(StepDescriptor.java:266) at org.jenkinsci.plugins.workflow.cps.DSL.invokeStep(DSL.java:263) at org.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:179) at org.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:122) at sun.reflect.GeneratedMethodAccessor849.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:93) at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:325) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1213) at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:1022) at org.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:42) at
