opened
apendua
username_0
Would it solve #68?
Implement all velocity methods, so that we can listen for results from mirrors
issue
created
apendua
username_0
@username_1 What do you think about this one?

The idea is basically that Gagarin could start a mirror and listen to tests results. It should be relatively easy to implement because it's a matter of providing appropriate environment variables to the mirror process, right?
comment
created
samhatoum
username_1
That's a great idea and yes it should be doable using the ENV vars. I would experiment with this approach and collect some findings. 

We've been talking about a new lifecycle for Velocity and how to rewrite mirrors to make them more robust. you can [see the hackpad here](https://velocity.hackpad.com/Important-topics-for-velocitycore-nN6VyVoOaeO).
comment
created
apendua
username_0
@username_1 Thanks! I will take a look.
comment
created
Laboratory
username_2
no velocity, it's bad idea :/
comment
created
samhatoum
username_1
@username_2 Care to elaborate?
comment
created
apendua
username_0
@username_2 I don't agree. Imagine you already have a project with a lot of velocity tests, which you don't want to rewrite yet you still want to use Gagarin as a single test runner.
comment
created
Laboratory
username_2
My test written with velocity doesn't run for 3 weeks and no one can help me.
comment
created
apendua
username_0
@username_2 Anyway, we don't want any kind of "frameworks wars" here on GitHub. It's not for expressing private opinions but for a technical discussion.
comment
created
Laboratory
username_2
@username_1 https://github.com/meteor-velocity/velocity/issues/281
comment
created
Laboratory
username_2
@username_0, ok, sorry
comment
created
samhatoum
username_1
@username_0 want to meet again to pick up where we left off? Velocity had really advanced since we spoke :)
comment