abcd - AeroGear build cli for Digger
Usage
Full documentation at http://digger-build-cli.readthedocs.io.
Requirements
If running outside a container:
Download and install conda: http://conda.pydata.org/miniconda.html
After cloning the repository run:
conda env create -f env.yaml python=3.5.1To activate the environment run (might need a new terminal window or reload bashrc/bash_profile):
source activate digger
You will also need Node 4.x, NPM, Cordova >=6 and Java 8 on your machine.
Some requirements are needed to run it outside of a container:
Installation
python setup.py installTests
Requirements
Installing development dependencies:
pip install -r requirements.txtTests will download all templates from their Github repository (master branch) and will try to build it.
If running outside of the container
Prepare
# create a folder for Gradle cache
mkdir /gradle-cache
# make sure you have write permissions
chown -R ${USER} /gradle-cacheAlso, make sure you have Android SDK on your machine and $ANDROID_HOME is set.
setup.py
python setup.py testusing py.test directly (from digger project root folder)
py.test -sRunning an individual test
For example:
py.test -s tests/test_build.py1 maintainer
Metadata
1 maintainer
Release files for abcd 0.3.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 |
|---|---|---|---|---|
| abcd-0.3.0.tar.gz | 13.0 kB | Without provenance | Details for abcd-0.3.0.tar.gz |
Release files / abcd-0.3.0.tar.gz
| Download URL | abcd-0.3.0.tar.gz |
|---|---|
| Size | 13.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
94fb38ce1b1ad80f0b525e16dddf76075907875396881a951029f7046258e288
|
|
BLAKE2b-256 checksum How to use checksums |
068a37aec7abf3ee477f9b7a1d5c6083d2b8fd8ef980da7bb3813724450f9eaf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for abcd 0.3.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.
