Re: How to diagnose java.io.NotSerializableException: org.codehaus.groovy.control.ErrorCollector errors?

Quick finding-- these errors have generally meant some problem with my source code. One thing I note is that variables scoped at script level seem to cause this error. Wrap them in a method and the problem disappears. So use def gitPipelineUser() { 'svcx_git_user' } rather than def

Re: Release Button or best practice

We have a similar design challenge. I was thinking about creating dependent builds and then chaining them, but the more I look at it the more I am convinced that Jenkins is just an awkward fit for CD. On Monday, August 21, 2017 at 8:31:28 AM UTC-7, Steven Foster wrote: > > I do like this

Re: git tags not fetched

I'm guessing this is a regression. Created https://issues.jenkins-ci.org/browse/JENKINS-46331 -- 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

git tags not fetched

We have a GitHub organization with repos detected and built by github-branch-folder. I note the following from https://wiki.jenkins.io/display/JENKINS/Git+Plugin for "Version 3.4.0 (July 17, 2017)" > >- Because each branch job in a multibranch project will only ever >build the one

Re: Mac Jenkins Can't Clone/fetch from GitHub

Hi, I am facing this issue: Git fetch timeout - while checking out from a private repo - PFB the log: Building in workspace /Users/Shared/Jenkins/Home/workspace/iOS job > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config

Re: xcode 2.0 NPE

its https://issues.jenkins-ci.org/browse/JENKINS-46326 On Mon, Aug 21, 2017 at 2:10 PM, Richard Ginga wrote: > no wait, that is not mine. do you see one from me? > > > On Mon, Aug 21, 2017 at 1:51 PM, Richard Ginga > wrote: > >> Thanks

Re: xcode 2.0 NPE

no wait, that is not mine. do you see one from me? On Mon, Aug 21, 2017 at 1:51 PM, Richard Ginga wrote: > Thanks Arnaud. created https://issues.jenkins-ci.org/browse/JENKINS-19886 > > > On Mon, Aug 21, 2017 at 1:02 PM, Arnaud Héritier > wrote: >

Re: xcode 2.0 NPE

Thanks Arnaud. created https://issues.jenkins-ci.org/browse/JENKINS-19886 On Mon, Aug 21, 2017 at 1:02 PM, Arnaud Héritier wrote: > Could you report an issue in Jira > > https://github.com/jenkinsci/xcode-plugin/blob/xcode- >

Re: xcode 2.0 NPE

Could you report an issue in Jira https://github.com/jenkinsci/xcode-plugin/blob/xcode-plugin-2.0.0/src/main/java/au/com/rayh/XCodeBuilder.java#L713 Seems to be related to the plist when packaging the IPA... It's probably due to a configuration change. In the issue please describe which

xcode 2.0 NPE

I am testing ios builds on xcode 2.0 after upgrading from 1.4.11. the build worked under 1.4.11 but I get an NPE in FilePath.mkdirs as below. I don't know what to make of this error (jenkins 2.7.1) *10:05:40* ** ARCHIVE SUCCEEDED ***10:05:40* *10:05:40* Cleaning up previously generated .ipa

Re: Release Button or best practice

I do like this solution and it seems really flexible but unfortunately it has one big problem for us. The build is not technically *done* until this input step is answered. Sometimes we will want to release over a week later. We release at any time really. If we timeout then we can't answer

Re: Advices & help needed : Github + Jenkins + Docker, permission denied

Up, please some one? Le jeudi 17 août 2017 13:06:16 UTC+2, Sowlène a écrit : > > Hi there, > I'm a young student trying to do something a little bit complicated to me > :) > > I've got a repo on github with my Dockerfile in. with many config file > too, as an Entrypoint.sh who initialize some

Re: Release Button or best practice

Actually we are using a input step without a timeout fixed to one day (in order to deploy the version which was deployed during the last night on pre-prodcution server). If you catch the timeout exception without any error, This tricks do the job. Le mercredi 16 août 2017 à 02:22 -0700, Steven

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

Hi Mark, suffixing 0 to Exit has worked amazingly my issue has resolved. You deserve round of applaud. Many thanks Suhas India On Friday, April 17, 2015 at 1:51:03 AM UTC+5:30, Mark Waite wrote: > > I'm surprised if a process leaking a file descriptor would cause a build > step to fail. I've

Re: How to resolve "Process leaked file descriptor" issue which caused job failure in Jenkins

Hi Mark, Just referred your comments and I have 0 to Exit as you shows below, and to my surprise jenkins error has disappeared, thanks a lot On Friday, April 17, 2015 at 1:51:03 AM UTC+5:30, Mark Waite wrote: > > I'm surprised if a process leaking a file descriptor would cause a build > step