Hey @drewbrend! 👋

I just ran a build with that version of the CLI and get both of those fields in the diagnostics file. Would you be able to share a snippet of what you're seeing in your chromatic-diagnostics.json? Do you see any errors in the logs?

No errors in the logs. Here's what the output chromatic-diagnostics.json looks like. I redacted some things, let me know if you need anything further.

{
"configuration": {
"configFile": "chromatic.config.json",
"projectId": "Project:##########",
"onlyChanged": true,
"zip": true
},
"exitCode": 0,
"exitCodeKey": "OK",
"flags": {
"storybookBuildDir": [
"storybook-static/current"
],
"onlyChanged": "",
"diagnostics": true,
"outputDir": [],
"externals": [],
"onlyStoryFiles": [],
"onlyStoryNames": [],
"untraced": [],
"fileHashing": true,
"interactive": true,
"appCode": []
},
"git": {
"version": "2.39.3 (Apple Git-146)",
"gitUserEmail": "[email protected]",
"uncommittedHash": "",
"commit": "e7ac1771fb85af84d6b02d9f7bcbb8ff92773005",
"committedAt": 1726147370000,
"committerEmail": "[email protected]",
"committerName": "someone else",
"branch": "master",
"slug": "my-repo",
"fromCI": false,
"parentCommits": [
"e7ac1771fb85af84d6b02d9f7bcbb8ff92773005"
]
},
"input": [],
"isOnboarding": false,
"options": {
"fromCI": false,
"inAction": false,
"dryRun": false,
"debug": false,
"autoAcceptChanges": false,
"exitZeroOnChanges": false,
"exitOnceUploaded": false,
"diagnosticsFile": "chromatic-diagnostics.json",
"fileHashing": true,
"interactive": true,
"isLocalBuild": false,
"originalArgv": [
"--storybook-build-dir",
"storybook-static/current",
"--only-changed",
"--diagnostics"
],
"onlyChanged": true,
"zip": true,
"storybookBuildDir": "storybook-static/current",
"storybookLogFile": "build-storybook.log",
"branchName": "",
"configFile": "chromatic.config.json",
"projectId": "Project:##########"
},
"packageJson": {
... copy of package.json here I've removed
},
"packagePath": "/some/path/to/package.json",
"rebuildForBuildId": "66e2eb9845ab52206b4d4600",
"sessionId": "3f3233c3-b7b5-425c-9e65-bfffcb9023ea",
"skip": true,
"startedAt": 1726235757138,
"task": "gitInfo",
"userError": false
}

I think I see what's happening here. The rebuildForBuildId and skip fields makes me think the CLI picked up that a build already ran successfully on that commit so it skipped everything and no build was created.

Do your logs mention something like that?

Ah okay, I think that makes sense since I was running this several times while working on configuring it in CI.

In my case, we're using the deployments from a branch to add a link to the deployment on a PR so reviewers can check it out.

I can construct the URL in the format of https://{$branchName}--${appId}.chromatic.com, but linking to the specific commit like that path does is nicer.

In the case of a rebuild I'd need to construct this URL instead of getting it from the value in chromatic-diagnostics.json... this isn't a big deal, but if I can rely on that value always being there it would simplify things for me.

Could a skipped run still return the links to the deployment and test results for the last run?

Yeah that sounds reasonable to me!

In an effort to prevent breaking things for other folks, I'm thinking we add a new field for rebuildForBuild which contains the build information you need. That would mean you'd have to check for that value because it won't exist in the same place in those cases (either build or rebuildForBuild. Does that work?

Yes, I think that'd work for me!

🚀 Issue was released in v11.11.0 🚀

@drewbrend if you use the latest version, you should get those fields! Remember, they'll be in rebuildForBuild when a rebuild is detected!