Ticket #1435 (closed enhancement: wontfix)
Switch to continuous.io for buildbot (?)
Reported by: | rgrp | Owned by: | |
---|---|---|---|
Priority: | awaiting triage | Milestone: | ckan-v1.6 |
Component: | ckan | Keywords: | |
Cc: | Repository: | ckan | |
Theme: | none |
Description
Change History
comment:2 Changed 2 years ago by thejimmyg
I personally can't see the benefit of switching to a generic paid service when we already have a highly customised and working infrastructure based on buildbot and buildkit - we do testing in VMs as well as continuous integration.
What is the advantage?
Suggest wont fix?
comment:3 Changed 2 years ago by dread
- Status changed from new to closed
- Resolution set to wontfix
From IRC today:
<rgrp> dread: btw have a big suggstion -- switch to continuous.io for our buildbot stuff ... <rgrp> openspending have done this and it's a nice setup ... <dread> rgrp: interesting - what's better? <dread> i assume it just starts a script and reports the result? <rgrp> that's right though also has integration with some bakcens (but we probably don't need that) <rgrp> the point is we don't need to boot machines, install and configure buildbot etc (though we may now have automated that ...) <dread> ah, i see, it's in the cloud <dread> did all that months ago, and don't need to setup the machine any more. <dread> if we do it again though, I'm all for it
Note: See
TracTickets for help on using
tickets.
Interesting. What's the reason to justify the effort?