setuptools_scm_azure_pipelines
Description
A stupidly simple setuptools_scm plugin that generates
PEP-440 post-releases packages versions prefixed
with the Azure Pipelines ${BUILD_BUILDID} for builds that happen on non-tagged git commits.
BUILD_BUILID, or rather $(Build.BuildId) in the Azure Pipeline lingo, is the variable that is set
by Azure Pipelines when a build is running.
When this variable is present and you are using this tool, your package's version will be:
{tag}, e.g.1.2.3when you are building on a tag ("exact version"),{tag}.post{BUILD_BUILDID}, e.g.1.2.3.post12345when you are building an intermediate version ("on-commit"),
This allows your fellow developpers to get the "latest" version of a package, no matter what.
You might not want that to happen everytime, though. In that case, don't forget to pin you dependencies correctly using one of:
Usage
Usage in pyproject.toml
Set it up in pyproject.toml [build-system] section like this:
[build-system]
requires = ["setuptools>=45", "wheel", "setuptools_scm>=6.2", "setuptools_scm_azure_pipelines>=1.0"]
[tool.setuptools_scm]
local_scheme = "no-local-version"
version_scheme = "post-release-azure-build-id"
1 maintainer
Metadata
1 maintainer
Release files for setuptools-scm-azure-pipelines 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| setuptools_scm_azure_pipelines-0.1.0.tar.gz | 6.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| setuptools_scm_azure_pipelines-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 11.0 kB
Release files / setuptools_scm_azure_pipelines-0.1.0.tar.gz
| Download URL | setuptools_scm_azure_pipelines-0.1.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f3bcb08d2c960201668c7bd6469a47dea9db6e1d453727b7459512b5b17b8883
|
|
BLAKE2b-256 checksum How to use checksums |
41c91b24d7f36c544bba1818f58153333cab2eddcc01504912fe3ce959180780
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.8
|
Release files / setuptools_scm_azure_pipelines-0.1.0-py3-none-any.whl
| Download URL | setuptools_scm_azure_pipelines-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b976bc6b294592d20274c2a4c09ee2c0ceba17060879f4f17e941db294a60fde
|
|
BLAKE2b-256 checksum How to use checksums |
a5ac8c51feebc61e4c23473acaa8533304a42de4ad7205890a34c7dd2d62b5d1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/4.8.2 pkginfo/1.7.1 requests/2.26.0 requests-toolbelt/0.9.1 tqdm/4.62.3 CPython/3.9.8
|
Security for setuptools-scm-azure-pipelines 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
