CloudDefense.AI
  • Connect Repositories
    • Scan a Github/Gitlab
    • Scan an Azure DevOps repository
    • Scan a Bitbucket repository
  • Scans
    • Written code Scan (SAST)
    • Open Source Libraries Scan (SCA)
    • Secrets Scan
    • DAST Scans
    • API Scan from CloudDefense UI
  • CI/CD
    • GitHub Enterprise Actions
    • Methods for CI/CD integration with CLI
    • CI/CD Policies
    • Jenkins integration with cdefence
  • Integration
    • IaC on GCR Scan
    • IaC on Amazon ECR Scan
    • IaC on Docker Hub Scan
    • Integration with ServiceNow
    • Integration with Jira
    • SSO Okta App Integration
    • Set up CloudDefense Single Sign-On (SSO)
    • SIEM
      • Azure Sentinel
      • IBM Qradar
      • Micro Focus ArcSight Logger
  • Features
    • Sharing Integration
    • How to Enable Multi-Factor Authentication
    • AUTO PR
    • Remediation using SAST Recommendations
    • Global Allowed List and Local allowed list - Documentation
    • File Exclude
  • CloudDefense CLI
    • Cloud Defense CLI
  • On-Prem Installation
    • Install CloudDefense Helm on a Kubernetes Cluster
    • Install CloudDefense suite on a Kubernetes cluster
  • Others
    • Team Management
    • User Management
    • App Management
    • LogIn/Signup process
Powered by GitBook
On this page
  • Step 1: Setting up runners
  • Step:2 Adding Repo secrets
  • Step 3: Adding our actions.yml
  1. CI/CD

GitHub Enterprise Actions

PreviousAPI Scan from CloudDefense UINextMethods for CI/CD integration with CLI

Last updated 2 years ago

Step 1: Setting up runners

GitHub enterprise needs “self-hosted” runners to support action system calls if needed. For our actions, we need to host a Linux VM that we listen to for the jobs. To do so we need to follow these steps

  • Go to settings -> Runners

  • Click on add runner and follow the setups to connect your Linux VM with Github

We use these above commands in our vm like:

Note: Make sure you mkdir the same as the repo name on your GitHub. For example, here we made “ObjcTest” which is the repo name

Check runner if connection “Idle” is available

Step:2 Adding Repo secrets

  • To add secrets (API-KEY). Settings -> Secrets -> New Repository Secrets

  • For our use case we will name the secret as API_KEY

Step 3: Adding our actions.yml

  • Now add our action.yml. In order to do that, make a folder structure like .github -> workflows -> action.yml, On the repo

  • Make sure that at line 18 of action.yml we have the same APP_NAME as that of the repo name

  • Commit and see the action run

  • Once the action is done. Check our UI for the results

\