-
Notifications
You must be signed in to change notification settings - Fork 26
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
APT-548 added generate-artifactory-path command to foreman #84
Conversation
@@ -1,3 +1,5 @@ | |||
//After updating this file, consider updating artifactory_path.rs to reflect the operating systems and architectures that Foreman recognizes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wish there was a better way to tie this together, but it doesn't seem like it. Luckily, since Matt added a fairly comprehensive set, it shouldn't need to change often.
let path = generate_artifactory_path("repo", "tool_name", "v0.1.0", "macos", None).unwrap(); | ||
assert_eq!( | ||
path, | ||
"artifactory/repo/tool_name/v0.1.0/tool_name-v0.1.0-macos.zip" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One interesting detail here is that the version number isn't duplicated in the github releases, but it also probably isn't a problem (we only really look for the os/arch keywords, iirc). I think we should be fine as is, but it's something to call attention to in case it affects our ability to share the artifact-choosing/download implementation.
Co-authored-by: Paul Doyle <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
This Foreman command generates a path that can be used to upload artifacts to Artifactory.