Page History

...

Build failures should be reported in the corresponding Jira issue (or a Jira issue should be created if none exists, yet). Contributors should be pinged to fix instabilities as soon as possible to ensure a stable infrastructure of the course of the release cycle. More details on Jira issues can be found on the Flink Jira Process wiki page.

Hints around AzureCI/Jira usage

• There are several URLs with placeholder that might be handy when accessing Jira through your browser using Firefox's bookmark keywords or Chrome's search engine feature:
  • https://issues.apache.org/jira/browse/FLINK-%s enables a lookup by ID (i.e. "<keyword> 123" in the browser's address field opens

    Jira
    server ASF JIRA serverId 5aa69414-a9e9-3523-82ec-879b028fb15b key FLINK-123

    straight away)
  • https://issues.apache.org/jira/browse/FLINK-10106?filter=-1&jql=project%20%3D%20FLINK%20AND%20text%20~%20%22%s%22%20AND%20status%20NOT%20IN%20(Closed%2C%20Resolved) searches for any open FLINK issue based on a query-string (i.e. "<keyword> asd" in the browser's address field opens a search result containing all open Flink Jira issues having the search term "asd" in it)
• AzureCI's console log output view supports line bookmarks: Each line number on the left side of the console log view has its own link assigned to it