Hi,
This is normally to do with the order in which artifacts are deployed
(among other things, Artifactory depends on the order when guessing which
artifacts belong to which build runs).
Do you deploy the artifacts using Maven's deploy goal or using the Jenkins
Artifactory plugin?
Cheers,
Noam
On Tue, Mar 20, 2012 at 10:13 PM, mcofran <[email protected]> wrote:
> Hi,
>
> I have Artifactory 2.3.1, using Jenkins 1.451 as a CI server, and Maven
> 3.x.
> I've got a repository setup for snapshot builds using a unique timestamped
> deployment strategy. Three artifacts are deployed, a jar, a pom, and an
> rpm
> generated with maven's rpm plugin as an attached-rpm. Once deployed into
> artifactory, everything looks good except the rpm file has a build number
> suffix of 1 less than the other 2 artifacts. So I see something like:
>
> foo.0.1-<date>.<time>-1-rpm.rpm
> foo.0.1-<date>.<time>-2.jar
> foo.0.1-<date>.<time>-2.pom
>
> Has anyone ever seen anything like that or know what might causing it?
>
> Thanks in advance.
>
>
> --
> View this message in context:
> http://forums.jfrog.org/Build-number-suffix-wrong-on-unique-snapshot-tp7390450p7390450.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
