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

LogRotator set globally on the instance

    XMLWordPrintable

Details

    Description

      As a Jenkins administrator, I'd like to be able to set the logrotator on the jobs on my instance. I'd like this value to be "read-only" on the jobs, so the users of my instance cannot change it. This way, I'm sure that the space usage of the builds is handled correctly.

      Today, it is possible to use the configuration slicing plugin to "re-apply" this logrotator configuration on the jobs from time to time. However, this task is time-consuming and having a way to prevent my users to change this value on the job configuration would be a more reliable solution. 

       

      Another solution would be to have the value set globally, and accept the users to change it on the job level, but the global value would act as a default value at the job creation time.

      Attachments

        Activity

          rtyler R. Tyler Croy added a comment -

          Nothing I've filed, but definitely in support of this concept

          rtyler R. Tyler Croy added a comment - Nothing I've filed, but definitely in support of this concept
          danielbeck Daniel Beck added a comment -

          Good point. I know rtyler has been complaining about lack of pipeline management, perhaps this is a duplicate of something he filed?

          danielbeck Daniel Beck added a comment - Good point. I know rtyler has been complaining about lack of pipeline management, perhaps this is a duplicate of something he filed?

          danielbeck I guess it could also be a per-folder configuration but a global configuration would still be nice. It would also be something less to worry about when creating new MultiBranch Pipeline on the instance. 

          alecharp Adrien Lecharpentier added a comment - danielbeck I guess it could also be a per-folder configuration but a global configuration would still be nice. It would also be something less to worry about when creating new MultiBranch Pipeline on the instance. 
          danielbeck Daniel Beck added a comment -

          Probably better off separate from core. This looks a lot like something that needs to implement various org dependent strategies.

          danielbeck Daniel Beck added a comment - Probably better off separate from core. This looks a lot like something that needs to implement various org dependent strategies.

          even with configuration-slicing, I need to reapply the configuration from time to time and if I don't for a long period of time, users can set the logrotation values and use all the space of the JENKINS_HOME.

          Also, from their point of view, they have a part of their jobs configuration that change without them knowing why (well, they do know but they disagree). So having this configuration "disabled" when set globally would make them understand they cannot modify it.

          alecharp Adrien Lecharpentier added a comment - even with configuration-slicing, I need to reapply the configuration from time to time and if I don't for a long period of time, users can set the logrotation values and use all the space of the JENKINS_HOME. Also, from their point of view, they have a part of their jobs configuration that change without them knowing why (well, they do know but they disagree). So having this configuration "disabled" when set globally would make them understand they cannot modify it.
          danielbeck Daniel Beck added a comment -

          this task is time-consuming

          Is configuration-slicing still around?

          danielbeck Daniel Beck added a comment - this task is time-consuming Is configuration-slicing still around?
          oleg_nenashev Oleg Nenashev added a comment -

          It would be nice

          oleg_nenashev Oleg Nenashev added a comment - It would be nice

          People

            Unassigned Unassigned
            alecharp Adrien Lecharpentier
            Votes:
            2 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: