<commit_before># Continuous delivery example

An example of implementing continuous delivery with Travis-CI.



# How it works

The _build branch is the single place where the CI tools do the building. The branch has a submodule of the source which should be built, so triggering a new build is simply a matter of updating the submodule SHA. This could be done manually, or could be automated to be done when the tests are successful, as has been done in this repository.
<commit_msg>Added readme + buttons.<commit_after># Continuous delivery example

An example of implementing continuous delivery with Travis-CI.


Tests: [![Build Status](https://travis-ci.org/pelson/package_with_continuous_delivery.svg?branch=master)](https://travis-ci.org/pelson/package_with_continuous_delivery); Build: [![Build Status](https://travis-ci.org/pelson/package_with_continuous_delivery.svg?branch=_build)](https://travis-ci.org/pelson/package_with_continuous_delivery)



# How it works

The _build branch is the single place where the CI tools do the building. The branch has a submodule of the source which should be built, so triggering a new build is simply a matter of updating the submodule SHA. This could be done manually, or could be automated to be done when the tests are successful, as has been done in this repository.

The same process can be used for building executables on OS X, Linux, and Windows through TravisCI, CircleCI and AppVeyor respectively.


{'fraction_non_alphanumeric': 0.05971173644474949, 'fraction_numerical': 0.0, 'mean_word_length': 5.0, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7670601', 'n_tokens_mistral': 385, 'n_tokens_neox': 368, 'n_words': 187}