Ah, also, I saw in this thread <https://groups.google.com/forum/#!searchin/jenkinsci-users/encrypt|sort:relevance/jenkinsci-users/Ap3C-RJaRrU/aAhBBit_OKkJ> a similar thing was asked. The suggestion is to use plain text. What do you think about this?
On Friday, December 23, 2016 at 9:57:44 AM UTC+3, Ali Ok wrote: > > Hi, > > Some story: > We are working on a project where we run Jenkins on OpenShift and we have > Linux slaves and OSX slaves. > Linux slaves are handled by OpenShift itself, but for OSX slaves we need > to do manual work. > In order to make the connection between Jenkins master and OSX slave, we > use SSH. For now, we start with password based authentication. > > Now, when I make the setup for OSX slave using the GUI, I can see in > credentials.xml there is something like this: > > > <com.cloudbees.plugins.credentials.impl.UsernamePasswordCredentialsImpl> > ... > <password>3uYDDPNS7g9eg8Hq9FLnrN+ZF+SZCteOYnkbl614gf4=</password> > > </com.cloudbees.plugins.credentials.impl.UsernamePasswordCredentialsImpl> > > > However, I am having trouble encrypting the password to this text > programmatically! The credentials.xml file should be filled by our script. > > I have seen many Python scripts which are doing the decryption, but I > wasn't able to make them work. Maybe they were for Jenkins 1.x. > > Please note that I need to do the encryption using Bash scripts. So, I > cannot use the Groovy util. > > Has anybody done something similar? > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3b4de10e-bd5f-40dc-96cf-3af13e645b5e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
