Bug 1028280

Summary:	[RFE] beaker-sync-tasks should support syncing from a local directory
Product:	[Retired] Beaker	Reporter:	Nick Coghlan <ncoghlan>
Component:	command line	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	develop	CC:	cbouchar, qwan, tools-bugs
Target Milestone:	future_maint	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-05-10 19:20:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Nick Coghlan 2013-11-08 05:28:51 UTC

Setting up a new Beaker instance includes a step to install the standard tasks from https://beaker-project.org/tasks/

This is an annoyingly manual process, and one that needs to be repeated if updated versions of these tasks are published.

I'm updating the quick start guide to suggest grabbing them all via wget:

    wget -r -np -nc https://beaker-project.org/tasks/

It would be good if they could be downloaded to the server itself and then bulk updated via:

    beaker-sync-tasks --dir <download_dir>/beaker-project.org/tasks/

Comment 1 Nick Coghlan 2013-11-08 05:34:28 UTC

In the meantime, this is also a fairly trivial bash command (run in the directory where the tasks were downloaded):

    for f in `ls *.rpm`; do bkr task-add $f; done

Comment 2 Roman Joost 2016-09-20 00:33:24 UTC

Small update: I looked into this today with the hope I could include it with my changes to Beaker-in-a-box. Turns out this item is a bit bigger than I anticipated. Dan mentioned that the current code has a few defects which need to be fixed first, before we can add the desired functionality.

Comment 3 Carol Bouchard 2021-05-10 19:20:51 UTC

Closing this as will not do, this feature is not impacting the RHEL 9 support that we are focusing on in the final LTS 28 version. 

If you think that this does have an impact on RHEL 9 support. Please give the business justification and reopen. 

 

If you have any question please contact Theo tapazogl.