-
Improvement
-
Resolution: Fixed
-
Minor
-
None
-
Jenkins - 2.73.3
TFS plugin - 5.121.0
The "Trigger release in TFS/Team Services" post build action requires that you specify the user name and password/PAT.
The core issue here is that this post build action should instead require global Jenkins credentials instead of the user directly providing their creds here.
The negative side effect that currently exists, is that each time you update the job, the credentials get wiped out and the user must re-enter them - in other words, you can't make any changes to the job at all without always having to re-enter the creds.
There is a feature request mentioning the need for using global creds: https://issues.jenkins-ci.org/browse/JENKINS-37795
I went ahead and logged this separate bug because the current experience where you must re-enter creds each time that you save is painful and wanted to make sure this wasn't overlooked.
----------------------------
Update on this - I upgraded to newer version of the plugin and don't see the behavior any more where the creds are getting wiped out, so this issue can be closed.
However, the issue I linked to where global Jenkins creds is still applicable.
This issue was fixed in the 5.126.0 release. Thank you for using the tfs plugin!