Taskotron contribution guide

Repositories

The repositories for the various components of Taskotron can be found on Pagure:

• libtaskotron
• taskotron-trigger
• ExecDB
• ResultsDB
• ResultsDB frontend
• ResultsDB API client library

The repositories for the tasks developed alongside Taskotron itself are in the Fedora QA project on Bitbucket:

• task-rpmlint
• task-depcheck
• task-upgradepath
• task-rpmgrill
• task-dockerautotest

If you need team membership, send a message out to qa-devel@ or file a ticket in QA:Phabricator against the infrastructure project.

Issue and code change tracking

Tracking of issues and code changes for all Taskotron projects happens in the Fedora QA instance of Phabricator. Please see this section of the page for general instructions on submitting issues and 'diffs' in Phabricator.

Taskotron-specific instructions

There are some specific considerations for contributing to Taskotron components.

gitflow

Gitflow is a git branching strategy that has been used successfully in the blocker tracking app and several Fedora infra apps.

• Description of the gitflow strategy
• gitflow tool code and docs

Use the develop branch
When using gitflow, the current in-development branch is develop, not master. Be careful not to start developing against an older branch

Tests

Taskotron components usually have test suites built on Pytest. Ensure you have pytest installed to run the tests.

Linting

As we are using code linting, you will also need the flake8 tool - run sudo dnf install python-flake8 to install it.

General Thoughts and conventions

• Be smart
• All code going into develop branches MUST be reviewed
• All code should have good unit tests where appropriate
  • When in doubt, ask