Skip to content
This repository was archived by the owner on Apr 16, 2025. It is now read-only.

Commit ab6c51d

Browse files
Merge pull request #23 from Jdubrick/archive-repo
Final Steps To Archive Repository
2 parents 69e9fd9 + af8fdc2 commit ab6c51d

File tree

3 files changed

+6
-29
lines changed

3 files changed

+6
-29
lines changed

.ci/Dockerfile

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,8 @@ COPY . /registry
1212
# Download the registry build tools
1313
RUN git clone https://github.com/devfile/registry-support.git /registry-support
1414

15+
RUN cd /registry-support && git checkout -f 4bc237b077e1bd478ea24195fac7c35fd2975441
16+
1517
# Run the registry build tools
1618
RUN /registry-support/build-tools/build.sh /registry /build
1719

CONTRIBUTING.md

Lines changed: 0 additions & 4 deletions
This file was deleted.

README.md

Lines changed: 4 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,9 @@
11
# devfile-registry
22

3-
Source repository for the Red Hat product devfile registry
3+
> [!WARNING]
4+
> This repository has been retired and will no longer be maintained. It has been archived and will remain read-only.
45
5-
This product devfile registry is updated weekly, by 12pm EST Wednesdays, with any updated stacks in this repository.
6-
7-
## Registry Updates
8-
9-
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.
10-
11-
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:
12-
13-
- Stack name
14-
- Why the refresh is needed
15-
- Why the refresh cannot wait until the next regularly scheduled refresh
6+
Source repository for the Red Hat product devfile registry.
167

178
## Developing
189

@@ -23,18 +14,6 @@ If you are a stack owner and need to request an urgent refresh of the registry s
2314

2415
### Build
2516

26-
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).
17+
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).
2718

2819
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).
29-
30-
## Contributing
31-
32-
For contributing Devfile stacks to this registry, please see [CONTRIBUTING.md](CONTRIBUTING.md).
33-
34-
For testing devfile stacks in the registry, or devfile stacks that you are contributing, please see the [testing doc](tests/README.md).
35-
36-
## Reporting any issue
37-
38-
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.
39-
40-
For issues relating to the hosted product devfile registry service in general, please use this repository for opening issues.

0 commit comments

Comments
 (0)