Skip to content

[JENKINS-67823] GitHub organization folders not rendered correctly (regression in Jenkins 2.335) #17877

Closed

Description

@jenkins-infra-bot

The GitHub organization folders on my Jenkins instance do not render correctly with Jenkins 2.335. I assume an icon is missing somewhere.

Similar issues seen elsewhere on the same instance:

Similar issue is also visible in GitLab and Gitea organization folders.

Removing the leading slash fixes it

 

 


Originally reported by markewaite, imported from: GitHub organization folders not rendered correctly (regression in Jenkins 2.335)
  • assignee: notmyfault
  • status: Closed
  • priority: Major
  • component(s): core
  • label(s): regression, ux
  • resolution: Fixed
  • resolved: 2022-04-08T14:45:46+00:00
  • votes: 6
  • watchers: 12
  • imported: 2025-11-24
Raw content of original issue

The GitHub organization folders on my Jenkins instance do not render correctly with Jenkins 2.335. I assume an icon is missing somewhere.

Similar issues seen elsewhere on the same instance:

Similar issue is also visible in GitLab and Gitea organization folders.

Removing the leading slash fixes it

 

 

environment
Jenkins: 2.335<br/>
OS: Linux - 4.18.0-348.12.2.el8_5.x86_64<br/>
---<br/>
PrioritySorter:4.1.0<br/>
ace-editor:1.1<br/>
adoptopenjdk:1.4<br/>
analysis-model-api:10.9.2<br/>
ant:1.13<br/>
antisamy-markup-formatter:2.7<br/>
apache-httpcomponents-client-4-api:4.5.13-1.0<br/>
async-http-client:1.9.40.0<br/>
authentication-tokens:1.4<br/>
authorize-project:1.4.0<br/>
badge:1.9.1<br/>
basic-branch-build-strategies:1.3.2<br/>
bitbucket:214.v2fd4234d0554<br/>
blueocean-commons:1.25.2<br/>
blueocean-config:1.25.2<br/>
blueocean-core-js:1.25.2<br/>
blueocean-dashboard:1.25.2<br/>
blueocean-display-url:2.4.1<br/>
blueocean-events:1.25.2<br/>
blueocean-git-pipeline:1.25.2<br/>
blueocean-github-pipeline:1.25.2<br/>
blueocean-i18n:1.25.2<br/>
blueocean-jwt:1.25.2<br/>
blueocean-personalization:1.25.2<br/>
blueocean-pipeline-api-impl:1.25.2<br/>
blueocean-pipeline-scm-api:1.25.2<br/>
blueocean-rest:1.25.2<br/>
blueocean-rest-impl:1.25.2<br/>
blueocean-web:1.25.2<br/>
bootstrap4-api:4.6.0-3<br/>
bootstrap5-api:5.1.3-5<br/>
bouncycastle-api:2.25<br/>
branch-api:2.7.0<br/>
build-blocker-plugin:1.7.8<br/>
build-name-setter:2.2.0<br/>
build-timeout:1.20<br/>
buildresult-trigger:0.17<br/>
caffeine-api:2.9.2-29.v717aac953ff3<br/>
checks-api:1.7.2<br/>
cloudbees-bitbucket-branch-source:751.vda_24678a_f781<br/>
cloudbees-folder:6.18<br/>
cloudbees-jenkins-advisor:3.3.2<br/>
clover:4.12.2-rc526.70638c0b_0a_16<br/>
code-coverage-api:2.0.4<br/>
command-launcher:1.6<br/>
conditional-buildstep:1.4.1<br/>
config-file-provider:3.9.0<br/>
configuration-as-code:1346.ve8cfa_3473c94<br/>
configurationslicing:1.53-rc424.6447a610239f<br/>
conventional-commits:0.11.0<br/>
copyartifact:1.46.2<br/>
credentials:1074.v60e6c29b_b_44b_<br/>
credentials-binding:1.27.1<br/>
data-tables-api:1.11.4-1<br/>
description-setter:1.10<br/>
display-url-api:2.3.5<br/>
docker-commons:1.19<br/>
docker-workflow:1.28<br/>
dtkit-api:3.0.0<br/>
durable-task:493.v195aefbb0ff2<br/>
echarts-api:5.3.0-2<br/>
elastic-axis:1.4.5<br/>
email-ext:2.87<br/>
envinject:2.4.0<br/>
envinject-api:1.8<br/>
external-monitor-job:191.v363d0d1efdf8<br/>
favorite:2.3.3<br/>
font-awesome-api:6.0.0-1<br/>
forensics-api:1.8.0<br/>
git:4.10.3<br/>
git-client:3.11.1-rc3029.b_07504b_cc834<br/>
git-forensics:1.4.0<br/>
git-parameter:0.9.15<br/>
git-server:1.10<br/>
gitea:1.4.1<br/>
github:1.34.2<br/>
github-api:1.301-378.v9807bd746da5<br/>
github-branch-source:2.11.4<br/>
github-scm-filter-aged-refs:0.2.0<br/>
github-scm-trait-commit-skip:0.4.0<br/>
gitlab-api:1.0.6<br/>
gitlab-branch-source:1.5.9<br/>
gitlab-plugin:1.5.28<br/>
gradle:1.38<br/>
groovy-postbuild:2.5<br/>
h2-api:1.4.199<br/>
handlebars:3.0.8<br/>
handy-uri-templates-2-api:2.1.8-1.0<br/>
htmlpublisher:1.29<br/>
implied-labels:0.9-rc53.5459bffcfe74<br/>
jackson2-api:2.13.1-246.va8a9f3eaf46a<br/>
jacoco:3.3.1<br/>
javadoc:217.v905b_86277a_2a_<br/>
javax-activation-api:1.2.0-2<br/>
javax-mail-api:1.6.2-5<br/>
jaxb:2.3.0.1<br/>
jdk-tool:1.5<br/>
jenkins-design-language:1.25.2<br/>
jersey2-api:2.35-3<br/>
jira:3.7<br/>
jjwt-api:0.11.2-9.c8b45b8bb173<br/>
jnr-posix-api:3.1.7-1<br/>
job-dsl:1.78.3<br/>
jquery:1.12.4-1<br/>
jquery3-api:3.6.0-2<br/>
jsch:0.1.55.2<br/>
junit:1.55<br/>
junit-realtime-test-reporter:82.vc2a_3f0f7a_291<br/>
label-verifier:1.4<br/>
ldap:2.7<br/>
leastload:3.0.0<br/>
lockable-resources:2.14<br/>
log-parser:2.2<br/>
mailer:408.vd726a_1130320<br/>
mapdb-api:1.0.9.0<br/>
matrix-auth:3.0.1<br/>
matrix-project:1.20<br/>
maven-plugin:3.17<br/>
mercurial:2.16<br/>
metrics:4.1.6.1<br/>
momentjs:1.1.1<br/>
monitoring:1.90.0<br/>
naginator:1.18.1<br/>
nodelabelparameter:1.10.3<br/>
okhttp-api:4.9.3-105.vb96869f8ac3a<br/>
pam-auth:1.7<br/>
parallel-test-executor:1.13<br/>
parameterized-trigger:2.43<br/>
pipeline-build-step:2.16<br/>
pipeline-github-lib:36.v4c01db_ca_ed16<br/>
pipeline-graph-analysis:188.v3a01e7973f2c<br/>
pipeline-graph-view:51.v5a693b766483<br/>
pipeline-input-step:446.vf27b_0b_83500e<br/>
pipeline-maven:3.10.0<br/>
pipeline-milestone-step:100.v60a_03cd446e1<br/>
pipeline-model-api:2.2064.v5eef7d0982b_e<br/>
pipeline-model-definition:2.2064.v5eef7d0982b_e<br/>
pipeline-model-extensions:2.2064.v5eef7d0982b_e<br/>
pipeline-rest-api:2.21<br/>
pipeline-stage-step:291.vf0a8a7aeeb50<br/>
pipeline-stage-tags-metadata:2.2064.v5eef7d0982b_e<br/>
pipeline-stage-view:2.21<br/>
pipeline-utility-steps:2.12.0<br/>
plain-credentials:1.8<br/>
platformlabeler:1252.vf3552fe534b_1<br/>
plugin-util-api:2.14.0<br/>
pollscm:1.3.1<br/>
popper-api:1.16.1-2<br/>
popper2-api:2.11.2-1<br/>
preSCMbuildstep:0.3<br/>
prism-api:1.26.0-2<br/>
promoted-builds:867.v7c3a_b_83a_eb_79<br/>
pubsub-light:1.16<br/>
resource-disposer:0.17<br/>
run-condition:1.5<br/>
scm-api:595.vd5a_df5eb_0e39<br/>
script-security:1131.v8b_b_5eda_c328e<br/>
snakeyaml-api:1.29.1<br/>
sse-gateway:1.25<br/>
ssh-agent:1.24.1<br/>
ssh-credentials:1.19<br/>
ssh-slaves:1.33.0<br/>
sshd:3.1.0<br/>
structs:308.v852b473a2b8c<br/>
support-core:2.80<br/>
swarm:3.30<br/>
testng-plugin:581.v200b_22e1a_b_4e<br/>
text-finder:1.18<br/>
throttle-concurrents:2.6<br/>
timestamper:1.17<br/>
token-macro:277.v7c8f82a_d66b_3<br/>
trilead-api:1.0.13<br/>
uno-choice:2.5.7<br/>
variant:1.4<br/>
versioncolumn:2.2<br/>
view-job-filters:2.3<br/>
warnings-ng:9.11.0<br/>
windows-slaves:1.8<br/>
workflow-aggregator:2.6<br/>
workflow-api:1138.v619fd5201b_2f<br/>
workflow-basic-steps:937.v7a_b_7579e07a_3<br/>
workflow-cps:2656.vf7a_e7b_75a_457<br/>
workflow-cps-global-lib:561.va_ce0de3c2d69<br/>
workflow-durable-task-step:1121.va_65b_d2701486<br/>
workflow-job:1167.v8fe861b_09ef9<br/>
workflow-multibranch:707.v71c3f0a_6ccdb_<br/>
workflow-scm-step:2.13<br/>
workflow-step-api:622.vb_8e7c15b_c95a_<br/>
workflow-support:813.vb_d7c3d2984a_0<br/>
ws-cleanup:0.40<br/>
xshell:0.10<br/>
xunit:3.0.5
8 attachments

