Display name different from Job name

35 views
Skip to first unread message

Sverre Moe

unread,
Apr 13, 2015, 8:26:56 AM4/13/15
to jenkins...@googlegroups.com
I have duplicated jobs in different views.

Development: Job
View1: Job1
View2: Job2
View3: Job3

When I am standing in View3, is it possible to show job/project name Job instead of Job3? Have a different display name that is different from Project name.
Job to Job3 is the same project, but with different Git branch to build.

Since the job name must be unique in Jenkins, it would be great if one could instead use a Display name in the view listing.

Development: Job
View1: Job
View2: Job
View3: Job

Sverre Moe

unread,
Apr 13, 2015, 9:10:55 AM4/13/15
to jenkins...@googlegroups.com
I found setting Display Name. Problem with this is under view All, there will be a number of projects with the same display name. One has to hover over them to find out which project name it is.

Stephen Connolly

unread,
Apr 13, 2015, 9:42:39 AM4/13/15
to jenkins...@googlegroups.com
why not use folders to group the jobs... that way you can reuse the Job name in each folder

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/06019381-b30a-4613-b798-176cc3942806%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sverre Moe

unread,
Apr 13, 2015, 9:49:34 AM4/13/15
to jenkins...@googlegroups.com

Stephen Connolly

unread,
Apr 13, 2015, 10:11:05 AM4/13/15
to jenkins...@googlegroups.com
Yes. That is a free OSS plugin but sales would not let us make it open source without retaining "CloudBees" in the name 

Les Mikesell

unread,
Apr 13, 2015, 10:43:33 AM4/13/15
to jenkinsci-users
On Mon, Apr 13, 2015 at 9:10 AM, Stephen Connolly
<stephen.al...@gmail.com> wrote:
> Yes. That is a free OSS plugin but sales would not let us make it open
> source without retaining "CloudBees" in the name
>

That's... confusing. How do you distinguish what is open and what isn't?

--
Les Mikesell
lesmi...@gmail.com

Stephen Connolly

unread,
Apr 13, 2015, 11:09:47 AM4/13/15
to jenkins...@googlegroups.com
Easy, if it is in wiki.jenkins-ci.org and the source code published on github/jenkins then it's OSS

If it's not there but listed in release-notes.cloudbees.com then it will only show up in our proprietary update center (so you only see them if you have a license) and the source code will probably be in github.com/cloudbees and not source code you can see.

Basically, if you can see it in your update center (unless it is https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Enterprise+by+CloudBees) then it is free to install and unencumbered by a license requirement

--
You received this message because you are subscribed to the Google Groups "Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com.

Stephen Connolly

unread,
Apr 13, 2015, 11:11:09 AM4/13/15
to jenkins...@googlegroups.com
On 13 April 2015 at 16:09, Stephen Connolly <stephen.al...@gmail.com> wrote:
Easy, if it is in wiki.jenkins-ci.org and the source code published on github/jenkins then it's OSS

If it's not there but listed in release-notes.cloudbees.com then it will only show up in our proprietary update center (so you only see them if you have a license) and the source code will probably be in github.com/cloudbees and not source code you can see.

Basically, if you can see it in your update center (unless it is https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+Enterprise+by+CloudBees) then it is free to install and unencumbered by a license requirement

Obviously if you have a CloudBees license then you will be seeing our update center and consequently you will see our closed source plugins, but you will be able to install them as you have a license for them in that case anyway!!! 
Reply all
Reply to author
Forward
0 new messages