p4lang
CI: Create a CI job that builds the spec PDF and HTML for a PR
... I think this would be very useful and it would make it easier to check small changes (where one can be quite certain to not break anything, but still wants to make sure) without having to bring up build locally.
The question is, should we do it soon (for Madoko) and then update it for AsciiDoc, or wait until we have migrated to AsciiDoc (#1298).
I'd probably propose waiting until AsciiDoc migration since it appears to be impending, but let's discuss in meeting.
I know that P4Runtime already has something like this, though I don't know anything about how it works. Just that I can go to https://s3-us-west-2.amazonaws.com/p4runtime/ci/main/P4Runtime-Spec.html (and replace main with any other branch) and it will render the specification.
Um, we have this?
See for example here: https://p4.org/p4-spec/docs/p4-16-working-draft.html and look at the HTML source.
Hi everyone, I’ve prepared a draft version based on the approach used in the P4Runtime repo. Currently, I still need to resolve issues with creating the Docker container for the AsciiDoc environment.
There is a job that does this now here.
However, I need to update it to execute on pull requests in addition to branch push, as the usual mode of operation for PRs in this repo is likely to be a fork and pull rather than a branch and pull.
Briefly discussed in Feb 3 LDWG: Waiting to hear back from Ryan when he's back.
Briefly discussed in Feb 3 LDWG: Waiting to hear back from Ryan when he's back.
An initial discussion/proposal of a possible alignment between the P4 LDWG and the P4 Runtime 'CI workflow for spec publication' began in the last comments of this PR: https://github.com/p4lang/p4runtime/pull/539. The discussion will continue here: https://github.com/p4lang/p4runtime/issues/544."