> > Hi Mark, >> > I searched through /var/lib/Jenkins on the server. The credentialsID is in com.dabsquared.gitlabjenkins.connection.GitLabConnectionConfig.xml so I have no idea where that might correspond to something in Jenkins. The thing that most concerns me here is that it did work and was relatively easy to set up and now, after several Jenkins and plugin and gitlab upgrades, it does not work. And seems now to be very complicated. For instance, on build triggers for a job, (Build when a change is pushed to GitLab - advanced) I generated a secret key but did not want it so used previous page to back out. Agreed to leave page and yet the secret key is now there and saved. The gitlab plugin seems to have taken steps backwards.
I also wonder if the instructions are keeping pace with changes? John -- 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/cc379234-df3a-49e6-bfe6-76c718884c2d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
