/
Can MettleCI prevent the promotion of CopyOf* jobs?

Can MettleCI prevent the promotion of CopyOf* jobs?

The job compliance library that ships with MettleCI includes a rule explicitly  designed to identify potentially redundant jobs.  This rule also looks for other naming indicators for jobs which may not be intended for production use.  The rule looks for user-configured naming signature that indicates a job is not intended for production use, such as 'CopyOf', 'WIP', 'Temp', and sequences of numbers that look like timestamps.   MettleCI's Compliance library ships with a default Blocklist used to identify these patterns. 

Neither the Report Card nor the MettleCI Workbench 'separate' jobs from your project. However, utilising the Job Naming Compliance rule in your build pipeline (e.g. in your Continuous Integration plan) as a mandatory check will prohibit jobs with names like this from making their way into your code's Master branch in Git.

Related content

Do we need to modify our jobs to be compatible with MettleCI?
Do we need to modify our jobs to be compatible with MettleCI?
More like this
Can MettleCI manage Job parameter files in version control?
Can MettleCI manage Job parameter files in version control?
More like this
Job Naming
More like this
Would the integrity of DataStage jobs be maintained if we later removed MettleCI from our servers ?
Would the integrity of DataStage jobs be maintained if we later removed MettleCI from our servers ?
More like this
Does the MettleCI Unit Test job parameter need to be removed from a job before promoting it to a Production environment?
Does the MettleCI Unit Test job parameter need to be removed from a job before promoting it to a Production environment?
More like this
Does Mettle CI support Git branching/merging functionality?
Does Mettle CI support Git branching/merging functionality?
More like this

© 2015-2024 Data Migrators Pty Ltd.