Open pedromorgan opened 5 years ago
So to create a "sim-server.exe".. check this https://openplcproject.gitlab.io/openplc_go/
So the "downloads/" and the executables are all created by gitlab, on commits to master after testing.. That's why I stick rice etc in there.. https://gitlab.com/openplcproject/openplc_go/blob/master/.gitlab-ci.yml
@npiganeau so here's a demo of the ci @ gitlab, making a www site and the exe's for various platforms
downloads
for the exe'soh and the "script config" is https://gitlab.com/ts2-project/ts2-sim-server/blob/pedro-html/.gitlab-ci.yml
@npiganeau can u respond to this issue.. and evaluate please.
It all works as am using gitlab-ci.yml on "client projects".. mainly using free tier...
It solves a lot of limitations of github..imho, notably pages using whatever platform
What's you gitlab username so i can add u to project et all.. so u can evaluate.. main goal is to automate a load of stuff is it not ?
If u dont like it, then of course I will destroy (or u can) all the project
Can't you do the same with Travis CI on Github ?
no. 1) travis is just a ci checker, so we use travis (and circle ci and appveyor) et all
2) u missed the point of generating www sites, and exe's
@pedromorgan Can we imagine to keep GitHub as main repository and also GitHub pages because we have good referencing on Google and use Gitlab as a CI only that pushes back to GitHub?
@npiganeau This is another project and it generated go.lang exe's with gitlab-ci https://openplcproject.gitlab.io/openplc_go/md_build_index.html
Note it build a few platforms https://gitlab.com/openplcproject/openplc_go/blob/master/.gitlab-ci.yml
Ok this is deep but we need to do it.. for mainly the following reasons..
documentation = main reason
making exe's for download
ci + testing