<commit_before># Contributing

All changes to this repo should be uploaded to Gerrit. Please see below if
you don't have an account on Gerrit yet.

A recommended setup is (replace _`<gerritusername>`_ with your gerrit account
name):

	git clone https://github.com/sillsdev/ci-builder-scripts.git
	cd ci-builder-scripts
	git config remote.origin.pushurl \
		ssh://<gerritusername>@gerrit.lsdev.sil.org/ci-builder-scripts.git
	git config remote.origin.push "+refs/heads/*:refs/for/master/*"

You can push your changes to Gerrit by running:

	git push origin HEAD:refs/for/master

The FieldWorks [wiki page](https://github.com/sillsdev/FwDocumentation/wiki/Workflow-Overview)
gives an overview of the general workflow.
For the ci-builder-scripts project we use a simplified version of the
workflow which differs in so far that all development is done on the
`master` branch.

## Create new build job by adding new groovy file

To add a build job to Jenkins you can add a new groovy file. Take one of the
existing files as a template. The documentation for the Jenkins Job DSL API
can be found on the [server itself](https://jenkins.lsdev.sil.org/plugin/job-dsl/api-viewer/index.html).
<commit_msg>[Documentation] Add port to gerrit URL<commit_after># Contributing

All changes to this repo should be uploaded to Gerrit. Please see below if
you don't have an account on Gerrit yet.

A recommended setup is (replace _`<gerritusername>`_ with your gerrit account
name):

	git clone https://github.com/sillsdev/ci-builder-scripts.git
	cd ci-builder-scripts
	git config remote.origin.pushurl \
		ssh://<gerritusername>@gerrit.lsdev.sil.org:59418/ci-builder-scripts.git
	git config remote.origin.push "+refs/heads/*:refs/for/master/*"

You can push your changes to Gerrit by running:

	git push origin HEAD:refs/for/master

The FieldWorks [wiki page](https://github.com/sillsdev/FwDocumentation/wiki/Workflow-Overview)
gives an overview of the general workflow.
For the ci-builder-scripts project we use a simplified version of the
workflow which differs in so far that all development is done on the
`master` branch.

## Create new build job by adding new groovy file

To add a build job to Jenkins you can add a new groovy file. Take one of the
existing files as a template. The documentation for the Jenkins Job DSL API
can be found on the [server itself](https://jenkins.lsdev.sil.org/plugin/job-dsl/api-viewer/index.html).

{'fraction_non_alphanumeric': 0.08309218685407194, 'fraction_numerical': 0.002066969822240595, 'mean_word_length': 4.377777777777778, 'pattern_counts': {'":': 0, '<': 7, '<?xml version=': 0, '>': 7, 'https://': 6, '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': '455038', 'n_tokens_mistral': 763, 'n_tokens_neox': 705, 'n_words': 295}