I’ve tried to follow the discussions on this here and elsewhere, but it all
goes down a rat’s nest and I end up pretty much as confused and ignorant as
I started out.
MSFT is littered with warnings like this: “*Important The dashboard
submission REST APIs will no longer be available for use as of the end of
October 2016. APIs for driver submissions are under consideration for a
future release.*”
or this:
*Important The dashboard submission REST APIs will no longer be available
for use as of the end of November 10th, 2016. APIs for driver submissions
are under consideration for a future release.*
Given that even the dates don’t agree, confidence in above being accurate:
0.
So am I wasting my time even trying to automate submissions for a) WHQL or
b) attestation signing? Does anyone have this working?
Mark Roddy
We’re currently trying to get the tests themselves automated and integrated into our continuous integration builds. Once we get that working we were hoping you’d have the automated submissions figured out 
This process is all a bit ‘Mickey Mouse’ (with all due respect to Mickey). With the recent additions of containers to Server, it’d be really slick if Microsoft could cook up a container that has this process a little more boilerplate. I’d love for my build machine to kick off a build when a new change is committed to a branch, compile, unit test, functional test, HLK test, create a submission, retrieve the submission, build it into my installer, and sign the thing.
That’s REALLY a lot more work than it should be at this point in time.
I don’t intend to hijack your original concern though. I have had ZERO luck with their automated submissions. I wish I could offer more help.
That (a pre-cooked container) would be just the right thing. Everyone
everywhere stabbing at this mess in the dark with a dull and rusty blade is
just not a great way to get to repeatable secure processes.
Mark Roddy
On Mon, Dec 19, 2016 at 3:07 PM, wrote:
> We’re currently trying to get the tests themselves automated and
> integrated into our continuous integration builds. Once we get that
> working we were hoping you’d have the automated submissions figured out
>
> This process is all a bit ‘Mickey Mouse’ (with all due respect to
> Mickey). With the recent additions of containers to Server, it’d be really
> slick if Microsoft could cook up a container that has this process a little
> more boilerplate. I’d love for my build machine to kick off a build when a
> new change is committed to a branch, compile, unit test, functional test,
> HLK test, create a submission, retrieve the submission, build it into my
> installer, and sign the thing.
>
> That’s REALLY a lot more work than it should be at this point in time.
>
> I don’t intend to hijack your original concern though. I have had ZERO
> luck with their automated submissions. I wish I could offer more help.
>
> —
> NTDEV is sponsored by OSR
>
> Visit the list online at: http:> showlists.cfm?list=ntdev>
>
> MONTHLY seminars on crash dump analysis, WDF, Windows internals and
> software drivers!
> Details at http:
>
> To unsubscribe, visit the List Server section of OSR Online at <
> http://www.osronline.com/page.cfm?name=ListServer>
></http:></http:>