[
https://issues.apache.org/jira/browse/ARROW-8043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428894#comment-17428894
]
Alessandro Molina edited comment on ARROW-8043 at 10/14/21, 3:51 PM:
---------------------------------------------------------------------
Curious about the {{dedicated JIRA tags; one for each nightly job so a JIRA}}
part. Are we sure that can scale on long term? I'm not sure Jira was designed
to have more than an handful of tags/labels and github is already having an
hard time loading the list of branches as we create a new branch every time.
For example [https://github.com/ursacomputing/crossbow/settings/pages] just
times out due to that.
was (Author: amol-):
Curious about the \{{dedicated JIRA tags; one for each nightly job so a JIRA }}
part. Are we sure that can scale on long term? I'm not sure Jira was designed
to have more than an handful of tags/labels and github is already having an
hard time loading the list of branches as we create a new branch every time.
For example [https://github.com/ursacomputing/crossbow/settings/pages] just
times out due to that.
> [Developer] Provide better visibility for failed nightly builds
> ---------------------------------------------------------------
>
> Key: ARROW-8043
> URL: https://issues.apache.org/jira/browse/ARROW-8043
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Continuous Integration, Developer Tools
> Affects Versions: 0.16.0
> Reporter: Ben Kietzman
> Assignee: David Dali Susanibar Arce
> Priority: Major
> Labels: pull-request-available
> Fix For: 7.0.0
>
>
> Emails reporting nightly failures are unsatisfactory in two ways: there is a
> large click/scroll distance between the links presented in that email and the
> actual error message. Worse, once one is there it's not clear what JIRAs have
> been made or which of them are in progress.
> One solution would be to replace or augment the [NIGHTLY] email with a page
> ([https://ursa-labs.github.org/crossbow] would be my favorite) which shows
> how many nights it has failed, a shortcut to the actual error line in CI's
> logs, and useful views of JIRA. We could accomplish this with:
> - dedicated JIRA tags; one for each nightly job so a JIRA can be easily
> associated with specific jobs
> - A static HTML dashboard with client side JavaScript to
> ** scrape JIRA and update the page dynamically as soon as JIRAs are opened
> ** show any relationships between failing jobs
> ** highlight jobs that have not been addressed, along with a counter of how
> many nights it has gone unaddressed
> - provide automatic and expedited creation of correctly labelled JIRAs, so
> that viewers can quickly organize/take ownership of a failed nightly job.
> JIRA supports reading form fields from URL parameters, so this would be
> fairly straightforward:
>
> [https://issues.apache.org/jira/secure/CreateIssueDetails!init.jspa?pid=12319525&issuetype=1&summary=[NIGHTLY:gandiva-jar-osx,gandiva-jar-trusty]&versions=12340948&fixVersions=12347769&components=12334626]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
