From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: IGT development <igt-dev@lists.freedesktop.org>
Cc: Daniel Vetter <daniel.vetter@intel.com>
Subject: [igt-dev] [PATCH i-g-t 3/4] gitlab-ci: Build docs by default
Date: Mon, 29 Oct 2018 09:10:29 +0100 [thread overview]
Message-ID: <20181029081030.4041-3-daniel.vetter@ffwll.ch> (raw)
In-Reply-To: <20181029081030.4041-1-daniel.vetter@ffwll.ch>
I just realized that when you push to a non-HEAD branch, then gitlab
doesn't bother to build the deploy stage. Which means if you push to a
branch, then that's not properly tested.
So build docs right away. We're not going to waste anything, since the
deploy:pages job will pick up right from where we left.
Signed-off-by: Daniel Vetter <daniel.vetter@intel.com>
---
.gitlab-ci.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 12601cb7f200..2e04c0e84e1b 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -24,6 +24,7 @@ build:tests-fedora:
script:
- meson $MESON_OPTIONS build
- ninja -C build
+ - ninja -C build igt-gpu-tools-doc
artifacts:
paths:
- build
--
2.19.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-10-29 8:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 8:10 [igt-dev] [PATCH i-g-t 1/4] lib: Make libunwind optional again Daniel Vetter
2018-10-29 8:10 ` [igt-dev] [PATCH i-g-t 2/4] gitlab-ci: build test libunwind stubs Daniel Vetter
2018-10-29 8:10 ` Daniel Vetter [this message]
2018-10-29 8:10 ` [igt-dev] [PATCH i-g-t 4/4] gitlab-ci: arm64 cross compiling Daniel Vetter
2018-10-29 8:39 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/4] lib: Make libunwind optional again Patchwork
2018-10-29 9:33 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-10-29 10:20 ` [igt-dev] [PATCH i-g-t 1/4] " Petri Latvala
2018-10-29 15:35 ` Daniel Vetter
2018-10-29 15:41 ` Eric Anholt
2018-10-29 15:55 ` [igt-dev] [PATCH i-g-t] " Daniel Vetter
2018-10-29 17:15 ` Daniel Vetter
2018-10-29 17:20 ` Daniel Vetter
2018-10-29 18:37 ` Sean Paul
2018-10-29 19:06 ` Daniel Vetter
2018-10-30 10:28 ` Petri Latvala
2018-10-30 2:24 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t] lib: Make libunwind optional again (rev5) Patchwork
2018-10-30 12:54 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2018-10-30 17:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2018-10-30 12:22 [igt-dev] [PATCH i-g-t 1/4] lib: Make libunwind optional again Daniel Vetter
2018-10-30 12:22 ` [igt-dev] [PATCH i-g-t 3/4] gitlab-ci: Build docs by default Daniel Vetter
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=20181029081030.4041-3-daniel.vetter@ffwll.ch \
--to=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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