Skip to content

Conversation

PerseidMeteor
Copy link
Collaborator

Now same repoes with different tag converts with same cache repo, but the cache tag is different. This will result in very few or even no use of the cache layer in the converted cache, so we have make the same repo using the same tagged cache repo.

change

  • make cache repo with same tag

@PerseidMeteor PerseidMeteor force-pushed the feat-use-one-cache-repo branch from 97201f7 to 785c74d Compare September 1, 2023 03:08
@PerseidMeteor PerseidMeteor force-pushed the feat-use-one-cache-repo branch 2 times, most recently from 3361bb4 to c147c7f Compare September 1, 2023 07:17
Now  same repoes with different tag converts with same cache repo, but the cache tag is different. This will result in very few or even no use of the cache layer in the converted cache, so we have make the same repo using the same tagged cache repo.

Signed-off-by: YuQiang <y_q_email@163.com>
@PerseidMeteor PerseidMeteor force-pushed the feat-use-one-cache-repo branch from c147c7f to 4a854ed Compare September 4, 2023 12:05
Copy link
Collaborator

@imeoer imeoer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, LGTM!

@imeoer imeoer merged commit f1e1593 into goharbor:main Sep 5, 2023
@PerseidMeteor PerseidMeteor deleted the feat-use-one-cache-repo branch September 5, 2023 02:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants