Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-66224

Jira 7.4.0 and higher cannot be built from source due to internal NPM registry

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Gathering Impact (View Workflow)
    • Priority: Low
    • Resolution: Unresolved
    • Affects Version/s: 7.4.0, 7.4.1, 7.4.2, 7.5.0, 7.4.3, 7.4.4, 7.4.5, 7.5.1, 7.5.2, 7.6.0, 7.5.3, 7.4.6, 7.5.4, 7.6.1, 7.6.2, 7.6.3, 7.6.4, 7.4.7, 7.8.0, 7.8.1, 7.8.2, 7.6.5, 7.8.3, 7.9.0, 7.10.0, 7.9.2, 7.6.6, 7.8.4, 7.11.0, 7.10.1, 7.6.7, 7.10.2, 7.6.8, 7.11.1, 7.11.2, 7.12.0, 7.12.1, 7.12.2, 7.12.3
    • Fix Version/s: None
    • Component/s: Installation
    • Introduced in Version:
      7.04
    • Support reference count:
      14
    • Symptom Severity:
      Severity 2 - Major
    • UIS:
      40
    • Current Status:
      Hide
      Atlassian Update – 22 October 2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.

      Atlassian will keep the issue open and continue to watch this issue for the further updates.

      Thank you,
      Ignat Alexeyenko
      Jira Bugmaster

      Show
      Atlassian Update – 22 October 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in next 6 months. Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will keep the issue open and continue to watch this issue for the further updates. Thank you, Ignat Alexeyenko Jira Bugmaster

      Description

      Summary

      Attempting to build Jira from source will fail to build as resources are required from an internal registry not open to the public.

      Steps to Reproduce

      Attempt to build Jira from source by initiating ./build.sh

      Expected Results

      Jira build completes successfully

      Actual Results

      The build fails due to connection failures. Resources from an internal registry https://npm-private.atlassian.io can't be obtained.

      Notes

      There are 3 files that reference the internal registry

      <source>/jira-project/yarn.lock
      <source>/jira-project/jira-components/jira-webapp/src/main/resources/johnson-page/yarn.lock
      <source>/jira-project/conf/frontend/npm/preinstall.js

      The build fails because the registry is not a public registry and the build log shows:

      [INFO] verbose 1.072 Error: https://npm-private.atlassian.io/@atlassian%2feslint-config-jira-fecq/-/@atlassian%2feslint-config-jira-fecq-3.1.0.tgz: Request failed "401 Unauthorized"
      

       

      Workaround

      No workaround for building source. Jira must be installed with standard binary/installer.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              sseaver Shaun Seaver
              Votes:
              60 Vote for this issue
              Watchers:
              50 Start watching this issue

                Dates

                Created:
                Updated: