Skip to content

Conversation

vaibhavdaren
Copy link
Collaborator

@vaibhavdaren vaibhavdaren commented Sep 2, 2025

In this Pull request, I have added support for the Repository-File artifact type for the Almighty Install Plugin.
The classes add support for the file type.

  • implement the feature
  • Initial Review

For the next PR: #3995 (comment)

@vaibhavdaren vaibhavdaren self-assigned this Sep 2, 2025
@vaibhavdaren vaibhavdaren added the ci | skip Do not run any tests (useful for very early drafts). label Sep 2, 2025
@vaibhavdaren vaibhavdaren marked this pull request as draft September 2, 2025 22:55
@vaibhavdaren vaibhavdaren added this to the 1.57 milestone Sep 3, 2025
@github-project-automation github-project-automation bot moved this to backlog in planning Sep 3, 2025
@vaibhavdaren vaibhavdaren moved this from backlog to implement in planning Sep 3, 2025
@vaibhavdaren vaibhavdaren force-pushed the almight-repo-file branch 2 times, most recently from 2fa47a5 to 9c7d609 Compare September 3, 2025 09:49
@vaibhavdaren vaibhavdaren linked an issue Sep 3, 2025 that may be closed by this pull request
@vaibhavdaren vaibhavdaren requested a review from happz September 3, 2025 11:00
@happz
Copy link
Collaborator

happz commented Sep 3, 2025

@vaibhavdaren would it make sense to rebase this PR on top of the koji/brew one? #4011 That one seems to be adding the basic structure, and koji/brew "artifacts", I would expect the repository file to build upon that, adding new artifact type, sharing the directories with koji/brew providers, and so on.

@vaibhavdaren vaibhavdaren changed the base branch from main to avinay-brew-koji-build-helpers September 4, 2025 09:19
@vaibhavdaren vaibhavdaren force-pushed the almight-repo-file branch 2 times, most recently from a1d5fb3 to c2f378d Compare September 4, 2025 09:55
@github-project-automation github-project-automation bot moved this from implement to done in planning Sep 4, 2025
@vaibhavdaren vaibhavdaren reopened this Sep 4, 2025
@vaibhavdaren
Copy link
Collaborator Author

@vaibhavdaren would it make sense to rebase this PR on top of the koji/brew one? #4011 That one seems to be adding the basic structure, and koji/brew "artifacts", I would expect the repository file to build upon that, adding new artifact type, sharing the directories with koji/brew providers, and so on.

I have rebased on top of his branch. Changed functions to match signatures. Let me review the orginal CR and put my thoughts on that as well.

Copy link
Collaborator

@LecrisUT LecrisUT left a comment

Choose a reason for hiding this comment

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

I think for this PR the focus should be more on the design of the prepare plugin, namely:

  • Creating the PrepareRepoData and PrepareRepo skeleton, you can reference the prepare install plugin
    @container
    class PrepareInstallData(tmt.steps.prepare.PrepareStepData):

    @tmt.steps.provides_method('install')
    class PrepareInstall(tmt.steps.prepare.PreparePlugin[PrepareInstallData]):

    (Naming of course flexible)
  • Hook into the providers to download the artifacts and do the actual repo creation
  • Misc adjustments like hooking into the schema and other stuff that would pop up

You could also focus this PR on the second point if you think the scope could be too big

@AthreyVinay
Copy link
Collaborator

FYI - there are still ongoing structural changes to the abstract class implementation :)

@AthreyVinay AthreyVinay force-pushed the avinay-brew-koji-build-helpers branch from dc2cc84 to 6b79896 Compare September 5, 2025 15:38
@vaibhavdaren vaibhavdaren moved this from done to review in planning Sep 8, 2025
@vaibhavdaren vaibhavdaren marked this pull request as ready for review September 8, 2025 18:51
Copy link
Collaborator

@psss psss left a comment

Choose a reason for hiding this comment

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

Looks like a good kick-off, thanks! I would just place the repository enablement implementation under a new method which would be used across all providers.

@vaibhavdaren vaibhavdaren requested a review from happz October 3, 2025 13:31
@vaibhavdaren vaibhavdaren requested a review from psss October 3, 2025 14:00
Copy link
Collaborator

@psss psss left a comment

Choose a reason for hiding this comment

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

Thanks! Sounds good enough as the first version, let's start from here.

@thrix
Copy link
Collaborator

thrix commented Oct 6, 2025

/packit retest-failed

@thrix thrix moved this from review to merge in planning Oct 6, 2025
vaibhavdaren and others added 13 commits October 8, 2025 01:03
This file provides classes for handling repository file artifacts in the tmt framework.
It includes the `RepositoryFileInfo` class, which encapsulates metadata about a repository
file. Fix #3995
**Note**: This separate PR enables a focused "work-shopping" session on
the class structure. Isolating this major change from the much larger PR
(#4018) provides clarity for discussion and refinement. This separation
is a temporary measure, as the code will ultimately be a single commit
within the main PR.

* [x] Change the base structure skeleton
Co-authored-by: graphite-app[bot] <96075541+graphite-app[bot]@users.noreply.github.com>
@psss psss force-pushed the almight-repo-file branch from 2734c62 to 0cedcf4 Compare October 7, 2025 23:04
@psss
Copy link
Collaborator

psss commented Oct 8, 2025

The two failures are irrelevant, merging.

@psss psss merged commit 3a64256 into main Oct 8, 2025
24 of 25 checks passed
@psss psss deleted the almight-repo-file branch October 8, 2025 05:27
@github-project-automation github-project-automation bot moved this from merge to done in planning Oct 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci | full test Pull request is ready for the full test execution plugin | artifact Related to the `prepare/artifact` plugin. step | prepare Stuff related to the prepare step
Projects
Status: done
Development

Successfully merging this pull request may close these issues.

7 participants