OSSForks/pytorch
1
0
Fork 0
mirror of https://github.com/zebrajr/pytorch.git synced 2025-12-06 12:20:52 +01:00
Code Issues Actions 38 Packages Projects Releases Wiki Activity
06a156efc7
pytorch/scripts/release
History
Eli Uriegas 67f765328b scripts: Change promote pypi to be more flexible (#53774) 
Summary:
Promotion to PyPI should be more flexible to allow any package to be
promoted to PyPI.

After we re-added a version suffix to cuda 10.2 it means that this
script needs to have the flexibility to designate which platform and
which version suffix will actually be uploaded to PyPI

Should coincide with https://github.com/pytorch/builder/pull/678

Signed-off-by: Eli Uriegas <eliuriegas@fb.com>

Pull Request resolved: https://github.com/pytorch/pytorch/pull/53774

Reviewed By: jbschlosser

Differential Revision: D27052347

Pulled By: seemethere

fbshipit-source-id: 71129cc5afbd7de448c970ef721bc979c3420586
2021-03-15 13:30:21 -07:00
..
anaconda-prune ci: Add anaconda pruning to CI pipeline (#44651) 2020-09-15 10:51:05 -07:00
promote scripts: Change promote pypi to be more flexible (#53774) 2021-03-15 13:30:21 -07:00
README.md .circleci: Add simple backup and restore solution for RCs (#38690) 2020-05-21 13:09:12 -07:00
restore-backup.sh .circleci: Add simple backup and restore solution for RCs (#38690) 2020-05-21 13:09:12 -07:00

README.md

PyTorch Release Scripts

These are a collection of scripts that are to be used for release activities.

NOTE: All scripts should do no actual work unless the DRY_RUN environment variable is set to disabled. The basic idea being that there should be no potential to do anything dangerous unless DRY_RUN is explicitly set to disabled.

Requirements to actually run these scripts

  • AWS access to pytorch account
  • Access to upload conda packages to the pytorch conda channel
  • Access to the PyPI repositories

Promote

These are scripts related to promotion of release candidates to GA channels, these can actually be used to promote pytorch, libtorch, and related domain libraries.

Usage

Usage should be fairly straightforward and should actually require no extra variables if you are running from the correct git tags. (i.e. the GA tag to promote is currently checked out)

PACKAGE_TYPE and PACKAGE_NAME can be swapped out to promote other packages.

Promoting pytorch wheels

promote/s3_to_s3.sh

Promoting libtorch archives

PACKAGE_TYPE=libtorch PACKAGE_NAME=libtorch promote/s3_to_s3.sh

Promoting conda packages

promote/conda_to_conda.sh

Promoting wheels to PyPI

WARNING: These can only be run once and cannot be undone, run with caution

promote/wheel_to_pypi.sh

Restoring backups

All release candidates are currently backed up to s3://pytorch-backup/${TAG_NAME} and can be restored to the test channels with the restore-backup.sh script.

Which backup to restore from is dictated by the RESTORE_FROM environment variable.

Usage

RESTORE_FROM=v1.5.0-rc5 ./restore-backup.sh