refactor: remove validation step and update FlyFrog URL in integration test workflow; enhance CI end notification details in README

Author: sverdlov93

.github/workflows/integration-test.yml

@@ -10,35 +10,13 @@ permissions:
 jobs:
   integration-test:
     runs-on: ubuntu-latest
-    # Only run if a valid FlyFrog test URL is configured
-    if: vars.FLYFROG_TEST_URL != ''
     steps:
       - name: Checkout repository
         uses: actions/checkout@v4
 
-      - name: Validate FlyFrog server endpoints
-        run: |
-          FLYFROG_URL="${{ vars.FLYFROG_TEST_URL || 'https://flyfrog.example.com' }}"
-          echo "Testing FlyFrog server at: $FLYFROG_URL"
-          
-          # Test if the server responds (basic connectivity check)
-          if ! curl -s --max-time 10 "$FLYFROG_URL" > /dev/null; then
-            echo "⚠️  Warning: FlyFrog server is not reachable"
-            echo "Integration test may fail due to server connectivity"
-          else
-            echo "✅ FlyFrog server is reachable"
-          fi
-
       - name: Run FlyFrog action
         id: run-action
         uses: ./
         with:
-          url: ${{ vars.FLYFROG_TEST_URL || 'https://flyfrog.example.com' }}
+          url: ${{ vars.FLYFROG_TEST_URL || 'https://ffjob1682705.jfrogdev.org' }}
           ignore: docker, podman
-
-      - name: Assert action completed successfully
-        run: |
-          echo "✅ FlyFrog action completed without errors"
-          echo "   - OIDC authentication succeeded"
-          echo "   - Package managers configured successfully"
-          echo "   - CI end notification completed"

README.md

@@ -62,7 +62,9 @@ When using OIDC authentication:
    - Request an OIDC token from GitHub Actions
    - Exchange it for a FlyFrog access token via the `/flyfrog/api/v1/ci/start-oidc` endpoint
    - Use the resulting token to authenticate with FlyFrog
-   - Notify CI session end via the `/flyfrog/api/v1/ci/end` endpoint on completion
+   - Automatically notify CI session end via the `/flyfrog/api/v1/ci/end` endpoint when the job completes (using GitHub Actions post-job mechanism)
+
+> **Note**: The CI end notification runs automatically after the main action completes, regardless of whether the main action succeeds or fails. This ensures proper cleanup and session management on the FlyFrog server.
 
 ### FlyFrog Server Configuration for OIDC