| Re: [papyrus-rt-dev] Hudson disk usage |
Hi everyone. I've finished cleaning up the Hudson jobs.I deleted the jobs suggested by Christian:
- Papyrus-Gerrit-Master-All (disabled)
- Papyrus-RT-Gerrit-mars
- Papyrus-RT-Gerrit-master (disabled)
- Papyrus-RT-Gerrit-neon.x (disabled)
- Papyrus-RT-Gerrit-Tests
- Papyrus-RT-Mars-All
- Papyrus-RT-Master-All
- Papyrus-RT-Master-RCPTT(old) (disabled)
- Papyrus-RT-Product (disabled)
- Papyrus-RT-StableRelease-0.7.1 (disabled) — can we just archive the Hudson configuration data for this?
- TEST-Papyrus-RT-CodegenRTS-BuildFrom-gitroot-Triggered-nightly-PublishTo-nightly (disabled)
I left the following jobs:
- Papyrus-RT-Feature-Inheritance
- Papyrus-RT-Nexus-Deploy
- Papyrus-RT-Quality
- All the Papyrus-RT-<stream>-<component> jobs
- Papyrus-RT-Master-Product-* jobs
- Papyrus-RT-Installer-* jobs
So as of today, the only disabled job is
- Papyrus-RT-Installer-Promotion
--Ernesto Posse
On Thu, Jan 5, 2017 at 3:38 AM MAGGI Benoit <Benoit.MAGGI@xxxxxx> wrote:Hi Ernesto,
I can’t really say which one may or may not be deleted.
But I can suggest to add a description in the different views:
- some may be obvious but is still good to have good information (for example a link to Wiki/Update site… for mars installation)
- some are strange, for example the “Old job” view is probably here to keep around some jobs that should be removed in the future
o You may find some to be deleted here
o It may be interesting to add some line to explain the purpose of the view (How long should a job be kept when listed in this view?)
Regards,
Benoit
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Christian Damus
Envoyé : mercredi 4 janvier 2017 20:20
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>Objet : Re: [papyrus-rt-dev] Hudson disk usage
Hi, Ernesto,
I think we can delete these:
- Papyrus-Gerrit-Master-All (disabled)
- Papyrus-RT-Gerrit-mars
- Papyrus-RT-Gerrit-master (disabled)
- Papyrus-RT-Gerrit-neon.x (disabled)
- Papyrus-RT-Gerrit-Tests
- Papyrus-RT-Mars-All
- Papyrus-RT-Master-All
- Papyrus-RT-Master-RCPTT(old) (disabled)
- Papyrus-RT-Product (disabled)
- Papyrus-RT-StableRelease-0.7.1 (disabled) — can we just archive the Hudson configuration data for this?
- TEST-Papyrus-RT-CodegenRTS-BuildFrom-gitroot-Triggered-nightly-PublishTo-nightly (disabled)
This one is still in use until the inheritance feature is merged to master:
- Papyrus-RT-Feature-Inheritance
These are the installer builds that need to continue basically forever:
- Papyrus-RT-Installer
- Papyrus-RT-Installer-Promotion (disabled)
I don’t know what these are:
- Papyrus-RT-Nexus-Deploy (disabled)
- Papyrus-RT-Quality
Thanks,
Christian
On Jan 4, 2017, 11:56 -0500, Ernesto Posse <eposse@xxxxxxxxxxxxx>, wrote:
Ok, I've updated all jobs, except for Master-Product-Release, whose artifacts I assume we'd like to keep.
While doing this, I realized that we still have a bunch of old jobs, some of which are disabled, and which we might not need any more. See the list below.
We definitely want those described by http://wiki.eclipse.org/Papyrus-RT/Developer/Developer_Guide/Builds, namely
* Papyrus-RT-Gerrit-<stream>-<component>
* Papyrus-RT-<stream>-<component>
Where <stream> right now is <Master>
But there are a few for which it is not clear if we are still using them or need them, e.g. Papyrus-RT-Gerrit-mars, Papyrus-RT-Gerrit-master, Papyrus-RT-Nexus-Deploy, Papyrus-RT-StableRelease-0.7.1, etc.
On the codegen side we can get rid of all the *-CodegenRTS-* jobs now, but I don't know about the rest. Can you take a look and say whether there are jobs which we no longer need?
Papyrus-Gerrit-Master-All (disabled)
Papyrus-RT-CodegenRTS-BuildFrom-gerrit-Master (disabled)
Papyrus-RT-CodegenRTS-BuildFrom-gitroot-Triggered-gitpoll-PublishTo-repo (disabled)
Papyrus-RT-CodegenRTS-BuildFrom-gitroot-Triggered-nightly-PublishTo-nightly (disabled)
Papyrus-RT-Feature-Inheritance
Papyrus-RT-Gerrit-Codegen
Papyrus-RT-Gerrit-Common
Papyrus-RT-Gerrit-Core
Papyrus-RT-Gerrit-Cpp
Papyrus-RT-Gerrit-mars
Papyrus-RT-Gerrit-master (disabled)
Papyrus-RT-Gerrit-Migration
Papyrus-RT-Gerrit-neon.x (disabled)
Papyrus-RT-Gerrit-Profile
Papyrus-RT-Gerrit-RCPTT
Papyrus-RT-Gerrit-Releng
Papyrus-RT-Gerrit-Tests
Papyrus-RT-Gerrit-Tooling
Papyrus-RT-Installer
Papyrus-RT-Installer-Promotion (disabled)
Papyrus-RT-Mars-All
Papyrus-RT-Master-All
Papyrus-RT-Master-Codegen
Papyrus-RT-Master-Core
Papyrus-RT-Master-Product
Papyrus-RT-Master-Product-Integration
Papyrus-RT-Master-Product-Milestone
Papyrus-RT-Master-Product-Release
Papyrus-RT-Master-RCPTT
Papyrus-RT-Master-RCPTT(old) (disabled)
Papyrus-RT-Master-Tooling
Papyrus-RT-Nexus-Deploy (disabled)
Papyrus-RT-Product (disabled)
Papyrus-RT-Quality
Papyrus-RT-StableRelease-0.7.1 (disabled)
TEST-Papyrus-RT-CodegenRTS-BuildFrom-gitroot-Triggered-nightly-PublishTo-nightly (disabled)
--
Ernesto Posse
Zeligsoft
On Wed, Jan 4, 2017 at 11:03 AM Christian Damus <give.a.damus@xxxxxxxxx> wrote:
+1
cW
On Jan 4, 2017, 10:42 -0500, Ernesto Posse <eposse@xxxxxxxxxxxxx>, wrote:
I've updated the Master-Product job to keep only 3 as Benoit suggests.
Should we do the same for all jobs?
On Wed, Jan 4, 2017 at 3:22 AM MAGGI Benoit <Benoit.MAGGI@xxxxxx> wrote:
Hi Simon,
My 2 cents:
My usual practice is to keep 30 builds but reduce the number of artifacts.
It’s quite useful to keep logs but most of the time useless to keep old nightly artifacts.
For example, add 3 in the last field here [1].
Regards,
Benoit
1 : https://hudson.eclipse.org/papyrus-rt/view/Master%20(Neon)/job/Papyrus-RT-Master-Product/configure
De :papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part de Simon Redding
Envoyé : mardi 3 janvier 2017 19:58
À : 'papyrus-rt developer discussions' <papyrus-rt-dev@xxxxxxxxxxx>
Objet : [papyrus-rt-dev] Hudson disk usage
All,
It seems that the Papyrus-RT builds are consuming a lot of space on the Hudson build server. It looks like we keep the last 30 builds by default. I would like to reduce that to the last 10 builds to save space. Let me know if you have any concerns with this.
Regards,
Simon
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev--
Ernesto Posse
Zeligsoft
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev_______________________________________________--
Ernesto Posse
Zeligsoft
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev--_______________________________________________Ernesto Posse
Zeligsoft
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev