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
Before push it the already build image to docker hub, it might be necessary to test this image, by running a simplified upwelling test case. We have two choices here: 1) create the configuration files in this repository or 2) clone the experiment1 from roms_idealized_experiments, developed by @dksasaki.
It is mandatory, however, that we edit the .in file to change the integration time to something shorter (perhaps using sed), to shorten the building time in the GitHub action.
Another important point to consider here is that we must download the ROMS source code before running any application inside the container, so we will have to set some ROMS credentials as repository variables. Perhaps, just by downloading the source code, it is possible to copy the upwelling test case, edit what must be edited, and run the application without any new file here in this repository.
How to check if the application runs properly inside the container?
To check if the applications run properly, an idea is to save the output of the running to a file and check if the last lines of this logfile have the specific text (ROMS/TOMS: DONE...). Once this information is found in the log file, then we are able to push a tested image to the docker hub.
What I believe is the right template to insert into the workflow
We could use something similar to:
Before push it the already build image to docker hub, it might be necessary to test this image, by running a simplified upwelling test case. We have two choices here: 1) create the configuration files in this repository or 2) clone the experiment1 from roms_idealized_experiments, developed by @dksasaki.
It is mandatory, however, that we edit the .in file to change the integration time to something shorter (perhaps using
sed
), to shorten the building time in the GitHub action.Another important point to consider here is that we must download the ROMS source code before running any application inside the container, so we will have to set some ROMS credentials as repository variables. Perhaps, just by downloading the source code, it is possible to copy the upwelling test case, edit what must be edited, and run the application without any new file here in this repository.
How to check if the application runs properly inside the container?
To check if the applications run properly, an idea is to save the output of the running to a file and check if the last lines of this logfile have the specific text (
ROMS/TOMS: DONE...
). Once this information is found in the log file, then we are able to push a tested image to the docker hub.What I believe is the right template to insert into the workflow
We could use something similar to:
The text was updated successfully, but these errors were encountered: