https://github.com/baxeno/maven-noci-publisher

Publish Maven artifacts into Artifactory without CI
https://github.com/baxeno/maven-noci-publisher

artifactory bash continuous-delivery gradle linux maven

Last synced: about 20 hours ago
JSON representation

Publish Maven artifacts into Artifactory without CI

• Host: GitHub
• URL: https://github.com/baxeno/maven-noci-publisher
• Owner: baxeno
• License: mit
• Created: 2018-04-11T17:29:11.000Z (over 6 years ago)
• Default Branch: master
• Last Pushed: 2018-09-20T18:51:51.000Z (about 6 years ago)
• Last Synced: 2024-07-30T17:52:40.618Z (4 months ago)
• Topics: artifactory, bash, continuous-delivery, gradle, linux, maven
• Language: Shell
• Size: 54.7 KB
• Stars: 3
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# maven-noci-publisher

This tool make it possible to publish Maven artifacts into [Artifactory](https://jfrog.com/artifactory/) using [Gradle](https://gradle.org/) without a [Jenkins](https://jenkins.io/) CI pipeline.

The following use cases can be solved:

1. When transitioning an organization or a company into a continues delivery model where legacy components and products still need maintenance with infrequent releases in an old workflow, ex. no pipeline as code, no git source management (SVN, CVS), no artifact management, manual test, etc.

1. 3rd party components are needed in a pipeline, but they are not released in a binary repository, ex. source code releases of OpenSSL, cURL, Linux kernel, etc.

## Requirements

**Shell:**

Use one of the following shells to execute the `publish.sh` script:

_Linux:_ Bash

_Windows:_ GitBash

> Note: Other shells might also work but has not been tested.

**Artifactory permissions:**

The user running this tool must have `Deploy/Cache` permissions to Maven repositories.

**Gradle (Artifactory) configuration:**

Setup Artifactory credentials for use in Gradle.

_Linux:_ `~/.gradle/init.d/artifactory.gradle`

_Windows:_ `C:\Users\xxx\.gradle\init.d\artifactory.gradle`

> Note: Create parent directories in case they don't exist, ex. `mkdir -p ~/.gradle/init.d`.

Template for`artifactory.gradle` can be seen below:

```

allprojects {

  ext {

    artifactory_contextUrl = "https://artifactory.company.com/artifactory"

    artifactory_user = "xxx"

    artifactory_password = "123456789abcdef01234567890"

  }

}

```

> Note: Use API key from Artifactory as `artifactory_password`.

> 1) Avoid leaving your password in a plain text file.

> 2) No need to change it in case of Active Directory integration with password expiration.

## Usage

0) Read requirements above ;)

1) Copy artifacts to the directory where this git repository is cloned.

2) Modify `publish.sh` with your new Maven artifacts using one or more calls to the functions below.

```

publish_internal_artifact     []

publish_3rdparty_artifact    []

```

3) Run script: `./publish.sh`.

### Configuration

Default tool configuration uses the following Maven repository names:

**Internal company components:**

Components in this repository should all use [semantic versioning](https://semver.org/) so your pipelines can take advantage of dynamic dependency management in a continues delivery flow.

Maven repository: `maven-release-local`

**3rd party components:**

Components in this repository will have many different version formats and therefore you cannot use dynamic dependency management.

Maven repository: `maven-3rdparty-local`