You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there interest in setting up continuous integration for testing BraCeR output? Travis builds can run Docker images, for example, which would make implementation easier. As a first step testing could be limited to the assemble command and take advantage of the existing test data. I would be happy to take a first pass.
The text was updated successfully, but these errors were encountered:
Hi Derek,
Sure, please have a go at this. Thanks!
How easy would it be to make something that would work across both BraCeR and TraCeR (www.github.com/teichlab/tracer <http://www.github.com/teichlab/tracer>)? That’d be very cool but no worries if it’s loads of extra work.
Thanks and best wishes,
Mike
On 11 Jun 2018, at 18:46, Derek Croote ***@***.***> wrote:
Is there interest in setting up continuous integration for testing BraCeR output? Travis builds can run Docker images <https://docs.travis-ci.com/user/docker/>, for example, which would make implementation easier. As a first step testing could be limited to the assemble command and take advantage of the existing test data. I would be happy to take a first pass.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub <#15>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABFwhoHRydbr1Fwt1zKRgXeYUt50LaJOks5t7q0JgaJpZM4UjHlc>.
Is there interest in setting up continuous integration for testing BraCeR output? Travis builds can run Docker images, for example, which would make implementation easier. As a first step testing could be limited to the
assemble
command and take advantage of the existing test data. I would be happy to take a first pass.The text was updated successfully, but these errors were encountered: