[JIRA] (JENKINS-26660) Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline
Title: Message Title Alexey Melezhik commented on JENKINS-26660 Re: Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline Hi Scott! won't accomplish anything as long as the plugin continues to use git config as a source of submodule information Exactly. Now I have to ssh to jenkins server and edit git config file manually at workspace to allow plugin to work after I removed git sub module from super repo. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-26660) Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline
Title: Message Title Alexey Melezhik commented on JENKINS-26660 Re: Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline HI Mark Waite! If the "Clean before checkout" and "Clean after checkout" were extended to allow an additional behavior to "clean submodules" ... Not diving into implementation of PR mentioned too much , but, say I have about ~ 200 sub modules in my superproject and I checked "Clean ..." options , what time does it take me to get sub modules update? My concerns if this has side effect in uploading things from the scratch ? Which in case of many git sub modules usually takes awhile ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39350) Git client plugin does not respect changes at .gitmodules list ( e.g. removing git sub modules )
Title: Message Title Alexey Melezhik commented on JENKINS-39350 Re: Git client plugin does not respect changes at .gitmodules list ( e.g. removing git sub modules ) Maybe it would be helpful. As temporary workaround I need to: 1. remove git submoulde using convenient commands: 1) git deinit foo 2) git rm foo 3) git rm --cached foo 4) # so on ... 2. do some clean up a jenkins job's workspace: $ ssh jenkins-server $ cd /path/working/dir $ nano .git/config # and remove path to deleted repository `foo' Looks like plugin relies on git/config to resolve an actual list of submodules Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-26660) Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline
Title: Message Title Alexey Melezhik commented on JENKINS-26660 Re: Add another '-f' to git clean to remove deleted submodules or other repos checked out in workspace in pipeline HI! I am just curios , what ETA on this issue? Thanks (PS. it's really blocker to use git plugin for us ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39350) Git client plugin does not respect changes at .gitmodules list ( e.g. removing git sub modules )
Title: Message Title Alexey Melezhik commented on JENKINS-39350 Re: Git client plugin does not respect changes at .gitmodules list ( e.g. removing git sub modules ) Looks like this one looks similar to JENKINS-26660 ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39350) Git client plugin does not respect changes at .gitmodules list ( e.g. removing git sub modules )
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39350 Git client plugin does not respect changes at .gitmodules list ( e.g. removing git sub modules ) Change By: Alexey Melezhik Summary: Git client plugin does not respect changes at .gitmodules list ( e.g. removing git sub modules ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39350) Git client plugin does respect changes at .gitmodules list ( e.g. removing git sub modules )
Title: Message Title
Alexey Melezhik updated an issue
Jenkins / JENKINS-39350
Git client plugin does respect changes at .gitmodules list ( e.g. removing git sub modules )
Change By:
Alexey Melezhik
I successfully created a jenkins task with Git SCM checking out a git repository with some git sub modules include. (I use git client plugin V 2.0.0 , with advanced submodules behaviors - "Recursively update submodules" - checked and "Update tracking submodules to tip of branch" - checked ). Job gets build successfully. Later on I removed some sub modules from the list, for example:{noformat}git submodule deinit some-projectgit rm some-projectgit commit -a -m "remove this module"git push{noformat}However when I run new build I get and error from the plugin:{noformat}hudson.plugins.git.GitException: Command "/usr/bin/git submodule update --init --recursive --remote some-project" returned status code 1:stdout: stderr: error: pathspec 'some-project' did not match any file(s) known to git.{noformat}I assume that git plugin should respect changes at superproject git repository , like removing some sub modules from there. But it seems it does not. Or I miss something. As far as taking a console git client it succeed on cases when sub modules gets removed:{noformat}git submodule initgit submodule syncgit submodule update --remote --init --merge --recursive {noformat}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39350) Git client plugin does respect changes at .gitmodules list ( e.g. removing git sub modules )
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39350 Git client plugin does respect changes at .gitmodules list ( e.g. removing git sub modules ) Change By: Alexey Melezhik Summary: Plugin Git client plugin does respect changes at .gitmodules list ( e.g. removing git sub modules ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39350) Plugin does respect changes at .gitmodules list
Title: Message Title Alexey Melezhik created an issue Jenkins / JENKINS-39350 Plugin does respect changes at .gitmodules list Issue Type: Bug Assignee: Mark Waite Components: git-client-plugin Created: 2016/Oct/28 11:52 AM Priority: Major Reporter: Alexey Melezhik I successfully created a jenkins task with Git SCM checking out a git repository with some git sub modules include. (I use git plugin, with advanced submodules behaviors - "Recursively update submodules" - checked and "Update tracking submodules to tip of branch" - checked ). Job gets build successfully. Later on I removed some sub modules from the list, for example: git submodule deinit some-project git rm some-project git commit -a -m "remove this module" git push However when I run new build I get and error from the plugin: hudson.plugins.git.GitException: Command "/usr/bin/git submodule update --init --recursive --remote some-project" returned status code 1: stdout: stderr: error: pathspec 'some-project' did not match any file(s) known to git. I assume that git plugin should respect changes at superproject git repository , like removing some sub modules from there. But it seems it does not. Or I miss something. As far as taking a console git client it succeed on cases when sub modules gets removed:
[JIRA] (JENKINS-39350) Plugin does respect changes at .gitmodules list ( e.g. removing git sub modules )
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39350 Plugin does respect changes at .gitmodules list ( e.g. removing git sub modules ) Change By: Alexey Melezhik Summary: Plugin does respect changes at .gitmodules list ( e.g. removing git sub modules ) Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39253) Clarification on Git submodules case
Title: Message Title Alexey Melezhik commented on JENKINS-39253 Re: Clarification on Git submodules case If the job's SCM (git) URL "loosely matches" that of the git repository listed inside the BitBucket-provided payload, AND Probably this is not true if: job's SCM (git) URL is MAIN repository URL and git repository listed inside the BitBucket-provided is a _some git sub module URL _ ... Correct me if I am wrong ... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39253) Clarification on Git submodules case
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39253 Clarification on Git submodules case Change By: Alexey Melezhik Hi ! Not sure if this an issue. But after reading bitbucket plugin docs I am not clear if plugin works properly for jobs configured as Git SCM ( Git plugin ) with sub modules.The history of this question is we have about ~ 300 bitbucket git repositories get together as git sub modules into a single git repository, lets call it MAIN repository. So obviously we *** don not want *** to have a 300 jenkins jobs ( each for every repo ) as every repo is just a logical unit of whole project/system, we want to trigger some actions when whatever repository listed as git submodule at MAIN repository is updated. So I have a following job setup:* Git SCM for MAIN repository with sub modules update enabled* Some builds steps to be taken when MAIN repos is updated ( read when one of git sub modules is updated )I am till not sure if bitbucket plugin trigger my job build using so called URLs smart "loosely matching " , as obviously those URLS - are git sub modules URLs , not MAIN repo one... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39253) Clarification on Git submodules case
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39253 Clarification on Git submodules case Change By: Alexey Melezhik Hi ! Not sure if it is the this an issue. But after reading bitbucket plugin docs I am not clear if plugins plugin works properly for jobs configured with as Git SCM ( git Git plugin ) with sub modules.The history of this question is we have about ~ 300 bitbucket git repositories get together as git sub modules into a single git rep mdo repository , lets call it MAIN repository. So I obviously we *** don 't not want obviously *** to have a 300 jenkins jobs ( each for every repo , ) as every repo is just a logical unit of whole project /system , I we want to trigger some action actions when whatever repository listed as git submodule at MAIN repository is updated. So I have a following job setup:* Git SCM for MAIN repository with sub modules update enabled * Some builds steps to be taken when MAIN repos is updated ( read when one of git sub modules is updated ) I am till not sure if bitbucket plugin trigger my job build using so called URLs smart matching, as obviously those URLS - are git sub modules URLs , not MAIN repo one... Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39253) Clarification on Git submodules case
Title: Message Title Alexey Melezhik updated an issue Jenkins / JENKINS-39253 Clarification on Git submodules case Change By: Alexey Melezhik Summary: clerafiaction Clarification on Git submodules case Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-39253) clerafiaction on Git submodules case
Title: Message Title Alexey Melezhik created an issue Jenkins / JENKINS-39253 clerafiaction on Git submodules case Issue Type: Task Assignee: Unassigned Components: bitbucket-plugin Created: 2016/Oct/25 8:45 PM Priority: Minor Reporter: Alexey Melezhik Hi ! Not sure if it is the issue. But after reading bitbucket plugin docs I am not clear if plugins works properly for jobs configured with Git SCM ( git plugin ) with sub modules. The history of this question is we have about ~ 300 bitbucket git repositories get together as git sub modules into a single git rep mdo, lets call it MAIN repository. So I don't want obviously have a 300 jenkins jobs each for every repo, as every repo is just a logical unit of whole project, I want to trigger some action when whatever repository listed as git submodule at MAIN repository updated. So I have job setup: Git SCM for MAIN repository with sub modules update enabled I am till not sure if bitbucket plugin trigger my job build using so called URLs smart matching, as obviously those URLS - are git sub modules URLs , not MAIN repo one...
