Development process for script runner scripts (COSMOS 5)

[djordan-nh]

Hello,

I intend to use the COSMOS 5 script runner feature for system testing, but I am finding long cycle times between making script updates and actually testing them, making development/debugging slow. I am curious if there are any steps in my process that could be simplified or even done using command line to help speed up development.

Here is the current process from making a script update to actually testing it:

1. Make updates to COSMOS ruby scripts in VS Code
2. Build the plugin gem from command line
3. Restart COSMOS (and cleanup in order to re-upload script files)
   1. ./cosmos-control.sh stop
   2. ./cosmos-control.sh cleanup
   3. ./cosmos-control.sh start
4. Connect to COSMOS and create initial username/password
5. Upload plugin, enter plugin variables
6. Wait for plugin to initialize
7. Open script runner, and open script file to test
8. Run script and debug
9. (repeat)

And a couple key questions:

• Is it necessary to restart/cleanup COSMOS in order to re-upload script files? (is there an easier way)
• Can COSMOS scripts be run somehow from command line in COSMOS 5 in addition to using the script runner GUI?

Thank you for any help!

[ghost]

Lots of comments :)

1. The easiest path would be to edit the scripts in ScriptRunner, and then save and run them.

If you want to edit outside ScriptRunner in VS Code, that's fine, but currently you will need to rebuild the plugin and then "upgrade" it from the Admin tab. This will work, but the problem you may be running into is leftover edited versions of the script that are "winning" versus the new version you built into the plugin. To fix that, you'll need to open the edited script in ScriptRunner (should have a * by its name), and then File -> Delete. Then reopen the file and it should be the new version.

Thanks for the reminder that we need to make this simpler. You should never have to stop and restart COSMOS. And definitely not cleanup because that deletes everything.

To answer your last question, yes scripts can be run from the command line, but running scripts outside of ScriptRunner they will just stop with an exception if anything goes wrong, rather than the ScriptRunner behavior of pausing. See: https://github.com/BallAerospace/COSMOS/blob/master/examples/external_script.rb

[djordan-nh]

Thanks for the suggestions, this all is helpful to know.

Our end goal is for scripts to run in script runner, but testing them initially in command line can help find some errors quicker, particularly for SW developers. And VS Code is helpful so I can edit the files directly within our git repository. I will try to get with the example script working and go from there.

For some team members, I am planning for them to fully edit and run scripts in the script runner for testing. Is there a best way to get all the modified scripts out of COSMOS so I can commit them back into a git repo? We want to keep these scripts version controlled.

Thank you again! :)

[djordan-nh]

I have found that MinIO can be used to help with removing modified scripts, and can be used to download modified scripts.

If you want to upload a plugin to cosmos and replace all scripts, you can log in to your MinIO instance and then delete the targets_modified folder to delete any scripts that had been modified. Additionally, this folder can be downloaded if you want to grab the modified files and put them in a repo.