OpenCPN/plugins

admiralty-tide-tables deployment fails 404 and code 148

rgleason opened this issue · 4 comments

rgleason commented

I've spent the morning trying to figure out these failures to push already built metadata and tarballs to
Cloudsmith using Cloudsmith CLI and the cloudsmith-upload.sh

Any suggestions would be appreciated. I've just added and built deviation_pi and that works!

https://github.com/rgleason/admiralty_tide_tables_pi

build-android-arm64 - Failed
Appveyor Failure https://ci.appveyor.com/project/rgleason/admiralty-tide-tables-pi/builds/47817621

Checking raw package upload parameters ... ERROR
Failed to validate upload parameters! (status: 404 - Not Found)
Detail: Not found.
Hint: This usually means the user/org is wrong or not visible.
Command exited with code 148

build-debian-x86_64-12-bookworm - Failed
https://app.circleci.com/pipelines/github/rgleason/admiralty_tide_tables_pi/4/workflows/b8c4a9cf-9587-467e-9379-57fd69f1111f/jobs/116

Checking raw package upload parameters ... ERROR
Failed to validate upload parameters! (status: 404 - Not Found)

Detail: Not found.
Hint: This usually means the user/org is wrong or not visible.

Exited with code exit status 148
rgleason commented

https://support.circleci.com/hc/en-us/articles/360060360811-CircleCI-API-v2-returns-404-Not-Found-

When sending requests to CircleCI API v2 endpoints, you might receive a 404 response. Depending on which endpoint you're using at the time you could get any of the following response:
{"message" : "Not Found"}
{"message" : "Pipeline not found"}
{"message" : "Project not found"}
{"message" : "Workflow not found"}

The response {"message" : "Not Found"} indicates that the URL path you specified is incorrect, specifically the endpoint path.

Depending on the endpoint, the responses {"message" : "Project not found"} , {"message" : "Pipeline not found"} or {"message" : "Workflow not found"} can happen when you're authenticating your API call using a project API token as opposed to a personal API token.

note: Please ensure that the user who created the personal API token has access to the repository.

Project tokens are currently not supported on API v2. Any token found under "Project Settings > API Permissions" is a project API token, regardless of the scope you assigned to it.
For any request made via CircleCI API v2 endpoints, make sure to use personal API tokens.

rgleason commented

Under Circleci [Plugin} SSH Keys Checkout SSH Keys

A deploy key is a repo-specific SSH key. GitHub has the public key, and we store the private key. The deployment key gives CircleCI access to a single repository. If you want to push to your repository from builds, please add a user key as described below or manually add a read-write deployment key.

rgleason commented
  • cloudsmith push raw
    --republish
    --no-wait-for-sync
    --name admiralty_tide_tables_pi-0.1.3.0-android-arm64-16-android-arm64-metadata
    --version 0.1.3.0+120.ff263d1
    --summary 'admiralty_tide_tables opencpn plugin metadata for automatic installation' opencpn/admiralty_tide-beta
    /home/circleci/project/build/admiralty_tide_tables_pi-0.1.3.0-android-arm64-16-android-arm64.xml

Checking raw package upload parameters ... ERROR
Failed to validate upload parameters! (status: 404 - Not Found)

Detail: Not found.
Hint: This usually means the user/org is wrong or not visible.

Exited with code exit status 148

### opencpn/admiralty_tide-beta

It should be "admiralty-tide-beta" to match the names used for the repositories in Cloudsmith