Re: Interested in building your plugin on ci.jenkins.io?

Thanks a lot! This worked well :) -Fritz On 17.02.2017 13:01, Robert Sandell wrote: > Here is one example using the declarative style that is running on > ci.jenkins.io > > https://github.com/stapler/stapler/blob/master/Jenkinsfile > > /B > > On Wed, Feb 15, 2017 at

Re: Interested in building your plugin on ci.jenkins.io?

Here is one example using the declarative style that is running on ci.jenkins.io https://github.com/stapler/stapler/blob/master/Jenkinsfile /B On Wed, Feb 15, 2017 at 6:04 PM, Fritz Elfert wrote: > (replies inline) > > On 15.02.2017 17:40, R. Tyler Croy wrote: > >

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On 15.02.2017 17:40, R. Tyler Croy wrote: > (replies inline) > > On Tue, 14 Feb 2017, Fritz Elfert wrote: > >> Please add https://github.com/jenkinsci/jclouds-plugin > > > You may be interested in using the buildPlugin() method provided by a Shared > Library. Makes things

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Tue, 14 Feb 2017, Fritz Elfert wrote: > Please add https://github.com/jenkinsci/jclouds-plugin You may be interested in using the buildPlugin() method provided by a Shared Library. Makes things rather simple, and looks like it covers the defaults the jclouds-plugin's

Re: Interested in building your plugin on ci.jenkins.io?

Please add https://github.com/jenkinsci/jclouds-plugin Also: I would like to use maven 3.2.x instead of maven 3.3.x See: https://groups.google.com/forum/#!topic/jenkinsci-dev/ebczuKKmOPg Thanks -Fritz -- You received this message because you are subscribed to the Google Groups "Jenkins

Re: Interested in building your plugin on ci.jenkins.io?

Can you add https://github.com/jenkinsci/sauce-ondemand-plugin too? I finally got it not eating up a ton of memory On Monday, September 5, 2016 at 4:44:40 PM UTC-7, James Dumay wrote: > > Hi Tyler, > > I'd love for https://github.com/jenkinsci/display-url-api-plugin to be > built on that

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 24 Oct 2016, Jesse Glick wrote: > On Sun, Oct 23, 2016 at 10:52 AM, Alexandru Somai > wrote: > > it uses the GitHub Org plugin > > for this, so when I have the Jenkinsifle in the repository, the project > > should be automatically created in

Re: Interested in building your plugin on ci.jenkins.io?

Hello, I'd like to have one of my plugins, the run-selector-plugin , to be built on ci.jenkins.io too. From what I've seen, now it uses the GitHub Org plugin for this, so when I have the Jenkinsifle in the repository, the project should be

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Tue, 06 Sep 2016, Mark Waite wrote: > On Tue, Sep 6, 2016 at 2:08 PM R. Tyler Croy wrote: > > > (replies inline) > > > > On Sun, 04 Sep 2016, Mark Waite wrote: > > > > > Is there a plan to update ci.jenkins.io to the latest workflow plugin so > > > that

Re: Interested in building your plugin on ci.jenkins.io?

> On 06.09.2016, at 22:41, halk...@gmail.com wrote: > > I assume you are talking about the new plugin created by Andrew Bayer? > > https://jenkins.io/blog/2016/09/06/jenkins-world-speaker-blog-pipeline-model-definition/ > >

Re: Interested in building your plugin on ci.jenkins.io?

ipeline-model-definition/ > > > > https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+ > Model+Definition+Plugin > > > > > > > > *From: *Mark Waite <mark.earl.wa...@gmail.com> > *Sent: *September 6, 2016 1:25 PM > *To: *jenkinsci-dev@googlegrou

RE: Interested in building your plugin on ci.jenkins.io?

I assume you are talking about the new plugin created by Andrew Bayer? https://jenkins.io/blog/2016/09/06/jenkins-world-speaker-blog-pipeline-model-definition/ https://wiki.jenkins-ci.org/display/JENKINS/Pipeline+Model+Definition+Plugin From: Mark Waite -- You received this message because

Re: Interested in building your plugin on ci.jenkins.io?

On Tue, Sep 6, 2016 at 2:08 PM R. Tyler Croy wrote: > (replies inline) > > On Sun, 04 Sep 2016, Mark Waite wrote: > > > Is there a plan to update ci.jenkins.io to the latest workflow plugin so > > that I can switch to uses "{" and "}" to identify blocks? I'd like to > >

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Sun, 04 Sep 2016, Mark Waite wrote: > Is there a plan to update ci.jenkins.io to the latest workflow plugin so > that I can switch to uses "{" and "}" to identify blocks? I'd like to > remove the warning from the jobs I host on my private machines, but I don't > want to

Re: Interested in building your plugin on ci.jenkins.io?

Is there a plan to update ci.jenkins.io to the latest workflow plugin so that I can switch to uses "{" and "}" to identify blocks? I'd like to remove the warning from the jobs I host on my private machines, but I don't want to break ci.jenkins.io with a Jenkinsfile that it does not yet

Re: Interested in building your plugin on ci.jenkins.io?

Hi Tyler, I'd love for https://github.com/jenkinsci/display-url-api-plugin to be built on that server. There is a Jenkinsfile already in the repo. Thanks, James On Tuesday, August 9, 2016 at 1:48:24 AM UTC+10, R Tyler Croy wrote: > > Howdy there, your friendly project infrastructure dude

Re: Interested in building your plugin on ci.jenkins.io?

Hi Tyler, I just added a Jenkinsfile to the Jenkins Gradle plugin [1]. Could you add this plugin to https://ci.jenkins.io? Cheers, Stefan [1] https://github.com/jenkinsci/gradle-plugin Am Montag, 8. August 2016 17:48:24 UTC+2 schrieb R Tyler Croy: > > Howdy there, your friendly project

Re: Interested in building your plugin on ci.jenkins.io?

Well, the default setting in the new plugin parent pom is a test-parallelisation of 1C and IIRC the default max heap the the JVM runs on is 512MB. My tests are a bit more hungry for heap than that so I've set the max heap to 1GB per fork (I used to have it on 2GB but our current build slaves

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Wed, 17 Aug 2016, Robert Sandell wrote: > What are the specs for the slaves that the plugin builds will be running > on? I'm asking because I had to do some tweaking of my surefire parameters > to make them fit into the slaves (sorry agents) the community plugins are >

Re: Interested in building your plugin on ci.jenkins.io?

What are the specs for the slaves that the plugin builds will be running on? I'm asking because I had to do some tweaking of my surefire parameters to make them fit into the slaves (sorry agents) the community plugins are currently building on. So an increase in available cores for example might

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Fri, 12 Aug 2016, Kanstantsin Shautsou wrote: > In travis i have sudo and running docker, i can re-install it and i can run > docker in docker. Prepare env in any way i need for integration tests. > So the same. Can you link me to your .travis.yml so I can see exactly

Re: Interested in building your plugin on ci.jenkins.io?

In travis i have sudo and running docker, i can re-install it and i can run docker in docker. Prepare env in any way i need for integration tests. So the same. > On Aug 12, 2016, at 17:00, R. Tyler Croy wrote: > > (replies inline) > > On Fri, 12 Aug 2016, Kanstantsin

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Fri, 12 Aug 2016, Kanstantsin Shautsou wrote: > Is it possible to run docker daemon? Could you expand more on what you mean by this? Does this mean executing an agent as root, or having the ability to run a Docker daemon parallel to the one already running on the machine?

Re: Interested in building your plugin on ci.jenkins.io?

Is it possible to run docker daemon? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. To view this discussion

Re: Interested in building your plugin on ci.jenkins.io?

Will there be any solutions for getting secrets available? I've been working on a Jenkinsfile to run on our internal one (https://github.com/saucelabs/jenkins-sauce-ondemand-plugin/blob/master/Jenkinsfile) but want to hook up various external tools for "quality" checking. Gavin On Monday,

Re: Interested in building your plugin on ci.jenkins.io?

Tyler, the TFS Plugin does not need a windows agent to run the build. For IT tests is needs a full TFS server but we are handling that separately already anyway. Just for simple build integration without the IT tests as we have not it might be a good simple start. We already have a build on the

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 08 Aug 2016, Manfred Moser wrote: > Hi Tyler, > > Can you point me to some docs on setting that up. I would like to create > that setup for the tfs jenkins plugin. Does the tfs plugin require Windows-based agents to build? If so, you might be blocked by

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Tue, 09 Aug 2016, fkp...@gmail.com wrote: > Hi, > will there be any support for Xbuild ? so that a combined java & c# plugin > can be built? > > if so, I'd like the hp automation tools plugin to be built on that and i'll > write the Jenkinsfile. I'm not clear on whether

