Skip to content

Latest commit

 

History

History
90 lines (64 loc) · 3.05 KB

README.md

File metadata and controls

90 lines (64 loc) · 3.05 KB
Raw

Copr Nightly Trigger

Copr build status

Systemd units to trigger nightly builds of one or more Copr projects.

Installation

This package is available from the chrisbouchard/upliftinglemma Copr. Assuming you're using a recent version of Fedora or CentOS, you can install using dnf.

$ dnf copr enable chrisbouchard/upliftinglemma
$ dnf install copr-nightly-trigger

Configuration

The [email protected] service template lets you configure multiple build triggers from the same server. So if we're building a package foo, we may instantiate the service as [email protected]. The name is purely for organization; it's not used by the build.

This service is configured using standard systemd configuration techniques. There are two properties and a credential that must be supplied. So, for the service mentioned above, we'd create the directory /etc/systemd/system/[email protected] and create a configuration file, e.g., 00-copr.conf (the name does not matter).

/etc/systemd/system/[email protected]/00-copr.conf
[service]
Environment=PROJECT=awesomeproject
Environment=PACKAGE=foo
LoadCredential=copr:/etc/copr-nightly/your-copr-credentials.conf
/etc/copr-nightly/your-copr-credentials.conf
[copr-cli]
login = ...
username = yourusername
token = ...
copr_url = https://copr.fedorainfracloud.org
# expiration date: 2021-04-01

(The /etc/copr-nightly directory is reserved for Copr credentials files, and is owned by root with 0600 permissions to keep out prying eyes, but the path can technically be anywhere.)

Copr credentials are obtained from Copr API after logging in. The same credentials file can be used by multiple services, as it only identifies your user. Note credentials expire after a few months, so make sure to keep them up-to-date.

You can test that the service is configured correctly by starting it manually:

$ systemctl start [email protected]

Running Nightly

As the name implies, the goal is to trigger a build every night around midnight. The [email protected] timer template will trigger the corresponding service at that time. Once the service is configured, you must enable the timer. For our foo example, we'd enable the timer as follows:

$ systemctl enable --now [email protected]

Future Work

  • It would be nice if we didn't have to keep the credentials files up-to-date manualy, given that they expire every 180 days. There may be a way to do this using the Copr CLI, but I haven't learned it yet.