![]() ![]() ![]() ![]() There are two plugins in jenkins related to ssh that can be used: Publish Over SSH and Jenkins SSH plugin. If you have a parametrized build, you also can define HOME that way and check if your slave picks up the right value for HOME: (as mentioned in " git clone with ssh issue") Don't forget to have both id_rsa and id_rsa.pub in the %HOME%\.ssh directory: you need both public and private ssh keys.If it is not, that may mean you need to add that variable to the "system environment variables", not the "user environment variables". you need to make your slave display ' set' in order to check if HOME is defined when used with the SYSTEM account.Similar resolution: " Problem with Hudson Git Gitosis on windows".Similar issue: " Problem with Hudson Git Gitosis on windows".My slave agent running as service under SYSTEM account. I've put correct id_rsa under the C:\jenkins\.ssh but still have this issue. I've specified to override HOME on the windows slave node to point it to C:\jenkins. Since Windows doesn't have a HOME, you need to define it explicitly, to whatever directory you want. As I commented, specifying the HOME environment variable is key, when using ssh protocol. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |