[JIRA] Resolved: (JENKINS-8572) Credentials visable in UI and configuration gets corrupted

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] Resolved: (JENKINS-8572) Credentials visable in UI and configuration gets corrupted

JIRA noreply@jenkins-ci.org

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

teilo resolved JENKINS-8572.
----------------------------

    Fix Version/s:     (was: current)
       Resolution: Duplicate

duplicate of JENKINS-8524

> Credentials visable in UI and configuration gets corrupted
> ----------------------------------------------------------
>
>                 Key: JENKINS-8572
>                 URL: http://issues.jenkins-ci.org/browse/JENKINS-8572
>             Project: Jenkins
>          Issue Type: Bug
>          Components: m2release
>    Affects Versions: current
>         Environment: Hudson: 1.385
> m2release plugin: 0.6.1
> Maven: 2.2.1
>            Reporter: domi
>            Assignee: teilo
>            Priority: Blocker
>         Attachments: befor_release.jpg, while_building.jpg
>
>
> After triggering a release build, the whole commandline is visable in the original maven build section - including the SCM credentials!
> Reproduce:
> - configure release plugin (see attachement "befor_release.jpg")
> - start a release build
> - define SCM credentials
> - trigger build
> - wait 1 minute
> - open the jobs configuration
> - check the build configuration -> you'll find the credentials in the "Goals and options" field of the Build section (not the one from the release plugin configuration - see attachement "while_building.jpg")
> Strange enough, we even had cases where this values where persistet to the configuration!
> unfortunatly this is an absolut killer for this plugin.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira