setup-jfrog-cli icon indicating copy to clipboard operation
setup-jfrog-cli copied to clipboard

Getting 404 while uploading package to JFrog artifactory

Open unixbps opened this issue 3 years ago • 2 comments

While uploading file to JFrog artifactory using Github Action we are getting 404. seems to it's appending "Build" metadata like "Build number, Build name " etc..

Here is the build log(uploading url): https://artifactory.xyz.com/ext-release-local/xyz-CCPX/demo.env;build.number=33;build.timestamp=1659113030285;vcs.revision=35fdebe46da530800c16b011e2aba1756c2d6d6f;vcs.url=https%3A%2F%2Fgithub.com%2Fxyz-prod%2FCentralised-Config-Files.git;vcs.branch=master;build.name=Upload+Config+files+to+Artifactory:

Here is the workflow

name: Upload Config files to Artifactory

on: push: branches: - master

workflow_dispatch:

jobs: publish: runs-on: [self-hosted, linux, X64] steps: - name: Checkout uses: actions/checkout@v3 - name: Setup Artifactory uses: jfrog/setup-jfrog-cli@v2 - name: Upload to Artifactory run: jf rt u --spec artifactory-spec.json --url 'https://artifactory.xyz.com' --user ${{ secrets.xyz_ARTIFACTORY_USER }} --password ${{ secrets.XYZ_ARTIFACTORY_PASS }}

Here is the spec file

{ "files": [ { "pattern": "configs/*.env", "target": "ext-release-local/xyz-CCPX/"
}, { "pattern": "configs-tf/tf-apply.sh", "target": "ext-release-local/xyz-CCPX/TF-CONFIG/"
} ] }

How can we skip the build metadata during upload, like "build number, buildname" etc..

unixbps avatar Aug 01 '22 07:08 unixbps

You may want to look into replacing uses: jfrog/setup-jfrog-cli@v2 with uses: jfrog/setup-jfrog-cli@v3.

devoredevelops avatar Jan 11 '23 20:01 devoredevelops