On 3/15/2021 9:27, Michaud Michael wrote: > Hi Ede, hey Mike,
> > The only automated build which has been set up for now is in > .github/workflows. It is a direct adaptation of github workflow documentation > and does the bare minimum : automatically compile the project after each push. > > It is possible to do a lot more including packaging and releases, but it is > not done yet. > > When we will have a first release to publish, It would be nice to have it > available on github. don't see why. sure we should make the most of the services offered. still Github has backdraws. starting from a really unintuitive releases page, a generally convoluted UI up to the storage limits it opposes on free accounts. and let's not forget it's a service offered by Microsoft that in the past managed to simply block repos for supposedly holding copyrighted code or otherwise violating TOS reasons. > I think it would be nice to use github workflow to automate all these task > but I don't know if it is compatible with your idea to create backup and to > push files on sf.net.files. might be possible to build on Github and push to sf.net. dunno. but i am actually not willing to learn some Github specific way to build, that i cannot use on other platforms as well. > Anyway, if you feel more comfortable with setting up the automatic > build/release from your server, as it was done with our sourceforge repo, I > would also appreciate. As I'm not an expert in this area, my first criteria > would be to have a build system as simple to use/maintain as possible. > totally. it's just the easiest, at least for now. it is just some shell script run via cron every 15mins, comparing revisions and on update running a mvn build and sftping it up to sf.net. just gotta adapt it from svn to git. to infinity and beyond!.. ede _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
