Skip to content

Instantly share code, notes, and snippets.

@abadger
Last active June 30, 2021 16:51
Show Gist options
  • Select an option

  • Save abadger/29f077e634eb7c826139b493f67305f1 to your computer and use it in GitHub Desktop.

Select an option

Save abadger/29f077e634eb7c826139b493f67305f1 to your computer and use it in GitHub Desktop.
How to test how much more memory the docs build will consume as collections are added
* Checkout ansible-build-data
* git clone https://github.com/ansible-community/ansible-build-data
* For testing the devel tree, modify the latest ansible.in file (currently ansible-build-data/5/ansible.in)
* Example, this adds the community.dns collection to the collection docs that will be built:
* echo 'community.dns ' >> ansible-build-data/5/ansible.in
* For testing the stable tree, you will have to modify the latest ansible-X.Y.Z.deps file:
* echo 'community.dns: 1.0.1' >> ansible-build-data/4/ansible-4.2.0.deps
* Download the patch to ansible-core:
* wget https://github.com/ansible/ansible/pull/75150.patch
* Checkout the ansible-core code:
* git clone https://github.com/ansible/ansible
* cd ansible
* apply the patch to your checkout:
* git apply ../75150.patch
* Tell the docs build to use your local copy of ansible-build-data when building the ansible package devel docs:
* Note: the ansible-build-data path can be absolute. If relative as in the example, it is relative to the ansible/docs/docsite directory
* make webdocs EXTRA_PLUGIN_FORMATTER_ARGS='--ansible-build-data=../../../ansible-build-data'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment