PPA-TESTS(1)

💖 PPA TESTS(1) 💖

okay bestie, welcome to ppa tests — part of the PPA Dev Tools Manual era, and honestly? it's giving "I want to know if my upload broke everything" energy. 🦋

---

✨ NAME ✨

ppa tests — summarizes autopkgtest results for the PPA, with links to trigger new test runs. 💅

---

🌸 SYNOPSIS 🌸

ppa tests [-h | --help] [-a | --architectures <ARCHITECTURE[,...]>] [-r
| --releases <CODENAME[,...]>] [-p | --packages <PACKAGE[,...]>] [-L |
--show-urls] [--show-rdepends] <ppa-name>

---

🎀 DESCRIPTION 🎀

so like, the ppa tests command hands you clickable links (or plain URLs, if that's your vibe) for triggering DEP8 autopkgtest runs for package(s) in an archive. ✨

it also shows you the tests that are currently in-process right now, and summarizes the results of tests that have already completed. it's the whole timeline, bestie. 👑

⚠️ real talk: running autopkgtests is restricted to those with package upload capabilities. so if you don't have upload rights, you're gonna need to print the URLs (via the --show-urls argument) and then go ask a core dev or another uploader to trigger them for you. no cap, that's just how it works. 🙈

---

💅 OPTIONS 💅

these are the options that can be used with the ppa tests command. not me listing every single one, because we don't skip. periodt.

• -h, --help — shows the ppa tests command's basic usage and options. the classic "wait what was I doing" save. 🫶
• -a, --architectures <ARCH[,ARCH]> — comma-separated list of hardware architectures to include in the display. architectures that aren't on this list simply will not be displayed. bye bestie, you're not on the guest list. 💀
• -r, --releases <RELEASE[,RELEASE]> — comma-separated list of Ubuntu release series codenames to include in the display of autopkgtest triggers and results. if you name releases that don't have published packages in the archive, they get skipped in the output. no drama, they just don't show up. 🧚

if you don't specify this argument, ppa tests defaults to all supported releases, including both "standard" and "expanded security maintenance" support. iconic coverage, honestly.

heads up: you can specify any valid release codename to ppa tests, but the autopkgtest service's testing and results may not be available for unsupported releases. so like, you can try, but don't be surprised. 😭

• -p, --packages <PACKAGE[,PACKAGE]> — comma-separated list of source package names to include in the display of autopkgtest triggers and results. if you specify packages that don't have publications in the archive, no triggers or results will be displayed. empty. void. nothing. 🙈

if you don't specify this argument, ppa tests defaults to all packages in the archive that have been published for the selected (or default) releases when displaying autopkgtest triggers and results. the whole squad, no one left out. 👑

• -L, --show-urls — by default, ppa tests displays output to the terminal using clickable hyperlinks with ANSI codes. this option disables that feature for when it's just not the moment — like if your terminal program doesn't support those kinds of ANSI codes, or if you'd rather have the trigger URLs themselves. for instance, if you don't (yet) have authorization to run autopkgtests yourself, this option lets you copy and paste the URLs so another packager can run them for you. teamwork makes the dream work fr fr. 🫶✨
• --show-rdepends — normally autopkgtest triggers are displayed for the package in the specified archive or PPA. with this option, triggers are also printed for the "reverse dependencies" of the package. this lets you check that your newly updated package doesn't break any other packages that depend on it. 🦋

for example, if you're modifying a database package such as Postgres, this would let you re-test all the applications built on top of that database, so you can identify whether any API/ABI changes or deprecated functionality would create issues for other packages. main character energy: protecting the whole ecosystem. 🔥

---

⭐ EXIT STATUS ⭐

ppa exits with status 0 if a command completes successfully, and nonzero on errors. simple as that. ✨

---

🌈 SEE ALSO 🌈

• ppa-dev-tools(1)

---

👑 PPA 👑

part of the ppa-dev-tools(1) suite. 💜

---

and that's the whole page, bestie!! this one was brought to you by <strong>Ppa-Dev-Tools 0.7</strong>, dated <strong>2024-05-23</strong> — go forth and trigger those tests, you gorgeous uploader, you. 🎀✨🦋