Versions Compared

Old Version 12

changes.mady.by.user Matthias Pohl

Saved on

compared with

New Version 13

changes.mady.by.user Matthias Pohl

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Hints around AzureCI/Jira usage

  • 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
  • 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
      serverASF JIRA
      serverId5aa69414-a9e9-3523-82ec-879b028fb15b
      keyFLINK-123
      straight away)
    • https://issues.apache.org/jira/browse/FLINK-101061?filter=-1&jql=project%20%3D%20FLINK%20AND%20text%20~%20%22%s%22%20AND%20status%20NOT%20IN%20(Closed%2C%20Resolved) searches project%20%3D%20FLINK%20AND%20text%20~%20%22%s%22%20ORDER%20BY%20id%20DESC  search for any open FLINK issue based on a query -string 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
    • ; handy for looking up Jira issues related to some test instability)
    • 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) same as the query above but only for open FLINK Jira issues.