On Mon, Mar 10, 2014 at 3:45 PM, Stephen Connolly
<[email protected]> wrote:
>
> 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
Nothing at all wrong with the idea. But I can take any mapping of one
thing to another and mistype it or misunderstand it - or have the
computer put stuff in the wrong character set so what I see isn't what
jenkins will try to map. What I want is a way to have the mapping
done and check the results (by executing them to the extent possible)
before committing it. And I do call mapping one thing to another
magic if there isn't a way to trace your way through it.
--
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.
