Just had a look at the API.

So what version is at https://dl.bintray.com/rob-nash/BinaryDump/iOS/dequable.zip ? Where is the package information here?

My binary profile currently has Dequable 1.3.0

When I attempt to upload 1.2.0 with the same :file_path and the following headers, I receive a 409 conflict error code and a message.

{
"message": "Unable to upload files: An artifact with the path 'iOS/dequable.zip' already exists under another version"
}

Navigating the website, I can see that the file directory responds to version filters. So it's important to realise two things here.

The metadata must include the version number
The file path must be unique.

So going forward, a naming convention is required. Such as

/content/rob-nash/BinaryDump/iOS/dequable_1.2.0.zip
/content/rob-nash/BinaryDump/iOS/dequable_1.3.0.zip

:subject will be something configurable but :repo and :package have to be derivable from the Cartfile.resolved. How would Rome derive :repo and :package from the above Cartfile.resolved for all 3 cases?

:subject = rob-dash
Agreed, this must be configurable.

:repo = BinaryDump
One caveat to using this service, is that you need to create and name a repo. There can be many repos. The onus should be on the user, in my opinion, to create one and provide the name to Rome. So, this also has to be configurable.

:package = Dequable
This can be extracted from Cartfile.resolved. In your above example, it would be Alamofire.

Note that ios-rest is not the final name of the framework binary, this is why there is a https://github.com/blender/Rome#repositorymap section

So we can supply the following paths

iOS/Dequable.framework.1.3.0.zip
iOS/Dequable.framework.dSym.1.3.0.zip
Dequable.version.1.3.0.zip

Get Version Files will return information about all of these files.

Uh oh!

Support for Bintray #120

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions