Skip to content

action-build is no longer interpreting environment variables #79

@Guillaumebeuzeboc

Description

@Guillaumebeuzeboc

The new release of action-build 1.3.0 appears to no longer import or use the environment variables of the GH step or job.

In my case:

    env:
      SNAPCRAFT_BUILDER_ID: ${{ github.run_id }}
    steps:
      [...]
      - uses: snapcore/action-build@v1
        env:
          SNAPCRAFT_REMOTE_BUILD_STRATEGY: force-fallback
        with:
          path: .
          snapcraft-args: "remote-build --launchpad-accept-public-upload --build-id ${{ matrix.snap_names }}-${{ SNAPCRAFT_BUILDER_ID }}"

to be interpreted as

/usr/bin/sudo -u runner -E snapcraft remote-build --launchpad-accept-public-upload --build-id noetic-desktop-amd64-${SNAPCRAFT_BUILDER_ID}

(SNAPCRAFT_BUILDER_ID is not interpreted)

Could be that this recent change induced the new behaviour

Our CI that was working fine before stopped working after this release.

Is it an intended behaviour?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions