Actually, we do have a CI:
https://st-ci.cern.ch/
Aha! I did not know about this. That's already quite useful. It looks like it doesn't test GitHub PRs, but still 👍
For your questions:
Can we provide our own build nodes? Or does Travis provide their own build nodes? If we can only relay on Travis build nodes, how many do we get?
Travis provide the nodes. You're allowed to run whatever you like, but within a time limit of around an hour, I think.
Are you willing to maintain the Travis CI for XRootD?
Yes.
For what platforms can we build? Currently we are interested in epel6, epel7, latest 3 fedora releases, fedora-rawhide, and OSX, can we cover that with Travis?
The available environments are defined here:
https://docs.travis-ci.com/user/ci-environment/
You only get 'one Linux', Ubuntu, and macOS. So, Travis won't replace your more comprehensive Jenkins tests (not to write it off entirely, but testing on multiple platforms is a good idea).
At least the release builds should be done with mock, as they go to epel/fedora, can we do that with Travis CI?
The only "mock" I'm familiar with is the Python testing module, and then I don't understand what you mean 😄 So I guess there must be another mock?
Can we run unit/functional tests in docker containers?
Yep! You can run whatever commands you like, defined in a Travis configuration file.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/xrootd/xrootd","title":"xrootd/xrootd","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/xrootd/xrootd"}},"updates":{"snippets":[{"icon":"PERSON","message":"@alexpearce in #502: \u003e Actually, we do have a CI:\r\n\u003e https://st-ci.cern.ch/\r\n\r\nAha! I did not know about this. That's already quite useful. It looks like it doesn't test GitHub PRs, but still 👍 \r\n\r\nFor your questions:\r\n\r\n\u003e Can we provide our own build nodes? Or does Travis provide their own build nodes? If we can only relay on Travis build nodes, how many do we get?\r\n\r\nTravis provide the nodes. You're allowed to run whatever you like, but within a time limit of around an hour, I think.\r\n\r\n\u003e Are you willing to maintain the Travis CI for XRootD?\r\n\r\nYes.\r\n\r\n\u003e For what platforms can we build? Currently we are interested in epel6, epel7, latest 3 fedora releases, fedora-rawhide, and OSX, can we cover that with Travis?\r\n\r\nThe available environments are defined here:\r\n\r\nhttps://docs.travis-ci.com/user/ci-environment/\r\n\r\nYou only get 'one Linux', Ubuntu, and macOS. So, Travis won't replace your more comprehensive Jenkins tests (not to write it off entirely, but testing on multiple platforms _is_ a good idea).\r\n\r\n\u003e At least the release builds should be done with mock, as they go to epel/fedora, can we do that with Travis CI?\r\n\r\nThe only \"mock\" I'm familiar with is the Python testing module, and then I don't understand what you mean 😄 So I guess there must be another mock?\r\n\r\n\u003e Can we run unit/functional tests in docker containers?\r\n\r\nYep! You can run whatever commands you like, defined in a [Travis configuration file](https://docs.travis-ci.com/user/customizing-the-build/)."}],"action":{"name":"View Issue","url":"https://github.com/xrootd/xrootd/issues/502#issuecomment-293306330"}}}
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1