-
Notifications
You must be signed in to change notification settings - Fork 162
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
cronjobs: expand script to run stand-alone #1215
Conversation
With this PR instructions to set up the source code repo have been turned into executable script chunks. Hence, if the scripts are executed on a new server, the GitHub repo cloning is done as well as needed directories are created. Furthermore, some minor script tuning.
FYI: Installation of dependencies on grass.osgeo.org:
Due to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking into this. I didn't get far in a Docker container (just guessing what the setup needs to be):
docker run -it ubuntu bash
apt update
apt install git
git clone https://github.com/neteler/grass-addons.git
cd grass-addons/
git switch cron_standalone_scripts
cd ..
git clone https://github.com/OSGeo/grass
apt install $(cat grass/.github/workflows/apt.txt)
grass-addons/utils/cronjobs_osgeo_lxd/cron_grass_current_stable_build_binaries.sh
grass-addons/utils/cronjobs_osgeo_lxd/cron_grass_current_stable_build_binaries.sh: 141: cd: can't cd to /home//src//releasebranch_8_4/
Perhaps, you can try to get just one of these run in a Docker container and, if that still runs on the lxd server, you can then sync the other ones too.
utils/cronjobs_osgeo_lxd/cron_grass_current_stable_build_binaries.sh
Outdated
Show resolved
Hide resolved
utils/cronjobs_osgeo_lxd/cron_grass_current_stable_build_binaries.sh
Outdated
Show resolved
Hide resolved
utils/cronjobs_osgeo_lxd/cron_grass_current_stable_build_binaries.sh
Outdated
Show resolved
Hide resolved
Should be addressed in 250c4a8 I got this running:
|
Instructions added to |
@wenzeslaus any objections to merge this PR? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At one point we need to iterate and improve each time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look okay. I was not able to run it at this moment due to connection issues with the Ubuntu package archives.
Co-authored-by: Vaclav Petras <[email protected]>
With this PR instructions to set up the source code repo have been turned into executable script chunks. Hence, if the scripts are executed on a new server, the GitHub repo cloning is done as well as needed directories are created.
Furthermore, some minor script tuning.