.. _tutorial-new-package: Add a new package ================= The following document demonstrates how to create a new Python package for Software Heritage, hereafter named ``swh-foo``. We will need to create a project, initialize the new repository, reference the project in the Continuous Integration system and finally add the project to the documentation. .. _create-new-project: Create a project ---------------- Creating the project from swh-py-template_ can be done using the ``bin/init-py-repo`` tool. This script uses the ``gitlab`` command-line tool provided by the `python-gitlab `_ module. Before running ``init-py-repo``, please make sure that the ``gitlab`` command is working and configured with an access token of scope ``api``. The following commands need to run from the base directory ``swh-environment``. 1. Use ``bin/init-py-repo`` to initialize the repository with a project template and create the corresponding gitlab project: .. code-block:: console pip install -r requirements.txt bin/init-py-repo swh-foo 2. Install the pre-commit hook: .. code-block:: console pre-commit install Add the repo on the swh-environment project ------------------------------------------- Declare the repository on the *mr* configuration: - Edit the ``.mrconfig`` file and declare the new repository. For an example, `look at the addition of swh-graphql `__. - Create a merge request with the changes. .. note:: Adding the repository in ``.mrconfig`` will break ``swh-docs`` builds until the new module is registered in the documentation as explained below. Install CI jobs --------------- - In swh-jenkins-jobs_, open `jobs/swh-packages.yaml `__ and add a section like the others for the new repository. .. note:: Jobs will automatically be recreated when changes are pushed to the ``swh-jenkins-jobs`` repository. See `Jenkins documentation `_ for details. Hack hack hack -------------- The generated project should have everything needed to start hacking in. You should typically start with: - fill the README file - write some code in ``swh/foo`` - write tests in ``swh/foo/tests`` - add yourself in ``CONTRIBUTORS`` if needed - add some sphinx documentation in ``docs`` Make an initial release ----------------------- Releases are made automatically by Jenkins when a tag is pushed to a module repository. Making an initial release is thus done by doing: .. code-block:: console git tag v0.0.0 git push origin --tags v0.0.0 .. note:: Before adding a new module to the documentation, at least one release must have been made. Otherwise, the documentation will not build as it won’t be able to fetch the Python package from PyPI nor determine the version number. This is why we need to make an initial release before moving forward. Update the documentation ------------------------ The documentation is in the swh-docs_ project. Each Python module get a section of the documentation automatically generated from its source code. To add a new module to the documentation: - Add the package to the dependencies in ``requirements-swh.txt`` (publication build) and ``requirements-swh-dev.txt`` (documentation development build). - Reference the package in the ``toctree`` located in ``docs/devel/api-reference.rst`` - Add the package with a concise description to the index of the development part, located in ``docs/devel/index.rst``. .. code-block:: rst :ref:`swh.foo ` short description of the repository - Ensure this builds fine locally (run ``tox run`` and ``tox run -e sphinx-dev``) - Open a merge request with the above changes. .. _`Continuous Integration (CI)`: https://jenkins.softwareheritage.org .. _swh-py-template: https://gitlab.softwareheritage.org/swh/devel/swh-py-template .. _swh-jenkins-jobs: https://gitlab.softwareheritage.org/swh/infra/ci-cd/swh-jenkins-jobs .. _swh-docs: https://gitlab.softwareheritage.org/swh/devel/swh-docs