ccmenu
ccmenu copied to clipboard
ccmenu
Ability to prepend jenkins instance name to build name
In my workplace we have one Jenkins instance per project, which is running a pipeline of jobs such as build/system test/user acceptance etc.
Each Jenkins has identical build names and it makes it difficult to understand which build is associated with a given project in CCMenu.
It would be nice if we could specify a Jenkins Name/Project Name that is prepended on to each Jenkins Build.
What is the "Jenkins name"? Do you mean the hostname / some abbreviation of the host name?
Hi Erik - My first thought is just a custom name which could be assigned at configuration time in CCMenu. I'm not sure (in our case at least) that an instance name exists or can be populated.
I see. Just like a name field that by default gets populated with the project name from the CI server, but that can be edited/overridden. Sounds like a good feature.
+1 We have a lot of Jenkins builds that I care about, and they all have long, convoluted names. A customizable 'nickname' field for each project would be awesome.
+1 Currently on my list there are just a bunch of items called "Trigger" and I don't know which one is which. Please add option to set custom name for each project.
This seems like a really desirable feature, probably a simple approach with a prefix field that is by default empty would work very well.
@erikdoe Thanks for the hint! Now I am running the code from trunk and it mostly works. Here are my observations so far
- If you enable "with last build time" you lose the prefix from display
- I find the option for prefix quite hard to find, i was expecting to see a new field in add job screen
- I usually want to add a prefix per server instead of for each added job, imagine that we have 500 jobs on most of our servers. Good that I usually cctray monitor only about 20, because managing prefixes would have been near to impossible.
- I know that adding GUI takes a lot of effort, but I want to remark that I would not mind if instead of that fancy UI I would have a simple YAML file with the config. No more UI for config options means more time to focus on other cool features.
I am not sure that others think about this but considering that we are all developers, editing a text file should be easier than clicking a lot. Also I love being able to include it in a git repo.
Thanks for the feedback. Much appreciated. Some comments:
- Losing this prefix is a bug, which I hadn't noticed; obviously a test is missing somewhere. Will look into it.
- I thought about adding the display name to the add-project flow, but didn't know where to put it. The issue is that I wanted to stick with one term, ie. display name, and I didn't know how to apply this to multiple projects.
- Regarding the last point and handling many projects. Maybe adding two additional entries to the menu would help: add prefix to project names and reset display names. These would work on a multi selection.
- Regarding the point about the UI. This has been requests before, see #24 for example. The comments over there also contain a description on how you can modify the config on a textual level today.
Hope this helps.
If you feel strongly about having a mechanism to add the same prefix to multiple projects at the same time, please open a new issue for that.
Thanks for the new release! Maybe I am missing something but my impression is that current implementation does not fully address the original issue, is more like an workaround that allows user to override the name of the build.
Overriding the name of the build from the server is very different than adding a suffix to all jobs from one server (url).
I don't mind adding a new ticket but I think the title and description of this ticket should be changed in order to avoid confusions because what is described in them is not addressed by the 1.13 release.