pzygielo commented on pull request #97: URL: https://github.com/apache/maven-invoker-plugin/pull/97#issuecomment-1029955153
Just out of curiosity of the failures on cloudbees - as I don't know where the jenkins pipeline source is stored and if it's publicly available at all. (If it is I'd be happy to learn its location.) The master - green one: ``` $ curl --silent https://ci-maven.apache.org/blue/rest/organizations/jenkins/pipelines/Maven/pipelines/maven-github/pipelines/maven-invoker-plugin/branches/master/runs/1/log/?start=0 | grep -a "Fetching upstream" Fetching upstream changes from https://gitbox.apache.org/repos/asf/maven-jenkins-env.git Fetching upstream changes from https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git Fetching upstream changes from https://github.com/apache/maven-invoker-plugin.git [...] Fetching upstream changes from https://github.com/apache/maven-invoker-plugin.git ``` while the failing build for this PR: ``` $ curl --silent https://ci-maven.apache.org/blue/rest/organizations/jenkins/pipelines/Maven/pipelines/maven-github/pipelines/maven-invoker-plugin/branches/PR-97/runs/1/log/?start=0 | grep -a "Fetching upstream" Fetching upstream changes from https://gitbox.apache.org/repos/asf/maven-jenkins-env.git Fetching upstream changes from https://gitbox.apache.org/repos/asf/maven-jenkins-lib.git ``` So it seems that checkout of the project was not successful, however the build (next step I presume) was started regardless? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
