Software Alternatives, Accelerators & Startups
Register | Login

Concourse VS Step in Time

Compare Concourse VS Step in Time and see what are their differences

IsDown.app
Monitor all your cloud services with our status page aggregator. IT teams choose IsDown to monitor all their vendors and get alerts whenever an outage occurs. Integration with Datadog, PagerDuty, Slack, Microsoft Teams, and a lot more. featured
This page does not exist
Contents:
  1. » Base Details
  2. » Videos
  3. » Reviews
  4. » Alternatives

Concourse logo Concourse

Pipeline-based CI system written in Go

Step in Time logo Step in Time

A music player app for rehearsals
  • Concourse Landing page
    Landing page //
    2021-07-31
  • Step in Time Landing page
    Landing page //
    2020-01-14

Concourse features and specs

  • Simplicity and Consistency
    Concourse CI offers a simple and consistent UI/UX across different platforms. The interface is intuitive and designed to make it easy for users to visualize complex pipelines.
  • Containerized Builds
    Everything Concourse runs is within containers, ensuring isolated and reproducible builds. This method reduces the chances of environment-related issues during the deployment process.
  • Pipeline as Code
    Concourse utilizes a declarative approach to define pipelines using YAML files, which makes versioning and changing pipelines straightforward and trackable.
  • Scalability
    Concourse is highly scalable and can work well with very large pipelines and numerous concurrent builds, especially fitting for microservices architectures.
  • Dynamic Workflows
    It supports dynamic workflows through its resource/event-driven nature, allowing pipelines to react automatically to changes in resources.

Possible disadvantages of Concourse

  • Steeper Learning Curve
    New users might find Concourse's approach to pipeline as code and its unique abstractions more challenging to grasp initially compared to other CI/CD tools.
  • Limited Plugin Ecosystem
    Compared to other CI/CD platforms, Concourse has a more limited plugin ecosystem, which may require building custom resources for specific tasks that are readily available in other solutions.
  • Resource Intensity
    Due to its containerization strategy, Concourse can be resource-intensive, particularly if not appropriately managed or scaled.
  • Less Community Support
    Although active, the community around Concourse CI is smaller than those for more established CI/CD tools like Jenkins, which can result in fewer community-contributed plugins and resources.
  • Complex Configuration
    While powerful, the configuration files can become complex and hard to manage for large-scale deployments, requiring significant maintenance effort.

Step in Time features and specs

No features have been listed yet.

Concourse videos

+ Add

Concourse Smart Wheels - Review

More videos:

  • Review - Australian Golf Digest TV - Concourse CBM3 Golf Buggy
  • Review - THE GOLF SHOW CONCOURSE CBM3

Step in Time videos

+ Add

Step In Time Dance Review

More videos:

  • Review - Step in Time Group 2 Vocal Review
  • Review - Step in Time Sweeps Vocal Review

Category Popularity

0-100% (relative to Concourse and Step in Time)

Concourse

Step in Time

Continuous Integration
86 86%
Continuous Integration
14% 14
DevOps Tools
84 84%
DevOps Tools
16% 16
Continuous Deployment
86 86%
Continuous Deployment
14% 14
Code Collaboration
100 100%
Code Collaboration
0% 0

User comments

Share your experience with using Concourse and Step in Time. For example, how are they different and which one is better?
Log in or Post with

Social recommendations and mentions

Based on our record, Concourse seems to be more popular. It has been mentiond 22 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.

Concourse mentions (22)

  • Tracking Supermarket Prices with Playwright
    > My CI of choice is [Concourse](https://concourse-ci.org/) which describes itself as "a continuous thing-doer". While it has a bit of a learning curve, I appreciate its declarative model for the pipelines and how it versions every single input to ensure reproducible builds as much as it can. What's the thought process behind using a CI server - which I thought is mainly for builds - for what essentially is a data... - Source: Hacker News / 10 months ago
  • We built the fastest CI in the world. It failed
    > Imagine you live in a world where no part of the build has to repeat unless the changes actually impacted it. A world in which all builds happened with automatic parallelism. A world in which you could reproduce very reliably any part of the build on your laptop. That sounds similar to https://concourse-ci.org/ I quite like it, but it never seemed to gain traction outside of Cloud Foundry. - Source: Hacker News / over 1 year ago
  • Ask HN: What do you use to run background jobs?
    I used Concourse[0] for a while. No real complaints, the visibility is nice but the functionality isn't anything new. [0] https://concourse-ci.org/. - Source: Hacker News / almost 2 years ago
  • How to host React/Next "Cheaply" with a global audience? (NGO needs help)
    We run https://concourse-ci.org/ on our own hardware at our office. (as a side note, running your own hardware, you realise just how abysmally slow most cloud servers are.). Source: about 2 years ago
  • Cicada - Build CI pipelines using TypeScript
    We use https://concourse-ci.org/ at the moment and have been reasonably happy with it, however it only has support for linux containers at the moment, no windows containers. (MacOS doesn't have a containers primitive yet unfortunately). Source: about 2 years ago
View more

Step in Time mentions (0)

We have not tracked any mentions of Step in Time yet. Tracking of Step in Time recommendations started around Mar 2021.

What are some alternatives?

When comparing Concourse and Step in Time, you can also consider the following products

Jenkins - Jenkins is an open-source continuous integration server with 300+ plugins to support all kinds of software development

Screwdriver - Yahoo's Continuous Delivery Build System for Dynamic Infrastructure

Codeship - Codeship is a fast and secure hosted Continuous Delivery platform that scales with your needs.

Prevalent ThirdParty Risk Management - Prevalent ThirdParty Risk Management is an online service that offers cyber-attack security risk management for your company.

Travis CI - Simple, flexible, trustworthy CI/CD tools. Join hundreds of thousands who define tests and deployments in minutes, then scale up simply with parallel or multi-environment builds using Travis CI’s precision syntax—all with the developer in mind.

Taskcluster - Taskcluster is the task execution framework that supports Mozilla's continuous integration and...

Loading...