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

chore(IDX): Simplify versioning #3984

Merged
merged 1 commit into from
Feb 18, 2025
Merged

chore(IDX): Simplify versioning #3984

merged 1 commit into from
Feb 18, 2025

Conversation

nmattia
Copy link
Contributor

@nmattia nmattia commented Feb 17, 2025

This simplifies the mechanism used to stamp the released artifacts with a version.

In the non-release mode, a constant version is used. In release mode (with --config=stamp) the HEAD commit id and timestamp are used.

This also removes some workarounds that were necessary to re-trigger bazel evaluation (timestamp file, etc) as well as the distinction between "IC version" and "IC RC-only version".

Moreover the upload check (to ensure we don't upload non-release artifacts) is removed because (1) uploads are (currently) always necessary (for SHA256SUMS files) and (2) the check was using an incorrect string in the comparison (couple extra zeros) which meant it never triggers.

@github-actions github-actions bot added the chore label Feb 17, 2025
@nmattia nmattia marked this pull request as ready for review February 17, 2025 14:46
@nmattia nmattia requested review from a team as code owners February 17, 2025 14:46
@nmattia nmattia added the CI_ALL_BAZEL_TARGETS Runs all bazel targets and uploads them to S3 label Feb 17, 2025
Copy link
Collaborator

@basvandijk basvandijk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't see anything wrong with this. It looks like a great simplification!

I am wondering what happened in the past when a PR was labelled with CI_ALL_BAZEL_TARGETS. Were
artifacts uploaded to our CDNs under the all-zeros revision?

And IIUC, this still happens with this PR right?

@basvandijk basvandijk requested a review from a team February 17, 2025 15:25
@nmattia
Copy link
Contributor Author

nmattia commented Feb 17, 2025

Were artifacts uploaded to our CDNs under the all-zeros revision?

That's what it looked like!

@github-actions github-actions bot added the @dre label Feb 17, 2025
This simplifies the mechanism used to stamp the released artifacts with
a version.

In the non-release mode, a constant version is used. In release mode
(with `--config=stamp`) the HEAD commit id and timestamp are used.

This also removes some workarounds that were necessary to re-trigger
bazel evaluation (timestamp file, etc) as well as the distinction
between "IC version" and "IC RC-only version".

Moreover the upload check (to ensure we don't upload non-release
artifacts) is removed because (1) uploads are (currently) always
necessary (for SHA256SUMS files) and (2) the check was using an
incorrect string in the comparison (couple extra zeros) which meant it
never triggers.
@nmattia nmattia enabled auto-merge February 18, 2025 11:23
@nmattia nmattia added this pull request to the merge queue Feb 18, 2025
Merged via the queue into master with commit 4e132ab Feb 18, 2025
25 checks passed
@nmattia nmattia deleted the nm-release branch February 18, 2025 12:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants