I've converted my fork of portmill to being a postgres app:
http://github.com/purp/portmill
All specs pass, coverage is still 100% (not hard for a trivial app =).
Bill, I'd need to work with you to tweak the database and deployment
host info. Florian, do you have a separate process that's
On Jan 6, 2010, at 7:49 AM, Jim Meyer wrote:
I've converted my fork of portmill to being a postgres app:
http://github.com/purp/portmill
All specs pass, coverage is still 100% (not hard for a trivial app =).
Bill, I'd need to work with you to tweak the database and deployment host
On 1/3/10 11:57 PM, Jordan K. Hubbard wrote:
On Jan 3, 2010, at 3:45 AM, C. Florian Ebeling wrote:
If somebody wanted to work on Portmill I offer my help with getting
started, and answer questions possibly coming up. It is all still on
my github account, but I haven't touched it in the last
I've looked at this a couple of times. Unfortunately, I wasn't able to get
CouchDB and the will_paginate gem to play nice (which Florian was obviously
able to do =) and have never had time to chase that down fully. I keep
thinking this must be really simple which prevents me from flipping it
On 2010-1-6 10:38 , C. Florian Ebeling wrote:
William Siegrist who looks after the other MP systems was
pushing into the direction of MySQL anyway
I don't remember it that way. He was against adding Yet Another DBMS to
the server without a good reason. MySQL was simply mentioned as what
Yes, I think you're right. Using an AR data persistence model that
shouldn't make a big difference, though.
Florian
On 06.01.2010, at 00:52, Joshua Root j...@macports.org wrote:
On 2010-1-6 10:38 , C. Florian Ebeling wrote:
William Siegrist who looks after the other MP systems was
pushing
On Jan 5, 2010, at 17:52, Joshua Root wrote:
On 2010-1-6 10:38 , C. Florian Ebeling wrote:
William Siegrist who looks after the other MP systems was
pushing into the direction of MySQL anyway
I don't remember it that way. He was against adding Yet Another DBMS to
the server without a good
On Jan 5, 2010, at 3:52 PM, Joshua Root wrote:
On 2010-1-6 10:38 , C. Florian Ebeling wrote:
William Siegrist who looks after the other MP systems was
pushing into the direction of MySQL anyway
I don't remember it that way. He was against adding Yet Another DBMS to
the server without a
Jordan K. Hubbard wrote:
Hey, that's life - things change! Thanks for being honest about
it, in any case, since I think that leaves the door open for any
volunteer(s) who still want to see package building / regression
testing sometime in the future. Anyone out there interested?
How
Hi Jordan,
I have secretly been working on a build server I call Portmill, which polls
the svn, and builds every
port that changes. Results get posted to a web app which presents them,
together with build logs (tails) for the ones that fail
How's this coming along? I just thought I'd
On Jan 3, 2010, at 3:45 AM, C. Florian Ebeling wrote:
If somebody wanted to work on Portmill I offer my help with getting
started, and answer questions possibly coming up. It is all still on
my github account, but I haven't touched it in the last half a year.
Sorry to give this probably
On Jun 6, 2009, at 3:21 PM, C. Florian Ebeling wrote:
I have secretly been working on a build server I call Portmill, which polls
the svn, and builds every
port that changes. Results get posted to a web app which presents them,
together with build logs (tails) for the ones that fail
How's
Just one suggestion, as we all pile on Florian's design: Can we
please try to do our best to resist the temptation of allowing the
perfect to become the enemy of the good enough? I too see a lot of
issues with Florian's portmill system, but I also know that things
tend to evolve rather
Moving this to a *.macports.org domain would make sense to make clear
that it is official. I am sure this is just where Florian is testing the
whole thing.
Yes, of course, and I think I mentioned it earlier somewhere. I'd
really like to see move the app to a macports subdomain. Same with
Most of that functionality can be embedded into javascript, which
avoids putting all the work on the backend dev (C.Florian).
Additionally, there are plenty of people who know Javascript/jQuery --
regardless of Ruby or PHP -- and can add it as a patch.
Just a thought.
On Jun 10, 2009, at
Looks great to me. Some feature requests, from an MacPorts user perspective.
When I'm considering using MacPorts to help me out with a build, I need to
know whether it's going to succeed. The first thing I want to do is search
for a specific port to see whether it will build. So these might
Florian did a really great job here.
Thanks. :)
I can understand reasons for
developing that more or less in private as I assume he has been
experimenting with that a lot before he came up with something usable.
But I agree that it would be better now to have it in the MacPorts
repository.
I notice it flagged the mldonkey build as failed, but in fact it was one of
mldonkey's dependencies which failed. Perhaps there is a way that could be
made more clear in the interface.
Yes, it did mark mldonkey as failure, but take it as what it really
is: a change event picked up in the
On Tue, Jun 9, 2009 at 3:19 AM, Jim Meyerj...@geekdaily.org wrote:
On 6/8/09 4:56 PM, Jeremy Lavergne wrote:
I'll take on the rewriting to PHP this summer if it needs to be done.
And I'll volunteer to help with the Rails upkeep if not. =]
Thanks, greately appreciated! Just have look at the
--On 8 June 2009 20:29:19 -0400 Jeremy Lavergne
jer...@lavergne.gotdns.org wrote:
There's a difference between a crash and a failed compilation in that the
system can't just catch it. Apple also pays people to look at those
crash reports.
Paid or not, if you can't see a problem then you
2009/6/9 Ian Eiloart i...@sussex.ac.uk:
--On 8 June 2009 20:29:19 -0400 Jeremy Lavergne jer...@lavergne.gotdns.org
wrote:
There's a difference between a crash and a failed compilation in that the
system can't just catch it. Apple also pays people to look at those
crash reports.
Paid or
On 2009-06-08 22:36, Ryan Schmidt wrote:
I imagine you've been working on this for awhile, and since this is
an open source project, it would have been nice to know you were
working on this, and to have the code in the MacPorts repository (the
users area would have been a good place for
On 2009-06-09 21:08, Andre Stechert wrote:
Note that we currently allow users to log crash reports using TRAC --
an automated build failure notification just makes it easier for the
user and, if appropriately designed (as Ian said), easier for us too.
Once the logging proposal has been
--On 6 June 2009 12:43:36 -0700 Jordan K. Hubbard j...@apple.com wrote:
and if there are no users of a port to report errors, then who really
cares if it's broken?
All the users who come to MacPorts, give it a go, then go away without
reporting the errors that cause them to give up. It's
On Jun 6, 2009, at 15:36, Jeremy Lavergne wrote:
http://portmill.florianebeling.com/ is doing a default build for
all ports if I'm not mistaken.
I'm just getting back to this thread.
Thank you for your work on this, Florian!
Some friendly criticism:
I imagine you've been working on this
On Jun 8, 2009, at 2:18 AM, Ian Eiloart wrote:
So, and automated test suite would (a) get errors diagnosed and
fixed quicker, (b) reduce the number of errors as a result, and (c)
give us a way of flagging them before a user starts a 20 minute
build process.
I have been reading this
On Jun 8, 2009, at 15:49, Scott Haneda wrote:
On Jun 8, 2009, at 2:18 AM, Ian Eiloart wrote:
So, and automated test suite would (a) get errors diagnosed and
fixed quicker, (b) reduce the number of errors as a result, and
(c) give us a way of flagging them before a user starts a 20
minute
On Jun 8, 2009, at 5:46 PM, Ryan Schmidt wrote:
It is also a very good way to get an exact idea of what ports are
being installed. You can then see that port x has been installed
400 times, 390 of those with no issues, 10 of those with some issue.
I proposed this two years ago but was shot
On Mon, Jun 08, 2009 at 03:36:21PM -0500, Ryan Schmidt said:
[...]
You said you wrote this with Rails and CouchDB. While I understand the
desire to write using technologies you're familiar with, MacPorts is
written in Tcl, and the main MacPorts web site is written in PHP and
MySQL, and it
I'll take on the rewriting to PHP this summer if it needs to be done.
On Jun 8, 2009, at 7:54 PM, Bryan Blackburn wrote:
Of course it doesn't really lower the barrier if someone knows Rails
but not
PHP, especially when quite a bit of code has already been written.
While
trying to stay
2009/6/8 Scott Haneda talkli...@newgeo.com:
On Jun 8, 2009, at 2:46 PM, Ryan Schmidt wrote:
I proposed this two years ago but was shot down because this was considered
an
invasion of privacy and people didn't want MacPorts phoning home. I had
wanted
to have a nice status display on the
There's a difference between a crash and a failed compilation in that
the system can't just catch it. Apple also pays people to look at
those crash reports.
We're almost entirely unpaid volunteers with a variable body count.
On Jun 8, 2009, at 8:26 PM, Andre Stechert wrote:
If a program
On 6/8/09 4:56 PM, Jeremy Lavergne wrote:
I'll take on the rewriting to PHP this summer if it needs to be done.
And I'll volunteer to help with the Rails upkeep if not. =]
--j
On Jun 8, 2009, at 7:54 PM, Bryan Blackburn wrote:
Of course it doesn't really lower the barrier if someone
On 6/8/09 6:17 PM, Jim Meyer wrote:
On 6/8/09 2:46 PM, Ryan Schmidt wrote:
It is also a very good way to get an exact idea of what ports are
being installed. You can then see that port x has been installed 400
times, 390 of those with no issues, 10 of those with some issue.
I proposed this
That's really cool - thanks for taking so much initiative on this one!
Bill has already volunteered MacOSForge resources (which I endorse) towards
creating a buildbot, the definition for which I'm sure is open to
discussion, so perhaps you and he could work together in figuring out how to
On Jun 6, 2009, at 3:43 PM, Jordan K. Hubbard wrote:
I know that the word packaging is kind of a dirty word in MacPorts-
land (perhaps largely due to the fact that certain people just won't
stop harping about it :-), so maybe it's time for a new(er) topic in
an old conversation: Testing.
On Jun 6, 2009, at 3:43 PM, Jordan K. Hubbard wrote:
Wouldn't it be easier to simply make the creation and homing of a
testing framework a bigger priority? I've said it many times, but
I'll say it again: If someone can handle the creation part, I'm
fairly confident that the homing
On Jun 6, 2009, at 12:50 PM, Jeff Johnson wrote:
What is the actual connection between testing and the graph you
have included?
Um. OK, sure, I'll spell it out.
1. We have a lot of ports. The number of ports we have is growing at
3-4 digit rates a year.
2. The essential mission of any
On Jun 6, 2009, at 1:01 PM, Daniel J. Luke wrote:
There have been a few attempts at this in the past - what was wrong
with them again? (I can remember at least three - your chroot build
scripts, wbb4's builds that auto generated a website that listed
failures and successes, and blb's mpab
http://portmill.florianebeling.com/ is doing a default build for all
ports if I'm not mistaken.
On Jun 6, 2009, at 4:35 PM, Jordan K. Hubbard wrote:
They all kinda worked but not well enough that nobody wanted to
actually host them anywhere since they were more clearly science
On Jun 6, 2009, at 13:31, Jordan K. Hubbard wrote:
What I'm essentially proposing is that a testing harness be built
which:
1. Iterates through all Portfiles on the system, save those
explicitly marked Broken (which will be periodically swept and
marked for extermination after a short
On Jun 6, 2009, at 12:43 PM, Jordan K. Hubbard wrote:
I know that the word packaging is kind of a dirty word in MacPorts-
land (perhaps largely due to the fact that certain people just won't
stop harping about it :-), so maybe it's time for a new(er) topic in
an old conversation: Testing.
On Sat, Jun 6, 2009 at 9:43 PM, Jordan K. Hubbardj...@apple.com wrote:
I know that the word packaging is kind of a dirty word in MacPorts-land
(perhaps largely due to the fact that certain people just won't stop harping
about it :-), so maybe it's time for a new(er) topic in an old
I forgot the link, but it is the one Jeremy posted already:
http://portmill.florianebeling.com/
On Sun, Jun 7, 2009 at 12:21 AM, C. Florian
Ebelingflorian.ebel...@gmail.com wrote:
On Sat, Jun 6, 2009 at 9:43 PM, Jordan K. Hubbardj...@apple.com wrote:
I know that the word packaging is kind of
On Jun 6, 2009, at 3:12 PM, William Siegrist wrote:
I suggest we setup a buildbot master at build.macports.org and have
it (at least initially) test building/installing/testing base and
ports after each commit. I think for an initial effort, in light of
all earlier attempts failing, we
On Jun 6, 2009, at 3:21 PM, C. Florian Ebeling wrote:
This has also been my view, and I have secretly been working on a
build server I call Portmill, which polls the svn, and builds every
port that changes. Results get posted to a web app which presents
them, together with build logs (tails)
46 matches
Mail list logo
