Overview

Opencog components dependency graph:

source code

Integration CircleCI job

CircleCI integration job is aimed to test all OpenCog related repositories front-to-back using set of repos and branches. Thus it can be used to build singnet fork or opencog fork or get part of repos from singnet and part from user's own forks.

Job starts from building docker containers and publishing them into private DockerHub repo. Then it uses fresh containers to build and test all components in a way similar to cogutil CircleCI workflow. Green status means that one can use provided set of branches to build and run all OpenCog tests from the scratch.

Restrictions

Only single workflow instance can be running at the same time.

Because of CircleCI API restrictions workflow cannot be started via API with parameters passed. It is workarounded by setting build properties before build started. It may mean that one cannot run few builds in parallel with different parameters, though I am not sure about it.

More serious restriction is using private DockerHub to keep fresh docker images. Right now workflow uses hardcoded tags to push images. This means that two jobs in parallel will push two images using same tag and finally will use the same docker image.

CircleCI job used is private CircleCI job

Before making this infrastructure publically available few things should be addressed (see below).

Merging script

Merge opencog to singnet

Script automatically merges opencog repos to singnet forks.

In empty directory execute:

python merge-opencog-to-singnet.py \
	--github-token <github-token> \
	--circleci-token <circleci-token> \
	--action merge

This command clones all forked singnet repos, creates new branches, merges latest opencog code to them. In case of merge conflict in some repo script stops. User should resolve conflict and make merge commit for the repo. Then script can be started again. It continues merging from next repo. After doing merge script pushes branches into user's github repo forks, starts CI on the set of branches and stops.

By default all singnet forks are considered, in order to use only some of them one can use the --forks options and provide a comma separated list of repository names, such as --forks cogutil,atomspace. The --forks option can be used across all actions, not just merge.

User should check CI status manually and execute:

python merge-opencog-to-singnet.py \
	--github-token <github-token> \
	--circleci-token <circleci-token> \
	--action pr

This command raises PRs from merge branches to the singnet repos.

After merging PRs new repo state can be released using release command. Before releasing and publishing dockers user should be logged to the dockerhub using:

docker login -u <dockerhub-username>

After this one can release using:

python merge-opencog-to-singnet.py \
	--github-token <github-token> \
	--action release

By default release tags merge results using release-YYYYMMDD tag and publish dockers with this tag. Tag can be changed using --tag parameter.

Run CI

One can use --action ci to run Circle CI integration job. This action has two parameters --ci-fork to set fork which should be used, and --ci-branch to set name of the branch. For example to rerun CI after merge one can execute:

python merge-opencog-to-singnet.py \
	--github-token <github-token> \
	--circleci-token <circleci-token> \
	--action ci \
	--ci-fork singnet \
	--ci-branch master

Cleanup

Following command removes all merge branches from local and remote repositories:

python merge-opencog-to-singnet.py \
	--github-token <github-token> \
	--circleci-token <circleci-token> \
	--action clean

Github API token

Github token is used to:

• read public repositories;
• create forks to keep new branches;
• push merge results;
• raise PRs.

You can create one using your Github account. Use Settings/Developer settings/Personal access tokens menu. Press Generate New Token button. Set following permissions:

• repo/public_repo
• admin:org/read Generate new token.

CircleCI token

Is required to configure and start CircleCI integration build.

To generate new token:

• open CircleCI app
• open User settings/Personal API Tokens
• press Generate New Token
• enter token name
• press Add API Token Copy generated token.

Items to address

TODO:

• find a way to start integration build passing list of branches and repos using CircleCI API
• find a way to run several integration builds simultaneously if required
• add a check to not try raising PRs which are already raised
• how to add privileges for adding new ref to repo (tag for instance)
• create repository for integration CircleCI and merge script and move code there
• add singularitynet private dockerhub repos to keep intermediate dockers for integration build
• create dockerhub user which has permissions to write in intermediate docker repos
• create CircleCI user which has permissions to start builds for all singnet fork repos