Setup PR-CI runner without access to shared team resources - for private runner

[pvoborni]

Currently, PR-CI runners use FedoraPeopleUpload subtask for artifact uploads.

Setup for this task is hardcoded in constants.py as:

FEDORAPEOPLE_KEY_PATH = '/root/.ssh/freeipa_pr_ci'
FEDORAPEOPLE_DIR = 'ipa-maint@fedorapeople.org:/srv/groups/freeipa/prci/{path}'
FEDORAPEOPLE_BASE_URL = 'https://fedorapeople.org/groups/freeipa/prci/'
FEDORAPEOPLE_JOBS_URL = urllib.parse.urljoin(FEDORAPEOPLE_BASE_URL, 'jobs/')

Making this part configurable will allow people without access to FreeIPA team's official freeipa_pr_ci private key use PR-CI for their private runners.

Thinking of it. If we change FedoraPeopleUpload class into, e.g., RsyncUpload and define what the remote location should support we might then configure the CI against any server.

[dhnunes]

Hy @pvoborni ,

I think this Issue is not more applicable due to implementation of AWS right?

Using S3, everything that the developer will need is to configure the S3 and DynamoDB properly to process the PR's and upload the artifacts.

[pvoborni]

Private S3 solves that but creates a different problem - a need for S3 and bit of knowledge of its configuration. I would not completely dismiss the idea of own rsync server but I'm fine with closing the issue - doesn't seem worth to spend time on it right now.

[pvoborni]

rsync upload existed in the project before S3 introduction. It was removed in 2693519