tencent cloud

title: Upload Generic Artifacts - CODING Help Center
pageTitle: Upload Generic Artifacts
pagePrevTitle: Team Template
pagePrev: ci/manage/team-template.html
pageNextTitle: Retrieve Entered Credentials
pageNext: ci/plugins/credentials.html
alias: devops/ci/plugins/generic.html

Feature Overview

In an actual production environment, many tasks are repetitive. CODING Continuous Integration (CODING-CI) features plugins that can help you handle tedious and repetitive tasks efficiently. You can also use custom parameters to address unique needs. More built-in plugins are coming soon. At the moment, you can use the following convenient plugin types in CODING-CI:

• Upload generic artifacts
• Retrieve uploaded credentials
• Automatically add reviewers in merge requests
• Manual confirmation

Use plugin to upload generic artifacts

In the process of building a CI task, you can choose to upload an artifact to the CODING Artifact Repository (CODING-AR). Generic artifacts upload plugin allows you to conveniently upload generic artifacts of up to 5 GB in Continuous Integration. Before using this function, ensure that you have a basic understanding of generic repositories. For more information, see Using Generic Repositories.

Getting Started

You can use a fixed template or a Jenkinsfile configuration to upload generic artifacts.

Fixed Template

1. Before using the plugin, make sure that you have created a generic repository. Take a test repository as an example below.

2. Click "New Build Plan" and select "Artifact Repository" > CODING Generic Artifact Upload.

3. Set the default value to "test" repository you have just created. You can also fill in your artifact repository URL in the code.

4. Select "Trigger build after creation" and click "OK" to run the build.

5. After the build is complete, the file uploaded beforer will appear in the artifact repository.

Jenkinsfile Configuration

1. When selecting a code repository, make sure the code repository contains a Jenkinsfile with the configuration below.

pipeline {
  agent any
  stages {
      stage('Upload to generic repository') {
          steps {
              // Use the fallocate command to create a file of 10 MB in size. (The default working directory in Continuous Integration is /root/workspace.)
              sh 'fallocate -l 10m my-generic-file'
               codingArtifactsGeneric(
                  files: 'my-generic-file',
                  repoName: 'myrepo', // Fill in your repository parameters here, for example, ${env.GENERIC_REPO_NAME}
              )
          }
      }
  }
}

2. In "Process Configuration", you can modify the Jenkinsfile configuration.

More examples of parameters

pipeline {
  agent any
  stages {
      stage('Upload to generic repository') {
          steps {
              // Use the fallocate command to create a file of 10 MB in size. (The default working directory in Continuous Integration is /root/workspace.)
              sh 'fallocate -l 10m my-generic-file'
               codingArtifactsGeneric(
                  files: 'my-generic-file',
                  repoName: 'myrepo',
              )
          }
      }
  }
}

Parameter Descriptions

==== 2020/08/24 ====