To rebuild a SNAPSHOT: click in the package -> go to
"edit" tab ->
click on "Create Snapshot for deployment" -> Choose an existing
snapshot from the radio-button list (you must have at least one
previous snapshot) -> Click on "Create new snapshot"
This actually replaced the old snapshot with a newly created one under
the same name. The snapshot itself is read-only and immutable once it is
created, same as a historical version of package. I guess your use case
is a client wants to point to a stable version of a package, eg. so
called the last successful build so that the client is immune from the
any unstable changes on the latest version? Sth similar to this jira:
. This jiar is still talking
about snapshot, though similar result can be achieved by tagging package
version with custom names. Eg, we can create a tag called
"LastSuccessfulBuild" and keep moving this tag and apply it to a
historical version of package either manually or automatically.
Cheers,
Jervis
This will replace the old version of the snapshot with a new version
with the same name containing the current state of the package.
Best Regards,
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Esteban Aliverti
- Developer @
http://www.plugtree.com <
http://www.plugtree.com>
- Blog @
http://ilesteban.wordpress.com
On Sun, Oct 9, 2011 at 6:49 AM, Jervis Liu <jliu(a)redhat.com
<mailto:jliu@redhat.com>> wrote:
Esteban Aliverti wrote:
> Hi Jervis,
> When you build a SNAPSHOT with an existing name (Guvnor shows
you all
> the SNAPSHOTS and lets you select an existing one), the SNAPSHOT is
> updated (maybe under the hood the SNAPSHOT gets removed and a
new one
> is created). So, if you have an application pointing to the SNAPSHOT
> you can update the assets it uses without modifying anything in the
> application itself.
>
Hi Esteban, I can not find any places in Guvnor UI that allows you to
rebuild a snapshot. Are you referring to the Working Set instead?
> Best Regards,
>
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>
> Esteban Aliverti
> - Developer @
http://www.plugtree.com <
http://www.plugtree.com>
> - Blog @
http://ilesteban.wordpress.com
>
>
> 2011/10/8 Jervis Liu <jliu(a)redhat.com <mailto:jliu@redhat.com>
<mailto:jliu@redhat.com <mailto:jliu@redhat.com>>>
>
> Hi Esteban,
>
> The package snapshot wont be gone in the near future. One reason
> is for backward compatibility. Another concern is that we still
> need to find out if there are any use cases that package version
> can not cover. In this case, your input is exactly what we are
> looking for. Please see my comment in-line below.
>
> On 2011/10/8 17:09, Esteban Aliverti wrote:
>> Jervis, so you are trying to deprecate SNAPSHOTS in favor of
>> Versions? I don't think they address the same issue. With
>> SNAPSHOTS you can put different names to different
"moments" of a
>> package.
> We don't have this yet, but I guess this will be a very useful
> feature. I.e. a named package version or package version alias.
>> More important, SNAPSHOTS were created and updated on
demand and
>> not every time you update the package, so you can update a
>> SNAPSHOT definition adding or changing its assets and you don't
>> need to update your applications.
> Not sure how you can do this? a SNAPSHOT is a read-only copy of
> package. You can not change its configuration nor you can add or
> change its asset.
>> They always read the package using same SNAPSHOT name.
>> Using versions, I need to be careful in change my applications
>> when I want them to use some modifications I have in my
package.
>> I mean, I also see package versioning as something good,
but I'm
>> not sure if versions could replace SNAPSHOT. Are you
planning to
>> add some way to put a name to a particular group of
versioned assets?
>>
>> Best Regards,
>>
>> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
>>
>> Esteban Aliverti
>> - Developer @
http://www.plugtree.com <
http://www.plugtree.com>
>> - Blog @
http://ilesteban.wordpress.com
>>
>>
>> 2011/10/8 jliu <jliu(a)redhat.com <mailto:jliu@redhat.com>
<mailto:jliu@redhat.com <mailto:jliu@redhat.com>>>
>>
>> On 2011/10/7 9:54, Demian Calcaprina wrote:
>>> Hi again.
>>>
>>> I have been able to use guvnor package versions with some
>>> success..
>>>
>>> Is there any service I can call to create a new version? I
>>> have checked that it seems to change the package version
>>> when you click on "save package". Can I have some URL
to
>>> achieve it automatically?
>>>
>> Hi,
>>
>> Sorry for the late response, I was in holiday. There is no
>> REST service to create a package version as this is not
>> needed. A package version is created automatically when
your
>> package gets updated (through Guvnor UI or through REST).
>>
>> Cheers,
>> Jervis
>>
>>> Thanks
>>>
>>> Demian
>>>
>>> On Tue, Oct 4, 2011 at 9:57 AM, Demian Calcaprina
>>> <calcacuervo(a)gmail.com <mailto:calcacuervo@gmail.com>
<mailto:calcacuervo@gmail.com <mailto:calcacuervo@gmail.com>>> wrote:
>>>
>>> Thanks Jervis.
>>>
>>> I currently use Guvnor 5.2, and saw that I can use
>>> version so I will try to use them.
>>>
>>> - Is there something I will be missing about versions,
>>> by using 5.2?
>>> - Do you know when a new version is created? With
>>> Snapshots, I could choose when to create a new
one. How
>>> about versions?
>>>
>>> Thanks!
>>>
>>> Demian
>>>
>>> 2011/10/3 jliu <jliu(a)redhat.com
<mailto:jliu@redhat.com> <mailto:jliu@redhat.com
<mailto:jliu@redhat.com>>>
>>>
>>> On 2011/10/4 1:54, Demian Calcaprina wrote:
>>>> Hi everyone. I am using Guvnor 5.2, and I need to
>>>> make some operations from my application.
>>>>
>>>> Specifically, I need to make two operations
remotely:
>>>> - List Snapshots, as it is possible to list
packages.
>>>> - Create a new snapshot from a package.
>>>>
>>>> Is this possible to make these operation through
>>>> rest API?
>>>>
>>> Hi,
>>>
>>> Start from 5.3, Guvnor Packages are fully
versioned.
>>> I would recommend you to use a vesioned package
>>> instead of package snapshot. Package snapshot will
>>> be deprecated in the future.
>>>
>>> Cheers,
>>> Jervis
>>>> Thanks,
>>>>
>>>> Demian
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> rules-users mailing list
>>>> rules-users(a)lists.jboss.org
<mailto:rules-users@lists.jboss.org>
<mailto:rules-users@lists.jboss.org
<mailto:rules-users@lists.jboss.org>>
>>>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>>>
>>>
>>>
>>> _______________________________________________
>>> rules-users mailing list
>>> rules-users(a)lists.jboss.org
<mailto:rules-users@lists.jboss.org>
>>> <mailto:rules-users@lists.jboss.org
<mailto:rules-users@lists.jboss.org>>
>>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> rules-users mailing list
>>> rules-users(a)lists.jboss.org
<mailto:rules-users@lists.jboss.org>
<mailto:rules-users@lists.jboss.org
<mailto:rules-users@lists.jboss.org>>
>>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>>
>>
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users(a)lists.jboss.org
<mailto:rules-users@lists.jboss.org>
<mailto:rules-users@lists.jboss.org
<mailto:rules-users@lists.jboss.org>>
>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>
>>
>>
>>
>> _______________________________________________
>> rules-users mailing list
>> rules-users(a)lists.jboss.org
<mailto:rules-users@lists.jboss.org>
<mailto:rules-users@lists.jboss.org
<mailto:rules-users@lists.jboss.org>>
>>
https://lists.jboss.org/mailman/listinfo/rules-users
>>
>
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org
<mailto:rules-users@lists.jboss.org>
<mailto:rules-users@lists.jboss.org
<mailto:rules-users@lists.jboss.org>>
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
>
>
------------------------------------------------------------------------
>
> _______________________________________________
> rules-users mailing list
> rules-users(a)lists.jboss.org <mailto:rules-users@lists.jboss.org>
>
https://lists.jboss.org/mailman/listinfo/rules-users
>
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org <mailto:rules-users@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/rules-users
------------------------------------------------------------------------
_______________________________________________
rules-users mailing list
rules-users(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users