Implement repetitive build jobs in a central place

[kalinkrustev]

No description provided.

[kalinkrustev]

An example is the code added for publish-prerelease in mojaloop/central-services-stream#141, but also many other jobs in the same .circleci/config.yml file

[kalinkrustev]

@elnyry-sam-k , what do you think of the idea of having the build jobs in a central place?

I prepared a draft orb here #39, it is based on jobs taken from central-ledger with added one more job for publishing the pre-release branches.

Repos can start reusing the jobs gradually unless they need something specific.

[elnyry-sam-k]

DRY, lets do it!!

Thanks for this, @kalinkrustev

[kalinkrustev]

@elnyry-sam-k actually putting multiple orbs in one repo is not a good idea, as the automation that Circle CI provides for publishing orbs is not convenient for such case. Can I create a new repo for the build orb? Maybe mojaloop/orb-build ?

[elnyry-sam-k]

ok, is something like ci-config-orb-build ok?

[kalinkrustev]

Moved to mojaloop/ci-config-orb-build#1

@elnyry-sam-k, as per this permissions matrix, I think I will need the mojaloop github org owner to create the orb mojaloop/build or to set the CIRCLE_TOKEN in this context https://app.circleci.com/settings/organization/github/mojaloop/contexts/1d64c5ff-d141-4bc2-9ccb-4c4ae3169041, so that orbs can be published automatically.

Currently I can't publish even a dev release, as the orb mojaloop/build does not exist.

[elnyry-sam-k]

reached out on slack, lets sort it out