CI Tools and Frameworks

Continuous Integration
- For Analysis and Testing
  - For verification, notification and assembly
    - Using Git hooks
    - Using Github Actions
    - Implementing build tooling (e.g. Maven plugins, SetupTools, Make)
    - Using Checksum hashing
  - For credentialing
    - Implementing keystore Jenkins Credentials Binding Plugin
    - Using ssh
    - Using oauth
  - For executing and reporting tests
    - Using Jenkins plugins
    - Using TravisCI Build Addons
    - Using (Java) Maven plugins
    - Using (Python) SetupTools
    - Using (C#) NUnit
    - Using (C/C++) Make/Cmake
    - Using (Node.js) npm-test
    - Using (any) Testrail Connector
- For Compilation
  - For build integration and reporting
    - Using Jenkins
    - Using TravisCI
  - For dependency management and packaging
    - Using (Java) Maven
    - Using (Python) SetupTools/Pip
    - Using (C#) NuGet
    - Using (C/C++) Make/Cmake
    - Using (Node.js) npm
    - Using (any) Ant
- For Orchestration
  - For deploying services
    - Using workflows
      - Using Puppet
      - Using Ansible
      - Using Chef
    - Using scripts
      - Using Python
      - Implementing platform scripting [shell, Powershell]
  - For cloud or datacenter deployments
    - Using Terraform
    - Using Kubernetes
    - Using CloudFormation
    - Using SaltStack
- For Release Management
  - For packaging
    - Using Docker
    - Implementing archiving (tar, zip, gz)
    - Using RPM
    - Using JAR, WAR
  - For releasing software
    - Using Jenkins ()
    - Using TravisCI
    - Using Github Actions
  - For storing build artifacts
    - Using software repositories
      - Using Artifactory
      - Using Nexus
    - Using OSS repositories
      - Using (Java) Maven Central
      - Using (Python) PyPi
      - Using (C#) Nuget
      - Using (C/C++) yum, dnf
      - Using (Node.js) npm