Upload supplemental data for Azure jobs #2686
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
minestarks
force-pushed
the
minestarks/azure-submit-circuit
branch
from
977f3c5 to
c784e96
Compare
minestarks
changed the base branch from
main
to
minestarks/refactor-submit-job
github-merge-queue bot
pushed a commit
that referenced
this pull request
Sep 8, 2025
Refactoring Azure job submission so that this PR is easier to read: #2686 There's a slight change in order of the telemetry events. We were sending `submitJob` twice when the Copilot tools were invoked. This is the only behavior change I'm expecting. Co-authored-by: Mine Starks <>
minestarks
force-pushed
the
minestarks/azure-submit-circuit
branch
from
502e2fb to
11aba05
Compare
orpuente-MS
approved these changes
Sep 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds an "upload supplemental data" step to Azure job submission.
This step is currently disabled by default, and can be enabled via user settings (not expected to be useful today except for testing).
If job submission succeeded, we attempt to generate a circuit diagram. If successful, the resulting JSON diagram data is uploaded to the
circuitDatablob in the same storage container as the job input data.