Hi Med, Another example could be my repo on YANG Push Lite:
https://github.com/rgwilton/draft-yp-observability/ I have used Martin’s repo as a template, but I have a separate build file (https://github.com/rgwilton/draft-yp-observability/blob/main/build.mill) (using Mill rather than Make) to handle the YANG aspects, but still use Make for the underlying conversion from Markdown to draft + HTML. The readme file associated with the repo https://github.com/rgwilton/draft-yp-observability/blob/main/README.md gives some instructions. It is still somewhat a work in progress, but currently will (at least on Mac OS): * Download RFCs & drafts revisions, download/install python venv & pyang, extract YANG files, fixed some mistakes, compiler and validates sets of modules together (using pyang, and also YANG lint, if installed on the path), builds various YANG trees and generates snippets from them. * The generated assets can then be referenced into a markdown file. * If you ask mill to watch local files (“./mill --watch all”), then it can automatically recompile locally if you change the build file, or any of the local YANG files, or the markdown source file, so you can keep a copy of the generated html open next to you and it will auto update YANG files, draft text, and tree diagrams whenever you save. It also has a command that you can run to check if there are newer versions of any referenced drafts, e.g.: rwilton@RWILTON-M-4RJ2 draft-yp-observability % ./mill checkDraftLatest [1/1] checkDraftLatest [1] Warning: draft-ietf-netconf-yang-notifications-versioning latest revsion is 8, using 7 [1] Warning: draft-ietf-netconf-yang-library-augmentedby latest revsion is 3, using 2 [1/1] ============================== checkDraftLatest ============================== 8s The actual underlying build rules are currently in the repo here: https://github.com/rgwilton/draft-yp-observability/blob/main/util_ietf.mill But when I get the time, my plan to package the build rules as a versioned Jar file on Maven, which can then be trivially imported by the draft specific build file. I haven’t spent any time to hook this into github actions – but that is something else that I would probably also do. Kind regards, Rob From: Florian Kauer <florian.ka...@linutronix.de> Date: Tuesday, 15 April 2025 at 03:54 To: mohamed.boucad...@orange.com <mohamed.boucad...@orange.com>, netmod@ietf.org <netmod@ietf.org> Cc: Italo Busi <italo.b...@huawei.com> Subject: [netmod] Re: Call for volunteers for CI/CD YANG Integration in martinthomson/internet-draft-template Hi all, On 4/11/25 15:37, mohamed.boucad...@orange.com wrote: > If you are interested to help with this, please drop us an email. A first > meeting is schedule April 28. I would also be interested in this discussion. We are currently approaching the CI/CD YANG topic in the following way https://github.com/Linutronix/yang-validation It was used to work on draft-ietf-netmod-intf-ext-yang-16 and IEEE 802.1Qcw Greetings, Florian _______________________________________________ netmod mailing list -- netmod@ietf.org To unsubscribe send an email to netmod-le...@ietf.org
_______________________________________________ netmod mailing list -- netmod@ietf.org To unsubscribe send an email to netmod-le...@ietf.org
