5725 initial CI documentation

[donsizemore]

New Contributors

Welcome! New contributors should at least glance at CONTRIBUTING.md, especially the section on pull requests where we encourage you to reach out to other developers before you start coding. Also, please note that we measure code coverage and prefer you write unit tests. Pull requests can still be reviewed without tests or completion of the checklist outlined below. Thanks!

Related Issues

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

Pull Request Checklist

• Unit tests completed
• Integration tests: None
• Deployment requirements, SQL updates, Solr updates, etc.: None
• Documentation completed
• Merged latest from "develop" branch and resolved conflicts

[coveralls]

Coverage remained the same at 17.99% when pulling 42c6f81 on OdumInstitute:5725_CI_documentation into 879bb73 on IQSS:develop.

[pdurbin]

@donsizemore I'm glad you're characterizing the dataverse-jenkins (the git repo) and https://jenkins.dataverse.org as a work in progress. I think you've stubbed this out very well. Thanks!!

[qqmyers]

The documentation looks fine to me. FWIW QDR isn't using this at present (except for the connection through PRs) - we have a different Chef/Jenkins/Github integration going. Might be something we can leverage going forward though...

[pdurbin]

except for the connection through PRs

@qqmyers thanks, can you please expand on this a bit? Right now we have Travis integrated such that we see when checks done by Travis pass or fail, like this example from pull request #5621:

Are you saying that from GitHub you see "All checks have passed" (or failures) based on testing done on Jenkins?

[qqmyers]

@pdurbin - I just meant that I use Dataverse's build system when I submit PRs. Otherwise, when I'm developing, I'm relying on QDR's build system and checking test results in our jenkins console, etc. W.r.t. integration, I'm not sure how its done in QDR, but new builds are triggered by my commits to github - I don't think the results get back to github (not sure I've looked).

[4tikhonov]

Hi @pdurbin and others, we're not going to create a clone of Dataverse, the idea that all our contribution should go to the master branch. And we already have first priorities for development in DataverseEU.

[pdurbin]

@4tikhonov yes, of course, and we're looking forward to pull requests from you and the rest of the DataverseEU developers! What I was trying to say at #5725 (comment) is that I'm wondering if I can get an account on your CI pipeline system. I showed your slides to @djbrooke this morning and said, "It's like Slava's throwing a continuous integration party and I hope I get invited!" 🎉 🎈 Is it possible for me to trigger a build on your system and see if I broke anything when I push code? Do I need an account? Can I get an account? 😄 I'd love to play in your playground, if you're ok with that. 😄

[4tikhonov]

@pdurbin, sure, I think it's not a problem. We're discussing now to setup two different DataverseEU instances, first on CESSDA Google Cloud (for sure) and second on Kubernetes cluster in Poland (it has to be finally decided). Guys from Poland also interested to deliver polish translation, so just stay tuned. :)

[landreev]

Thank you Don!