Hi Tim, If you referring to "File Release" feature of TeamForge, then you've to create "package" and "release" first in TeamForge first and then you can use Collabnet Plugin.
However if your use case is just archiving "files" into TeamForge from Jenkins without caring about release and stuff.. then "Document" section of TeamForge can be populated using " CollabNet Document Uploader" build step. There you do not need to create upload path beforehand. If it does not exist then plugin build steps creates it and uploads your build generated file specified to TeamForge. Br Dharmesh Sheta -------------------------- SW Engineer www.collab.net On Thursday, May 31, 2012 10:04:50 AM UTC+2, Tim wrote: > > Hi there, > > I use the collabnet plugin help me to upload jar package into teamforge > automatically, however, the bad thing is that I have to create the package > and folder first in the teamforge. > > Do you know if there is better idea for me not create this folder first? > > Br, > Tim >
