Hello,
Please take look at the logical flow of my action:
jobs:
CreateModPackagesUploadToRelease:
runs-on: ubuntu-latest
steps:
- name: Clone repository
uses: actions/checkout@master
- name: Create package
id: CreatePackage
run: |
<custom code>
- name: Upload zip package to release
uses: svenstaro/upload-release-action@v1-release
with:
repo_token: ${{ secrets.GITHUB_TOKEN }}
file: ${{ steps.CreatePackage.outputs.PackageName }}
asset_name: ${{ steps.CreatePackage.outputs.PackageName }}
tag: ${{ github.ref }}
Notice the step: CreatePackage
This action creates test.zip file and variable PackageName is assigned to the filename via “##[set-output name=PackageName;]$($PackageName)”. So the next task (“Upload zip package to release”) can get this file from GitHub-hosted runner.
Question:
Is there a way to replace “CreatePackage” action via “Docker” action?
Does “Docker” actions can be chained like that? As a extra step?
If yes, then how to access container filesystem in order to get test.zip file path for “Upload zip package to release” task?