Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle registry boards in processor #592

Merged
merged 3 commits into from
Jul 3, 2023
Merged

Handle registry boards in processor #592

merged 3 commits into from
Jul 3, 2023

Conversation

AbdulrhmnGhanem
Copy link
Member

I tried three approaches to handle the registry boards:

  1. clone the repo, checkout the hash, create an empty gitea repo, and push to gitea (the most complicated)

  2. migrate the repo, clone it, and change the default branch, and push

  3. checkout the hash in the processor (the cleanest)

I settled for making the processor handle the registry boards.

@AbdulrhmnGhanem AbdulrhmnGhanem marked this pull request as draft June 30, 2023 13:06
@AbdulrhmnGhanem AbdulrhmnGhanem marked this pull request as ready for review July 1, 2023 16:53
processor/src/queues.ts Outdated Show resolved Hide resolved
Comment on lines 187 to 190
if (registryHash) {
// no need to pull if we aren't going to use the latest commit
done()
}
Copy link
Member

Choose a reason for hiding this comment

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

But you are still pulling below, you are just releasing the lock early?

Copy link
Member Author

Choose a reason for hiding this comment

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

Resolved in 68230b6.

processor/src/queues.ts Outdated Show resolved Hide resolved
processor/src/queues.ts Outdated Show resolved Hide resolved
AbdulrhmnGhanem and others added 2 commits July 3, 2023 00:10
Co-authored-by: Kaspar Emanuel <kaspar.emanuel@gmail.com>
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