anchor.diff:  #!/usr/bin/groovy
   
   post {
  -	always {
  -    	
  +    always {  	
       }
       
       success {
  
positive.code: With pipelines, you can (and you should!) now treat your build as you treat your code!
  This means for instance that you should keep your pipeline https://en.wikipedia.org/wiki/Don't_repeat_yourself[DRY].
  
  ### Extracting functions
  
  As for the rest of the code, try to find pattern to be able to extract methods and reuse your code.
  Do not just copy and paste.
  Of course functions will not help you from a pipeline to another, but it is a good starting point.
  If you have the same function duplicated in multiple pipelines, it will help you to go to the next step.
  If the logic is duplicated throughtout your pipelines, the next step will take more time (and will be more error prone).
  
  ### Pipeline Shared Libraries
  
  
negative.code: 
  :hp-tags: Jenkins, Jenkinsfile, Pipelines
  
  Jenkins Pipeline are great.
  They allow the developer to keep its pipeline and its build near its code.
  But developing a Pipeline can quickly become cumbersome:
  
  * The text area of the Jenkins UI is not really convenient when you start writing pipelines a bit more complex than your basic hello world.
  * Your code can grow and become hard to maintain (yeah, we end up having the same problems in our builds than in the rest of our code!).
  * Validation is not easy...
  
  This post will sum up some technics I found useful to help me be efficient with pipelines.
  Of course the list is not exhaustive.
  I am more than interested by any new technic you would like to share in the comments.
  
  ## Writing the Jenkinsfile
  
  