[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: CI/CD Pipeline & DSL





On Tue, Sep 20, 2016 at 7:15 AM, Charles Moulliard <cmoullia redhat com> wrote:



On Mon, Sep 19, 2016 at 1:39 PM, Ben Parees <bparees redhat com> wrote:


On Mon, Sep 19, 2016 at 1:28 PM, Charles Moulliard <cmoullia redhat com> wrote:
Hi,


- Is Groovy DSL syntax still supported with Openshift Jenkins Pipeline ?

When using the openshift plugin from within a Jenkinsfile (jenkins pipeline plugin), ​the openshift jenkins plugin offers both the DSL that is described in that link, as well as the ability to just use groovy to invoke the plugin api directly.​

Good to know that 

 

Additional questions :

- Is it the list of the jenkins plugins that we package with the OpenShift Docker Image -  https://github.com/openshift/jenkins/blob/master/1/contrib/openshift/base-plugins.txt ?

​yes​. 

This information should be part of the Openshift Enterprise Documentation as a table to help our users to figure out if the jenkins server they will use contains the list of the plugins they envision to use. Make sense ?

​it does, although the jenkins server itself does offer an easy way to see what plugins are installed (via the web console) which will always be more accurate than any documentation we try to maintain.

​also i should note that base-plugins.txt is the list of plugins installed in the CentOS jenkins image.  For the rhel image, the list is here:
https://github.com/openshift/jenkins/blob/master/1/Dockerfile.rhel7#L37

because for rhel the plugins come from rpms (that we maintain and package ourselves), not downloaded over the internet as they are for centos.​

​for the most part the lists should be in sync.

 

 
- Can you confirm that the Openshift Jenkins Docker image always package the latest Jenkins Release (= LTS) ?

​we do our best to keep it up to date with the latest LTS, but there may be times when we fall behind for a few days/weeks until we can get the image updated.​

Do you know which Jenkins release has been used when you have created the Docker image for the OpenShift Release (Origin or Enterprise). If this info is available, then it should be documented also 

​The jenkins image isn't necessarily aligned to an openshift release, they are independent and can be updated or "ship" at any time we deem necessary or desirable.  It's also not tied to a release, so you can be on openshift 3.1 and using the latest jenkins image.

We include an env variable in the image which tells you what version your image has:
https://github.com/openshift/jenkins/blob/master/1/Dockerfile.rhel7#L15

 

 
- Is it possible to trigger a Jenkins job (= Pipeline) when a new commit has been pushed into a git project ?

​you can do that using the git scm plugin for jenkins.

This is a point that we should certainly discuss together as many projects will be interested that this integration is done by default or at least that we provide guidance, how to instructions to use it (example : https://www.cloudbees.com/blog/better-integration-between-jenkins-and-github-github-jenkins-plugin, ...) like also to trigger the a new Build

​I'm a little bit torn here.  This is a general jenkins education/documentation issue.  There's nothing openshift specific about it, so I don't want to start maintaining jenkins tutorials in the openshift documentation.  Our statement is generally:  we're giving you a jenkins server.  you can do anything with it that you'd do with a normal jenkins server.  Also here are some useful openshift integration capabilities we include by default.

It's the same story for our mysql, EAP, etc images.  Those are products that have their own documentation...we need to document any "gotchas" about our images and using them in openshift, but we shouldn't be documenting standard product usage.

 

 

Regards,

Charles

On Fri, Sep 16, 2016 at 7:52 PM, Ben Parees <bparees redhat com> wrote:

In the meantime, you can certainly install the fabric8 plugin into our jenkins image and use those additional pipeline steps. The openshift pipeline feature works with any valid jenkinsfile.  We just happen to include the openshift specific plugin/dsl support in the image we ship.

Ben Parees | OpenShift


On Sep 16, 2016 19:08, "Clayton Coleman" <ccoleman redhat com> wrote:
It's been discussed.  The primary concern would that would become a versionable API once we ship it, so we have to have a release and versioning process that maintains backwards compatibility for users for the life of the product.  That part is what we haven't sorted out yet.

On Fri, Sep 16, 2016 at 9:23 AM, Charles Moulliard <cmoullia redhat com> wrote:
Hi,

As far as I know Openshift and Fabric8 projects have developed DSL to define Jenkins Pipelines running top of OpenShift/Kubernetes


Is it planned that (some) Fabric8 DSL tasks will be integrated in a future version of OpenShift ?

Regards,

Charles

_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users



_______________________________________________
users mailing list
users lists openshift redhat com
http://lists.openshift.redhat.com/openshiftmm/listinfo/users





--
Ben Parees | OpenShift





--
Ben Parees | OpenShift


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]