diff --git a/.ci/Dockerfile b/.ci/Dockerfile index 942507a..0f6d11c 100644 --- a/.ci/Dockerfile +++ b/.ci/Dockerfile @@ -12,6 +12,8 @@ COPY . /registry # Download the registry build tools RUN git clone https://github.com/devfile/registry-support.git /registry-support +RUN cd /registry-support && git checkout -f 4bc237b077e1bd478ea24195fac7c35fd2975441 + # Run the registry build tools RUN /registry-support/build-tools/build.sh /registry /build diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md deleted file mode 100644 index 5c69754..0000000 --- a/CONTRIBUTING.md +++ /dev/null @@ -1,4 +0,0 @@ -# Contributing to this registry - -This document outlines the requirements for contributing a devfile stack or sample to this repository. -See [devfile registry contributing guide](https://github.com/devfile/registry/blob/main/CONTRIBUTING.md) for details. diff --git a/README.md b/README.md index 05dbdb3..93c5354 100644 --- a/README.md +++ b/README.md @@ -1,18 +1,9 @@ # devfile-registry -Source repository for the Red Hat product devfile registry +> [!WARNING] +> This repository has been retired and will no longer be maintained. It has been archived and will remain read-only. -This product devfile registry is updated weekly, by 12pm EST Wednesdays, with any updated stacks in this repository. - -## Registry Updates - -The staging product devfile registry is refreshed upon each commit to main in this repository. Production is promoted manually and as mentioned above, is done each Wednesday, as needed. - -If you are a stack owner and need to request an urgent refresh of the registry service before Wednesday (for example if a stack is broken), please open an issue in this repository outlining the following: - -- Stack name -- Why the refresh is needed -- Why the refresh cannot wait until the next regularly scheduled refresh +Source repository for the Red Hat product devfile registry. ## Developing @@ -23,18 +14,6 @@ If you are a stack owner and need to request an urgent refresh of the registry s ### Build -To build this devfile registry into a container image run `.ci/build.sh`. A container image will be built using the [devfile registry build tools](https://github.com/devfile/registry-support/tree/master/build-tools). +To build this devfile registry into a container image run `.ci/build.sh`. A container image will be built using the [devfile registry build tools](https://github.com/devfile/registry-support/tree/master/build-tools) up until commit [4bc237b](https://github.com/devfile/registry-support/commit/4bc237b077e1bd478ea24195fac7c35fd2975441). From there, push the container image to a container registry of your choice and deploy using one of the methods outlined [here](https://github.com/devfile/registry-support#deploy). - -## Contributing - -For contributing Devfile stacks to this registry, please see [CONTRIBUTING.md](CONTRIBUTING.md). - -For testing devfile stacks in the registry, or devfile stacks that you are contributing, please see the [testing doc](tests/README.md). - -## Reporting any issue - -For issues relating to a specific devfile stack in this repository, please reach out to the devfile stack maintainer to determine where to open an issue. - -For issues relating to the hosted product devfile registry service in general, please use this repository for opening issues.