James,

The tests are run by https://travis-ci.org and the pass/fail can be seen
with each pull request (Ex :
https://github.com/apache/fineract/pull/527). History
is at https://travis-ci.org/apache/fineract .

Regards,
Vishwas



On Sat, Feb 16, 2019 at 2:15 PM James Dailey <[email protected]> wrote:

> Thanks Michael! +1
>
> Is the infra tix already in or does it need to be requested?
>
> Once running is there a URL to check on pass/fail status?
>
>
>
> On Wed, Feb 13, 2019, 2:40 PM Michael Vorburger <[email protected] wrote:
>
> > Hello everyone,
> >
> > On 2019/02/12 13:38:49, Ed Cable <[email protected]> wrote:
> > > +1>
> > >
> > > Santosh, can you please update community on status of integration
> tests?>
> > >
> > > Ed>
> > >
> > > On Tue, Feb 12, 2019, 01:21 Myrle Krantz <[email protected] wrote:>
> > >
> > > > Hey all,>
> > > >>
> > > > Michael has suggested enabling Travis for the Fineract repo.  What
> > this>
> > > > would do is automatically call the build on code submitted with a PR.
> > We>
> > > > could also configure it to automatically run integration tests (that
> > will>
> > > > only be useful if the integration tests are currently working).  This
> > will>
> > > > make merging good PRs a little easier and rejecting PRs which break
> > the>
> > > > build a lot easier.>
> > > >>
> > > > This question is only for Fineract 1.x currently.  Fineract CN will
> > require>
> > > > a bit more work to get CI support running because of the way it is
> > spread>
> > > > across multiple repositories.>
> > > >>
> > > > What do you think?  If there are no objections in the next 72 hours,
> > I'd>
> > > > like to give Infra the go-ahead.>
> > > >>
> > > > Best Regards,>
> > > > Myrle>
> >
> > FYI this is now fully done; hope this small contribution helps this
> > community to be a little more effective.
> >
> > Please see https://issues.apache.org/jira/browse/FINERACT-697 for the
> full
> > details of the work that was required and done for this to work.
> >
> > All the best,
> > M.
> >
> > PS: I'm not actually reading this list (and won't, just due to general
> > load), but am replying to this via web interface; please Reply-To-All if
> > you want me to see replies.
> >
>

Reply via email to