On Wed, Sep 26, 2012 at 8:53 PM, Matt Corallo wrote:
> Jenkins currently just runs the test script after each new commit to
> bitcoin (and provides binaries to anyone who wants them), so its pretty
> basic (though jenkins has way more features than we use). The bitcoin
> one lives at http://jenki
On Wed, 2012-09-26 at 13:28 +0100, steve wrote:
> Hi Matt,
>
> Glad to have another ninja onboard :)
>
> On 25/09/2012 21:41, Matt Corallo wrote:
> > Although Jenkins may not be the best system, we already have
> > jenkins and pull-tester (which is a dumb python script I wrote to
> > test all inc
There are test cases that can be automated. That's Jenkins, and those will
be run automagically.
Then there are tests that cannot be automated; things like "Does the GUI
look OK on all of the platforms that we support (Windows XP/2000/Vista/7/8,
Ubuntu/Debian blah with window managers foo and bar,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/09/2012 17:06, Mark Friedenbach wrote:
> Running a concurrent Mantis tracker would be confusing and fragment
> the development pathway. We have an issue tracker; it's on github.
I think you misunderstand what I am proposing.
QA needs more than
On Wed, Sep 26, 2012 at 12:06 PM, Mark Friedenbach wrote:
> Certainly developers should be responsible for making sure that regression
> tests for bugs they fix make it either into the unit tests or Matt's
> functional test repository. QA should hold them accountable for that
> (re-opening tickets
Running a concurrent Mantis tracker would be confusing and fragment the
development pathway. We have an issue tracker; it's on github.
What's being talked about here are two separate things. Jenkins is a
continuous integration system. It can be configured to run the suite of
unit tests, regression
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
- -BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 26/09/2012 13:49, Wladimir wrote:
> Steve,
Hi Wladimir,
>
>> So, currently there are 4 potential places for bugs to be
>> reported 1 - jenkins (and unit tests) 2 - git 3 - mailing list 4
>> - for
Steve,
> So, currently there are 4 potential places for bugs to be reported
> 1 - jenkins (and unit tests)
> 2 - git
> 3 - mailing list
> 4 - forum (bitcointalk...)
> 5? - is there still the ability to add bugs via sourceforge?
Currently github is the authoritative place to report issues. When
so
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Matt,
Glad to have another ninja onboard :)
On 25/09/2012 21:41, Matt Corallo wrote:
> Although Jenkins may not be the best system, we already have
> jenkins and pull-tester (which is a dumb python script I wrote to
> test all incoming pull reques
On Wednesday, September 26, 2012 11:41:13 AM Daniel F wrote:
> on 09/26/2012 01:49 AM Wladimir said the following:
> > I'm willing to write this. But I know these kinds of proposals always
> > end in a big discussion about what should be and what should not be on
> > bitcoin.org, however we should
on 09/26/2012 01:49 AM Wladimir said the following:
> I'm willing to write this. But I know these kinds of proposals always
> end in a big discussion about what should be and what should not be on
> bitcoin.org, however we should be a bit pragmatic here.
May I suggest a page bitcoin.org/developer
11 matches
Mail list logo
