From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"yocto@lists.yoctoproject.org" <yocto@lists.yoctoproject.org>
Cc: YP docs mailing list <docs@lists.yoctoproject.org>
Subject: Re: [docs] No more nightly builds?
Date: Tue, 11 Jan 2022 12:12:17 +0100 [thread overview]
Message-ID: <0694d983-509f-61ea-ddaf-e97835ecf678@bootlin.com> (raw)
In-Reply-To: <3b82d9590897c50ad54ff22137cb7163b26267ce.camel@linuxfoundation.org>
On 1/11/22 12:09 PM, Richard Purdie wrote:
> On Tue, 2022-01-11 at 12:01 +0100, Michael Opdenacker wrote:
>> Hi Richard,
>>
>> On 1/11/22 11:41 AM, Richard Purdie wrote:
>>> On Tue, 2022-01-11 at 10:47 +0100, Michael Opdenacker wrote:
>>>> Greetings,
>>>>
>>>> Do we still have nightly builds? I cannot find them anywhere, but the
>>>> documentation still refer to a broken location
>>>> (https://autobuilder.yocto.io/pub/nightly/).
>>> We do run them but they're "a-quick" six nights a week with an "a-full" on a
>>> weekend. The results of all non-release builds go here:
>>>
>>> https://autobuilder.yocto.io/pub/non-release/
>>>
>>> The "nightly" builds don't produce shared artefacts any more, just test result
>>> files and reports.
>>
>> Right. So the documentation can stop referring to them as a way to get
>> the latest code.
> I think it should be replaced with something about "latest test results"?
Maybe, but then in the test manual, because the section referring to
nightly builds about getting Yocto Project code
(https://docs.yoctoproject.org/dev-manual/start.html#locating-yocto-project-source-files).
Thanks
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2022-01-11 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 9:47 No more nightly builds? Michael Opdenacker
2022-01-11 10:41 ` [docs] " Richard Purdie
2022-01-11 11:01 ` Michael Opdenacker
2022-01-11 11:09 ` Richard Purdie
2022-01-11 11:12 ` Michael Opdenacker [this message]
2022-01-11 11:16 ` Richard Purdie
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=0694d983-509f-61ea-ddaf-e97835ecf678@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=yocto@lists.yoctoproject.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