RackHD Jenkins pipeline coding convention

Goal:

1. Put all Jenkins jobs under source code.
2. Dashboard shows different jobs according to role type.
3. Put all the nodes in a resource pool.

For example, several stacks for continuous test, smoke test

Pipeline should lock a stack for  smoke test, continuous test…

Developers should lock a stack before debug with the specified node.

Success Criteria:

1. Implement functions and handy dashboard 
2. It’s convenience to check log. (Try to avoid triggering other job)
   
   

Code Convention & Guideline

1. Avoid exposing sensitive information with Jenkins plugin: Credentials Binding Plugin
2. If a pipeline is reused in other pipelines, try to reuse by code instead of re-use job like before, it can be implemented with groovy method(library file) or a runnable groovy script.
3. adding comments for auto-generated groovy part
4. Pipeline BEST_PRACTICES

Former user (Deleted)  drafting.