Very interesting.

I'll read further through your project code this evening.

I'm curious for any feedback you have on my current project description.
Especially, what do you think of my DSL idea:
   https://github.com/pvdissel/cy.io/wiki/Global-design

About the "working knowledge". Let's try it out.
I'm in The Netherlands (GMT+2 it's ~11:00am when sending this message).
Let's find a date and time and set-up a hangout to chat :)

Ok?

/Patrick


On 04/23/2013 03:22 AM, Andrew Oberstar wrote:
Hi Patrick,

I really like the idea of your CI server. I played around with a similar
idea <https://github.com/ajoberstar/grave-ci> while beginning to learn
Scala, though it does next to nothing right now. The nice thing about
making use of Gradle is that the CI server doesn't need to do a whole
lot. Really just setting up the environment and kicking off the build.
Gradle's model allows you to feed information back to the CI server if
you want any of the reports or artifacts of the build.

I'm not aware of any documentation of the internals, though others would
know better. I have a working knowledge of some segments, though I don't
know how well I could explain them.

Andy


On Mon, Apr 22, 2013 at 3:23 PM, Patrick van Dissel <pvdis...@gmail.com
<mailto:pvdis...@gmail.com>> wrote:

    Hi,

    I'm looking for someone or some document who/which can give me an
    in-depth overview of the Gradle internal workings.

    I'm interested on how Gradle works internally, from front to back,
    incl. the GroovyDSL implementation, the abstractions, factories, CLI
    UI output, etc.

    I've already read through most of the launcher, core and plugin
    code. Trying to learn from the gradle implementation. On one side I
    find the code fascinatingly clean and separated/abstract. but on the
    other side I'm missing the link between the abstraction and how it's
    working at runtime.

    I know gradleware provides Gradle In-Depth trainings, but those are
    trainings about how to use gradle from the outside as far as I
    understand from the description like:
    http://www.gradleware.com/__products/training/live/gradle-__depth
    <http://www.gradleware.com/products/training/live/gradle-depth>
    I'm more interested in the internal workings of gradle.

    Why I'm interested in the internals?
    Two reasons:
    1. I'm building a open-source Continuous Integration server, which
    uses practices that Gradle uses but then on a CI level. Gradle,
    Maven, make, etc, are still needed to build the specific projects.
        I think my wiki page explains it best, why I want to build
    another CI tool and what I want to do better:
    https://github.com/pvdissel/__cy.io/wiki/Why-a-new-CI-tool
    <https://github.com/pvdissel/cy.io/wiki/Why-a-new-CI-tool>
    https://github.com/pvdissel/__cy.io/wiki/Global-design
    <https://github.com/pvdissel/cy.io/wiki/Global-design> (DSL ideas)
        So I want to learn the Gradle internals, so I can use the same
    implementation ideas/ways in my tool. I can even see my tool as an
    extension of Gradle :D My CI tool managing the project release
    pipelines while gradle is used for the project specific automation
    and building.

        Note "cy.io <http://cy.io>" is a temporary name and the project
    is still in early development. During the DevOpsDays Amsterdam
    conference (http://www.devopsdays.org/__events/2013-amsterdam/
    <http://www.devopsdays.org/events/2013-amsterdam/>) on June 14-15 I
    want to throw my ideas into the world with an Ignite talk and an
    Open-Space discussion on what people think of my ideas and I would
    like to discuss implementation details with them. To see what the
    next steps could be.

    2. I would love to help out on Gradle development. I found the
    contribute list on:
    http://www.gradle.org/__contribute <http://www.gradle.org/contribute>
        But also for those, I think it would be good to have knowledge
    of the internal working of Gradle.

    So, summary of my questions:
    - Am I right about the offered trainings? Are they about how to use
    Gradle and not about the Gradle internals?
    - Is there documentation on the gradle internal workings?
    - Is there someone who is willing to give me an intro into the
    Gradle internal workings?
    - And of course, any feedback on my Cy.io project is also always
    welcome :)

    Kind regards,
    Patrick van Dissel

    ------------------------------__------------------------------__---------
    To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/__manage_email
    <http://xircles.codehaus.org/manage_email>




---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email


Reply via email to