[ 
https://issues.jenkins-ci.org/browse/JENKINS-13369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

domi resolved JENKINS-13369.
----------------------------

    Resolution: Fixed

I just released version 0.3 of the managed-scripts plugin to fix this issue.
                
> Lost 'Managed script file' section and all saved scripts after Jenkins upgrade
> ------------------------------------------------------------------------------
>
>                 Key: JENKINS-13369
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-13369
>             Project: Jenkins
>          Issue Type: Bug
>          Components: config-file-provider, managed-scripts
>    Affects Versions: current
>            Reporter: Tetiana Tvardovska
>            Assignee: domi
>            Priority: Critical
>         Attachments: configfiles_ci_localhost.JPG, 
> configfiles_ci_localhost_inspection.JPG
>
>
> The section "Managed script file - create a managed/reusable script") had 
> disappeared with all saved scripts after Jenkins upgrade to ver. 1.458. 
> See attached screenshot, right site 'ci:8080'
> It happened after upgrading a headless system using option 'Upgrade 
> Automatically'.
> Jenkins ver. 1.458.
> [Managed 
> Scripts|https://wiki.jenkins-ci.org/display/JENKINS/Managed+Script+Plugin] 
> version 0.2.0
> Bug is related to the [Config File Provider 
> Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]
>  version 2.0.
> PS Other installation (localhost on the attached screenshot) on Ubuntu system 
> had not lost scripts and still shows all scripts and saved scripts. It has 
> [Config File Provider 
> Plugin|https://wiki.jenkins-ci.org/display/JENKINS/Config+File+Provider+Plugin]
>  older version 1.2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to