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

ci: Build ROM release from versioned git ref (revive) #1907

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

leongross
Copy link
Contributor

Revive of PR #1604.

@leongross leongross marked this pull request as ready for review January 24, 2025 15:23
.github/workflows/fpga.yml Outdated Show resolved Hide resolved
@@ -25,6 +25,9 @@ on:
rom-version:
default: "latest"
type: string
rom-ref:
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think ultimately our goal is for the nightly release workflow to be runnable with specified ROM & FW refs. Would it make sense to try to factor out some of the steps in this file so it can be reused in the nightly one as well?

Not sure if that would improve things or just make the CI more confusing.

benjamindoron and others added 2 commits January 31, 2025 11:32
* trap exit (induced e.g. by set -e) and add cleanup when script calls
  early exit
* update script to comply with SC2086
* change return codes to 0-255 range SC2242
* add verbosity flags for commands modifying the filesystem

Signed-off-by: leongross <[email protected]>
@leongross leongross force-pushed the leongross/build_versioned_release_rom branch from 362878e to 1d48817 Compare January 31, 2025 10:32

- name: Generate release zip
run: |
./ci-tools/release/build_release.sh "_versioned_build_test_" ${{ inputs.rom-ref }} ${{ inputs.firmware-version }}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

So when we talk about firmware this means FMC and RT, right? So we don't want to consider different revisions for FMC and RT?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Ya, I think currently it's fine to build FMC and RT from the same revision.

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.

3 participants