Thanks much Bruno! Luckily, the credentials issue was discovered to be user error where they were only attempting to use a ssh key instead of a simple username/password.
Should you, or anyone, feel like poking at the plugin though, the other issues on the todo list are: * properly object orienting the code base to be more in line with java and jenkins practices * moving the code base over to use the SuSe developed saltapi library (last I looked we were waiting on feature developments from the saltlib project) * supporting the new pipeline/workflow plugin On Saturday, March 19, 2016 at 4:51:25 PM UTC-5, kinow wrote: > > Hi Christian, > > We are evaluating Saltstack at work, and one of the tasks assigned to me > is to look into how to integrate our PHP/Java builds with the server > provisioning and configuration. > > I have a working test environment with one master and two minions, so will > try to install saltstack-plugin in a test Jenkins server and then toy with > it a little bit, and also try to reproduce the issue with the > credentials-plugin. Will report any comments in that issue (though I think > it might be better to use Jenkins JIRA?). > > Thanks > Bruno > > > ------------------------------ > *From:* Christian McHugh <[email protected] <javascript:>> > *To:* Jenkins Developers <[email protected] <javascript:>> > *Sent:* Saturday, 19 March 2016 3:18 AM > *Subject:* RFH: salt plugin > > Howdy everybody, > > A while back I created a plugin that allows you to define a build step > that kicks off salt calls through saltapi's rest interface. > https://github.com/jenkinsci/saltstack-plugin > https://wiki.jenkins-ci.org/display/JENKINS/saltstack-plugin > > The plugin works well for the intended purposes. However, I am not a > (java) programmer and due to a job change will not have as much time to > dedicate to becoming one :) As such, I was wondering if there was anyone in > the community willing to help assist with maintenance of this plugin and > perhaps help with modernizing and properly jenkins'ing the codebase. > > Specifically, I just released a version of the plugin that trades out > username/password fields in favor of using credentials ( :) ), but after > making the release I've gotten a bug report that the credentials dropdown > isn't being populated as expected ( :( ) > https://github.com/jenkinsci/saltstack-plugin/issues/16 > > This functionality works for me and some others that participated in some > beta releases, but since I'm not able to replicate I'm not sure where to go > from here. > > Is anyone able to provide guidance or direction on credentials usage or > able to perform a quick code review with me? > > > Thanks much! > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/a65543dc-0be4-42cb-9889-e35ea8186ca1%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/a65543dc-0be4-42cb-9889-e35ea8186ca1%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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-dev/14dd717a-9383-41ca-955c-c8a78ae8fb03%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
