Jump to page: 1 2
Thread overview
[Issue 14381] It is too difficult to contribute to the auto-tester
Mar 31, 2015
Brad Roberts
Mar 31, 2015
Théo Bueno
Mar 31, 2015
Brad Roberts
Apr 03, 2015
Martin Nowak
Apr 06, 2015
Martin Nowak
Jul 26, 2015
Mathias LANG
Jul 26, 2015
Mathias LANG
Apr 08, 2016
greenify
Oct 22, 2016
Mathias Lang
Dec 17, 2022
Iain Buclaw
Jan 17, 2023
Iain Buclaw
March 31, 2015
https://issues.dlang.org/show_bug.cgi?id=14381

--- Comment #1 from Brad Roberts <braddr@puremagic.com> ---
My major comment is to stop thinking of the auto-tester as the D auto-tester. Think of it as a tool that the D community uses that is owned and operated by me.  I agree that it's currently and for the past year poorly owned.  But it's not specific to D and I don't intend to add capabilities to it that are specific to D or the D development process.

Some of the feature work you suggest below can fit within either the build or the test target without requiring changes to the auto-tester.

Some of it is general enough to work for more than D.

--
March 31, 2015
https://issues.dlang.org/show_bug.cgi?id=14381

Andrei Alexandrescu <andrei@erdani.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #2 from Andrei Alexandrescu <andrei@erdani.com> ---
(In reply to Brad Roberts from comment #1)
> My major comment is to stop thinking of the auto-tester as the D auto-tester.  Think of it as a tool that the D community uses that is owned and operated by me.  I agree that it's currently and for the past year poorly owned.  But it's not specific to D and I don't intend to add capabilities to it that are specific to D or the D development process.
> 
> Some of the feature work you suggest below can fit within either the build or the test target without requiring changes to the auto-tester.
> 
> Some of it is general enough to work for more than D.

So what is the action item here, Brad? Do you plan to open things up or do we need to duplicate the effort?

I said this and I maintain: we need to move away the setup in which only one person is the bottleneck for everything about D vitals.

Please let us know if and when you are willing to open the system. Thanks.

--
March 31, 2015
https://issues.dlang.org/show_bug.cgi?id=14381

Théo Bueno <munrek@gmx.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|ASSIGNED                    |NEW
                 CC|                            |munrek@gmx.com

--- Comment #3 from Théo Bueno <munrek@gmx.com> ---
Brad Roberts has done a great work with his platform, but have we ever considered to move to a standardized, complete and easily extensible solution such as Jenkins ? At this point, IMHO the option should be considered.

--
March 31, 2015
https://issues.dlang.org/show_bug.cgi?id=14381

--- Comment #4 from Brad Roberts <braddr@puremagic.com> ---
(In reply to Andrei Alexandrescu from comment #2)
> (In reply to Brad Roberts from comment #1)
> > My major comment is to stop thinking of the auto-tester as the D auto-tester.  Think of it as a tool that the D community uses that is owned and operated by me.  I agree that it's currently and for the past year poorly owned.  But it's not specific to D and I don't intend to add capabilities to it that are specific to D or the D development process.
> > 
> > Some of the feature work you suggest below can fit within either the build or the test target without requiring changes to the auto-tester.
> > 
> > Some of it is general enough to work for more than D.
> 
> So what is the action item here, Brad? Do you plan to open things up

Depends on what you mean by open things up?  I've always accepted pull requests, though most have been reworked before being merged as they're typically not workable as is.

Do I plan on allowing anyone other than me to have merge / pull permissions? Not at this time.

Do I plan on allowing anyone other than me to have login access to the client build machines?  Not blanketly no.  If there's some extraordinary need for debugging purposes, maybe.  That said, there's almost always going to be a better way to do that.. like a VM for instance.

> or do we need to duplicate the effort?

I hope not, it'd be a pretty large duplication of effort.

> I said this and I maintain: we need to move away the setup in which only one person is the bottleneck for everything about D vitals.

That's a huge exaggeration over the current situation.  Me for the auto-tester is far from a bottleneck for everything about D vitals.  I'm a bottleneck for one key tool, certainly.

> Please let us know if and when you are willing to open the system. Thanks.

I'm open to discussion and feature requests.  I'm open to accepting contributions, but only in directions that I believe are right for the tool. I'm going to say no to things that I don't believe are a good fit.

--
April 03, 2015
https://issues.dlang.org/show_bug.cgi?id=14381

Martin Nowak <code@dawg.eu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |code@dawg.eu

--- Comment #5 from Martin Nowak <code@dawg.eu> ---
Let's take a concrete example. I'm trying to get dlang.org/documentation
building integrated into or CI since 4 month, because it breaks too often and
regularly stalls releases.
https://github.com/braddr/d-tester/issues/41

I tried various ways (email, newsgroup, github) to get a bit of your attention on that topic. I also tried to implement it myself, but couldn't get the client script to run on my machine. This is asking for 10-20 minutes of your time for an important feature, it is mainly a communication issue though.

--
April 06, 2015
https://issues.dlang.org/show_bug.cgi?id=14381

--- Comment #6 from Martin Nowak <code@dawg.eu> ---
We could move the build/test scripts into the DMD/druntime/phobos repos, that would help with things such as this. https://github.com/D-Programming-Language/druntime/pull/1206

--
July 26, 2015
https://issues.dlang.org/show_bug.cgi?id=14381

Mathias LANG <pro.mathias.lang@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |3031

--
July 26, 2015
https://issues.dlang.org/show_bug.cgi?id=14381

Mathias LANG <pro.mathias.lang@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|3031                        |

--
April 08, 2016
https://issues.dlang.org/show_bug.cgi?id=14381

greenify <greeenify@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |greeenify@gmail.com

--- Comment #7 from greenify <greeenify@gmail.com> ---
Ldc now uses buildbot to handle their ci.

https://forum.dlang.org/post/hikcbbqqnpvvyirxgzxu@forum.dlang.org

Basically every user can contribute and run his own client. Seems to be a mature project with 2k stars on github.

--
October 22, 2016
https://issues.dlang.org/show_bug.cgi?id=14381

Mathias Lang <mathias.lang@sociomantic.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |acehreli@yahoo.com

--- Comment #8 from Mathias Lang <mathias.lang@sociomantic.com> ---
*** Issue 16608 has been marked as a duplicate of this issue. ***

--
« First   ‹ Prev
1 2