Strider-CD
distributed runners
As far as I can see, strider's runners are built into strider main process. What do you think about distributed runner, that might run on the same host, different host, or even on your local machine, like Gitlab CI's.
BTW, I love the fact that strider has an (option for) built-in runner.
:+1: The gitlab CI option is very easy, you just install the runner on the machine then give it the hostname of the CI server and the unique key that the CI server generates for the next runner.
Strider runners are pluggable. A gitlab runner plugin could be developed pretty easily I'm sure.
On Friday, January 31, 2014, Mike [email protected] wrote:
[image: :+1:] The gitlab CI option is very easy, you just install the runner on the machine then give it the hostname of the CI server and the unique key that the CI server generates for the next runner.
Reply to this email directly or view it on GitHubhttps://github.com/Strider-CD/strider/issues/335#issuecomment-33826366 .
Niall O'Higgins W: http://niallohiggins.com E: [email protected] T: @niallohiggins
No update on this? I'd rather not have to develop a runner, I don't have much Node experience.
I managed to do it, by overriding the simple runner spawn config. and making it ssh into the slave machine. the problem is that I didn't get it to work on multiple slaves, yet.
@kayoub5 check out Strider-CD/core, it's the latest work on a parallelized/distributed setup.
Any updates for this feature ? I have 11 projects in the strider and dedicated server with 8 cores, but strider is build only one project at the same time. So server are use only one core. Any way to run different projects build parallel ?
See my comment above, and feel free to comment there. I don't see any work being done of the current version to move this forward, unless someone has a good amount of time to dedicate to making the runners multi-process based. I don't have that time.
Ok, Strider-CD/core and Strider-CD/drone - it is a new version of strider ? I can try to realize this feature. Some docs about strider architecture very helpful to me, how it work in general
Basically jobs come into strider, and strider sends them to the runner which runs the plugin code based on your configuration. Check out https://github.com/Strider-CD/strider-runner-core and the simple and docker runners in this org.