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

Helix job links no longer show up in builds #11129

Closed
1 of 2 tasks
MichalStrehovsky opened this issue Oct 4, 2022 · 3 comments
Closed
1 of 2 tasks

Helix job links no longer show up in builds #11129

MichalStrehovsky opened this issue Oct 4, 2022 · 3 comments

Comments

@MichalStrehovsky
Copy link
Member

  • This issue is blocking
  • This issue is causing unreasonable pain

It used to be that I could get a link to the Helix job from AzDo, like so:

  Sent Helix Job; see work items at https://helix.dot.net/api/jobs/e6df725b-7a21-4eab-a4c1-3c1e82c8b4be/workitems?api-version=2019-06-17

But what I see now is:

  Sent Helix Job; see work items at [System.String]::Copy('').TrimEnd('/')/api/jobs/5c729cc2-8299-4430-86f7-001e35434c43/workitems?api-version=2019-06-17

See e.g. https://dev.azure.com/dnceng-public/public/_build/results?buildId=39472&view=logs&jobId=b2c675c1-1c32-50e9-7c40-e762459300db&j=b2c675c1-1c32-50e9-7c40-e762459300db&t=4f51db95-f7de-5a4e-cd10-f078782dd75b

@riarenas
Copy link
Member

riarenas commented Oct 4, 2022

I think this was a side effect of this change: #11041 which was then reverted in #11093. Version 8.0.0-beta.22503.2 of the Helix SDK should include the revert.

@riarenas
Copy link
Member

riarenas commented Oct 4, 2022

looks like for runtime's case, dotnet/runtime#76605 includes the fix. In the meantime, you can use the helix artifacts tab in the test section of the build, which is the preferred way to access helix job information. There's a good chance we're going to remove the links altogether from the console output. dotnet/dnceng#1222

@riarenas
Copy link
Member

riarenas commented Oct 7, 2022

The necessary arcade sdk to get this bug reverted has already flowed down to repos, and as they take the updates they should see this resolved. Closing but feel free to reopen if you keep seeing this even after having the most up to date arcade updates.

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

No branches or pull requests

2 participants