Jenkins 2.0 Piplines with GitHub Organization Folder Plugin and API rate_limit issues

2016-08-12 Thread Jesse Glick
Probably the plugin needs to be optimized to make fewer requests. I do not believe it has been carefully analyzed in this regard. Ideally GitHub would make your limit proportional to the size of the organization. -- You received this message because you are subscribed to the Google Groups "Jen

How can I get Jenkins on Linux to do builds on Windows machines without Active Directory?

2016-08-12 Thread Kiran
I want Jenkins on Linux to do builds on Windows servers. Naturally the authentication must be secure as it is in a production environment. The Windows servers are not part of any domain. I thought I'd try to configure Windows credentials to be saved in Jenkins. These credentials are those t

Re: New Pipeline Maven plugin

2016-08-12 Thread Will Currie
Nice. It seems to non-pipeline/'old-school'/regular jenkins maven build has support for tracking fingerprints of artefacts used and produced by any given maven build. I'm taking about the work that seems to be done by MavenFingerprinter

RE: Slaves on Old OS's

2016-08-12 Thread Jason Pyeron
> -Original Message- > From: Simona Avornicesei > Sent: Friday, August 12, 2016 10:50 > To: Jenkins Users > Subject: Re: Slaves on Old OS's > > What is the reason for keeping/using such old machines? We are building / testing software on Windows NT 4 and Windows 2000 Here is the java ver

Re: [Git-Plugin] notifyCommit not matching local (windows) repository

2016-08-12 Thread Mark Waite
The message "No Git consumers using SCM API plugin for: /D/Repositories/Project" is usually not an indication that notifyCommit was completely ignored. There are two messages which are reported if a notifyCommit is called and no Jenkins job is polling that URL: $ notify=http://localhost:8080/git/

Re: [Git-Plugin] notifyCommit not matching local (windows) repository

2016-08-12 Thread John Thornborrow
We just have the one windows box that hosts all of our stuff so jenkins and the git repo are on the same box. No slaves/remote agents. Project builds fine if we use trigger build API, manually build, or actually poll git. Literally the only problem we are stuck with is notifyCommit not recognising

Re: [Git-Plugin] notifyCommit not matching local (windows) repository

2016-08-12 Thread Mark Waite
If you're using command line git, you might try /D/Repositories/Project. That syntax may work on the same machine which hosts the repository. That won't work for an agent running on a different machine, or a Jenkins server hosted on a different machine. If you need to use agents which are not th

Best practices: many distinct jobs vs parameterized jobs

2016-08-12 Thread Rich Schumacher
Hey folks, I'm using the Job DSL plugin to create CI/CD pipelines for a bunch of projects. The projects themselves are very similar and therefore the jobs for build and release will be nearly identical, differing only in stuff like Git repo to clone, email address for notifications, etc. I'v

[Git-Plugin] notifyCommit not matching local (windows) repository

2016-08-12 Thread John Thornborrow
Hi! Build(s) configured with repo: D:/Repositories/Project post-commit hook configured with: curl http://server/git/notifyCommit?url=D:/Repositories/Project Always returns: "No GIT consumers using SCM API plugin for: D:/Repositories/Project" Job definitely has SCM Poll checked. Any clues?

Re: Slaves on Old OS's

2016-08-12 Thread Matt Wilson
haha. Nothing older than 5.x. I'll give that a try on AIX. I know I've tried that on Solaris, but I don't think I have on AIX. cheers On Friday, August 12, 2016 at 3:06:27 PM UTC-4, Baptiste Mathus wrote: > > Which version for AIX? 5.x or even older? > > Don't have one handy anymore, but IIRC

Re: Slaves on Old OS's

2016-08-12 Thread Baptiste Mathus
Which version for AIX? 5.x or even older? Don't have one handy anymore, but IIRC simply copying the /usr/java7 folder (IIRC the path) onto an older version should often work (pretty sure we did it on 6.x to 5.x, maybe 4.x but not sure). Obviously that would make the support contract unusable, but

Re: Pipeline script for Build Trigger

2016-08-12 Thread John Engelman
I was able to get the branch to enable the trigger by adding the following to my Jenkinsfile: properties([ pipelineTriggers([ [$class: "GitHubPushTrigger"] ]) ]) I then manually executed a Branch Index on the parent job and the resulting PR builds had the trigger on push setting

Re: Slaves on Old OS's

2016-08-12 Thread Matt Wilson
Back ports eh. I'll have to look in to that. Thanks Right now I'm having issues with some old AIX and Solaris boxes On Friday, August 12, 2016 at 10:22:37 AM UTC-4, Baptiste Mathus wrote: > > Hi, > > Can't you use a backport or something of the JDK 7 on those platforms? > > BTW, can you tell w

Re: Slaves on Old OS's

2016-08-12 Thread Matt Wilson
Trust me, I wish I didn't have to bother with them. There are lots of different reasons. Old hardware that hasn't been replaced. Old build reproducability. Customer requirement. On Friday, August 12, 2016 at 10:50:07 AM UTC-4, Simona Avornicesei wrote: > > What is the reason for keeping/usin

