date:20170821

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

2017-08-21 Thread Nick Mellor

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 gitPipelineUser = 'svc_git_user' 

This is probably not the only reason you might get this error, but it's one 
possible thing to check.

Cheers,

Nick

On Friday, 7 October 2016 09:37:29 UTC+11, John Hovell wrote:
>
> Quick question how to diagnose non-serializable errors, or how to avoid 
> the issue entirely in my case.
>
> I thought I could add a @NonCPS annotation 
>  to my 
> method to bypass/disable serialization but adding the annotation does not 
> seem to make any difference in the error I receive. 
>
> Jenkins is 2.7.4 with latest plugins as of a few days ago.
>
> Am I using NonCPS incorrectly or is there a way to translate the below 
> code-snippet to something that is serializable (seems unnecessary in my 
> case but perhaps this is the only option for global libraries?)
>
> (Relatedly, would it be simpler to use a bash script to perform the below 
> logic? Is there some parallel/analog for global pipeline libraries for 
> bash? I saw there is support for resources but not files that can be 
> executed)
>
> java.io.NotSerializableException: org.codehaus.groovy.control.ErrorCollector
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967)
>   at 
> org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854)
>   at 
>

Re: Release Button or best practice

2017-08-21 Thread ahammond

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 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 
> the input step, but if we don't timeout then the build does not finish. It 
> would be lovely if we could specify an input step between two different 
> jobs, or split it in some way so we can have builds completing and later 
> decide to continue some builds to the deploy stage.
>
> On Monday, August 21, 2017 at 10:54:46 AM UTC+1, Ludovic SMADJA wrote:
>>
>> 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.
>>
>> -- 
>>
>> Ludovic SMADJA
>> R engineer - build process and development JALIOS SA 
>> http://www.jalios.com
>>
>>

-- 
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/1ef94f3a-67cb-43f9-b4bf-24b97aefd742%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: git tags not fetched

2017-08-21 Thread ahammond

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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/80253b10-0ea1-4922-a07c-2e49dddfab8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

git tags not fetched

2017-08-21 Thread ahammond

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 specific branch, the default behaviour for a Git Branch 
>Source is now to use a minimal refspec corresponding to just the required 
>branch. Tags will not be checked out by default. If you have a multibranch 
>project that requires the full set of ref-specs (for example, you might 
>have a pipeline that will use some analysis tool on the diff with some 
>other branch) you can restore the previous behaviour by adding the 
>"Advanced Clone Behaviours". Note: In some cases you may also need to add 
>the "Specify ref specs" behaviour.
>
> I click into my_organization->Configure->Projects under GitHub 
Organization and enable "Advanced clone behaviors". Instead of an option to 
_enable_ fetching of tags, there is "Do not fetch tags". It is not enabled, 
however My builds still do not fetch tags. I tried enabling it in the hopes 
that it was just a developer forgetting to update the description, but no 
luck:

