cpf/templating

A better template and scaffolding plugin for Jenkins

templating's Issues

Being able to see the differences between an actual implementation and its template

Sometimes, the actual job is updated without the template being updated as well. This represents a risk to lose configuration when synchronizing the template.

Displaying the differences between a template and an implementing job could help to correct the template before synchronizing.

Being able to disconnect implementations from their scaffold

Once jobs have been created from a scaffold, it would be nice to be able to disconnect those from the scaffold, in order to avoid any synchronization accident.

The description of the template job is not taken into account

The "description" field of a template is not copied to the implementing job.

Being able to delete scaffold

Today, the deletion of a scaffold does not work and a Jenkins downtime is needed to get rid of it.

Re-enabling the deletion would be easier, but what about the linked jobs?

Scaffolding: Replace "template" with the qualifier

While standing up a scaffold: Replace "template" with the qualifier provided

• Replace the "job append name" with "qualifier" - it's no longer just an append name
• When standing up, replace the token "template" with the qualifier
• Explain on the standup page the behavior

The token will be "template" by convention.

Being able to reinit a scaffold using new parameters

Once a scaffold has been used to create a list of implementing jobs, we should be able to re-initialize those jobs by giving a new set of parameters.