On Mon, Mar 10, 2014 at 7:28 AM, Stephen Connolly
<stephen.alan.conno...@gmail.com> wrote:
> I will give you my vision.
>
> In my vision there are two types of things:
>
> 1. Things that depend on the stuff in a build job itself
> 2. Things that depend on the inter-relationship of jobs within a CI server.
>
> Traditionally, Jenkins takes the view that there is just one type of thing.
> So you end up configuring everything in the Jenkins job (or you use the evil
> one and have slightly less to configure)
I'm inclined to think that nothing should depend on jenkins - except
maybe promotion or deployment steps. That is, the build and test
steps should be exactly repeating things the developer can do himself
and may have done before his commit. Jenkins should just repeat that
to ensure that everything really is in source control and meshes with
anything else that might have been committed.
> Literate (and I think it needs a better name BTW) is about moving the Type 1
> things out of the Jenkins UI and into the SCM where they belong.
Is there a standalone literate-builder that the developer can
run/test/debug on his own without jenkins support?
--
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.
