jfrog-project-onboarding

JFrog Project Onboarding (Master Orchestration)

This is the entry-point skill for onboarding GitHub projects to the JFrog Platform.

Prerequisites Check

Before starting, complete JFrog CLI setup and verify all prerequisites. If any check fails, abort immediately -- do not proceed with any onboarding steps. Report which check(s) failed and guide the user to fix them.

Step 1: JFrog CLI, jf config, confirm platform, readiness

1. Follow ../../../platform-features/skills/jfrog-cli/login-flow.md (JFrog CLI 2.100.0+, jf config show, user confirms URL, jf api /artifactory/api/v1/system/readiness).
2. Prefer jf api for all JFrog REST calls per ../../../platform-features/skills/jfrog-cli/jf-api-patterns.md. Use --server-id when multiple servers exist.
3. Optional: For manifest URL comparison, derive JFROG_URL from jf config show or keep .env in sync; see auth.md for curl fallback when the CLI is unavailable.

Step 2a: Validate token authentication (run with required_permissions: ["full_network"])

Verify credentials work (capture body + status; never pipe straight to jq):

BODY=/tmp/jf-onb-version.json
CODE=/tmp/jf-onb-version.code
jf api /artifactory/api/system/version >"$BODY" 2>"$CODE"
HTTP_CODE=$(tr -d '\r\n' < "$CODE")

if [ "$HTTP_CODE" = "200" ]; then
  echo "OK: Token authentication successful"
else
  echo "FAIL: Token authentication failed (HTTP $HTTP_CODE)"
  exit 1
fi

Fallback: curl -s -o /dev/null -w "%{http_code}" -H "Authorization: Bearer $JFROG_ACCESS_TOKEN" "$JFROG_URL/artifactory/api/system/version"

Step 2b: Validate platform admin privileges (MANDATORY -- run with required_permissions: ["full_network"])

Verify platform admin privileges. If this check fails, abort immediately -- do not proceed with any onboarding steps.