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

Pass jobId to the actionsDownloadInfo controller #1639

Merged
merged 17 commits into from
Feb 9, 2022

Conversation

BALAGA-GAYATRI
Copy link
Contributor

@BALAGA-GAYATRI BALAGA-GAYATRI commented Jan 28, 2022

Context

In order to have the job level telemetry in the github warehouse, jobId need to be passed to this table - hive_hydro.hydro.github_actions_v0_resolve_action_request

Implementation

  • In this PR jobId is being passed as a query parameter to the controller while downloading the actions info.
  • This subsequently gets passed to the launch and launch passes this to dotcom's actions resolve API.
  • Inside dotcom this jobId will be accepted and added to hive_hydro.hydro.github_actions_v0_resolve_action_request.
  • We have arrived at the jobId (executionContext.Root.Id) by matching it with the one from CustomerIntelligenceHelper.cs

👉ADR for detailed implementation.

Tracking items -

Other PRs

@BALAGA-GAYATRI BALAGA-GAYATRI requested a review from a team as a code owner January 28, 2022 19:16
ActionReferenceList actionReferenceList,
object userState = null,
CancellationToken cancellationToken = default)
{
HttpMethod httpMethod = new HttpMethod("POST");
Guid locationId = new Guid("27d7f831-88c1-4719-8ca1-6a061dad90eb");
object routeValues = new { scopeIdentifier = scopeIdentifier, hubName = hubName, planId = planId };
object routeValues = new { scopeIdentifier = scopeIdentifier, hubName = hubName, planId = planId, jobId = jobId };
Copy link
Member

Choose a reason for hiding this comment

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

will this new route without versioning break compat between the latest runner and old GHES.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If it is a query parameter change without route value , would it still break the compat and do we need GHES testing in that case?

Copy link
Member

Choose a reason for hiding this comment

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

I would suggest you always test GHES with any REST API changes.

@hross hross requested review from thboop and fhammerl January 31, 2022 12:16
@TingluoHuang TingluoHuang merged commit 374989b into actions:main Feb 9, 2022
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