Skip to main content

Pentaho+ documentation has moved!

The new product documentation portal is here. Check it out now at docs.hitachivantara.com. 

 
Hitachi Vantara Lumada and Pentaho Documentation

Publish the product releases to the Global Artifactory

  1. Last updated
  2. Save as PDF

This section describes the process followed by the DevOps team for publishing the product releases into the Global Artifactory.

NoteWhen preparing to onboard your product to the marketplace, click Contact Support to establish a communication channel with the DevOps team.

The DevOps team is responsible for the Artifactory configuration, product build, release process, and any product-related DevOps activities.

The product releases are published in the Hitachi Marketplace Artifactory using continuous integration and continuous delivery (CI/CD) automation.

  • If your product team already has integrated such automation into the CI/CD pipeline, get help from the DevOps team with the configurations necessary for uploading the product releases to the repository.
  • If your product team does not know to develop or adapt their own CI/CD pipelines to integrate Global Artifactory publication, work with the DevOps team to create a custom process for uploading the product releases into the repository.
Parent Topic
Child Topics

Standard CI/CD-ready configuration

The standard configuration for uploading your product release to the Artifactory repository includes:

  • A set of development and release repositories for the binary packages of your application, such as Maven or Docker.
  • A service access token for pushing and pulling packages through the Artifactory repository.
NoteFor security and repeatability purposes, your enterprise software builds must not resolve third-party artifacts from the public repositories. The third-party remote repositories for Maven central, Docker.io, and Node.js are pre-configured, so you can resolve the third-party open-source software (OSS) package through the system. Contact the DevOps team to set up the necessary configurations to pull packages from the public repositories.
Parent Topic

Continuous release CI/CD automation workflow

The DevOps team uses the CI/CD automation workflow to:

  • Configure the CI/CD process to resolve Maven, Docker, or other artifacts used in your product build binaries using the Artifactory repository server.
  • Ensure that the CI/CD process deploys all the build binaries in your product development repositories. You can use the JFrog CLI tool with the manifest file that is used to create the Artifactory BuildInfo metadata.
  • Use build metadata to promote your product binaries from the development repositories to the release repositories and define the release bundles.
JFrog repository
Parent Topic

Custom release

The custom release includes automated or manual Artifactory publications that do not have the CI/CD automation workflow. The DevOps team can use the Artifactory CLI tool to generate the build information and support the creation and deployment of the release bundles.

Parent Topic