Craig Rodrigues (2016-05-27 08:59):
Hi,
The new Jenkins UI looks nice, and will be a big improvement over the
existing UI.
The original selling point of Jenkins was that even with the
simplistic forms-based UI,
someone could fill out a relatively simple form, and have a continuous
integration pipeline.
I have met people who were general devops and scripting people, and
could use Jenkins quite nicely.
While I understand the motivation for Pipeline (previously known as
Workflow), I can't say I'm very happy with the results.
Here are some of the pain points I've encountered with Pipeline scripts:
* Other than the most trivial of scripts, you need to be a
knowledgable Groovy programmer. For example, to make a global
variable, you need to use a @Field. (What?!) Most scripting and
devops people that I know don't really know Groovy.
[...]
Groovy is not my thing either. The syntax is not very hard, but using it
with Jenkins is just trail and error. There are some changes from
version to version and no central place to learn from.
I think this would be solved by providing recepies that would be updated
for each Jenkins version. Some recepies ideas:
1. How to read a build parameter and conditionally run some shell script.
2. How to trigger build of another project.
3. How to trigger build of another project with some static parameters
of various types.
4. How to trigger build of another project passing all parameters from
current job/build.
5. How to copy artifacts from another project.
6. How to send files over SSH.
7. How to execute scripts over SSH.
Regards,
Nux.
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/2c5be2a6-607a-7cae-e935-e285a7c70266%40mol.com.pl.
For more options, visit https://groups.google.com/d/optout.
