Hacker News new | comments | show | ask | jobs | submit login

Have been working with it for a few months, and I am not positive about it.

UI is pretty but often breaks. Is unusable when you have a pipeline with dozens of concurrent jobs.

Concept of teams is fine, but when you have to switch between them, even with oauth authentication, it is a pain.

Job concurrency control is binary.

We never have been able to have worker pool scale down without a hiccup, always some darn worker hogging containers and atc not removing it, leading to stalled pipelines.

That overlay network it comes with, garden thingy, creates so many problems and solves just one...

Oh and not having BUILD_ vars available in tasks is rude, thank you very much, but there are cases when it is just mandatory and concourse makes it impossible to do.

At least new version has better secrets handling, previously it was a joke.




> UI is pretty but often breaks. Is unusable when you have a pipeline with dozens of concurrent jobs.

Find this hard to believe - we have some pretty spectacular pipelines which render without a hiccup.


My experience after having the browser UI open is that intially stuff renders, then starts to take ages to update state ( these pretty pulsing frames are no longer showing or rendering badly ). Quite often switching to a different pipeline renders empty space.

Also, when you have around 100+ resources and jobs in one pipeline, in a vertical plane, they are impossible to identify


100+ jobs will break your browser. RabbitMQ has been complaining about it for a while.


100+ jobs in one pipeline?


Yes, some systems we work with have over 100 items ( jobs and resources) in one pipeline ... because microservices...


> That overlay network it comes with, garden thingy, creates so many problems and solves just one...

Can you expand upon this a little bit? Garden is the containerisation piece, what about it creates problems and what single problem do you think it is solving?


> UI is pretty but often breaks. Is unusable when you have a pipeline with dozens of concurrent jobs.

Are you running it on a potato? :) We have massive builds that have never had problems in the UI.


I have seen it, with not too many pipelines, and it just falls over. (and no, it is not a potato - its a pretty large bare metal machine)


There is a drain / purge endpoint you could look into for scaling down workers.

Admittedly I don't do it often, but I haven't experienced a problem with it when I have.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | DMCA | Apply to YC | Contact

Search: