Add build-docs job to main github actions file#8504
Conversation
jonkoops
left a comment
There was a problem hiding this comment.
This is a welcome change. Great work! I just have one small comment.
Co-authored-by: Jon Koops <jonkoops@gmail.com>
jonkoops
left a comment
There was a problem hiding this comment.
Sorry for the additional review comments, but looks like we can optimize things a bit.
|
@exequiel09 it's now failing with a surprising error about not being able to build some internal example for some reason... |
|
@exequiel09 looks like |
|
Maybe related to this. still reading docs: https://jekyllrb.com/docs/troubleshooting/#configuration-problems |
|
It's really hard debugging this pipeline issue 😅 |
|
Finally! It worked https://github.com/Leaflet/Leaflet/actions/runs/3165492356/jobs/5154569243 🎊 |
Falke-Design
left a comment
There was a problem hiding this comment.
The building works but it doesn't break when the error happens:
https://github.com/Falke-Design/Leaflet/actions/runs/3165535999/jobs/5154637242
| @@ -1,4 +1,4 @@ | |||
| exclude: [build, debug, node_modules, spec, src, CNAME, reference-tpl.html, CHANGELOG.md, README.md, LICENSE] | |||
| exclude: [build, debug, node_modules, spec, src, CNAME, reference-tpl.html, CHANGELOG.md, README.md, LICENSE, vendor/bundle, vendor/cache, vendor/gems, vendor/ruby] | |||
There was a problem hiding this comment.
Just thinking out loud here, perhaps it would be better to use an include rather than to list all the things that should be excluded?
jonkoops
left a comment
There was a problem hiding this comment.
Code changes look good to me, but I am interested why it doesn't fail the job as expected when an error is introduced as @Falke-Design mentioned.
Yeah, debugging stuff on Github Actions can be a bit of a hassle. I usually test on my own fork as well, less waiting on upstream capacity. |
|
oh. I didn't know that I can run GH actions on a fork 😲 |
Not sure on how to run on my own fork. Quick search landed me on the event |
https://stackoverflow.com/a/64785111 I think I need to do some digging further to bubble up the error |
|
Can we store the output on a file and check if it contains |
|
Found a repo: https://github.com/epstechtheatre/Jekyll-Tester |
Pushed commit to use the suggestion action 6edc829 |
|
Seems like the suggested action for jekyll doesn't work. This line was never emitted https://github.com/epstechtheatre/Jekyll-Tester/blob/5331113e1372cd3a625eaa7398e334fe21397507/src/index.ts#L91 in this fork run: https://github.com/exequiel09/Leaflet/actions/runs/3165731159/jobs/5154974801#step:5:141 |
|
Okay so it's not related to |
|
Okay I know the fix. Pushing another one. removing the suggested action as well |
… proper exit status
|
Added |
Falke-Design
left a comment
There was a problem hiding this comment.
I have no idea how the workflows are working but the output looks good now 😄
jonkoops
left a comment
There was a problem hiding this comment.
Workflow is looking good to me, got a couple small questions but after that I think we can merge.
| @@ -1,4 +1,4 @@ | |||
| exclude: [build, debug, node_modules, spec, src, CNAME, reference-tpl.html, CHANGELOG.md, README.md, LICENSE] | |||
| exclude: [build, debug, node_modules, spec, src, CNAME, reference-tpl.html, CHANGELOG.md, README.md, LICENSE, vendor/bundle, vendor/cache, vendor/gems, vendor/ruby] | |||
There was a problem hiding this comment.
Do we really need anything from the vendor directory? Perhaps we can exclude all of it?
| exclude: [build, debug, node_modules, spec, src, CNAME, reference-tpl.html, CHANGELOG.md, README.md, LICENSE, vendor/bundle, vendor/cache, vendor/gems, vendor/ruby] | |
| exclude: [build, debug, node_modules, spec, src, CNAME, reference-tpl.html, CHANGELOG.md, README.md, LICENSE, vendor] |
There was a problem hiding this comment.
I'm not sure on the proper solution but the jekyll website suggested that fix on CI issue #8504 (comment)
There maybe folders that jekyll team don't want to ignore hence they added a blacklist of it
There was a problem hiding this comment.
Mentioned in jekyll website:
The proper solution is to incorporate the default setting for exclude: rather than override it completely:
For versions up to v3.4.3, the exclude: setting must look like following:
exclude:
- Gemfile
- Gemfile.lock
- node_modules
- vendor/bundle/
- vendor/cache/
- vendor/gems/
- vendor/ruby/
- any_additional_item # any user-specific listing goes at the end
@Falke-Design we need the build to command to return non-zero exit status to make GitHub actions check fail. In that case jekyll build returns 1 when there are errors and 0 if there's none. |
|
Thank you so much for this contribution @exequiel09. This change helps us out a lot! |


Closes #8502