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 <[email protected]> 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 [email protected] http://www.usna.edu/Users/cs/adina/
