|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
Hi @Supratim,
When we commit our code to Jenkins repositories at GitHub, usually we include special tokens (JENKINS-9999, or [FIXED JENKINS-9999]. Jenkins has some backend jobs that read the commit log and resolve and stop the progress on the issues. Then the plug-in maintainer releases a new version and, once it's released, he/she closes the issues.
I've just released Jenkins TestLink Plug-in 3.3, this new version includes the fix for this issue. Keep an eye on @jenkins_release and once you see TestLink Plug-in there, update your Jenkins instance and the issue should be gone.
Let me know if that works, ok? Cheers, Bruno