Replies: 1 comment
-
|
I would like to find homes for some of these abandoned resource types. I'm planning to put them in https://github.com/PixelAirIO/ instead of in the Concourse Github org though. It's definitely important to maintain a healthy resource ecosystem, but I don't want folks to think the main Concourse org will endlessly adopt resource types. I'm probably going to tackle the resource types found in the projects pipelines first: https://github.com/concourse/ci |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
There are some resource types like git-branches which have not been maintained in years and still show up in official documentation. Since these resource types are not bundled with concourse itself, there is no automatic process to update software versions and push new images for them.
For this reason, I'm continuous absorbing these resource types in Concourse.nix, and with Nix these resource types dependencies would be shipped in lockstep with Concourse nix package itself:
I'm also adding e2e concourse tests in the same repository to test these resources but progress may be slow.
Maybe something like this can exists in the concourse organization and there would be some automatic process that pushes out new images?
Beta Was this translation helpful? Give feedback.
All reactions