[ 
https://issues.apache.org/jira/browse/BEAM-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tomo Suzuki updated BEAM-8737:
------------------------------
    Description: 
beam_Dependency_Check is missing high priority items for newly created ticket. 
Current implementation considers dependency updates as high priority for only 
items that have already open JIRA tickets.

For example, 
https://builds.apache.org/job/beam_Dependency_Check/235/consoleFull sent email 
but the email did not contain bigtable-client-core. The current version 1.8.0 
is 4-minor-version older than the latest 1.12.1.

I'm suspecting the line with {{high_priority_deps.append}}:

{noformat}
      if (version_comparer.compare_dependency_versions(curr_ver, latest_ver) or
          compare_dependency_release_dates(curr_release_date, 
latest_release_date)):
        # Create a new issue or update on the existing issue
        jira_issue = jira_manager.run(dep_name, curr_ver, latest_ver, sdk_type, 
group_id = group_id)
        if (jira_issue.fields.status.name == 'Open' or
            jira_issue.fields.status.name == 'Reopened'):
          dep_info += "<td><a href=\'{0}\'>{1}</a></td></tr>".format(
            ReportGeneratorConfig.BEAM_JIRA_HOST+"browse/"+ jira_issue.key,
            jira_issue.key)
          high_priority_deps.append(dep_info)
{noformat}



  was:beam_Dependency_Check is missing high priority items for newly created 
ticket. Current implementation considers dependency updates as high priority 
for only items that have already open JIRA tickets.


> beam_Dependency_Check is missing high priority items for newly created ticket
> -----------------------------------------------------------------------------
>
>                 Key: BEAM-8737
>                 URL: https://issues.apache.org/jira/browse/BEAM-8737
>             Project: Beam
>          Issue Type: Bug
>          Components: build-system
>            Reporter: Tomo Suzuki
>            Priority: Major
>
> beam_Dependency_Check is missing high priority items for newly created 
> ticket. Current implementation considers dependency updates as high priority 
> for only items that have already open JIRA tickets.
> For example, 
> https://builds.apache.org/job/beam_Dependency_Check/235/consoleFull sent 
> email but the email did not contain bigtable-client-core. The current version 
> 1.8.0 is 4-minor-version older than the latest 1.12.1.
> I'm suspecting the line with {{high_priority_deps.append}}:
> {noformat}
>       if (version_comparer.compare_dependency_versions(curr_ver, latest_ver) 
> or
>           compare_dependency_release_dates(curr_release_date, 
> latest_release_date)):
>         # Create a new issue or update on the existing issue
>         jira_issue = jira_manager.run(dep_name, curr_ver, latest_ver, 
> sdk_type, group_id = group_id)
>         if (jira_issue.fields.status.name == 'Open' or
>             jira_issue.fields.status.name == 'Reopened'):
>           dep_info += "<td><a href=\'{0}\'>{1}</a></td></tr>".format(
>             ReportGeneratorConfig.BEAM_JIRA_HOST+"browse/"+ jira_issue.key,
>             jira_issue.key)
>           high_priority_deps.append(dep_info)
> {noformat}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to