Hi Liran, Thank you for trying out Artifactory!
- Metadata is all the information about binaries that we store. It
includes (along other things) properties, but not limited to them.
Properties are special only because have a UI support for them. Here's the
screenshot that explains it:
[image: Inline image 2]
- The status might be anything you want (it's just a string). Our build
server plugins feature a release process, that uses 'Staged' and 'Released'
statuses, but you are more than welcome to come up with your own statuses,
that match your process (specially since you don't plan to use a build
server integration features). You change a status of a build ('promote' as
we call it) by REST, here's
how<http://wiki.jfrog.org/confluence/display/RTF/Artifactory%27s+REST+API#Artifactory%27sRESTAPI-BuildPromotion>
.
Hope that helps,
Baruch
Baruch.
--
Developer Advocate
JFrog Ltd
www.jfrog.com
+972544954353
@jbaruch
On Tue, Jan 1, 2013 at 2:36 PM, Tal, Liran <[email protected]> wrote:
> Hi everyone,****
>
> ** **
>
> I’m currently evaluating the use of Artifactory for an inside project
> we’re doing and need some answers which I couldn’t find in the User Guide.
> ****
>
> I’d like to add that we’re not looking into integrating it with a build
> server but rather as being a generic content repository.****
>
> ** **
>
> *Metadata and properties* – what is the difference exactly? It’s possible
> to both attach items with set properties as well as metadata in the form of
> an XML but I’m not seeing a clear distinction between both. Also on this
> topic, is it possible to set ****
>
> specific properties to be ‘required’ when an artifact is being submitted?*
> ***
>
> ** **
>
> ** **
>
> *Artifact Life-cycle* – It seems that through the use of ‘build
> integration’ it’s possible to ‘promote’ artifacts. What does this actually
> mean? A use-case that we require is for users to create their repositories
> and artifacts and be able to toggle them as ****
>
> say ‘dev’ or ‘qa’ status, meaning that they wouldn’t be able to be
> consumed by a ‘public’ user and at a later time the entire repo or an
> artifact can be ‘promoted’ to ‘released’ state where it will be able to be
> publically consumed.****
>
> ** **
>
> So what I’m really asking is if there’s a built-in workflow for such
> use-case? Correct me if I’m wrong but I guess such flow can be achieved by
> simply having 2 repositories: ‘private’ and ‘public’ and to move/copy
> artifacts from one to another when it’s set to be ‘released’ and manage the
> security access to these 2 repos correctly.****
>
> ** **
>
> ** **
>
> Thanks in advance!****
>
> ** **
>
> Regards,****
>
> Liran.****
>
>
> ------------------------------------------------------------------------------
> Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS
> and more. Get SQL Server skills now (including 2012) with LearnDevNow -
> 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts.
> SALE $99.99 this month only - learn more at:
> http://p.sf.net/sfu/learnmore_122512
> _______________________________________________
> Artifactory-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/artifactory-users
>
>
<<2013-01-02_095348.png>>
------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612
_______________________________________________ Artifactory-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/artifactory-users
