Details
-
Bug
-
Resolution: Fixed
-
Low
-
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
-
7.04
-
29
-
Severity 2 - Major
-
12
-
-
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.
