Can't build JIRA 7.1.0 from source

Alex Shchagin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 13, 2016

It fails on JIRA Board plugin with the message:

Traceback (most recent call last):
  File "./jmake_npm_runner.py", line 10, in <module>
    NpmRunner().run_command(sys.argv[1:])
  File "../../../../jmake_src/node/NpmRunner.py", line 25, in run_command
    raise NodeRegistryMisconfiguredException("Atlassian NPM registry not configured, please refer to https://extranet.atlassian.com/display/NPM/npm.atlassian.io+Home or type:\n\n\n\n\tnpm login --registry=https://npm-private.atlassian.io --scope=atlassian\n\n\n")
node.NodeVersionChecker.NodeRegistryMisconfiguredException: Atlassian NPM registry not configured, please refer to https://extranet.atlassian.com/display/NPM/npm.atlassian.io+Home or type:
	npm login --registry=https://npm-private.atlassian.io --scope=atlassian

If I try to issue

npm login --registry=https://npm-private.atlassian.io --scope=Atlassian 

command it asks for a username and a password which I obviously do not have.

Mentioned https://extranet.atlassian.com pages are also not available.

Anything I can do with it?

3 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
JessicaB November 7, 2016

@Alexander Shchagin (quisapps) - how did you get past it complaining about the 'exec (exec-npm-install) on project jira-board-plugin: Command execution failed. Cannot run program "python3"' to get to the NPM problem?

Alex Shchagin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 7, 2016

Well here's the patch that makes JIRA 7.1.x buildable:

# HG changeset patch
# User alex
# Date 1463673850 -10800
#      Thu May 19 19:04:10 2016 +0300
# Node ID 0b091fca59decf83305ec6ead6dcef26c0dfcc4e
# Parent  c3bd363d1c3bd134c175ad48748e9b9ae3f2ef16
JIRA 7.1.7 POMs fixed to allow building
diff -r c3bd363d1c3b -r 0b091fca59de jira-source/atlassian-jira-7.1.7-source/jira-project/jira-components/jira-plugins/jira-board-plugin/pom.xml
--- a/jira-source/atlassian-jira-7.1.7-source/jira-project/jira-components/jira-plugins/jira-board-plugin/pom.xml	Thu May 19 19:03:26 2016 +0300
+++ b/jira-source/atlassian-jira-7.1.7-source/jira-project/jira-components/jira-plugins/jira-board-plugin/pom.xml	Thu May 19 19:04:10 2016 +0300
@@ -132,7 +132,7 @@
                     </filesets>
                 </configuration>
             </plugin>
-
+<!--
             <plugin>
                 <groupId>org.codehaus.mojo</groupId>
                 <artifactId>exec-maven-plugin</artifactId>
@@ -190,6 +190,7 @@
                     </execution>
                 </executions>
             </plugin>
+-->
         </plugins>
     </build>
 </project>
\ No newline at end of file
diff -r c3bd363d1c3b -r 0b091fca59de jira-source/atlassian-jira-7.1.7-source/jira-project/jira-components/jira-plugins/jira-fileviewer-plugin/pom.xml
--- a/jira-source/atlassian-jira-7.1.7-source/jira-project/jira-components/jira-plugins/jira-fileviewer-plugin/pom.xml	Thu May 19 19:03:26 2016 +0300
+++ b/jira-source/atlassian-jira-7.1.7-source/jira-project/jira-components/jira-plugins/jira-fileviewer-plugin/pom.xml	Thu May 19 19:04:10 2016 +0300
@@ -43,8 +43,8 @@
                 </executions>
             </plugin>
             <!--Specifics for File Preview-->
+<!--
             <plugin>
-                <!-- Install npm modules first -->
                 <groupId>org.codehaus.mojo</groupId>
                 <artifactId>exec-maven-plugin</artifactId>
                 <version>1.2.1</version>
@@ -87,6 +87,7 @@
                     </execution>
                 </executions>
             </plugin>
+-->
             <plugin>
                 <groupId>net.sf.alchim</groupId>
                 <artifactId>yuicompressor-maven-plugin</artifactId>
JessicaB November 8, 2016

@Alexander Shchagin (quisapps) - can you point me to where you found this? When I refer to the ticket it doesn't expose a lot, other then it was resolved in 7.2.0. Thank you!

 

If this helps someone else I got further, it then fussed about the 2nd step in the build.bat file (call mvn325.bat clean install -f jira-project/jira-components/jira-webapp/pom.xml -Dmaven.test.skip -Pbuild-from-source-dist -Dmaven.test.skip -s %SETTINGSFILE% -Dmaven.repo.local=%cd%\%LOCALREPO% %* )

[WARNING] The requested profile "build-from-source-dist" could not be activated because it does not exist. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.4.1 :clean (default-clean) on project atlassian-jira-webapp: Failed to clean project : Failed to delete C:\Users\xxxxxx\test\jira-project\jira-components\jira-weba pp\target\jira\WEB-INF\classes\com\atlassian\jira\workflow -> [Help 1]

The following POM file: /jira-source/atlassian-jira-7.1.7-source/jira-project/jira-distribution/jira-source-distribution/pom.xml doesn't have a profile named: build-from-source-dist but it does have:

<profiles>

    <profile>

        <id>build-source-distribution</id>

        <activation>

              <property>      

                   <name>!skipSourceDistribution</name>

              </property>

       </activation>

I updated my build.bat to reference that ID instead: call mvn325.bat clean install -f jira-project/jira-components/jira-webapp/pom.xml -Dmaven.test.skip -Pbuild-source-distribution -Dmaven.test.skip -s %SETTINGSFILE% -Dmaven.repo.local=%cd%\%LOCALREPO% %*

Then I reran my build.bat and eventually the Build was successful.

Alex Shchagin
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 8, 2016

@Jessica Bartsch It's my own :) For me, applying this patch was enough for the build to succeed; however, I build under Linux.

0 votes
ohernandez
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 28, 2016

Hi @Alexander Shchagin (quisapps) / @Audrius Idzelis,

This is caused by a bug, we have already been made aware of it and we are currently working on a fix.

The bug is being tracked at https://jira.atlassian.com/browse/JRA-60365

 

Regards,

 

Oswaldo Hernández.

JIRA Bugmaster.

[Atlassian].

0 votes
Audrius Idzelis March 16, 2016

Alexander Shchagin -did you manage to solve this issue ? I see the  same problem is still present in 7.1.1 and 7.1.2 releases.

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events