You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
We'd like to deliver an example collection hub build pipeline to simplifying collection lifecycle management. Eventually, we'll teach kabanero to react to GitHub events to drive this pipeline.
The text was updated successfully, but these errors were encountered:
The same issue that @stephenkinder raised on the Collections board was closed by him with this comment:
"we decided to close this specific issue for now until we decide on the best way to approach moving forward to champ lifecycle. There is a proposal to extract the appsody stack and build configuration from the collection hub and point at the appsody stack from kabanero. If we separate concerns, it is likely we will have different build processes." (kabanero-io/collections#171 (comment))
Should this issue also be closed until it is decided what needs to be done. I don't want time and effort to be wasted doing this if it is deemed not needed at the moment.
We'd like to deliver an example collection hub build pipeline to simplifying collection lifecycle management. Eventually, we'll teach kabanero to react to GitHub events to drive this pipeline.
The text was updated successfully, but these errors were encountered: