You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 38 Next »

The following tables list the tools used in OpenECOMP development. This is intended for reference. For instructions on installing client tools and preparing to access the server-based tools, see Setting Up Your Development Environment.

Client-Based Tools

These tools are installed on your client development system.

Tool NameURLDescription
Git client https://www.atlassian.com/git/tutorials/install-git

Client for distributed source control system. The download referenced here includes the command-line tool Git Bash.

IntelliJ

https://www.jetbrains.com/idea/

One of several possible Java development environments. (The IntelliJ Community Edition is open source.) Uses the Java SDK.

Java SDKhttp://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.htmlRequired for Java builds
Mavenhttp://maven.apache.org/download.cgicommand-line tool for building Java (and other) programs
PuTTYhttp://www.putty.org/Remote SSH terminal; also, a public/private key generator.
Python (optional)

https://www.python.org/

Script engine needed by some components
other tools
See the Development Guides for specific additional tools required by different subsystems. Example tools include: nodejs, node-gyp (which in turn requires Python v.2.7.x and GCC), grunt-cli, and bower.

Server-Based Tools and Repositories

These tools and repositories are server-based. Some are accessed via a browser with no setup, other than obtaining a login and password. Others may require you to set environment variables, create private encryption keys, or make settings within client tools.

Tool NameURLDescription
Confluencehttps://wiki.openecomp.orgOpenECOMP Development Wiki, used to provide project documentation, guidelines, and other information.
Gerrit serverhttps://gerrit.openecomp.org/

Gerrit code review server, hosting the Git repositories as well as controlling access, push, and review of new code. It also hosts the Jenkins job configuration in a Git repository that follows the same workflow.

Identity portalhttps://identity.linuxfoundation.org/registering portal : controls user account and group management.
Jenkins Masterhttps://jenkins.openecomp.org/

OpenECOMP Jenkins Master host, this host will only serve as a 'Display' as most of the jobs will be executed by 'minions' (slave hosts which are defined by using the Jenkins configuration repository in Gerrit).

JIRAhttps://jira.openecomp.org/OpenECOMP JIRA instance, used to track issues, releases, stories...
Nexus 2https://nexus.openecomp.org/OpenECOMP Nexus 2 repository, this repo will hold Maven2 artifacts produced by builds (both Release and Snapshot, also Javadoc-mavensite), Access is automatically provided to builds by the maven settings on the Jenkins Master, see Jenkins job for more details. User should be able to access and browse artifacts through this URL.
Nexus 3https://nexus3.openecomp.org/OpenECOMP Nexus 3 repository, this repo will hold Docker containers produced by OpenECOMP builds. Access is automatically provided to builds by the maven settings on the Jenkins Master, see Jenkins job for more details. User should be able to access and browse artifacts through this URL.
Sonarhttps://sonar.openecomp.org/OpenECOMP Sonar server, will hold Sonar metrics computed by component builds
  • No labels