You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bloodhound.apache.org by Gavin McDonald <ga...@16degrees.com.au> on 2012/02/01 00:09:41 UTC
Catching up
Hi all,
I've been away for 2 weeks on personal leave but am now ready to join in
with whatever needs doing.
My initial goals were to help getting the infrastructure + related software
up and running.
I notice Tony of Infra has created a VM. (someone mentioned that it was
disabled for password logins, good! it
will stay that way, get a key!)
Please can I have a summary of the situation so far, what's been done, what
are we waiting on, etc, what queries
do you have. I'll get started when I know what we need doing first.
Thanks
Gav...
Re: Catching up
Posted by Olemis Lang <ol...@gmail.com>.
Hi !
On Fri, Feb 10, 2012 at 1:21 AM, Gavin McDonald <ga...@16degrees.com.au> wrote:
>
> > -----Original Message-----
> > From: Olemis Lang [mailto:olemis@gmail.com]
> > Sent: Monday, 6 February 2012 11:25 PM
> > To: bloodhound-dev@incubator.apache.org
> > Subject: Re: Catching up
> >
> > On Mon, Feb 6, 2012 at 6:58 AM, Gary <ga...@wandisco.com> wrote:
> > >
[...]
>
> > >
> > I believe that Buildbot and Jenkins are the readily available choices. It
> would
> > be nice to have a solution that Trac/Bloodhound would be able to integrate
> > with but it is not a strict necessity.
> > >
> >
> > http://trac-hacks.org/wiki/BuildbotPlugin
> > http://trac-hacks.org/wiki/TracBuildbotIntegration
> > https://github.com/rbosetti/trac-buildbot-watcher
>
> Not sure we need any of that at this stage just to check if code from svn
> will build.
>
ok . that was JFTR ;)
>
> >
> > If you ask me ... I'd rather go for Jenkins (... but mainly because I'm
> more
> > familiar with it ;)
> >
> > https://wiki.jenkins-ci.org/display/JENKINS/Trac+Plugin
> > https://wiki.jenkins-ci.org/display/JENKINS/Trac+Publisher+Plugin
> > http://trac-hacks.org/wiki/HudsonTracPlugin
>
> Again, that might or might not come later, I'm more concerned with general
> CI
> build stuff rather than integration. Integrating our CI systems with a
> development
> instance is not my idea of fun at the moment. Let's stick to just making
> sure the
> code passes our build tests.
>
ok . Below I mention general (tactic | strategic) decisions I (always)
make regarding testing + CI of Python / Trac projects ;)
So far JFTR . With time I hope this will be improved .
- Tests are run using setuptools test command
* Functional dependencies (libraries, ...) are declared in setup.py
`install_requires` , so should be installed automatically
* Libraries needed for testing purposes are declared in
`tests_require` so should be installed automatically every time
setuptools `test` command is executed
* Lightweight test cases & infrastructure (e.g. mock objects ,
no physical Trac environment required , in-memory
Trac database sqlite::memory: , ... )
* The subset of the tests defined in an specific module can be run
using -m option
* For CI (at least using Jenkins ;) it's necessary to generate
JUnit XML report . This will be possible by adding a library
supporting this (e.g. unittest-xml-reporting [1]_ ) and selecting the
test runner using -r option of setuptools test command .
e.g. in general , in order to run the test suite it will only be
needed to execute a command similar to
{{{
#!sh
$ python setup.py test -r <module.TestRunnerClass> -m <module>
}}}
at least that's the idea ;)
... like I said this is JFTR . I know you'll need to have code + tests
so as to play with it
;)
BTW . Tests are implemented in Dashboard plugin . I often don't see
the need for testing a theme , but it's possible to have e.g. some
twill-fu in there so as to make some assertions
;)
> > > At this point there is still no real code in the repositories to for CI
> to test and
> > so I think that it would be good if we could ask Olemis to contribute his
> work
> > on the theme and dashboard to the svn repositories. That will also have
> the
> > advantage that everyone can play with his code and contribute patches
> back.
> > I'm hoping to get some code down in there too shortly.
>
> what about a main core dump, are we going to get a specific tag of the trac
> instance
> in svn to get going with?
>
I guess that should be the case if patches will be applied on top of
Trac distribution (and some facts make me think that's what's going to
happen ... at some point in the future ;)
If this is the case then IMO it'd be nice to have a build job to run
Trac test suite ensure those patches don't break the test cases in
there ...
> >
> > In there you'll find a few test cases , With time I can provide
> instructions so as
> > to run the test suite (or part of it ;) , especially in a CI environment .
> During
> > this week I'll also try to do the same thing @ testrun.org (Jenkins /
> Hudson) ;
> > just to satisfy my curiosity and try to be at least a bit accurate
> sometimes ;)
>
> From my perspective, I don’t mind which we use. I will set up a Buildbot
> build
> once I know what the tests are. I will also do the same for our Jenkins
> instance, though
> once that is up I tend to leave that for other committers to then
> tweak/play/lookafter.
>
ok
.. [1] PyUnit-based test runner with JUnit like XML reporting
(http://pypi.python.org/pypi/unittest-xml-reporting/1.0.3)
--
Regards,
Olemis
Facebook => http://www.facebook.com/olemis
Twitter => http://www.twitter.com/olemislc (@olemislc)
Blog ES => http://simelo-es.blogspot.com
Blog EN => http://simelo-en.blogspot.com
Quora => http://www.quora.com/olemis
Youtube => http://youtube.com/user/greatsoftw
Featured article : Identificando números primos con expresión regular en Perl
http://feedproxy.google.com/~r/simelo-news/~3/BHr859OSndo/identificando-numeros-primos-con.html
Tweet: yo no puedo creer q haya pasado inadvertido el 1/2/12 12:12 ...
@elainediaz2003 no dijo na' ... OMG ! ... much more coming soon ;) #fb
Follow @olemislc Reply Retweet 12:59 Feb-01
Get this email app!
Get a signature like this. CLICK HERE.
RE: Catching up
Posted by Gavin McDonald <ga...@16degrees.com.au>.
> -----Original Message-----
> From: Olemis Lang [mailto:olemis@gmail.com]
> Sent: Monday, 6 February 2012 11:25 PM
> To: bloodhound-dev@incubator.apache.org
> Subject: Re: Catching up
>
> On Mon, Feb 6, 2012 at 6:58 AM, Gary <ga...@wandisco.com> wrote:
> >
> > Hi,
> >
>
> :)
>
> [...]
> >
> >
> > As noted we have the VM on which an instance of Trac is running. We
could
> do with deciding on how various types of users should be able to interact
> with this - and therefore we probably need to know if there are any rules
> Apache have for this. So do we want (or are we allowed):
> >
> > * Full anonymous access for wiki page creating/editing and ticket
> > opening/closing or
> > * User self-registration for the same actions
> >
> > or any other options?
>
>
> Maybe this ?
>
> http://trac-hacks.org/wiki/AuthOpenIdPlugin
>
> [...]
> >
> >
> > Particular work I am interested in getting arranged is CI. Is this
something
> that Gavin would be able to get involved with or have recommendations for?
> I believe that Buildbot and Jenkins are the readily available choices. It
would
> be nice to have a solution that Trac/Bloodhound would be able to integrate
> with but it is not a strict necessity.
> >
>
> http://trac-hacks.org/wiki/BuildbotPlugin
> http://trac-hacks.org/wiki/TracBuildbotIntegration
> https://github.com/rbosetti/trac-buildbot-watcher
Not sure we need any of that at this stage just to check if code from svn
will build.
>
> If you ask me ... I'd rather go for Jenkins (... but mainly because I'm
more
> familiar with it ;)
>
> https://wiki.jenkins-ci.org/display/JENKINS/Trac+Plugin
> https://wiki.jenkins-ci.org/display/JENKINS/Trac+Publisher+Plugin
> http://trac-hacks.org/wiki/HudsonTracPlugin
Again, that might or might not come later, I'm more concerned with general
CI
build stuff rather than integration. Integrating our CI systems with a
development
instance is not my idea of fun at the moment. Let's stick to just making
sure the
code passes our build tests.
>
> > At this point there is still no real code in the repositories to for CI
to test and
> so I think that it would be good if we could ask Olemis to contribute his
work
> on the theme and dashboard to the svn repositories. That will also have
the
> advantage that everyone can play with his code and contribute patches
back.
> I'm hoping to get some code down in there too shortly.
what about a main core dump, are we going to get a specific tag of the trac
instance
in svn to get going with?
> >
>
> afaict , there's no problem for me to do so . Nonetheless I'll have to
follow
> the development in Apache svn repos from a distance (... as I have no
> commit access in there ...)
>
> In there you'll find a few test cases , With time I can provide
instructions so as
> to run the test suite (or part of it ;) , especially in a CI environment .
During
> this week I'll also try to do the same thing @ testrun.org (Jenkins /
Hudson) ;
> just to satisfy my curiosity and try to be at least a bit accurate
sometimes ;)
>From my perspective, I dont mind which we use. I will set up a Buildbot
build
once I know what the tests are. I will also do the same for our Jenkins
instance, though
once that is up I tend to leave that for other committers to then
tweak/play/lookafter.
Having some code in our svn and some test cases will be great, I can then do
something :)
Gav...
>
> --
> Regards,
>
> Olemis
>
> Facebook => http://www.facebook.com/olemis Twitter
> => http://www.twitter.com/olemislc (@olemislc) Blog ES => http://simelo-
> es.blogspot.com Blog EN => http://simelo-en.blogspot.com Quora
> => http://www.quora.com/olemis Youtube =>
> http://youtube.com/user/greatsoftw
>
> Featured article : Identificando números primos con expresión regular en
> Perl http://feedproxy.google.com/~r/simelo-
> news/~3/BHr859OSndo/identificando-numeros-primos-con.html
> Tweet: yo no puedo creer q haya pasado inadvertido el 1/2/12 12:12 ...
> @elainediaz2003 no dijo na' ... OMG ! ... much more coming soon ;) #fb
> Follow @olemislc Reply Retweet 12:59 Feb-01
> Get this email app!
> Get a signature like this. CLICK HERE.
Re: Catching up
Posted by Olemis Lang <ol...@gmail.com>.
On Mon, Feb 6, 2012 at 6:58 AM, Gary <ga...@wandisco.com> wrote:
>
> Hi,
>
:)
[...]
>
>
> As noted we have the VM on which an instance of Trac is running. We could do with deciding on how various types of users should be able to interact with this - and therefore we probably need to know if there are any rules Apache have for this. So do we want (or are we allowed):
>
> * Full anonymous access for wiki page creating/editing and ticket
> opening/closing or
> * User self-registration for the same actions
>
> or any other options?
Maybe this ?
http://trac-hacks.org/wiki/AuthOpenIdPlugin
[...]
>
>
> Particular work I am interested in getting arranged is CI. Is this something that Gavin would be able to get involved with or have recommendations for? I believe that Buildbot and Jenkins are the readily available choices. It would be nice to have a solution that Trac/Bloodhound would be able to integrate with but it is not a strict necessity.
>
http://trac-hacks.org/wiki/BuildbotPlugin
http://trac-hacks.org/wiki/TracBuildbotIntegration
https://github.com/rbosetti/trac-buildbot-watcher
If you ask me ... I'd rather go for Jenkins (... but mainly because
I'm more familiar with it ;)
https://wiki.jenkins-ci.org/display/JENKINS/Trac+Plugin
https://wiki.jenkins-ci.org/display/JENKINS/Trac+Publisher+Plugin
http://trac-hacks.org/wiki/HudsonTracPlugin
> At this point there is still no real code in the repositories to for CI to test and so I think that it would be good if we could ask Olemis to contribute his work on the theme and dashboard to the svn repositories. That will also have the advantage that everyone can play with his code and contribute patches back. I'm hoping to get some code down in there too shortly.
>
afaict , there's no problem for me to do so . Nonetheless I'll have to
follow the development in Apache svn repos from a distance (... as I
have no commit access in there ...)
In there you'll find a few test cases , With time I can provide
instructions so as to run the test suite (or part of it ;) ,
especially in a CI environment . During this week I'll also try to do
the same thing @ testrun.org (Jenkins / Hudson) ; just to satisfy my
curiosity and try to be at least a bit accurate sometimes ;)
--
Regards,
Olemis
Facebook => http://www.facebook.com/olemis
Twitter => http://www.twitter.com/olemislc (@olemislc)
Blog ES => http://simelo-es.blogspot.com
Blog EN => http://simelo-en.blogspot.com
Quora => http://www.quora.com/olemis
Youtube => http://youtube.com/user/greatsoftw
Featured article : Identificando números primos con expresión regular en Perl
http://feedproxy.google.com/~r/simelo-news/~3/BHr859OSndo/identificando-numeros-primos-con.html
Tweet: yo no puedo creer q haya pasado inadvertido el 1/2/12 12:12 ...
@elainediaz2003 no dijo na' ... OMG ! ... much more coming soon ;) #fb
Follow @olemislc Reply Retweet 12:59 Feb-01
Get this email app!
Get a signature like this. CLICK HERE.
Re: Catching up
Posted by Greg Stein <gs...@gmail.com>.
On Feb 6, 2012 6:59 AM, "Gary" <ga...@wandisco.com> wrote:
>
> Hi,
>
> For some reason I thought that I had responded to this thread. Sorry
about that..
>
> As noted we have the VM on which an instance of Trac is running. We could
do with deciding on how various types of users should be able to interact
with this - and therefore we probably need to know if there are any rules
Apache have for this. So do we want (or are we allowed):
>
> * Full anonymous access for wiki page creating/editing and ticket
> opening/closing or
> * User self-registration for the same actions
>
> or any other options?
Apache is a serious spam target. I think anon access would be very
troublesome.
> I haven't looked at configuring mail to allow for users to look after
themselves yet so I'll probably have to test configurations to make sure
that I can get it working. Talking of which, I wonder if it would be
overkill to have some kind of staging server that we can test changes to
the trac/bloodhound vm before they go live?
Probably overkill. Recall that the test is being used by a small community.
Impacts from bugs are minimal.
>
> Another aspect of the Trac setup I have not touched yet is working out
how to integrate with the bloodhound svn repository. I think that Trac
generally expects this to be on the same server as itself. I assume that
this is not the case here.
Subversion is on its own server. The only access will be remote. Basically,
nothing but ViewVC is allowed to run on the svn server, for security
reasons.
>
> Particular work I am interested in getting arranged is CI. Is this
something that Gavin would be able to get involved with or have
recommendations for? I believe that Buildbot and Jenkins are the readily
available choices. It would be nice to have a solution that Trac/Bloodhound
would be able to integrate with but it is not a strict necessity.
Those two systems are available. The community should pick one or both to
use, and then work with Infra on that. Gavin will ultimately be the guy
working on it, and may be able to expedite, but I'll leave that to him :-)
>
> At this point there is still no real code in the repositories to for CI
to test and so I think that it would be good if we could ask Olemis to
contribute his work on the theme and dashboard to the svn repositories.
That will also have the advantage that everyone can play with his code and
contribute patches back. I'm hoping to get some code down in there too
shortly.
Something needs to be buildable in order to attract any new community. Or
to have a focus for discussion and development. The barren svn is our
biggest problem right now, IMO.
>...
Cheers,
-g
Re: Catching up
Posted by Gary <ga...@wandisco.com>.
Hi,
For some reason I thought that I had responded to this thread. Sorry
about that..
As noted we have the VM on which an instance of Trac is running. We
could do with deciding on how various types of users should be able to
interact with this - and therefore we probably need to know if there are
any rules Apache have for this. So do we want (or are we allowed):
* Full anonymous access for wiki page creating/editing and ticket
opening/closing or
* User self-registration for the same actions
or any other options? I haven't looked at configuring mail to allow for
users to look after themselves yet so I'll probably have to test
configurations to make sure that I can get it working. Talking of which,
I wonder if it would be overkill to have some kind of staging server
that we can test changes to the trac/bloodhound vm before they go live?
Another aspect of the Trac setup I have not touched yet is working out
how to integrate with the bloodhound svn repository. I think that Trac
generally expects this to be on the same server as itself. I assume that
this is not the case here.
Particular work I am interested in getting arranged is CI. Is this
something that Gavin would be able to get involved with or have
recommendations for? I believe that Buildbot and Jenkins are the readily
available choices. It would be nice to have a solution that
Trac/Bloodhound would be able to integrate with but it is not a strict
necessity.
At this point there is still no real code in the repositories to for CI
to test and so I think that it would be good if we could ask Olemis to
contribute his work on the theme and dashboard to the svn repositories.
That will also have the advantage that everyone can play with his code
and contribute patches back. I'm hoping to get some code down in there
too shortly.
Have I missed anything important?
Cheers,
Gary
--
Best wishes,
Gary Martin
Lead Developer
WANdisco, Inc.
http://www.wandisco.com
On 01/31/2012 11:09 PM, Gavin McDonald wrote:
> Hi all,
>
> I've been away for 2 weeks on personal leave but am now ready to join in
> with whatever needs doing.
>
> My initial goals were to help getting the infrastructure + related software
> up and running.
>
> I notice Tony of Infra has created a VM. (someone mentioned that it was
> disabled for password logins, good! it
> will stay that way, get a key!)
>
> Please can I have a summary of the situation so far, what's been done, what
> are we waiting on, etc, what queries
> do you have. I'll get started when I know what we need doing first.
>
> Thanks
>
> Gav...
>
>
Re: Catching up
Posted by Olemis Lang <ol...@gmail.com>.
On Tue, Jan 31, 2012 at 6:09 PM, Gavin McDonald <ga...@16degrees.com.au>
wrote:
> Hi all,
>
:)
[...]
>
> Please can I have a summary of the situation so far, what's been done,
what
> are we waiting on, etc, what queries
> do you have. I'll get started when I know what we need doing first.
>
as far as I can say ...
- Add CI (parameterized build in Jenkins jargon ... afaicr ;) build job to
run
dashboard plugin test suite (once code will be out there ;) .
that's definitely not *what we need doing first* , but it's my $0.02
contribution to the TODO list
;)
PS: I'm guessing you'll dedicate some time to CI , isn't it ?
--
Regards,
Olemis
Facebook => http://www.facebook.com/olemis
Twitter => http://www.twitter.com/olemislc (@olemislc)
Blog ES => http://simelo-es.blogspot.com
Blog EN => http://simelo-en.blogspot.com
Quora => http://www.quora.com/olemis
Youtube => http://youtube.com/user/greatsoftw
Featured article : Identificando números primos con expresión regular en
Perl<http://feedproxy.google.com/~r/simelo-news/~3/BHr859OSndo/identificando-numeros-primos-con.html>
http://feedproxy.google.com/~r/simelo-news/~3/BHr859OSndo/identificando-numeros-primos-con.html
[image: Twitter] <http://twitter.com/olemislc>Tweet: RT @WANdisco How you
can add #uTest to #uberSVN... http://t.co/SCUhNd6B #fb
Follow @olemislc <http://twitter.com/olemislc> Reply
<http://twitter.com/?status=@olemislc%20&in_reply_to_status_id=160415165316218880&in_reply_to=olemislc>
Retweet <http://twitter.com/?status=RT%20%40olemislc%3A%20RT%20%40WANdisco%20How%20you%20can%20add%20%23uTest%20to%20%23uberSVN...%20http%3A%2F%2Ft.co%2FSCUhNd6B%20%23fb>
12:35
Jan-20 <http://twitter.com/olemislc/statuses/160415165316218880>
Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
Get a signature like this.
<http://r1.wisestamp.com/r/landing?promo=17&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_17>CLICK
HERE.<http://r1.wisestamp.com/r/landing?promo=17&dest=http%3A%2F%2Fwww.wisestamp.com%2Femail-install%3Futm_source%3Dextension%26utm_medium%3Demail%26utm_campaign%3Dpromo_17>