Activity

  1. jenkins-infra-bot commented on Feb 16, 2022

    @jenkins-infra-bot
    Author
  2. jenkins-infra-bot commented on Feb 16, 2022

    @jenkins-infra-bot
    Author
    notmyfault:
    • Original comment link
    • Raw content of original comment:

      Could you take a look at "Inspect Element" in the browser? That could lead us into the right direction of the icon missing.

    Could you take a look at "Inspect Element" in the browser? That could lead us into the right direction of the icon missing.

  3. jenkins-infra-bot commented on Feb 17, 2022

    @jenkins-infra-bot
    Author
    han_geerligs:
    • Original comment link
    • Raw content of original comment:

      Hello,

       

      I observe the same behaviour for Gitea and GitLab organisation folders since updating to 2.335. See also attached image 

      --Han

    Hello,

     

    I observe the same behaviour for Gitea and GitLab organisation folders since updating to 2.335. See also attached image 

    --Han

  4. jenkins-infra-bot commented on Feb 17, 2022

    @jenkins-infra-bot
    Author
    markewaite:

    Thanks han_geerligs

    notmyfault here is an image from "Inspect" on that location

  5. jenkins-infra-bot commented on Feb 17, 2022

    @jenkins-infra-bot
    Author
    notmyfault:
    • Original comment link
    • Raw content of original comment:

      Does removing the leading slash make it work again?

      The URL itself looks fine.

      Edit: Hm, the class looks malformed nevertheless, because it solely defines the size, unless I'm mistaken.  Yes I was 

    Does removing the leading slash make it work again?

    The URL itself looks fine.

    Edit: Hm, the class looks malformed nevertheless, because it solely defines the size, unless I'm mistaken.  Yes I was 

  6. jenkins-infra-bot commented on Feb 17, 2022

    @jenkins-infra-bot
    Author
    markewaite:
    • Original comment link
    • Raw content of original comment:

      Yes, removing the leading '/' works.

    Yes, removing the leading '/' works.

  7. jenkins-infra-bot commented on Feb 17, 2022

    @jenkins-infra-bot
    Author
    han_geerligs:
    • Original comment link
    • Raw content of original comment:

      I can confirm that removing the / makes the icon visible again! See attachment.

       

      --Han

    I can confirm that removing the / makes the icon visible again! See attachment.

     

    --Han

  8. jenkins-infra-bot commented on Feb 18, 2022

    @jenkins-infra-bot
    Author
    cschoell:
    • Original comment link
    • Raw content of original comment:

      It seems to prepend the context path and then adds the configured jenkins url, before adding the actual sub path.

    It seems to prepend the context path and then adds the configured jenkins url, before adding the actual sub path.

  9. jenkins-infra-bot commented on Feb 23, 2022

    @jenkins-infra-bot
    Author
    phbaer:
    • Original comment link
    • Raw content of original comment:

      This is still an issue in 2.336 for Organization Folders configured for Bitbucket Team/Project.

      Had to roll back to 2.334.

    This is still an issue in 2.336 for Organization Folders configured for Bitbucket Team/Project.

    Had to roll back to 2.334.

  10. jenkins-infra-bot commented on Feb 23, 2022

    @jenkins-infra-bot
    Author
    notmyfault:

    Let's move this specific issue to https://issues.jenkins.io/browse/JENKINS-67877, because JENKINS-67823 is a different one.

  11. jenkins-infra-bot commented on Mar 31, 2022

    @jenkins-infra-bot
    Author
    han_geerligs:

    Hello,

     

    I observe that this issue occurs again for GitLab Branch Source with the latest release (Jenkins 2.342).

    URL for missing icon is http://han_mob:8080/gitlab-logo

    When going to the folder page the GitLab logo is displayed correctly:

    URL for correct folder icon is http://han_mob:8080/static/829452d6/plugin/gitlab-branch-source/images/48x48/gitlab-logo.png 

    --Han

  12. jenkins-infra-bot commented on Mar 31, 2022

    @jenkins-infra-bot
    Author
    gulyas_istvan_netlock:
    • Original comment link
    • Raw content of original comment:

      It also works well without host: /static/829452d6/plugin/gitlab-branch-source/images/48x48/gitlab-logo.png

    It also works well without host: /static/829452d6/plugin/gitlab-branch-source/images/48x48/gitlab-logo.png

  13. jenkins-infra-bot commented on Mar 31, 2022

    @jenkins-infra-bot
    Author
    notmyfault:

    cc janfaracik

  14. jenkins-infra-bot commented on Apr 7, 2022

    @jenkins-infra-bot
    Author
    basil:
    • Original comment link
    • Raw content of original comment:

      Between JENKINS-67823, JENKINS-67849, JENKINS-67869, and JENKINS-67877 I am having a hard time understanding what issues remain at the time of current writing. If you are still experiencing an issue and are running the latest weekly and latest plugins, please leave a comment in this ticket so that we can assess what remains to be done for this work unit.

    Between JENKINS-67823, JENKINS-67849, JENKINS-67869, and JENKINS-67877 I am having a hard time understanding what issues remain at the time of current writing. If you are still experiencing an issue and are running the latest weekly and latest plugins, please leave a comment in this ticket so that we can assess what remains to be done for this work unit.

  15. jenkins-infra-bot commented on Apr 8, 2022

    @jenkins-infra-bot
    Author
    phbaer:
    • Original comment link
    • Raw content of original comment:

      We're experiencing the issue still with Jenkins 2.342 and Bitbucket/Team Organization Folders with a path prefix. The icons are referenced like this:

      <img src="/jenkinshttps://some.domain.com/jenkins/custom-avatar-cache/69549bc20c74b266c34560cc7f5e182e.png?size=32x32" alt="Bitbucket Team/Project" tooltip="Bitbucket Team/Project" class="icon-lg" title="Bitbucket Team/Project">

       This situation is currently handled by the webserver with a redirect, hence no screen shot.

    We're experiencing the issue still with Jenkins 2.342 and Bitbucket/Team Organization Folders with a path prefix. The icons are referenced like this:

    Bitbucket Team/Project

     This situation is currently handled by the webserver with a redirect, hence no screen shot.

  16. jenkins-infra-bot commented on Apr 8, 2022

    @jenkins-infra-bot
    Author
    ben_gineer:
    • Original comment link
    • Raw content of original comment:

      Similar here on latest build. We see this for both GitHub and Bitbucket organisations:

       

      And the source looks like this:

      <img src="/jenkinshttps://avatars.githubusercontent.com/u/7047555?v=4&amp;s=32" alt="GitHub Organization" tooltip="GitHub Organization" class="icon-lg" title="GitHub Organization"> 

      As you can see, the prefix is unnecessarily added to the beginning.

       

    Similar here on latest build. We see this for both GitHub and Bitbucket organisations:

     

    And the source looks like this:

    "/jenkinshttps://avatars.githubusercontent.com/u/7047555?v=4&s=32" alt="GitHub Organization" tooltip="GitHub Organization" class="icon-lg" title="GitHub Organization"> 

    As you can see, the prefix is unnecessarily added to the beginning.

     

  17. jenkins-infra-bot commented on Apr 8, 2022

    @jenkins-infra-bot
    Author
    basil:
    • Original comment link
    • Raw content of original comment:

      OK, so it seems the only remaining issues are not specific to plugin but are specific to prefix, i.e. JENKINS-67849. So it seems I picked the wrong bug to close. My apologies. Let me reopen JENKINS-67849 and close this one. Let's continue the discussion over at JENKINS-67849.

    OK, so it seems the only remaining issues are not specific to plugin but are specific to prefix, i.e. JENKINS-67849. So it seems I picked the wrong bug to close. My apologies. Let me reopen JENKINS-67849 and close this one. Let's continue the discussion over at JENKINS-67849.

  18. jenkins-infra-bot commented on Apr 12, 2022

    @jenkins-infra-bot
    Author
    basil:
    • Original comment link
    • Raw content of original comment:

      This ticket has gone beyond the point where it is possible to discern what problems have been solved and what problems remain, so I am closing it.

      If you are having a problem and are running with a prefix, see JENKINS-67849.

      If you are having a problem and are not running with a prefix, file a new ticket with labels "ux" and "regression", the specific plugin you are using, and steps to reproduce the problem from scratch.

    This ticket has gone beyond the point where it is possible to discern what problems have been solved and what problems remain, so I am closing it.

    If you are having a problem and are running with a prefix, see JENKINS-67849.

    If you are having a problem and are not running with a prefix, file a new ticket with labels "ux" and "regression", the specific plugin you are using, and steps to reproduce the problem from scratch.

  19. jenkins-infra-bot commented on Nov 24, 2025

    @jenkins-infra-bot
    Author

    [Original is_duplicated_by from Jira: JENKINS-67869]

  20. removed
    bugFor changelog: Minor bug. Will be listed after features
    on Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions