Picon
Favicon

Anthill Build regardless Question

How do I configure anthill to build regardless of no updates being made to the subversion repository on a timed schedule.

The way I have my setup is… Anthill checks out /mainfolder/build folder
And the actual build.xml has svnant commands that either checkout or update the repository
Problem is….on a timed schedule anthill will never do anything since the /mainfolder/build folder will rarely change

Please help

Thanks,
Josh

_______________________________________________
Anthill mailing list
Anthill@...
http://lists.urbancode.com/mailman/listinfo/anthill
Eric Minick | 7 Feb 07:14

Re: Anthill Build regardless Question

Josue,

AnthillOS doesn't handle this situation particularly well. It's really 
designed to be doing the interaction with your core project. You do have 
a couple options though.

1) Use a 'file system' repository. If your build script changes almost 
never, you could manually put that build script out to some location and 
just have AnthillOS run against that. The File System Repo doesn't 
detect changes, so it will always build.

2) Check in bogus changes. If your SVN tasks could also check in a bogus 
change to a scratch file in the /mainfolder/build path, Anthill would 
see those changes on the next build and react to them.

3) Grab the source, and change how schedules work. :)

AnthillPro handles this quite nicely and if we get some time to revisit 
AnthillOS, we might steal a feature from it and add a force build flag 
to schedules.

-- Eric

Claros, Josue (Mission Systems) wrote:

> How do I configure anthill to build regardless of no updates being 
> made to the subversion repository on a timed schedule.
>
> The way I have my setup is… Anthill checks out /mainfolder/build folder
> And the actual build.xml has svnant commands that either checkout or 
> update the repository
> Problem is….on a timed schedule anthill will never do anything since 
> the /mainfolder/build folder will rarely change
>
> Please help
>
> Thanks,
> Josh
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>  
>
Picon
Favicon

RE: Anthill Build regardless Question

Thanks Eric,

Can you explain how to do option number 3 in detail. 

Thanks,
Josh 

-----Original Message-----
From: anthill-bounces@...
[mailto:anthill-bounces@...] On Behalf Of Eric Minick
Sent: Tuesday, February 06, 2007 10:15 PM
To: Anthill user list
Subject: Re: [Anthill] Anthill Build regardless Question

Josue,

AnthillOS doesn't handle this situation particularly well. It's really
designed to be doing the interaction with your core project. You do have
a couple options though.

1) Use a 'file system' repository. If your build script changes almost
never, you could manually put that build script out to some location and
just have AnthillOS run against that. The File System Repo doesn't
detect changes, so it will always build.

2) Check in bogus changes. If your SVN tasks could also check in a bogus
change to a scratch file in the /mainfolder/build path, Anthill would
see those changes on the next build and react to them.

3) Grab the source, and change how schedules work. :)

AnthillPro handles this quite nicely and if we get some time to revisit
AnthillOS, we might steal a feature from it and add a force build flag
to schedules.

-- Eric

Claros, Josue (Mission Systems) wrote:

> How do I configure anthill to build regardless of no updates being 
> made to the subversion repository on a timed schedule.
>
> The way I have my setup is... Anthill checks out /mainfolder/build 
> folder And the actual build.xml has svnant commands that either 
> checkout or update the repository Problem is....on a timed schedule 
> anthill will never do anything since the /mainfolder/build folder will

> rarely change
>
> Please help
>
> Thanks,
> Josh
>
>-----------------------------------------------------------------------
>-
>
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>  
>

_______________________________________________
Anthill mailing list
Anthill@...
http://lists.urbancode.com/mailman/listinfo/anthill
Eric Minick | 7 Feb 18:54

Re: Anthill Build regardless Question

Fair question. I just realized that the how to get the source is a bit 
hard to find.

That page is here:
http://www.anthillpro.com/html/products/anthillos/for-developers.html

I can dig in to the code and point you in the right direction later this 
afternoon if you'd like (I've got to run to a meeting right now).

-- Eric

Claros, Josue (Mission Systems) wrote:

>Thanks Eric,
>
>Can you explain how to do option number 3 in detail. 
>
>Thanks,
>Josh 
>
>-----Original Message-----
>From: anthill-bounces@...
>[mailto:anthill-bounces@...] On Behalf Of Eric Minick
>Sent: Tuesday, February 06, 2007 10:15 PM
>To: Anthill user list
>Subject: Re: [Anthill] Anthill Build regardless Question
>
>Josue,
>
>AnthillOS doesn't handle this situation particularly well. It's really
>designed to be doing the interaction with your core project. You do have
>a couple options though.
>
>1) Use a 'file system' repository. If your build script changes almost
>never, you could manually put that build script out to some location and
>just have AnthillOS run against that. The File System Repo doesn't
>detect changes, so it will always build.
>
>2) Check in bogus changes. If your SVN tasks could also check in a bogus
>change to a scratch file in the /mainfolder/build path, Anthill would
>see those changes on the next build and react to them.
>
>3) Grab the source, and change how schedules work. :)
>
>AnthillPro handles this quite nicely and if we get some time to revisit
>AnthillOS, we might steal a feature from it and add a force build flag
>to schedules.
>
>-- Eric
>
>Claros, Josue (Mission Systems) wrote:
>
>  
>
>>How do I configure anthill to build regardless of no updates being 
>>made to the subversion repository on a timed schedule.
>>
>>The way I have my setup is... Anthill checks out /mainfolder/build 
>>folder And the actual build.xml has svnant commands that either 
>>checkout or update the repository Problem is....on a timed schedule 
>>anthill will never do anything since the /mainfolder/build folder will
>>    
>>
>
>  
>
>>rarely change
>>
>>Please help
>>
>>Thanks,
>>Josh
>>
>>-----------------------------------------------------------------------
>>-
>>
>>_______________________________________________
>>Anthill mailing list
>>Anthill@...
>>http://lists.urbancode.com/mailman/listinfo/anthill
>> 
>>
>>    
>>
>
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>  
>
Picon
Favicon

RE: Anthill Build regardless Question

Thanks Eric,

Yes I would like for you to point me in the right direction when you
have the time thank you very much.
By the way...i was under the impression that I could modify the way
anthillos works by modifying 
The pagelets under /conf/profiles/Unix/unix_subversion ...guess theres
more to it than I thought.
I originally wanted anthillOS to do an update instead of a checkout if
there was an existing repository because my svn repository is almost
half a gig...so every time I build it takes over 2 hours to complete
because it always checks out a fresh copy of the repository.
My solution was to checkout the build folder and use svnant commands
within my build script...and now I have this problem.

Anyway your help would be greatly appreciated 
Thanks,
Josh

-----Original Message-----
From: anthill-bounces@...
[mailto:anthill-bounces@...] On Behalf Of Eric Minick
Sent: Wednesday, February 07, 2007 9:55 AM
To: Anthill user list
Subject: Re: [Anthill] Anthill Build regardless Question

Fair question. I just realized that the how to get the source is a bit
hard to find.

That page is here:
http://www.anthillpro.com/html/products/anthillos/for-developers.html

I can dig in to the code and point you in the right direction later this
afternoon if you'd like (I've got to run to a meeting right now).

-- Eric

Claros, Josue (Mission Systems) wrote:

>Thanks Eric,
>
>Can you explain how to do option number 3 in detail. 
>
>Thanks,
>Josh
>
>-----Original Message-----
>From: anthill-bounces@...
>[mailto:anthill-bounces@...] On Behalf Of Eric Minick
>Sent: Tuesday, February 06, 2007 10:15 PM
>To: Anthill user list
>Subject: Re: [Anthill] Anthill Build regardless Question
>
>Josue,
>
>AnthillOS doesn't handle this situation particularly well. It's really 
>designed to be doing the interaction with your core project. You do 
>have a couple options though.
>
>1) Use a 'file system' repository. If your build script changes almost 
>never, you could manually put that build script out to some location 
>and just have AnthillOS run against that. The File System Repo doesn't 
>detect changes, so it will always build.
>
>2) Check in bogus changes. If your SVN tasks could also check in a 
>bogus change to a scratch file in the /mainfolder/build path, Anthill 
>would see those changes on the next build and react to them.
>
>3) Grab the source, and change how schedules work. :)
>
>AnthillPro handles this quite nicely and if we get some time to revisit

>AnthillOS, we might steal a feature from it and add a force build flag 
>to schedules.
>
>-- Eric
>
>Claros, Josue (Mission Systems) wrote:
>
>  
>
>>How do I configure anthill to build regardless of no updates being 
>>made to the subversion repository on a timed schedule.
>>
>>The way I have my setup is... Anthill checks out /mainfolder/build 
>>folder And the actual build.xml has svnant commands that either 
>>checkout or update the repository Problem is....on a timed schedule 
>>anthill will never do anything since the /mainfolder/build folder will
>>    
>>
>
>  
>
>>rarely change
>>
>>Please help
>>
>>Thanks,
>>Josh
>>
>>----------------------------------------------------------------------
>>-
>>-
>>
>>_______________________________________________
>>Anthill mailing list
>>Anthill@...
>>http://lists.urbancode.com/mailman/listinfo/anthill
>> 
>>
>>    
>>
>
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>  
>

_______________________________________________
Anthill mailing list
Anthill@...
http://lists.urbancode.com/mailman/listinfo/anthill
Eric Minick | 7 Feb 20:06

Re: Anthill Build regardless Question

Josh,

The pagelets can be modified to alter the commands used to interact with 
subversion. The problem is more subtle. After the command to retrieve a 
change log is issued, no changes are detected by the part of the system 
that does the parsing.

With no changes the build system decides a build is not required and 
moves on to the next request in the queue. If you hacked the get 
changelog pagelet to get a wider set of changes, that might work but I 
think we filter out changes prior to build time because subversion tends 
to return too much information in change logs.

As for code changes, I would look at two approaches:
1) Change com.urbancode.anthill.BuildManager.*requiresBuild()* to always 
require the build.
2 )Change AnthillSchedule.run() to set the force build flag on its new 
build defnition. That would require putting a build definition on the 
build queue rather than just the project. For an example of that, see 
com.urbancode.anthill.web.admin.BuildProjectStepTwoServlet. This could 
be expanded to make that optional with a UI widget if you wanted to 
contribute it back.

There could be other options or more complications, but that's what I 
see after taking a quick look.

-- Eric

Claros, Josue (Mission Systems) wrote:

>Thanks Eric,
>
>Yes I would like for you to point me in the right direction when you
>have the time thank you very much.
>By the way...i was under the impression that I could modify the way
>anthillos works by modifying 
>The pagelets under /conf/profiles/Unix/unix_subversion ...guess theres
>more to it than I thought.
>I originally wanted anthillOS to do an update instead of a checkout if
>there was an existing repository because my svn repository is almost
>half a gig...so every time I build it takes over 2 hours to complete
>because it always checks out a fresh copy of the repository.
>My solution was to checkout the build folder and use svnant commands
>within my build script...and now I have this problem.
>
>Anyway your help would be greatly appreciated 
>Thanks,
>Josh
> 
>
>-----Original Message-----
>From: anthill-bounces@...
>[mailto:anthill-bounces@...] On Behalf Of Eric Minick
>Sent: Wednesday, February 07, 2007 9:55 AM
>To: Anthill user list
>Subject: Re: [Anthill] Anthill Build regardless Question
>
>Fair question. I just realized that the how to get the source is a bit
>hard to find.
>
>That page is here:
>http://www.anthillpro.com/html/products/anthillos/for-developers.html
>
>I can dig in to the code and point you in the right direction later this
>afternoon if you'd like (I've got to run to a meeting right now).
>
>-- Eric
>
>
>Claros, Josue (Mission Systems) wrote:
>
>  
>
>>Thanks Eric,
>>
>>Can you explain how to do option number 3 in detail. 
>>
>>Thanks,
>>Josh
>>
>>-----Original Message-----
>>From: anthill-bounces@...
>>[mailto:anthill-bounces@...] On Behalf Of Eric Minick
>>Sent: Tuesday, February 06, 2007 10:15 PM
>>To: Anthill user list
>>Subject: Re: [Anthill] Anthill Build regardless Question
>>
>>Josue,
>>
>>AnthillOS doesn't handle this situation particularly well. It's really 
>>designed to be doing the interaction with your core project. You do 
>>have a couple options though.
>>
>>1) Use a 'file system' repository. If your build script changes almost 
>>never, you could manually put that build script out to some location 
>>and just have AnthillOS run against that. The File System Repo doesn't 
>>detect changes, so it will always build.
>>
>>2) Check in bogus changes. If your SVN tasks could also check in a 
>>bogus change to a scratch file in the /mainfolder/build path, Anthill 
>>would see those changes on the next build and react to them.
>>
>>3) Grab the source, and change how schedules work. :)
>>
>>AnthillPro handles this quite nicely and if we get some time to revisit
>>    
>>
>
>  
>
>>AnthillOS, we might steal a feature from it and add a force build flag 
>>to schedules.
>>
>>-- Eric
>>
>>Claros, Josue (Mission Systems) wrote:
>>
>> 
>>
>>    
>>
>>>How do I configure anthill to build regardless of no updates being 
>>>made to the subversion repository on a timed schedule.
>>>
>>>The way I have my setup is... Anthill checks out /mainfolder/build 
>>>folder And the actual build.xml has svnant commands that either 
>>>checkout or update the repository Problem is....on a timed schedule 
>>>anthill will never do anything since the /mainfolder/build folder will
>>>   
>>>
>>>      
>>>
>> 
>>
>>    
>>
>>>rarely change
>>>
>>>Please help
>>>
>>>Thanks,
>>>Josh
>>>
>>>----------------------------------------------------------------------
>>>-
>>>-
>>>
>>>_______________________________________________
>>>Anthill mailing list
>>>Anthill@...
>>>http://lists.urbancode.com/mailman/listinfo/anthill
>>>
>>>
>>>   
>>>
>>>      
>>>
>>_______________________________________________
>>Anthill mailing list
>>Anthill@...
>>http://lists.urbancode.com/mailman/listinfo/anthill
>>_______________________________________________
>>Anthill mailing list
>>Anthill@...
>>http://lists.urbancode.com/mailman/listinfo/anthill
>> 
>>
>>    
>>
>
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>  
>
Kuruba, Mahesh | 18 Feb 15:53

Anthill OS - PVCSRepositoryAdapter - FAILED to get revision list.

Hi,
 
I'm using Anthill OS and have setup Anthill to automate the build process by getting the source from a PVCS repository.
The configuration seem to be able to get the source from PVCS and do the build. But it seem to be failing at the point of incrementing the build number with the following error. Appreciate if you can let me know how to fix this.
 
Thanks,
Mahesh
 
 
Anthill version 1.8.1.303
 
Retrieving project files: OK
FAILED to get revision list.  Message: PVCSRepositoryAdapter: Error executing: cmd /x/c cd /d "C:\MyInstall\anthill-1.8.1.303\work\MyProject" &&  pcli run -s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli" "Q:\My_Project\My_Project_source" ""
.  Exit Code: -1
Incrementing version: FAILED to build project.  Message: ProfileAdapter prepareForEdit failed: -13 FAILED to get revision list.  Message: PVCSRepositoryAdapter: Error executing: cmd /x/c cd /d "C:\MyInstall\anthill-1.8.1.303\work\MyProject" &&  pcli run -s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli" "Q:\My_Project\My_Project_source" ""
.  Exit Code: -1
 
-------------------------------------
C:\MyInstall\anthill-1.8.1.303\publishDir\MyProject\buildLogs\MyProject-null-build.log
 
 
st1\:* { BEHAVIOR: url(#ieooui) } <at> font-face { font-family: Book Antiqua; } <at> page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; } st1\:* { BEHAVIOR: url(#ieooui) } st1\:* { BEHAVIOR: url(#ieooui) } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline; text-underline: single } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline; text-underline: single } A:visited { COLOR: blue; TEXT-DECORATION: underline; text-underline: single } SPAN.MsoHyperlinkFollowed { COLOR: blue; TEXT-DECORATION: underline; text-underline: single } SPAN.SpellE { mso-style-name: ""; mso-spl-e: yes } DIV.Section1 { page: Section1 }

 

Mahesh Kuruba

                  Associate

 

 

 

Booz Allen Hamilton Inc.

12345 Parklawn Drive

Rockville, MD20852
Tel (301) 255-2732
Fax (301) 255-2755

kuruba_mahesh-Tu/zuyJGTcU@public.gmane.org

 

 

 

Booz | Allen | Hamilton

 

 

 

 

 
Attachment (Kuruba, Mahesh.vcf): text/x-vcard, 442 bytes
Attachment (smime.p7s): application/x-pkcs7-signature, 4491 bytes
_______________________________________________
Anthill mailing list
Anthill@...
http://lists.urbancode.com/mailman/listinfo/anthill
Andy Levy | 19 Feb 17:56
Picon

Re: Variables replacement

On 2/19/07, Kris Wolff <k.wolff@...> wrote:
> ok, i understand this.
> what i can't find in the more than 300 pages is, how will transfer svn
> the file properties? Or better: when i set the properties, why the next
> man in the team have them, too? Will transfer svn more than just the
> plain textfile? Tehre must be a properties, or setting file, or?

Please remember to use Reply To All so discussion stays on the list.

Once you set a property on a file managed by Subversion, that property
is part of the metadata about the file which Subversion tracks. Once
you've set the property, anyone checking the file(s) out will see it
attached to the file, and it will remain set until someone deletes or
changes the property.

Please read the portion of the manual which I linked earlier.

> Andy Levy schrieb:
> > On 2/19/07, Kris Wolff <k.wolff@...> wrote:
> >> and.... hm is this a client issue? What happens when a college updated a
> >> file?
> >> The man dosn't spend much light on the "new" thing.... or do i think too
> >> much in cvs?
> >
> > Once a property is set on a file, it's there until someone removes it.
> > New files, when added, will need to have it set. This can be automated
> > using auto-props (again, see the manual), but it's purely a
> > client-side setting - to enforce the setting of properties on the
> > server, you'll need a pre-commit hook to check  them and reject the
> > commit if they're missing.
> >
> >> Kris Wolff schrieb:
> >> > Hi Andy,
> >> >
> >> > thanx for your reply, i fount the property settings and get this
> >> > working for one file. Can i do this on everyfile? so called globaly?
> >> > or do i have to register the properties for every single file in the
> >> > trunk? *bigrollingeyes*
> >> >
> >> > Thanks,
> >> > Kris
> >> >
> >> > Andy Levy schrieb:
> >> >> On 2/19/07, Kris Wolff <k.wolff@...> wrote:
> >> >>> Hi List,
> >> >>>
> >> >>> i am very new to svn, comming from good old cvs. I am testing our
> >> >>> server
> >> >>> and stuck with a very tiny, maby (for you) easy beginners question.
> >> >>>
> >> >>> I have a Head in my source, looks like:
> >> >>> <?
> >> >>> // $Id$
> >> >>> // $Revision$
> >> >>> // $Author$
> >> >>> // $Date$
> >> >>> // $HeadURL
> >> >>>
> >> >>> echo("test");
> >> >>> ?>
> >> >>>
> >> >>> but as i checked in, the variables will  not replaced? why? is it a
> >> >>> server issue? Howe can i fix?
> >> >>
> >> >> Keyword replacement is only performed on files which have the
> >> >> appropriate values set in the svn:keywords property. See
> >> >>
> >> http://svnbook.red-bean.com/nightly/en/svn.advanced.props.special.keywords.html
> >>
> >> >>
> >> >
> >>
> >> --
> >> Kris Wolff
> >> wdv New Media
> >> Online-Technik
> >>
> >> wdv Gesellschaft für Medien &
> >> Kommunikation mbH & Co. OHG
> >> Siemensstr. 6
> >> D-61352 Bad Homburg v.d.H.
> >>
> >> Telefon: 06172 - 670 451
> >> Telefax: 06172 - 670 172
> >> mailto: k.wolff@...
> >> www.wdv-newmedia.de
> >>
> >>
> >> ---
> >> wdv Gesellschaft fuer Medien & Kommunikation mbH & Co. OHG,
> >> Bad Homburg v.d.H., AG. Bad Homburg HRA 3087
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@...
> >> For additional commands, e-mail: users-help@...
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@...
> > For additional commands, e-mail: users-help@...
> >
>
> --
> Kris Wolff
> wdv New Media
> Online-Technik
>
> wdv Gesellschaft für Medien &
> Kommunikation mbH & Co. OHG
> Siemensstr. 6
> D-61352 Bad Homburg v.d.H.
>
> Telefon: 06172 - 670 451
> Telefax: 06172 - 670 172
> mailto: k.wolff@...
> www.wdv-newmedia.de
>
>
> ---
> wdv Gesellschaft fuer Medien & Kommunikation mbH & Co. OHG,
> Bad Homburg v.d.H., AG. Bad Homburg HRA 3087
>
>
Eric Minick | 20 Feb 01:00

Re: Anthill OS - PVCSRepositoryAdapter - FAILED to get revision list.

Mahesh,

I'm not sure what's going wrong here, perhaps it would be easier to 
switch to using the 
com.urbancode.anthill.adapter.ProjectPropertyFileVersionAdapter . That 
stores the version number in Anthill and would avoid these steps.

Would that work for you?

-- Eric

Kuruba, Mahesh wrote:

> Hi,
>  
> I'm using Anthill OS and have setup Anthill to automate the build 
> process by getting the source from a PVCS repository.
> The configuration seem to be able to get the source from PVCS and do 
> the build. But it seem to be failing at the point of incrementing the 
> build number with the following error. Appreciate if you can let me 
> know how to fix this.
>  
> Thanks,
> Mahesh
>  
> ------------------------------------------------------------------------
>  
> Anthill version 1.8.1.303
>  
> Retrieving project files: OK
> FAILED to get revision list.  Message: PVCSRepositoryAdapter: Error 
> executing: cmd /x/c cd /d 
> "C:\MyInstall\anthill-1.8.1.303\work\MyProject" &&  pcli run 
> -s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli" 
> "Q:\My_Project\My_Project_source" ""
> .  Exit Code: -1
> Incrementing version: FAILED to build project.  Message: 
> ProfileAdapter prepareForEdit failed: -13 FAILED to get revision 
> list.  Message: PVCSRepositoryAdapter: Error executing: cmd /x/c cd /d 
> "C:\MyInstall\anthill-1.8.1.303\work\MyProject" &&  pcli run 
> -s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli" 
> "Q:\My_Project\My_Project_source" ""
> .  Exit Code: -1
>  
> -------------------------------------
> C:\MyInstall\anthill-1.8.1.303\publishDir\MyProject\buildLogs\MyProject-null-build.log
> ------------------------------------------------------------------------
>  
>  
>
>  
>
> Mahesh Kuruba
>
>                   Associate
>
>  
>
>  
>
>  
>
> Booz Allen Hamilton Inc.
>
> 12345 Parklawn Drive
>
> Rockville, MD 20852
> Tel (301) 255-2732
> Fax (301) 255-2755
> kuruba_mahesh@... <mailto:kuruba_mahesh@...>
>
> 	
>
>  
>
>  
>
>  
>
> Booz | Allen | Hamilton <http://www.bah.com/>
>
> ------------------------------------------------------------------------
>
>  
>
>  
>
>  
>
>  
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>  
>
Kuruba, Mahesh | 21 Feb 01:37

Re: Anthill OS - PVCSRepositoryAdapter - FAILED to get revision list.

Eric,

Thanks for the reply.

The Anthill document recommended to use the UrbanCodeVersionAdapter vs.
ProjectPropertyFileVersionAdapter and so I configured accordingly.

But I followed your suggestion and switched to use
ProjectPropertyFileVersionAdapter.
Now I get the  following new error.

AS an fyi, PVCSRepositoryAdapter is configured as follows -

 ---------------------------------------------------------------------- 
|repository.pvcs.work.dir    |  work/myproject                          |
|repository.pvcs.projectDir  |  Q:\My_Project\my_project_source         |
|repository.pvcs.project     |  <blank>                                 |
|repository.pvcs.archiveDir  |  Q:\My_Project\my_project_source\archives|
|repository.pvcs.branch      |  <blank>                                 |
|repository.pvcs.dateFormat  | MMM dd yyyy HH:mm:ss                     |
 -----------------------------------------------------------------------

Any ideas?

Thanks,
Mahesh

================== Tomcat console content =================================
19:01:35:640 [Thread - AnthillBuildDaemon] INFO
com.urbancode.anthill.BuildManager  - step 2) is project up to date?
19:01:38:109 [Thread - AnthillBuildDaemon] INFO
com.urbancode.anthill.adapter.PVCSRepositoryAdapter  - getRevisionsSince
script command: cmd /x/c cd /d
"C:\MyInstall\anthill-1.8.1.303\work\myproject" &&
 pcli run
-s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli
" "Q:\My_Project\my_project_source" ""

19:01:38:140 [Thread - AnthillBuildDaemon] ERROR
com.urbancode.anthill.BuildManager  - PVCSRepositoryAdapter: Error
executing: cmd /x/c cd /d "C:\MyInstall\anthill-1.8.1.303\work\myproject" &&
 pcli run
-s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli
" "Q:\My_Project\my_project_source" ""
.  Exit Code: -1
com.urbancode.anthill.adapter.RepositoryException: PVCSRepositoryAdapter:
Error executing: cmd /x/c cd /d
"C:\MyInstall\anthill-1.8.1.303\work\myproject" &&
 pcli run
-s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli
" "Q:\My_Project\my_project_source" ""
.  Exit Code: -1
        at
com.urbancode.anthill.adapter.PVCSRepositoryAdapter.getRevisionsSince(PVCSRe
positoryAdapter.java:261)
        at
com.urbancode.anthill.BuildManager.requiresBuild(BuildManager.java:343)
        at com.urbancode.anthill.BuildManager.build(BuildManager.java:109)
        at
com.urbancode.anthill.AnthillProject.releaseProject(AnthillProject.java:231)
        at
com.urbancode.anthill.AnthillProject.releaseProject(AnthillProject.java:217)
        at
com.urbancode.anthill.AnthillProject.releaseProject(AnthillProject.java:195)
        at com.urbancode.anthill.AnthillProject.run(AnthillProject.java:187)
        at com.urbancode.anthill.BuildDaemon.run(BuildDaemon.java:73)
19:01:38:187 [Thread - AnthillBuildDaemon] INFO
com.urbancode.anthill.BuildManager  - step 3) Increment version:
19:01:38:187 [Thread - AnthillBuildDaemon] INFO
com.urbancode.anthill.adapter.ProjectPropertyFileVersionAdapter  - Branch
from the reposito
ry adapter:
19:01:38:187 [Thread - AnthillBuildDaemon] INFO
com.urbancode.anthill.adapter.ProjectPropertyFileVersionAdapter  -
Incrementing version: nu
ll
19:01:38:203 [Thread - AnthillBuildDaemon] ERROR
com.urbancode.anthill.BuildManager  -
java.lang.NullPointerException
        at
com.urbancode.anthill.adapter.ProjectPropertyFileVersionAdapter.incrementVer
sion(ProjectPropertyFileVersionAdapter.java:94)
        at com.urbancode.anthill.BuildManager.build(BuildManager.java:115)
        at
com.urbancode.anthill.AnthillProject.releaseProject(AnthillProject.java:231)
        at
com.urbancode.anthill.AnthillProject.releaseProject(AnthillProject.java:217)
        at
com.urbancode.anthill.AnthillProject.releaseProject(AnthillProject.java:195)
        at com.urbancode.anthill.AnthillProject.run(AnthillProject.java:187)
        at com.urbancode.anthill.BuildDaemon.run(BuildDaemon.java:73)

============================================================================
=============== Email Notification content ================================
Anthill version 1.8.1.303

Retrieving project files: OK
FAILED to get revision list.  Message: PVCSRepositoryAdapter: Error executing:
cmd /x/c cd /d "C:\MyInstall\anthill-1.8.1.303\work\myproject" &&  pcli
run -s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pc
li" "Q:\My_Project\my_project_source" ""
.  Exit Code: -1
Incrementing version: FAILED to build project.  Message: null
============================================================================

-----Original Message-----
From: anthill-bounces@...
[mailto:anthill-bounces@...] On Behalf Of
anthill-request@...
Sent: Tuesday, February 20, 2007 1:04 PM
To: anthill@...
Subject: Anthill Digest, Vol 37, Issue 6

