ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Oleg Nenashev
Dear all,

We would like to announce support of GitHub README files as a documentation source for plugins.jenkins.io. Some examples of the documentation from GitHub:
Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter
 
The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos. 

Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.  

How to enable GitHub documentation for your plugin? 
  • Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
  • Change the <url> field in pom.xml so that it points to GitHub (example PR)
  • Release a new plugin version
  • Wait for few hours till the change gets propagated
Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.

Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.

If you have any questions/feedback, please do not hesitate to answer in this thread or to join the https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.

Best regards,
Oleg Nenashev

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Matt Sicker
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <[hidden email]> wrote:

>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> https://plugins.jenkins.io/configuration-as-code
> https://plugins.jenkins.io/mailer
> https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Rick
Awesome feature!

On Wed, Sep 4, 2019 at 5:58 AM Matt Sicker <[hidden email]> wrote:
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <[hidden email]> wrote:
>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> https://plugins.jenkins.io/configuration-as-code
> https://plugins.jenkins.io/mailer
> https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.


--

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Gavin Mogan
Just so I understand, as I was kinda confused, https://plugins.jenkins.io/folder-auth is showing content because its pulling from github's README.md


I was very confused cause release logs kept being mentioned.

On Tue, Sep 3, 2019 at 4:46 PM Rick <[hidden email]> wrote:
Awesome feature!

On Wed, Sep 4, 2019 at 5:58 AM Matt Sicker <[hidden email]> wrote:
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <[hidden email]> wrote:
>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> https://plugins.jenkins.io/configuration-as-code
> https://plugins.jenkins.io/mailer
> https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.


--

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_Duv4CHGmGCq7a%2B8_nWnzYEuq0AoOdtYh%3DeVk2Jaw3Ov%2BXw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Oleg Nenashev
Hi Gavin,

I was very confused cause release logs kept being mentioned.

Release logs are generally not supported by the plugin site.There is a task to support CHANGELOG.md and GitHub Releases in WEBSITE-637, but it is yet to be implemented

Current state for changelogs:
  • If you publish Wiki documentation and keep changelog in Wiki and , it will be displayed on the plugin site. E.g. https://plugins.jenkins.io/cvs
  • If you publish GitHub documentation and keep changelog in README, it will be displayed on the plugin site. No example ATM
  • If you publish GitHub documentation and reference changelogs from README (badges or in text), the references will be displayed
  • If you publish GitHub documentation and just use GitHub releases or CHANGELOG.md without referencing them from readme, there will be no reference to changelog from the site
My plan is to eventually use the logic similar to how Dependabot displays changelogs in pull requests. Maybe even by reusing the Dependabot library in the Plugin Site backend or whatever changelog crawler.
Please let me know if it answers your question.

Best regards,
Oleg

On Wednesday, September 4, 2019 at 1:58:15 AM UTC+2, Gavin Mogan wrote:
Just so I understand, as I was kinda confused, <a href="https://plugins.jenkins.io/folder-auth" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;">https://plugins.jenkins.io/folder-auth is showing content because its pulling from github's README.md

Checking <a href="https://plugins.jenkins.io/folder-auth" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;">https://plugins.jenkins.io/folder-auth i can see <a href="https://wiki.jenkins.io/display/JENKINS/Folder+Authorization+Plugin" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FFolder%2BAuthorization%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4xGoJckPwO0kvtilpt7-0xuNpTQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FFolder%2BAuthorization%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4xGoJckPwO0kvtilpt7-0xuNpTQ&#39;;return true;">https://wiki.jenkins.io/display/JENKINS/Folder+Authorization+Plugin is quite empty, so that makes sense.

I was very confused cause release logs kept being mentioned.

On Tue, Sep 3, 2019 at 4:46 PM Rick <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="ZRvBDd1DAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">linux...@...> wrote:
Awesome feature!

On Wed, Sep 4, 2019 at 5:58 AM Matt Sicker <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="ZRvBDd1DAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">msi...@...> wrote:
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="ZRvBDd1DAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">o.v.n...@...> wrote:
>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for <a href="http://plugins.jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fplugins.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHbzOwz67aV6GYSsTTC8sHeRwDrFA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fplugins.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHbzOwz67aV6GYSsTTC8sHeRwDrFA&#39;;return true;">plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> <a href="https://plugins.jenkins.io/configuration-as-code" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fconfiguration-as-code\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGREdBv0YarfFQyrwXsMOEQsKruKA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fconfiguration-as-code\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGREdBv0YarfFQyrwXsMOEQsKruKA&#39;;return true;">https://plugins.jenkins.io/configuration-as-code
> <a href="https://plugins.jenkins.io/mailer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fmailer\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGEt9j8W84dKR4dgo0Z61Lbj_vdlQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fmailer\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGEt9j8W84dKR4dgo0Z61Lbj_vdlQ&#39;;return true;">https://plugins.jenkins.io/mailer
> <a href="https://plugins.jenkins.io/folder-auth" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;">https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use <a href="https://www.jsdelivr.com/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jsdelivr.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6cMUjfirRYQYBiqBEc7WNJ2IeIA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jsdelivr.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6cMUjfirRYQYBiqBEc7WNJ2IeIA&#39;;return true;">https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the <a href="https://gitter.im/jenkinsci/docs" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitter.im%2Fjenkinsci%2Fdocs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEKIgJnqAwLgiWMjrllLmZl6CIA9A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitter.im%2Fjenkinsci%2Fdocs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEKIgJnqAwLgiWMjrllLmZl6CIA9A&#39;;return true;">https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="ZRvBDd1DAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
> To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="ZRvBDd1DAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.


--
Zhao Xiaojie (Rick)
Blog: <a href="https://github.com/LinuxSuRen" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FLinuxSuRen\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG4gY6ISa78QQ6cKGlC4hBhOBiFHQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FLinuxSuRen\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG4gY6ISa78QQ6cKGlC4hBhOBiFHQ&#39;;return true;">https://github.com/LinuxSuRen
Twitter: <a href="https://twitter.com/suren69811254" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftwitter.com%2Fsuren69811254\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNERXvRNJdVgqBjy-eOOuilnpQMX_A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftwitter.com%2Fsuren69811254\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNERXvRNJdVgqBjy-eOOuilnpQMX_A&#39;;return true;">https://twitter.com/suren69811254

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="javascript:" target="_blank" gdf-obfuscated-mailto="ZRvBDd1DAQAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkin...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Robert Sandell-2
Finally!! Yay! :D

Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo.

/B

Den ons 4 sep. 2019 kl 09:47 skrev Oleg Nenashev <[hidden email]>:
Hi Gavin,

I was very confused cause release logs kept being mentioned.

Release logs are generally not supported by the plugin site.There is a task to support CHANGELOG.md and GitHub Releases in WEBSITE-637, but it is yet to be implemented

Current state for changelogs:
  • If you publish Wiki documentation and keep changelog in Wiki and , it will be displayed on the plugin site. E.g. https://plugins.jenkins.io/cvs
  • If you publish GitHub documentation and keep changelog in README, it will be displayed on the plugin site. No example ATM
  • If you publish GitHub documentation and reference changelogs from README (badges or in text), the references will be displayed
  • If you publish GitHub documentation and just use GitHub releases or CHANGELOG.md without referencing them from readme, there will be no reference to changelog from the site
My plan is to eventually use the logic similar to how Dependabot displays changelogs in pull requests. Maybe even by reusing the Dependabot library in the Plugin Site backend or whatever changelog crawler.
Please let me know if it answers your question.

Best regards,
Oleg

On Wednesday, September 4, 2019 at 1:58:15 AM UTC+2, Gavin Mogan wrote:
Just so I understand, as I was kinda confused, https://plugins.jenkins.io/folder-auth is showing content because its pulling from github's README.md


I was very confused cause release logs kept being mentioned.

On Tue, Sep 3, 2019 at 4:46 PM Rick <[hidden email]> wrote:
Awesome feature!

On Wed, Sep 4, 2019 at 5:58 AM Matt Sicker <[hidden email]> wrote:
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <[hidden email]> wrote:
>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> https://plugins.jenkins.io/configuration-as-code
> https://plugins.jenkins.io/mailer
> https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.


--

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Oleg Nenashev
Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo. 

Yes, we could do so. We have several cases when the documentation is hosted on custom pages or on jenkins.io, and there are definitely some opportunities for custom sources. Moeover, if this engine is eve implemented, we could reuse it later to implement the GitHub => jenkins.io publishing later.

The easiest way would be to....

BR, Oleg

