[forge-dev] Forge Teamcity build linking

[Tomaz Cerar]

Hi,

I think this was intermittent issue that should be solved. I was doing some mentainence work on few build agents
Where I also dropped local maven cache. Not sure how this permission issue could have occurred.

Btw brontes now has local nexus mirror to speed up building on clean local repositories. 
You can configure to use it under maven build step settings. If not already configured.

--
tomaz

> -----Original Message-----
> From: Lincoln Baxter [mailto:lbaxter at redhat.com]
> Sent: Tuesday, December 10, 2013 8:05 PM
> To: Tomaz Cerar
> Cc: Forge Dev List
> Subject: Re: Forge Teamcity build linking
> 
> Thanks Tomaz,
> 
> We have another question.
> 
> We've started seeing this error. Any ideas what this is about?
> 
> http://brontes.lab.eng.brq.redhat.com/viewLog.html?buildId=6826&buildTy
> peId=Forge_FurnaceCdi_Linux&tab=buildLog#_focus=291
> 
> And a snippit for you:
> 
> 
> ------------------
> [13:38:57][org.jboss.forge.furnace.container:cdi] Downloaded:
> http://repo1.maven.org/maven2/org/jboss/jboss-parent/12/jboss-parent-
> 12.pom (0 B at 0.0 KB/sec)
> [13:38:57][org.jboss.forge.furnace.container:cdi] [main] WARN
> org.eclipse.aether.internal.impl.DefaultUpdateCheckManager - Failed to
> write tracking file /store/repository/org/jboss/jboss-parent/12/jboss-parent-
> 12.pom.lastUpdated
> [13:38:57][org.jboss.forge.furnace.container:cdi]
> java.io.FileNotFoundException: /store/repository/org/jboss/jboss-
> parent/12/jboss-parent-12.pom.lastUpdated (Permission denied)
> [13:38:57][org.jboss.forge.furnace.container:cdi] 	at
> java.io.RandomAccessFile.open(Native Method)
> [13:38:57][org.jboss.forge.furnace.container:cdi] 	at
> java.io.RandomAccessFile.<init>(RandomAccessFile.java:233)
> ------------------
> 
> 
> Thanks!
> 
> ----- Original Message -----
> From: "Tomaz Cerar" <tcerar at redhat.com>
> To: "Lincoln Baxter" <lbaxter at redhat.com>
> Sent: Monday, November 25, 2013 10:33:31 AM
> Subject: RE: Forge Teamcity build linking
> 
> Hey,
> 
> All you need to do is add dependencies under build configuration.
> 
> Ping me on IRC
> 
> --
> tomaz
> 
> > -----Original Message-----
> > From: Lincoln Baxter [mailto:lbaxter at redhat.com]
> > Sent: Friday, November 22, 2013 8:49 PM
> > To: Tomaz Cerar
> > Cc: George Gastaldi
> > Subject: Forge Teamcity build linking
> >
> > Hey Tomaz,
> >
> > I have a question about Teamcity. We are experiencing new build failures
> > (apparently due to the addition of a new build module "Furnace -
> Container
> > Simple").
> >
> > How can we link the builds so that the Core - 2.0 build has access to the
> build
> > result artifacts of this build, like you did with the Furnace Runtime and
> > Container CDI builds?
> >
> > I'm hoping we can learn enough to prevent the need for you to have to do
> > this for us again in the future.
> >
> > Thanks very much!
> >
> > --
> > Lincoln Baxter, III
> > JBoss, by Red Hat
> > lbaxter at redhat.com
> >
> > "If you want something, you'll find a way; if you don't, you'll find an
> excuse."