Hi Frode,
It's probably a pure Gradle issue.
You need to make sure that the artifact that you want to publish is a
part of the configuration that is being published (the default one is
the "archives" configuration).
For example you can do the following:
configurations {
myConfig
}
task buildMyNewConfig {
configurations.myConfig.addArtifact(new
DefaultPublishArtifact("mysql","sql","sql",null,new Date(),
file('/tmp/mysql.sql')))
}
task buildInfo.configuration = configurations.myConfig
task buildInfo.doFirst {
buildMyNewConfig
}
This will define a new configuration called "myConfig" and the task
buildMyNewConfigwill attach a custom external artifact to be published.
Lastly the task that is called "buildInfo" which is essentially what the
Artifactory-Gradle plugin runs the buildMyNewConfigtask which attaches
the artifact, and assigns this configuration to the buildInfo task
configuration.
You can find more information concerning the configurations and tasks in
the Gradle forums.
HTH,
Tomer
On 02/14/2011 06:23 AM, Frode Egeland wrote:
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
------------------------------------------------------------------------------
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
