Skip to content
This repository has been archived by the owner on Oct 11, 2024. It is now read-only.

updates for nm-magic-wand, nightly or release #247

Merged
merged 5 commits into from
May 17, 2024
Merged

Conversation

andy-neuma
Copy link
Member

@andy-neuma andy-neuma commented May 16, 2024

SUMMARY:

  • update GHA action nm-build-vllm to not install nm-magic-wand-nightly
  • update build script to not install nm-magic-wand-nightly (we might consider getting rid of this script altogether, since we aren't really using it)
  • remove unused GHA action nm-test-vllm. this has been superseded by nm-install-test-whl
  • update GHA action nm-install-test-whl to get version of nm-magic-wand if nm-magic-wand-nightly is not present
  • update setup.py to default generate "nightly" package and add option based on ENV to generate release package. this also includes managing the dependency on nm-magic-wand.
  • update set-env action to set ENV based on wf_category input
  • update "release" workflow to include all supported python versions
  • delete obsolete "gen-whl"

NOTES:

  • "magic-wand" is only a runtime dependency, so no need to install it during build phase.
  • this PR makes it so that we by default generate a "nightly" package with a "nightly" version number. if we want to generate a release package we'll need to specify wf_category as RELEASE.

TEST PLAN:
runs on remote push. verifying that wf_category set to RELEASE will generate appropriate package.

ran "build" workflow with wf_category set to RELEASE ... package looks properly named and versioned ... https://github.com/neuralmagic/nm-vllm/actions/runs/9129675592

the "remote push" defaulted to generating a "nightly" package ... please see ... https://github.com/neuralmagic/nm-vllm/actions/runs/9129665988

@@ -306,9 +307,28 @@ def find_version(filepath: str) -> str:
raise RuntimeError("Unable to find version string.")


# Neuralmagic packaging ENV's
Copy link
Collaborator

Choose a reason for hiding this comment

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

could these be added to nm-vllm/vllm/envs.py?

This is the central location for env vars - perhaps not b/c this is setup.py, but just thought I would ask

Copy link
Member Author

Choose a reason for hiding this comment

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

i can take a look

@andy-neuma andy-neuma merged commit d69a34a into main May 17, 2024
12 checks passed
@andy-neuma andy-neuma deleted the nightly-v-release branch May 17, 2024 18:21
andy-neuma added a commit that referenced this pull request May 17, 2024
SUMMARY:
* update GHA action `nm-build-vllm` to not install
`nm-magic-wand-nightly`
* update build script to not install `nm-magic-wand-nightly` (we might
consider getting rid of this script altogether, since we aren't really
using it)
* remove unused GHA action `nm-test-vllm`. this has been superseded by
`nm-install-test-whl`
* update GHA action `nm-install-test-whl` to get version of
`nm-magic-wand` if `nm-magic-wand-nightly` is not present
* update `setup.py` to default generate "nightly" package and add option
based on ENV to generate release package. this also includes managing
the dependency on `nm-magic-wand`.
* update `set-env` action to set ENV based on `wf_category` input
* update "release" workflow to include all supported python versions
* delete obsolete "gen-whl"

NOTES:
- "magic-wand" is only a runtime dependency, so no need to install it
during build phase.
- this PR makes it so that we by default generate a "nightly" package
with a "nightly" version number. if we want to generate a release
package we'll need to specify `wf_category` as `RELEASE`.

TEST PLAN:
runs on remote push. verifying that `wf_category` set to `RELEASE` will
generate appropriate package.

ran "build" workflow with `wf_category` set to `RELEASE` ... package
looks properly named and versioned ...
https://github.com/neuralmagic/nm-vllm/actions/runs/9129675592

the "remote push" defaulted to generating a "nightly" package ... please
see ... https://github.com/neuralmagic/nm-vllm/actions/runs/9129665988

---------

Co-authored-by: andy-neuma <andy@neuralmagic.com>
andy-neuma added a commit that referenced this pull request May 17, 2024
SUMMARY:
* update GHA action `nm-build-vllm` to not install
`nm-magic-wand-nightly`
* update build script to not install `nm-magic-wand-nightly` (we might
consider getting rid of this script altogether, since we aren't really
using it)
* remove unused GHA action `nm-test-vllm`. this has been superseded by
`nm-install-test-whl`
* update GHA action `nm-install-test-whl` to get version of
`nm-magic-wand` if `nm-magic-wand-nightly` is not present
* update `setup.py` to default generate "nightly" package and add option
based on ENV to generate release package. this also includes managing
the dependency on `nm-magic-wand`.
* update `set-env` action to set ENV based on `wf_category` input
* update "release" workflow to include all supported python versions
* delete obsolete "gen-whl"

NOTES:
- "magic-wand" is only a runtime dependency, so no need to install it
during build phase.
- this PR makes it so that we by default generate a "nightly" package
with a "nightly" version number. if we want to generate a release
package we'll need to specify `wf_category` as `RELEASE`.

TEST PLAN:
runs on remote push. verifying that `wf_category` set to `RELEASE` will
generate appropriate package.

ran "build" workflow with `wf_category` set to `RELEASE` ... package
looks properly named and versioned ...
https://github.com/neuralmagic/nm-vllm/actions/runs/9129675592

the "remote push" defaulted to generating a "nightly" package ... please
see ... https://github.com/neuralmagic/nm-vllm/actions/runs/9129665988

Co-authored-by: andy-neuma <andy@neuralmagic.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants