From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] ci: Add spinx related job
Date: Mon, 6 May 2024 23:27:34 +0200 [thread overview]
Message-ID: <20240506212734.71279-1-pvorel@suse.cz> (raw)
Because by default we don't build doc at all.
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
Hi,
Tested: https://github.com/pevik/ltp/actions/runs/8976016156
NOTE: it'd be nice to add make install target
(I'm not sure how to get prefix, hopefully including
include/mk/config.mk could be enough).
Also, I'd rename (in a separate commit) .github/workflows/ci.yml
to .github/workflows/ci-docker-build.yml to make it more obvious.
Kind regards,
Petr
.github/workflows/ci-sphinx-doc.yml | 35 +++++++++++++++++++++++++++++
1 file changed, 35 insertions(+)
create mode 100644 .github/workflows/ci-sphinx-doc.yml
diff --git a/.github/workflows/ci-sphinx-doc.yml b/.github/workflows/ci-sphinx-doc.yml
new file mode 100644
index 000000000..4bde5cbc8
--- /dev/null
+++ b/.github/workflows/ci-sphinx-doc.yml
@@ -0,0 +1,35 @@
+# SPDX-License-Identifier: GPL-2.0-or-later
+# Copyright (c) 2024 Petr Vorel <pvorel@suse.cz>
+
+name: "Test building sphinx doc"
+
+on: [push, pull_request]
+
+permissions: {}
+
+jobs:
+ sphinx:
+ runs-on: ubuntu-latest
+ steps:
+ - name: Checkout LTP
+ uses: actions/checkout@v2
+ with:
+ path: ltp
+
+ - name: Install spinx
+ run: |
+ sudo apt update
+ sudo apt install python3-sphinx python3-virtualenv
+
+ - name: Install spinx dependencies
+ run: |
+ cd "$GITHUB_WORKSPACE/ltp/doc/"
+ python3 -m virtualenv .venv
+ . .venv/bin/activate
+ pip install -r requirements.txt
+
+ - name: Build doc
+ run: |
+ cd "$GITHUB_WORKSPACE/ltp/doc/"
+ . .venv/bin/activate
+ make
--
2.43.0
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next reply other threads:[~2024-05-06 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 21:27 Petr Vorel [this message]
2024-05-07 15:07 ` [LTP] [PATCH 1/1] ci: Add spinx related job Petr Vorel
2024-05-07 15:21 ` Cyril Hrubis
2024-05-07 16:47 ` Petr Vorel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240506212734.71279-1-pvorel@suse.cz \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).