Closed thompson318 closed 4 years ago
In GitLab by @ThomasDowrick on Nov 16, 2018, 13:28
changed the description
In GitLab by @ThomasDowrick on Nov 16, 2018, 13:29
changed the description
In GitLab by @ThomasDowrick on Nov 19, 2018, 17:24
I've got this up and running for sckit-surgeryimage. If a commit is tagged, then the CI Pipeline will have a manual step to deploy to PyPI.
I've also updated the Wiki page with some more info: https://weisslab.cs.ucl.ac.uk/WEISS/PlatformManagement/SNAPPY/wikis/pushing-package-to-pypi
Do we want to make this part of PythonTemplate, or implement it manually for projects that need it?
@MattClarkson @StephenThompson Any further thoughts, or can we close this now?
In GitLab by @MattClarkson on Nov 20, 2018, 05:00
assigned to @ThomasDowrick
In GitLab by @MattClarkson on Nov 20, 2018, 05:01
Please can we add it to Python Template?
THanks
In GitLab by @StephenThompson on Nov 20, 2018, 09:03
Yes, I agree it would be good to add it to the template.
In GitLab by @ThomasDowrick on Nov 20, 2018, 17:22
I have added this to the template (https://weisslab.cs.ucl.ac.uk/WEISS/SoftwareRepositories/PythonTemplate/commit/00eec0ff6dac0cc2e9077173e526da57373756d1) and tested it in a new cookiecutter project.
Until we move the software packages into a single Group, it is necessary to manually set the PYPI_USER and PYPI_PASS variables for any new projects, otherwise the deploy stage will fail on an authentication error.
In GitLab by @ThomasDowrick on Nov 20, 2018, 17:22
closed
In GitLab by @ThomasDowrick on Nov 16, 2018, 13:27
This can be a manual option in the pipeline, and only avaialable when a tagged version has been pushed to master.
Tom Doel provided this sample code below. $PYPI_USER and $PYPI_PASS need to be store as gitlab variables.