Could you try again now please? On 13 January 2016 at 19:26, Steve Ebersole <steve(a)hibernate.org&gt; wrote: > Trying to push and verify my announcement blog post for 5.0.7 release, but > Jenkins fails to build it[1]. Apparently command `rake` not found. > > So what now? > > [1] - http://ci.hibernate.org/view/Website/job/staging.in.relation.to/145/ > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev

Sorry, spoke too soon... RROR: Running Awestruct failed. /mnt/jenkins-workdir/workspace/staging.in.relation.to/Rakefile:104:in `run_awestruct' /mnt/jenkins-workdir/workspace/staging.in.relation.to/Rakefile:71:in `block in <top (required)>' Tasks: TOP => gen (See full trace by running task with --trace) On Wed, Jan 13, 2016 at 1:45 PM Steve Ebersole <steve(a)hibernate.org&gt; wrote: > Whatever you did seems to have done the trick: > http://ci.hibernate.org/view/Website/job/staging.in.relation.to/146/ > > Thanks > > > On Wed, Jan 13, 2016 at 1:32 PM Sanne Grinovero <sanne(a)hibernate.org&gt; > wrote: > >> Could you try again now please? >> >> On 13 January 2016 at 19:26, Steve Ebersole <steve(a)hibernate.org&gt; wrote: >> > Trying to push and verify my announcement blog post for 5.0.7 release, >> but >> > Jenkins fails to build it[1]. Apparently command `rake` not found. >> > >> > So what now? >> > >> > [1] - >> http://ci.hibernate.org/view/Website/job/staging.in.relation.to/145/ >> > _______________________________________________ >> > hibernate-dev mailing list >> > hibernate-dev(a)lists.jboss.org >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev >> >

Ok, that fixed this last problem On Wed, Jan 13, 2016 at 2:17 PM Steve Ebersole <steve(a)hibernate.org&gt; wrote: > Per Hardy this might be due to a bad post uploaded to staging by Max. I > just deleted that file from staging and am trying build again > > On Wed, Jan 13, 2016 at 1:50 PM Steve Ebersole <steve(a)hibernate.org&gt; > wrote: > >> Sorry, spoke too soon... >> >> RROR: Running Awestruct failed. >> /mnt/jenkins-workdir/workspace/staging.in.relation.to/Rakefile:104:in `run_awestruct' >> /mnt/jenkins-workdir/workspace/staging.in.relation.to/Rakefile:71:in `block in <top (required)>' >> Tasks: TOP => gen >> (See full trace by running task with --trace) >> >> >> >> On Wed, Jan 13, 2016 at 1:45 PM Steve Ebersole <steve(a)hibernate.org&gt; >> wrote: >> >>> Whatever you did seems to have done the trick: >>> http://ci.hibernate.org/view/Website/job/staging.in.relation.to/146/ >>> >>> Thanks >>> >>> >>> On Wed, Jan 13, 2016 at 1:32 PM Sanne Grinovero <sanne(a)hibernate.org&gt; >>> wrote: >>> >>>> Could you try again now please? >>>> >>>> On 13 January 2016 at 19:26, Steve Ebersole <steve(a)hibernate.org&gt; >>>> wrote: >>>> > Trying to push and verify my announcement blog post for 5.0.7 >>>> release, but >>>> > Jenkins fails to build it[1]. Apparently command `rake` not found. >>>> > >>>> > So what now? >>>> > >>>> > [1] - >>>> http://ci.hibernate.org/view/Website/job/staging.in.relation.to/145/ >>>> > _______________________________________________ >>>> > hibernate-dev mailing list >>>> > hibernate-dev(a)lists.jboss.org >>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev >>>> >>> _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Ok, on to the next... staging.hibernate.org build fails now: rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.1] On Wed, Jan 13, 2016 at 2:34 PM andrea boriero <dreborier(a)gmail.com&gt; wrote: > the problem seems related with the file name > > /2016-01-12-jboss-community-asylum-hibernate-strikes-back-episode-v..erb > > instead of > > /2016-01-12-jboss-community-asylum-hibernate-strikes-back-episode-v. > *html*.erb > > On 13 January 2016 at 20:22, Steve Ebersole <steve(a)hibernate.org&gt; wrote: > >> Ok, that fixed this last problem >> >> On Wed, Jan 13, 2016 at 2:17 PM Steve Ebersole <steve(a)hibernate.org&gt; >> wrote: >> >> > Per Hardy this might be due to a bad post uploaded to staging by Max. >> I >> > just deleted that file from staging and am trying build again >> > >> > On Wed, Jan 13, 2016 at 1:50 PM Steve Ebersole <steve(a)hibernate.org&gt; >> > wrote: >> > >> >> Sorry, spoke too soon... >> >> >> >> RROR: Running Awestruct failed. >> >> /mnt/jenkins-workdir/workspace/staging.in.relation.to/Rakefile:104:in >> `run_awestruct' >> >> /mnt/jenkins-workdir/workspace/staging.in.relation.to/Rakefile:71:in >> `block in <top (required)>' >> >> Tasks: TOP => gen >> >> (See full trace by running task with --trace) >> >> >> >> >> >> >> >> On Wed, Jan 13, 2016 at 1:45 PM Steve Ebersole <steve(a)hibernate.org&gt; >> >> wrote: >> >> >> >>> Whatever you did seems to have done the trick: >> >>> http://ci.hibernate.org/view/Website/job/staging.in.relation.to/146/ >> >>> >> >>> Thanks >> >>> >> >>> >> >>> On Wed, Jan 13, 2016 at 1:32 PM Sanne Grinovero <sanne(a)hibernate.org >> > >> >>> wrote: >> >>> >> >>>> Could you try again now please? >> >>>> >> >>>> On 13 January 2016 at 19:26, Steve Ebersole <steve(a)hibernate.org&gt; >> >>>> wrote: >> >>>> > Trying to push and verify my announcement blog post for 5.0.7 >> >>>> release, but >> >>>> > Jenkins fails to build it[1]. Apparently command `rake` not >> found. >> >>>> > >> >>>> > So what now? >> >>>> > >> >>>> > [1] - >> >>>> >> http://ci.hibernate.org/view/Website/job/staging.in.relation.to/145/ >> >>>> > _______________________________________________ >> >>>> > hibernate-dev mailing list >> >>>> > hibernate-dev(a)lists.jboss.org >> >>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev >> >>>> >> >>> >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > >

Davide, since Dec 21st this job is configured to run on slave4 only (which is offline). Is there a specific reason for this or can it be changed to run on any node again? 2016-01-14 3:21 GMT+01:00 Steve Ebersole <steve(a)hibernate.org&gt;: > Ok, next problem... :( > > http://ci.hibernate.org/view/Website/job/www.hibernate.org/ This job has > been stuck in "pending—ci-slave-4 is offline" for hours now. > > > On Wed, Jan 13, 2016 at 2:37 PM Steve Ebersole <steve(a)hibernate.org&gt; wrote: > >> Ok, on to the next... >> >> staging.hibernate.org build fails now: >> >> rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1165) [sender=3.1.1] >> >> >> >> On Wed, Jan 13, 2016 at 2:34 PM andrea boriero <dreborier(a)gmail.com&gt; >> wrote: >> >>> the problem seems related with the file name >>> >>> /2016-01-12-jboss-community-asylum-hibernate-strikes-back-episode-v..erb >>> >>> instead of >>> >>> /2016-01-12-jboss-community-asylum-hibernate-strikes-back-episode-v. >>> *html*.erb >>> >>> On 13 January 2016 at 20:22, Steve Ebersole <steve(a)hibernate.org&gt; wrote: >>> >>>> Ok, that fixed this last problem >>>> >>>> On Wed, Jan 13, 2016 at 2:17 PM Steve Ebersole <steve(a)hibernate.org&gt; >>>> wrote: >>>> >>>> > Per Hardy this might be due to a bad post uploaded to staging by Max. >>>> I >>>> > just deleted that file from staging and am trying build again >>>> > >>>> > On Wed, Jan 13, 2016 at 1:50 PM Steve Ebersole <steve(a)hibernate.org > >>>> > wrote: >>>> > >>>> >> Sorry, spoke too soon... >>>> >> >>>> >> RROR: Running Awestruct failed. >>>> >> /mnt/jenkins-workdir/workspace/ staging.in.relation.to/Rakefile:104:in >>>> `run_awestruct' >>>> >> /mnt/jenkins-workdir/workspace/ staging.in.relation.to/Rakefile:71:in >>>> `block in <top (required)>' >>>> >> Tasks: TOP => gen >>>> >> (See full trace by running task with --trace) >>>> >> >>>> >> >>>> >> >>>> >> On Wed, Jan 13, 2016 at 1:45 PM Steve Ebersole < steve(a)hibernate.org&gt; >>>> >> wrote: >>>> >> >>>> >>> Whatever you did seems to have done the trick: >>>> >>> http://ci.hibernate.org/view/Website/job/staging.in.relation.to/146/ >>>> >>> >>>> >>> Thanks >>>> >>> >>>> >>> >>>> >>> On Wed, Jan 13, 2016 at 1:32 PM Sanne Grinovero < sanne(a)hibernate.org >>>> > >>>> >>> wrote: >>>> >>> >>>> >>>> Could you try again now please? >>>> >>>> >>>> >>>> On 13 January 2016 at 19:26, Steve Ebersole <steve(a)hibernate.org > >>>> >>>> wrote: >>>> >>>> > Trying to push and verify my announcement blog post for 5.0.7 >>>> >>>> release, but >>>> >>>> > Jenkins fails to build it[1]. Apparently command `rake` not >>>> found. >>>> >>>> > >>>> >>>> > So what now? >>>> >>>> > >>>> >>>> > [1] - >>>> >>>> >>>> http://ci.hibernate.org/view/Website/job/staging.in.relation.to/145/ >>>> >>>> > _______________________________________________ >>>> >>>> > hibernate-dev mailing list >>>> >>>> > hibernate-dev(a)lists.jboss.org >>>> >>>> > https://lists.jboss.org/mailman/listinfo/hibernate-dev >>>> >>>> >>>> >>> >>>> _______________________________________________ >>>> hibernate-dev mailing list >>>> hibernate-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/hibernate-dev >>>> >>> >>> > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

Hi, On Thu, Jan 14, 2016 at 10:37:42AM +0200, Vlad Mihalcea wrote: > I see that the production and the staging are out of sync now and trying to > merge the upstream production leads to a merge commit. > > How do we normally handle the cases when the production branch history > diverges from staging? You force push production to staging. There is no strong requirement for staging being in sync with production. Staging is also there to test changes in the sites L&F or HTML fixes. It is quite common that staging and production are out of sync. For that reason it is important that when you want to blog you base your work on top of production and not staging. Staging is just a convenient place to try changes to the site. A forced push is perfectly ok. Personally I always pull from production and create "blog" branches from this branch. Then when I want to preview the changes life, I do a forced push to the staging branch. If I am happy with the result I push to production. --Hardy

> I thought those must be in-sync, like in a typical QA and production > environment where you push changes from develop -> qa -> production Staging can differ from production (usually be ahead) for previewing changes. Then "releasing" is just a fast-forward merge from staging to production. We don't enforce any specific workflow, though (like only merges from staging are legit to production or so). Personally, when using staging, I always try to leave it set to (or fast-forwardable to) production when I am done with a given authoring job. So the next guy coming after me doesn't have to care about any non-published commits on staging. 2016-01-14 10:21 GMT+01:00 Vlad Mihalcea <mihalcea.vlad(a)gmail.com&gt;: > Hi, > > Thanks for the clarifications. I thought that forced push is disabled, but > that might be true for the ORM, OGM, etc projects only. > I was also using a separate branch for every post, but I was branching from > staging because that was the default branch I got when forking the repo. > > I thought those must be in-sync, like in a typical QA and production > environment where you push changes from develop -> qa -> production > I'm now writing a new post and push it to both staging and production when > I'm done. > > Vlad > > On Thu, Jan 14, 2016 at 10:56 AM, Hardy Ferentschik <hardy(a)hibernate.org > > wrote: >> >> Hi, >> >> On Thu, Jan 14, 2016 at 10:37:42AM +0200, Vlad Mihalcea wrote: >> > I see that the production and the staging are out of sync now and trying >> > to >> > merge the upstream production leads to a merge commit. >> > >> > How do we normally handle the cases when the production branch history >> > diverges from staging? >> >> You force push production to staging. There is no strong requirement for >> staging being >> in sync with production. Staging is also there to test changes in the >> sites L&F or HTML >> fixes. It is quite common that staging and production are out of sync. >> >> For that reason it is important that when you want to blog you base your >> work on top of >> production and not staging. Staging is just a convenient place to try >> changes to the site. >> A forced push is perfectly ok. >> >> Personally I always pull from production and create "blog" branches from >> this branch. >> Then when I want to preview the changes life, I do a forced push to the >> staging branch. >> If I am happy with the result I push to production. >> >> --Hardy >> > _______________________________________________ hibernate-dev mailing list hibernate-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev

> I thought those must be in-sync, like in a typical QA and production > environment where you push changes from develop -> qa -> production Staging can differ from production (usually be ahead) for previewing changes. Then "releasing" is just a fast-forward merge from staging to production. We don't enforce any specific workflow, though (like only merges from staging are legit to production or so). Personally, when using staging, I always try to leave it set to (or fast-forwardable to) production when I am done with a given authoring job. So the next guy coming after me doesn't have to care about any non-published commits on staging. 2016-01-14 10:21 GMT+01:00 Vlad Mihalcea <mihalcea.vlad(a)gmail.com&gt;: > Hi, > > Thanks for the clarifications. I thought that forced push is disabled, but > that might be true for the ORM, OGM, etc projects only. > I was also using a separate branch for every post, but I was branching from > staging because that was the default branch I got when forking the repo. > > I thought those must be in-sync, like in a typical QA and production > environment where you push changes from develop -> qa -> production > I'm now writing a new post and push it to both staging and production when > I'm done. > > Vlad > > On Thu, Jan 14, 2016 at 10:56 AM, Hardy Ferentschik <hardy(a)hibernate.org > > wrote: >> >> Hi, >> >> On Thu, Jan 14, 2016 at 10:37:42AM +0200, Vlad Mihalcea wrote: >> > I see that the production and the staging are out of sync now and trying >> > to >> > merge the upstream production leads to a merge commit. >> > >> > How do we normally handle the cases when the production branch history >> > diverges from staging? >> >> You force push production to staging. There is no strong requirement for >> staging being >> in sync with production. Staging is also there to test changes in the >> sites L&F or HTML >> fixes. It is quite common that staging and production are out of sync. >> >> For that reason it is important that when you want to blog you base your >> work on top of >> production and not staging. Staging is just a convenient place to try >> changes to the site. >> A forced push is perfectly ok. >> >> Personally I always pull from production and create "blog" branches from >> this branch. >> Then when I want to preview the changes life, I do a forced push to the >> staging branch. >> If I am happy with the result I push to production. >> >> --Hardy >> >

Hi, > Do we have to rewrite the staging history to match production and force > push it? If you want staging to look like production, just push the production branch onto staging. $ git push -f origin production:staging --Hardy

The staging.hibernate.org should now work again, It was a problem of permissions, the owner of the folder with the site changed (not sure why) and the rsync script wasn't able to update it. Davide On Thu, Jan 14, 2016 at 1:15 PM, Vlad Mihalcea <mihalcea.vlad(a)gmail.com&gt; wrote: > Thanks. The two branches are now in-sync. > > Vlad > > On Thu, Jan 14, 2016 at 2:22 PM, Hardy Ferentschik <hardy(a)hibernate.org&gt; > wrote: > > > Hi, > > > > > Do we have to rewrite the staging history to match production and > force > > > push it? > > > > If you want staging to look like production, just push the production > > branch onto staging. > > > > $ git push -f origin production:staging > > > > --Hardy > > > > > _______________________________________________ > hibernate-dev mailing list > hibernate-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev >

you looking for something else than the different URLs?

you looking for something else than the different URLs?

Ok, what for?

Ok, what for?