opendevstack / opendevstack/ods-quickstarters

Add configurations to use internal Nexus repository

Open
#810 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
39
Forks
50
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.
Building of new projects fail due to missing repository configuration.

Describe the solution you'd like
Adding the required configurations to the project would provide a solid foundation and consistency across projects.
e.g. A Java project using gradle requires the correct Nexus URL for code dependencies ( in build.gradle) and managing plugins (in settings.gradle)

Describe alternatives you've considered
An alternative is to allow the firewall to connect to all public repositories

Additional context
none

Example settings.gradle settings:

pluginManagement {
    repositories {
        maven {
            url "https://nexus-repository-url.some.where/repository/maven-central/"
        }
        maven {
            url "https://nexus-repository-url.some.where/repository/atlassian_public/"
        }
        maven {
            url "https://nexus-repository-url.some.where/repository/maven-public/"
        }
    }
}
rootProject.name = 'my-amazing-project'

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by inspecting the Java quickstarter Gradle configuration, especially build.gradle and settings.gradle, and compare how dependency and plugin repositories are currently defined. Determine which project quickstarters need the internal Nexus configuration, then verify that new projects can resolve dependencies and plugins without access to public repositories.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system, devops
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.