-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Improve "Build Binaries" and "Build Test" GitHub Actions #1463
Improve "Build Binaries" and "Build Test" GitHub Actions #1463
Conversation
I like this, i need to open another pr to copy the config.ini so we are not maintaining 2 versions of it |
What about changing the build action to zip up & tag releases instead? That'll keep the repo size down by removing all the compiled firmware as well. |
i worry about posting releases too fast for little features + handling release names. I would like to see more releases though |
bit off topic and maybe just my 2 cents, but at the moment we have 2 config.ini files and maybe it would be possible to remove the one under the TFT/src/User folder and keep only the one in the Copy to SD Card root directory to update folder |
I’d keep the one in the |
Speaking of the
|
The last commit limits binary building to only run in this (bigtreetech/BIGTREETECH-TouchScreenFirmware) repo, since you end up with double commits/binary replacement when syncing or rebasing your fork. |
@Codel1417: The last commit copies |
Sorry to be such a pain, but can I ask why the two config.ini's are needed? I am not a complete newbie but it happened to me twice that I edited the one and copied the other to the SD card. It is just confusing to have the same file twice. |
Its easier for users that want something to just work without looking for files. |
Not sure I understand.
Easier it would be to have one, like it is the case for all other files.
Codel1417 <notifications@github.com> schrieb am Do. 31. Dez. 2020 um 23:39:
… Sorry to be such a pain, but can I ask why the two config.ini's are needed?
I am not a complete newbie but it happened to me twice that I edited the
one and copied the other to the SD card. It is just confusing to have the
same file twice.
Its easier for users that want something to just work without looking for
files.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1463 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM6XKZF32CJ4M5U6MWYYM4TSXT4T3ANCNFSM4VOSY2JQ>
.
|
I agree. Ideally, the The duplicate Since this PR now duplicates |
A developer is used to work with files in different folders. The common
user is having issues to find the compiled firmware once he came to the
point being able to compile at all.
I am afraid that you implemented a solution for a problem which finally
does not fix the root of it.
As always - just my 2 cents as a dump user.
Keith Bennett <notifications@github.com> schrieb am Fr. 1. Jän. 2021 um
09:18:
… Easier it would be to have one
I agree.
Ideally, the Copy to SD Card root directory to update folder wouldn’t
exist and BigTreeTech would use GitHub’s Releases feature to attach
precompiled firmware, config, images, etc. for SD updating as well as the
source code, but that’s not the process here.
The duplicate config.ini issue exists because one sits along side
Configuration.h in the source code folder for developers and the other
sits in the Copy to SD Card root directory to update folder alongside the
firmware binaries so it’s in one place for users.
Since this PR now duplicates config.ini, it’s a non-issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1463 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AM6XKZCKRYG4IAJ7AQLRG4TSXWALVANCNFSM4VOSY2JQ>
.
|
@oldman4U as explained by @thisiskeithb, while navigating through the file list tree in VS Code and when there are many files opened in the editor it is easier to find config.ini when it is in the src directory. The config.ini file in Copy to SD Card root directory to update is in a different hierarchy. A copy is placed in Copy to SD Card root directory to update so that all the files needed by the user to flash/update the device are at one place. @thisiskeithb please add |
I am concerned about the situation once the average user finished the download and starts working on it. |
This reverts commit ff5f697.
I pushed this change initially, but there's a potential for the latest |
Description
Copy
config.ini
when building binaries so the version located inCopy to SD Card root directory to update/
won't have to be updated each time the main version inTFT/src/User/
is updated.Ignore changes to the following files/folders for automatic binary/config uploads:
Ignore changes to the following files/folders for build tests:
Tagging @Codel1417 as they introduced automatic binary uploads in #1450
Benefits
Automate updating
config.ini
in the "Copy to SD Card" folder and only run CI when needed & don't upload new binaries when readmes/non-code changes are committed.Related Issues
None.