Continuous integration (Travis or similar)

[pdurbin]

We've benefitted from having Travis set up at https://travis-ci.org/IQSS/dataverse and should consider it for this repo as well.

[richarda23]

We're building on our Jenkins server, and can add your email to notifications of failed builds if you like, although obviously feel free to set up a Travis build if you want it public.

[pdurbin]

@richarda23 hi! As I mentioned at IQSS/dataverse#5724 I have some news to share about continuous integration.

On Friday @donsizemore and I got it in our head that the new Global Dataverse Community Consortium ( http://dataversecommunity.global ) and/or the Dataverse community ought to have a Jenkins server available for testing. Don checked with Jon and UNC is willing to host it. I created a DNS entry at https://jenkins.dataverse.org but we only have one job so far. Can we work with you to add as many jobs as you need for dataverse-client-java ensure that nothing breaks in the future?

For more on the conversation Don and I had, please see http://irclog.iq.harvard.edu/dataverse/2019-04-05#i_90075

[pdurbin]

Over at IQSS/dataverse#5725 we are working on explaining to the Dataverse community what options are offered to them in terms of testing and continuous integration, including the new Jenkins server I mentioned above.

[pdurbin]

I just set up a push webhook to https://jenkins.dataverse.org/github-webhook/

@donsizemore and I discussed this at http://irclog.iq.harvard.edu/dataverse/2019-06-04#i_96026

[pdurbin]

Related: https://dataverse.zulipchat.com/#narrow/stream/377090-python/topic/containers.20for.20API.20testing

[pdurbin]

@richarda23 check out this awesome work by @JR-1991

https://github.com/gdcc/container-test/blob/6cb49d8e58b2269acaec71e3509f9dd5fbec8cc7/.github/workflows/run_dv.yml

https://github.com/gdcc/container-test/actions/runs/4854677636