Vertretungsberechtigte Geschäftsführer Gordon Davies, Madhu Ranganathan, Christian Waida, Registergericht Amtsgericht Bonn, Registernummer HRB 10646
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.
it's hard to tell you, how your job names should look like. You will need to sit down (with colleagues) and think, what you need. Here is what we do: ['...' means *our* naming convention for things]
We separate our job names in 'slots'; 'slots' are separated by '-' (because we got names from outside, which use '_' in what could be a content for a slot). We use '.' to separate items in one "slot', if we should need it. We have the following slots: (you'll see that you need to get your own ;-)
# System component ("Jenkins" for CI-internal stuff)
# purpose (build/test/publish/...)
discriminator (if we need several jobs of the same type; e.g. for different users)
If a slot is unused, just the '-' remains, e.g.
b: PHY_TX------ciScriptsUpdate (and this should have been named JENKINS-... - we have our slips...)
We have a "'jobNameParser' which picks apart these things, and is used so the jobs do what their name says they should do. (For special jobs, 'b' above, we don't use that; only for more generic like 'a')
The order you choose, should e.g. give a reasonable sorting.
Now you need to find a structure fitting your needs. (*)
Have the appropriate amount of fun
(*) We had literally discussions on and off over weeks, years ago, before we settled for our current structure.
Martin Schmude schrieb am Mittwoch, 27. Januar 2021 um 17:53:42 UTC+1:
at the department I am working at we operate a Jenkins with ~100 pipeline jobs.
The jobs have evolved over ~4 years without any conventions about job and stage names.
Today we have a mess. Related jobs cannot easily be recognized by name. The "logic" how a job is sectioned into stages is different between all jobs.
We want to clean up and establish naming conventions. Before thinking a lot myself an issue I want to become aware of how others solved it.
Maybe there are well established naming conventions out there that we don't know, but could adopt easily. At jenkins.io I didn't land a hit.