git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Michele Hallak <mhallak@iai.co.il>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: git projects with submodules in different sites - in txt format (:+(
Date: Tue, 2 Oct 2018 05:47:11 +0000	[thread overview]
Message-ID: <15774B2750A13244948B89FDD2FEC2EACF15C69A@EXS11.iai.co.il> (raw)

Hi,

I am getting out of idea about how to change the methodology we are using in order to ease our integration process... Close to despair, I am throwing the question to you...

We have 6 infrastructure repositories.
Each project is composed of 4 repositories, each one using one or two infrastructure repositories as sub-modules. (Not the same)

The infrastructure repositories are common to several projects and in the case we have to make change in the infrastructure for a specific project, we are doing it on a specific branch until properly merged.

Everything is fine (more or less) and somehow working.

Now, we have one project that will be developed in another site and with another git server physically separated from the main site.

I copied the infrastructure repositories in the new site and removed and add the sub-modules in order for them to point to the url in the separated git server.

Every 2 weeks, the remotely developed code has to be integrated back in the main site. 
My idea was to format GIT patches, integrate in the main site, tag the whole thing and ship back the integrated tagged code to the remote site.
... and now the nightmare starts:

Since the .gitmodules is different, I cannot have the same SHA and then same tag and I am never sure that the integrated code is proper.

May be there is a simple solution that I don't know about to my problem? Is there something else than GIT patches? Should I simply ship to the remote site the code as is and change the submodules each time?

Thanks a lot for trying to help me,

Michele



*********************************************************************************************** Please consider the environment before printing this email ! The information contained in this communication is proprietary to Israel Aerospace Industries Ltd. and/or third parties, may contain confidential or privileged information, and is intended only for the use of the intended addressee thereof. If you are not the intended addressee, please be aware that any use, disclosure, distribution and/or copying of this communication is strictly prohibited. If you receive this communication in error, please notify the sender immediately and delete it from your computer. Thank you. Visit us at: www.iai.co.il

             reply	other threads:[~2018-10-02  6:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02  5:47 Michele Hallak [this message]
2018-10-02 21:00 ` git projects with submodules in different sites - in txt format (:+( Philip Oakley
2018-10-03 13:37   ` Michele Hallak

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15774B2750A13244948B89FDD2FEC2EACF15C69A@EXS11.iai.co.il \
    --to=mhallak@iai.co.il \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).