[release-monitoring] Combine poetry and pip for build
The poetry install is creating an editable installation, which is not what we want. Let's instead use pip for installation and poetry to build the package and create requirements.txt. Signed-off-by: Michal Konečný <mkonecny@redhat.com>
This commit is contained in:
parent
c5fa0f91f1
commit
c20364bc7a
1 changed files with 5 additions and 3 deletions
|
@ -55,8 +55,7 @@ items:
|
|||
pushd anitya && \
|
||||
{% if env == 'staging' %}
|
||||
git checkout staging && \
|
||||
poetry config virtualenvs.create false && \
|
||||
poetry install && \
|
||||
poetry export -f requirements.txt | pip-3 install -r /dev/stdin && \
|
||||
{% else %}
|
||||
git checkout production && \
|
||||
python3 setup.py install && \
|
||||
|
@ -68,7 +67,10 @@ items:
|
|||
mkdir -p ../anitya/static/docs/ && \
|
||||
cp -r _build/html/* ../anitya/static/docs/ && \
|
||||
popd && \
|
||||
{% if env != 'staging' %}
|
||||
{% if env == 'staging' %}
|
||||
poetry build && \
|
||||
pip-3 install dist/*.whl && \
|
||||
{% else %}
|
||||
python3 setup.py install && \
|
||||
pip-3 install . && \
|
||||
{% endif %}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue