Re: Jenkins installer for Windows and Mac

Hi Daniel Thank you. 2017-08-11 22:27 GMT+09:00 Daniel Beck : > > > On 11. Aug 2017, at 10:08, Masaru Tsuchiyama wrote: > > > > Could you tell me how to build Windows and Mac Installers of Jenkins? > > https://github.com/jenkinsci/packaging should have

Re: Installing jenkins frontend and backend separately

Jenkins doesn't really have a concept of a front end and a back end. There is a Jenkins war file which provides the REST API, the web page generation, and the storage. Separating it into a front end and a back end is probably an enormous effort. Can you provide a higher level view of your need?

Installing jenkins frontend and backend separately

Hi all, I'm interested in installing frontend and backends of jenkins separately and I would like to have one front end server and multiple backend servers. Then connect to backend servers using the front end server. I would like to know whether it is already possible? or is it possible

Maintenance help needed on ghprb-plugin

Hi folks - I've been maintaining this for a year or so, and it's been a good ride. However, I no longer feel I can be an effective maintainer for various reasons including time commitments. Looking for volunteers. If you've developed on this plugin before please feel free to answer on

Re: Jenkins installer for Windows and Mac

> On 11. Aug 2017, at 10:08, Masaru Tsuchiyama wrote: > > Could you tell me how to build Windows and Mac Installers of Jenkins? https://github.com/jenkinsci/packaging should have everything you need. Note that It's not going to be as easy as building Jenkins, as it's not

Jenkins installer for Windows and Mac

Hi. Could you tell me how to build Windows and Mac Installers of Jenkins? I have successfully built jenkins.war with the following command on Fedora 26. mvn clean install -pl war -am -DskipTests I saw https://github.com/jenkinsci/jenkins/blob/master/BUILDING.TXT -- Masaru Tsuchiyama

Re: */api/json fails for a new Jenkins plugin

But it looks like your action is attached to a job. So instead you could/should just put @Exported on the getters in the action that you want exposed and then get it via the /job/test/api/json endpoint instead. /B 2017-08-10 22:55 GMT+02:00 Daniel Mercier : > Thank you very