Hi Miguel,
How will be visible to which release the package, binary, properties belong when there is more than one?
One approach could be to have a <GE_name>:<release>, e.g. Backend_ThingsManagement_GE:1.1.3
Another approach could be to have one "package" (in forge terms) for the GE and the filenames of the package to have the release ID in the name, e.g. clotho-management-application-occi-0.3.34_noarch_fiware_rel1.3.rpm <https://forge.fi-ware.eu/frs/download.php/84/clotho-management-application-occi-0.3.34.noarch.rpm>
Maybe this was discussed, then sorry for my ignorance.
Thanks & Br,
Lorant
From: fiware-bounces at lists.fi-ware.eu [mailto:fiware-bounces at lists.fi-ware.eu] On Behalf Of ext Miguel Carrillo
Sent: Wednesday, June 27, 2012 6:01 PM
To: fiware at lists.fi-ware.eu
Cc: fiware-wpl at lists.fi-ware.eu; fiware-wpa at lists.fi-ware.eu
Subject: Re: [Fiware] [Fiware-wpl] Software delivery (how to provideDeliverable D.x.2.a)
Dear all,
I have been warned (thanks, Alex) that in some special cases a given GE could be released privately. This is exceptional but it is stated in the DoW:
In these very concrete cases, the SCM will not be used and the "Files" part of the project can be made private for that particular GE.
Best regards,
Miguel
El 27/06/2012 17:05, Miguel Carrillo escribió:
Dear all,
As editing the wiki will take a bit longer I will write a (rather long) email and will explain how to proceed with some aspects of the software delivery that were not clearly explained yet. Given the urgency of this I send it to the general list but please proceed to discuss any concerns internally in your respective WP lists.
This message refers to software delivery. This means:
* 1) Delivery for installation on the testbed(packages, properties and binaries)
* 2) Source code delivery - this does not apply to those GE who have agreed not to provide it
I will add all tall his to the private wiki later, putting alongside all the guidelines that are there already.
First of all, the software delivery will take place on the forge. As regards the project within the forge, we will use the project of the WP (Iot, Data, Apps, Tools...)
PART 1 - Delivery for installation on the testbed
========================================
The packages, properties and binaries go to the "Files" part of the project.
We have already delivered a GE in cloud and you can use it as an example:
* https://forge.fi-ware.eu/frs/?group_id=14
First you create a Package (this goes with the GE name)
Then you create 3 blocks per GE (using the "Create New Release" feature)
* Packages (rpm, debian... ) - this does not apply to the particular example we provide but it should apply in many cases in your GEs
* Binaries
* Properties - miscelaneous files
Please follow the same naming convention for the 3 blocks (Packages, Binaries, Properties). Add all three even if one of them is empty in your particular case.
I see that this deliverable is Public according to the DoW so this should be publicly available, not private (the WPL must administrate this). If there are any particular concerns, let me know (privately - please do not reply to this email, it gets to more than 100 people!).
For the WPL/WPA - hint: if you still cannot see this publicly, go to the admin part of the "Users" of the "Admin" section of the project and tweak the "Observer" user.
(this is not visible to most users, just those with admin right on the project)
PART 2 - Delivery of source code
========================================
Depending on the GE, you may have decided to provide this or not. We would expect this for most of the GEs.
This goes to the "SCM" tool in the project.
There you have a link to subversion where you can upload all the software. The admin of each WP (WPL and WPA, please proceed to do so) has the right to make their SCM public on the internet on the admin page of the SCM:
It is "all or nothing". Once this is made public, you cannot hide branches. Let us settle this: the SVN will be made public for each technical WP so the code that is uploaded here will be public. If something is private, you will not upload it here.
When the testbed environment is fully set up we will send further instructions to provide extended info for the deployment (we will ask for maven - *.pom files - or test scripts, for instance). But this is not strictly necessary to meet the deadline that is upon us so we will do it later (but very soon!)
Best regards,
Miguel
--
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77
e-mail: mcp at tid.es
Follow FI-WARE on the net
Website: http://www.fi-ware.eu
Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
Twitter: http://twitter.com/Fiware
LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
--
----------------------------------------------------------------------
_/ _/_/ Miguel Carrillo Pacheco
_/ _/ _/ _/ Telefónica Distrito Telefónica
_/ _/_/_/ _/ _/ Investigación y Edifico Oeste 1, Planta 9
_/ _/ _/ _/ Desarrollo Ronda de la Comunicación S/N
_/ _/_/ 28050 Madrid (Spain)
Tel: (+34) 91 483 26 77
e-mail: mcp at tid.es
Follow FI-WARE on the net
Website: http://www.fi-ware.eu
Facebook: http://www.facebook.com/pages/FI-WARE/251366491587242
Twitter: http://twitter.com/Fiware
LinkedIn: http://www.linkedin.com/groups/FIWARE-4239932
----------------------------------------------------------------------
________________________________
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at.
http://www.tid.es/ES/PAGINAS/disclaimer.aspx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120629/d51fa69d/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 4916 bytes
Desc: image001.gif
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120629/d51fa69d/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 5904 bytes
Desc: image002.gif
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120629/d51fa69d/attachment-0001.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 6424 bytes
Desc: image003.png
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120629/d51fa69d/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 8244 bytes
Desc: image004.png
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120629/d51fa69d/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 3857 bytes
Desc: image005.png
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120629/d51fa69d/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 2746 bytes
Desc: image006.png
URL: <https://lists.fiware.org/private/fiware-wpa/attachments/20120629/d51fa69d/attachment-0003.png>
You can get more information about our cookies and privacy policies clicking on the following links: Privacy policy Cookies policy