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 created issue -
          James Dumay made changes -
          Epic Link New: JENKINS-35749 [ 171790 ]
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Assignee Original: Tom FENNELLY [ tfennelly ]
          Description Original: *In scope*
          * Move i18n into a plugin and distribute with blue ocean
          * Resource bundles should be cached appropriately
          ** {{/_i18n/resource/myplugin/1.0.0/jenkins.plugins.blueocean.dashboard.Messages/en}}
          ** 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
          New: *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

          *In scope*
          * Move i18n into a plugin and distribute with blue ocean
          * Resource bundles should be cached appropriately
          ** {{/_i18n/resource/myplugin/1.0.0/jenkins.plugins.blueocean.dashboard.Messages/en}}
          ** 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
          Priority Original: Minor [ 4 ] New: Critical [ 2 ]
          James Dumay made changes -
          Description Original: *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

          *In scope*
          * Move i18n into a plugin and distribute with blue ocean
          * Resource bundles should be cached appropriately
          ** {{/_i18n/resource/myplugin/1.0.0/jenkins.plugins.blueocean.dashboard.Messages/en}}
          ** 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
          New: *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/myplugin/1.0.0/jenkins.plugins.blueocean.dashboard.Messages/en}}
          ** 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
          James Dumay made changes -
          Description Original: *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/myplugin/1.0.0/jenkins.plugins.blueocean.dashboard.Messages/en}}
          ** 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
          New: *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}}
          ** 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
          James Dumay made changes -
          Assignee New: Tom FENNELLY [ tfennelly ]
          James Dumay made changes -
          Priority Original: Critical [ 2 ] New: Blocker [ 1 ]
          James Dumay made changes -
          Description Original: *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}}
          ** 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
          New: *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
          Tom FENNELLY made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]

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

              Created:
              Updated:
              Resolved: