# Plugin documentation migration

**URL:** <https://community.jenkins.io/t/plugin-documentation-migration/11939>\
**Category:** Contributing\
**Tags:** sig-docs\
**Created:** [January 22, 2024, 1:39pm UTC](https://community.jenkins.io/t/plugin-documentation-migration/11939 "2024-01-22T13:39:27Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![FrogDevelopper](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/frogdevelopper/32/5771_2.png) [@FrogDevelopper](https://community.jenkins.io/u/FrogDevelopper)\
**Post date:** [January 22, 2024, 1:39pm UTC](https://community.jenkins.io/t/plugin-documentation-migration/11939/1 "2024-01-22T13:39:27Z")

</div>

Hello  
I’ve followed the steps in [How to enable GitHub documentation for your plugin?](https://www.jenkins.io/blog/2019/10/21/plugin-docs-on-github/#how-to-enable-github-documentation-for-your-plugin) to have the plugin display documentation from Github instead of the out-dated wiki.  
Even if the `<url>` balise target the Github repository in the [pom.xml](https://github.com/jenkinsci/multibranch-build-strategy-extension-plugin/blob/3dc306525d0cbb8416d5f508a95ccd581f3d1898/pom.xml#L20) in controller, the site still display the old documentation.

It has been 4 days now, so the page shouldn’t be displaying the correct documentation ?

What am I missing ?

---

<div class="post-metadata">

**Author:** ![FrogDevelopper](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/frogdevelopper/32/5771_2.png) [@FrogDevelopper](https://community.jenkins.io/u/FrogDevelopper)\
**Post date:** [January 22, 2024, 1:41pm UTC](https://community.jenkins.io/t/plugin-documentation-migration/11939/2 "2024-01-22T13:41:02Z")

</div>

Link to plugin: [Pipeline: Multibranch build strategy extension](https://plugins.jenkins.io/multibranch-build-strategy-extension/)

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [January 22, 2024, 1:53pm UTC](https://community.jenkins.io/t/plugin-documentation-migration/11939/3 "2024-01-22T13:53:39Z")

</div>

The plugin documentation URL is extracted from the pom file of the **most recent release** of the plugin. If you haven’t delivered a new release of the plugin, then the documentation URL of the plugin will remain on the wiki.

If you apply the `developer` label to the [pull request](https://github.com/jenkinsci/multibranch-build-strategy-extension-plugin/pull/29) that modified the documentation URL, then that will generate a new release and 6-12 hours after that release, the page on the plugins site will be updated.

---

<div class="post-metadata">

**Author:** ![FrogDevelopper](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/frogdevelopper/32/5771_2.png) [@FrogDevelopper](https://community.jenkins.io/u/FrogDevelopper)\
**Post date:** [January 22, 2024, 1:56pm UTC](https://community.jenkins.io/t/plugin-documentation-migration/11939/4 "2024-01-22T13:56:11Z")

</div>

OK, thanks

I didn’t knew about the `developer` label

---

<div class="post-metadata">

**Author:** ![MarkEWaite](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/markewaite/32/20_2.png) [@MarkEWaite](https://community.jenkins.io/u/MarkEWaite)\
**Post date:** [January 22, 2024, 2:10pm UTC](https://community.jenkins.io/t/plugin-documentation-migration/11939/5 "2024-01-22T14:10:29Z")

</div>

You may need to invoke the GitHub action yourself from the repository.