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

FreeStyle and Native Maven jobs should be disabled

    Details

    • Type: Task
    • Status: Resolved (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: evergreen
    • Labels:
      None
    • Sprint:
      Evergreen - Milestone 1
    • Similar Issues:

      Description

      Jenkins Essentials aims at providing an opinionated version of Jenkins, with an Obvious Path To User Success.

      For this purpose, we want to provide Pipeline jobs only to users, at least for now. I.e. FreeStyle and native Maven jobs should be hidden or removed.

        Attachments

          Activity

          Show
          danielbeck Daniel Beck added a comment - https://github.com/daniel-beck/hide-maven-plugin/ ?
          Hide
          batmat Baptiste Mathus added a comment -

          Heh, yeah, exactly . Your code is a bit less convoluted than the one I wrote in https://github.com/jenkinsci/essentials-plugin/pull/10

          Show
          batmat Baptiste Mathus added a comment - Heh, yeah, exactly . Your code is a bit less convoluted than the one I wrote in https://github.com/jenkinsci/essentials-plugin/pull/10
          Hide
          batmat Baptiste Mathus added a comment -

          Oh, wait, you actually used DescriptorVisibilityFilter and I used jenkins.ExtensionFilter, wondering if there is one that is recommended. The outcome seems to be the same.

          AIUI, the PR I filed really makes the whole extension unavailable to the extension system, when DescriptorVisibilityFilter only acts on the UI side.

          Show
          batmat Baptiste Mathus added a comment - Oh, wait, you actually used DescriptorVisibilityFilter and I used jenkins.ExtensionFilter , wondering if there is one that is recommended. The outcome seems to be the same. AIUI, the PR I filed really makes the whole extension unavailable to the extension system, when DescriptorVisibilityFilter only acts on the UI side.
          Hide
          batmat Baptiste Mathus added a comment -

          https://github.com/jenkinsci/essentials-plugin/pull/10 is the Java/Jenkins part. To wrap this up, now I need to 1) bump to this version on evergreen side, which I already did locally, and it works fine when testing manually. And 2) add a test for this in distribution/tests/tests.sh in evergreen repo.

          Show
          batmat Baptiste Mathus added a comment - https://github.com/jenkinsci/essentials-plugin/pull/10 is the Java/Jenkins part. To wrap this up, now I need to 1) bump to this version on evergreen side, which I already did locally, and it works fine when testing manually. And 2) add a test for this in distribution/tests/tests.sh in evergreen repo.
          Hide
          danielbeck Daniel Beck added a comment -

          DVF fit my use case way back when better: Supporting existing Maven jobs while hiding it from the UI (still allowed copying, POST config.xml, etc.).

          EF seems better here (but might be slightly more dangerous).

          Show
          danielbeck Daniel Beck added a comment - DVF fit my use case way back when better: Supporting existing Maven jobs while hiding it from the UI (still allowed copying, POST config.xml, etc.). EF seems better here (but might be slightly more dangerous).

            People

            • Assignee:
              rtyler R. Tyler Croy
              Reporter:
              batmat Baptiste Mathus
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: