Skip to content

[DO NOT MERGE] test: control for registry experiment (no registry change)#10455

Closed
davidfirst wants to merge 3 commits into
masterfrom
test-registry-control
Closed

[DO NOT MERGE] test: control for registry experiment (no registry change)#10455
davidfirst wants to merge 3 commits into
masterfrom
test-registry-control

Conversation

@davidfirst

Copy link
Copy Markdown
Member

Throwaway control. Identical to #10436 (default registry = bit.cloud), fresh branch/lane, to check whether a small bit ci pr build reproduces the ~21m capsule install (vs the 2m seen in #10446 with the registry flipped to npmjs). Isolates registry-change vs lane-freshness/transient-bit.cloud-load. Will be closed.

Exposes the existing builder skipTasks mechanism on `bit ci pr`, letting a
PR build skip named build/publish tasks. On the throwaway PR lane the schema
and preview artifacts and the npm publish aren't needed (they're regenerated
on the final export to main), so skipping them speeds up the job.

Wire bit_pr CI to skip ExtractSchema, GeneratePreview, GenerateEnvTemplate
and PublishComponents (~8-10m). Flag is general/user-facing and reaches both
the build and snap/tag pipelines.
The schema/preview artifacts and npm publish are generally useful (browsable
preview, API schema, installable packages); we're deliberately skipping them
on the PR validation lane to optimize for speed, not because they're never
needed. They're still produced on the final export to main.
@davidfirst davidfirst closed this Jun 26, 2026
@davidfirst davidfirst deleted the test-registry-control branch June 26, 2026 14:36
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.

1 participant