You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Some of our publishers publish embargoed packages that require them to run pipelines a few hours prior to release. However, this method introduces a few areas of unreliability, including pipeline agent failure, network issues, authentication problems surrounding config changes, etc. that can end up delaying their release.
Describe the solution you'd like
It would be ideal if Pulp is able to support scheduled package adding and repo publishing following that. Publishers would be able to build their packages, upload their packages, and then schedule a time for Pulp to perform the add and publish actions. If anything goes wrong during the upload/scheduling process, publishers can resolve them earlier without delaying their release schedule. But once that is complete, Pulp will guarantee that their packages are distributed publicly on time without additional issues.
Describe alternatives you've considered
Our alternative here is to use a separate container that publishers can use to schedule future releases. The container would have a db and regularly check if it needs to add/publish packages in Pulp. If there is a scheduled task, the container calls Pulp to add the packages to the repo and publish them.
Additional context
Could be related to #6104, but wanted to hear some thoughts on this before proceeding.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Some of our publishers publish embargoed packages that require them to run pipelines a few hours prior to release. However, this method introduces a few areas of unreliability, including pipeline agent failure, network issues, authentication problems surrounding config changes, etc. that can end up delaying their release.
Describe the solution you'd like
It would be ideal if Pulp is able to support scheduled package adding and repo publishing following that. Publishers would be able to build their packages, upload their packages, and then schedule a time for Pulp to perform the add and publish actions. If anything goes wrong during the upload/scheduling process, publishers can resolve them earlier without delaying their release schedule. But once that is complete, Pulp will guarantee that their packages are distributed publicly on time without additional issues.
Describe alternatives you've considered
Our alternative here is to use a separate container that publishers can use to schedule future releases. The container would have a db and regularly check if it needs to add/publish packages in Pulp. If there is a scheduled task, the container calls Pulp to add the packages to the repo and publish them.
Additional context
Could be related to #6104, but wanted to hear some thoughts on this before proceeding.
The text was updated successfully, but these errors were encountered: