antsibull-build -- Ansible Build Scripts
Tooling for building various things related to Ansible
Scripts that are here:
- antsibull-build - Builds Ansible 6+ from component collections (docs)
Related projects are antsibull-changelog and antsibull-docs, which are in their own repositories (antsibull-changelog repository, antsibull-docs repository). Currently antsibull-changelog is a dependency of antsibull-build. Therefore, the scripts contained in it will be available as well when installing antsibull-build.
You can find a list of changes in the Antsibull Build changelog.
antsibull-build is covered by the Ansible Code of Conduct.
Licensing
This repository abides by the REUSE specification. See the copyright headers in each file for the exact license and copyright. Summarily:
- The default license is the GNU Public License v3+
(
GPL-3.0-or-later). src/antsibull/_vendor/shutil.pyincludes code derived from CPython, licensed under the Python 2.0 License (Python-2.0.1).
Versioning and compatibility
From version 0.1.0 on, antsibull-build sticks to semantic versioning and aims at providing no backwards compatibility breaking changes to the command line API (antsibull-build) during a major release cycle. We might make exceptions from this in case of security fixes for vulnerabilities that are severe enough.
We explicitly exclude code compatibility. antsibull-build is not supposed to be used as a library. The only exception are potential dependencies with other antsibull projects (currently, none). If you want to use a certain part of antsibull-build as a library, please create an issue so we can discuss whether we add a stable interface for parts of the Python code. We do not promise that this will actually happen though.
Development
Install and run nox to run all tests. That's it for simple contributions!
nox will create virtual environments in .nox inside the checked out project
and install the requirements needed to run the tests there.
antsibull-build depends on the sister antsibull-core, antsibull-changelog,
antsibull-docs-parser, antsibull-docutils, and antsibull-fileutils projects.
By default, nox will install development versions of these projects from
Github.
If you're hacking on antsibull-core, antsibull-changelog, antsibull-docs-parser,
antsibull-docutils and/or antsibull-fileutils alongside antsibull-build,
nox will automatically install the projects from ../antsibull-core,
../antsibull-changelog, ../antsibull-docs-parser, ../antsibull-docutils,
and ../antsibull-fileutils when running tests if those paths exist.
You can change this behavior through the OTHER_ANTSIBULL_MODE env var:
OTHER_ANTSIBULL_MODE=auto— the default behavior described aboveOTHER_ANTSIBULL_MODE=local— install the projects from../antsibull-core,../antsibull-changelog,../antsibull-docs-parser,../antsibull-docutils, and../antsibull-fileutils. Fail if those paths don't exist.OTHER_ANTSIBULL_MODE=git— install the projects from the Github main branchOTHER_ANTSIBULL_MODE=pypi— install the latest version from PyPI
To run specific tests:
nox -e testto only run unit tests;nox -e lintto run all linters;nox -e formattersto runisortandblack;nox -e codeqato runflake8,pylint,reuse lint, andantsibull-changelog lint;nox -e typingto runmypy.nox -e coverage_releaseto build a test ansible release. This is expensive, so it's not run by default.nox -e check_package_filesto run the generate-package-files integration tests. This is somewhat expensive and thus not run by default. Runnox -e check_package_files -- regento regenerate the test fixtures.nox -e coverageto display combined coverage results after runningnox -e test coverage_release check_package_files;
Run nox -l to list all test sessions.
To create a more complete local development env:
git clone https://github.com/ansible-community/antsibull-changelog.git
git clone https://github.com/ansible-community/antsibull-core.git
git clone https://github.com/ansible-community/antsibull-docs-parser.git
git clone https://github.com/ansible-community/antsibull-docutils.git
git clone https://github.com/ansible-community/antsibull-build.git
cd antsibull-build
python3 -m venv venv
. ./venv/bin/activate
pip install -e '.[dev]' -e ../antsibull-changelog -e ../antsibull-core -e ../antsibull-docs-parser -e ../antsibull-docutils
[...]
nox
Creating a new release:
- Run
nox -e bump -- <version> <release_summary_message>. This:- Bumps the package version in
src/antsibull/__init__.py. - Creates
changelogs/fragments/<version>.ymlwith arelease_summarysection. - Runs
antsibull-changelog releaseand adds the changed files to git. - Commits with message
Release <version>.and runsgit tag -a -m 'antsibull-build <version>' <version>. - Runs
hatch build --cleanto build an sdist and wheel indist/and clean up any old artifacts in that directory.
- Bumps the package version in
- Run
git pushto the appropriate remotes. - Once CI passes on GitHub, run
nox -e publish. This:- Runs
hatch publishto publish the sdist and wheel generated during step 1 to PyPI; - Bumps the version to
<version>.post0; - Adds the changed file to git and runs
git commit -m 'Post-release version bump.';
- Runs
- Run
git push --follow-tagsto the appropriate remotes and create a GitHub release.
Metadata
Release files for antsibull-build 0.78.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 |
|---|---|---|---|---|
| antsibull_build-0.78.0.tar.gz | 658.4 kB | Without provenance | Details for antsibull_build-0.78.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| antsibull_build-0.78.0-py3-none-any.whl | Python 3 | none | any | Details for antsibull_build-0.78.0-py3-none-any.whl |
Total release size: 777.2 kB
Release files / antsibull_build-0.78.0.tar.gz
| Download URL | antsibull_build-0.78.0.tar.gz |
|---|---|
| Size | 658.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dac97b243fd6694eb122f6f85265e06af9dad7692c8e1c2d825104564e3861e7
|
|
BLAKE2b-256 checksum How to use checksums |
31e020a9dd55c744bb15a56b9eb438b886d5f6dce12e2e4c458c33abcb24452d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.16.5 cpython/3.14.3 HTTPX/0.28.1
|
Release files / antsibull_build-0.78.0-py3-none-any.whl
| Download URL | antsibull_build-0.78.0-py3-none-any.whl |
|---|---|
| Size | 118.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f4c1f3d8350302d1ed4c31327e9aef0c0fc01f265b08bfe0d842945d7e104698
|
|
BLAKE2b-256 checksum How to use checksums |
09a1320a2581c0a5ef92795223c3ff0b5b6539a3128408f1ebd0e1bcd83375a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
Hatch/1.16.5 cpython/3.14.3 HTTPX/0.28.1
|
Security for antsibull-build 0.78.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.