scikit-ci-addons
scikit-ci-addons is a command line tool and a set of scripts useful to help drive the CI of projects leveraging services like Appveyor, CircleCI, or TravisCI.
Originally developed to help install prerequisites for building Python extension, it is now useful to support other type of projects.
Latest Release
Versions |
Downloads |
|---|---|
|
|
Build Status
Linux |
MacOSX |
Windows |
|
|---|---|---|---|
PyPI |
|
|
|
Overall Health
Miscellaneous
Free software: Apache Software license
Documentation: http://scikit-ci-addons.readthedocs.org
Source code: https://github.com/scikit-build/scikit-addons
Mailing list: https://groups.google.com/forum/#!forum/scikit-build
History
scikit-ci-addons was initially developed in May 2016 by Omar Padron to facilitate the continuous integration of the scikit-build project.
At that time, it consisted of code directly embedded in the CI script used in scikit-build project.
Then, in early September 2016, with the desire to setup cross-platform continuous integration for other project and avoid duplication or maintenance hell, the code was factored out by Jean-Christophe Fillion-Robin into a set of reusable scripts available in the scikit-ci project. By simply cloning the repository, it was possible to more easily enable CI for other projects.
While this was an improvement, this prevented the distribution of standalone and simple scikit-ci package. To better separate concerns and facilitate testing and maintenance, in late September 2016, the scripts were moved into their own project and scikit-ci-addons was born.
Finally, in late October 2016, Jean-Christophe came up with the concept of scikit-ci-addons command line tool allowing to execute the scripts (or add-ons) distributed within the scikit-ci-addons package.
Release files for scikit-ci-addons 0.25.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 |
|---|---|---|---|---|
| scikit-ci-addons-0.25.0.tar.gz | 127.9 kB | Without provenance | Details for scikit-ci-addons-0.25.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scikit_ci_addons-0.25.0-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for scikit_ci_addons-0.25.0-py2.py3-none-any.whl |
Total release size: 173.5 kB
Release files / scikit-ci-addons-0.25.0.tar.gz
| Download URL | scikit-ci-addons-0.25.0.tar.gz |
|---|---|
| Size | 127.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9f5886ab0570bbb541194a71242cf5e4eef4821d3a72b7e4d51432ccc84bdc51
|
|
BLAKE2b-256 checksum How to use checksums |
44682a18f84887b3f8ea0bbbe32f14032a05912e96636d245d7c3ca4c69661ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.20.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.5.0+
|
Release files / scikit_ci_addons-0.25.0-py2.py3-none-any.whl
| Download URL | scikit_ci_addons-0.25.0-py2.py3-none-any.whl |
|---|---|
| Size | 45.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
a2d213d505c7eb072b5a19a83991d623a891358c805a7a4a86ca905692c7f9e7
|
|
BLAKE2b-256 checksum How to use checksums |
cb841fb0241578111d9797c8fc88bb46848ed85be82818904e4f04dd52c31b42
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.20.1 setuptools/40.2.0 requests-toolbelt/0.8.0 tqdm/4.23.4 CPython/3.5.0+
|
Security for scikit-ci-addons 0.25.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.
