Install Bikeshed on CI #42
Conversation
This helps us move away from depending on the CSSWG API server, which is often broken.
|
As mentioned on Chat I'm concerned about the wastefulness of this approach. In that we'd end up downloading and installing Bikeshed for each build. As opposed to now where we do a fetch to a service with our input document and use the output document. @tantek @npdoty reportedly the W3C does this in its tooling. Might be something for the Sustainability CG to look into? |
|
Reiterating some private discussions: I don't think the waste is significant here. We're talking ~5 seconds of electricity on both client and server, both of which are probably ~500 watts, so 1K watt-seconds = $0.00018054. That's about 0.568 grams of CO2, whereas sending an email is estimated to take 4 grams of CO2. Even if my calculations were several orders of magnitude off, I think the human time invested in dealing with these failures is more valuable than even a whole dollar of elecricity/CO2. If you're worried you can eat one less burger (~2.5 kg CO2). |
| @@ -17,6 +17,7 @@ jobs: | |||
| - uses: actions/setup-python@v4 | |||
| with: | |||
| python-version: "3.11"@@build_with_node@@ | |||
There was a problem hiding this comment.
Do we want to bump this to .12 at the same time?
There was a problem hiding this comment.
I'm scared since Bikeshed is only tested up to 3.11 (per https://speced.github.io/bikeshed/#install-py3 and their GitHub CI file) and I've previously gotten bitten by backward incompatibilities between 3.11 and 3.12 on the web platform tests project.
|
And would you mind adding the workflow_dispatch thingie? I can do a deploy across all standards I suppose on Monday. Just before we do the RDs. |
This helps us move away from depending on the CSSWG API server, which is often broken.