On 10 March 2014 20:14, Les Mikesell <[email protected]> wrote:

> On Mon, Mar 10, 2014 at 3:01 PM, Stephen Connolly
> <[email protected]> wrote:
> >
> >> I'd expect much faster acceptance with a full standalone version that
> >> did exactly the same things except from a checked out local workspace.
> >>  I wouldn't expect people to write make/cmake/project(etc.) files
> >> without the ability to run/test them locally before committing and
> >> don't see much difference here (except maybe automatic branch tracking
> >> for other versions).
> >
> >
> > Remember literate is just a verbatim statement of the command(s) to type
> in.
> >
> > The only magic the Jenkins literate plugin adds is around conceptualising
> > those commands within Jenkins
> >
> > You don't need to install anything to look at a README.md and type in
> > commands ;-)
>
> Sure, I can type commands easily enough.  The usual problem is that
> either I didn't interpret the instructions correctly or  what I type
> isn't interpreted the way I expected.  So I start with the assumption
> that the first several/many attempts aren't going to be correct and
> that the bulk of the time working on it will be debugging and figuring
> out what it really is doing instead of what I expected.   So not being
> able to see inside that magic conceptualization part would be a big
> problem for me.
>

There is no big magic... the only magic is around how to decide which
section is the build section (hint: it's the section with "build" in the
title... unless you change the defaults) and how to map between the
readme's description of the build environment and jenkins tool installers
(which is mapping one user contributed set of names against another set of
names)

Next to no magic at all... unless you call that the magic... that there is
nothing hidden going on at all!

Remember the whole point of literate is that you have to tell the user how
to build your software project... so why not use those exact same
instructions for the CI system


>
> --
>   Les Mikesell
>     [email protected]
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to