Re: Interested in building your plugin on ci.jenkins.io?

Hi, will there be any support for Xbuild ? so that a combined java & c# plugin can be built? if so, I'd like the hp automation tools plugin to be built on that and i'll write the Jenkinsfile. thanks Fima. On Monday, August 8, 2016 at 6:48:24 PM UTC+3, R Tyler Croy wrote: > > Howdy there, your

Re: Interested in building your plugin on ci.jenkins.io?

Hi Tyler, Can you point me to some docs on setting that up. I would like to create that setup for the tfs jenkins plugin. Manfred On Mon, Aug 8, 2016 at 8:48 AM, R. Tyler Croy wrote: > Howdy there, your friendly project infrastructure dude here. I'm hoping to > get > more

Re: Interested in building your plugin on ci.jenkins.io?

On Mon, Aug 8, 2016 at 2:17 PM, Mark Waite wrote: > I hope one day to be able to use the Jenkinsfile to run and report findbugs > warnings, to run and report code coverage, and more. I would expect all that to be part of the standard script; there is nothing

Re: Interested in building your plugin on ci.jenkins.io?

On Mon, Aug 8, 2016 at 1:21 PM R. Tyler Croy wrote: > (replies inline) > > On Mon, 08 Aug 2016, Mark Waite wrote: > > > Is there an eventual evolution planned to move to using the GitHub > > Organizations Folder plugin to build and test pull requests for subsets > of > > the

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 08 Aug 2016, Mark Waite wrote: > Is there an eventual evolution planned to move to using the GitHub > Organizations Folder plugin to build and test pull requests for subsets of > the jenkinsci GitHub organization? > > I was quite impressed with the results of my quick

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 08 Aug 2016, Jesse Glick wrote: > On Mon, Aug 8, 2016 at 11:48 AM, R. Tyler Croy wrote: > > If your plugin > > repository already has a `Jenkinsfile`, or you're interested in creating one > > for your plugin, I would love to have your plugin built

Re: Interested in building your plugin on ci.jenkins.io?

On Mon, Aug 8, 2016 at 12:06 PM Jesse Glick wrote: > On Mon, Aug 8, 2016 at 11:48 AM, R. Tyler Croy > wrote: > > If your plugin > > repository already has a `Jenkinsfile`, or you're interested in creating > one > > for your plugin, I would love to have

Re: Interested in building your plugin on ci.jenkins.io?

On Mon, Aug 8, 2016 at 11:48 AM, R. Tyler Croy wrote: > If your plugin > repository already has a `Jenkinsfile`, or you're interested in creating one > for your plugin, I would love to have your plugin built on our existing > Jenkins-on-Jenkins. I continue to advocate having

Re: Interested in building your plugin on ci.jenkins.io?

I see the git plugin but not the git client plugin. What's the link? On Mon, Aug 8, 2016, 10:09 AM R. Tyler Croy wrote: > (replies inline) > > On Mon, 08 Aug 2016, Mark Waite wrote: > > > I'd like the git client plugin built on https://ci.jenkins.io/ if > > possible. It

Re: Interested in building your plugin on ci.jenkins.io?

Is there an eventual evolution planned to move to using the GitHub Organizations Folder plugin to build and test pull requests for subsets of the jenkinsci GitHub organization? I was quite impressed with the results of my quick experiments with the GitHub Organizations Folder plugin. Mark Waite

Re: Interested in building your plugin on ci.jenkins.io?

(replies inline) On Mon, 08 Aug 2016, Mark Waite wrote: > I'd like the git client plugin built on https://ci.jenkins.io/ if > possible. It already has a Jenkinsfile on its active branches, and has > been running tests in my various development and test environments from > that Jenkinsfile.

Re: Interested in building your plugin on ci.jenkins.io?

I'd like the git client plugin built on https://ci.jenkins.io/ if possible. It already has a Jenkinsfile on its active branches, and has been running tests in my various development and test environments from that Jenkinsfile. Mark Waite On Mon, Aug 8, 2016 at 9:48 AM R. Tyler Croy

Interested in building your plugin on ci.jenkins.io?

Howdy there, your friendly project infrastructure dude here. I'm hoping to get more accurate usage requirements for our eventual migration of https://ci.jenkins.io, and the rest of our infra, to Azure [0]. If your plugin repository already has a `Jenkinsfile`, or you're interested in creating one