Hey Shay,
I appreciate the prompt reply!
1. In regards to properties via the REST API for the open source version, the
wiki page on that states:
Set Item Properties
Description: Attach properties to an item (file or folder). When a
folder is used property attachment is recursive by default.
Notes: Requires Artifactory Pro
So it seems that the properties/metadata feature is not enabled in the open
source version regardless of UI/API mechanism.
Is that indeed the case?
Not directly related to properties but since the build actions in the REST
API are not provided in the open source version it seems weird that the basic
actions of copying
artifacts would not be available too but this is what the wiki states:
Copy Item
Description: Copy an artifact or a folder to the specified destination.
Optionally suppress cross-layout module path translation during copy.
You can test the copy using dry run.
Copy item behaves similarly to a standard file system and supports
renames. If the target path doesn't exist, the source item is copied and
optionally renamed. Otherwise, if the target exists and it is a
directory, the source is copied and placed under the target directory.
Notes: Requires Artifactory Pro
2. So the property search is a plain key=value? If so, is the value string case
sensitive? And what chars are allowed for value?
I was also wondering if the open source version supports dependency management,
if so I'd appreciate if you can provide a link to read about it.
Regards,
Liran.
-----Original Message-----
From: shayb [mailto:[email protected]]
Sent: יום ד 20 פברואר 2013 14:25
To: [email protected]
Subject: Re: [Artifactory-users] Open source version features
Hi Liran,
1. With the open source version, the properties section will be disabled in
Artifactory UI. you can edit properties via REST only.
2. Artifactory does not support properties range search.
Although it might require a little bit more work on your part, you can
search for all artifacts with version property; that is, you can get them by
searching for property-name=version without property value, and write your own
script to determine the range.
3. It is not possible in Artifactory, but deploying an empty text file should
work.
4. We dont have a reference specifying which resource needs the pro version,
but a feature requiring the pro version will have a note in the wiki page, such
as:
http://wiki.jfrog.org/confluence/display/RTF/Artifactory%27s+REST+API#Artifactory'sRESTAPI-BuildPromotion
hope this helps,
Shay.
--
View this message in context:
http://forums.jfrog.org/Open-source-version-features-tp7578592p7578594.html
Sent from the Artifactory - Users mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics Download AppDynamics Lite for free
today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
