This repository has been archived by the owner on Jan 27, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 102
Adjust snapshot branch to build distribution Docker image #88
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
# Here the version of the registry is specified this storage branch uses. | ||
# It should always be a specific version to make sure builds are reproducible. | ||
ARG PACKAGE_REGISTRY=57d417a84fa038cfb50a0cd661372c194199b3fd | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @jsoriano Registry version is fixed. Here it is a commit hash but i expect it will become a released version soon. |
||
FROM docker.elastic.co/package-registry/package-registry:${PACKAGE_REGISTRY} | ||
|
||
LABEL package-registry=${PACKAGE_REGISTRY} | ||
|
||
# Adds specific config and packages | ||
COPY deployment/package-registry.yml /registry/config.yml | ||
COPY packages /packages | ||
|
||
# TODO: Find way to also copy in packages from staging and production | ||
|
||
# Sanity check on the packages. If packages are not valid, container does not even build. | ||
RUN ./package-registry -dry-run |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
package_paths: | ||
- /packages | ||
|
||
cache_time.search: 10s | ||
cache_time.categories: 10s | ||
cache_time.catch_all: 10s |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kuisathaverat for now, I just made this up. Not sure if this is going to work.
The goal is that as soon as this PR is merged, it pushes to
docker.elastic.co/package-registry/distribution:snapshot
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
currently, the pipeline uses the BRANCH_NAME as tag so it will push to
docker.elastic.co/package-registry/distribution:master
, we push for every branch or tag.if we want to change it to
docker.elastic.co/package-registry/distribution:snapshot
for the master branch it is easy to make, Do we want to publish other branches to that namespace (docker.elastic.co/package-registry
)?I see that there is a branch name snapshot, it push to
docker.elastic.co/package-registry/distribution:snapshot
but is not the master branchThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This PR is against the
snapshot
branch. Does this mean it is just going to work?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ouch!!, I didn't realize that the PR is against the snapshot branch, yep it makes the thing