Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-71866

rename "Build" and "Build with parameters" hyperlinks, buttons

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • core
    • None
    • 2.425

      There are a lot of different cases where Jenkins is not only used for building software, but also for pure automated deployment workflows, continued testing, or even running scheduled server power on/power off jobs.

      For this reason I would like to propose to rename "Build" and "Build with parameters" link on the left menu to "Run" and "Run with parameters". The same goes with "Build" button when "Build with parameters" link is clicked.

          [JENKINS-71866] rename "Build" and "Build with parameters" hyperlinks, buttons

          There is the Customize Build Now Label plugin for renaming the "Build" button. However, according to JENKINS-46554, it cannot rename "Build with Parameters".

          Kalle Niemitalo added a comment - There is the Customize Build Now Label plugin for renaming the "Build" button. However, according to JENKINS-46554 , it cannot rename "Build with Parameters".

          Vilius added a comment -

          Customize Build Now Label plugin would be a nice addition if one needs to change the text from the default on different pipelines. However, given that that plugin saw last activity 8 years ago, I'm not sure what its state is. Especially when using with declarative pipelines.

          My proposal is still to change the default text and then use the plugin in case one needs something else, not wise versa how it is now. 

          Vilius added a comment - Customize Build Now Label plugin would be a nice addition if one needs to change the text from the default on different pipelines. However, given that that plugin saw last activity 8 years ago, I'm not sure what its state is. Especially when using with declarative pipelines. My proposal is still to change the default text and then use the plugin in case one needs something else, not wise versa how it is now. 

          Apparently called via AlternativeUiTextProvider (javadoc) from ParametrizedJobMixin.getBuildNowText().  Huh, that looks like it would apply to "Build with Parameters" too.

          Kalle Niemitalo added a comment - Apparently called via AlternativeUiTextProvider ( javadoc ) from ParametrizedJobMixin.getBuildNowText() .  Huh, that looks like it would apply to "Build with Parameters" too.

          If the default text were changed to "Run", then would one also have to rename "Discard Old Builds", "Disable Build", "Execute concurrent builds", etc.?

          The Customize Build Now plugin could perhaps be changed to make it invokable from pipelines like so:

          options {
            customizeBuildNow('Run')
          }
          

          I wonder if just adding @symbol("customizeBuildNow") would suffice.

          Kalle Niemitalo added a comment - If the default text were changed to "Run", then would one also have to rename "Discard Old Builds", "Disable Build", "Execute concurrent builds", etc.? The Customize Build Now plugin could perhaps be changed to make it invokable from pipelines like so: options { customizeBuildNow( 'Run' ) } I wonder if just adding @symbol("customizeBuildNow") would suffice.

          Vilius added a comment -

          If the default text were changed to "Run", then would one also have to rename "Discard Old Builds", "Disable Build", "Execute concurrent builds", etc.?

          Good question. I do believe these probably also needs adjustment some time into the future, however I would consider them of less importance and out of scope of this task. That's because the main reason of my proposed change is to make UI more understandable for simple Jenkins pipeline users, who execute pipelines daily, not operators  or developers of the pipelines.

          Vilius added a comment - If the default text were changed to "Run", then would one also have to rename "Discard Old Builds", "Disable Build", "Execute concurrent builds", etc.? Good question. I do believe these probably also needs adjustment some time into the future, however I would consider them of less importance and out of scope of this task. That's because the main reason of my proposed change is to make UI more understandable for simple Jenkins pipeline users , who execute pipelines daily, not operators  or developers of the pipelines.

          Vilius added a comment -

          I see that this ticket is marked as Done. Just wondering how I could test this in latest version? Does mentioned annotation in declarative pipeline works now?

          From the code it looks like nothing really was changed. The PR is more related to JENKINS-46554 than this ticket.

          Vilius added a comment - I see that this ticket is marked as Done. Just wondering how I could test this in latest version? Does mentioned annotation in declarative pipeline works now? From the code it looks like nothing really was changed. The PR is more related to JENKINS-46554 than this ticket.

          vilius, https://github.com/jenkinsci/customize-build-now-plugin/pull/5 references JENKINS-46554 and adds @Symbol("customizeBuildNow") to BuildNowTextProperty.DescriptorImpl in the Customize Build Now plugin, but it has not been merged yet. I think that will allow the text to be set by a pipeline but I am not sure whether the syntax will be options or properties.

          Kalle Niemitalo added a comment - vilius , https://github.com/jenkinsci/customize-build-now-plugin/pull/5 references JENKINS-46554 and adds @Symbol("customizeBuildNow") to BuildNowTextProperty.DescriptorImpl in the Customize Build Now plugin, but it has not been merged yet. I think that will allow the text to be set by a pipeline but I am not sure whether the syntax will be options or properties .

          Markus Winter added a comment - - edited

          Declarative:

          options {
            customizeBuildNow alternateBuildButton: 'Run', alternateBuildNow: 'Run', alternateBuildWithParams: 'Run with Parameters'
          }

          Scripted:

          properties([customizeBuildNow(alternateBuildButton: 'Run', alternateBuildNow: 'Run', alternateBuildWithParams: 'Run With Parameters')])

          Markus Winter added a comment - - edited Declarative: options {   customizeBuildNow alternateBuildButton: 'Run' , alternateBuildNow: 'Run' , alternateBuildWithParams: 'Run with Parameters' } Scripted: properties([customizeBuildNow(alternateBuildButton: 'Run' , alternateBuildNow: 'Run' , alternateBuildWithParams: 'Run With Parameters' )])

          Markus Winter added a comment - - edited

          Released as 15.vb_342d7b_90df0

          You can also define the values globally now, with job configuration taking precedence

          Markus Winter added a comment - - edited Released as 15.vb_342d7b_90df0 You can also define the values globally now, with job configuration taking precedence

            mawinter69 Markus Winter
            vilius Vilius
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: