Google Git
Sign in
apache / flink-jira-bot

Apache Flink Jira Bot

Mirrored from https://github.com/apache/flink-jira-bot.git
Clone this repo:

Branches

  1. 96764c4 Merge pull request #23 from knaufk/FLINK-23206 by Konstantin Knauf · 2 years, 9 months ago master
  2. d06a472 [FLINK-23206] Minor tickets are moved to Not a Priority instead of closing by Konstantin Knauf · 2 years, 9 months ago
  3. ee516a3 Merge pull request #22 from knaufk/hotfix-blocker-issues by Konstantin Knauf · 2 years, 10 months ago
  4. bc37608 [hotfix] dont warn on tickets that already have the warning label by Konstantin Knauf · 2 years, 10 months ago
  5. 614cd74 Merge pull request #21 from knaufk/FLINK-23250 by Konstantin Knauf · 2 years, 10 months ago

Apache Flink Jira Bot

The Flink Jira Bot partially enforces the Apache Flink Jira process. Please see Apache Flink Jira Process for all the guidlines and conventions that we try to follow.

Usage

./venv/bin/python3 flink_jira_bot.py --help
usage: flink_jira_bot.py [-h] [-d] [-c CONFIG]

Apache Flink Jira Bot

optional arguments:
  -h, --help            show this help message and exit
  -d, --dry-run         no action on Jira, only logging
  -c CONFIG, --config CONFIG
                        path to config file (default: config.yaml)

There are also make targets for the important actions:

Run

make run

Dry-Run

The dry-run does not make any changes to the Apache Flink Jira, but instead only logs the actions it would do.

make dry-run

Configuration

Both make run and make dry-run look for the password of flink-jira-bot in an environment variable called JIRA_PASSWORD.

The configuration of the rules can be found in config.yaml.

About the Rules

Rule 1 Tickets Need an Assignee or Discussion Eventually

Any ticket (except ones with priority “Not a Priority”) needs an assignee, or an update within {stale_<blocker|critical|major|minor>.stale_days}, otherwise the priority will be reduced after a warning period of {stale_<blocker|critical|major>.warning_days} days. An update of a Sub-Task counts as an update to the ticket. Before this happens the assignee/reporter/watchers are notified that the ticket is about to become stale and will be deprioritized. The time periods before warning differ based on the priority:

Rule 2: Unassign Stale Assigned Tickets

Assigned tickets without an update for {stale_assigned.stale_days} days are marked stale. The assignee is notified and asked for an update on the status of her contribution.

About Apache Flink

Apache Flink is an open source project of The Apache Software Foundation (ASF).

Flink is a distributed data processing framework with powerful stream and batch processing capabilities. Learn more about Flink at http://flink.apache.org/