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

Pod templates aren't necessarily followed

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      In our pipelines we use pod templates to specify the build environment. The issue is that when I update a container image in the pod template the old version of the pod template still exists on Jenkins. This is evident in the "Cloud" settings within Jenkins /configure page. A new template is also created with the correct settings. However an issue arises because the pod label is the same on both templates and Jenkins uses the old template.

      I consider this a bug because I feel that whatever is specified in my pod template code should be what is run.

      One possible solution on my end is to version the name of the pod template and I believe that would alleviate these issues. However without any sort of proper cleanup the amount of templates will just build and build within the Jenkins configure page which is certainly undesirable.

      Ideally I feel that nothing should be stored on Jenkins in terms of pod templates and only my pod template code upon execution is considered.  

      Thoughts? 

      Thanks for your time.

        Attachments

          Issue Links

            Activity

            steve21168 Steven Goodstein created issue -
            larslawoko Lars Lawoko made changes -
            Field Original Value New Value
            Link This issue duplicates JENKINS-47759 [ JENKINS-47759 ]
            steve21168 Steven Goodstein made changes -
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]

              People

              Assignee:
              csanchez Carlos Sanchez
              Reporter:
              steve21168 Steven Goodstein
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: