Hi Sam,
The meaning of "Deploy all artifacts to the selected target repository in
one go (as opposed to the deploy at the end of each module build, used by
Maven/Ivy)" is that it deploys all the artifacts at the end of the reactor
build, as opposed to Maven deploy which publishes at the end of each reactor
module.
Although you conceive the different parts of the build you've split up as
"Modules", they are now separate Maven runs, not Maven reactor modules.
The Artifactory Maven 3 plugin is integrated into Maven's lifecycle and thus
"lives" as long as each reactor build lives.
If you're looking for the Maven consistency and layout, the Generic
deployment won't be of too much help.
Other than that, I can only suggest that you configure each separate build
to archive it's produced artifacts and write a small script to analyze the
pom files and deploy them to the correct locations.
HTH,
Noam
On Thu, Jul 21, 2011 at 7:34 AM, samt <[email protected]> wrote:
> Hi,
>
> We are using maven 3 and bamboo 3.1 and want to split our build across
> several jobs so that different modules can be built in parallel on remote
> agents. This works fine except that build artifacts are deployed to
> artifactory after each job completes instead of in one go after all jobs
> have completed.
>
> The Bamboo Artifactory Plug-in states that it can "Deploy all artifacts to
> the selected target repository in one go (as opposed to the deploy at the
> end of each module build, used by Maven/Ivy)". This sounds like what we
> need
> except I believe it refers to the "Artifactory Maven 3 Task" deploying
> build
> artifacts at the end of the task's execution (after it has completed
> running
> the maven build) which of course occurs within a single job.
>
> So I attempted to use the "Artifactory Generic Deploy Task" in a later
> stage
> to deploy shared artifacts produced by jobs in an earlier stage. This
> almost
> works as desired execpt that it appears to deploy the artifacts as normal
> files rather than as maven artifacts, i.e. artifactory saves the JAR at the
> path defined in the 'Published Artifacts' declaration instead of reading
> the
> pom file from inside the JAR and copying both the JAR and the POM to the
> appropriate package/version location.
>
> Is there any way to deploy build artifacts to artifactory only after
> several
> bamboo jobs have completed successfully?
>
> Thanks
> Sam
>
> --
> View this message in context:
> http://forums.jfrog.org/Question-on-Bamboo-Artifactory-Plug-in-and-multiple-jobs-tp6605402p6605402.html
> Sent from the Artifactory - Users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> 5 Ways to Improve & Secure Unified Communications
> Unified Communications promises greater efficiencies for business. UC can
> improve internal communications as well as offer faster, more efficient
> ways
> to interact with customers and streamline customer service. Learn more!
> http://www.accelacomm.com/jaw/sfnl/114/51426253/
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
------------------------------------------------------------------------------
5 Ways to Improve & Secure Unified Communications
Unified Communications promises greater efficiencies for business. UC can
improve internal communications as well as offer faster, more efficient ways
to interact with customers and streamline customer service. Learn more!
http://www.accelacomm.com/jaw/sfnl/114/51426253/
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