On Wed, Sep 4, 2019 at 12:22 PM Robert Sandell <[hidden email]> wrote:
Finally!! Yay! :D

Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo.

/B

Den ons 4 sep. 2019 kl 09:47 skrev Oleg Nenashev <[hidden email]>:
Hi Gavin,

I was very confused cause release logs kept being mentioned.

Release logs are generally not supported by the plugin site.There is a task to support CHANGELOG.md and GitHub Releases in WEBSITE-637, but it is yet to be implemented

Current state for changelogs:
  • If you publish Wiki documentation and keep changelog in Wiki and , it will be displayed on the plugin site. E.g. https://plugins.jenkins.io/cvs
  • If you publish GitHub documentation and keep changelog in README, it will be displayed on the plugin site. No example ATM
  • If you publish GitHub documentation and reference changelogs from README (badges or in text), the references will be displayed
  • If you publish GitHub documentation and just use GitHub releases or CHANGELOG.md without referencing them from readme, there will be no reference to changelog from the site
My plan is to eventually use the logic similar to how Dependabot displays changelogs in pull requests. Maybe even by reusing the Dependabot library in the Plugin Site backend or whatever changelog crawler.
Please let me know if it answers your question.

Best regards,
Oleg

On Wednesday, September 4, 2019 at 1:58:15 AM UTC+2, Gavin Mogan wrote:
Just so I understand, as I was kinda confused, https://plugins.jenkins.io/folder-auth is showing content because its pulling from github's README.md


I was very confused cause release logs kept being mentioned.

On Tue, Sep 3, 2019 at 4:46 PM Rick <[hidden email]> wrote:
Awesome feature!

On Wed, Sep 4, 2019 at 5:58 AM Matt Sicker <[hidden email]> wrote:
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <[hidden email]> wrote:
>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> https://plugins.jenkins.io/configuration-as-code
> https://plugins.jenkins.io/mailer
> https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.


--

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAWWnWsHtGSSRhr6Lh6xhbdD-gKcewfrx_h%3DJihYFyDJQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

halkeye
Longer term too, it should probably be the actual git revision that was published, since master often contains changes that are not yet live.

On Wed., Sep. 4, 2019, 4:45 a.m. Oleg Nenashev, <[hidden email]> wrote:
Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo. 

Yes, we could do so. We have several cases when the documentation is hosted on custom pages or on jenkins.io, and there are definitely some opportunities for custom sources. Moeover, if this engine is eve implemented, we could reuse it later to implement the GitHub => jenkins.io publishing later.

The easiest way would be to....

BR, Oleg

On Wed, Sep 4, 2019 at 12:22 PM Robert Sandell <[hidden email]> wrote:
Finally!! Yay! :D

Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo.

/B

Den ons 4 sep. 2019 kl 09:47 skrev Oleg Nenashev <[hidden email]>:
Hi Gavin,

I was very confused cause release logs kept being mentioned.

Release logs are generally not supported by the plugin site.There is a task to support CHANGELOG.md and GitHub Releases in WEBSITE-637, but it is yet to be implemented

Current state for changelogs:
  • If you publish Wiki documentation and keep changelog in Wiki and , it will be displayed on the plugin site. E.g. https://plugins.jenkins.io/cvs
  • If you publish GitHub documentation and keep changelog in README, it will be displayed on the plugin site. No example ATM
  • If you publish GitHub documentation and reference changelogs from README (badges or in text), the references will be displayed
  • If you publish GitHub documentation and just use GitHub releases or CHANGELOG.md without referencing them from readme, there will be no reference to changelog from the site
My plan is to eventually use the logic similar to how Dependabot displays changelogs in pull requests. Maybe even by reusing the Dependabot library in the Plugin Site backend or whatever changelog crawler.
Please let me know if it answers your question.

Best regards,
Oleg

On Wednesday, September 4, 2019 at 1:58:15 AM UTC+2, Gavin Mogan wrote:
Just so I understand, as I was kinda confused, https://plugins.jenkins.io/folder-auth is showing content because its pulling from github's README.md


I was very confused cause release logs kept being mentioned.

On Tue, Sep 3, 2019 at 4:46 PM Rick <[hidden email]> wrote:
Awesome feature!

