This is a small library that can be used to setup Continuous Delivery of Azure web apps thru Visual Studio Team Services
Перейти к файлу
Luca Boccassi 874094b8b5 Separate build dependencies from install dependencies
Allows setup.py to correctly let mock out of the install dependencies
2019-06-14 12:14:20 +01:00
aex_accounts VSTS Account Creation migration to AEX APIs (#20) 2017-10-27 14:16:28 +05:30
continuous_delivery Implemented multiple new command parameters for CI/CD functionalities for Azure Webapps (#17) 2017-10-09 15:15:55 +05:30
tests VSTS Account Creation migration to AEX APIs (#20) 2017-10-27 14:16:28 +05:30
vsts_cd_manager Fixing a bug to fetch correct account name (#22) 2018-06-12 15:56:21 +05:30
vsts_info_provider fixing broken mapping 2017-04-28 10:54:37 -04:00
.gitignore Initial checkin of the supporting classes 2017-03-24 10:18:16 -04:00
LICENSE Initial commit 2017-03-23 11:41:15 -07:00
README.rst Added unit tests and updated readme 2017-05-12 17:11:45 -04:00
__init__.py Initial checkin of the supporting classes 2017-03-24 10:18:16 -04:00
setup.py Separate build dependencies from install dependencies 2019-06-14 12:14:20 +01:00

README.rst

Visual Studio Team Services Continuous Delivery Manager
=======================================================

This project provides the class ContinuousDeliveryManager and supporting classes. This CD manager class allows
the caller to manage Azure Continuous Delivery pipelines that are maintained within a VSTS account.

Contribute Code
===============

This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments.

Packaging
=========

The released packages for this code can be found here https://pypi.python.org/pypi/vsts-cd-manager. 
Use the standard PYPI packaging flow to push a new release. Make sure to increment the version number appropriately.

*Example*
::
    python setup.py sdist
    python -m twine upload dist/*
::

Running Tests
=============
The only class we have unit tests for is the ContinuousDeliveryManager class. As features are added, add tests 
and maintain a high (>80%) code coverage number for this class.
You can run these tests in the following way:
::
    python tests/test_continuous_delivery_manager.py
::

Code Coverage
=============
Code coverage for the vsts_cd_manager.py file should be kept current with any new features. Most of the other code 
is boiler plate REST API code that could be generated for the most part. You can find out more about how to run
code coverage here: https://coverage.readthedocs.io/en/coverage-4.4