Hi,
Have a similar problem in upgrading to a more recent image, we were stuck
on 2.19 for some time, and now trying to roll forward to the latest LTS.
We have a number of groovy scripts that are triggered by jobs that need to
execute in a system context (system groovy build step from
https://w
s
>> any sort of ACL permission system is in place. I find it helpful to
>> run this after a plugin update, I see the new versions of the plugins
>> in the jobs/*/config.xml. I'm using Jenkins LTS 1.565.3.
>>
>>
>>
>> On Wed, Oct 15, 2014 at 5:56 PM
ee the new versions of the plugins
> in the jobs/*/config.xml. I'm using Jenkins LTS 1.565.3.
>
>
>
> On Wed, Oct 15, 2014 at 5:56 PM, Darragh Bailey
> wrote:
> >
> > Just went through an upgrade from an old version of jenkins/plugins and
> > discovered that some
Just went through an upgrade from an old version of jenkins/plugins and
discovered that some jobs have not had their XML properly updated.
This is resulting in odd behaviour where triggered jobs do not appear in
the UI and are not readable, but the associated files appear on-disk.
By going to
