You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From reading http://probo.ci/docs/steps/script-plugin/ I guess this can be determined with a step that does ls -l $ASSET_DIR but it would be nicer to have a more straightforward method.
Looks like the asset receiver at app.probo.ci works differently than the open source repo and the authentication it uses wouldn't let you get a list of assets without a session cookie. I guess there's not really any programmatic way to access the asset list. @tizzo Is there any chance you will change this endpoint (on app.probo.ci) to allow the use of upload tokens as an authentication method:
We are currently focused on getting some new features tested and released such as Gitlab integration, a logs viewer, and shell access to the build container, but we definitely could add some improvements like this to the Probo Uploader to our Roadmap for future releases. Thanks for the feedback guys!
I will keep this issue open and follow up once we release updates to the Probo Uploader.
It would be nice to know a list of assets that are uploaded using a specific token.
I guess
probo-uploader --token [UPLOAD TOKEN] --list-remote-files
or something?The text was updated successfully, but these errors were encountered: