The thrift complier/code generator is a native executable, the thrift jar is
pulled in through maven. I simply included it because currently we check in
the generated thrift code, but if I am asking it would be great to generate it
each time instead of checking it in. Sorry I didn't respond sooner, I am a bit
busy with other things and have not had time to spin up an ubuntu VM and see
what we need to install to make storm work. I should hopefully get to it today
or tomorrow.
- Bobby
On Thursday, May 28, 2015 3:04 AM, Sergio Fernández <[email protected]>
wrote:
Hi Bob,
On Thu, May 21, 2015 at 3:38 PM, Bobby Evans <[email protected]> wrote:
I don't know the debian-style dependencies off the top of my head but I will
try to work on it.
Well, the typical dependencies you'd need to have for building Storm on Ubuntu.
Then it's much easier to translate top INFRA the needs the box would require at
builds.apache.org.
At a high level we need python(which I think is already there, at least on most
boxes), ruby with the json module installed (I think ruby is there on many
boxes, but no json module), and nodejs. I would love to see thrift 0.9.2, but
we are checking in the generated code for now, so it is not a requirement.
OK, Python and Ruby (with their respective JSON modules) are system
dependencies. But Thrift is not a project dependency (i.e., maven dependency)?
With those details I could take care of getting the Jenkins setup done.
Having nightly builds will lower the barrier for new people who jump in Storm.
Cheers,
On Thursday, May 21, 2015 8:32 AM, Sergio Fernández <[email protected]>
wrote:
Hi,
thanks for the quick reply, Bobby.
Whatever you miss in the current jenkins' boxes can be discussed with infra.
Can you please detail the actual needs (Debian-style) and I' can take care of
making it possible.
In case you'd like to use external ASF tooling, with Travis you just need to
encrypt your credentials for pushing artifacts to repository.apache.org, as
described at:
https://coderwall.com/p/9b_lfq/deploying-maven-artifacts-from-travis
I'm new in this project; but definitely is something you should have at some
point.
Cheers,
On Thu, May 21, 2015 at 3:23 PM, Bobby Evans <[email protected]>
wrote:
The real problem is that we don't have any automated builds set up. The apache
jenkins build boxes don't have all of the dependencies we need installed on
them, we have been playing around with travis-ci, but I'm not sure if it will
ever be able to push to repository.apache.org. Please file a JIRA for it, I'm
not sure when we will find time to work it all out, but it is something at
least I have been thinking about.
- Bobby
On Thursday, May 21, 2015 7:59 AM, Sergio Fernández <[email protected]>
wrote:
I forward this question to dev@
---------- Forwarded message ----------
From: Sergio Fernández <[email protected]>
Date: Tue, May 19, 2015 at 11:21 AM
Subject: snapshots deployment?
To: [email protected]
Hi,
I'm very new on Storm, but I'm pretty sure I'll appear here quite
frequently from now ;-)
Putting my hands on my first project I have to say that I find a bit tricky
that the project does not frequently publish maven snapshots to
repository.apache.org (in my case required to access artifacts such as
multilang-python).
Do you have any plan guys to do it? Not sure if you're already using
Jenkins, but is trivial to have then deployment from there (many users like
me would be very thankful).
Just that. Thanks for building such awesome project!
Cheers,
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: [email protected]
w: http://redlink.co
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: [email protected]
w: http://redlink.co
--
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: [email protected]
w: http://redlink.co
