| @jreed:matrix.org | Okay. Zuul Merged! I'll do my best to next get this repo converted over to a python package. That means the files/folders will move around. I want to say I'll do this today, but it might take me a while. | 13:59 |
|---|---|---|
| @jreed:matrix.org | Are there any pressures to finish sooner? | 13:59 |
| @jreed:matrix.org | ... I know I've been asking for everyone to hold off adding new code. | 14:00 |
| @brunomuniz:matrix.org | No, don't worry. Let's work together on this on what's best for all of us. | 14:00 |
| @brunomuniz:matrix.org | I like the idea of packaging and having someone with experience taking this step is the best approach, I think. | 14:01 |
| @jreed:matrix.org | I've never put a package out on pypi.org before, but to start one could pip install with the repo URL. | 14:02 |
| @jreed:matrix.org | Cool. Thanks for understanding :) | 14:03 |
| @fungicide:matrix.org | once you have a functional, installable package and can, for example, use https://pypi.org/p/build to locally create an sdist and wheel, then publication to pypi is quite trivial. there are release jobs already defined in zuul you can simply add to your project to publish it to pypi every time you push a new signed git tag to gerrit | 14:07 |
| @jreed:matrix.org | oh nice. Thanks. | 14:11 |
| @jreed:matrix.org | I created another task on the storyboard for this step so we don't loose track of it. | 14:13 |
| @fungicide:matrix.org | https://zuul-ci.org/docs/zuul-jobs/latest/python-jobs.html#job-python-upload-pypi | 15:40 |
| @fungicide:matrix.org | you could either copy the way the https://zuul.opendev.org/t/openstack/job/release-openstack-python job is configured supplying your own credentials, or delegate permission to the `openstackci` account on pypi and just use that job directly | 15:46 |
| @fungicide:matrix.org | i don't know if starlingx currently has any existing python-based projects it publishes to pypi, but if it does then probably just copy however they're set up | 15:47 |
| @tcervi:matrix.org | Hi everyone, | 17:27 |
| last week we merged-back the f/antelope branch to the main branch and we had no issues on the first builds after the merge. | ||
| There was a lot of work done to update our build system in order to be prepared to build the same package in different versions (i.e., using build layers) and solving the different dependency chains. | ||
| I am happy to announce that we now have the f/antelope changes already in main branch and building successfully for a while 😁 | ||
| The build jobs are already reflecting the manifest separation between StarlingX (ISO) and StarlingX OpenStack (application). | ||
| Many thanks to the build team scott.little and Davlet, and to the stx-openstack distro team lutimura Lucas de Ataides rleite | ||
| 🎉🎉🚀 | ||
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!