Description of problem: Currently the only way of updating a server's task with tasks from b.p.o is to clone the task repo from upstream, and then add the tasks by hand from there. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Running 'beaker-sync-tasks' with no args should default to syncing any common tasks from upstream to the local server. Additional info:
Also relevant is bug 1028280 (which proposes to support syncing from a local directory of tasks). That's a bit simpler, since the task already copies the remote RPMs down to a local directory, and bug 1012783 points out that for correctness, the tasks should be downloaded to a separate directory and then added from there. If this variant used an explicit "--upstream" option, then that would give three ways to do it: beaker-sync-tasks --dir <path to staging area> beaker-sync-tasks --upstream beaker-sync-tasks --remote <Beaker server URL> The virtual-fedora quick start currently has the following approach, but I didn't copy it to the main admin guide since the task-add invocation may be different for a real system: ======================================= We will now add a few task RPMs to ensure we can run jobs (including those with guest recipes) as well as inventory systems and reserve them through the scheduler. Use wget (or an equivalent command) to retrieve the latest versions of the standard task RPMs (this is best done on the host system rather than the Beaker server VM): $ wget -r -np -nc https://beaker-project.org/tasks/ Add the tasks manually via http://beaker-server-lc.beaker/bkr/tasks/new or by using the bkr-task-add(1) command (in the directory where the scripts were downloaded, using the admin account configured when first installing Beaker): $ for f in `ls *.rpm` > do > bkr task-add --hub=http://beaker-server-lc.beaker/bkr \ > --username=<USER> --password=<PASSWORD> $f > done =======================================