Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Hudson problem, moving built update site to downloads directory 
Hi Martin

Thank you for reviewing - it is hard to find somebody spending time on that.

- Why are the nightly builds listed first? Typically these are for "contributers" and consumers are interested in the more stable ones, so listing the stable ones first is mostly preferred.

> We are still working on the project website (download page). The download page is auto generated from our download area (build.eclipse.org /downloads/scout/repositoryOverview.xml). 

- Why is your version number not 0.x.y when you're still in Incubation ?

> Applications build on Scout (Version 3.5.5) are released and installed with many customers worldwide. Since downgrading of version numbers is not that easy and we do not plan to maintain two P2 repositories (one for release train another for our customers) we keep the version > 3.5.5. (see also attached mail)

- Why is the "incubation egg" icon missing from your download site?

> We simply forgot to add the incubation egg there. It will be added with the next update. Thank you for reminding.


- Andy 


-----Ursprüngliche Nachricht-----
Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Im Auftrag von Oberhuber, Martin
Gesendet: Montag, 28. Februar 2011 15:21
An: Cross project issues
Betreff: Re: [cross-project-issues-dev] Hudson problem, moving built update site to downloads directory

Hello Andreas,

Your post got me interested so I looked at the Scout download pages:
http://www.eclipse.org/scout/downloads/

Couple questions from my "uninformed consumer" point of view -

- Why are the nightly builds listed first? Typically these are for "contributers" and consumers are interested in the more stable ones, so listing the stable ones first is mostly preferred.

- Why is your version number not 0.x.y when you're still in Incubation ?

- Why is the "incubation egg" icon missing from your download site?

I'm not meaning to police the Eclipse rules about incubation state here - there might be good reasons for not adhering - but note that the rules about incubation state have been made for a good reason, in order to inform and protect consumers in a consistent manner and thus helping projects prosper. As architecture council members / mentors, we are meant to help projects best interact with the Community so I thought I'd mention this.

Thanks,
Martin
--
Martin Oberhuber, SMTS / Product Architect - Development Tools, Wind River
direct +43.662.457915.85  fax +43.662.457915.6


-----Original Message-----
From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Andreas Hoegger
Sent: Saturday, February 26, 2011 1:53 PM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Hudson problem, moving built update site to downloads directory

Hi Matt

We solved this issue using a cron. 
Resources to publish are copied into a publish stagingArea folder fetched by a cron.
See: 
  - build.eclipse.org   /downloads/scout/publish.sh
  - releng project SVN http://dev.eclipse.org/svnroot/technology/org.eclipse.scout/scout.builder/trunk/

If you need any help let me know.

-Andy

Von: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] Im Auftrag von Matthew Heitz
Gesendet: Freitag, 25. Februar 2011 21:18
An: cross-project-issues-dev@xxxxxxxxxxx
Betreff: [cross-project-issues-dev] Hudson problem, moving built update site to downloads directory


Hi, 

 I'm setting up builds on Hudson for a new project, and having problems getting the update site moved to the downloads directory.  My build.xml kicks off promote.xml, which should do the job.  Here's the output: 

    [echo] Search /opt/users/hudsonbuild/workspace/cbi-edt-nightly/build/ for folders matching "N*" ...
   [echo] Found /opt/users/hudsonbuild/workspace/cbi-edt-nightly/build/N201102251430
   [echo] Found /opt/users/hudsonbuild/workspace/cbi-edt-nightly/build/N201102251438
   [echo] Promote build in /opt/users/hudsonbuild/workspace/cbi-edt-nightly/build/N201102251438 ...
   [echo] /usr/bin/rsync -a --exclude=eclipse/ /opt/users/hudsonbuild/workspace/cbi-edt-nightly/build/N201102251438 /home/data/httpd/download.eclipse.org/edt/downloads/drops/nightly/0.7.0/
   [exec] rsync: recv_generator: mkdir "/home/data/httpd/download.eclipse.org/edt/downloads/drops/nightly/0.7.0/N201102251438" failed: Permission denied (13)


 When logged in to build.eclipse.org, I verified that the directories exist, and their permissions are 775.  In my promote.properties file I have targetGroup=tools.edt.  My account is a member of tools.edt, and tools.edt shows up when I do ls -l on the directories. 

 Any ideas? 

 Thanks,
 Matt
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--- Begin Message --- 
If memory serves, Scout intends to graduate when they release. Upon
graduation, a project can assume whatever release number they feel best
serves their community. So, 3.7.0 is fine. Milestones can be so-named as
well

In the meantime, however, Scout is incubating and should be careful to
make sure that they conform to incubation-conforming downloads labelling
rules...

http://wiki.eclipse.org/Development_Resources/HOWTO/Parallel_IP_Process

Wayne

On 01/31/2011 05:51 AM, Nicolas Bros wrote:
> Hi,
>
> I would like to point you to the discussion here
> on cross-project-issues-dev titled : "Changing Eclipse BIRT Indigo
> Version Number to BIRT 3.7", that discusses version numbering.
> Also, projects in incubation are normally required to have a version
> strictly lower than 1.0. So, I think you'd need a formal exception if
> you don't want to follow this rule.
>
> On Mon, Jan 31, 2011 at 11:41 AM, Andreas Hoegger
> <Andreas.Hoegger@xxxxxxxxx <mailto:Andreas.Hoegger@xxxxxxxxx>> wrote:
>
>     If nobody mind the Eclipse Scout project will join the Indigo
>     release train with version 3.7.0 and Incubation state.
>
>     Applications build on Scout (Version 3.5.5) are released and
>     installed with many customers worldwide. Since downgrading of
>     version numbers is not that easy and we do not plan to maintain two
>     P2 repositories (one for release train another for our customers) we
>     keep the version > 3.5.5.
>
>     Hope everybody is fine with that.
>
>     Andreas Hoegger
>
>     ______________________________________________________
>     BSI Business Systems Integration AG
>     Andreas Michael Hoegger
>     Eclipse Scout Project Lead
>     Täfernstrasse 16a
>     CH-5405 Baden
>
>     business (direct): +41 (0)56 484 16 87 <tel:+41564841687>
>     mobile:            +41 (0)78 615 29 29 <tel:+41786152929>
>     mail:              andreas.hoegger@xxxxxxxxx
>     <mailto:andreas.hoegger@xxxxxxxxx>
>     web:               www.bsiag.com <http://www.bsiag.com>
>
>     Meet me at:
>     - EclipseCon 2011 Santa Clara, California 2011 March 21 - 24
>     (http://www.eclipsecon.org/2011)
>     ______________________________________________________
>
>     _______________________________________________
>     cross-project-issues-dev mailing list
>     cross-project-issues-dev@xxxxxxxxxxx
>     <mailto:cross-project-issues-dev@xxxxxxxxxxx>
>     https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
>
>
>
> --
> Nicolas Bros
> R&D
> tel: 06 75 09 19 88
> nbros@xxxxxxxxxxxxxxxx <mailto:nbros@xxxxxxxxxxxxxxxx>
> nbros.mia@xxxxxxxxx <mailto:nbros.mia@xxxxxxxxx>
> Mia-Software, 410 clos de la Courtine
> 93160 Noisy-le-Grand
> http://www.mia-software.com
> .: model driven agility :.
>
>
>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

--- End Message ---

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Back to the top