scikit-ci
scikit-ci enables a centralized and simpler CI configuration for Python extensions.
By having appveyor.yml, azure-pipelines.yml, circle.yml and .travis.yml calling the same scikit-ci command-line executable, all the CI steps for all service can be fully described in one scikit-ci.yml configuration file.
Latest Release
Versions |
Downloads |
|---|---|
|
|
|
Build Status
Linux |
macOS |
Windows |
|
|---|---|---|---|
PyPI |
|
|
|
Overall Health
Miscellaneous
Free software: Apache Software license
Documentation: http://scikit-ci.readthedocs.org
Source code: https://github.com/scikit-build/scikit-ci
Mailing list: https://groups.google.com/forum/#!forum/scikit-build
History
scikit-ci was initially developed in May 2016 by Omar Padron to facilitate the continuous integration of the scikit-build project.
At that time, it already consisted of a driver script calling methods specific to each continuous integration service. By having each CI service calling the same driver script, there was no need to deal with implementing install/test/build steps over and over in different scripting languages (power shell, shell or windows batch). Instead all code was implemented in python code leveraging the subprocess module.
Later in early September 2016, with the desire to setup cross-platform continuous integration for other project and avoid duplication or maintenance hell, a dedicated repository was created by Jean-Christophe Fillion-Robin. By simply cloning the repository, it was possible to more easily enable CI for other projects.
While this was an improvement, all the steps were still hardcoded in the driver scripts, the project was not easily customizable. More could be done to improve the user experience.
Finally, in late September 2016, all hardcoded code was moved into standalone executable python scripts. Then, Jean-Christophe came up with the concept of scikit-ci.yml configuration file. This configuration file allows to describe the commands and environment for each step (install, test and build) specific to a project and associated continuous integration services.
Metadata
Release files for scikit-ci 0.21.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-0.21.0.tar.gz | 56.8 kB | Without provenance | Details for scikit-ci-0.21.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| scikit_ci-0.21.0-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for scikit_ci-0.21.0-py2.py3-none-any.whl |
Total release size: 72.9 kB
Release files / scikit-ci-0.21.0.tar.gz
| Download URL | scikit-ci-0.21.0.tar.gz |
|---|---|
| Size | 56.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91986c8cb29710a1bfdd109ea2d60d9fc76109217ea5b853fa84d7daa39e238e
|
|
BLAKE2b-256 checksum How to use checksums |
b58029b44fab7b878efc029cebceffe4f91bdd4d8d6bcc027880155eb1785385
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.4.3+
|
Release files / scikit_ci-0.21.0-py2.py3-none-any.whl
| Download URL | scikit_ci-0.21.0-py2.py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
d3c282f2adf2aead5f24b086600526a53bf8dd2f08bf3394d60619d3cbf0b64a
|
|
BLAKE2b-256 checksum How to use checksums |
39fd649b63a3c9e0e0545adaa7fa20b4036297969f9eca15eabe81555bc81583
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.13.0 pkginfo/1.5.0.1 requests/2.21.0 setuptools/41.0.1 requests-toolbelt/0.9.1 tqdm/4.32.1 CPython/3.4.3+
|
Security for scikit-ci 0.21.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.