Enhancement #1848
Do not remove repository credentials while regenerating a job
Status: | Rejected | Start date: | 04/16/2014 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Moringen | % Done: | 0% | |
Category: | Jenkins API | |||
Target version: | 0.3 |
Description
In case a jenkins job already exists and the user configured credentials manually for the repository checkout, do not remove the credentials during regeneration.
Related issues
History
#1 Updated by J. Moringen almost 10 years ago
- Tracker changed from Bug to Enhancement
Considering how Jenkins' new credentials architecture works, this is unlikely to happen.
#2 Updated by J. Moringen almost 10 years ago
- Category set to Jenkins API
#3 Updated by J. Moringen almost 10 years ago
- Target version set to 0.3
#4 Updated by J. Moringen over 9 years ago
- Status changed from New to Rejected
Will be solved by implementing #1984.
#5 Updated by J. Moringen over 9 years ago
- Related to Enhancement #1984: Use credentials plugin for authenticating SCM access added