Hi Noam, Thanks for the response. I've now written a small gradle build script which generates a file (this is at work, and it's a RPM I'm making). The build info gets sent to Artifactory, but not the artifact itself. I have specified "**/*.rpm" as the include pattern, so I'm somewhat confused as to what else I'm missing. Do I need to get gradle itself to do the deployment of the artifact to Artifactory (a task I thought the plugin was designed to handle)? As it stands, my build.gradle has no references to any repository. Is that what I'm doing wrong?
Thanks, Frode On Mon, Feb 14, 2011 at 02:08, Noam Tenne <[email protected]> wrote: > Hi Frode, > Currently, the Artifactory plugin provides publication support only for > artifacts that are a result of a Maven, Ivy or Gradle build, but support for > "free-style" jobs is planned for a future version. > HTH, > Noam ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
