On Tue, Sep 26, 2017 at 2:45 AM, Mike Jumper <[email protected]> wrote:
> On Mon, Sep 25, 2017 at 7:38 PM, Nick Couchman <[email protected]> wrote: > > > There's been some churn in the community of folks wanting some support > for > > continuous integration with the Guacamole repos. Travis CI has come up a > > couple of times - I stumbled across it and thought it might be useful, > and > > another contributor opened a PR for adding the travis.yml files for the > > client and server repos. However, Mike also pointed out that ASF also > > operates a Jenkins instance that we could leverage. > > > > So, the two questions up for discussion are: > > > > 1) Do we want to leverage a CI system, such as Jenkins or Travis, for the > > Guacamole code? > > > > > Yes. > > ... > > My personal votes are: > > > > 1) Yes, we should leverage some sort of CI system, like Jenkins, for > making > > up-to-date builds available. While the Guacamole code is relatively > small > > and easy to build yourself, there are certainly instances, both while > > developing and while testing and using the product, that it's useful to > > have those pre-built binaries available. > > > > > It's probably important to distinguish between CI and generation of nightly > binary builds. CI has far more to offer than just providing pre-built > binaries, and Guacamole would greatly benefit from CI. > > ... > > http://www.apache.org/legal/release-policy.html#host-rc > > Also: > > http://www.apache.org/legal/release-policy.html#release-types > > Specifically: > > "Nightly Builds ... are intended for regular testing of the build process > and to give automated testers a common build for regression testing. They > are not intended for use by the general public." > Good to know. Nightly builds for dev/test only. > > 2) Personally I don't have an affinity for one CI system or another - if > > ASF provides Jenkins, seems like that's probably the best way to go, but > > I'm not familiar enough with Jenkins or Travis or any of the others to > know > > what the merits of one are vs. another. > > > > I'm pretty squarely in the Jenkins camp, as I've found Travis overly > limiting and separation-of-concerns-violatey: > > https://github.com/apache/incubator-guacamole-server/ > pull/110#issuecomment-331723648 > > ... but am curious what others here think. > > - Mike > Sounds good - I agree that having the Travis CI code inside the repo seems a little...odd, and that it feels cleaner to have the build system handling things completely separate from the code. Jenkins is fine with me, the more-so since ASF runs an instance. -Nick
