+1 Apache Yetus is a great starting point (and makes it easy to run the
same test(s) locally). I am embarrassed that I have not mentioned it
myself :)
Sean Busbey wrote:
Any particular reason y'all are aiming at using Travis CI for PR
evaluation rather than the ASF Jenkins?
I ask because my next suggestion is to look at Apache Yetus
Test-Patch[1] for automating a bunch of contribution checks (beyond
just "running maven"). I know we have examples to point to for using
it on jenkins, but I don't have a working example on Travis-CI yet.
[1]: http://yetus.apache.org/documentation/0.2.1/precommit-basic/
On Tue, May 10, 2016 at 6:35 AM, Adina Crainiceanu wrote:
Yes, integrating performance testing is part of the project. Maybe we can
talk about ways to achieve that during the next Rya meeting.
Thanks,
Adina
On Mon, May 9, 2016 at 4:53 PM, Puja Valiyil wrote:
Integrating Travis ci sounds good! Some tests don't run well on my Windows
box so that would be super useful!
Beyond that we had said integrating some performance benchmarking into the
infrastructure was a good use of his time?
Sent from my iPhone
On May 9, 2016, at 1:58 PM, Adina Crainiceanu wrote:
Aaron, Josh, Puja,
From the discussion during the office hours last week and the link Josh
sent, I understand that the continuous integration for Rya is set, just
some details need to be taken care of (set the job to run automatically).
Is that correct? If not, is there something that Amila can do for the
continuous integration task?
Here is a paragraph from Amila's original proposal. I want to know if any
of it still needs to be done/can be done by Amila.
"As the first step, I will integrate RYA build to jenkins[1] and
travisCI[2]. By using jenkins and travisCI, we can automate RYA build per
commit basis or per daily basis. We can use either way we prefer, but I
believe per commit is more suitable since then we can identify if any
commit cause to any build failure or test failure. Jenkins is an open
source tool to perform continuous integration and build automation. We
can
use apache jenkins servers to run RYA jenkins build jobs. I have to
discuss
with apacheÂinfrastructure team also about how to achieve this and I have
already started a mailing thread in their mailing list. TravisCI is also
a
continuous integration tool which I am planning to configure with RYA
build. By using travisCI, we can get a build status per every PR that a
contributor send, so when merging PRs committers don’t need to run and
check them again."
Thank you,
Adina
On Wed, May 4, 2016 at 1:03 PM, Josh Elser
wrote:
https://builds.apache.org/job/incubator-rya-develop/
It looks like there hasn't been a build since 2016/04/07. So, the job is
there to run, it's just not automatically being run.
- Josh
--
Dr. Adina Crainiceanu
Associate Professor, Computer Science Department
United States Naval Academy
410-293-6822
ad...@usna.edu
http://www.usna.edu/Users/cs/adina/
--
Dr. Adina Crainiceanu
Associate Professor, Computer Science Department
United States Naval Academy
410-293-6822
ad...@usna.edu
http://www.usna.edu/Users/cs/adina/
