Hacker News new | ask | show | jobs
by nstart 3266 days ago
Not sure when it came about, but when I first evaluated Concourse, not being able to trigger jobs manually was a primary blocker. Glad this showed up on HN again, because they've added it in at some point. My favourite thing about Concourse was really its ideas around "Resources". This always felt so much better than this idea of plugins due to how unified the experience was. Also, the ability to implement resources for yourself is extremely easy. So if I had an internal software running, being able to build something for it meant defining three bash scripts.

That said, the docs around implementing resources still needs some improvements. Whatever I learnt was from cloning and modifying existing resources.
1 comments
fatterypt 3266 days ago
This is also close to my experience. Improving, but not there yet. Unfortunately, it will retrigger the same job with the updated version of the resources. With other CI tools, it was possible to replay the same job, with whatever inputs they took by the time they ran, with concourse it does not seem t be possible.

A practical impact of this issue is that we cannot simply reprocess a previous deploy step, with the old artifacts and inputs in a middle of an outage.

link
wlamartin 3266 days ago
You can achieve this by clicking on a resource and hitting toggling the "power button" to off for each of the resources you don't want to include in the build.
link
fatterypt 3266 days ago
While this may even work, it is not practical and it is a disappointing experience for a pipeline centric type of CI such as concourse.

In other tools, hitting re-run would simply replay the job, with the same state it was executed in the first run. I would expect concourse to behave similarly, but no.

link
jacques_chester 3265 days ago
> In other tools, hitting re-run would simply replay the job, with the same state it was executed in the first run.

If the job failed, you get this. Otherwise I figure that the idea is that you're satisfied with those versions of the resources acted on by the job.

Disclosure: I work for Pivotal.

link
wlamartin 3266 days ago
I guess I'm not clear on why you would be wanting to do this so frequently that the toggle is impractical, though it's likely that I simply haven't come across this use case.
link