============
|codacy|
|code-climate|
A tool to help manage projects with dependencies spread across repositories.
Inspiration
-----------
I work on several projects spread across repositories; some of these leverage
sub-repositories in some form, and it's led to additional complexity trying to
stay in sync (especially when dealing with merges, release lines, hot fixes,
and all the other fun things that happen in large software projects). The
goal here is to have a suite of scripts to help keep repositories in sync and
working well together, without the issues that sub-repositories introduce.
Installation
------------
Requirements
~~~~~~~~~~~~
dev-pipeline requires python3; python2 will not work.
>From PyPi
~~~~~~~~~
If a published version is good enough, you can install using pip_. PyPi_ has
all published versions, including alpha and beta releases.
.. code:: bash
$ pip3 install dev-pipeline
>From Source
~~~~~~~~~~~
If the version in PyPi_ isn't recent enough, you can install directoy from
source using pip_. Because dev-pipeline is spread across several repositories
(each tool and plugin is tracked separately), you'll need to install all of
them as well (see their documentation). Dependencies are listed in
`setup.py`_.
.. code:: bash
$ cd /path/to/dev-pipeline
$ pip3 install
If you don't have pip available, you can run :code:`setup.py` directly.
.. code:: bash
$ cd /path/to/dev-pipeline
$ python3 setup.py install
If the install completes without errors, then you're good to go.
Using
-----
The first thing you'll need to do is write a `build configuration`_. Once
you're ready, a build directory.
.. code:: bash
# configure with default settings
$ dev-pipeline configure
If everything went well, you're ready to build.
.. code:: bash
# enter whatever directory the configure step used
$ cd build
# bootstrap will both pull the package sources and build them
$ dev-pipeline bootstrap
That's it. Check the tool documentation for information on what's available.
.. |codacy| image:: https://api.codacy.com/project/badge/Grade/0d9cf1d52ca846dc99de6cc621dfeb7b
:target: https://www.codacy.com/app/snewell/dev-pipeline?utm_source=github.com&utm_medium=referral&utm_content=dev-pipeline/dev-pipeline&utm_campaign=Badge_Grade
.. |code-climate| image:: https://api.codeclimate.com/v1/badges/9427722fafe270b6716f/maintainability
:target: https://codeclimate.com/github/dev-pipeline/dev-pipeline/maintainability
:alt: Maintainability
.. _build configuration: docs/config.rst
.. _pip: https://pypi.python.org/pypi/pip
.. _PyPi: https://pypi.org/project/dev-pipeline/
.. _setup.py: https://github.com/dev-pipeline/dev-pipeline/blob/master/setup.py
Metadata
Release files for dev-pipeline 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-0.4.0.tar.gz | 3.3 kB | Without provenance | Details for dev-pipeline-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dev_pipeline-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for dev_pipeline-0.4.0-py3-none-any.whl |
Total release size: 9.1 kB
Release files / dev-pipeline-0.4.0.tar.gz
| Download URL | dev-pipeline-0.4.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
25be4d025c5b66de7cb53dc9d077b01823710f061796d275ea9a50fa2bd1b17c
|
|
BLAKE2b-256 checksum How to use checksums |
0c5f5726f5af14d90d405d32a724f800a4107520bf6a3b0c14723fab2cbd4d77
|
| 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-0.4.0-py3-none-any.whl
| Download URL | dev_pipeline-0.4.0-py3-none-any.whl |
|---|---|
| Size | 5.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
273d8d18343d6913c7ce08b3f2ca1b32c4f8798d5d3b50d8296ca08ef5853325
|
|
BLAKE2b-256 checksum How to use checksums |
9e4474ce2146d835bd1ee6b0c4d1d82a406e62e34588ec22c814e2d4ca1db054
|
| 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 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.