On Wed, Sep 4, 2019 at 5:58 AM Matt Sicker <[hidden email]> wrote:
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <[hidden email]> wrote:
>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> https://plugins.jenkins.io/configuration-as-code
> https://plugins.jenkins.io/mailer
> https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.


--

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAWWnWsHtGSSRhr6Lh6xhbdD-gKcewfrx_h%3DJihYFyDJQ%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutA4BPRjx%3DMrsZ%2BO2Rf5c04U0RQ75Dbk9zGcxsV9XC4_A%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Oleg Nenashev
Longer term too, it should probably be the actual git revision that was published, since master often contains changes that are not yet live.

https://issues.jenkins-ci.org/browse/WEBSITE-641 has been created for it a while ago. It would be a nice follow-up indeed
Anyway, the current behavior is pretty much like in Confluence.
 

On Wed, Sep 4, 2019 at 3:55 PM Gavin <[hidden email]> wrote:
Longer term too, it should probably be the actual git revision that was published, since master often contains changes that are not yet live.

On Wed., Sep. 4, 2019, 4:45 a.m. Oleg Nenashev, <[hidden email]> wrote:
Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo. 

Yes, we could do so. We have several cases when the documentation is hosted on custom pages or on jenkins.io, and there are definitely some opportunities for custom sources. Moeover, if this engine is eve implemented, we could reuse it later to implement the GitHub => jenkins.io publishing later.

The easiest way would be to....

BR, Oleg

On Wed, Sep 4, 2019 at 12:22 PM Robert Sandell <[hidden email]> wrote:
Finally!! Yay! :D

Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo.

/B

Den ons 4 sep. 2019 kl 09:47 skrev Oleg Nenashev <[hidden email]>:
Hi Gavin,

I was very confused cause release logs kept being mentioned.

Release logs are generally not supported by the plugin site.There is a task to support CHANGELOG.md and GitHub Releases in WEBSITE-637, but it is yet to be implemented

Current state for changelogs:
  • If you publish Wiki documentation and keep changelog in Wiki and , it will be displayed on the plugin site. E.g. https://plugins.jenkins.io/cvs
  • If you publish GitHub documentation and keep changelog in README, it will be displayed on the plugin site. No example ATM
  • If you publish GitHub documentation and reference changelogs from README (badges or in text), the references will be displayed
  • If you publish GitHub documentation and just use GitHub releases or CHANGELOG.md without referencing them from readme, there will be no reference to changelog from the site
My plan is to eventually use the logic similar to how Dependabot displays changelogs in pull requests. Maybe even by reusing the Dependabot library in the Plugin Site backend or whatever changelog crawler.
Please let me know if it answers your question.

Best regards,
Oleg

On Wednesday, September 4, 2019 at 1:58:15 AM UTC+2, Gavin Mogan wrote:
Just so I understand, as I was kinda confused, https://plugins.jenkins.io/folder-auth is showing content because its pulling from github's README.md


I was very confused cause release logs kept being mentioned.

On Tue, Sep 3, 2019 at 4:46 PM Rick <[hidden email]> wrote:
Awesome feature!

On Wed, Sep 4, 2019 at 5:58 AM Matt Sicker <[hidden email]> wrote:
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <[hidden email]> wrote:
>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> https://plugins.jenkins.io/configuration-as-code
> https://plugins.jenkins.io/mailer
> https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.


--

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com.


--
Robert Sandell
Software Engineer
CloudBees, Inc.
CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAWWnWsHtGSSRhr6Lh6xhbdD-gKcewfrx_h%3DJihYFyDJQ%40mail.gmail.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutA4BPRjx%3DMrsZ%2BO2Rf5c04U0RQ75Dbk9zGcxsV9XC4_A%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLCBDBVDGqzwdZH89Jj6q7vLV3Ozxg31hDK7eHybe7QDEQ%40mail.gmail.com.
Reply | Threaded
Open this post in threaded view
|

Re: ANN: Support of plugin docs from GitHub on plugins.jenkins.io (WEBSITE-406)

Oleg Nenashev
Hi all,

Just few updates here:
  • Over the last week 29 plugins were migrated to GitHub documentation sources. Some of them are waiting for release, but there is a good trend
    • Few examples: Git, Git Client, JobDSL, Kubernetes, Gradle, Warnings NG, Role Strategy, Mailer, etc.
  • There are example of migration to Gradle flow (e.g. here). It is also a one-line change for the url field in the jenkinsPlugin{} 
    closure from Gradle JPI Plugin
  • There were few updates in documentation rendering since the announcement:
    • There was a regression in Wiki rendering due t encoding issues. It was fixed by Zbynek in Plugin Site API v1.7.0
    • When GitHub source is used, the header and extra padding are now truncated, so there is no double header on the plugin page. Thanks to Zbynek again!
    • We added a "Links" tab to the right panel. Javadoc links have been added there. Later we will also add Changelog URLs, JIRA/GitHub issues links and other metadata which can be traversed from the repo
    • There is ongoing work by Zbynek to add support of arbitrary GitHub URLs as documentation sources, not just README. See https://github.com/jenkins-infra/plugin-site-api/pull/69

BR, Oleg

On Wednesday, September 4, 2019 at 4:04:34 PM UTC+2, Oleg Nenashev wrote:
Longer term too, it should probably be the actual git revision that was published, since master often contains changes that are not yet live.

<a href="https://issues.jenkins-ci.org/browse/WEBSITE-641" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FWEBSITE-641\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHm7xrTyVnFFEYw7vdKjTREHPPSkA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FWEBSITE-641\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHm7xrTyVnFFEYw7vdKjTREHPPSkA&#39;;return true;">https://issues.jenkins-ci.org/browse/WEBSITE-641 has been created for it a while ago. It would be a nice follow-up indeed
Anyway, the current behavior is pretty much like in Confluence.
 

On Wed, Sep 4, 2019 at 3:55 PM Gavin <[hidden email]> wrote:
Longer term too, it should probably be the actual git revision that was published, since master often contains changes that are not yet live.

On Wed., Sep. 4, 2019, 4:45 a.m. Oleg Nenashev, <[hidden email]> wrote:
Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo. 

Yes, we could do so. We have several cases when the documentation is hosted on custom pages or on <a href="http://jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">jenkins.io, and there are definitely some opportunities for custom sources. Moeover, if this engine is eve implemented, we could reuse it later to implement the GitHub => <a href="http://jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fjenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFxN3TNcVz4ABxnDGK3ixwttT1E1A&#39;;return true;">jenkins.io publishing later.

The easiest way would be to....
  • Add a new "hpi.pluginDocumentationUrl" property to Maven HPI Plugin (similar to hpi.pluginChangelogUrl and hpi.pluginLogoUrl  in <a href="https://github.com/jenkinsci/maven-hpi-plugin/releases/tag/maven-hpi-plugin-3.8" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fmaven-hpi-plugin%2Freleases%2Ftag%2Fmaven-hpi-plugin-3.8\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEW1s70mU98fPOqJvFQx-TXEsylMA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkinsci%2Fmaven-hpi-plugin%2Freleases%2Ftag%2Fmaven-hpi-plugin-3.8\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEW1s70mU98fPOqJvFQx-TXEsylMA&#39;;return true;">3.8)
  • Update <a href="https://github.com/jenkins-infra/update-center2" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fupdate-center2\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHSQVR6YBsJCH27r4himFm0dllMWA&#39;;return true;">Jenkins Update Center to take this property into account while generating <a href="http://mirror.serverion.com/jenkins/updates/current/plugin-documentation-urls.json" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmirror.serverion.com%2Fjenkins%2Fupdates%2Fcurrent%2Fplugin-documentation-urls.json\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGklvMSdQJEBn1deOEwZVKnZTi4nQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fmirror.serverion.com%2Fjenkins%2Fupdates%2Fcurrent%2Fplugin-documentation-urls.json\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGklvMSdQJEBn1deOEwZVKnZTi4nQ&#39;;return true;">plugin-documentation-urls JSON
  • Update <a href="https://github.com/jenkins-infra/plugin-site-api/blob/develop/src/main/java/io/jenkins/plugins/services/impl/GithubExtractor.java" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fplugin-site-api%2Fblob%2Fdevelop%2Fsrc%2Fmain%2Fjava%2Fio%2Fjenkins%2Fplugins%2Fservices%2Fimpl%2FGithubExtractor.java\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHsyIDiNPud6N5FA6CH-2M7yXkBGw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fplugin-site-api%2Fblob%2Fdevelop%2Fsrc%2Fmain%2Fjava%2Fio%2Fjenkins%2Fplugins%2Fservices%2Fimpl%2FGithubExtractor.java\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHsyIDiNPud6N5FA6CH-2M7yXkBGw&#39;;return true;">GitHubExtractor in <a href="https://github.com/jenkins-infra/plugin-site-api" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fplugin-site-api\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEs1ii0PulZUdZCODI1gm3oA6dMjQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2Fjenkins-infra%2Fplugin-site-api\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEs1ii0PulZUdZCODI1gm3oA6dMjQ&#39;;return true;">Plugin Site API to properly process custom URLs. A new extractor might be required
 I have created <a href="https://issues.jenkins-ci.org/browse/WEBSITE-648" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FWEBSITE-648\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIibxKP5THM58e7z1-UvMyZ-RPyQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FWEBSITE-648\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFIibxKP5THM58e7z1-UvMyZ-RPyQ&#39;;return true;">https://issues.jenkins-ci.org/browse/WEBSITE-648 for it.

BR, Oleg

On Wed, Sep 4, 2019 at 12:22 PM Robert Sandell <[hidden email]> wrote:
Finally!! Yay! :D

Would it be possible to have something other than the README.md? As I mentioned way back when the GSoC project that never finished, to me the README is more about the repository itself; what it is, how to build it etc. i.e. developer documentation. While user documentation should be something/somewhere else in the repo.

/B

Den ons 4 sep. 2019 kl 09:47 skrev Oleg Nenashev <[hidden email]>:
Hi Gavin,

I was very confused cause release logs kept being mentioned.

Release logs are generally not supported by the plugin site.There is a task to support CHANGELOG.md and GitHub Releases in <a href="https://issues.jenkins-ci.org/browse/WEBSITE-637" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FWEBSITE-637\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHnye_V7P_zSNelNVQ2Gonj9d8p5Q&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fissues.jenkins-ci.org%2Fbrowse%2FWEBSITE-637\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHnye_V7P_zSNelNVQ2Gonj9d8p5Q&#39;;return true;">WEBSITE-637, but it is yet to be implemented

Current state for changelogs:
  • If you publish Wiki documentation and keep changelog in Wiki and , it will be displayed on the plugin site. E.g. <a href="https://plugins.jenkins.io/cvs" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fcvs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGqqV6d-z_EXrhsI_9OQbqsUB1ogg&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fcvs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGqqV6d-z_EXrhsI_9OQbqsUB1ogg&#39;;return true;">https://plugins.jenkins.io/cvs
  • If you publish GitHub documentation and keep changelog in README, it will be displayed on the plugin site. No example ATM
  • If you publish GitHub documentation and reference changelogs from README (badges or in text), the references will be displayed
    • Badges example: <a href="https://plugins.jenkins.io/configuration-as-code" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fconfiguration-as-code\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGREdBv0YarfFQyrwXsMOEQsKruKA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fconfiguration-as-code\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGREdBv0YarfFQyrwXsMOEQsKruKA&#39;;return true;">https://plugins.jenkins.io/configuration-as-code
    • Text example: <a href="https://plugins.jenkins.io/mailer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fmailer\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGEt9j8W84dKR4dgo0Z61Lbj_vdlQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fmailer\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGEt9j8W84dKR4dgo0Z61Lbj_vdlQ&#39;;return true;">https://plugins.jenkins.io/mailer (scroll to the bottom)
  • If you publish GitHub documentation and just use GitHub releases or CHANGELOG.md without referencing them from readme, there will be no reference to changelog from the site
    • Example: <a href="https://plugins.jenkins.io/folder-auth" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;">https://plugins.jenkins.io/folder-auth (I will fix it today)
    • Users will need to navigate to GitHub to see the links to changelog
My plan is to eventually use the logic similar to how Dependabot displays changelogs in pull requests. Maybe even by reusing the Dependabot library in the Plugin Site backend or whatever changelog crawler.
Please let me know if it answers your question.

Best regards,
Oleg

On Wednesday, September 4, 2019 at 1:58:15 AM UTC+2, Gavin Mogan wrote:
Just so I understand, as I was kinda confused, <a href="https://plugins.jenkins.io/folder-auth" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;">https://plugins.jenkins.io/folder-auth is showing content because its pulling from github's README.md

Checking <a href="https://plugins.jenkins.io/folder-auth" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;">https://plugins.jenkins.io/folder-auth i can see <a href="https://wiki.jenkins.io/display/JENKINS/Folder+Authorization+Plugin" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FFolder%2BAuthorization%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4xGoJckPwO0kvtilpt7-0xuNpTQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwiki.jenkins.io%2Fdisplay%2FJENKINS%2FFolder%2BAuthorization%2BPlugin\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE4xGoJckPwO0kvtilpt7-0xuNpTQ&#39;;return true;">https://wiki.jenkins.io/display/JENKINS/Folder+Authorization+Plugin is quite empty, so that makes sense.

I was very confused cause release logs kept being mentioned.

On Tue, Sep 3, 2019 at 4:46 PM Rick <[hidden email]> wrote:
Awesome feature!

On Wed, Sep 4, 2019 at 5:58 AM Matt Sicker <[hidden email]> wrote:
Great news!

On Tue, Sep 3, 2019 at 4:18 PM Oleg Nenashev <[hidden email]> wrote:
>
> Dear all,
>
> We would like to announce support of GitHub README files as a documentation source for <a href="http://plugins.jenkins.io" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fplugins.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHbzOwz67aV6GYSsTTC8sHeRwDrFA&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fplugins.jenkins.io\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHbzOwz67aV6GYSsTTC8sHeRwDrFA&#39;;return true;">plugins.jenkins.io. Some examples of the documentation from GitHub:
>
> <a href="https://plugins.jenkins.io/configuration-as-code" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fconfiguration-as-code\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGREdBv0YarfFQyrwXsMOEQsKruKA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fconfiguration-as-code\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGREdBv0YarfFQyrwXsMOEQsKruKA&#39;;return true;">https://plugins.jenkins.io/configuration-as-code
> <a href="https://plugins.jenkins.io/mailer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fmailer\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGEt9j8W84dKR4dgo0Z61Lbj_vdlQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Fmailer\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNGEt9j8W84dKR4dgo0Z61Lbj_vdlQ&#39;;return true;">https://plugins.jenkins.io/mailer
> <a href="https://plugins.jenkins.io/folder-auth" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fplugins.jenkins.io%2Ffolder-auth\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH5EBBFc7JaAkNIBB_lS5eY5_Barw&#39;;return true;">https://plugins.jenkins.io/folder-auth
>
> Why? This is a long-anticipated feature, many plugins have already moved their documentation to GitHub. By supporting such source in plugin site we provide good user experience to Jenkins users who look for documentation. At the same time, plugin maintainers now can follow the documentation-as-code approach and make documentation changes a part of the pull requests. It also gives an opportunity to review the documentation changes and to add documentation contributor recognition, especially if the story is combined with Release Drafter.
>
> The story is tracked as WEBSITE-406 which is a part of the wider subproject for supporting GitHub-based documentation in the Jenkins plugin site and update managers (WEBSITE-637 under the umbrella of the Documentation SIG). Later steps include support showing changelogs from GitHub releases, showing plugin logos.
>
> Current state. GitHub documentation source support is a new feature, early adopters are welcome to try it out. There might be defects we have not discovered yet, and it is yet to be seen how it scales. The implementation uses a GitHub application token to get a high API limit, and we also use <a href="https://www.jsdelivr.com/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jsdelivr.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6cMUjfirRYQYBiqBEc7WNJ2IeIA&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.jsdelivr.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNE6cMUjfirRYQYBiqBEc7WNJ2IeIA&#39;;return true;">https://www.jsdelivr.com/ as a CDN for images. If you hit any issue, please file a ticket in the WEBSITE-637 EPIC.
>
> How to enable GitHub documentation for your plugin?
>
> Move documentation from Wiki to GitHub README if you have not done it yet. Both Markdown and Asciidoc are supported
> Change the <url> field in pom.xml so that it points to GitHub (example PR)
> Release a new plugin version
> Wait for few hours till the change gets propagated
>
> Code? If you want to see the changes under the hood of the plugin site, please see the links in Plugin Site API v1.6.0 (yes, now we have changelog there!). So far we needed only the backend changes to add the feature, but there will be front-end changes for other stories inside the EPIC. If you are a Java or JavaScript/React developer, any contributions will be appreciated. The plugin site is really easy to develop.
>
> Credits. I would like to thank Zbynek Konecny and Olivier Vernin for their work on these stories. They have done the vast majority of changes to make it happen.
>
> If you have any questions/feedback, please do not hesitate to answer in this thread or to join the <a href="https://gitter.im/jenkinsci/docs" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitter.im%2Fjenkinsci%2Fdocs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEKIgJnqAwLgiWMjrllLmZl6CIA9A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgitter.im%2Fjenkinsci%2Fdocs\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNEKIgJnqAwLgiWMjrllLmZl6CIA9A&#39;;return true;">https://gitter.im/jenkinsci/docs chat. We will also have sync-ups and demos at the regular Documentation SIG meetings.
>
> Best regards,
> Oleg Nenashev
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
> To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAKuSVR7cO-W%2BfXqe2K0BBsm8qa-38Arb-9Do32UHNDXg%40mail.gmail.com.



--
Matt Sicker
Senior Software Engineer, CloudBees

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAEot4ox_VA5Uyy2XN%3Df75xC07Z_CY3%3Dxjm3cXRjA_b1vdE59PA%40mail.gmail.com.


--
Zhao Xiaojie (Rick)
Blog: <a href="https://github.com/LinuxSuRen" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FLinuxSuRen\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG4gY6ISa78QQ6cKGlC4hBhOBiFHQ&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Fgithub.com%2FLinuxSuRen\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNG4gY6ISa78QQ6cKGlC4hBhOBiFHQ&#39;;return true;">https://github.com/LinuxSuRen
Twitter: <a href="https://twitter.com/suren69811254" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftwitter.com%2Fsuren69811254\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNERXvRNJdVgqBjy-eOOuilnpQMX_A&#39;;return true;" onclick="this.href=&#39;https://www.google.com/url?q\x3dhttps%3A%2F%2Ftwitter.com%2Fsuren69811254\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNERXvRNJdVgqBjy-eOOuilnpQMX_A&#39;;return true;">https://twitter.com/suren69811254

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAMM7nTFdtSin_SFeop25Pr0Sas%2BXgXzubapiZgEMvRY9c6nZcA%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/199e5624-89ac-4e9d-b674-848d9c796efd%40googlegroups.com.


--
Robert Sandell
Software Engineer
CloudBees,<a href="http:///" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http:///&#39;;return true;" onclick="this.href=&#39;http:///&#39;;return true;"> Inc.
<a href="http://www.cloudbees.com/" rel="nofollow" target="_blank" onmousedown="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.cloudbees.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFD5q8pAuc6CUBHDK6LlPC4hQt3lQ&#39;;return true;" onclick="this.href=&#39;http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.cloudbees.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFD5q8pAuc6CUBHDK6LlPC4hQt3lQ&#39;;return true;">CloudBees-Logo.png
Twitter: robert_sandell

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit <a href="https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe&#39;;return true;">https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS1ux03k%3DW-QWmoz6PMC70CWVF%2BTp9RcT3kONx%2B2h_g3Tw%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAWWnWsHtGSSRhr6Lh6xhbdD-gKcewfrx_h%3DJihYFyDJQ%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" rel="nofollow" target="_blank" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAWWnWsHtGSSRhr6Lh6xhbdD-gKcewfrx_h%3DJihYFyDJQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAWWnWsHtGSSRhr6Lh6xhbdD-gKcewfrx_h%3DJihYFyDJQ%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLAWWnWsHtGSSRhr6Lh6xhbdD-gKcewfrx_h%3DJihYFyDJQ%40mail.gmail.com.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit <a href="https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe&#39;;return true;">https://groups.google.com/d/topic/jenkinsci-dev/VSdfVMDIW-A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to [hidden email].
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutA4BPRjx%3DMrsZ%2BO2Rf5c04U0RQ75Dbk9zGcxsV9XC4_A%40mail.gmail.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutA4BPRjx%3DMrsZ%2BO2Rf5c04U0RQ75Dbk9zGcxsV9XC4_A%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutA4BPRjx%3DMrsZ%2BO2Rf5c04U0RQ75Dbk9zGcxsV9XC4_A%40mail.gmail.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-dev/CAG%3D_DutA4BPRjx%3DMrsZ%2BO2Rf5c04U0RQ75Dbk9zGcxsV9XC4_A%40mail.gmail.com.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/6442aa9d-b3cf-4005-afea-349456e55019%40googlegroups.com.