Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39891

Add i18n backend into a plugin and distribute with Blue Ocean

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Blocker Blocker
    • blueocean-plugin
    • None
    • tasman

      Context

      • We think that having two very different i18n behaviors across 2.7.x and the latest LTS is going to be a source of quality risk
      • We want all supported versions to use i18n in the same way

      In scope

      • Move i18n into a plugin and distribute with blue ocean
      • Resource bundles should be cached appropriately
        • /_i18n/resource/blueocean-dashboard/1.0.0/jenkins.plugins.blueocean.dashboard.Messages/en
        • /_i18n/resource/$PLUGIN_NAME/$PLUGIN_VERSION/$BUNDLE_NAME/$LANG
        • Any non-snapshot version should be cached for 365 days
        • Any snapshot version should not be cached
      • Update blueocean i18n so that it loads via the new endpoint above
      • Remove any english fall backs from the jsx as now all versions of Blue Ocean can load i18n bundles
      • Locale spec ala JENKINS-39034

          [JENKINS-39891] Add i18n backend into a plugin and distribute with Blue Ocean

          James Dumay added a comment -

          tfennelly out of curiosity how do you solve JENKINS-39891 when caching is involved?

          James Dumay added a comment - tfennelly out of curiosity how do you solve JENKINS-39891 when caching is involved?

          Tom FENNELLY added a comment -

          jamesdumay you referenced this JIRA. Did you mean JENKINS-39034 ? Either way, I'm not sure what you mean by "when caching is involved". Which caching are you referring to ... server-side or browser? As normal, the browser caching is based on the URL and the cache-control header is based on the isBrowserCacheable() check.

          Tom FENNELLY added a comment - jamesdumay you referenced this JIRA. Did you mean JENKINS-39034 ? Either way, I'm not sure what you mean by "when caching is involved". Which caching are you referring to ... server-side or browser? As normal, the browser caching is based on the URL and the cache-control header is based on the isBrowserCacheable() check .

          Michael Neale added a comment -

          FYI when it is time to publish, github.com/jenkins-infra/repository-permissions-updater will need a PR to give permissions to push the new hpi etc

          Michael Neale added a comment - FYI when it is time to publish, github.com/jenkins-infra/repository-permissions-updater will need a PR to give permissions to push the new hpi etc

            tfennelly Tom FENNELLY
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: