You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There can be two tasks in GradleRIO, one that pulls off the deployed app and another that puts the pulled-off app back on the RIO. The backup task could put the deployed app into a zip on the host PC if we want to specifically make it portable.
For dependency matching reasons it may also be useful to copy off the WPILib/Vendor shared objects to the backed up archive.
The scenario I can see this being useful for:
Team has a known working project deployed and has run a match(es) with it. Team wants to make improvement/change
Team backs up deployed app
Team makes change to their code (using git/vcs or not) and deploys it for testing
Change doesn't test well or team runs out of time
Rather than reverting code and redeploying (trusting that revert was done correctly and there are no differences between reverted code and what was previously deployed) team can redeploy the backup app.
This removes some manual steps in the process (primarily reverting code) that are required to have a redeploy from source be successful in matching what was previously deployed.
We should support rsyncing files off of the roboRIO. This can probably be a dedicated task with a specific location hardcoded just like file deploys.
See: https://www.chiefdelphi.com/t/copy-files-off-robot-during-deploy/390969/4
The text was updated successfully, but these errors were encountered: