Re: [flux-dev] Meeting Minutes - July 24, 2014

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

I asked around (on twitter) and got some
examples. There are various ways to do it. eGit publishes from within the
Maven build code, and the location is parameterized in the hudson job configuration.
Here is the job:

https://hudson.eclipse.org/egit/job/egit/configure

The publishing is done from an extra
pom file that just performs an Ant copy:

http://git.eclipse.org/c/egit/egit.git/tree/org.eclipse.egit.repository/pom.xml

The other approach is to add an extra
post-build step in the Hudson configuration. This is probably the easiest
answer, since when running the build locally you wouldn't want to publish
anyway:

https://hudson.eclipse.org/swtbot/job/swtbot-tycho/configure

Anyone logged in as a committer can
view these job configurations.

As far as updating the download page,
the easiest approach is to have a PHP download page that automatically
generates a build list based on the available directories. This makes it
easy to for example clean up old builds, promote builds, etc, and the download
page just refreshes automatically. Updating a download page listing from
a build tends to be brittle. I have copied the generic PHP download page
used by Eclipse and Orion into the Flux download area. If download directories
are added by builds, the page should just refresh automatically.

John




From:      
 Martin Lippert <mlippert@xxxxxxxxx>
To:      
 Flux developer discussions
<flux-dev@xxxxxxxxxxx>, 
Date:      
 07/30/2014 06:40 AM
Subject:    
   Re: [flux-dev]
Meeting Minutes - July 24, 2014
Sent by:    
   flux-dev-bounces@xxxxxxxxxxx

---

Hey John,

this is great, thanks for that. Is there a good and small example of a
tycho build on Hudson that publishes download artifacts (incl. a p2 repo)
and updates the download page automatically, so that we can see (and copy)
how that works?

Cheers,
-Martin



> I have requested a Flux Hudson instance.  Flux already has a
download area assigned to it. I have put a placeholder page in there for
now: 
> 
> http://download.eclipse.org/flux/
> 
> This is also a good place to put a public p2 repository. Alternatively
we can store build artifacts in the public Eclipse Nexus/Maven instance
at https://repo.eclipse.org





> 
> John 
> 
> 
> 
> 
> From:        Martin Lippert <mlippert@xxxxxxxxx>
> To:        Flux developer discussions <flux-dev@xxxxxxxxxxx>,
> Date:        07/25/2014 03:59 AM 
> Subject:        Re: [flux-dev] Meeting Minutes
- July 24, 2014 
> Sent by:        flux-dev-bounces@xxxxxxxxxxx 
> 
> 
> 
> Hey John,
> 
> > Sorry I had to miss today due to a conflict. Looks like lots
of interesting work going on. 
> 
> No problem. See you next week on the call.
> 
> > Nieraj should I request a Hudson configuration for Flux so the
headless build can be run there? 
> 
> Yes, a hudson instance would be great. I think we are going to run
a tycho build on there that will produce two things in the end:
> - a p2 repository for the Flux Eclipse integration (so that people
can install that from this p2 repo)
> - a “headless JDT service” product that we can run on Linux and
OSX (and deploy to CF)
> 
> I guess you know what we need to do to get a publicly accessible p2
repo up somewhere as well as a download area for the headless JDT service
product? (and maybe some others in the future)
> 
> Cheers,
> -Martin
> 
> 
> 
> 
> > 
> > John 
> > 
> > 
> > 
> > 
> > From:        Martin Lippert <mlippert@xxxxxxxxx>
> > To:        Flux developer discussions <flux-dev@xxxxxxxxxxx>,
> > Date:        07/24/2014 12:42 PM 
> > Subject:        [flux-dev] Meeting Minutes
- July 24, 2014 
> > Sent by:        flux-dev-bounces@xxxxxxxxxxx
> > 
> > 
> > 
> > Things are coming together from the various parts… :-)
> > 
> > https://wiki.eclipse.org/Flux/Meeting_minutes/20140724
> > 
> > Cheers,
> > Martin
> > 
> > 
> > _______________________________________________
> > flux-dev mailing list
> > flux-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/flux-dev
> > 
> > 
> > _______________________________________________
> > flux-dev mailing list
> > flux-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> > https://dev.eclipse.org/mailman/listinfo/flux-dev
> 
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/flux-dev
> 
> 
> _______________________________________________
> flux-dev mailing list
> flux-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> https://dev.eclipse.org/mailman/listinfo/flux-dev

_______________________________________________
flux-dev mailing list
flux-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/flux-dev