Continuous integration is there any job naming conventions in the jenkins

jenkins continuous-integration continuous-delivery
user2750116 picture user2750116 · Apr 6, 2016 · Viewed 7.9k times · Source

I would like to know if we have any job naming conventions exist in the continuous integration. we are using Jenkins for Ci , please suggest .

naming conventions should be something like this , environment, service, purpose build or deploy etc.

any other suggestions are appreciated.

Answer

Thomas Hirsch picture Thomas Hirsch · Nov 22, 2016

I am using a convention that goes like this:

<primary purpose of the job | uppercase>_<(GitHub) project name>_<branch name / additional info>

So jobs would be named like

BUILD_my-project
DEPLOY_my-project_staging
TEST_my-project_staging
UTILITY_install-helpful-tool_staging
INFRA_run-job-dsl

To make things easier to maintain, especially when using the JobDSL I prefer to not have separate display names for jobs, at the cost of having both hyphens and underscores in job names.

Related questions

How to trigger Jenkins builds remotely and to pass parameters

I am invoking a Jenkins job remotely using: wget http://<ServerIP>:8080/job/Test-Jenkins/build?token=DOIT Here Test-Jenkins job is invoked and DOIT is the security token that I have used. Now I need to pass some parameters …

Read More
How to set environment variables in Jenkins?

I would like to be able to do something like: AOEU=$(echo aoeu) and have Jenkins set AOEU=aoeu. The Environment Variables section in Jenkins doesn't do that. Instead, it sets AOEU='$(echo aoeu)'. How can I get …

Read More
How to choose between Hudson and Jenkins?

It took me an hour or so to work out Hudson has only branched recently (Jan/2011) I have no idea how rapid the change of each branch is now, but more importantly, what is the direction each branch is taking …

Read More