-
Notifications
You must be signed in to change notification settings - Fork 55
ci: Build ROM release from versioned git ref (revive) #1907
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
base: main
Are you sure you want to change the base?
Conversation
@@ -25,6 +25,9 @@ on: | |||
rom-version: | |||
default: "latest" | |||
type: string | |||
rom-ref: |
There was a problem hiding this comment.
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.
362878e
to
1d48817
Compare
|
||
- name: Generate release zip | ||
run: | | ||
./ci-tools/release/build_release.sh "_versioned_build_test_" ${{ inputs.rom-ref }} ${{ inputs.firmware-version }} |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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.
5ba7955
to
461e177
Compare
2fc0287
to
03ce821
Compare
c24504c
to
1642751
Compare
Signed-off-by: Benjamin Doron <[email protected]>
* 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]>
Signed-off-by: leongross <[email protected]>
nightly-release.yml Signed-off-by: leongross <[email protected]>
Signed-off-by: leongross <[email protected]>
* remove unnecessary pull_requests trigger for fpga.yml * re-add the pull_requests trigger fro versioned-full-build-test Signed-off-by: leongross <[email protected]>
f9e12fb
to
c68098a
Compare
Signed-off-by: leongross <[email protected]>
Signed-off-by: leongross <[email protected]>
Signed-off-by: leongross <[email protected]>
Signed-off-by: leongross <[email protected]>
Signed-off-by: leongross <[email protected]>
Signed-off-by: leongross <[email protected]>
c68098a
to
13a9dfb
Compare
Signed-off-by: leongross <[email protected]>
13a9dfb
to
b2ba74b
Compare
Signed-off-by: leongross <[email protected]>
f98d6f8
to
831ac19
Compare
Signed-off-by: leongross <[email protected]>
831ac19
to
62abe57
Compare
Hey @leongross, it looks like there's some failing CI in this PR. Any questions you have for getting this running? |
I am not entirely sure what the reason is for the error; in the |
e0dba13
to
619c4a1
Compare
Signed-off-by: leongross <[email protected]>
619c4a1
to
0c46993
Compare
Revive of PR #1604.