Skip to content
Snippets Groups Projects
Commit ae02b138 authored by Anton Joubert's avatar Anton Joubert
Browse files

Move metadata validation to CI build step

katversion needs git, so the validation also needs git.  Move the
metadata validation to the build step, rather than installing git
again in the publish step.  The dist files from the build step are
the ones that get published, so OK to move the check there.
parent d39640db
No related branches found
No related tags found
No related merge requests found
...@@ -33,6 +33,7 @@ build wheel: ...@@ -33,6 +33,7 @@ build wheel:
# TODO: consider moving git installation to ska-python-buildenv Dockerfile # TODO: consider moving git installation to ska-python-buildenv Dockerfile
- apt-get -y update - apt-get -y update
- apt-get install -y git --no-install-recommends - apt-get install -y git --no-install-recommends
- scripts/validate-metadata.sh
- python setup.py sdist bdist_wheel - python setup.py sdist bdist_wheel
artifacts: artifacts:
paths: paths:
...@@ -88,8 +89,6 @@ publish to nexus: ...@@ -88,8 +89,6 @@ publish to nexus:
TWINE_USERNAME: $TWINE_USERNAME TWINE_USERNAME: $TWINE_USERNAME
TWINE_PASSWORD: $TWINE_PASSWORD TWINE_PASSWORD: $TWINE_PASSWORD
script: script:
# Check metadata requirements
- scripts/validate-metadata.sh
- pip install twine - pip install twine
- twine upload --repository-url $PYPI_REPOSITORY_URL dist/* - twine upload --repository-url $PYPI_REPOSITORY_URL dist/*
only: only:
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Please register or to comment