anchor.diff:  Its aim is to give a more config like touch to the pipeline.
   Code vs Config, here we are again (let's not replay maven vs gradle and gulp vs grunt all over again...)!
   Again, the plugin was https://youtu.be/TsWkZLLU-s4?t=27m35s[demoed in the last Jenkins Online Meetup].
  -The API does not seem stable for the moment, but some stuff seems very intersting.
  +The API does not seem stable for the moment, but some stuff seems very interesting.
   For instance, the notification issue I raised before could be adressed with something like:
   
   [source, groovy]
  
positive.code: #!/usr/bin/groovy
  
  try {
  	notify(start)
      //put here all your pipeline
      notify(success)
  } catch(exception) {
  	notify(failure)
  }
  
  def notify(state) {
  	//notify scm
  }
  ----
  
  As you can see, a lot of duplicated between the builds, with a huge maintenance problem.
  What is happening is the SCM API is changing for instance?
  I would need to iterate over all the pipelines to update the code of the notify function.
  Same issue if we can finally get rid of this try/catch structure (side note, that might soon be the case as we will see in the last part of this article).
  I would have to manually change all the Jenkinsfiles.
  
  
negative.code: 
  ### The IDE
  
  Well, I won't go into an IDE war, this is far from being the point of the article.
  Your favorite java IDE (with potentially a groovy support plugin) will do the trick.
  
  That being said, you can do more than having a simple groovy IDE, you can also teach your IDE to understand the DSL used by Jenkins!
  This works thanks to the GroovyDSL (GDSL).
  A GDSL is basically a file that will describe the meta language that a DSL uses.
  By putting this file in the classpath of a groovy project, your IDE will be able to assist you write code that follows the DSL.
  The good news is that the Jenkins pipeline exposes a GDSL.
  Go to _$jenkins_base_url/pipeline_syntax/gdsl_ to get it.
  Then add this file in the classpath of your project and voilà, your IDE can now autocomplete!
  
  Note that I only tested this feature in Intellij, but this should work in other groovy compatible IDEs.
  Also, plugins might enrich the DSL without being described in the GDSL, so don't expect the autocomplete to be absolutely complete.
  
  ### The linter
  
  During development of a pipeline, it's easy to make a typo in your Jenkinsfile and end up with an invalide Jenkinsfile.
  This is a pain, as you lose time understanding the mistake, fix it, commit the fix and push it.
  The good news is that there is a way to shorten this feedback loop.
  
  Jenkins offers a linter for your Jenkinsfile.
  Best way to use the linter is with the JenkinsCLI.
  You will need the https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Model+Definition+Plugin[Pipeline Model Definition] version 0.7 at least.
  You can then ask Jenkins to lint your Jenkinsfile:
  
  