[JENKINS-75931] core taglibs generate mismatching links and anchors

[jenkins-infra-bot]

Table of content links do not correctly link to anchors on https://reports.jenkins.io/core-taglib/jelly-taglib-ref.html

E.g. the link target is https://reports.jenkins.io/core-taglib/jelly-taglib-ref.html#form:apply

But the actual anchor is form.3Aapply, i.e., https://reports.jenkins.io/core-taglib/jelly-taglib-ref.html#form.3Aapply 

Bisecting indicates this broke between 2.481 (working) and 2.482 (broken).

---

Related infra https://github.com/jenkins-infra/core-taglibs-report-generator/tree/master just runs the core site build and publishes the output.

---

Originally reported by danielbeck, imported from: core taglibs generate mismatching links and anchors

• assignee: danielbeck
• status: Closed
• priority: Minor
• component(s): core
• label(s): 2.516.2-fixed, regression
• resolution: Fixed
• resolved: 2025-07-25T11:42:04+00:00
• votes: 0
• watchers: 3
• imported: 2025-11-24

Raw content of original issue

Table of content links do not correctly link to anchors on https://reports.jenkins.io/core-taglib/jelly-taglib-ref.html

E.g. the link target is https://reports.jenkins.io/core-taglib/jelly-taglib-ref.html#form:apply

But the actual anchor is form.3Aapply, i.e., https://reports.jenkins.io/core-taglib/jelly-taglib-ref.html#form.3Aapply 

Bisecting indicates this broke between 2.481 (working) and 2.482 (broken).

Related infra https://github.com/jenkins-infra/core-taglibs-report-generator/tree/master just runs the core site build and publishes the output.

[jenkins-infra-bot]

• Remote links associated with this issue:

  • jellydoc-maven-plugin#​154
  • Parent pom PR 700 - use updated Maven plugin
  • Parent pom PR 698 - use updated Maven plugin
  • Jenkins core PR 10928 to use parent pom 1.136

[jenkins-infra-bot]

krisstern:

• Original comment link
• Raw content of original comment:

  danielbeck Does this really belong to `core` as an `lts-candidate`? 
  

danielbeck Does this really belong to `core` as an `lts-candidate`? 

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  krisstern Only way to fix the site. It basically runs a core build.
  

krisstern Only way to fix the site. It basically runs a core build.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  The same failure happens with Jenkins weekly as is reported for Jenkins LTS.  This is a good LTS candidate but the fix needs to be included in a Jenkins weekly release before it can be backported.
  
  Fixing it in a Jenkins weekly release requires a new release of the Jenkins parent pom that is included in a Jenkins weekly release.  The parent pom pull request was merged last week but there has not been a new release of the parent pom.  Once parent pom 1.135 or later is released, the parent pom can be updated in Jenkins weekly and then that parent pom update can be considered as a possible backport candidate for an LTS.
  

The same failure happens with Jenkins weekly as is reported for Jenkins LTS. This is a good LTS candidate but the fix needs to be included in a Jenkins weekly release before it can be backported.

Fixing it in a Jenkins weekly release requires a new release of the Jenkins parent pom that is included in a Jenkins weekly release. The parent pom pull request was merged last week but there has not been a new release of the parent pom. Once parent pom 1.135 or later is released, the parent pom can be updated in Jenkins weekly and then that parent pom update can be considered as a possible backport candidate for an LTS.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  danielbeck the new release (226.x)  of the jellydoc maven plugin is included in Jenkins 2.522 as part of pull request 10922.  I confirmed that version of the jellydoc maven plugin is used by running mvn versions:plugin-updates-report .  However, when I checkout the jenkins-2.522 tag, change to the core directory, and run the build command, the links still seem to be incorrect.  Commands that I used were:
  
  
  git checkout jenkins-2.522
  mvn -am -pl war,bom -Pquick-build clean install
  cd core
  mvn --show-version --batch-mode -DgenerateProjectInfo=false -DgenerateSitemap=false -e clean site:site
  grep -r form.*apply target
  target/site/jelly-taglib-ref.html:<td><a href='#form:apply'>apply</a></td>
  
  
  Is there some mistake that I've made in using the new release of the jellydoc maven plugin?
  

danielbeck the new release (226.x) of the jellydoc maven plugin is included in Jenkins 2.522 as part of pull request 10922. I confirmed that version of the jellydoc maven plugin is used by running mvn versions:plugin-updates-report . However, when I checkout the jenkins-2.522 tag, change to the core directory, and run the build command, the links still seem to be incorrect. Commands that I used were:

git checkout jenkins-2.522
mvn -am -pl war,bom -Pquick-build clean install
cd core
mvn --show-version --batch-mode -DgenerateProjectInfo=false -DgenerateSitemap=false -e clean site:site
grep -r form.*apply target
target/site/jelly-taglib-ref.html:'#form:apply'>apply

Is there some mistake that I've made in using the new release of the jellydoc maven plugin?

[jenkins-infra-bot]

danielbeck:

• Original comment link
• Raw content of original comment:

  My best guess is that Bump org.jenkins-ci:jenkins from 1.134 to 1.135 stapler-maven-plugin#155 is also a prerequisite. See the command I ended up invoking in my PR and the description below.
  

My best guess is that jenkinsci/stapler-maven-plugin#155 is also a prerequisite. See the command I ended up invoking in my PR and the description below.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  Thanks!  That makes sense.  I've approved that pull request and marked it as a bug fix.  We should have a new release of the stapler maven plugin soon.
  
  I've confirmed with a local build that issue is solved with the combination of the new release of the stapler maven plugin and the recent release of the jellydoc maven plugin.  A new release of the Jenkins parent pom should be available later today and will include that fix.
  

Thanks! That makes sense. I've approved that pull request and marked it as a bug fix. We should have a new release of the stapler maven plugin soon.

I've confirmed with a local build that issue is solved with the combination of the new release of the stapler maven plugin and the recent release of the jellydoc maven plugin. A new release of the Jenkins parent pom should be available later today and will include that fix.

[jenkins-infra-bot]

markewaite:

• Original comment link
• Raw content of original comment:

  I confirmed that parent pom 1.136 works as expected.  Checked with a local build of Update dependency org.jenkins-ci:jenkins to v1.136 #10928
  

I confirmed that parent pom 1.136 works as expected. Checked with a local build of #10928