Skip to content

Update .strata.yml

0ff8b66
Select commit
Loading
Failed to load commit list.
Merged

fix: Update preprocessor tag for SFCI #5731

Update .strata.yml
0ff8b66
Select commit
Loading
Failed to load commit list.
SFCI-Gec-Github-App / continuous-integration/sfci/build failed Mar 4, 2026 in 1m 38s

Pipeline Completed

Build failed in step: oss-forked-pr-check

, Please refer below for the failed step log-lines and potential fix

Failed Step Logs(last 50-lines) Next Steps by Codegenie to fix
+ [2026-03-04T09:15:39-0800] if [[ -f "$FEATURE_ROLLOUT_RESULT_FILE" ]]; then
forked_repo_build_allowed=$(grep -zoP "allowFeatureToRun_oss-forked-pr-builds:\s*\K(true|false)" $FEATURE_ROLLOUT_RESULT_FILE || echo "false")
if [[ "$forked_repo_build_allowed" == "true" ]]; then
echo "forked_repo_build_allowed is true"
pip3 install PyGithub
python3 $OSS_INNERSOURCE_GATING_SCRIPT --check-oss-forked-pr
fi
fi
/usr/bin/cixrc: line 30: warning: command substitution: ignored null byte in input
forked_repo_build_allowed is true
Looking in indexes: https://nexus-proxy.repo.local.sfdc.net/nexus/repository/pypi-all/simple
Collecting PyGithub
Downloading https://nexus-proxy.repo.local.sfdc.net/nexus/repository/pypi-all/packages/pygithub/2.8.1/pygithub-2.8.1-py3-none-any.whl (432 kB)
Collecting typing-extensions>=4.5.0
Downloading https://nexus-proxy.repo.local.sfdc.net/nexus/repository/pypi-all/packages/typing-extensions/4.15.0/typing_extensions-4.15.0-py3-none-any.whl (44 kB)
Collecting pyjwt[crypto]>=2.4.0
Downloading https://nexus-proxy.repo.local.sfdc.net/nexus/repository/pypi-all/packages/pyjwt/2.11.0/pyjwt-2.11.0-py3-none-any.whl (28 kB)
Collecting pynacl>=1.4.0
Downloading https://nexus-proxy.repo.local.sfdc.net/nexus/repository/pypi-all/packages/pynacl/1.6.2/pynacl-1.6.2-cp38-abi3-manylinux_2_34_x86_64.whl (1.4 MB)
Requirement already satisfied: urllib3>=1.26.0 in /usr/lib/python3.9/site-packages (from PyGithub) (1.26.5)
Requirement already satisfied: requests>=2.14.0 in /usr/lib/python3.9/site-packages (from PyGithub) (2.25.1)
Requirement already satisfied: cryptography>=3.4.0 in /usr/lib64/python3.9/site-packages (from pyjwt[crypto]>=2.4.0->PyGithub) (36.0.1)
Collecting cffi>=2.0.0
Downloading https://nexus-proxy.repo.local.sfdc.net/nexus/repository/pypi-all/packages/cffi/2.0.0/cffi-2.0.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.whl (216 kB)
Requirement already satisfied: idna<3,>=2.5 in /usr/lib/python3.9/site-packages (from requests>=2.14.0->PyGithub) (2.10)
Requirement already satisfied: chardet<5,>=3.0.2 in /usr/lib/python3.9/site-packages (from requests>=2.14.0->PyGithub) (4.0.0)
Requirement already satisfied: pycparser in /usr/lib/python3.9/site-packages (from cffi>=2.0.0->pynacl>=1.4.0->PyGithub) (2.20)
Requirement already satisfied: ply==3.11 in /usr/lib/python3.9/site-packages (from pycparser->cffi>=2.0.0->pynacl>=1.4.0->PyGithub) (3.11)
Installing collected packages: cffi, pyjwt, typing-extensions, pynacl, PyGithub
Successfully installed PyGithub-2.8.1 cffi-2.0.0 pyjwt-2.11.0 pynacl-1.6.2 typing-extensions-4.15.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
Running enhanced gating for OSS forked repository PR...
Fork repository: SujithKandamuri
Build cause: RestartStageCause,UserIdCause
Automatic build detected from forked repository.
Build is blocked for security reasons. Please trigger a manual build to proceed.
To trigger a manual build, please contact the repository maintainers.

Please click here for complete failed step logs. Note: This link will expire once the SFCI build is deleted from the sfci-managed Jenkins UI.
Note: Next Steps by Codegenie is an experimental feature at this time and will improve over time.

The error indicates that the build is blocked due to security restrictions when automatically triggered from a forked repository. This is a common safeguard to prevent unauthorized or malicious changes from being executed in the CI pipeline.

Steps to Resolve:

  1. Trigger a Manual Build:

    • Contact the repository maintainers or the SFCI-Oncall team to manually trigger the build. This bypasses the automatic block for forked repositories.
  2. Update Repository Configuration:

    • If frequent builds from forked repositories are required, consider adding the forked repository to the exception list in the SFCI configuration file:
      • Submit a PR to the feature.yaml file in the SFCI feature rollout configuration.
      • Tag the SFCI-Oncall team to merge the PR.
      • Once merged, the SFCI-Oncall team will manually remove the GitHub-Age-ref plugin configuration from the Jenkins instance.
  3. Evaluate Repository Visibility:

    • If the parent repository is set to "Internal" or "Private," consider switching it to "Public" if security policies allow. This can simplify builds from forked repositories.
  4. Security Considerations:

    • Ensure that all security implications are evaluated before allowing builds from forked repositories. This includes reviewing the forked repository's code and contributors.

For more details, refer to the SFCI Managed FAQ [1][2].


Details

Job Details Pipeline Stages Artifacts
Stage Duration
โœ… Setup
0min 28s
๐Ÿ”ฒ Precheck
๐Ÿ”ฒ Invoke worker job
๐Ÿ”ฒ Build
๐Ÿ”ฒ Package
๐Ÿ”ฒ Integration test
๐Ÿ”ฒ Poll worker job
๐Ÿ”ฒ Publish
๐Ÿ”ฒ Post publish
โœ… Finally
0min 26s
โœ… Teardown
0min 23s