Need advice about which tool to choose?Ask the StackShare community!
Concourse vs gulp: What are the differences?
Concourse: Pipeline-based CI system written in Go. Concourse's principles reduce the risk of switching to and from Concourse, by encouraging practices that decouple your project from your CI's little details, and keeping all configuration in declarative files that can be checked into version control; gulp: The streaming build system. Build system automating tasks: minification and copying of all JavaScript files, static images. More capable of watching files to automatically rerun the task when a file changes.
Concourse belongs to "Continuous Integration" category of the tech stack, while gulp can be primarily classified under "JS Build Tools / JS Task Runners".
"Real pipelines" is the primary reason why developers consider Concourse over the competitors, whereas "Build speed" was stated as the key factor in picking gulp.
Concourse and gulp are both open source tools. gulp with 31.3K GitHub stars and 4.4K forks on GitHub appears to be more popular than Concourse with 3.92K GitHub stars and 472 GitHub forks.
According to the StackShare community, gulp has a broader approval, being mentioned in 1158 company stacks & 690 developers stacks; compared to Concourse, which is listed in 18 company stacks and 17 developer stacks.
I'm planning to setup complete CD-CD setup for spark and python application which we are going to deploy in aws lambda and EMR Cluster. Which tool would be best one to choose. Since my company is trying to adopt to concourse i would like to understand what are the lack of capabilities concourse have . Thanks in advance !
I would definetly recommend Concourse to you, as it is one of the most advanced modern methods of making CI/CD while Jenkins is an old monolithic dinosaur. Concourse itself is cloudnative and containerbased which helps you to build simple, high-performance and scalable CI/CD pipelines. In my opinion, the only lack of skills you have with Concourse is your own knowledge of how to build pipelines and automate things. Technincally there is no lack, i would even say you can extend it way more easily. But as a Con it is more easy to interact with Jenkins if you are only used to UIs. Concourse needs someone which is capable of using CLIs.
Pros of Concourse
- Real pipelines16
- Containerised builds10
- Flexible engine9
- Fast6
- Open source4
- No Snowflakes3
- Simple configuration management3
- You have to do everything2
- Fancy Visualization1
Pros of gulp
- Build speed451
- Readable277
- Code-over-configuration244
- Open source210
- Node streams175
- Intuitive107
- Lots of plugins83
- Works great with browserify66
- Easy to Learn45
- Laravel-elixir17
- build workflow4
- Simple & flexible3
- Great community3
- Stylus intergration2
- Clean Code2
- jade intergration2
- Well documented0
Sign up to add or upvote prosMake informed product decisions
Cons of Concourse
- Fail forward instead of rollback pattern2