Re: Deletion of a GitHub Repository in a GitHub Organization

2020-02-15 Thread Jan Monterrubio
Does it disappear if you force an Organization Scan? On Sat, Feb 15, 2020 at 15:10 'Maik Brauer' via Jenkins Users < jenkinsci-users@googlegroups.com> wrote: > Hi, > > > > I have a GitHub Repository inside a GitHub Organization. All is properly > scanned by Jenkins. > > When no deleting a GitHub

WARNING hudson.FilePath#_getChannelForSerialization: A FilePath object is being serialized when it should not be, indicating a bug in a plugin. See https://jenkins.io/redirect/filepath-serialization

2020-02-15 Thread kumar reddy
Hi All, Seeing the below warning on jenkins 2.190.3. Eventhough it is a warning it is annoying by creating huge logs If any one has come across this please let me how to resolve this 2020-02-14 03:50:03.740+ [id=223127]WARNING hudson.FilePath#_getChannelForSerialization: A FilePath

Deletion of a GitHub Repository in a GitHub Organization

2020-02-15 Thread 'Maik Brauer' via Jenkins Users
Hi, I have a GitHub Repository inside a GitHub Organization. All is properly scanned by Jenkins. When no deleting a GitHub Repo, I would expect that it will be deleted also from the Jenkins GitHub Organization. It still stays there. What else can we do to get rid of this Repo Finally?

Re: step in build suddenly injecting new parameter flags, resulting in build failure

2020-02-15 Thread Glenn Caccia
Unfortunately, no. The POM and project are in source control. No changes. The maven plugin axistools is a very old plugin that hasn't had a new version since 10 years ago. Plus, if I build the project directly through maven locally, it builds fine without the additional parameters that I

Re: Frequent "Disconnected computer for node" messages in jenkins logs

2020-02-15 Thread Ivan Fernandez Calvo
After seen the log I understand you are asking for the INFO messages that inform that a Docker agent is disconnected, IIRC those messages are normal they only inform about the Docker agent status, you can change the verbose level of the Java package on logs configuration to omit those type of

Re: step in build suddenly injecting new parameter flags, resulting in build failure

2020-02-15 Thread James Nord
Could it be that you have not locked the versions of maven plugins in your maven pom.xml? the axis-maven-plugin or whatever you are using to generate the wsdl that's failing could have been updated and you may be getting a newer version than you used to in the CO environment.