2015-09-24 23:58 GMT-07:00 domi <[email protected]>: > As Richard, I also think that we would need some sort of a concept for a > CD pipeline. I consider my self as a quite advanced jenkins user, but still > I end up redesigning some sort of a CD pipeline with every new installation > or even project from scratch with different plugins then I used before. CD > is a great concept and sure it looks different for everyone - but people > wanna have guidance and then they will be able to change it the way it > works for them. > In my point of view Jenkins 2.0 would need some sort of a definition for > it and give answers/proposals how to do these steps together (and > visualise): > - build some sort of artifact (this stage might include unit tests) > - promote artifacts for integration tests > - do a release build > - store the released artifacts (depending on the type also make it public > available, e.g. for maven, npm, bower,…) > - promote released artifacts to test env > - trigger tests on test env > - promote released artifacts to prod env > (for sure the list is not complete and every step has to be plugable for > different technologies, but you get the idea) > > I know we have all the components/plugins to solve all these issues, but > its hard for a newbe (and also experienced users) to really get this right. > Workflow for sure is great to go for something like this, but I think we > need something on top of it (maybe its just a good documentation) to really > get people into this. >
Yes, I totally agree. The other day I saw Tom showing his experiment to add ACE editor to Jenkins Workflow config UI (which also came with a drop-down to let you insert some templates.) I've also talked with Jesse and others a number of times about how we can generate GDSL <https://confluence.jetbrains.com/display/GRVY/Scripting+IDE+for+DSL+awareness> and DSLD <https://spring.io/blog/2011/05/09/better-dsl-support-in-groovy-eclipse>. Something like that is clearly needed, no question. -- Kohsuke Kawaguchi -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/CAN4CQ4xRZud6KeB4o0z2OmW%2BbX0hJzeUg-ESSS0xTqw6bWMWRw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