Running on jenkins-agent-8GB-0c2185cb-8ff2-402c-8e9e-3e49df68e557 in 
/jenkins/workspace/rfree_docker-jenkins_master-76M6OWBGMGMW63CGIV6UX7DGQI3CXBAL6A5BM6Z7HKBA3SXZTZBQ[Pipeline]
 {[Pipeline] stage[Pipeline] { (Declarative: Checkout SCM)[Pipeline] checkout > 
git rev-parse --is-inside-work-tree # timeout=10
> Fetching changes from the remote Git repository
>  > git config remote.origin.url 
> https://github.com/anchorfree/docker-jenkins.git # timeout=10
> Fetching without tags
> Fetching upstream changes from 
> https://github.com/anchorfree/docker-jenkins.git
>  > git --version # timeout=10
> using GIT_ASKPASS to set credentials Jenkins Global Pipeline Libraries scan 
> credentials
>  > git fetch *--no-tags* --progress 
> https://github.com/anchorfree/docker-jenkins.git 
> +refs/heads/master:refs/remotes/origin/master
> Checking out Revision 41cfac69a0c19ef98ff70ff1bba0e571c81bd5c2 (master)
> Commit message: "upgrade to official Jenkins 2.60.3"
>
>
How do I get Jenkins to fetch tags?

A 

-- 
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/1ea00927-5f86-4baa-bed1-c63d14645d6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-08-21 Thread Ashwin Ganesh

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 remote.origin.url https://github.com/myRepo 
 # timeout=10

Fetching upstream changes from https://github.com/myRepo 


 > git --version # timeout=10

using GIT_ASKPASS to set credentials 

 > git fetch --tags --progress https://github.com/myRepo 
 
+refs/heads/*:refs/remotes/origin/*

ERROR: Timeout after 10 minutes

ERROR: Error fetching remote repo 'origin'

hudson.plugins.git.GitException: Failed to fetch from 
https://github.com/myRepo 

at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:817)

at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1084)

at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1115)

at hudson.scm.SCM.checkout(SCM.java:495)

at hudson.model.AbstractProject.checkout(AbstractProject.java:1212)

at 
hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:566)

at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86)

at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:491)

at hudson.model.Run.execute(Run.java:1739)

at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)

at hudson.model.ResourceController.execute(ResourceController.java:97)

at hudson.model.Executor.run(Executor.java:419)

Caused by: hudson.plugins.git.GitException: Command "git fetch --tags 
--progress https://github.com/myRepo 
 
+refs/heads/*:refs/remotes/origin/*" returned status code 143:




On Monday, 5 June 2017 14:52:53 UTC-4, Mark Waite wrote:
>
> From the "Global Tool Configuration" page of "Manage Jenkins", configure a 
> Maven installer that downloads the maven version you need from the apache 
> distribution locations.  Jenkins will then install that tool for you 
> automatically when you define the job to require that version of maven.
>
> Mark Waite
>
> On Mon, Jun 5, 2017 at 11:48 AM Techos  > wrote:
>
>> Hello, 
>>
>> Thanks for your help, I have the same problem and it's ok now. 
>>
>> but, I have a new problem *Cannot run program "mvn" (in directory 
>> "/Users/xxx/.jenkins/jobs/myproject/workspace*
>>
>> Do someone has any idea? 
>>
>> Thanks.
>>
>>
>> Le mercredi 24 mai 2017 05:00:20 UTC+2, Shuguo Yang a écrit :
>>>
>>> Hey, this is because Jenkins is running as the user jenkins, which is 
>>> not the current user on your mac. 
>>>
>>> The default path is "/User/Share/Jenkins", install it under 
>>> "$HOME/.jenkins" to make it work. 
>>> So:
>>>
>>>
>>> 1. Stop the current Jenkin on your mac.
>>>
>>> *sudo launchctl unload /Library/LaunchDaemons/org.jenkins-ci.plist*
>>> The, double check you can't access "localhost:8080" 
>>>
>>> 2.  Double click the "jenkins.war" file under "Application/jenkins". You 
>>> will found jenkins
>>> was reinstalled to "$HOME/.jenkins" again. 
>>>
>>> 3. Then re-config the job, git should works well
>>>
>>> I also encounter this issue, and above steps works well for me.
>>>
>>> On Monday, September 19, 2016 at 3:35:05 PM UTC+8, Ankit Arora wrote:

 Hi,

 I am also getting Error while Connecting Jenkins from Github.

 *Error : Failed to connect to repository : Error performing command: 
 git.exe ls-remote -h*

 Please suggest the solution

 *//BR*


 *Ankit AroraTest Engineer  *
 *✉ : **ankitarora...@gmail.com || ankitarora...@gmail.com*
 *☎ :* 
 *+91-9654293205 ,+91-8285678798 *


 *P please consider the environment before printing any emailPlease 
 say "No" to Plastics *


  


 On Sat, Sep 17, 2016 at 4:06 AM, Hung  wrote:

> HI,  I am new to setting up Jenkins.  I am trying to setup a Jenkins 
> server
> on a Mac Mini.  I am having trouble with the Jenkins setup because I 
> made a
> simple project that is to sync to a github repo and then run a script.
> Unfortunately I can't get this simple project to run correctly.  I keep
> getting a timeout error.  Here is a Console output.
>
>  15:16:57 Building in workspace
> /Users/Shared/Jenkins/Home/workspace/MacWitchesServers
> 15:16:57  > /usr/bin/git rev-parse --is-inside-work-tree # timeout=10
> 15:16:57 Fetching changes from the remote Git repository
> 15:16:57  > /usr/bin/git config remote.origin.url
> https://github.com/MyAccount/sample # timeout=10
> 15:16:57 Fetching upstream changes from 
> https://github.com/MyAccount/sample
> 15:16:57  > /usr/bin/git --version # timeout=10
> 15:16:57 using

Re: xcode 2.0 NPE

2017-08-21 Thread Richard Ginga

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 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-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 settings you defined in your build
>>>
>>> On Mon, Aug 21, 2017 at 6:13 PM, Richard Ginga >> > wrote:
>>>
 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 files*10:05:40* Cleaning up previously generated 
 .dSYM.zip files*10:05:40* Packaging IPA*10:05:40* ERROR: Build step failed 
 with exception*10:05:40* java.lang.NullPointerException 
 *10:05:40*
  at hudson.FilePath.mkdirs(FilePath.java:2944) 
 *10:05:40*
at hudson.FilePath.access$800(FilePath.java:195) 
 *10:05:40*
 at hudson.FilePath$37.invoke(FilePath.java:1932) 
 *10:05:40*
  at hudson.FilePath$37.invoke(FilePath.java:1929) 
 *10:05:40*
  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772) 
 *10:05:40*
at hudson.remoting.UserRequest.perform(UserRequest.java:153) 
 *10:05:40*
at hudson.remoting.UserRequest.perform(UserRequest.java:50) 
 *10:05:40*
 at hudson.remoting.Request$2.run(Request.java:332) 
 *10:05:40*
at 
 hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
  
 *10:05:40*
   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
 *10:05:40*
 at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
  
 *10:05:40*
at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
  
 *10:05:40*
   at java.lang.Thread.run(Thread.java:748) 
 *10:05:40*
   at ..remote call to stt-osx-vm2-test(Native Method)*10:05:40*   
 at 
 hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)*10:05:40*
 at 
 hudson.remoting.UserResponse.retrieve(UserRequest.java:253)*10:05:40*  
   at hudson.remoting.Channel.call(Channel.java:781)*10:05:40* at 
 hudson.FilePath.act(FilePath.java:1007)*10:05:40*at 
 hudson.FilePath.act(FilePath.java:996)*10:05:40* at 
 hudson.FilePath.write(FilePath.java:1929)*10:05:40*  at 
 au.com.rayh.XCodeBuilder._perform(XCodeBuilder.java:713)*10:05:40*   at 
 au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:287)*10:05:40*at 
 hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)*10:05:40*
   at 
 hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)*10:05:40*
   at hudson.model.Build$BuildExecution.build(Build.java:205)*10:05:40*
 at hudson.model.Build$BuildExecution.doRun(Build.java:162)*10:05:40*at 
 hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)*10:05:40*

Re: xcode 2.0 NPE

2017-08-21 Thread Richard Ginga

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:
>
>> 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 settings you defined in your build
>>
>> On Mon, Aug 21, 2017 at 6:13 PM, Richard Ginga 
>> wrote:
>>
>>> 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 files*10:05:40* Cleaning up previously generated 
>>> .dSYM.zip files*10:05:40* Packaging IPA*10:05:40* ERROR: Build step failed 
>>> with exception*10:05:40* java.lang.NullPointerException 
>>> *10:05:40*
>>>   at hudson.FilePath.mkdirs(FilePath.java:2944) 
>>> *10:05:40*
>>>at hudson.FilePath.access$800(FilePath.java:195) 
>>> *10:05:40*
>>> at hudson.FilePath$37.invoke(FilePath.java:1932) 
>>> *10:05:40*
>>>  at hudson.FilePath$37.invoke(FilePath.java:1929) 
>>> *10:05:40*
>>>  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772) 
>>> *10:05:40*
>>>at hudson.remoting.UserRequest.perform(UserRequest.java:153) 
>>> *10:05:40*
>>>at hudson.remoting.UserRequest.perform(UserRequest.java:50) 
>>> *10:05:40*
>>> at hudson.remoting.Request$2.run(Request.java:332) 
>>> *10:05:40*
>>>at 
>>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
>>>  
>>> *10:05:40*
>>>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
>>> *10:05:40*
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>>  
>>> *10:05:40*
>>>at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>>  
>>> *10:05:40*
>>>   at java.lang.Thread.run(Thread.java:748) 
>>> *10:05:40*
>>>   at ..remote call to stt-osx-vm2-test(Native Method)*10:05:40*   
>>> at 
>>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)*10:05:40*
>>> at 
>>> hudson.remoting.UserResponse.retrieve(UserRequest.java:253)*10:05:40*   
>>>  at hudson.remoting.Channel.call(Channel.java:781)*10:05:40* at 
>>> hudson.FilePath.act(FilePath.java:1007)*10:05:40*at 
>>> hudson.FilePath.act(FilePath.java:996)*10:05:40* at 
>>> hudson.FilePath.write(FilePath.java:1929)*10:05:40*  at 
>>> au.com.rayh.XCodeBuilder._perform(XCodeBuilder.java:713)*10:05:40*   at 
>>> au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:287)*10:05:40*at 
>>> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)*10:05:40* 
>>>  at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)*10:05:40*
>>>   at hudson.model.Build$BuildExecution.build(Build.java:205)*10:05:40*
>>> at hudson.model.Build$BuildExecution.doRun(Build.java:162)*10:05:40*at 
>>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)*10:05:40*
>>>   at hudson.model.Run.execute(Run.java:1741)*10:05:40*at 
>>> hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:05:40*at 
>>> hudson.model.ResourceController.execute(ResourceController.java:98)*10:05:40*
>>>

Re: xcode 2.0 NPE

2017-08-21 Thread Richard Ginga

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-
> 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 settings you defined in your build
>
> On Mon, Aug 21, 2017 at 6:13 PM, Richard Ginga 
> wrote:
>
>> 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 files*10:05:40* Cleaning up previously generated 
>> .dSYM.zip files*10:05:40* Packaging IPA*10:05:40* ERROR: Build step failed 
>> with exception*10:05:40* java.lang.NullPointerException 
>> *10:05:40*
>>at hudson.FilePath.mkdirs(FilePath.java:2944) 
>> *10:05:40*
>>at hudson.FilePath.access$800(FilePath.java:195) 
>> *10:05:40*
>> at hudson.FilePath$37.invoke(FilePath.java:1932) 
>> *10:05:40*
>>  at hudson.FilePath$37.invoke(FilePath.java:1929) 
>> *10:05:40*
>>  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772) 
>> *10:05:40*
>>at hudson.remoting.UserRequest.perform(UserRequest.java:153) 
>> *10:05:40*
>>at hudson.remoting.UserRequest.perform(UserRequest.java:50) 
>> *10:05:40*
>> at hudson.remoting.Request$2.run(Request.java:332) 
>> *10:05:40*
>>at 
>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
>>  
>> *10:05:40*
>>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
>> *10:05:40*
>> at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>  
>> *10:05:40*
>>at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>>  
>> *10:05:40*
>>   at java.lang.Thread.run(Thread.java:748) 
>> *10:05:40*
>>   at ..remote call to stt-osx-vm2-test(Native Method)*10:05:40*   at 
>> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)*10:05:40*
>> at 
>> hudson.remoting.UserResponse.retrieve(UserRequest.java:253)*10:05:40*
>> at hudson.remoting.Channel.call(Channel.java:781)*10:05:40* at 
>> hudson.FilePath.act(FilePath.java:1007)*10:05:40*at 
>> hudson.FilePath.act(FilePath.java:996)*10:05:40* at 
>> hudson.FilePath.write(FilePath.java:1929)*10:05:40*  at 
>> au.com.rayh.XCodeBuilder._perform(XCodeBuilder.java:713)*10:05:40*   at 
>> au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:287)*10:05:40*at 
>> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)*10:05:40*  
>> at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)*10:05:40*
>>   at hudson.model.Build$BuildExecution.build(Build.java:205)*10:05:40*at 
>> hudson.model.Build$BuildExecution.doRun(Build.java:162)*10:05:40*at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)*10:05:40*
>>   at hudson.model.Run.execute(Run.java:1741)*10:05:40*at 
>> hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:05:40*at 
>> hudson.model.ResourceController.execute(ResourceController.java:98)*10:05:40*
>> at hudson.model.Executor.run(Executor.java:410)*10:05:40* Build step 
>> 'Xcode' marked build as failure
>>
>>
>> --
>> Dick Ginga
>> Build Engineer
>> rgi...@disruptorbeam.com
>>
>> --
>> You received this

Re: xcode 2.0 NPE

2017-08-21 Thread Arnaud Héritier

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 settings you defined in your build

On Mon, Aug 21, 2017 at 6:13 PM, Richard Ginga 
wrote:

> 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 files*10:05:40* Cleaning up previously generated 
> .dSYM.zip files*10:05:40* Packaging IPA*10:05:40* ERROR: Build step failed 
> with exception*10:05:40* java.lang.NullPointerException 
> *10:05:40*
> at hudson.FilePath.mkdirs(FilePath.java:2944) 
> *10:05:40*
>at hudson.FilePath.access$800(FilePath.java:195) 
> *10:05:40*
> at hudson.FilePath$37.invoke(FilePath.java:1932) 
> *10:05:40*
>  at hudson.FilePath$37.invoke(FilePath.java:1929) 
> *10:05:40*
>  at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772) 
> *10:05:40*
>at hudson.remoting.UserRequest.perform(UserRequest.java:153) 
> *10:05:40*
>at hudson.remoting.UserRequest.perform(UserRequest.java:50) 
> *10:05:40*
> at hudson.remoting.Request$2.run(Request.java:332) 
> *10:05:40*
>at 
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
>  
> *10:05:40*
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266) 
> *10:05:40*
> at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>  
> *10:05:40*
>at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
>  
> *10:05:40*
>   at java.lang.Thread.run(Thread.java:748) 
> *10:05:40*
>   at ..remote call to stt-osx-vm2-test(Native Method)*10:05:40*   at 
> hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)*10:05:40* 
>at 
> hudson.remoting.UserResponse.retrieve(UserRequest.java:253)*10:05:40*
> at hudson.remoting.Channel.call(Channel.java:781)*10:05:40* at 
> hudson.FilePath.act(FilePath.java:1007)*10:05:40*at 
> hudson.FilePath.act(FilePath.java:996)*10:05:40* at 
> hudson.FilePath.write(FilePath.java:1929)*10:05:40*  at 
> au.com.rayh.XCodeBuilder._perform(XCodeBuilder.java:713)*10:05:40*   at 
> au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:287)*10:05:40*at 
> hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)*10:05:40*  
> at 
> hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)*10:05:40*
>   at hudson.model.Build$BuildExecution.build(Build.java:205)*10:05:40*at 
> hudson.model.Build$BuildExecution.doRun(Build.java:162)*10:05:40*at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)*10:05:40*
>   at hudson.model.Run.execute(Run.java:1741)*10:05:40*at 
> hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:05:40*at 
> hudson.model.ResourceController.execute(ResourceController.java:98)*10:05:40* 
>at hudson.model.Executor.run(Executor.java:410)*10:05:40* Build step 
> 'Xcode' marked build as failure
>
>
> --
> Dick Ginga
> Build Engineer
> rgi...@disruptorbeam.com
>
> --
> 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

xcode 2.0 NPE

2017-08-21 Thread Richard Ginga

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 files*10:05:40* Cleaning up previously
generated .dSYM.zip files*10:05:40* Packaging IPA*10:05:40* ERROR:
Build step failed with exception*10:05:40*
java.lang.NullPointerException
*10:05:40*
at hudson.FilePath.mkdirs(FilePath.java:2944)
*10:05:40*
at hudson.FilePath.access$800(FilePath.java:195)
*10:05:40*
at hudson.FilePath$37.invoke(FilePath.java:1932)
*10:05:40*
at hudson.FilePath$37.invoke(FilePath.java:1929)
*10:05:40*
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2772)
*10:05:40*
at hudson.remoting.UserRequest.perform(UserRequest.java:153)
*10:05:40*
at hudson.remoting.UserRequest.perform(UserRequest.java:50)
*10:05:40*
at hudson.remoting.Request$2.run(Request.java:332)
*10:05:40*
at 
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68)
*10:05:40*
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
*10:05:40*
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
*10:05:40*
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
*10:05:40*
at java.lang.Thread.run(Thread.java:748)
*10:05:40*
at ..remote call to stt-osx-vm2-test(Native Method)*10:05:40*   
at
hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1416)*10:05:40*
at hudson.remoting.UserResponse.retrieve(UserRequest.java:253)*10:05:40*
at hudson.remoting.Channel.call(Channel.java:781)*10:05:40* at
hudson.FilePath.act(FilePath.java:1007)*10:05:40*   at
hudson.FilePath.act(FilePath.java:996)*10:05:40*at
hudson.FilePath.write(FilePath.java:1929)*10:05:40* at
au.com.rayh.XCodeBuilder._perform(XCodeBuilder.java:713)*10:05:40*  at
au.com.rayh.XCodeBuilder.perform(XCodeBuilder.java:287)*10:05:40*   at
hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)*10:05:40*
at 
hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)*10:05:40*
at hudson.model.Build$BuildExecution.build(Build.java:205)*10:05:40*
at hudson.model.Build$BuildExecution.doRun(Build.java:162)*10:05:40*
at 
hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)*10:05:40*
at hudson.model.Run.execute(Run.java:1741)*10:05:40*at
hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)*10:05:40*   at
hudson.model.ResourceController.execute(ResourceController.java:98)*10:05:40*
at hudson.model.Executor.run(Executor.java:410)*10:05:40* Build step
'Xcode' marked build as failure


-- 
Dick Ginga
Build Engineer
rgi...@disruptorbeam.com

-- 
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/CAL3PpaVwxqy3%3D0T_NMU0dOtZt%2Bq5AUQDbum5HeX_B4fJqD%3Dv2Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Release Button or best practice

2017-08-21 Thread Steven Foster

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 
the input step, but if we don't timeout then the build does not finish. It 
would be lovely if we could specify an input step between two different 
jobs, or split it in some way so we can have builds completing and later 
decide to continue some builds to the deploy stage.

On Monday, August 21, 2017 at 10:54:46 AM UTC+1, Ludovic SMADJA wrote:
>
> 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.
>
> -- 
>
> Ludovic SMADJA
> R engineer - build process and development JALIOS SA 
> http://www.jalios.com
>
>

-- 
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/93818a64-f2c0-4c76-9ba7-ffe71ce08c63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-08-21 Thread Sowlène

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 things when i run Docker 
> Container with my docker image.
>
> I would like to connect my github repo with Jenkins (something i think i 
> successed) and i want to use Docker directly into Jenkins.
>
> In fact We have :
>
> My Github Repo with my Dockerfile manage by Jenkins2 (& 
> pipelines/BlueOcean) => Jenkins Build my Docker Image with my Dockerfile on 
> Github
> ( docker build -t solene/installtv2 . )
>
> At this step, I just want to use Jenkins to Run docker container to test 
> applications dev by my coworkers.
>
> But each time I try to run Docker container this error appear : 
>
> docker run -e DATABASE_TYPE=mysql -e DATABASE_USER=tracimuser -e 
> DATABASE_PASSWORD=tracimpassword -e DATABASE_HOST=192.168.1.73 -e 
> DATABASE_NAME=tracimdb solene/installtv2
>
> container_linux.go:262: starting container process caused "exec: 
> \"/tracim/entrypoint.sh\": permission denied"
>
> docker: Error response from daemon: oci runtime error: 
> container_linux.go:262: starting container process caused "exec: 
> \"/tracim/entrypoint.sh\": permission denied".
>
> time="2017-08-17T11:21:12+02:00" level=error msg="error waiting for 
> container: context canceled" 
>
> script returned exit code 126
>
>
> I don't understand why :/ When I try it localy it works :/ 
> Do you have some advices ?
> Is it better to use master/slave configuration in this case ? (thing i 
> don't know how to use, and i don't really understand)
>
> Thank's for your help ! :)
>
>

-- 
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/ae40c79b-51e7-4a0b-a792-9ba256603a4a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Release Button or best practice

