Skip to content

Latest commit

 

History

History
66 lines (45 loc) · 2.03 KB

File metadata and controls

66 lines (45 loc) · 2.03 KB

JFrog Pipelines Template - Java CI

This template simplifies CI pipeline for any Java package


Features


Pipelines

  • One pipeline for deleting different types of artifacts except Docker type for given repos
  • One dedicated pipeline to delete Docker artifacts

Pre-requisites

  • A Jfrog Platform Access token needs to be created with privileges to delete artifacts from target repositories.

Parameters (same for both the pipelines)

timeUnit

  • values: ['year', 'month', 'day', 'hour', 'minute']
  • default: 'month'
  • description: The unit of the time interval. year, month, day, hour or minute are allowed values. Default month.

timeInterval

  • default: 1
  • description: The time interval to look back before deleting an artifact.

searchOn:

  • values: ['last_downloaded', 'created']
  • default: 'last_downloaded'
  • description: Parameter to choose the search condition. Defaults to search artifacts last downloaded before selected time.

repos:

  • default: ''
  • description: A list of repositories to clean. This parameter is required. Default override allowed from values.yml.

dryRun:

  • default: 'true'
  • values: ['true', 'false']
  • description: If this parameter is passed, artifacts will not actually be deleted. Default false. Default override allowed from values.yml.

paceTimeMS:

  • default: 1000
  • description: The number of milliseconds to delay between delete operations. Default override allowed from values.yml.

maxRepos:

  • default: 10
  • description: Maximum allowed repos to search. Default override allowed from values.yml.

maxArtifacts:

  • default: 100
  • description: Maximum allowed artifacts to be deleted. Default override allowed from values.yml.

Execution Options

  • Manual Trigger
    • Trigger from JFrog Pipelines screen with default values
    • Change the parameters in environment variables section and trigger
  • Scheduled Trigger
    • Enable cron with correct expression in values.yml. Push the changes to Git source.
    • A new Cron resource will be created and will trigger the pipeline as per the Cron expression.