-
Notifications
You must be signed in to change notification settings - Fork 12
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
Run MATLAB from shell with v2? #89
Comments
Hi @rdzman, At the moment, the We are considering ways to support shell-based workflows in the future but I do not have anything official to give you now. The run actions use a "run-matlab-command" binary behind-the-scenes that you could use as a stopgap for shell-based workflows but please note the "run-matlab-command" binary is undocumented and subject to change in the future. - name: Setup MATLAB
uses: matlab-actions/setup-matlab@v2
- name: Get run-matlab-command
run: |
wget -O /usr/local/bin/run-matlab-command https://ssd.mathworks.com/supportfiles/ci/run-matlab-command/v2/glnxa64/run-matlab-command
chmod +x /usr/local/bin/run-matlab-command
- name: Run MATLAB Command
run: run-matlab-command "disp('hello world')" |
…up-matlab@v2. For the latter, I had to use the undocumented 'run-matlab-command'. Ref: matlab-actions/setup-matlab#89 (comment)
…up-matlab@v2. For the latter, I had to use the undocumented 'run-matlab-command'. Ref: matlab-actions/setup-matlab#89 (comment)
…up-matlab@v2. For the latter, I had to use the undocumented 'run-matlab-command'. Remove os input. Make note about nojvm input being irrelevant under v2. Ref: matlab-actions/setup-matlab#89 (comment)
…up-matlab@v2. For the latter, I had to use the undocumented 'run-matlab-command'. Remove os input. Make note about nojvm input being irrelevant under v2. Ref: matlab-actions/setup-matlab#89 (comment)
Thank you. This appears to solve the problem ... with one minor issue. With v1, there were quite a few Matlab Toolboxes included, but when I run v2 via Is there a way to include these via |
With
These details will be in the action documentation when v2 is officially released shortly. |
Thank you! Exactly what I needed. Please do let me know if/when this |
With v1 I was able to configure my CI to use the same workflow to run my own custom test environment in both MATLAB and Octave, by launching them via the command line. For MATLAB, I used
matlab -batch "myscript"
.After switching to v2, I get a "License checkout failed" error when attempting to launch MATLAB from a shell.
Can I add a
-c licensefile
to the command to make it work? If so, where is the license file? If not, please tell me how I can successfully launch MATLAB from a shell script to run my custom tests.And keep in mind that the reason I am not able to use
matlab-actions/run-command
is because I'm using the same workflow to run my custom test scripts on Octave. I have a lot of projects with this setup, so redesigning all of them would be prohibitive.Any help is appreciated.
The text was updated successfully, but these errors were encountered: