|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-13230) Not able to use Jenkins ... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)
- [JIRA] (JENKINS-13230) Not able to use Jen... [email protected] (JIRA)

@bap by "natural", i meant standard behaviour of vanilla jenkins. i would have expected the publish-over-ssh plugin to replicate that behaviour. i am surprised that an extra token plugin might be needed for that purpose.
but you are right, after rereading this issue, it might not have anything to do with it.
i will remove my comment and post it on my issue.