Setup echidna for continuous deployment

[tobie]

Not sure whether this needs WG approval.

/cc @anssiko @fhirsch

[marcoscaceres]

Yes, but I think I got blanket approval a while back... you will need to find the approval in the DAP archives. If you search for emails from me, it might be easy to find as it's probably the last thing I posted to DAP. 

On January 19, 2016 at 10:19:42 AM, Tobie Langel ([email protected]) wrote:

Not sure whether this needs WG approval.

/cc @anssiko @fhirsch

---

Reply to this email directly or view it on GitHub: https://github.com/w3c/sensors/issues/74

[tobie]

Seems there's approval in the October 2015 minutes.

[tobie]

@dontcallmedom can you help with this? Or point me to the right direction?

Thanks!

[dontcallmedom]

pull request forthcoming :)

[tobie]

:dancer:

[dontcallmedom]

So, given that this spec is using bikeshed, setting up echidna will be a bit more convoluted than I thought, since we need to provide echidna with a ready-to-publish version of the document (whereas the file served in the repo is formatted to be an editor draft).

I think getting bikeshed and echidna to work together is a work in progress; it was waiting for w3c/echidna#243 to land, which it did last week; hopefully, we'll be able to set it soon, but in the meantime, I need to reopen the issue.

[dontcallmedom]

@tobie I can't run the bikeshed source through the on-line processor. Am I missing something?

Even running it via curl generates errors and warnings, e.g.

curl https://api.csswg.org/bikeshed/ -F url=http://w3c.github.io/sensors/index.bs -F paragraph=md -F output=html -F md-status=WD -F md-Level=1 > Overview.html

(and that's using a "Level=1" metadata which I'm not sure we want to adopt)

[tobie]

See https://github.com/tabatkins/bikeshed/pull/264.

You'll also need to use a GH auth token to get the issue list with the --gh-token option.

[dontcallmedom]

@tobie could you document the command line you use to generate the HTML from the .bs file? that would probably save me time from figuring bikeshed out

[tobie]

I was precisely thinking that I should have written it down somewhere. :-/

[tobie]

Or more precisely, regretting I hadn't.

[tobie]

So the current version of bikeshed is somewhat broken for our purpose, see: https://github.com/tabatkins/bikeshed/pull/571

[tobie]

Here's the command line I use:

$ bikeshed -f spec --gh-token=[INSERT_TOKEN_HERE]

You'll have to define the GH TOKEN in Travis' repository settings.

[dontcallmedom]

so, from what I understand, bikeshed should inherit "soon" from a "publish" command that would enable direct publication on echidna.

Meanwhile, the currently available option to use echdina+travis+bikeshed aren't really practical from my perspective (they require entrusting a W3C account password to Travis), so I think the best we can do is to wait until bikeshed adds this publish command.

[dontcallmedom]

(needless to say that in the meantime, I'm happy to either do the manual publications or give you the relevant tokens to do so yourself)