Add parameter service job id

[phelipealves]

This addition fix the confirmation of coveralls_parallel build. The environment variable _CIRCLE_WORKFLOWID is used to identify the coveralls job and confirm that the parallel task has completed.

[nickmerwin]

Hi @phelipealves, thank you for the PR -- could you provide a use case description for this addition with links to a build on Circle using it, please?

[phelipealves]

Hi @nickmerwin, this build is made for an enterprise software from ESCALE.

This addition is used to confirm the parallel build. In our CI workflow, the coverage result will be sent to coveralls only when the code is in the master branch (staging environment). However, in pull requests or in another branch only coveralls jobs will be executed, without confirm.

• In this addition, the coveralls build number is the CIRCLE_WORKFLOW_ID value, now called job_id. We used this variable because the coverage confirmation is performed in another circleci job and, in the last implementation, the CIRCLE_BUILD_NUM number was not the same. Thus, coveralls confirmation would not be possible.
• Lastly, the token is a environment variable and needs of dollar sign $ to be accessed by SO.

This is a copy of our CircleCI configuration file: https://gist.github.com/phelipealves/ee66988027d2799a7e3694396de80fb1#file-config-yml-L165-L184

• CircleCI buid of workflow 70427D0F-D52D-4C89-A414-0ABE964BA846: https://i.ibb.co/RBHh6DV/Screenshot-from-2019-12-26-08-54-29.png.
  1. In the staging workflow, first build-and-test
  2. After that, coverage-done
  3. As we can see, in another workflows the coveralls is only executed in build-and-test creating a coveralls job.
• CircleCI step (coverage-done):
  1. Load variables: https://i.ibb.co/sFvLPfn/Screenshot-from-2019-12-26-08-17-24.png
  2. Send coverage done: https://i.ibb.co/VBfRJ0y/Screenshot-from-2019-12-26-08-17-38.png
• Coveralls results of https://coveralls.io/github/escaletech/health-broker: https://i.ibb.co/zxm6f2r/Screenshot-from-2019-12-26-08-15-41.png

[phelipealves]

Hi @nickmerwin, was added the case description in the last message :)

[nickmerwin]

Hi @phelipealves, we've released a new version of node-coveralls that includes better handling of Circle's parallelism, and new version of the Orb that utilizes it.

We're using CIRCLE_WORKFLOW_ID now as the Build Number that Coveralls will use to merge parallel job coverage.

Thank you again for the PR, and please confirm the new code solves your use-case when you have a chance.

Thanks!