hey Mike, indeed it is not. it's just a machine permanently connected to the net, that is payed by me and used for other projects as well. i could give you personal sftp access if you want to have a look, but otherwise i'd rather not opening it up for security reasons.
btw. preliminary snapshot builds are up (the folder in the zip files seems to be wrong still) https://sourceforge.net/projects/jump-pilot/files/OpenJUMP2_snapshots/ don't misunderstand me i am not opposed to some other solution :) it is just easiest this way for me right now. if you or actually anyone else realizes a it in any another way, even on github, so be it. i just see us standing in front of a big mountain of work being beating OJ2 back into shape on a new platform we are all not overly familiar with. so my priorities are a bit more focussed on getting started in the little time i've got. sunny regards ..ede On 3/17/2021 0:01, Michaud Michael wrote: > Hi, > > OK, my only concern is : is your build script written on a server which is > accessible and maintanable by any of us ? Sorry if you already answered this > question in the wiki. > > Michaël > >> envoyé : 15 mars 2021 à 16:32 >> de : edgar.sol...@web.de >> à : Michaud Michael <m.michael.mich...@orange.fr>, OpenJump develop and use >> <jump-pilot-devel@lists.sourceforge.net> >> objet : Re: [JPP-Devel] OJ2 snapshots >> >> >> 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
