Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting 404 while uploading package to JFrog artifactory #75

Open
unixbps opened this issue Aug 1, 2022 · 1 comment
Open

Getting 404 while uploading package to JFrog artifactory #75

unixbps opened this issue Aug 1, 2022 · 1 comment
Labels
question Further information is requested

Comments

@unixbps
Copy link

unixbps commented Aug 1, 2022

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 unixbps added the question Further information is requested label Aug 1, 2022
@devoredevelops
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants