public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Michael D Kinney" <michael.d.kinney@intel.com>
To: Rebecca Cran <rebecca@bsdio.com>,
	edk2-devel-groups-io <devel@edk2.groups.io>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Cc: Sean Brogan <sean.brogan@microsoft.com>,
	Michael Kubacki <michael.kubacki@microsoft.com>,
	Bret Barkelew <Bret.Barkelew@microsoft.com>
Subject: Re: Plans to generate Doxygen docs as part of Azure CI-style builds?
Date: Tue, 28 Apr 2020 00:50:34 +0000	[thread overview]
Message-ID: <MN2PR11MB446105CA824D522150BFE13CD2AC0@MN2PR11MB4461.namprd11.prod.outlook.com> (raw)
In-Reply-To: <b959a17a-ed8d-15d1-29e5-510e1a534720@bsdio.com>

Rebecca,

Those are both good ideas.  Have not had time to enable them yet.

Doxygen generated documentation into HTML on a site is possible.
There are some issues with the current CLI tool that does 
this where it generates random filename each build.  There is a
Doxygen config option to disable this behavior, so site updates
will not generate all new files every build.

We have considered generating binaries for OVMF and UEFI Shell
and posting them in the GitHub release page for a stable tag.
We could use a CI agent to do these release builds.

Mike

> -----Original Message-----
> From: Rebecca Cran <rebecca@bsdio.com>
> Sent: Monday, April 27, 2020 5:39 PM
> To: edk2-devel-groups-io <devel@edk2.groups.io>
> Cc: Sean Brogan <sean.brogan@microsoft.com>; Michael
> Kubacki <michael.kubacki@microsoft.com>; Bret Barkelew
> <Bret.Barkelew@microsoft.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>
> Subject: Plans to generate Doxygen docs as part of
> Azure CI-style builds?
> 
> I was wondering if there are any near-term plans to
> start generating and
> publishing EDK2 Doxygen documentation as part of an
> Azure build -
> perhaps on a nightly or weekly basis?
> 
> If not, then I'll work on getting my copy of the docs
> available again
> since I've found them useful in the past.
> 
> 
> Also, are there any plans to start publishing regular
> builds of OVMF and
> other platforms? I know there's the kraxel site that
> has OVMF builds,
> but if there aren't plans to do something similar then
> I might set
> something up myself.
> 
> 
> --
> Rebecca Cran
> 


  reply	other threads:[~2020-04-28  0:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  0:38 Plans to generate Doxygen docs as part of Azure CI-style builds? Rebecca Cran
2020-04-28  0:50 ` Michael D Kinney [this message]
2020-04-28  3:54   ` [edk2-devel] " Rebecca Cran

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-list 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=MN2PR11MB446105CA824D522150BFE13CD2AC0@MN2PR11MB4461.namprd11.prod.outlook.com \
    --to=devel@edk2.groups.io \
    /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