I'd like to dynamically specify the artifact version instead of pulling the latest version from the release repository

nulldriver / maven-resource

Maven Repository Manager Concourse Resource

Apache License 2.0

22 stars 49 forks source link

I'd like to dynamically specify the artifact version instead of pulling the latest version from the release repository #25

Open goprasad opened 6 years ago

goprasad commented 6 years ago

I'd like to dynamically specify the artifact version instead of pulling the latest version from the release repository

name: nexus-artifact type: maven source: artifact: com.fdc.ucom.customer:uComCustomerSvcs:jar url: http://xxxxx:8081/nexus/content/repositories/releases version : 1.3.0

patrickcrocker commented 6 years ago

This is similar to #24... can you expand on what this usecase would solve? When would you use this in your pipeline?

goprasad commented 6 years ago

I would like to pull the specific artifact version instead of latest ... I can explicitly provide the version number in params.yml file

goprasad commented 6 years ago

basically I needed something like this.

https://github.com/emerald-squad/artifactory-resource

basically user can provide the version input instead of retrieving everytime the latest version

Get a specific version using a JSON version file:

resources:

name: artifact type: artifactory source: host: "https://emerald.squad.com/artifactory" api_key: repository_id: repo-local group_id: emerald.squad artifact_id: wonderful-artifact version: uri: ssh://git@git.emerald.squad.com/wonderful-artifact.git file: artifact-versions.json key: wonderful-artifact private_key: | -----BEGIN RSA PRIVATE KEY----- ... -----END RSA PRIVATE KEY----- The JSON file in the git repo would look like this:

{ "wonderful-artifact": "1.0.0" }

Apohg commented 5 years ago

Hi,

I'm searching a way to deploy last master versioned tag by example, for a rollback task. Is there a way to chose a specific version of an artifact ?

Thank you

rhoughton-pivot commented 4 years ago

Or allow maven semantics in the source definition:

name: version-1.x
source:
  artifact: a.b.c:d:jar
  version: [1.0,2.0)
name: version-latest
source:
  artifact: a.b.c:d:jar

Zsmith32 commented 3 years ago

I would like to pull the specific artifact version instead of latest ... I can explicitly provide the version number in params.yml file

I'd like to have this as well. My use case is this. We have more then 10 applications that use the same base resource, but it takes us quite some time to upgrade all the applications. We need to be able to keep the pipeline tagged to a specific version of the resource so upgrading the base doesn't effect all applications.

patrickcrocker commented 3 years ago

Apologies, I've been away from this project for a while, but I'm ready to start work on enhancements again. I'll be reviewing this and other issues and coming up with a roadmap soon. And of course, PRs are always welcome (of which I have 7 I need to review as well)

Zsmith32 commented 3 years ago

No need to apologize :)

I think some of the PRs add a versioning option. So I just wanted to provide a clear use case.