Skip to content

Provide a composite action for setting up qnx sdp usage#2

Open
MTomBosch wants to merge 14 commits intoeclipse-score:mainfrom
MTomBosch:feature/setup-qnx-contribution
Open

Provide a composite action for setting up qnx sdp usage#2
MTomBosch wants to merge 14 commits intoeclipse-score:mainfrom
MTomBosch:feature/setup-qnx-contribution

Conversation

@MTomBosch
Copy link
Copy Markdown

@MTomBosch MTomBosch commented May 8, 2026

This pull request introduces a new composite GitHub Action, setup-qnx-sdp, to simplify and standardize the setup of the QNX Software Development Platform (SDP) in CI workflows. The action manages QNX license files, configures license server access, checks availability of qnx.com portal related credential helper, and ensures secure access to qnx.com.

This was tested by putting it into the qnx-build-yml resuable workflow (eclipse-score/cicd-workflows#107) and then running it on a company internal repository.

@AlexanderLanin
Copy link
Copy Markdown
Member

We should convert this to JS/TS with a proper post step.

Comment thread setup-qnx-sdp/action.yml
qnx-credential-helper:
description: Workspace root relative or absolute path to the QNX credential helper script that allows Bazel to access qnx.com with the provided credentials (qnx-user and qnx-password). If path is given but file does not exist an error will be raised. If an empty string is given no check will be performed. If file exists it is set to be executable. Finally a GITHUB_ENV var QNX_CREDENTIAL_HELPER is set with the absolute path to the credential helper script.
required: false
default: .github/tools/qnx_credential_helper.py
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to get rid of this local file. Maybe we can simply move it to qnx toolchain? So the toolchain itself behaves the same locally and on CI. Although currently the toolchain states, that SDP is out of scope and the user is responsible. As there are hundreds of ways to get the SDP. By that logic CI is responsible, and it should not be a local script.

No good idea at the moment.

I guess we have:

  • CI: currently uses qnx.com download until we can figure out local storage. Which we hopefully will in the next days to come.
  • S-CORE developer: will still download individually from qnx.com
  • End-Users / internal development based on S-CORE: will have their own internal SDP storage, as they cannot use the one from S-CORE

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants