Skip to content

RTECO-1884 - Inconsistent inputs from github workflows for packages e2e tests - #3679

Open
naveenku-jfrog wants to merge 1 commit into
masterfrom
RTECO-1884-inconsistent-workflow-dispatch-inputs
Open

RTECO-1884 - Inconsistent inputs from github workflows for packages e2e tests#3679
naveenku-jfrog wants to merge 1 commit into
masterfrom
RTECO-1884-inconsistent-workflow-dispatch-inputs

Conversation

@naveenku-jfrog

Copy link
Copy Markdown
Collaborator

Summary

The jfrog_url / jfrog_admin_token workflow_dispatch inputs (plus jfrog_user/jfrog_password in apkTests.yml) exist in every package/Artifactory e2e workflow to let a manual run skip the local Artifactory install and point at an external JPD instead.

Investigation into the reported "unused inputs" showed the wiring itself was correct in every workflow (passed through to install-local-artifactory and referenced in the go test invocation) - but checking actual workflow_dispatch run history shows these inputs have never actually been supplied by anyone: jfrog_admin_token was blank on every inspected run, and every run always took the local-install branch. In practice this is dead capability across the whole package/Artifactory suite set.

This PR removes it:

  • Deletes the jfrog_url/jfrog_admin_token (jfrog_user/jfrog_password for apk) workflow_dispatch inputs from all 18 affected workflows.
  • Removes the JFROG_URL/JFROG_ADMIN_TOKEN passthrough to install-local-artifactory - every suite now always installs Artifactory locally, matching actual usage.
  • Removes the now-always-empty env.JFROG_TESTS_IS_EXTERNAL == 'true' && format(...) || '' conditional from the affected go test commands (conanTests, gradleTests, mavenTests, nixTests, npmTests, nugetTests, pluginsTests, pnpmTests, poetryTests, pythonTests, rubyTests, artifactoryTests's project-suite step, transferTests's Artifactory-6 job).
  • apkTests.yml: also removes the redundant duplicate inputs block (it declared the same inputs under both workflow_call and workflow_dispatch, unlike every other suite which only declares under workflow_dispatch), makes "Install local Artifactory" unconditional (was gated on inputs.jfrog_url == ''), and drops the dead creds shell logic in the test-run step.
  • poetryTests.yml keeps its unrelated poetry_version input untouched.
  • accessTests.yml, helmTests.yml, huggingfaceTests.yml, lifecycleTests.yml, and transferTests.yml's first job read env.JFROG_TESTS_URL/env.JFROG_TESTS_LOCAL_ACCESS_TOKEN (set by the action regardless of local/external mode), not inputs.* directly, so their go test lines are unchanged.

No behavioral change for the actual CI path: every suite already always installed Artifactory locally in every observed run; this just removes the unused override capability and the resulting dead conditionals.

Test plan

  • Validated all 18 changed workflow files parse as valid YAML
  • Confirmed no remaining references to jfrog_url/jfrog_admin_token/jfrog_user/jfrog_password/JFROG_TESTS_IS_EXTERNAL in the changed files
  • CI (build-gate suites) runs green on this PR

🤖 Generated with Claude Code

… package e2e workflows

The jfrog_url/jfrog_admin_token (and jfrog_user/jfrog_password in
apkTests.yml) workflow_dispatch inputs let a suite skip local Artifactory
install and point at an external JPD instead. Run history shows these were
never actually supplied on any manual dispatch, so every suite always
installed Artifactory locally in practice. Removing the dead inputs, their
passthrough to install-local-artifactory, and the now-always-empty
JFROG_TESTS_IS_EXTERNAL conditionals from the go test invocations.

apkTests.yml also had these inputs declared twice (workflow_call and
workflow_dispatch) while every other suite only declared them under
workflow_dispatch - both are removed for consistency.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

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.

1 participant