As a member of the Dataverse community, I'm interested in learning more about continuous integration solutions that are available to me.

[donsizemore]

Would like to add https://jenkins.dataverse.org/ , Travis et alia to the dev guide. Pull request forthcoming.

[pdurbin]

@donsizemore thanks! Please be sure to mention this new repo I just created (and made you an admin of): https://github.com/IQSS/dataverse-jenkins

[pdurbin]

@donsizemore I just left a review on your pull request #5751 and approved it. I think it's a great little blurb and sets expectations well and gives pointers to the right places (the new service and repo linked above).

Coincidentally, I opened up Twitter this morning and found that @4tikhonov is talking a lot about continuous integration in some slides he just posted at https://twitter.com/4tykhonov/status/1116229640232873984

Here are some screenshots from those slides that have to do with continuous integration.

What I don't know is if any of these DataverseEU resources will be made available to Dataverse developers like myself. I hope so! @4tikhonov should we mention any of this in the Dataverse Dev Guide? Can you please take a look at pull request #5751? Thanks!

[pdurbin]

I should also mentioned that I put a bug in @amberleahey 's ear about the new Jenkins service hosted by UNC (thank you @donsizemore and @jonc1438 ) by replying to her post about how @bikramj plans to use Jenkins for the language packs idea: https://groups.google.com/d/msg/dataverse-internationalization-wg/2zSl9xDpH7g/289KeyScBgAJ

[bikramj]

Thanks for the tag @pdurbin, we are heavy users of Jenkins for in-house CI and code deployments for all our apps to various environments. It would be great if we can use UNC's instance to automate language packs. I haven't started any work on it yet but planning to do so in a week or two.

[pdurbin]

We should reach out to the developers of the client libraries listed in the API Guide and coordinate with them to start testing their code from the new Jenkins service. Here are the the issues to track:

• Test with jenkins.dataverse.org dataverse-client-python#52 @skasberger
• Test with jenkins.dataverse.org  dataverse-client-r#22 @monogan @maxheld83
• Continuous integration (Travis or similar) dataverse-client-java#5 @richarda23

[jonc1438]

Odum is happy to run the Jenkins site on behalf of Dataverse and the Global Dataverse Community Consortium. It is a new service so let us know how it works or if anyone needs anything. As always contributions and documentation welcome and appreciated.

[pdurbin]

@bikramj great!

@jonc1438 thanks again!

One more thought is that while I love Travis CI and I think we should continue using it for stuff like "does the war file even compile", I would favor a belt-and-suspenders approach of someday adding equivalent Jenkins jobs for these Travis jobs (but still keeping the Travis jobs, I mean):

• https://travis-ci.org/IQSS/dataverse (added in IQSS/dataverse-jenkins@11638c9 )
• https://travis-ci.org/IQSS/dataverse-ansible
• https://travis-ci.org/IQSS/dataverse-metrics
• https://travis-ci.org/IQSS/DataTaggingLibrary