Re: Failed build.

Thanks - I submitted another change and it seems to be back to normal. > On 25 Oct 2018, at 13:41, Jesse Glick wrote: > > On Thu, Oct 25, 2018 at 4:57 AM pallen wrote: >> Possibly one for infrastructure, but I can't post to that group. > > You can always file a ticket in the `INFRA` project.

Re: Failed build.

On Thu, Oct 25, 2018 at 4:57 AM pallen wrote: > Possibly one for infrastructure, but I can't post to that group. You can always file a ticket in the `INFRA` project. > https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/285/ > > Please can you re-run the build and check the slaves - it

Failed build.

Hi Guys, Possibly one for infrastructure, but I can't post to that group. https://ci.jenkins.io/job/Plugins/job/p4-plugin/job/master/285/ Please can you re-run the build and check the slaves - it looks like some sort of remoting issue. Thank you. Kind regards, Paul -- You received this

Re: [plugin dev][Cloudbees build service] failed build due to usage of msbuild in pom in Jenkinsci repo

On Tue, Jul 19, 2016 at 8:18 AM, wrote: > I guess the issue is due to Jenkins node based on Linux while the pom > requires windows path for .Net framework files. > > What's the best solution for cases such as this? Sorry, I do not think we currently support plugin builds which

Re: [plugin dev][Cloudbees build service] failed build due to usage of msbuild in pom in Jenkinsci repo

I believe the cloudbees Jenkins stuff doesn't allow changes from anyone outside the infra team. On Thu, Jul 21, 2016 at 1:25 AM wrote: > does anyone has an idea how to change the build template that is used? or > how to customize our pom to support it? > > > On Tuesday, July

Re: [plugin dev][Cloudbees build service] failed build due to usage of msbuild in pom in Jenkinsci repo

does anyone has an idea how to change the build template that is used? or how to customize our pom to support it? On Tuesday, July 19, 2016 at 3:18:01 PM UTC+3, fkp...@gmail.com wrote: > > Hi, > i've noticed that the regular Jenkins build of our plugin on the cloudbees > service for Jenkins CI

Re: failed build 1.526 on macos

I reported this weeks ago, it's a simple thing to fix and has already been fixed in later releases. The root cause is that the license for a package that the POM pulls in has changed, and it has changed from 'nothing' to 'CDDL'. The plugin is attempting to change the license *to* CDDL, and

Re: failed build 1.526 on macos

Not necessary. :-) I will test using a newer release. Thanks for the info! Cheers, Corey -- *Corey O'Connor* Software Engineer, Test Automation | co...@ooyala.com | (310) 980-7111 www.ooyala.com | blog http://www.ooyala.com/blog | @ooyalahttp://www.twitter.com/ooyala On Fri, Sep 13, 2013 at

failed build 1.526 on macos

Tried to build sources from tag 1.526: [ERROR] Failed to execute goal com.cloudbees:maven-license-plugin:1.7:process (default) on project maven-plugin: Execution default of goal com.cloudbees:maven-license-plugin:1.7:process failed: java.lang.IllegalStateException: Expecting [] but found