Skip to content

Latest commit

 

History

History
 
 

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 

README.md

CICD - Upload Single API Proxy

| Recipes by Topic | Recipes by Author | Request Enhancement | Report a bug | Fix documentation |

Sunny Kapoor Sunny Kapoor

This CICD Jenkins job allows you to checkout the configured API Proxy from the source code repository and either update or create the artefact on the API Portal tenant.

Instructions to consume the CICD Jenkins file

Environment Variables List

Configure the following environment variables before executing the Jenkins Job

Name Example Description
APIProxyName "CICDAPIProxy" The name of the API Proxy that needs to be uploaded to the API Portal tenant
APIPortalHost "${env.API_HOST}"
"eu20apiportal.cfapps.eu20.hana.ondemand.com"
The hostname (without HTTPS) of your API Portal tenant
AuthType "OAuth"
"Basic"
The Authentication Type to be used to connect to the API Portal Tenant. Values can be "OAuth" or "Basic"
APIPortalBasicAuth "${env.API_BasicAuth_CRED}"
"API_BasicAuth_Credentials"
The alias of the Basic credentials for the API Portal tenant which is deployed on your build server (like Jenkins)
APIPortalOAuthCredentials ${env.API_OAUTH_CRED}"
"API_OAuth_Credentials"
The alias of the OAuth credentials for the API Portal tenant which is deployed on your build server (like Jenkins)
GITRepositoryURL "${env.GIT_REPOSITORY_URL}"
"github.com/CICD/integrations.git"
The full URL of the source code repository without HTTPS
GITCredentials "${env.GIT_CRED}"
"GIT_Credentials"
The alias of the source code repository credentials which is deployed on your build server (like Jenkins)
GITBranch "${env.GIT_BRANCH_NAME}"
"refs/heads/master"
Specify the source code repository branch that you want to work with
GITFolder "IntegrationContent/API" Specify the folder structure in your source code repository from where you like to read the API Proxy

Related Recipes

References