Re: Jenkins nginx timeout

2016-08-12 Thread Mohamed Sadok Ben Jazia
Something to add, The server consumes a lot of CPU, it reachs 80% of 4CPU while loading the project page the the load stops after showing the 504 timeout error -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and

Jenkins nginx timeout

2016-08-12 Thread Mohamed Sadok Ben Jazia
Hello list, I'm running jenkins with nginx and everything works well. However, When sometimes i open a project in jenkins admin panel, i get a 504 timeout error. I didn't got any error in jenkins logs but in nginx logs upstream timed out (110: Connection timed out) while reading response header

Immediate Requirement- Sr. Java AWS Developer @ Beaverton, OR

2016-08-12 Thread Manjul Kumar
Hello, I hope you are doing well..!! I would like to share this open requirement with you, kindly go through this requirement , *Sr. Java AWS Developer* *Location*: Beaverton, OR *Duration*: Long-term *Experience Level*: 11+ years We have one position open for the Skillset of *AWS + Ang

Immediate Requirement- Sr. Java AWS Developer @ Beaverton, OR

2016-08-12 Thread Manjul Kumar
Hello, I hope you are doing well..!! I would like to share this open requirement with you, kindly go through this requirement , *Sr. Java AWS Developer* *Location*: Beaverton, OR *Duration*: Long-term *Experience Level*: 11+ years We have one position open for the Skillset of *AWS + Ang

Re: Slaves on Old OS's

2016-08-12 Thread Simona Avornicesei
What is the reason for keeping/using such old machines? -- 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 th

Re: Slaves on Old OS's

2016-08-12 Thread Baptiste Mathus
Hi, Can't you use a backport or something of the JDK 7 on those platforms? BTW, can you tell which ones they are? Thanks Le 12 août 2016 2:55 PM, "Matt Wilson" a écrit : > Hi all, > We're currently running Jenkins 1.651.1. > Is there any work around to get the current slave.jar to run with ol

vSphere Plugin & Hot Spares

2016-08-12 Thread Rob Oxspring
Hi I've recently started playing with the "Cloud" part of the vSphere Cloud Plugin to avoid manually managing slaves. Generally it's great but when building a job in a hurry it can be painful to wait for several minutes for a new slave to be cloned, especially when the job itself is only a min

Slaves on Old OS's

2016-08-12 Thread Matt Wilson
Hi all, We're currently running Jenkins 1.651.1. Is there any work around to get the current slave.jar to run with older versions of Java? I've got a few really old machines that are capped out at Java 5 or 6. Up until now these old machines have continued to run jobs via our old pre-jenkins b

Re: Jenkins 2.x - Pipeline(DSL) - Build failed but all stages are green

2016-08-12 Thread thomas . lehmann
All parts of the script are like this: try { // do something } catch(all) { def message="" notifySlack(message) throw new Exception(message) } // finally notifySlack("Done!") currentBuild.result = "SUCCESS" I never see a message from the "catch" but I see the "Done!". All pro

Re: Using HTTP Request plugin to remote control an IDE

2016-08-12 Thread Martin d'Anjou
Sounds like you need to implement a couple of polling loops (a loop to wait for the builder, a loop to query the status). I would do that in the Pipeline DSL. That would be easier than modifying the plugin. For example: def response = httpRequest 'http://localhost:8080/' while (response.status !

Re: Jenkins Publish Over SSH for Jenkins Pipeline

2016-08-12 Thread Baptiste Mathus
Yes. Plugins have generally to be explicitly modified to support pipeline. In that case, as this is quite simple to do with /raw/ calls, I suppose this may be the reason nobody IIRC bothered adding a step for that in publish over ssh plugin or another one. Cheers Le 12 août 2016 7:41 AM, "ctime8

Re: New Pipeline Maven plugin

2016-08-12 Thread Álvaro Lobato
It will override the settings only if you decide to, by specifying a settings parameter. If you don't specify, it will use the already defined ones. As for the release plugin I'm not aware of any plan for it on pipeline, are you having problems with sh/bat mvn release:prepare release:perform ?

Using HTTP Request plugin to remote control an IDE

2016-08-12 Thread Amaury Laurent
Hi everyone, I'm interested in using HTTP Request Plugin to remotely control our development environment. My objectives are: 1-Waiting for my builder to start (maybe in Build Environment section of Jenkins) 2-Trigger a build remotely 3-Periodically query its status 4-Retrieve build results fro

Re: Multibranch Pipeline: Jenkins View missing last build information

2016-08-12 Thread Sverre Moe
https://issues.jenkins-ci.org/browse/JENKINS-37369 fredag 1. juli 2016 10.03.34 UTC+2 skrev Sverre Moe følgende: > > The Jenkins views has no information about "Last Success", "Last Failure" > and "Last Duration" for Multibranch Pipelines. > It should propagate the result from the last built bran