Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP. Add a dynamically generated list of mailing list of all SIGs #2083

Closed
wants to merge 1 commit into from

Conversation

@sp1r
Copy link

commented Feb 4, 2019

Cannot think of ideal solution.

Original page is written in adoc and dynamic generation require haml. But html generated from haml lacks some nice and useful features like:

  • anchors for sections
  • note/warning blocks
    (And after all reading adoc is much more easy and pleasant)

For now I've ended with separate page (automatically generated): gh-pages
And added a link to it from "mailing lists" page: gh-pages

Can someone help with this? How to do it better way?

ISSUE: WEBSITE-588

Vyacheslav S. Spiridonov
Add a dynamically generated list of mailing list of all SIGs
WIP. Cannot think of ideal solution.
Dynamic generation require haml. But html generated from haml lacks some
pretty and useful features:
- anchors for sections
- note/warning blocks

And nonetheless reading adoc is much more easy and pleasant.

For now I've ended with separate page (automatically generated).
And added a link to it from "mailing lists" page.

ISSUE: WEBSITE-588

@batmat batmat requested a review from oleg-nenashev Feb 4, 2019

@oleg-nenashev

This comment has been minimized.

Copy link
Contributor

commented Feb 7, 2019

I would rather propose converting the entire content/mailing-lists.adoc page to HAML. Later we may want to do the same for local groups, so it might be easier to code the page

We did it for several pages with automatic content generation, e.g. https://github.com/jenkins-infra/jenkins.io/blob/master/content/projects/gsoc/2019/project-ideas.html.haml

@sp1r

This comment has been minimized.

Copy link
Author

commented Feb 8, 2019

OK, I'll try to pick up as much from adoc as I can.

@oleg-nenashev oleg-nenashev referenced this pull request Feb 19, 2019
@jenkinsadmin

This comment has been minimized.

Copy link

commented Apr 8, 2019

Build failed; the context from the latest run is:

