[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [flux-dev] Initial plans
|
Hey Rafael,
as John said, the project is in the early days, so don’t expect anything to be stable yet.
Nevertheless the prototype code is in the repository now and you could take a look at this, if you would like to. And from what you said it should be possible to build a server-side service that connects to the message bus and does the “keep files in sync” for the build server. The node.js repository components would be a good starting point for that. But keep in mind that the protocoll and the messages that are sent around at the moment will change in the future.
If you need more details about the existing prototype code, let me know.
HTH,
Martin
Am 04.06.2014 um 22:28 schrieb John Arthorne <John_Arthorne@xxxxxxxxxx>:
> Hey Rafael,
>
> It is still pretty early days for the project, I don't think we've gotten to the point of planning what the first release would look like, or when that will be. There is some information here on the work to incorporate messaging in the Orion Java server:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=434888
>
> I am exploring this right now and will put a pointer in that bug with any more details.
>
> John
>
>
>
> From: Rafael Chaves <rafael@xxxxxxxxxxxx>
> To: flux-dev@xxxxxxxxxxx,
> Date: 06/03/2014 06:25 PM
> Subject: [flux-dev] Initial plans
> Sent by: flux-dev-bounces@xxxxxxxxxxx
>
>
>
> Hi all,
> Good to see the first weekly call minutes on the wiki, thanks for that. I see there are several different fronts being tackled in parallel - but is there a planned/committed scope for the first milestone?
>
> I do intend on being an early adopter, so I am trying to have an idea on whether I'd be able to adopt the first milestone or would need to wait a little longer. Also, it would be great to see the early designs for the messaging infrastructure, the different use cases planned etc.
>
> In my case, my immediate use case involves being able to build in some random server projects that are being edited in an Orion workspace (and later elsewhere). Right now I have a hack to handle that that involves running the Orion server and the build server on the same machine, so the builder can see the workspace files. Instead, I would rather have a message with the entire project contents being consumed by the build service, or some way for the build service to request for the rest of the project contents.
>
> Cheers,
>
> Rafael_______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/flux-dev
>
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/flux-dev
>
