From: Brian P. <bs...@pr...> - 2015-07-27 17:47:12
|
Hi Trey, It looks like TC is understandably confused by the loss of history at SF, apparently r8663-8698 went *poof*. Not sure exactly what action needs to be taken for TC to handle this, but can you please look into ti? Thanks, Brian Pratt |
From: Brendan M. <bre...@pr...> - 2015-07-27 18:22:53
|
I think we need fresh checkouts on the TeamCity clients, as I explained to Josh and Trey last night. Subversion gives an error when your local source has a revision index ahead of what is available in the project on the server. On Mon, Jul 27, 2015 at 10:47 AM, Brian Pratt <bs...@pr...> wrote: > Hi Trey, > > It looks like TC is understandably confused by the loss of history at SF, > apparently r8663-8698 went *poof*. > > Not sure exactly what action needs to be taken for TC to handle this, but > can you please look into ti? > > Thanks, > > Brian Pratt > |
From: Chambers, M. <mat...@gm...> - 2015-07-27 18:27:28
|
Shouldn't every checkout be a fresh checkout with EC2 agents that have just spun up? Unless the image was created with a checkout already made (which might be a reasonable way to speed up CI, but the image would have to be incrementally updated to the latest revision). I manually started a Linux build to test. -Matt On 7/27/2015 12:55 PM, Brendan MacLean wrote: > I think we need fresh checkouts on the TeamCity clients, as I > explained to Josh and Trey last night. Subversion gives an error when > your local source has a revision index ahead of what is available in > the project on the server. > > On Mon, Jul 27, 2015 at 10:47 AM, Brian Pratt <bs...@pr... > <mailto:bs...@pr...>> wrote: > > Hi Trey, > > It looks like TC is understandably confused by the loss of history > at SF, apparently r8663-8698 went *poof*. > > Not sure exactly what action needs to be taken for TC to handle > this, but can you please look into ti? > > Thanks, > > Brian Pratt > > |
From: Chambers, M. <mat...@gm...> - 2015-07-27 18:32:41
|
Nevermind, apparently this metadata is being cached on the TeamCity server (at the VCS root level, which I don't have permission to edit it seems). On 7/27/2015 12:55 PM, Brendan MacLean wrote: > I think we need fresh checkouts on the TeamCity clients, as I > explained to Josh and Trey last night. Subversion gives an error when > your local source has a revision index ahead of what is available in > the project on the server. > > On Mon, Jul 27, 2015 at 10:47 AM, Brian Pratt <bs...@pr... > <mailto:bs...@pr...>> wrote: > > Hi Trey, > > It looks like TC is understandably confused by the loss of history > at SF, apparently r8663-8698 went *poof*. > > Not sure exactly what action needs to be taken for TC to handle > this, but can you please look into ti? > > Thanks, > > Brian Pratt > > |
From: Trey C. <tc...@la...> - 2015-07-27 18:35:59
|
The Proteowizard agents are all launched on-demand from AWS. They get a fresh checkout every time a new agent is started up. The problem here is that TeamCity is trying to fetch a changelist comparing the last revision it knew about (8698) to the latest revision that actually exists (8690). I haven't been able to find any TeamCity documentation on how to resolve this state. If we make a bunch of dummy commits to bump the revision number, TeamCity might start working. I can open a bug to JetBrains, but that doesn't help us much right now. On Mon, Jul 27, 2015 at 10:55 AM, Brendan MacLean <bre...@pr...> wrote: > I think we need fresh checkouts on the TeamCity clients, as I explained to > Josh and Trey last night. Subversion gives an error when your local source > has a revision index ahead of what is available in the project on the > server. > > On Mon, Jul 27, 2015 at 10:47 AM, Brian Pratt <bs...@pr...> > wrote: > >> Hi Trey, >> >> It looks like TC is understandably confused by the loss of history at SF, >> apparently r8663-8698 went *poof*. >> >> Not sure exactly what action needs to be taken for TC to handle this, but >> can you please look into ti? >> >> Thanks, >> >> Brian Pratt >> > > -- Trey Chadick (LabKey Software) tc...@la... 206.489.2577 |
From: Chambers, M. <mat...@gm...> - 2015-07-27 18:37:52
|
Can you reset the VCS roots to clear the metadata? -Matt On 7/27/2015 1:35 PM, Trey Chadick wrote: > The Proteowizard agents are all launched on-demand from AWS. They get > a fresh checkout every time a new agent is started up. > The problem here is that TeamCity is trying to fetch a changelist > comparing the last revision it knew about (8698) to the latest > revision that actually exists (8690). > I haven't been able to find any TeamCity documentation on how to > resolve this state. If we make a bunch of dummy commits to bump the > revision number, TeamCity might start working. > I can open a bug to JetBrains, but that doesn't help us much right now. > > On Mon, Jul 27, 2015 at 10:55 AM, Brendan MacLean > <bre...@pr... <mailto:bre...@pr...>> wrote: > > I think we need fresh checkouts on the TeamCity clients, as I > explained to Josh and Trey last night. Subversion gives an error > when your local source has a revision index ahead of what is > available in the project on the server. > > On Mon, Jul 27, 2015 at 10:47 AM, Brian Pratt > <bs...@pr... <mailto:bs...@pr...>> wrote: > > Hi Trey, > > It looks like TC is understandably confused by the loss of > history at SF, apparently r8663-8698 went *poof*. > > Not sure exactly what action needs to be taken for TC to > handle this, but can you please look into ti? > > Thanks, > > Brian Pratt > > > > > > -- > Trey Chadick (LabKey Software) > tc...@la... <mailto:tc...@la...> > 206.489.2577 |
From: Trey C. <tc...@la...> - 2015-07-27 22:07:40
|
Not sure how to clear the cache, but I copied the VCS roots and that seemed to do the trick. On Mon, Jul 27, 2015 at 11:37 AM, Chambers, Matthew < mat...@gm...> wrote: > Can you reset the VCS roots to clear the metadata? > > -Matt > > > On 7/27/2015 1:35 PM, Trey Chadick wrote: > > The Proteowizard agents are all launched on-demand from AWS. They get a > fresh checkout every time a new agent is started up. > The problem here is that TeamCity is trying to fetch a changelist > comparing the last revision it knew about (8698) to the latest revision > that actually exists (8690). > I haven't been able to find any TeamCity documentation on how to resolve > this state. If we make a bunch of dummy commits to bump the revision > number, TeamCity might start working. > I can open a bug to JetBrains, but that doesn't help us much right now. > > On Mon, Jul 27, 2015 at 10:55 AM, Brendan MacLean <bre...@pr...> > wrote: > >> I think we need fresh checkouts on the TeamCity clients, as I explained >> to Josh and Trey last night. Subversion gives an error when your local >> source has a revision index ahead of what is available in the project on >> the server. >> >> On Mon, Jul 27, 2015 at 10:47 AM, Brian Pratt < <bs...@pr...> >> bs...@pr...> wrote: >> >>> Hi Trey, >>> >>> It looks like TC is understandably confused by the loss of history at >>> SF, apparently r8663-8698 went *poof*. >>> >>> Not sure exactly what action needs to be taken for TC to handle this, >>> but can you please look into ti? >>> >>> Thanks, >>> >>> Brian Pratt >>> >> >> > > > -- > Trey Chadick (LabKey Software) > tc...@la... > 206.489.2577 > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > proteowizard-developer mailing list > pro...@li... > https://lists.sourceforge.net/lists/listinfo/proteowizard-developer > > -- Trey Chadick (LabKey Software) tc...@la... 206.489.2577 |