Error Building Atlassian JIRA 7.4.0

Jira Development Jira Server
1

I’m currently trying to build JIRA 7.4.0 each time I try the build it fails at the same place.

[INFO] verbose 4.458 Performing "GET" request to "https://npm-private.atlassian.io/@atlassian%2fstyl
elint-config-atlassian-fecq/-/@atlassian%2fstylelint-config-atlassian-fecq-1.0.0.tgz".
[INFO] verbose 26.008 Error: connect ETIMEDOUT 10.124.144.206:443
[INFO]     at Object.exports._errnoException (util.js:1029:11)
[INFO]     at exports._exceptionWithHostPort (util.js:1052:20)
[INFO]     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1093:14)
[INFO] info If you think this is a bug, please open a bug report with the information provided in "C
:\\test\\atlassian-jira-software-7.4.0-source\\jira-project\\yarn-error.log".
[INFO] info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
[ERROR] error An unexpected error occurred: "https://npm-private.atlassian.io/@atlassian%2ffecq-enfo
rcer/-/@atlassian%2ffecq-enforcer-5.1.3.tgz: connect ETIMEDOUT 10.124.144.206:443".

...

[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.3:yarn (yarn install) on
project jira-project: Failed to run task: 'yarn install --production --frozen-lockfile --prefer-offl
ine --no-progress --verbose' failed. (error code 1) -> [Help 1]

The yarn log file does not provide much help with the following error:

Trace: 
  Error: connect ETIMEDOUT 10.124.144.206:443
      at Object.exports._errnoException (util.js:1029:11)
      at exports._exceptionWithHostPort (util.js:1052:20)
      at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1093:14)

I’m running with the following config.
Winodws7
JDK 1.8.0_144
atlassian-jira-software-7.4.0-source

If anyone has experienced this error and knows a work around it would be appreciated.

1 Like
2

Looks like Atlassian has put an internal npm server into the 7.4 source. The only real way to fix it (since I’m hoping it needs that artifact somewhere) is to contact Atlassian through support.atlassian.com to get them to fix it (since it’s broken).

1 Like
3

I’ve filed a bug report for the behavior as it appears to be present in 7.4.0 up to the current release. You view the details of the bug report here JRASERVER-66224.

1 Like
4

My company would like to use like to use JIRA, but has encryption requirements (comments, worklog entries, fields, etc.) that will require forking the source.

What sort of timeline can we expect for fixing this and any similar issues that appear in the future? It will be a big problem if some major vulnerability is patched and due to a broken build we have to manually backport it.