Skip to content

Latest commit

 

History

History
76 lines (66 loc) · 3.28 KB

README.md

File metadata and controls

76 lines (66 loc) · 3.28 KB

Image

API Collection to CI

Overview

This project is a spin-off of this amazing Python Package find the parent repository here. This brilliant SDET Seyi 'nexus' Ajadi conceived the idea to ensure that engineers can focus on testing and creating collections while pipeline config will be handled via a simple Q&A. I merely expanded it to work on more pipelines.

postPipe removes the hassle of manually uploading Postman collections, whether they are from a UID or a saved file, into your CI/CD pipeline on GitHub, GitLab, or Bitbucket. It automates the process of exporting collections, setting up the required YAML pipeline, and making the initial commit, allowing you to focus on development rather than CI configuration.

Prerequisites

To use postPipe, you will need:

  • Postman API Key.
  • GitHub Setup: GitHub Personal Access Token
  • GitLab Setup: GitLab Personal Access Token
  • Bitbucket Setup: Bitbucket App Password

Retrieving Postman API KEY

  • Login to Postman Web or Desktop
  • Click on the desired collection
  • Click on Run
  • Check the Automate runs via CLI radio button
  • Click on Add API Key
  • Click Generate Key
  • Insert a name and click Generate
  • Copy the Postman API Key

Creating and Retrieving Tokens and App Password

GitHub

  • Login to GitHub
  • Click on your profile picture in the upper-right corner, then click Settings.
  • Scroll down and select Developer settings.
  • Click Personal access tokens on the left menu, then click classic tokens or fine grained tokens.
  • Click "Generate new token", name it, set the expiration(or create a never expiring one).
  • Select scopes (like repo and workPipe, you can select all(recommended)). Click Generate token and copy the token.
  • Save the token somewhere secure as once lost, it cannot be retrieved

GitLab

  • Login to GitLab
  • Click on your profile picture in the upper-left corner and select Edit profile or Preference.
  • Click Access tokens on the left side bar
  • Click on Add new token
  • Name it, set expiration, and check all boxes.
  • Save the token somewhere secure as once lost, it cannot be retrieved

Bitbucket

  • Login to Bitbucket
  • Click the Settings icon on the upper-right corner
  • Click Personal Bitbucket Settings
  • Click App passwords
  • Name and create an app password and check all boxes
  • Save the token somewhere secure as once lost, it cannot be retrieved

Environment Variables Setup

Windows

setx GITHUB_TOKEN "your_github_token"
setx POSTMAN_API_KEY "your_postman_api_key"

or

set GITHUB_TOKEN=<your_github_token>
set POSTMAN_API_KEY=<your_postman_api_key>

MacOS/Linux

export GITHUB_TOKEN="your_github_token"
export POSTMAN_API_KEY="your_postman_api_key"

Note

For GitLab and Bitbucket, replace GITHUB with GITLAB or BITBUCKET to have GITLAB_TOKEN or BITBUCKET_TOKEN

Usage

  • postPipe to run generally whereby the user can select from the three pipelines
  • postPipe --github to run a GitHub setup pipeline.
  • postPipe --gitlab to run a GitLab setup pipeline.
  • postPipe --bitbucket to run a Bitbucket setup pipeline.