Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactoring trigger-mobile-metrics script for updated notifications #6844

Merged
merged 1 commit into from
Jan 19, 2023

Conversation

SevaZhukov
Copy link
Contributor

https://mapbox.atlassian.net/browse/NAVSDK-216

These changes are necessary after mobile-metrics repository refactoring. We can't continue to trigger jobs because we need to set the context for sending notifications using Slack Orb. This we can implement only using workflows triggering.

@github-actions
Copy link

Changelog

Features

Bug fixes and improvements

  • Improved NavigationView camera behavior to go back into overview state if routes change during route preview state. #6840

Known issues ⚠️

Other changes

Android Auto Changelog

Features

Bug fixes and improvements

@codecov
Copy link

codecov bot commented Jan 17, 2023

Codecov Report

Merging #6844 (ec2a014) into main (1098030) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff            @@
##               main    #6844   +/-   ##
=========================================
  Coverage     72.64%   72.64%           
  Complexity     5564     5564           
=========================================
  Files           781      781           
  Lines         30116    30116           
  Branches       3561     3561           
=========================================
  Hits          21878    21878           
  Misses         6810     6810           
  Partials       1428     1428           


trigger_workflow(token, commit, publish_results)

if not publish_results:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happened to the branch where publish_results is True?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These jobs will be called by running the workflow with run_android_navigation_benchmark flag

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What do you mean? Why don't we publish results anymore?

trigger_workflow(token, commit, publish_results)

if not publish_results:
trigger_job(token, commit, "android-navigation-code-coverage-ci")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's not clear what happens if publish_results == false, the script trigger workflow and additionally triggered jobs, right?

@SevaZhukov
Copy link
Contributor Author

SevaZhukov commented Jan 18, 2023

Okay, I need to write more detailed information about what happens here.

Early this script ran:

on the main branch:

  • android-navigation-benchmark job (by workflow with run_android_navigation_benchmark flag)
  • android-navigation-binary-size job
  • android-navigation-code-coverage job

on other branches:

  • default workflow
  • android-navigation-code-coverage-ci job
  • android-navigation-binary-size-ci job

After refactoring:

on the main branch:

  • android-navigation-benchmark job (by workflow with run_android_navigation_benchmark flag)
  • android-navigation-binary-size job (by workflow with run_android_navigation_benchmark flag)
  • android-navigation-code-coverage job (by workflow with run_android_navigation_benchmark flag)

on other branches:

  • default workflow
  • android-navigation-code-coverage-ci job
  • android-navigation-binary-size-ci job

As you can see, nothing was changed in general. These changes are only for changed jobs/workflow structure in mobile-metrics.

@RingerJK @dzinad

@RingerJK
Copy link
Contributor

@SevaZhukov I get it. Thanks.

Do you know if we run default workflow from the SDK repo without run_android_navigation_benchmark flag it means we run nothing in mobile-metrics CI, right? So now (and before) triggering default workflow from non-main branch is doing nothing actually.

*default workflow is the actual name of the workflow from mobile-metrics repo

@SevaZhukov
Copy link
Contributor Author

SevaZhukov commented Jan 18, 2023

Do you know if we run default workflow from the SDK repo without run_android_navigation_benchmark flag it means we run nothing in mobile-metrics CI, right?

@RingerJK The default workflow without run_android_navigation_benchmark runs android-check-in-tests job and waiting for approval for other jobs

Copy link
Contributor

@RingerJK RingerJK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@SevaZhukov SevaZhukov merged commit ce11135 into main Jan 19, 2023
@SevaZhukov SevaZhukov deleted the NAVSDK-216 branch January 19, 2023 09:12
SevaZhukov added a commit that referenced this pull request Jan 23, 2023
SevaZhukov added a commit that referenced this pull request Jan 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants