| I don’t know how it translates to what Ernesto has documented below, but, from a product management perspective, what I would like to see “saved” in a secure, accessible location is:
- 0.8.0 final RCP and P2 Repo(s)
- 0.9.0 final RCP and P2 Repo(s)
I am assuming, here, that the source code lineup for these is still available and reusable in Git (preferably, or a compressed archive at the very least). Not necessarily because I expect to have to support them, but because this should be a good habit to get into, especially starting with 1.0! And this will be important for industrial usage (e.g., LTS) and is a concern for the Papyrus IC going forward.
Of course, for 1.0, I would also expect all of these artifacts to be “saved” (including the Oomph installer and its configuration).
If anyone has ideas as to how this aligns with the list below, please chime in!
Regards,
Charles Rivet
Senior Product Manager, Papyrus-RT product leader
A follow-up.
Looking into other folders there I found that the "builds" folder also contained old 0.7.x artifacts. I assumed we didn't need those either so I removed all of it.
We also have, rather confusingly, folders "rcp" and "rcps". The first contains this:
. |-- nightly | `-- 0.8.0 | `-- 20161212 | `-- org.eclipse.papyrusrt.rcp.product-win32.win32.x86_64.zip `-- releases `-- neon |-- 0.8.0 | |-- org.eclipse.papyrusrt.rcp.product-linux.gtk.x86_64.zip | |-- org.eclipse.papyrusrt.rcp.product-macosx.cocoa.x86_64.tar.gz | `-- org.eclipse.papyrusrt.rcp.product-win32.win32.x86_64.zip `-- 0.9.0 |-- org.eclipse.papyrusrt.rcp.product-linux.gtk.x86_64.zip |-- org.eclipse.papyrusrt.rcp.product-macosx.cocoa.x86_64.tar.gz `-- org.eclipse.papyrusrt.rcp.product-win32.win32.x86_64.zip
And the second contains
. `-- nightlies `-- 0.8.0 `-- 20161212 `-- org.eclipse.papyrusrt.rcp.product-win32.win32.x86_64.zip
The actual p2 update sites are under "updates" whose structure is as follows:
. |-- integration | |-- neon | | |-- 0.8.0 | | |-- 0.8.0-beta | | |-- I201704060516 | | |-- I201704130516 | | |-- I201704200516 | | |-- I201704270515 | | |-- I201705110515 | | `-- I201705250515 | `-- oxygen | `-- I201706220515 |-- milestones | `-- neon | `-- 0.8.0 | `-- M201607271727 |-- nightly | |-- neon | | `-- last | `-- oxygen `-- releases |-- mars | |-- 0.7.0 | | |-- codegen | | |-- codegen-old | | |-- codegen-old-2 | | |-- codegen-old-3 | | |-- codegen-old-4 | | |-- codegen-old-5 | | `-- tooling | |-- 0.7.0-old | | `-- tooling | |-- 0.7.1 | | |-- codegen | | `-- tooling | |-- 0.7.1-old | | `-- tooling | `-- 0.7.2 | |-- codegen | `-- tooling `-- neon |-- 0.8.0 | |-- R201610241656 | |-- test | `-- test_release `-- 0.9.0 `-- R201703231548
We also have a top-level "0.7.0" folder which looks quite outdated.
Finally we also have a "download" folder with the following:
. |-- 0.7.0 | |-- N201508071412 | | `-- Papyrus-RT-Update-N201508071412.zip | |-- N201508071431 | | `-- Papyrus-RT-Update-N201508071431.zip | |-- N201508071616 | | `-- Papyrus-RT-Update-N201508071616.zip | `-- N201509010919 | `-- Papyrus-RT-Update-N201509010919.zip |-- 0.7.1 | |-- N201510120954 | | `-- Papyrus-RT-Update-N201510120954.zip | `-- N201510121606 | `-- Papyrus-RT-Update-N201510121606.zip |-- 0.7.2 | `-- N201512141100 | `-- Papyrus-RT-Update-N201512141100.zip |-- 0.8.0 | |-- M201607280150 | |-- M201607280214 | | `-- Papyrus-RT-Update-test.zip | |-- R201607280301 | | `-- Papyrus-RT-Update-test.zip | `-- R201610241656 `-- 0.9.0 `-- R201703231548
Note that the last two "release" drops are empty.
I do not know who created all these.
So, from the above, which should I remove and which should I keep?
I assume we can remove all *-old* folders. Should we remove all 0.7.*? all 0.8.*? all 0.9.*? all test*?
Should I remove the top-level "rcps" which looks redundant? Do we need rcp/nightly?
-- Ernesto Posse Zeligsoft
I took a look and found that this archive folder used to be populated by the codegen build job (by the scripts/codegen/archive.sh script which I wrote to mimic the top-level archive.sh written by Celine). The codegen job used to have a different build than tooling, which is why it had separate scripts, but later the build was unified and the codegen build no longer invokes that script.
So these are indeed very old files and I have removed them all.
As for archiving nightlies, I'm not sure what we are doing exactly. Celine and Christian would have a better idea as they did the build reorganization. I see that the PapyrusRT-Master-* jobs have the archive post-build action enabled with " repository/**/*,*.zip" and for PapyrusRT-Master-Product it's " repository/**/*,*.zip ,**/products/*.zip , **/products/*.tar.gz". I'm not sure Furthermore, the build-after.shscript which is invoked by every job seems to move the generated p2 to ${WORKSPACE}/repository (component-wise or all) and the generated zipped p2 to ${WORKSPACE}. So in effect it looks like we have one archived copy of the nightly in each https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-<Component>/ws/ and for the whole thing at https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-Product/ws. The scripts remove any previous archive found at this locations, so in effect we have exactly one nightly archived.
Hudson's help states that
Archives the build artifacts (for example, distribution zip files or jar files) so that they can be downloaded later. Archived files will be accessible from the Hudson webpage. Normally, Hudson keeps artifacts for a build as long as a build log itself is kept, but if you don't need old artifacts and would rather save disk space, you can do so.
I don't know how long the "build log" is kept.
The maximum number of build records to keep is set to 30 and the maximum number of builds to keep with artifacts is 3 for each PapyrusRT-Gerrit-* job, and 10 and 3 respectively for each PapyrusRT-Master-* job. It's not clear to me where exactly those last 3 artifacts are stored, though.
-- Ernesto Posse Zeligsoft
--
--
_______________________________________________papyrus-rt-dev mailing listpapyrus-rt-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visithttps://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|
