Skip to content
This repository was archived by the owner on Apr 24, 2023. It is now read-only.
Open
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
41 changes: 41 additions & 0 deletions cli/RELEASING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
Releasing Cook Executor
=======================

Cook CLI is released on [PyPI](https://pypi.org/project/cook-executor/)

Prerequisites
-------------
Ensure you can build the cli following the instructions in README.md

Install `twine`:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Also install wheel to be able to bdist_wheel

```bash
pip3 install twine
```

Update version number
------------
Look at setup.py, and edit the version number which may reference another python variable to be edited.

Test Release
------------
Since PyPI does not allow modifying releases, it can be useful to test a release using their test instance.
```bash
rm -rf dist/*
python3 setup.py sdist bdist_wheel
python3 -m twine upload --repository-url https://test.pypi.org/legacy/ dist/*
```
Then, in a separate virtualenv for testing:
```bash
pip3 install --index-url https://test.pypi.org/simple/ --no-deps cook-executor==$VERSION
Copy link
Collaborator

Choose a reason for hiding this comment

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

CLI is cook-client

Copy link
Collaborator

Choose a reason for hiding this comment

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

(this is a few places in this file, btw)

pip3 install # install any other required dependencies from the main pypi repo
Copy link
Collaborator

Choose a reason for hiding this comment

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

This part was confusing to me. I ended up installing cook-client
pip3 install cook-client
and then using the full path to the cs in my virtual env. Is that what you meant?

```
If there is an issue with the release, you can just release another version. They are GC-ed periodically from the test instance.

Production Release
------------------
When you're ready to release the final version, just build and upload to the standard PyPI repo.
```bash
rm -rf dist/*
python3 setup.py sdist bdist_wheel
python3 -m twine upload dist/*
```
40 changes: 40 additions & 0 deletions jobclient/python/RELEASING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
Releasing Cook Executor
=======================

Cook's Jobclient API is released on [PyPI](https://pypi.org/project/cook-executor/)
Copy link
Collaborator

Choose a reason for hiding this comment

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

cook-client-api, not cook-executor


Prerequisites
-------------
Ensure you can build it following the instructions in README.md

Install `twine`:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Also install wheel to be able to bdist_wheel

```bash
pip3 install twine
```
Update version number
------------
Look at setup.py, and edit the version number which may reference another python variable to be edited.

Test Release
------------
Since PyPI does not allow modifying releases, it can be useful to test a release using their test instance.
```bash
rm -rf dist/*
python3 setup.py sdist bdist_wheel
python3 -m twine upload --repository-url https://test.pypi.org/legacy/ dist/*
```
Then, in a separate virtualenv for testing:
```bash
pip3 install --index-url https://test.pypi.org/simple/ --no-deps cook-executor==$VERSION
pip3 install # install any other required dependencies from the main pypi repo
```
If there is an issue with the release, you can just release another version. They are GC-ed periodically from the test instance.

Production Release
------------------
When you're ready to release the final version, just build and upload to the standard PyPI repo.
```bash
rm -rf dist/*
python3 setup.py sdist bdist_wheel
python3 -m twine upload dist/*
```
41 changes: 41 additions & 0 deletions sidecar/RELEASING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,41 @@
Releasing Cook Executor
Copy link
Collaborator

Choose a reason for hiding this comment

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

This file still says executor in some places

=======================

Cook Sidecar is released on [PyPI](https://pypi.org/project/cook-executor/)
Copy link
Collaborator

Choose a reason for hiding this comment

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

cook-sidecar, not cook-executor


Prerequisites
-------------
Ensure you can build the sidecar following the instructions in README.md

Install `twine`:
Copy link
Collaborator

Choose a reason for hiding this comment

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

Also install wheel to be able to bdist_wheel

```bash
pip3 install twine
```

Update version number
------------
Look at setup.py, and edit the version number which may reference another python variable to be edited.

Test Release
------------
Since PyPI does not allow modifying releases, it can be useful to test a release using their test instance.
```bash
rm -rf dist/*
python3 setup.py sdist bdist_wheel
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not sure if this is worth mentioning or if this is just some Python distribution basics that I missed, but bdist_wheel isn‘t available unless you pip install wheel

python3 -m twine upload --repository-url https://test.pypi.org/legacy/ dist/*
```
Then, in a separate virtualenv for testing:
```bash
pip3 install --index-url https://test.pypi.org/simple/ --no-deps cook-executor==$VERSION
Copy link
Collaborator

Choose a reason for hiding this comment

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

cook-sidecar, not cook-executor

pip3 install # install any other required dependencies from the main pypi repo
```
If there is an issue with the release, you can just release another version. They are GC-ed periodically from the test instance.

Production Release
------------------
When you're ready to release the final version, just build and upload to the standard PyPI repo.
```bash
rm -rf dist/*
python3 setup.py sdist bdist_wheel
python3 -m twine upload dist/*
```