dotnet / dotnet/source-build

Investigate whether re-bootstrapping without updating the SDK is possible

Open
#5,249 2 comments 1 reaction 0 assignees View on GitHub
area-infra
Dominant language
No language data
Stars
287
Forks
145
Avg merge
1d 22h
Merged PRs (30d)
10

Description

From Viktor:

> So we often re-bootstrap to get newer Arcade SDK changes in, i.e. for publishing updates (the v4 publishing work is a good example). Can we do re-bootstraps of only Arcade without updating the SDK? In SB terms, can we update PSB from stage1 without updating the SDK? Michael Simons (.NET)

From Michael:

> Technically there is no reason why this couldn't be done but as a general practice I don't think it is simple, we are not tooled for it, and therefore I would recommend we just do a normal re-bootstrap. You can't just update PSB without updating the SDK because they will not be coherent and it will likely break SB. In essence you are going to spend more time than doing a normal re-bootstrap.

From Viktor:

> Ok. You understand where I'm coming from with that though? People ask us to update the SDK less often and ideally just to public previews. But we re-bootstrap often enough just to get a newer Arcade.Sdk.

From Michael:

> I understand the ask, I am just pointing out how the toolset is coupled from a source build perspective therefore it is really only feasible to updated it as one.

From Viktor:

> Will the coherency aspect go away with stable preview builds?

From Michael:

> hmmm, it might. Would you mind logging an issue for us to consider/investigate supporting an arcade only rebootstrap?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.