Would we want to publish tarballs on mirrors.starlingx.cengn.ca as part of the build process? Tarball would be updated nightly, rather than with every update as a zuul based solution would have it. e.g. http://mirror.starlingx.cengn.ca/mirror/starlingx/<branch>/centos/<timestamp>/outputs/tarballs/<repo-name>-<branch>.tar.gz or only publish the latest on branch... an in a structure more like that seen in http://tarballs.openstack.org ... http://mirror.starlingx.cengn.ca/mirror/starlingx/tarballs/<repo-name>/<repo-name>-<branch>.tar.gz On 18-11-21 10:14 AM, Arce Moreno, Abraham wrote:
Hi all,
As a result of our review for story 2003736 [0], here you have our first level of findings but most important a request for comments:
[ Objective ]
"Create a new zuul check job to create tarballs from stx projects"
Taking the existing OpenStack tarball infrastructure, we have the url tarballs @ openstack org [1] so initial idea would be to host StarlingX tarballs in tarballs @ starlingx io [2]
- Any question on the objective? Anything to highlight? - Any other preference where to host the tarballs?
[ Zuul ]
There are some examples of jobs related to tarballs:
- publish-openstack-artifacts - publish-openstack-python-branch-tarball - build-openstack-puppet-tarball - publish-openstack-puppet-branch-tarball
Should we target a reuse of existing jobs, probably not listed above or create a new set of jobs?
- build-starlingx-tarball - publish-starlingx-tarball
Getting your feedback in these first 2 questions will allow us to get a solid direction for the rest of the week.
[0] https://storyboard.openstack.org/#!/story/2003736 [1] http://tarballs.openstack.org/ [2] http://tarballs.starlingx.io/
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss