-
Notifications
You must be signed in to change notification settings - Fork 150
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
[Feature] Enable GH Actions for grass-addons #172
Comments
May I merge here? Of course I'd like to preserve authorship somehow... |
Unfortunately, this needs little more than just copy pasting the files, but I have similar code in other repos. I can look at this, but it would be helpful, although not necessary, to have clear idea about what is happening on the current build server. Are the scripts in the repo up to date and complete? I looked at them once, but I was not really able to run them locally. Also what do you think about testing against different versions? 7.8 branch, master, Ubuntu PPA, ...? Some more important than the others? Is master reasonable? Perhaps @landam and @hellik can add Windows builds? BTW, co-authorship is recognized on GitHub (and possibly more universally) by |
what do you mean by adding windows builds? building GRASS? building addons? is there any progress in compiling GRASS with cmake? maybe this would ease windows builds on gh action? |
I guess both would be needed since there is no grass-dev package for Windows, right?
There is, but there is no timeline either. On top of that, CMake is just part of the compilation. Please see OSGeo/grass#348 (CMake only, some Windows support in separate PRs).
I don't know. People are using GitHub Actions with other things than CMake (msys, cygwin, ...), so it seems at least possible. The Windows VMs on GitHub Actions support Windows Docker containers, so one could run the same environment locally if needed (instead of dealing with the VM there). |
To improve the software quality it would be nice to have GH Actions also in the grass-addons repo.
It might be derived from the settings currently defined in GRASS GIS release_branch_7_8:
https://github.com/OSGeo/grass/tree/releasebranch_7_8/.github/workflows
What do you think (@wenzeslaus)?
The text was updated successfully, but these errors were encountered: