[ 
https://issues.apache.org/jira/browse/SPARK-58983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated SPARK-58983:
-----------------------------------
    Labels: pull-request-available  (was: )

> [spark-connect-rust] CI workflows fail to start: replace non-allowlisted 
> GitHub Actions
> ---------------------------------------------------------------------------------------
>
>                 Key: SPARK-58983
>                 URL: https://issues.apache.org/jira/browse/SPARK-58983
>             Project: Spark
>          Issue Type: Bug
>          Components: Project Infra
>    Affects Versions: 5.0.0
>            Reporter: Hyukjin Kwon
>            Priority: Major
>              Labels: pull-request-available
>
> All GitHub Actions workflows on apache/spark-connect-rust fail with 
> "startup_failure"
> ("This run likely failed because of a workflow file issue") on pushes to 
> master and on
> pull requests, so there is effectively no CI.
> Root cause: the workflows use third-party GitHub Actions that are not on the 
> ASF Actions
> allowlist (the ASF org restricts Actions to actions/* plus a vetted 
> allowlist), so the
> runs fail to start:
> - actions-rust-lang/setup-rust-toolchain (rust.yml, lint.yml, 
> build_python_connect.yml)
> - dtolnay/rust-toolchain, arduino/setup-protoc, PyO3/maturin-action,
>   pypa/gh-action-pypi-publish (release.yml)
> Fix: replace all non-allowlisted actions with GitHub-authored actions 
> (actions/checkout,
> actions/setup-python, actions/setup-java, actions/cache, 
> actions/upload-artifact,
> actions/download-artifact) plus shell steps (rustup for the toolchain, 
> apt/brew/choco for
> protoc, pip for maturin/twine). Also fix a pre-existing bug in 
> build_python_connect.yml's
> rust-checks job, which ran `cargo test -p spark-connect -p 
> spark-connect-core` using the
> old crate names (renamed to apache-spark-connect / apache-spark-connect-core).



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to