Pipelines: Your Doorway to Continuous Development
1–10 of 26 posts
Re: Pipelines: Your Doorway to Continuous Development
#2It doesn't seem to address the problem of migrating data from one version to the next.
Re: Pipelines: Your Doorway to Continuous Development
#3Buddy looks nice as service, nice job. It doesn't seem expensive so that's also a bonus, I guess the real test is the reliability of the service.
How long have you been working on the service?
Also, sorry for this, but my OCD is taking over:
> Wait, their could be more // their -> there
> your Pipeline got you covered // got -> has (unless you want to use slang, which could be an option)
Re: Pipelines: Your Doorway to Continuous Development
#4It doesn't seem to address the problem of migrating data from one version to the next.
Hi amelius, what do you mean by migrating data between versions?
Re: Pipelines: Your Doorway to Continuous Development
#5This initially came off as a new way to more efficiently manage project development and builds, but now it seems like it's just another CI platform. Or am I missing something?
Re: Pipelines: Your Doorway to Continuous Development
#6Buddy looks nice as service, nice job. It doesn't seem expensive so that's also a bonus, I guess the real test is the reliability of the service. How long have you been working on the service? Also, sorry for this, but my OCD is taking over: > Wait, their could be more // their -> there > your Pipeline got you covered // got -> has (unless you want to use slang, which could be an option)
Hi oblio,
Thanks for pointing out the errors, we'll fix that. We've been around for over a year with half a year of beta period before that.
The whole thing is really fast and stable: we chose Docker containers to run builds which ensures speed and compatibility across the whole team + contrary to some other CI/CD software we only deploy changed files which results in really fast deployments.
What languages/frameworks are you into?
Re: Pipelines: Your Doorway to Continuous Development
#7This initially came off as a new way to more efficiently manage project development and builds, but now it seems like it's just another CI platform. Or am I missing something?
Hi Chris,
Why do you think it's just another CI platform now? :)
Re: Pipelines: Your Doorway to Continuous Development
#8Buddy looks nice as service, nice job. It doesn't seem expensive so that's also a bonus, I guess the real test is the reliability of the service. How long have you been working on the service? Also, sorry for this, but my OCD is taking over: > Wait, their could be more // their -> there > your Pipeline got you covered // got -> has (unless you want to use slang, which could be an option)
Hi oblio, Thanks for pointing out the errors, we'll fix that. We've been around for over a year with half a year of beta period before that. The whole thing is really fast and stable: we chose Docker containers to run builds which ensures speed and compatibility across the whole team + contrary to some other CI/CD software we only deploy changed files which results in really fast deployments. What languages/framework…
Generally Java at work but Python and .NET when I get the chance. Is there any chance for Windows Docker containers? I know it's tricky and could be costly...
Re: Pipelines: Your Doorway to Continuous Development
#9It doesn't seem to address the problem of migrating data from one version to the next.
I find any talk about continuous integration that does not deal with migrations and data persistence a bit of a joke. I'm going to guess the writer is hoping to run migrations/db changes while maintenance mode is enabled.
Re: Pipelines: Your Doorway to Continuous Development
#10I use CircleCI and I am very satisfied. But I will take a look on Buddy, it seems more easy to configure, apparently.
CircleCI don't have a clear documentation about all the possibilites the service can do.