On Mon, Mar 10, 2014 at 3:01 PM, Stephen Connolly
<stephen.alan.conno...@gmail.com> 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.
--
Les Mikesell
lesmikes...@gmail.com
--
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 jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
