[Starlingx-discuss] StarlingX Master Branch Successful Compilation

[Arce Moreno, Abraham]

> This is great! Can we have a manifest with the commitID associated for this
> particular build?

Sure Cindy. Here you have 2 manifests of 2 successful builds, reason? 
I am somehow confused about the content of our manifest with the information
found at our Developer Guide [0] based on how we initialized the manifest:

    repo init -u https://git.starlingx.io/stx-manifest.git -m default.xml

I appreciate community corrections please. I was assuming this was the master 
but default revision is pointing to m/2018.07. Anyway, I went an build again changing
the default revision to master. Next see the details and links, 
repo was created using the line:

    repo manifest -r -o my-manifest.xml

[Details / Links]

Default Revision m/2018.07 [1]
The resulting manifest [2]
    stx-manifest/tree/default.xml content:
        <remote name="stx-staging" fetch="https://github.com/starlingx-staging"/>
        <default revision="m/2018.07"/>
        <project remote="starlingx" revision="m/2018.07" name="stx-tools.git" path="stx-tools"/>

Default Revision Master [3]
The resulting manifest [4]
  stx-manifest/tree/default.xml?h=m/2018.07 content:
      <remote name="stx-staging" fetch="https://github.com/starlingx-staging"/>
      <default revision="master" remote="stx-staging"/>
      <project remote="starlingx" revision="master" name="stx-tools.git" path="stx-tools"/>

As an additional information, I complete a parallel build of StarlingX using a Digital Ocean virtual
machine. It took ~ 7 hours, the specs were: 2 vCPUs, RAM 4 GB, Disk 80 GB.

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide
[1] https://git.openstack.org/cgit/openstack/stx-manifest/tree/default.xml
[2] https://etherpad.openstack.org/p/stx-manifest-2018.07
[3] https://git.openstack.org/cgit/openstack/stx-manifest/tree/default.xml?h=m/2018.07
[4] https://etherpad.openstack.org/p/stx-manifest-master