jfrog artifactory backend server for bob artifacts #445
Conversation
mahaase
commented
Nov 1, 2021
mahaase
commented
- all credits to @rhubert WIP: archive: added JFrog Artifactory backend #240
- re-tested twice :)
- synced with current master
- removed the replace of "/" by "_" in upload/download url
- i guess we should bring this into the master (instead loosing it)
The JFrog artifactory backend uses the dohq-artifcatory python lib and supports the authentication methods (username+password, API-Key, global configuration file) provided by this library.
Artifactory supports properties for artifcats. Added the properties key for archive spec
to provide archive properties. The properties are substitued whit the packageStep / metaEnv
of the package.
archive:
backend: "artifactory"
url: "http://localhost:8081/artifactory/example-repo-local"
properties:
FOO: "42"
BAR: "13"
TEST: "${TEST:-NotSet}"
…o current master resolved some conflicts and removed the replacing of slashes with underlines in upload/download url/tree
|
I can also open a MR to your branch, so u don't have to sync with master again.
Currently we do not delete artifacts at all. But yeah, I have no idea, how it could be possible to clean up the artifactory. |
|
I can just use your branch - this won't make a difference ;) I'm just asking because ATM I'm using http upload to artifatory (no need for additional properties) and this works without any problems. I don't have a good use case for additional artifactory integration - which properties are needed,... ? I'd need some input from your side. I've a |
|
the option to get additional properties would be nice. e.g. for images that will be released to customer. we could adapt the recipe like this, that a user of artifactory get all necessary information: versions, dependencies, variants, ....
sounds cool, for a full bob-artifactory support, this is important. |
2 participants
