Hi all,
I've recently been playing with the Literate plugin. As the plugin is still
young, I thought I'd drop some random lines here about my
findings/thoughts. Maybe this can yield some debate about views/future of
the plugin.
##################
# Works as advertised
Might sound obvious, but I actually managed to install it and tinker with
it quite quickly on our internal jenkins preprod server. That's not always
the case :-). Congrats to the developers for that (Stephen & Vincent, we're
looking at you :-)).
# Labels/text used in the README.md : tying to some server
In the .md you have to put things like:
* `rhel` and `maven-3.1.0`
- `jdk-1.7.0_64bits`
- `jdk-1.8.0_64bits`
IMO, this somehow ties the sources to an actual server and its labels.
What is your feeling about it? Is it maybe planned to add some form of
label mapping between what's in a project descriptor and the actual labels
in a jenkins instance?
##################
# Common values
Having to manage an averagely large Jenkins install (~400 jobs), I often
find myself doing the same things many times, using variables and so on.
Namely, in the case of literate-plugin, I'd see some form of :
# Build
$standardMvnBuild
useful to share between builds (or even through inheritance, mixing in like
Job DSL offers, etc.).
Though I agree it may also defeat some principles of the plugins or worsen
the coupling between sources and the actual server.
##################
# Integration with workflow-plugin / coordinating multiple jobs
I've not yet seen how to trigger other builds. I'm not even sure I see
clearly how this would be done in a literate-style without again falling
onto the above issue about tying things.
You'd have for example to define a name of job to trigger, and stick to it.
In Jenkins, the naming updates somehow automatically.
With only text, this would quickly become out-of-date.
##################
OK, let's call it a first shot.
Hope I was clear enough. If not just tell me. I hope this will help us
discuss about this very interesting work.
Thanks again.
Cheers
--
Baptiste
--
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.
