A dev-pipeline plugin to add the build-order command.
build-order will provide information about the order components will be
built in various output formats.
Installation
The simplest way to install is using pip.
$ cd /path/to/dev-pipeline-build-order
$ pip3 installIf you don’t have pip available, you can run setup.py directly.
$ cd /path/to/dev-pipeline-build-order
$ python3 setup.py installYou’ll need scm plugins installed to do anything useful.
Documentation
Information about the build-order command is avaialble in the
documentation.
1 maintainer
Metadata
1 maintainer
Release files for dev-pipeline-build-order 0.4.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 | Actions |
|---|---|---|---|---|
| dev-pipeline-build-order-0.4.0.tar.gz | 4.1 kB | Without provenance | Details for dev-pipeline-build-order-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dev_pipeline_build_order-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for dev_pipeline_build_order-0.4.0-py3-none-any.whl |
Total release size: 11.0 kB
Release files / dev-pipeline-build-order-0.4.0.tar.gz
| Download URL | dev-pipeline-build-order-0.4.0.tar.gz |
|---|---|
| Size | 4.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3cbd864e47c142c0675a5f319549940f752a53a2bf5f703fc62e4bccf0b59b33
|
|
BLAKE2b-256 checksum How to use checksums |
7f257bb0b05e02b54c531100386dc31e877217ff811283038242d96ce783772d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/36.7.2 requests-toolbelt/0.8.0 tqdm/4.23.3 CPython/3.6.5
|
Release files / dev_pipeline_build_order-0.4.0-py3-none-any.whl
| Download URL | dev_pipeline_build_order-0.4.0-py3-none-any.whl |
|---|---|
| Size | 6.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
892aca70af70352861595bd8822f019091d13c1e4bbf9eac2e035cc76983360c
|
|
BLAKE2b-256 checksum How to use checksums |
2f79e0851c761a94ec5fc580efb9307bc3c651588c4c526c9da1699c74215032
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.18.4 setuptools/36.7.2 requests-toolbelt/0.8.0 tqdm/4.23.3 CPython/3.6.5
|
Security for dev-pipeline-build-order 0.4.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.
