Re: [hibernate-dev] Jenkins upgrade

Marko brought to my attention that a few jobs, including Hibernate Validator's, were failing. The failures were caused by a regression in Jenkins 2.175 [1]. I just upgraded again, which should work around the problem. You may get warnings in your build logs related to FilePaths being serialized: p

Re: [hibernate-dev] Jenkins upgrade

Thanks guys! On Tue, Apr 30, 2019 at 8:07 AM Davide D'Alto wrote: > On a related note, I've created a new AMI to use as slave and > configure Jenkins to use it. > If there are issues, it is still possible to use the old one by > updating the Jenkins configuration (http://ci.hibernate.org/config

Re: [hibernate-dev] Jenkins upgrade

On a related note, I've created a new AMI to use as slave and configure Jenkins to use it. If there are issues, it is still possible to use the old one by updating the Jenkins configuration (http://ci.hibernate.org/configure) to the AMI ID we used before (custom fedora v23). Cheers, Davide On Tu

Re: [hibernate-dev] Jenkins updates

Hi, Jenkins is up-to-date now. Please, keep that in mind if you face some problems. Cheers, Davide On Fri, Jul 20, 2018 at 11:16 AM, Davide D'Alto wrote: > Hello, > I'm planning to update Jenkins today. > > This means that there might be some disruptions on CI. > > Let me know if you have somet

Re: [hibernate-dev] Jenkins updates tomorrow

CSS should be fixed as well now. There was a problem when going to the Nodes page where the buttons overlapped with the logout link. Let me know if there is something else weird. Cheers, Davide On Fri, Feb 9, 2018 at 7:23 PM, Davide D'Alto wrote: > I finished the Jenkins upgrades, I'm working

Re: [hibernate-dev] Jenkins updates tomorrow

I finished the Jenkins upgrades, I'm working on fixing some CSS issues. If you have some problems with the Jobs, let me know. Cheers, Davide On Thu, Feb 8, 2018 at 3:48 PM, Guillaume Smet wrote: > Thanks for warning and thanks for doing the update! > > > On Thu, Feb 8, 2018 at 4:34 PM, Davide D

Re: [hibernate-dev] Jenkins updates tomorrow

Thanks for warning and thanks for doing the update! On Thu, Feb 8, 2018 at 4:34 PM, Davide D'Alto wrote: > Hi, > I'm planning to update Jenkins tomorrow, it should painless but, just in > case, > expect possible disruptions. > > Cheers, > Davide > ___

Re: [hibernate-dev] Jenkins job priorities

Well done, thanks a lot. On Fri, Jan 12, 2018 at 8:12 AM, Yoann Rodiere wrote: > Quick update: the priority plugin seems to be working fine, and I disabled > the Heavy Job plugin. It turns out the Heavy Job plugin was preventing the > Amazon EC2 plugin to spin up new slaves, probably because the

Re: [hibernate-dev] Jenkins job priorities

Quick update: the priority plugin seems to be working fine, and I disabled the Heavy Job plugin. It turns out the Heavy Job plugin was preventing the Amazon EC2 plugin to spin up new slaves, probably because the Amazon EC2 plugin only saw two empty slots on an existing slave and couldn't understand

Re: [hibernate-dev] Jenkins job priorities

I know ;) Anyway I do agree that any release jobs should be given the highest priority in the job queue On Wed, Jan 10, 2018, 10:29 AM Guillaume Smet wrote: > On Wed, Jan 10, 2018 at 5:00 PM, Steve Ebersole > wrote: > >> And in advance I say I would not be cool with you killing my jobs for >>

Re: [hibernate-dev] Jenkins job priorities

On Wed, Jan 10, 2018 at 4:50 PM, Sanne Grinovero wrote: > I'm confused now. AFAIK this has never been the case? I understand > that the release process itself runs without running the tests, but > I'd still run the tests by triggering a full build before. > You made the example of the TCK and var

Re: [hibernate-dev] Jenkins job priorities

On Wed, Jan 10, 2018 at 5:00 PM, Steve Ebersole wrote: > And in advance I say I would not be cool with you killing my jobs for your > job to run > Yeah, that was my understanding. I don't expect anyone to be cool with it. ___ hibernate-dev mailing lis

Re: [hibernate-dev] Jenkins job priorities

And in advance I say I would not be cool with you killing my jobs for your job to run On Wed, Jan 10, 2018 at 9:52 AM Sanne Grinovero wrote: > On 10 January 2018 at 11:33, Guillaume Smet > wrote: > > On Wed, Jan 10, 2018 at 12:08 PM, Sanne Grinovero > > wrote: > >> > >> Some of our test suites

Re: [hibernate-dev] Jenkins job priorities

On 10 January 2018 at 11:33, Guillaume Smet wrote: > On Wed, Jan 10, 2018 at 12:08 PM, Sanne Grinovero > wrote: >> >> Some of our test suites used to take 2 hours to run (even 5 days some >> years ago); now you say waiting 20 minutes is not good enough? You'll >> have to optimise our code better

Re: [hibernate-dev] Jenkins job priorities

On Wed, Jan 10, 2018 at 12:08 PM, Sanne Grinovero wrote: > Some of our test suites used to take 2 hours to run (even 5 days some > years ago); now you say waiting 20 minutes is not good enough? You'll > have to optimise our code better :P > What I'm saying is that in the current setup, I don't w

Re: [hibernate-dev] Jenkins job priorities

> Let's not forget that many Apache projects take a week or two to > perform a release, we all know of other projects needing months, so by > the law of diminishing returns I don't think we should invest much > more of out time to shave on the 10 minutes.. just spin up some extra > nodes :) +1

Re: [hibernate-dev] Jenkins job priorities

On 10 January 2018 at 10:25, Guillaume Smet wrote: > Hi, > > On Wed, Jan 10, 2018 at 11:06 AM, Yoann Rodiere wrote: >> >> I hope we will be able to use this priority feature instead of the Heavy >> Job plugin (which allows to assign weights to jobs), and avoid concurrent >> builds completely. Wit

Re: [hibernate-dev] Jenkins job priorities

Hi, On Wed, Jan 10, 2018 at 11:06 AM, Yoann Rodiere wrote: > > I hope we will be able to use this priority feature instead of the Heavy > Job plugin (which allows to assign weights to jobs), and avoid concurrent > builds completely. With the current setup, someone releasing his/her > project will

Re: [hibernate-dev] Jenkins build became unstable: hibernate-search-master-mariadb #244

mysteries of Maven .. it sometimes reports SUCCESS, yet you have to scroll into the logs to find the error. I wonder if there's something off in our pom files: it's the the first time it happens. = Results : Tests in error: SearchNewEntityJmsMasterSlaveIT>MasterSlaveTestTemplate.dele

Re: [hibernate-dev] Jenkins

Thanks Sanne On 16 November 2015 at 10:08, Sanne Grinovero wrote: > I don't think orm-5.0-h2 ever worked? The configuration was wrong: it > wasn't fetching the branch 5.0 from the git repository, but it was > configured to monitor that branch for changes. > I changed it now, let me know if it do

Re: [hibernate-dev] Jenkins

I don't think orm-5.0-h2 ever worked? The configuration was wrong: it wasn't fetching the branch 5.0 from the git repository, but it was configured to monitor that branch for changes. I changed it now, let me know if it doesn't work. Sanne On 15 November 2015 at 20:32, andrea boriero wrote: > it

Re: [hibernate-dev] Jenkins

it's seems orm-5.0-h2 suffers the same problem. On 15 November 2015 at 00:48, andrea boriero wrote: > Thanks Sanne > On 14 Nov 2015 20:28, "Sanne Grinovero" wrote: > >> Looks like you were right. >> >> The local clones of the git repository on the build servers were >> corrupt; my guess is that

Re: [hibernate-dev] Jenkins

Thanks Sanne On 14 Nov 2015 20:28, "Sanne Grinovero" wrote: > Looks like you were right. > > The local clones of the git repository on the build servers were > corrupt; my guess is that happened when we recently run out of disk > space. > > I've reconfigured the job to fully wipe its repository a

Re: [hibernate-dev] Jenkins

Looks like you were right. The local clones of the git repository on the build servers were corrupt; my guess is that happened when we recently run out of disk space. I've reconfigured the job to fully wipe its repository and do a full clone; I'll let it run this way so that it will iteratively f

Re: [hibernate-dev] Jenkins notification plugin

Btw, have not tried this yet but I do see BuildWatch in my Play results and Google says it is installable to my phone... On Sat 18 May 2013 06:51:20 PM CDT, Steve Ebersole wrote: > > Doh. I missed the sony watch part :) > > On May 18, 2013 5:57 PM, "Sanne Grinovero"

Re: [hibernate-dev] Jenkins notification plugin

Doh. I missed the sony watch part :) On May 18, 2013 5:57 PM, "Sanne Grinovero" wrote: > Looks very nice! are you installing it? > > The app they recommend - BuildWatch - however is specifically meant > for an android watch from Sony (a specific product): I'd need to find > some alternative app

Re: [hibernate-dev] Jenkins notification plugin

Looks very nice! are you installing it? The app they recommend - BuildWatch - however is specifically meant for an android watch from Sony (a specific product): I'd need to find some alternative app, or create one, as I don't have that watch (and don't like wearing watches, although this one looks

Re: [hibernate-dev] Jenkins Plugins

Yes the scripts creating the server manage plugin installations too, but it's absolutely fine to install them manually to play with them, and add them to the script later when you're convinced you want to keep them. To make sure a plugin is automatically installed when re-running the machine creat

Re: [hibernate-dev] Jenkins Jobs

On May 4, 2012, at 7:33 PM, Steve Ebersole wrote: > Touche ;) > > Ok I'll just chaulk it up to that then. > > Overall do you think that is an issue with Jenkins? Or with the JBoss setup? > > not sure, but we may improve this. the slaves used by Jenkins can be labeled, and all hibernate jobs

Re: [hibernate-dev] Jenkins Jobs

Touche ;) Ok I'll just chaulk it up to that then. Overall do you think that is an issue with Jenkins? Or with the JBoss setup? On May 3, 2012 11:15 PM, "Strong Liu" wrote: > > On May 4, 2012, at 3:45 AM, Steve Ebersole wrote: > > But I killed it and #243 started *immediately* > > > well, you al

Re: [hibernate-dev] Jenkins Jobs

On May 4, 2012, at 3:45 AM, Steve Ebersole wrote: > But I killed it and #243 started *immediately* well, you already know, it sucks > > On Thu 03 May 2012 02:39:13 PM CDT, Strong Liu wrote: >> I think it was just waiting for next available executors, basically >> there were too many jobs in qu

Re: [hibernate-dev] Jenkins Jobs

But I killed it and #243 started *immediately* On Thu 03 May 2012 02:39:13 PM CDT, Strong Liu wrote: > I think it was just waiting for next available executors, basically > there were too many jobs in queue waiting to be run > > On May 4, 2012, at 3:27 AM, Steve Ebersole wrote: > >> Strong, I had

Re: [hibernate-dev] Jenkins Jobs

I think it was just waiting for next available executors, basically there were too many jobs in queue waiting to be run On May 4, 2012, at 3:27 AM, Steve Ebersole wrote: > Strong, I had to kill hibernate-core-master-matrix job #242. It had > been hanging for the last 8+ hours without every eve

Re: [hibernate-dev] Jenkins configuration?

On 03/22/2012 06:22 PM, Sanne Grinovero wrote: > Hi all, > sorry if it's a naive question, I'm not understanding what is wrong > this this CI job: > > http://hudson.qa.jboss.com/hudson/job/hibernate-search-master-windows/64/console > > It was working fine up to a couple of days ago, and there is no

Re: [hibernate-dev] Jenkins build became unstable: hibernate-core-master-matrix » mssql2008R1,java16_default,hibernate #185

On Mar 15, 2012, at 12:31 AM, Steve Ebersole wrote: > I am not able to produce this failure locally just using H2 and I do not > see how my change that would seem to cause this chaned the output SQL in > this particular case. H2 is fine, since our main master job finishes w/o any failure > >