Expand to view
./scripts/groovy pull
jre-alpine: Pulling from library/groovy
Digest: sha256:2164b5535f4dec72c123b5667df9275d9d73250a7859a8edd0a94a8a1cbc40cf
Status: Image is up to date for groovy:jre-alpine
./scripts/groovy scripts/release.rss.groovy 'https://updates.jenkins.io/release-history.json' > build/_site/releases.rss
./scripts/ruby bundle exec ./scripts/fetch-external-resources
Fetching external resources:
bundler: failed to load command: ./scripts/fetch-external-resources (./scripts/fetch-external-resources)
Faraday::ConnectionFailed: execution expired
  /usr/local/lib/ruby/2.6.0/net/http.rb:947:in `initialize'
  /usr/local/lib/ruby/2.6.0/net/http.rb:947:in `open'
  /usr/local/lib/ruby/2.6.0/net/http.rb:947:in `block in connect'
  /usr/local/lib/ruby/2.6.0/timeout.rb:103:in `timeout'
  /usr/local/lib/ruby/2.6.0/net/http.rb:945:in `connect'
  /usr/local/lib/ruby/2.6.0/net/http.rb:930:in `do_start'
  /usr/local/lib/ruby/2.6.0/net/http.rb:919:in `start'
  /usr/local/lib/ruby/2.6.0/net/http.rb:1470:in `request'
  /usr/local/lib/ruby/2.6.0/net/http.rb:1228:in `get'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday-0.9.2/lib/faraday/adapter/net_http.rb:80:in `perform_request'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday-0.9.2/lib/faraday/adapter/net_http.rb:40:in `block in call'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday-0.9.2/lib/faraday/adapter/net_http.rb:87:in `with_net_http_connection'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday-0.9.2/lib/faraday/adapter/net_http.rb:32:in `call'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday_middleware-0.9.2/lib/faraday_middleware/response/follow_redirects.rb:83:in `perform_with_redirection'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday_middleware-0.9.2/lib/faraday_middleware/response/follow_redirects.rb:69:in `call'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday-0.9.2/lib/faraday/rack_builder.rb:139:in `build_response'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday-0.9.2/lib/faraday/connection.rb:377:in `run_request'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/vendor/gems/ruby/2.6.0/gems/faraday-0.9.2/lib/faraday/connection.rb:140:in `get'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/scripts/fetch-external-resources:72:in `fetch_resource'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/scripts/fetch-external-resources:81:in `block in process'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/scripts/fetch-external-resources:80:in `each'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/scripts/fetch-external-resources:80:in `process'
  /mnt/agent-workspace/workspace/Infra_jenkins.io_PR-2083/scripts/fetch-external-resources:134:in `<top (required)>'
Makefile:49: recipe for target 'build/fetch' failed
make: *** [build/fetch] Error 1
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
Caught: hudson.AbortException: script returned exit code 2
[Pipeline] mail
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented May 8, 2019

Build failed; the context from the latest run is:

Expand to view
Merge succeeded, producing 1d81ee2a89ab122e857ae9d19abe5814799ac4ea
Checking out Revision 1d81ee2a89ab122e857ae9d19abe5814799ac4ea (PR-2083)
Commit message: "Merge commit 'c8d0710311ca6e32b38f501658c7af4f6e87b6f2' into HEAD"
First time build. Skipping changelog.
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build site)
[Pipeline] timeout
Timeout set to expire in 1 hr 0 min
[Pipeline] {
[Pipeline] sh
+ make all
mkdir -p build/_site
chmod u+x scripts/groovy scripts/ruby scripts/node scripts/asciidoctor-pdf scripts/awestruct scripts/user-site-deploy.sh scripts/release.rss.groovy scripts/fetch-external-resources
mkdir -p vendor/gems
./scripts/ruby pull
2.6: Pulling from library/ruby
c5e155d5a1d1: Pulling fs layer
221d80d00ae9: Pulling fs layer
4250b3117dca: Pulling fs layer
3b7ca19181b2: Pulling fs layer
425d7b2a5bcc: Pulling fs layer
9c5c6ef56f98: Pulling fs layer
c1215488e118: Pulling fs layer
a9e2c9b9152d: Pulling fs layer
425d7b2a5bcc: Waiting
9c5c6ef56f98: Waiting
c1215488e118: Waiting
a9e2c9b9152d: Waiting
3b7ca19181b2: Waiting
write /var/lib/docker/tmp/GetImageBlob763877354: no space left on device
Makefile:81: recipe for target 'build/ruby' failed
make: *** [build/ruby] Error 1
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // node
[Pipeline] echo
Caught: hudson.AbortException: script returned exit code 2
[Pipeline] mail
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented May 24, 2019

Build failed; the context from the latest run is:

Expand to view
[2019-05-24T13:20:01.498Z] mkdir -p content/_tmp
[2019-05-24T13:20:01.498Z] ./scripts/groovy pull
[2019-05-24T13:20:02.062Z] jre-alpine: Pulling from library/groovy
[2019-05-24T13:20:02.062Z] e7c96db7181b: Already exists
[2019-05-24T13:20:02.318Z] f910a506b6cb: Already exists
[2019-05-24T13:20:02.318Z] b6abafe80f63: Pulling fs layer
[2019-05-24T13:20:02.318Z] 3cc9816a0ac6: Pulling fs layer
[2019-05-24T13:20:02.318Z] e22d00a4d511: Pulling fs layer
[2019-05-24T13:20:02.318Z] e22d00a4d511: Verifying Checksum
[2019-05-24T13:20:02.318Z] e22d00a4d511: Download complete
[2019-05-24T13:20:02.575Z] 3cc9816a0ac6: Verifying Checksum
[2019-05-24T13:20:02.575Z] 3cc9816a0ac6: Download complete
[2019-05-24T13:20:02.832Z] b6abafe80f63: Verifying Checksum
[2019-05-24T13:20:02.832Z] b6abafe80f63: Download complete
[2019-05-24T13:20:05.354Z] b6abafe80f63: Pull complete
[2019-05-24T13:20:06.285Z] 3cc9816a0ac6: Pull complete
[2019-05-24T13:20:06.285Z] e22d00a4d511: Pull complete
[2019-05-24T13:20:06.285Z] Digest: sha256:8e48946c13029aebf1988d0f39507a69bc8264435d9c3b0e8258d6be333606fd
[2019-05-24T13:20:06.285Z] Status: Downloaded newer image for groovy:jre-alpine
[2019-05-24T13:20:06.285Z] ./scripts/groovy scripts/release.rss.groovy 'https://updates.jenkins.io/release-history.json' > build/_site/releases.rss
[2019-05-24T13:20:11.540Z] Caught: groovy.json.JsonException: Unable to process url: https://updates.jenkins.io/release-history.json
[2019-05-24T13:20:11.540Z] groovy.json.JsonException: Unable to process url: https://updates.jenkins.io/release-history.json
[2019-05-24T13:20:11.540Z] 	at release_rss.run(release.rss.groovy:18)
[2019-05-24T13:20:11.540Z] Caused by: javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[2019-05-24T13:20:11.540Z] 	... 1 more
[2019-05-24T13:20:11.540Z] Caused by: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: validity check failed
[2019-05-24T13:20:11.540Z] 	... 1 more
[2019-05-24T13:20:11.540Z] Caused by: java.security.cert.CertPathValidatorException: validity check failed
[2019-05-24T13:20:11.540Z] 	... 1 more
[2019-05-24T13:20:11.540Z] Caused by: java.security.cert.CertificateExpiredException: NotAfter: Tue May 21 11:33:35 GMT 2019
[2019-05-24T13:20:11.540Z] 	... 1 more
[2019-05-24T13:20:12.105Z] Makefile:49: recipe for target 'build/fetch' failed
[2019-05-24T13:20:12.105Z] make: *** [build/fetch] Error 1
[2019-05-24T13:20:12.139Z] [Pipeline] }
[2019-05-24T13:20:12.173Z] [Pipeline] // timeout
[2019-05-24T13:20:12.199Z] [Pipeline] }
[2019-05-24T13:20:12.233Z] [Pipeline] // stage
[2019-05-24T13:20:12.263Z] [Pipeline] }
[2019-05-24T13:20:12.319Z] [Pipeline] // node
[2019-05-24T13:20:12.409Z] [Pipeline] echo
[2019-05-24T13:20:12.423Z] Caught: hudson.AbortException: script returned exit code 2
[2019-05-24T13:20:12.484Z] [Pipeline] mail
[2019-05-24T13:20:14.880Z] [Pipeline] End of Pipeline
[2019-05-24T13:20:12.307Z] Terminated
[2019-05-24T13:20:15.340Z] 
[2019-05-24T13:20:15.340Z] GitHub has been notified of this commit’s build result
[2019-05-24T13:20:15.340Z] 
[2019-05-24T13:20:15.340Z] ERROR: script returned exit code 2
[2019-05-24T13:20:15.340Z] Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented May 29, 2019

Build failed; the context from the latest run is:

Expand to view
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 2858: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 2924: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 3796: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4397: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4417: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4504: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4552: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4590: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4657: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4686: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4790: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4844: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4901: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 4983: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5102: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5148: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5200: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5347: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5372: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5398: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5426: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5455: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5484: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5513: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5543: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5580: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5651: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5709: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5786: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5830: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: user-handbook.adoc: line 5850: invalid style for listing block: pipeline
[2019-05-29T13:29:51.216Z] asciidoctor: WARNING: could not embed image: /tmp/image-20190529-1-uhpz3v.jpg; No such file or directory @ rb_sysopen - /tmp/image-20190529-1-uhpz3v.jpg
[2019-05-29T13:29:51.216Z] Makefile:33: recipe for target 'pdfs' failed
[2019-05-29T13:29:51.216Z] make: *** [pdfs] Error 1
[2019-05-29T13:29:51.246Z] [Pipeline] }
[2019-05-29T13:29:51.278Z] [Pipeline] // timeout
[2019-05-29T13:29:51.300Z] [Pipeline] }
[2019-05-29T13:29:51.326Z] [Pipeline] // stage
[2019-05-29T13:29:51.347Z] [Pipeline] }
[2019-05-29T13:29:51.381Z] [Pipeline] // node
[2019-05-29T13:29:51.420Z] [Pipeline] echo
[2019-05-29T13:29:51.427Z] Caught: hudson.AbortException: script returned exit code 2
[2019-05-29T13:29:51.454Z] [Pipeline] mail
[2019-05-29T13:29:51.951Z] [Pipeline] End of Pipeline
[2019-05-29T13:29:52.323Z] 
[2019-05-29T13:29:52.323Z] GitHub has been notified of this commit’s build result
[2019-05-29T13:29:52.323Z] 
[2019-05-29T13:29:52.323Z] ERROR: script returned exit code 2
[2019-05-29T13:29:52.323Z] Finished: FAILURE

Powered by the Comment Logger

@zbynek

This comment has been minimized.

Copy link
Contributor

commented Jun 7, 2019

@sp1r nice progress, are you still interested in finishing this?

@sp1r

This comment has been minimized.

Copy link
Author

commented Jun 8, 2019

@zbynek I'm most certainly stuck.

@zbynek

This comment has been minimized.

Copy link
Contributor

commented Jun 8, 2019

@sp1r is there anything in particular you are stuck on? For your notes from the PR description

anchors for sections

Those are generated on client side in JavaScript, see content/_layouts/simplepage.html.haml

note/warning blocks

You can check how adoc writes those into HTML and build the same HTML structure in haml.

To simplify the structure of the haml file you can create partials: maybe one for a google group, one for non-google group and maybe one for the admonition (with parameters for content and type: warning/note).

@sp1r

This comment has been minimized.

Copy link
Author

commented Jun 10, 2019

@zbynek nothing specific I guess. I've tried to copy existing html to haml, became confused on eight's level of indentation and slowly lost all the motivation.

@MarkEWaite

This comment has been minimized.

Copy link
Contributor

commented Jun 16, 2019

Superseded by #2336 which has been merged. Thanks for launching the idea, and thanks @zbynek for bringing it to its conclusion. Much appreciated!

@MarkEWaite MarkEWaite closed this Jun 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
5 participants
You can’t perform that action at this time.