Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions RELEASING.rst
Original file line number Diff line number Diff line change
@@ -1,6 +1,10 @@
Release Procedure
-----------------

#. Dependening on the magnitude of the changes in the release, consider testing
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps we should have a workflow which runs them all in parallel? This workflow can then be triggered manually and perhaps also in a cron and/or merge with main.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that would be good, but I am too lazy to do that ATM, but wanted to at least make it possible to test locally for now.

some of the large downstream users of pluggy against the upcoming release.
You can do so using the scripts in the ``downstream/`` directory.

#. From a clean work tree, execute::

tox -e release -- VERSION
Expand Down
6 changes: 6 additions & 0 deletions downstream/.gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
/conda/
/datasette/
/devpi/
/hatch/
/pytest/
/tox/
2 changes: 2 additions & 0 deletions downstream/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,2 @@
This directory contains scripts for testing some downstream projects
against your current pluggy worktree.
12 changes: 12 additions & 0 deletions downstream/conda.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
#!/usr/bin/env bash
set -eux -o pipefail
if [[ ! -d conda ]]; then
git clone https://github.com/conda/conda
fi
pushd conda && trap popd EXIT
git pull
set +eu
source dev/start
set -eu
pip install -e ../../
pytest -m "not integration and not installed"
10 changes: 10 additions & 0 deletions downstream/datasette.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
#!/usr/bin/env bash
set -eux -o pipefail
if [[ ! -d datasette ]]; then
git clone https://github.com/simonw/datasette
fi
pushd datasette && trap popd EXIT
git pull
python -m venv venv
venv/bin/pip install -e .[test] -e ../..
venv/bin/pytest
13 changes: 13 additions & 0 deletions downstream/devpi.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
#!/usr/bin/env bash
set -eux -o pipefail
if [[ ! -d devpi ]]; then
git clone https://github.com/devpi/devpi
fi
pushd devpi && trap popd EXIT
git pull
python -m venv venv
venv/bin/pip install -r dev-requirements.txt -e ../..
venv/bin/pytest common
venv/bin/pytest server
venv/bin/pytest client
venv/bin/pytest web
10 changes: 10 additions & 0 deletions downstream/hatch.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
#!/usr/bin/env bash
set -eux -o pipefail
if [[ ! -d hatch ]]; then
git clone https://github.com/pypa/hatch
fi
pushd hatch && trap popd EXIT
git pull
python -m venv venv
venv/bin/pip install -e . -e ./backend -e ../..
venv/bin/hatch run dev
10 changes: 10 additions & 0 deletions downstream/pytest.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
#!/usr/bin/env bash
set -eux -o pipefail
if [[ ! -d pytest ]]; then
git clone https://github.com/pytest-dev/pytest
fi
pushd pytest && trap popd EXIT
git pull
python -m venv venv
venv/bin/pip install -e .[testing] -e ../..
venv/bin/pytest
9 changes: 9 additions & 0 deletions downstream/tox.sh
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
#!/usr/bin/env bash
set -eux -o pipefail
if [[ ! -d tox ]]; then
git clone https://github.com/tox-dev/tox
fi
pushd tox && trap popd EXIT
python -m venv venv
venv/bin/pip install -e .[testing] -e ../..
venv/bin/pytest