[Starlingx-discuss] SCM: repo projects revision control

Liu, Changcheng changcheng.liu at intel.com
Wed Dec 5 01:14:23 UTC 2018


Hi Erich,
   Do you know which is latest stable version that Ceph could work well on it?

   I need set the "revision" item for every project as many as possible
   to fix code repository base.

B.R.
Changcheng

On 00:12 Wed 05 Dec, Cordoba Malibran, Erich wrote:
> Hi Liu, 
> 
> I think there are two ways to checkout a specific revision in all
> projects: 
> 
> 1) By using a tag/branch: This should exist in the all the
> repositories. For example, you can get the code for the r/2018.10
> release setting the default revision:
> 
> <default remote="starlingx" revision="r/2018.10" />
> 
> Which BTW doesn't exist in the default.xml for r/2018.10, we need to
> fix that.
> 
> 2) Setting a revision per project: This is painful, but you can set a
> revision for every repository: 
> 
> <project remote="starlingx"  name="stx-nfv.git" path="cgcs-
> root/stx/stx-nfv" revision="r/2018.10" />
> 
> Also, you can create/modify your own manifest.xml with the repo tool,
> using repo start and other subcommands[0]. The only requirement is that
> the manifest.xml should live in a git repository to use repo init.
> 
> I hope this can help.
> 
> -Erich
> 
> [0] https://source.android.com/setup/develop/repo
> 
> 
> 
> On Tue, 2018-12-04 at 01:11 +0000, Liu, Changcheng wrote:
> > Hi Scott & Dean,
> >      Is there any way for developers get the exactly same stx source
> > code after running below commands?
> > repo init -u https://git.starlingx.io/stx-manifest -m default.xml
> > repo sync
> >  
> > Currently, some projects are set to be fixed tag/version in
> > .repo/manifests/default.xml e.g. kubernetes.git
> >     1 +---  5 lines: <?xml version="1.0" encoding="UTF-8"?>--------
> > ------------------------
> >     6   <remote name="hpe-storage" fetch="https://github.com/hpe-stor
> > age" />
> >     7   <remote name="kubernetes" fetch="https://github.com/kubernete
> > s" />
> >     8   <remote name="docker" fetch="https://github.com/docker" />
> >     9 +-- 93 lines: <remote name="calico" fetch="https://github.com/p
> > rojectcalico" />------
> >   102   <!-- Kuberneties  -->
> >   103   <project remote="kubernetes" revision="refs/tags/v1.9.6"
> > name="kubernetes.git" path="cgcs-root/stx/git/kubernetes"/>
> >   104   <project remote="kubernetes" revision="refs/tags/v1.8.3"
> > name="dashboard.git" path="cgcs-root/stx/git/kube-dashboard"/>
> >   105 +--  5 lines: <project remote="kubernetes"
> > revision="refs/tags/1.14.8" name="dns.git" path="cgcs-
> > root/stx/git/kube-dns"/>--
> >  
> >     However, some projects are always moving ahead without setting
> > “revision” item.
> >  
> > B.R.
> > Changcheng
> >  
> >  
> > _______________________________________________
> > Starlingx-discuss mailing list
> > Starlingx-discuss at lists.starlingx.io
> > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss



More information about the Starlingx-discuss mailing list