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

[packit] Copr enhancements #872

Merged

Conversation

lachmanfrantisek
Copy link
Member

@lachmanfrantisek lachmanfrantisek commented Jun 19, 2020

  • Be able to set listed_on_hp,preserve_project,additional_repos in CLI for copr-build.
  • Allow setting/editing of unlisted_on_hp,temporary,additional_repos for copr projects.
  • Add new fields for metadata about copr-builds.
  • Fixes: Add support for COPR external repositories #774
  • Users can set also additional_packages in config but it's not used yet. (Needs to be set per-chroot and will take more time to make it properly.)
  • PR in packit-service with proper tests will follow.

@lachmanfrantisek lachmanfrantisek added the 🌞 friday 🤟 Weekend is coming! label Jun 19, 2020
packit/cli/copr_build.py Outdated Show resolved Hide resolved
packit/cli/copr_build.py Outdated Show resolved Hide resolved
is_flag=True,
)
@click.option(
"--preserve-project",
Copy link
Contributor

Choose a reason for hiding this comment

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

Could an option taking the number of days to preserve the project offer more flexibility? 0 could mean "preserve forever" while the default could be 60.

Copy link
Member Author

Choose a reason for hiding this comment

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

Tha will also save us some problems with overwriting since I am not sure (now) how I can unset the deletion.

But is it useful for users? I would say that they want to either preserve or remove automatically the project. Do they care about specific numbers?

Copy link
Contributor

Choose a reason for hiding this comment

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

Why do we need to unset deletion?

Yeah, you have a point, maybe users don't care about the numbers that much, and if they do, it might be better to control those numbers in a separate option.

Copy link
Member Author

Choose a reason for hiding this comment

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

Why do we need to unset deletion?

It can be useful when they don't know about that option in the time when the project is created or the option is not present (e.g. our project for master builds of packit has it said and we can't edit that via packit.)

Copy link
Contributor

Choose a reason for hiding this comment

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

Based on the current help text I would expect expiration to be set only when the project is created by Packit:

Created copr project will not be removed after 60 days.

So when the Copr project already exists, I would expect this flag to have no effect.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, this will be tricky since no-value and default-value cannot be easily differentiated...

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

@lachmanfrantisek lachmanfrantisek changed the title Copr enhancements [packit] Copr enhancements Jun 19, 2020
- list_on_homepage
- preserve_project
- additional_packages
- additional_repos

Signed-off-by: Frantisek Lachman <flachman@redhat.com>
- list_on_homepage
- preserve_project
- additional_repos

The option additional_packages does not work yet since it's chroot specific.
If the temporary option is switched to False, the deletion will probably not be disabled.

Signed-off-by: Frantisek Lachman <flachman@redhat.com>
- --list-on-homepage
- --preserve-project
- --additional_repos

Signed-off-by: Frantisek Lachman <flachman@redhat.com>
@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

Will allow us to determine this in packit-service.

Signed-off-by: Frantisek Lachman <flachman@redhat.com>
@packit-as-a-service-stg
Copy link

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

  • sudo yum install -y dnf-plugins-core on RHEL 8
  • sudo dnf install -y dnf-plugins-core on Fedora
  • dnf copr enable packit/packit-service-packit-872-stg
  • And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

@softwarefactory-project-zuul
Copy link
Contributor

Build failed.

@lachmanfrantisek
Copy link
Member Author

recheck

@lachmanfrantisek
Copy link
Member Author

/packit test

@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded.

@lachmanfrantisek lachmanfrantisek added the mergeit When set, zuul wil gate and merge the PR. label Jun 20, 2020
@softwarefactory-project-zuul
Copy link
Contributor

Build succeeded (gate pipeline).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🌞 friday 🤟 Weekend is coming! mergeit When set, zuul wil gate and merge the PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for COPR external repositories
3 participants