jstrachan

6 ms·

1.
by jstrachan 8y ago
OpenShift's Jenkins integration is good. Though its even cooler to use Jenkins X on OpenShift as you get automated CI/CD pipelines + Environments, Preview Environments on Pull Requests and GitOps based Promotion between environmen
2.
by jstrachan 8y ago
even from an OSS goals perspective I'm looking forward to seeing better alignment, reuse and interoperability between Jenkins, Jenkins X & things like CodeShip & Knative Build
3.
by jstrachan 8y ago
BTW we use the kubernetes credentials provider plugin in Jenkins X which exposes Kubernetes Secrets as Jenkins Credentials; then the `credentials` step in the `Jenkinsfile` encrypts them from any build logs
4.
by jstrachan 8y ago
if you are happy to use Kubernetes then if you switch to Jenkins X you never need to configure a Jenkins server or create a groovy based DSL again: https://jenkins-x.io/
5.
by jstrachan 8y ago
invoke `make` from inside your `Jenkinfile`? :)
6.
by jstrachan 8y ago
Jenkins X can help compete effectively with other tools since it automates your entire CI/CD; from creating the Pipelines, setting up your Environments, creating Preview Environments on each Pull Request and then performing GitOps base
7.
by jstrachan 8y ago
one solution to the problem, if you are building apps for kubernetes is to use Jenkins X which automates all your CI/CD pipelines: https://jenkins-x.io/
8.
by jstrachan 8y ago
yeah, I see 'plugins' being around for a while but docker steps becoming the more cloud native long term alternative; being more reusable stand alone & not requiring changing a Jenkins Master (or even requiring a Jenkins maste
9.
by jstrachan 8y ago
I think as part of the new Jenkins architecture we should be able to make it much easier to stop at a point in a pipeline & open a terminal/REPL to test out steps. Also I'm hoping for a nice validated YAML based pipeline synta
10.
by jstrachan 8y ago
if you can't use kubernetes or containers then I guess Ansible is a fallback?
11.
by jstrachan 8y ago
OpenShift is a fork of the Kubernetes code base: https://github.com/openshift/origin I.e. it’s not using the upstream distribution of Kubernetes like the public cloud vendors or Heptio etc. It’s great it’s a Certified
12.
by jstrachan 8y ago
OpenShift is Red Hat's supported fork & distribution of Kubernetes - so its another platform we can install and use Jenkins X on. OpenShift also includes some Jenkins support; e.g. you can add BuildConfig resources via a YAML file
13.
by jstrachan 8y ago
we're using helm for installing/upgrading apps; it takes care of reverting bad versions/releases etc
14.
by jstrachan 8y ago
Jenkins X runs in containers on kubernetes and all the builds are done in containers. You can use whatever pod template (collection of docker images) in your CI/CD pipeline: http://jenkins-x.io/architecture/pod-tem
15.
by jstrachan 8y ago
Agreed! Jenkins X uses Skaffold to do the docker image building so can be configured to use kaniko or Google Container Builder etc https://github.com/GoogleContainerTools/skaffold
16.
by jstrachan 8y ago
Each environment is in a separate namespaces. You can add/edit/delete the Environments to use whatever namespaces you wish to use. Promotion is either automatic or manual. By default Staging is automatic and production is manual.
17.
by jstrachan 8y ago
Thanks! You are free to use any kubernetes cluster and install Jenkins X there: http://jenkins-x.io/getting-started/install-on-cluster/ The default is to use separate namespaces in kubernetes for each teams develo
18.
by jstrachan 8y ago
That’s a great point. This blog tries to compare Jenkins X versus Jenkins 2.0: https://dzone.com/articles/jenkins-x-the-good-bad-and-ugly It’s mostly about automation of install, configuration, environments, pipelines
19.
by jstrachan 8y ago
Thanks for your feedback. We are trying to make things simpler with Jenkins X by using best of breed tools (git providers, issue trackers, cloud services, service meshes, security & code quality tools etc) with best of breed OSS tools l
20.
by jstrachan 8y ago
It should do - in theory - it needs testing though ;). I notice that kops recently added support for Digital Ocean https://github.com/kubernetes/kops/blob/master/docs/tutorial... So we should be abl
21.
by jstrachan 8y ago
Btw I’m the author of the above blog post & committer on Jenkins X. So our focus is currently anyone looking to automate CI/CD on kubernetes, the cloud or any modern platform like OpenShift, Mesos or CloudFoundry which all come wit
22.
by jstrachan 8y ago
BTW we're hoping to make it easier to 'service link' your Preview Environments to other environments. https://github.com/jenkins-x/jx/issues/573 e.g. so you could deploy just your front end in
23.
by jstrachan 8y ago
Jenkins X creates a Preview Environment per Pull Request yeah; which can be as much or as little as you want it to be. e.g. it could be just 1 pod only or could be a suit of related apps (you may want to test multiple things together). You
24.
by jstrachan 8y ago
whoops, great catch thanks. Hoping we can figure out a fix very soon...
25.
by jstrachan 8y ago
The things you gain from switching to Jenkins X: * automated CI/CD for your kubernetes based applications using Helm Charts & GitOps to manage promotions (manual or automated) * a single command to create a kubernetes cluster, inst
26.
by jstrachan 8y ago
Sorry to hear you're underwhelmed! Did you check out the GitOps features for versioning all changes to all Environments in git with human approval? http://jenkins-x.io/about/features/#promotion Or the automat