Send Anthill mailing list submissions to
	anthill@...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.urbancode.com/mailman/listinfo/anthill
or, via email, send a message with subject or body 'help' to
	anthill-request@...

You can reach the person managing the list at
	anthill-owner@...

When replying, please edit your Subject line so it is more specific than
"Re: Contents of Anthill digest..."

Today's Topics:

   1. Re: Anthill OS - PVCSRepositoryAdapter - FAILED to get
      revision list. (Eric Minick)

----------------------------------------------------------------------

Message: 1
Date: Mon, 19 Feb 2007 17:00:45 -0700
From: Eric Minick <etm@...>
Subject: Re: [Anthill] Anthill OS - PVCSRepositoryAdapter - FAILED to
	get	revision list.
To: Anthill user list <anthill@...>
Message-ID: <45DA3A2D.3080103@...>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Mahesh,

I'm not sure what's going wrong here, perhaps it would be easier to switch
to using the com.urbancode.anthill.adapter.ProjectPropertyFileVersionAdapter
. That stores the version number in Anthill and would avoid these steps.

Would that work for you?

-- Eric

Kuruba, Mahesh wrote:

> Hi,
>
> I'm using Anthill OS and have setup Anthill to automate the build
> process by getting the source from a PVCS repository.
> The configuration seem to be able to get the source from PVCS and do
> the build. But it seem to be failing at the point of incrementing the
> build number with the following error. Appreciate if you can let me
> know how to fix this.
>
> Thanks,
> Mahesh
>
> ----------------------------------------------------------------------
> --
>
> Anthill version 1.8.1.303
>
> Retrieving project files: OK
> FAILED to get revision list.  Message: PVCSRepositoryAdapter: Error
> executing: cmd /x/c cd /d
> "C:\MyInstall\anthill-1.8.1.303\work\MyProject" &&  pcli run
>
-s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli
"
> "Q:\My_Project\My_Project_source" ""
> .  Exit Code: -1
> Incrementing version: FAILED to build project.  Message:
> ProfileAdapter prepareForEdit failed: -13 FAILED to get revision list.
> Message: PVCSRepositoryAdapter: Error executing: cmd /x/c cd /d
> "C:\MyInstall\anthill-1.8.1.303\work\MyProject" &&  pcli run
>
-s"C:\MyInstall\anthill-1.8.1.303\conf\profiles\Win32\win_pvcs\myscript.pcli
"
> "Q:\My_Project\My_Project_source" ""
> .  Exit Code: -1
>
> -------------------------------------
> C:\MyInstall\anthill-1.8.1.303\publishDir\MyProject\buildLogs\MyProjec
> t-null-build.log
> ----------------------------------------------------------------------
> --
>
>
>
>
>
>
>
>
>
> ----------------------------------------------------------------------
> --
>
>
>
>
>
>
>
>
>
>
>
>-----------------------------------------------------------------------
>-
>
>_______________________________________________
>Anthill mailing list
>Anthill@...
>http://lists.urbancode.com/mailman/listinfo/anthill
>
>

------------------------------

_______________________________________________
Anthill mailing list
Anthill@...
http://lists.urbancode.com/mailman/listinfo/anthill

End of Anthill Digest, Vol 37, Issue 6
**************************************
Attachment (smime.p7s): application/x-pkcs7-signature, 4491 bytes
_______________________________________________
Anthill mailing list
Anthill@...
http://lists.urbancode.com/mailman/listinfo/anthill

Gmane