News for hackers. Stuff that matters.
Re:Concourse CI by abraham_s on Monday July 17, 2017 @10:47AM (#14788921)
I evaluated concourse CI and I was impressed by the concept.

Pros - Setup was really easy.(I didn't use bosh). - Both server and build pipeline configuration (Yaml file) are easy to backup and recreate.

Cons - When I evaluated it , it had a few bugs which forced me to restart the server almost daily to keep it working. It should be more stable now.

-

Re:Concourse CI by jadeklerk on Monday July 17, 2017 @10:51AM (#14788964)
Did your evaluation happen a long time ago? Or, another question... did you run the binaries and appropriately screen them? I had the same problem until I realized I sucked at making a binary live a long time, and my eyes were opened to screen :)
Re:Concourse CI by abraham_s on Thursday July 20, 2017 @12:00AM (#14809934)
It was a known bug in the some go library. It was recently fixed. But at the time it caused concourse to stop working until restarted.
Re:Concourse CI by mugsie on Monday July 17, 2017 @12:05PM (#14789787)
Never run long running services in screen. Use a proper init system - screen is not the solution.