Skip to content

Latest commit

 

History

History
114 lines (86 loc) · 3.94 KB

managed-files.md

File metadata and controls

114 lines (86 loc) · 3.94 KB
Raw

ManagedFiles

The pipeline library supports the loading of Jenkins managed files references from json files by using the Pipeline Utility Steps Plugin

These references can be used to auto lookup ManageFile ids based on patterns. This can be useful to provide maven settings based on the scm url.

Based on the rules for writing libraries these json files must be places below the resources folder.

💡 The library only works with references/ids so your config files remain safe in the Jenkins instance.

💡 See also execMaven step

💡 See Extending with Shared Libraries for more information

Table of contents

JSON Format

In order to parse the files correctly they must be in the following format:

[
  {
    "pattern": "git\.yourcompany\.tld\/group1\/project1",
    "id": "group1-project1-managed-file",
    "name": "Local maven settings group1/project1",
    "comment": "Deploy maven setttings for project1 from group1 for nexus.yourcompany.tld"
  },
  {
      "pattern": "github\.com\/wcm-io",
      "id": "wcm-io-maven-global-settings",
      "name": "global maven settings wcm-io",
      "comment": "Global maven settings to build wcm-io projects"
  }
]

The properties pattern and id are mandatory, the comment and name properties are optional and can be omitted.

Using managed files

In order to use managed files inside your pipeline script you have to

  • load
  • parse and
  • search for a managed file based on a pattern

💡 The pattern is treated as regular expression

The Example is based on the execMaven step. This step loads a json and matches the incoming scm url against the entries to find matching settings ids to provide for the maven shell call.

import io.wcm.devops.jenkins.pipeline.managedfiles.ManagedFile 

ManagedFile autoLookupMavenSettings(String jsonPath, String scmUrl) {
    // load and parse the json
    JsonLibraryResource jsonLibraryResource = new JsonLibraryResource(steps, jsonPath)
    JSON managedFilesJson = jsonLibraryResource.load()
    ManagedFileParser parser = new ManagedFileParser()
    List<PatternMatchable> managedFiles = parser.parse(managedFilesJson)
    
    // match the scmUrl against the parsed mangedFiles and get the best match
    PatternMatcher matcher = new PatternMatcher()
    return (ManagedFile) matcher.getBestMatch(scmUrl, managedFiles)
}

void getGlobalMavenSettings() {
    ManagedFile managedFile = autoLookupMavenSettings('resources/managedfiles/maven/global-settings.json', 'git@git.yourcompany.tld:group1/project1')
    echo "Managed file id: '${managedFile.id}'" 
}

The result in this example would be a output in the log like:

Managed file id: 'group1-project1-managed-file'

💡 Refer to PatternMatching for more information on how the getBestMatch algorithm works

Step examples

configFileProvider

// load and parse the json
JsonLibraryResource jsonLibraryResource = new JsonLibraryResource(steps, 'resources/path/to/config.json')
JSON managedFilesJson = jsonLibraryResource.load()

ManagedFileParser parser = new ManagedFileParser()
List<PatternMatchable> managedFiles = parser.parse(managedFilesJson)

// match the scmUrl against the parsed mangedFiles and get the best match
PatternMatcher matcher = new PatternMatcher()
ManagedFile managedFile = matcher.getBestMatch('git@git.yourcompany.tld:group1/project1', managedFiles)

List configFiles = []
if (managedFile) {
    configFiles.push(configFile(fileId: managedFile.getId(), targetLocation: "", variable: 'MY_VARIABLE'))
}

configFileProvider(configFiles) {
    // some block
}