As far as I understand you've talked about milestone releases. But what is with a nightly build repository?

br, Sven

-- sent by phone

Am 06.01.2010 um 20:34 schrieb Gurkan Erdogdu <[email protected]>:

Hi Joe;

thks for configuring Hudson. When we were releasing in Incubator, I followed the following path for releasing OWB

1* Using "mvn release:prepare" and "mvn release:perfom -Prelease" goals. These actions do the following,
   * Creates a tag in SVN
   * Creates maven artifacts in staging area
       This area is specified by trunk/pom.xml as
       <properties>
         .....
         <siteId>/OWB/1.0.0-M3-rc2/plugins</siteId>
       </properties>
And URL is specified by
       <repository>
           <id>apache.openwebbeans.stage</id>
<url>scp://people.apache.org/home/gerdogdu/public_html/ staging-repo/${siteId}</url>
       </repository>

2* For deploying zip, tar etc. main distribution, using mvn deploy
   * Checkout tag version from SVN
   * cd "distribution" project folder
   * mvn deploy -Prelease
   * This will create distributions in staging area
        This area is specified by trunk/distribution/pom.xml
      <properties>
         <siteId>/OWB/1.0.0-incubating-M3-rc2/distribution</siteId>
      </properties>


2* Then VOTE
* If VOTE is successful, I manually copy distribution artifacts into proper places
     - zip, tar archives into "dist/" location
     - move maven artifacts into m2-incubator-repository


I really do not know how to automate those tasks or do we really need for automation? Some projects use Nexus Repository for releasing process. Look at https://issues.apache.org/jira/browse/INFRA-1896 . But I do not have so much experienced with it.

I would like to release M4 of the OWB in couple of next weeks.

Thks;

--Gurkan



________________________________
From: Joseph Bergmark <[email protected]>
To: [email protected]
Sent: Wed, January 6, 2010 9:08:42 PM
Subject: Re: artifacts in repos

I have set up a basic daily build on Hudson for OpenWebBeans-trunk.

http://hudson.zones.apache.org/hudson/job/OpenWebBeans-trunk/

Where do we want to go with this next?  Should it be publishing the
artifacts somewhere, should we use it to update the website?

Sincerely,

Joe

2010/1/5 Joseph Bergmark <[email protected]>

Thanks for the link Sven. I went ahead and opened an ticket to have an
account created.

Sincerely,

Joe

2010/1/1 Sven Linstaedt <[email protected]>

I have found this one [1] during my search. According to the faq, all you
need to do is opening a issue for your request.

I have needed nightly builds for private purposes. Setting OWB up in
hudson
with various reporting plugins was a task of less an hour.

br, Sven


[1] http://wiki.apache.org/general/Hudson


PS: And before I forget it completely... happy new year to all :)



2010/1/1 Gurkan Erdogdu <[email protected]>

Hi;

AFAIK we can use Hudson that infra. provides as our build server. Does
anybody has experience with it?

Thanks;


--Gurkan


________________________________
From: Matthias Wessendorf <[email protected]>
To: [email protected]
Sent: Wed, December 30, 2009 5:02:48 PM
Subject: artifacts in repos

Hey,

the artifacts in here:


http://people.apache.org/repo/m2-snapshot-repository/org/apache/openwebbeans/

are kinda "old". Also, the versioning is (maybe) a bit confusing. As
the 1.0.0-SNAPSHOT never gets incremented
on trunk (yeah, I know the M2, M3 releases are deployed on the
incubator snapshot repo).

Any intention to
a) update the artifacts (where is build server)
b) change the versioning ?

-Matthias

--
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf



___________________________________________________________________
Yahoo! Türkiye açıldı!  http://yahoo.com.tr
İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sun uyor!







___________________________________________________________________
Yahoo! Türkiye açıldı!  http://yahoo.com.tr
İnternet üzerindeki en iyi içeriği Yahoo! Türkiye sizlere sunuyo r!

Reply via email to