You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@skywalking.apache.org by GitBox <gi...@apache.org> on 2021/10/29 01:37:05 UTC

[GitHub] [skywalking-infra-e2e] kezhenxu94 edited a comment on pull request #62: Support save pod/container std log on the Environment

kezhenxu94 edited a comment on pull request #62:
URL: https://github.com/apache/skywalking-infra-e2e/pull/62#issuecomment-954340984


   > I hope to solve the problem by creating multiple directories by obtaining `job.name`, but I only found a solution [through API](https://docs.github.com/en/rest/reference/actions#workflow-jobs). Is anyone have another good idea?
   
   1. `job.name` doesn't distinguish the jobs spawned from a matrix, unless the `jobs.name` itself contains the matrix name, this is not the case always.
   2. [the API](https://docs.github.com/en/rest/reference/actions#workflow-jobs) doesn't allow you to get the job id/name spawned from a matrix, also, it requires you to pass a `job_id`, if you already have the job id, you don't need this API to get id.
   
   Actually when I was optimizing the main repo I've tried a lot to distinguish the jobs spawned from matrix but failed to find a solution, if you find out one please let me know.
   
   Currently the only way I can think of is to expose the log directory to users so that they can compose it via matrix name. e.g.
   
   ```yaml
       - name: Run E2E Test
         uses: apache/skywalking-infra-e2e@main
         with:
           e2e-file: $GITHUB_WORKSPACE/test/e2e-v2/cases/${{ inputs.config-file }}
           log-dir: skywalking-test-storage-${{ matrix.storage }}
   ```


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@skywalking.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org