FutoIn Continuous Integration & Delivery Tool
Project description
Intro
There are many continuous integration & delivery tools, but they are primarily targeted at own infrastructure. The demand for a new meta-tool is to merge many operations of different technologies like npm, composer, bundler, nvm, rvm, php-build and others under a single tool for runtime setup, project development, build, deployment and running.
NOTE: current focus is on web projects, but support of other types is a far target.
Full theoretical details are defined as FutoIn Spec FTN16 available at: https://github.com/futoin/specs/blob/master/draft/ftn16_cid_tool.md
Supported technologies & tools (so far):
cmake (uses make in proper order)
- docker (experimental)
docker-compose
- java
java for runtime (uses system packages)
jdk for development (uses system packages)
sdkman for SDK management (besides JRE & JDK)
ant
gradle
maven
make
- node
npm
bower
grunt
gulp
nvm (implicit)
- php - both system & any php-build supported
composer
php-build (implicit)
- python - system 2 & 3
virtualenv, venv is ignored due to issues with ensurepip package
pip
- ruby - both system & any rvm supported
gen
bundler
rvm (implicit)
- scala
sbt - Simple Build Tools for Scala
scp - for RMS
Tested on the following OSes:
- ArchLinux
latest
- CentOS
7 with EPEL repository enabled
- Debian
8 - Jessie
9 - Stretch
- Fedora
25
- Gentoo
Well… CID does support emerge, but you are on your own here ;)
- OpenSUSE
42.1 Leap
- Ubuntu
14.04 LTS - Trusty
16.04 LTS - Xenial
16.10 - Yakkety
- Other Linux
it should work without issues, if system packages are installed manually
Setup
cid is written in commonly available Python language supporting both Python versions 2.7 and 3+.
Run the following:
pip install futoin-cid
If pip is not available then it’s strongly suggested to install one first:
easy_install pip
To allow cid automatically install system packages, please allow execution of apt-get, dnf, zypper or yum in sudoers. Example:
username ALL=(ALL) NOPASSWD: /usr/bin/apt-get install username ALL=(ALL) NOPASSWD: /usr/bin/apt-get install * username ALL=(ALL) NOPASSWD: /usr/bin/dnf install username ALL=(ALL) NOPASSWD: /usr/bin/dnf install * username ALL=(ALL) NOPASSWD: /usr/bin/emerge username ALL=(ALL) NOPASSWD: /usr/bin/emerge * username ALL=(ALL) NOPASSWD: /usr/bin/pacman username ALL=(ALL) NOPASSWD: /usr/bin/pacman * username ALL=(ALL) NOPASSWD: /usr/bin/zypper install username ALL=(ALL) NOPASSWD: /usr/bin/zypper install * username ALL=(ALL) NOPASSWD: /usr/bin/yum install username ALL=(ALL) NOPASSWD: /usr/bin/yum install *
Note: there are duplications with asterisk as some OSes have patched sudo
Usage
Please see details in the FTN16 spec:
cid tag <branch> [<next_version>] [--vcsRepo vcs_url] [--wcDir wc_dir] Get the latest <branch>. Update source for release & commit. Create tag. If <next_version> is omitted, the smallest version part is incremented. Current version is determined by tools (e.g. from package.json) cid prepare [<vcs_ref>] [--vcsRepo vcs_url] [--wcDir wc_dir] Retrieved the specific <vcs_ref>, if provided. --vcsRepo is required, if not in VCS working copy. Action depends on detected tools: * should clean up the project * should retrieve external dependencies cid build Action depends on detected tools. Runs tool-specific build/compilation. cid package Action depends on detected tools. Runs tool-specific package. If package is not found then config.package folder is put into archive - by default it's '.' relative to project root. cid check [--permissive] Action depends on detected tools. Runs tool-specific test/validation. cid promote <package> <rms_pool> [--rmsRepo rms_url] [--rmsHash type_value] Promote package to Release Management System (RMS) or manage package across RMS pools. cid deploy vcstag [<vcs_ref>] [--vcsRepo vcs_url] [--redeploy] [--deployDir deploy_dir] Deploy from VCS tag. cid deploy vcsref <vcs_ref> [--vcsRepo vcs_url] [--redeploy] [--deployDir deploy_dir] Deploy from VCS branch. cid deploy [rms] <rms_pool> [<package>] [--rmsRepo rms_url] [--rmsHash type_value] [--redeploy] [--deployDir deploy_dir] [--build] Deploy from RMS. cid run [<command>] Not implemented yet. cid ci_build <vcs_ref> <rms_pool> [--vcsRepo vcs_url] [--rmsRepo rms_url] [--permissive] Run prepare, build and package in one run. cid tool exec <tool_name> [-- <tool_arg>...] Execute <tool_name> binary with provided arguments. Tool and all its dependencies are automatically installed. Note: not all tools support execution. cid tool (install|uninstall|update) [<tool_name>] Manage tools. Note: not all tools support all kinds of actions. cid tool test [<tool_name>] Test if tool is installed. cid tool env [<tool_name>] Dump tool-specific environment variables to be set in shell for execution without CID. Tool and all its dependencies are automatically installed. cid tool (prepare|build|check|package|migrate) <tool_name> Run standard actions described above only for specific tool. Tool and all its dependencies are automatically installed. Note: auto-detection is skipped and tool is always run. cid tool list Show a list of supported tools. cid tool describe <tool_name> Show tool's detailed description.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for futoin_cid-0.4.2-py2.py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | eebb4efb0add35d8c2fa65a93cd5de6628d49dc421931c430055f494223a5bd7 |
|
MD5 | a884dee52a10173f69a276b0e56b5bcb |
|
BLAKE2b-256 | 874bcd0920ab6648c8c6cd7fc083b9cd8fc01a8adb7eb0015e086538646a8dc8 |