2017-08-21 Thread Ludovic SMADJA

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 Foster a écrit :
> On Tuesday, August 15, 2017 at 6:09:04 PM UTC+1, Simon Richter wrote:
> > You are looking for the "Promoted Builds" plugin.
> > 
> > 
> > 
> 
> Ah, I did come across this but unfortunately we are using pipeline builds and 
> it seems this isn't compatible 
> 
> 
> 
> 
> -- 
> 
> 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+unsubscribe@googleg
> roups.com.
> 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/4e285cf7-ba96-40a7-bcd2-d18
> 3cd72e472%40googlegroups.com.
> 
> For more options, visit https://groups.google.com/d/optout.
> 
-- 
Ludovic SMADJAR engineer - build process and development
JALIOS SA
http://www.jalios.com

-- 
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/1503309267.8119.5.camel%40jalios.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-08-21 Thread Suhas

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 never seen it fail in any of the cases where it was 
> reported on my jobs.
>
> You may want to confirm that the build step did not fail, independent of 
> whether or not there was a leaked file descriptor.  If you're building on 
> Unix, be sure that the build step reports success (exit 0 from a shell 
> script, etc.).
>
> Mark Waite
>
> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei  > wrote:
>
>> if it is hard to get rid of "Process leaked file descriptors",  is there 
>> anyway I can make Jenkins ignore this failure step (or don't fail it),  so 
>> I can move on next step.  
>> I am looking at Conditional buildstep plugin,  but not able to figure out 
>> how this plugin work and whether it is the right plugin to achieve above 
>> goal? 
>>
>> Please help.
>> Thanks
>> Victoria 
>>
>> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>>>
>>> I need to invoke two window processes in order to start our test after 
>>> Jenkins build is down. They were normally killed after being brought up, 
>>> and I receive "Process leaked file descriptors". I found someone suggest to 
>>> do "set BUILD_ID=dontKillMe " before calling my command to start processes.
>>> Good news is that the processes are able to stay. Bad news is "Process 
>>> leaked file descriptors" still occur and mark Jenkins job failed, hence, I 
>>> can't execute any test steps afterwards
>>>
>>> Any input will be highly appreciated.
>>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/69c8b4e3-e36a-4f45-a1b3-5f85569e03f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

2017-08-21 Thread Suhas

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 to fail.  I've never seen it fail in any of the cases where it was 
> reported on my jobs.
>
> You may want to confirm that the build step did not fail, independent of 
> whether or not there was a leaked file descriptor.  If you're building on 
> Unix, be sure that the build step reports success (exit 0 from a shell 
> script, etc.).
>
> Mark Waite
>
> On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei  > wrote:
>
>> if it is hard to get rid of "Process leaked file descriptors",  is there 
>> anyway I can make Jenkins ignore this failure step (or don't fail it),  so 
>> I can move on next step.  
>> I am looking at Conditional buildstep plugin,  but not able to figure out 
>> how this plugin work and whether it is the right plugin to achieve above 
>> goal? 
>>
>> Please help.
>> Thanks
>> Victoria 
>>
>> On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote:
>>>
>>> I need to invoke two window processes in order to start our test after 
>>> Jenkins build is down. They were normally killed after being brought up, 
>>> and I receive "Process leaked file descriptors". I found someone suggest to 
>>> do "set BUILD_ID=dontKillMe " before calling my command to start processes.
>>> Good news is that the processes are able to stay. Bad news is "Process 
>>> leaked file descriptors" still occur and mark Jenkins job failed, hence, I 
>>> can't execute any test steps afterwards
>>>
>>> Any input will be highly appreciated.
>>>
>> -- 
>> 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-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/62dee9f9-1119-4938-bd8e-502e71032633%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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

Re: Release Button or best practice

Re: git tags not fetched

git tags not fetched

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

Re: xcode 2.0 NPE

Re: xcode 2.0 NPE

Re: xcode 2.0 NPE

Re: xcode 2.0 NPE

xcode 2.0 NPE

Re: Release Button or best practice

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

Re: Release Button or best practice

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

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

15 matches

Site Navigation

Mail list logo

Footer information