The process of setting up HLK devices, running the tests, collecting the results, packaging for all variants, submitting the package, retrieving the signed package, and integrating the package into your installation/redistributable software is anything but concisely documented. Many of the individual steps have various levels of documentation, but for the most part we all have the same workflow needs (ex: make a change and get it to our customer). I've got all the steps between code change and making an installer automated (with the exception of the HLK signing process).
Are people actually automating that process successfully? If so, are you able to integrate it into the rest of your CI process? I'd be really curious how folks are pulling this off. What does the device topology look like (ex: build machine(s), HLK server/client(s), how do they interact, etc. I find doing basic things like creating a proper .cab file for submission a PITA every time I need to make a new one. I'd love to replace the entire manual process with an automated process that has a single configuration file to account for anything unique to my driver.
It looks like you're new here. If you want to get involved, click one of these buttons!
|Upcoming OSR Seminars||Kernel Debugging||30 Mar 2020||OSR Seminar Space|
|Developing Minifilters||20 Apr 2020||OSR Seminar Space & ONLINE|
|Writing WDF Drivers||11 May 2020||OSR Seminar Space & ONLINE|
|Internals & Software Drivers||28 Sept 2020||Dulles, VA|