Re: declarative pipeline and gitlab
Hi Gabriele, yes, you are right,thanks. The issue was the URL used (I need to RTFM carefully)... as it seems you have experience with this: by using pipeline so far I get in Jenkins only a note like "Started by GitLab push by.." without any link to gitlab merg request.. by using freestyle job, the links are overall there. did you manage to get this? Best Regards, Pablo On Monday, October 21, 2019 at 1:48:03 PM UTC+2, Gabriele Bonetti wrote: > > Hi, > > Maybe it's a "mister obvious" answer but have you set up the build trigger > on the receiving pipeline? In the pipeline configuration you should have an > option "Build when a change is pushed to gitlab" that you can enable and > select the set of the events that would trigger the pipeline. > Also from here you can confirm that the webhook you are using is correct. > > > > On Tuesday, October 15, 2019 at 10:47:12 AM UTC+2, Pa Y wrote: >> >> Hello, >> has somebody managed successfully to use declarative pipeline and gitlab? >> >> I followed the instructions listed here: >> https://docs.gitlab.com/ee/integration/jenkins.html and this works for >> freestyle jobs. we use this already without problems. >> >> Now, I try to move to pipelines to have more options in general. >> >> So far, we get gitlab hook sent succcessfully but for this we need to >> disable in Jenkins : Prevent Cross Site Request Forgery exploits , what >> I don't really want... >> >> And anyway after hook was sent, Jenkins job can't be triggered >> >> can maybe somebody share a running example? >> >> Thanks for any help in advance! >> >> Pablo >> >> >> -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/708e7ee8-1651-40fb-b0c8-6f7a6368bef5%40googlegroups.com.
Re: Git-client plugin version 2.8.6 breaks authentication on Windows box
Thanks. I think you provided the information I needed. I'm not planning to take any action on that bug report other than to watch that it is not a common occurrence for other users. On Mon, Oct 21, 2019 at 1:01 PM Patrick van der Velde < petrikvanderve...@gmail.com> wrote: > Created issue 59875: https://issues.jenkins-ci.org/browse/JENKINS-59875 > > Let me know if you need additional information. > > On Tuesday, 22 October 2019 00:41:45 UTC+13, Mark Waite wrote: >> >> Thanks. >> >> Could you open an issue on Jira >> https://issues.jenkins-ci.org/secure/Dashboard.jspa that describes the >> environment more fully? >> >> I'm running CLI git 2.7 on at least one machine (Ubuntu 16.04) and can >> successfully clone an https private repository from Visual Studio Online at >> https://markwaite.visualstudio.com/DefaultCollection/_git/elisp . I'm >> running CLI git 2.17 (not 2.18) on at least one other machine (Amazon Linux >> 2) and can successfully clone an https private repository from Visual >> Studio Online at >> https://markwaite.visualstudio.com/DefaultCollection/_git/elisp . >> >> I'd like more information about your environment to be included in that >> Jira issue. I need to know what version of Team Foundation Server you're >> running, what version of Windows, any details about the authentication >> techniques in use (appears to be http rather than https to your TFS server, >> assumed that the username and password do not contain Windows special >> characters like '%', etc.), what versions of CLI git were failing, what >> versions are now working, >> >> Thanks in advance for providing that information in case other users >> encounter the same problem. >> >> On Sun, Oct 20, 2019 at 10:26 PM Patrick van der Velde < >> petrikva...@gmail.com> wrote: >> >>> To answer my own question: Updating to the latest version of GIT fixes >>> it. >>> >>> Thanks Mark!!! >>> >>> On Monday, 21 October 2019 15:34:16 UTC+13, Patrick van der Velde wrote: Hi Our setup Server: - Jenkins 2.190.1 - Ubuntu 16.04.5 Agent - Jenkins swarm slave - Windows 2016 Source control: - GIT on TFS2018 When running with git-client plugin 2.8.6 we get the following error in the build log Running as SYSTEM [EnvInject] - Loading node environment variables. Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm role_generators team_development tool_msbuild tool_git) in workspace C:\ops\jenkins\workspace\testproduct12---b4eb99a4 [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is used... using credential sandboxuser Cloning the remote Git repository Cloning repository http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 > C:\Program Files\Git\cmd\git.exe init C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 Fetching upstream changes from http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 > C:\Program Files\Git\cmd\git.exe --version # timeout=10 using GIT_ASKPASS to set credentials User to access the sandbox project and the repos inside it. > C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 +refs/heads/*:refs/remotes/origin/* ERROR: Error cloning remote repo 'origin' hudson.plugins.git.GitException: Command "C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: fatal: Authentication failed for ' http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123/ ' at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at
Re: Git-client plugin version 2.8.6 breaks authentication on Windows box
Created issue 59875: https://issues.jenkins-ci.org/browse/JENKINS-59875 Let me know if you need additional information. On Tuesday, 22 October 2019 00:41:45 UTC+13, Mark Waite wrote: > > Thanks. > > Could you open an issue on Jira > https://issues.jenkins-ci.org/secure/Dashboard.jspa that describes the > environment more fully? > > I'm running CLI git 2.7 on at least one machine (Ubuntu 16.04) and can > successfully clone an https private repository from Visual Studio Online at > https://markwaite.visualstudio.com/DefaultCollection/_git/elisp . I'm > running CLI git 2.17 (not 2.18) on at least one other machine (Amazon Linux > 2) and can successfully clone an https private repository from Visual > Studio Online at > https://markwaite.visualstudio.com/DefaultCollection/_git/elisp . > > I'd like more information about your environment to be included in that > Jira issue. I need to know what version of Team Foundation Server you're > running, what version of Windows, any details about the authentication > techniques in use (appears to be http rather than https to your TFS server, > assumed that the username and password do not contain Windows special > characters like '%', etc.), what versions of CLI git were failing, what > versions are now working, > > Thanks in advance for providing that information in case other users > encounter the same problem. > > On Sun, Oct 20, 2019 at 10:26 PM Patrick van der Velde < > petrikva...@gmail.com > wrote: > >> To answer my own question: Updating to the latest version of GIT fixes it. >> >> Thanks Mark!!! >> >> On Monday, 21 October 2019 15:34:16 UTC+13, Patrick van der Velde wrote: >>> >>> Hi >>> >>> Our setup >>> >>> Server: >>> - Jenkins 2.190.1 >>> - Ubuntu 16.04.5 >>> >>> Agent >>> - Jenkins swarm slave >>> - Windows 2016 >>> >>> Source control: >>> - GIT on TFS2018 >>> >>> When running with git-client plugin 2.8.6 we get the following error in >>> the build log >>> >>> Running as SYSTEM >>> [EnvInject] - Loading node environment variables. >>> Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm >>> role_generators team_development tool_msbuild tool_git) in workspace >>> C:\ops\jenkins\workspace\testproduct12---b4eb99a4 >>> [WS-CLEANUP] Deleting project workspace... >>> [WS-CLEANUP] Deferred wipeout is used... >>> using credential sandboxuser >>> Cloning the remote Git repository >>> Cloning repository >>> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 >>> > C:\Program Files\Git\cmd\git.exe init >>> C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 >>> Fetching upstream changes from >>> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 >>> > C:\Program Files\Git\cmd\git.exe --version # timeout=10 >>> using GIT_ASKPASS to set credentials User to access the sandbox >>> project and the repos inside it. >>> > C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- >>> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 >>> +refs/heads/*:refs/remotes/origin/* >>> ERROR: Error cloning remote repo 'origin' >>> hudson.plugins.git.GitException: Command "C:\Program >>> Files\Git\cmd\git.exe fetch --tags --progress -- >>> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 >>> +refs/heads/*:refs/remotes/origin/*" returned status code 128: >>> stdout: >>> stderr: fatal: Authentication failed for ' >>> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123/ >>> ' >>> >>> at >>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) >>> at >>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) >>> at >>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) >>> at >>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) >>> at >>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) >>> at >>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) >>> at >>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) >>> at hudson.remoting.UserRequest.perform(UserRequest.java:212) >>> at hudson.remoting.UserRequest.perform(UserRequest.java:54) >>> at hudson.remoting.Request$2.run(Request.java:369) >>> at >>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) >>> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) >>> at
Re: [Jenkins Kubernetes Plugin] Issues building plugin from source
a jenkins server is started for each of those integration tests. the port used is printed in the logs On Mon, Oct 21, 2019 at 6:03 PM 'Andrew Douglas' via Jenkins Users < jenkinsci-users@googlegroups.com> wrote: > Thanks Carlos, > > "Some integration tests run a local jenkins" is it possible that this is > not starting correctly? I can't see a copy of Jenkins running anywhere > during testing. > > I'm using minikube on hyperkit for testing > > > Andrew > > On Monday, October 21, 2019 at 11:14:11 AM UTC+1, Carlos Sanchez wrote: >> >> you would need to check the pod logs, to see what happened >> probably the pods can't connect to jenkins and you may need to set the >> hot ip in maven >> anyway if you submit a PR it will be tested in jenkins infra and will >> give you the test results >> >> If your minikube is running in a VM (e.g. on virtualbox) and the host >> running mvn does not have a public hostname for the VM to access, you >> can set the jenkins.host.address system property to the (host-only or >> NAT) IP of your host: >> >> mvn clean install -Djenkins.host.address=192.168.99.1 >> >> >> On Thu, Oct 17, 2019 at 7:22 PM 'Andrew Douglas' via Jenkins Users < >> jenkins...@googlegroups.com> wrote: >> >>> Hi, I am trying to diagnose a potential issue with this plugin and have >>> downloaded the source (from >>> https://github.com/jenkinsci/kubernetes-plugin). >>> >>> I am running Minikube and have the latest version of Maven. When I try >>> to build the plugin with the command `mvn clean install >>> -DconnectorHost=0.0.0.0` I always get at least one integration test failure >>> and then the build fails. Failures typically look like: >>> >>> ``` >>> [INFO] Running >>> org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest >>> [ERROR] Tests run: 27, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: >>> 592.425 s <<< FAILURE! - in >>> org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest >>> [ERROR] >>> cascadingDelete(org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest) >>> Time elapsed: 180.127 s <<< ERROR! >>> org.junit.runners.model.TestTimedOutException: test timed out after 180 >>> seconds >>> at java.base@12.0.1/java.lang.Thread.sleep(Native Method) >>> at >>> app//org.jvnet.hudson.test.JenkinsRule.waitForCompletion(JenkinsRule.java:1430) >>> at >>> app//org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest.cascadingDelete(KubernetesPipelineTest.java:404) >>> at >>> java.base@12.0.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native >>> Method) >>> at java.base@12.0.1 >>> /jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >>> at java.base@12.0.1 >>> /jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >>> at java.base@12.0.1 >>> /java.lang.reflect.Method.invoke(Method.java:567) >>> at >>> app//org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) >>> at >>> app//org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) >>> at >>> app//org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) >>> at >>> app//org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) >>> at >>> app//org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) >>> at >>> app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) >>> at >>> app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) >>> at >>> app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) >>> at >>> app//org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) >>> at >>> app//org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:600) >>> at >>> app//org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) >>> at >>> app//org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) >>> at java.base@12.0.1 >>> /java.util.concurrent.FutureTask.run(FutureTask.java:264) >>> at java.base@12.0.1/java.lang.Thread.run(Thread.java:835) >>> >>> [ERROR] >>> computerCantBeConfigured(org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest) >>> Time elapsed: 0.493 s <<< ERROR! >>> org.jvnet.hudson.reactor.ReactorException: java.lang.Error: >>> java.lang.reflect.InvocationTargetException >>> at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) >>> at jenkins.InitReactorRunner.run(InitReactorRunner.java:48) >>> at jenkins.model.Jenkins.executeReactor(Jenkins.java:1152) >>> at jenkins.model.Jenkins.(Jenkins.java:959) >>> at hudson.model.Hudson.(Hudson.java:85) >>> at >>>
Re: [Jenkins Kubernetes Plugin] Issues building plugin from source
Thanks Carlos, "Some integration tests run a local jenkins" is it possible that this is not starting correctly? I can't see a copy of Jenkins running anywhere during testing. I'm using minikube on hyperkit for testing Andrew On Monday, October 21, 2019 at 11:14:11 AM UTC+1, Carlos Sanchez wrote: > > you would need to check the pod logs, to see what happened > probably the pods can't connect to jenkins and you may need to set the hot > ip in maven > anyway if you submit a PR it will be tested in jenkins infra and will give > you the test results > > If your minikube is running in a VM (e.g. on virtualbox) and the host > running mvn does not have a public hostname for the VM to access, you can > set the jenkins.host.address system property to the (host-only or NAT) IP > of your host: > > mvn clean install -Djenkins.host.address=192.168.99.1 > > > On Thu, Oct 17, 2019 at 7:22 PM 'Andrew Douglas' via Jenkins Users < > jenkins...@googlegroups.com > wrote: > >> Hi, I am trying to diagnose a potential issue with this plugin and have >> downloaded the source (from >> https://github.com/jenkinsci/kubernetes-plugin). >> >> I am running Minikube and have the latest version of Maven. When I try to >> build the plugin with the command `mvn clean install >> -DconnectorHost=0.0.0.0` I always get at least one integration test failure >> and then the build fails. Failures typically look like: >> >> ``` >> [INFO] Running >> org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest >> [ERROR] Tests run: 27, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: >> 592.425 s <<< FAILURE! - in >> org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest >> [ERROR] >> cascadingDelete(org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest) >> >> Time elapsed: 180.127 s <<< ERROR! >> org.junit.runners.model.TestTimedOutException: test timed out after 180 >> seconds >> at java.base@12.0.1/java.lang.Thread.sleep(Native Method) >> at >> app//org.jvnet.hudson.test.JenkinsRule.waitForCompletion(JenkinsRule.java:1430) >> at >> app//org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest.cascadingDelete(KubernetesPipelineTest.java:404) >> at >> java.base@12.0.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native >> >> Method) >> at >> java.base@12.0.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) >> at >> java.base@12.0.1/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >> at >> java.base@12.0.1/java.lang.reflect.Method.invoke(Method.java:567) >> at >> app//org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) >> at >> app//org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) >> at >> app//org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) >> at >> app//org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) >> at >> app//org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) >> at >> app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) >> at >> app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) >> at >> app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) >> at >> app//org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) >> at >> app//org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:600) >> at >> app//org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) >> at >> app//org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) >> at >> java.base@12.0.1/java.util.concurrent.FutureTask.run(FutureTask.java:264) >> at java.base@12.0.1/java.lang.Thread.run(Thread.java:835) >> >> [ERROR] >> computerCantBeConfigured(org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest) >> >> Time elapsed: 0.493 s <<< ERROR! >> org.jvnet.hudson.reactor.ReactorException: java.lang.Error: >> java.lang.reflect.InvocationTargetException >> at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) >> at jenkins.InitReactorRunner.run(InitReactorRunner.java:48) >> at jenkins.model.Jenkins.executeReactor(Jenkins.java:1152) >> at jenkins.model.Jenkins.(Jenkins.java:959) >> at hudson.model.Hudson.(Hudson.java:85) >> at >> org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:675) >> at org.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:402) >> at >> org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:595) >> at >>
Re: declarative pipeline and gitlab
Hi, Maybe it's a "mister obvious" answer but have you set up the build trigger on the receiving pipeline? In the pipeline configuration you should have an option "Build when a change is pushed to gitlab" that you can enable and select the set of the events that would trigger the pipeline. Also from here you can confirm that the webhook you are using is correct. On Tuesday, October 15, 2019 at 10:47:12 AM UTC+2, Pa Y wrote: > > Hello, > has somebody managed successfully to use declarative pipeline and gitlab? > > I followed the instructions listed here: > https://docs.gitlab.com/ee/integration/jenkins.html and this works for > freestyle jobs. we use this already without problems. > > Now, I try to move to pipelines to have more options in general. > > So far, we get gitlab hook sent succcessfully but for this we need to > disable in Jenkins : Prevent Cross Site Request Forgery exploits , what I > don't really want... > > And anyway after hook was sent, Jenkins job can't be triggered > > can maybe somebody share a running example? > > Thanks for any help in advance! > > Pablo > > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/ec6624ca-121b-4710-9f66-4438fb32126d%40googlegroups.com.
Re: Git-client plugin version 2.8.6 breaks authentication on Windows box
Thanks. Could you open an issue on Jira https://issues.jenkins-ci.org/secure/Dashboard.jspa that describes the environment more fully? I'm running CLI git 2.7 on at least one machine (Ubuntu 16.04) and can successfully clone an https private repository from Visual Studio Online at https://markwaite.visualstudio.com/DefaultCollection/_git/elisp . I'm running CLI git 2.17 (not 2.18) on at least one other machine (Amazon Linux 2) and can successfully clone an https private repository from Visual Studio Online at https://markwaite.visualstudio.com/DefaultCollection/_git/elisp . I'd like more information about your environment to be included in that Jira issue. I need to know what version of Team Foundation Server you're running, what version of Windows, any details about the authentication techniques in use (appears to be http rather than https to your TFS server, assumed that the username and password do not contain Windows special characters like '%', etc.), what versions of CLI git were failing, what versions are now working, Thanks in advance for providing that information in case other users encounter the same problem. On Sun, Oct 20, 2019 at 10:26 PM Patrick van der Velde < petrikvanderve...@gmail.com> wrote: > To answer my own question: Updating to the latest version of GIT fixes it. > > Thanks Mark!!! > > On Monday, 21 October 2019 15:34:16 UTC+13, Patrick van der Velde wrote: >> >> Hi >> >> Our setup >> >> Server: >> - Jenkins 2.190.1 >> - Ubuntu 16.04.5 >> >> Agent >> - Jenkins swarm slave >> - Windows 2016 >> >> Source control: >> - GIT on TFS2018 >> >> When running with git-client plugin 2.8.6 we get the following error in >> the build log >> >> Running as SYSTEM >> [EnvInject] - Loading node environment variables. >> Building remotely on BUILDAGENT (tool_nuget tool_powershell swarm >> role_generators team_development tool_msbuild tool_git) in workspace >> C:\ops\jenkins\workspace\testproduct12---b4eb99a4 >> [WS-CLEANUP] Deleting project workspace... >> [WS-CLEANUP] Deferred wipeout is used... >> using credential sandboxuser >> Cloning the remote Git repository >> Cloning repository >> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 >> > C:\Program Files\Git\cmd\git.exe init >> C:\ops\jenkins\workspace\testproduct12---b4eb99a4 # timeout=10 >> Fetching upstream changes from >> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 >> > C:\Program Files\Git\cmd\git.exe --version # timeout=10 >> using GIT_ASKPASS to set credentials User to access the sandbox >> project and the repos inside it. >> > C:\Program Files\Git\cmd\git.exe fetch --tags --progress -- >> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 >> +refs/heads/*:refs/remotes/origin/* >> ERROR: Error cloning remote repo 'origin' >> hudson.plugins.git.GitException: Command "C:\Program >> Files\Git\cmd\git.exe fetch --tags --progress -- >> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123 >> +refs/heads/*:refs/remotes/origin/*" returned status code 128: >> stdout: >> stderr: fatal: Authentication failed for ' >> http://tfshostname:8080/tfs/projectcollection/sandbox/_git/testproduct123/ >> ' >> >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2172) >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1864) >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:78) >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:545) >> at >> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:758) >> at >> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153) >> at >> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146) >> at hudson.remoting.UserRequest.perform(UserRequest.java:212) >> at hudson.remoting.UserRequest.perform(UserRequest.java:54) >> at hudson.remoting.Request$2.run(Request.java:369) >> at >> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) >> at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> at >> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) >> at >> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) >> at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) >> at java.lang.Thread.run(Thread.java:748) >> Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote >> call to JNLP4-connect connection from 172.17.35.148/172.17.35.148:49717 >> at >> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743) >> at >>
Re: [Jenkins Kubernetes Plugin] Issues building plugin from source
you would need to check the pod logs, to see what happened probably the pods can't connect to jenkins and you may need to set the hot ip in maven anyway if you submit a PR it will be tested in jenkins infra and will give you the test results If your minikube is running in a VM (e.g. on virtualbox) and the host running mvn does not have a public hostname for the VM to access, you can set the jenkins.host.address system property to the (host-only or NAT) IP of your host: mvn clean install -Djenkins.host.address=192.168.99.1 On Thu, Oct 17, 2019 at 7:22 PM 'Andrew Douglas' via Jenkins Users < jenkinsci-users@googlegroups.com> wrote: > Hi, I am trying to diagnose a potential issue with this plugin and have > downloaded the source (from https://github.com/jenkinsci/kubernetes-plugin > ). > > I am running Minikube and have the latest version of Maven. When I try to > build the plugin with the command `mvn clean install > -DconnectorHost=0.0.0.0` I always get at least one integration test failure > and then the build fails. Failures typically look like: > > ``` > [INFO] Running > org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest > [ERROR] Tests run: 27, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: > 592.425 s <<< FAILURE! - in > org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest > [ERROR] > cascadingDelete(org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest) > Time elapsed: 180.127 s <<< ERROR! > org.junit.runners.model.TestTimedOutException: test timed out after 180 > seconds > at java.base@12.0.1/java.lang.Thread.sleep(Native Method) > at > app//org.jvnet.hudson.test.JenkinsRule.waitForCompletion(JenkinsRule.java:1430) > at > app//org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest.cascadingDelete(KubernetesPipelineTest.java:404) > at > java.base@12.0.1/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > at java.base@12.0.1 > /jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at java.base@12.0.1 > /jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.base@12.0.1 > /java.lang.reflect.Method.invoke(Method.java:567) > at > app//org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at > app//org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at > app//org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at > app//org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at > app//org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at > app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at > app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at > app//org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48) > at app//org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) > at > app//org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:600) > at > app//org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at > app//org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at java.base@12.0.1 > /java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base@12.0.1/java.lang.Thread.run(Thread.java:835) > > [ERROR] > computerCantBeConfigured(org.csanchez.jenkins.plugins.kubernetes.pipeline.KubernetesPipelineTest) > Time elapsed: 0.493 s <<< ERROR! > org.jvnet.hudson.reactor.ReactorException: java.lang.Error: > java.lang.reflect.InvocationTargetException > at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:282) > at jenkins.InitReactorRunner.run(InitReactorRunner.java:48) > at jenkins.model.Jenkins.executeReactor(Jenkins.java:1152) > at jenkins.model.Jenkins.(Jenkins.java:959) > at hudson.model.Hudson.(Hudson.java:85) > at > org.jvnet.hudson.test.JenkinsRule.newHudson(JenkinsRule.java:675) > at org.jvnet.hudson.test.JenkinsRule.before(JenkinsRule.java:402) > at > org.jvnet.hudson.test.JenkinsRule$1.evaluate(JenkinsRule.java:595) > at > org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298) > at > org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292) > at > java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at java.base/java.lang.Thread.run(Thread.java:835) > Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException > at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) > at >
Jenkins AWS EBS performance IOPS investigate
Hi, I have Jenkins master (v2.190.1) installed as EC2 t2.small - it worked as expected until i've updated plugins recently and restarted jenkins. Now i can see that jenkins process consumes 100% CPU and it's caused by IOwait - disk performance is a bottleneck. Jenkins started to do some heavy disk reading which caused running out for EBS burst balance - now with 150G EBS i should have around 450 IOPS and it seems not to be enough for Jenkins - but it worked just fine a week ago. When i track jenkins process with strace i see that it reads/scans every job and branch and build i have which probably is the source of the issue. How can i check which plugin caused or maybe is it desired behavior that after restart Jenkins scan all the files over and over again? -- 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 jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/5c73f937-d6c2-40af-b707-2e600708b24d%40googlegroups.com.
