Trigger platform-pipeline build after successful execution

[stellarspot]

The fix allows to trigger the platform-pipeline after the current build successful execution.

It requires that in the CircleCI dashboard:

1. A token with name CIRCLECI_PLATFORM_PIPELINE_TOKEN is created
   Workflows -> platform-pipeline -> Settings -> API Permissions with necessary permissions.
2. The CIRCLECI_PLATFORM_PIPELINE_TOKEN env variable is added to the snet-daemon
   Workflows -> snet-daemon-> Settings ->Environment Variables

[amebel]

why would one need to trigger a build on master in another repo for pull-requests?

[stellarspot]

singnet/platform-pipeline projet is used for integration testing. It clones all necessary repositories from master and run the integration test. See pull request which is currently on the review: singnet/platform-pipeline#4 The integration test allows to check that nothing is broken when one module interacts with others.

[amebel]

Because the changes made by the pull-request are not merged, when the integration test is triggered, basically the triggered test is run without the changes introduced by the pr. As I understand it this is what is happening

1. test pull-request changes -> trigger test on platform-pipeline using master and without changes included in the pull-request, basically a rerun of the tests.
2. merge pull-request on pass of pull-request-change -> trigger test on platform-pipeline using newly introduced changes to master.

[stellarspot]

Thank you. I see now. I updated the fix to trigger the platform-pipeline integration test only if the there is a merge into the master branch (case 2).

[amebel]

Thanks! I have added the environment variables.