Skip to end of metadata
Go to start of metadata

Proposal: Update naming conventions for CI Jobs

Purpose:

Readability, Using grouping features of Jenkins, Clear understanding of tasks from name

Changes:

Jobs added to jenkins would use a consistent format:

project-version-job-subjob-env-detailOrCategory

  • Project: rice
  • Version: Without patch number (i.e. 2.4) would be used for branches or trunk development
    With patch number (i.e. 2.4.0) would be used for specific tagged versions
  • Job Type:
    • build: simple, nightly, revision
    • db: change-audit, install
    • deploy: functional, demo, performance
    • docbook: change-audit, install
    • license: ecl, third-party
    • release: perform, oss, site-deploy
    • scm: clean, update
    • site: deploy, deploy-docs-only
    • test: unit, integration, functional, performance
  • Env:  Currently referring to deployment environments (env1, env14, etc…)
  • Detail or Category: Special information regarding the build such as test process (jenkins or sauce labs), which application (krad-sampleapp, rice-sampleapp, rice standalone)

 

Proposal: Update all jobs to use scm job template 

Purpose:

Reuse, Simplify version updates

Changes:

All jobs that require use of svn will do so through job templates (i.e. rice-2.4-scm-clean).  

 

Proposal: Update all jobs using environments to do so through $DEPLOYENV variable

Purpose:

Simplify version updates

Changes:

Add parametrized build to all deploy and test-functional to use DEPLOYENV variable with default value and update remote.public.url and deploy.env values accordingly

 

Proposal: Update all non-deploy jobs to extract deployment tasks from their shell script

Purpose:

Prevent overlapping deployments, Reuse and DRY, Simplify version updates

Changes:

Replace all calls to deploy applications within script with triggered jobs as a build step or a post job step

  • No labels