Skip to content

[DRAFT][bazel] Initial build/release system, modified#9

Merged
pamaury merged 7 commits into
lowRISC:mainfrom
pamaury:bazel-builds
Jul 15, 2026
Merged

[DRAFT][bazel] Initial build/release system, modified#9
pamaury merged 7 commits into
lowRISC:mainfrom
pamaury:bazel-builds

Conversation

@pamaury

@pamaury pamaury commented Jun 2, 2026

Copy link
Copy Markdown
Collaborator

This is an alternative version of #6 using the module + injected repo architecture developed in lowRISC/opentitan#30268
This creates the initial build/release system, as well as an automated GitHub workflow to create the pre-sign release artefacts. See #9 (comment) for details

Example run:

@pamaury pamaury mentioned this pull request Jun 2, 2026
@pamaury
pamaury force-pushed the bazel-builds branch 2 times, most recently from a044b79 to 01402b5 Compare June 2, 2026 11:48
Comment thread skus/open/orchestrator/ot00.hjson Outdated
Comment thread skus/open/orchestrator/ot00_staging.hjson Outdated
Comment thread skus/open/rom_ext/BUILD Outdated
@pamaury
pamaury force-pushed the bazel-builds branch 23 times, most recently from faae43e to 8f5beea Compare June 8, 2026 14:24
@pamaury
pamaury force-pushed the bazel-builds branch 9 times, most recently from 6d316fb to 5062c7a Compare June 16, 2026 18:19
@pamaury
pamaury force-pushed the bazel-builds branch 10 times, most recently from 1bb14d7 to 46ee32d Compare June 25, 2026 09:37
options:
- pre-sign
- post-sign
release_branch:

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

It's inconvenient to have to select the release branch twice (once to run the workflow, once in the text box) when doing a post-signing release, also it is error-prone. But this is needed for pre-signing release. Maybe we could make it optional, only accept non-empty entries for pre-signing and for post-sining we always use the branch from which the workflow was ran?

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This is handled automatically now by updating the <<< ANCHOR >>>s, correct?

@pamaury pamaury Jul 1, 2026

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Yes

Comment thread doc/create_release.md Outdated
Comment thread skus/open/orchestrator/ot00.hjson Outdated
Comment thread skus/open/orchestrator/ot00_staging.hjson Outdated
Comment thread skus/open/rom_ext/BUILD Outdated
options:
- pre-sign
- post-sign
release_branch:

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This is handled automatically now by updating the <<< ANCHOR >>>s, correct?

@pamaury

pamaury commented Jul 1, 2026

Copy link
Copy Markdown
Collaborator Author

I think the PR should now be ready.

pamaury added 7 commits July 15, 2026 16:10
The lock file was not updated in a previous commit.

Signed-off-by: Amaury Pouly <amaury.pouly@opentitan.org>
Signed-off-by: Amaury Pouly <amaury.pouly@opentitan.org>
Signed-off-by: Amaury Pouly <amaury.pouly@opentitan.org>
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.

2 participants