Re: CI usability - isn't there a problem that tests are executed only after a developer pushed his changed to the repsitory?

Thanks for your ideas. I think an on-demand script would fit my organization, but I'll take into account the way that GIT script works. On Monday, August 5, 2013 4:20:05 AM UTC+3, Mark Waite wrote: > > > -- > *From:* Avihay Eyal > > *To:* jenkins...@googlegroups.c

Re: CI usability - isn't there a problem that tests are executed only after a developer pushed his changed to the repsitory?

> > From: Avihay Eyal >To: jenkinsci-users@googlegroups.com >Cc: dirk.heinri...@recommind.com >Sent: Sunday, August 4, 2013 12:37 PM >Subject: Re: CI usability - isn't there a problem that tests are executed only >after a developer pushed his changed to the re

Re: Jenkins server will not start after upgrade to 1.524 or 1.525, would appreciate any help.

Thank you! Removing maven.jpi.disabled and javadoc.jpi.disabled resolved the issue. Thanks again! On Mon, Aug 5, 2013 at 9:23 AM, Daniel Beck wrote: > See e.g. > > https://issues.jenkins-ci.org/browse/JENKINS-18922 > https://issues.jenkins-ci.org/browse/JENKINS-19000 > > Did you disable bundl

Re: Jenkins server will not start after upgrade to 1.524 or 1.525, would appreciate any help.

See e.g. https://issues.jenkins-ci.org/browse/JENKINS-18922 https://issues.jenkins-ci.org/browse/JENKINS-19000 Did you disable bundled plugins, like e.g. the Maven plugin? On 04.08.2013, at 23:15, Stuart Whelan wrote: > Hi folks, > > I was/am running 1.522 on a windows server 2008R2 64bit sy

Jenkins server will not start after upgrade to 1.524 or 1.525, would appreciate any help.

Hi folks, I was/am running 1.522 on a windows server 2008R2 64bit system using winstone. Last week I tried to upgrade to 524, and had to roll back as jenkins wouldn't start afterwards. Today I tried 525 and the same thing happened. A gist of the error log is: https://gist.github.com/StuartWhela

Re: CI usability - isn't there a problem that tests are executed only after a developer pushed his changed to the repsitory?

Am Sonntag, 4. August 2013, 11:37:27 schrieb Avihay Eyal: > So you're suggesting using a script, activated via commits to the developer > local repository? No. I'm suggesting a script that runs on demand, when the developers says he's ready. Bye... Dirk http://www.recommind.com --

Re: Plugin installation by hand doesn't work

Hi, indeed there was a permission problem in the hpi files I downloaded, thanks :) On Thursday, August 1, 2013 9:17:02 PM UTC+3, Daniel Beck wrote: > > What's in the log (/var/log/jenkins/jenkins.log probably)? > > Did you get the permissions of the files right? > > On 01.08.2013, at 18:13, Avi

Re: CI usability - isn't there a problem that tests are executed only after a developer pushed his changed to the repsitory?

I'm using Mercurial, which is a distrusted source control. So you're suggesting using a script, activated via commits to the developer local repository? Once the developer committed changes to it's repository, the script will build that changes with the latest code, run all the regression test