| Re: [papyrus-rt-dev] Hudson disk usage |
+1 for storing the xml file on the gitEven if git is able to store binaries, I prefer usually not to do so. Matter of readability when you browse the repo, and IMO I prefer to get something for the long term that I know I will always be able to read ;-)CheersRémi2017-01-10 16:29 GMT+01:00 Ernesto Posse <eposse@xxxxxxxxxxxxx>:It is an XML file indeed. Ok, I'll store in the repo under releng/hudson.On Tue, Jan 10, 2017 at 10:24 AM Christian Damus <give.a.damus@xxxxxxxxx> wrote:Hi, Rémi,Git handles binaries just fine, but I’m pretty sure these are XML files. I would prefer to keep these in the releng tree in git, maybe under a “releng/hudson” folder.
Cheers,
ChristianGood question, but I unfortunately don't have the answer ;-)What is the kind of file? xml one?What I see as options:- git repo, in the releng area, only accessible with a tag? Would be good only if the file is not a binary one.- download.eclipse.org, even if I do not feel the download server is for this kind of artifact. At least, this is a place where we can store binaries easily, and we could setup a folder where we could save our build configs.- wiki is not the place for such artifacts.So I would say for now the download server would be the best option until someone has a better idea.Regards,Rémi2017-01-10 16:08 GMT+01:00 Ernesto Posse <eposse@xxxxxxxxxxxxx>:
I did, but I just have the file locally in my machine. Where should we store it?
On Tue, Jan 10, 2017 at 3:13 AM Remi Schnekenburger <rschnekenburger@xxxxxxxxxxxxxxxxx> wrote:Hi Ernesto,Thanks a lot for the cleaning!For this one: Papyrus-RT-StableRelease-0.7.1: did you save the build configuration before deleting?Cheers,Rémi2017-01-09 19:10 GMT+01:00 Ernesto Posse <eposse@xxxxxxxxxxxxx>:
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