putting in a fake publish task and workflow to see if arm works #1
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: Temp Workflow to test a Fake Publish | |
on: | |
push: | |
branches: | |
- 'ewyles/pre-release-testing' | |
env: | |
UDS_CLI_VERSION: v0.11.0 | |
permissions: | |
contents: read | |
jobs: | |
fake-publish: | |
runs-on: ${{ matrix.architecture == 'arm64' && 'uds-ubuntu-arm64-4-core' || 'ubuntu-latest' }} | |
name: Temp - Fake Publish ${{ matrix.flavor }} ${{ matrix.architecture }} | |
strategy: | |
matrix: | |
flavor: [upstream, registry1] | |
architecture: [arm64] | |
exclude: | |
- flavor: registry1 | |
architecture: arm64 | |
permissions: | |
contents: read | |
packages: write | |
steps: | |
- uses: actions/checkout@a5ac7e51b41094c92402da3b24376905380afc29 # v4.1.6 | |
- name: Environment setup | |
# uses: defenseunicorns/uds-common/.github/actions/setup@11e591f2ec7d158923d973c85097ce28a5f55db4 # v0.4.5 | |
uses: defenseunicorns/uds-common/.github/actions/setup@ewyles/publish-arch | |
with: | |
registry1Username: ${{ secrets.IRON_BANK_ROBOT_USERNAME }} | |
registry1Password: ${{ secrets.IRON_BANK_ROBOT_PASSWORD }} | |
ghToken: ${{ secrets.GITHUB_TOKEN }} | |
- name: Publish Package | |
run: UDS_ARCHITECTURE=${{ matrix.architecture }} uds run -f tasks/fake-publish.yaml package --set FLAVOR=${{ matrix.flavor }} | |
- name: Save logs | |
if: always() | |
uses: defenseunicorns/uds-common/.github/actions/save-logs@11e591f2ec7d158923d973c85097ce28a5f55db4 # v0.4.5 | |
with: | |
suffix: ${{ matrix.flavor }}-${{ matrix.architecture }}-${{ github.run_id }}-${{ github.run_attempt }} |