Parabuild from a local folder

[mayank]

Hi,

I know the intent of Parabuild is CI when its linked with a SCM, however for some specific requirements, I want to explore the possibility of being able to do a build using Parabuild for my Android code from a folder on my machine(no SCM taggings).

Can someone help me do this.

Regards,
Mayank

[support]

Mayank,

Parabuild provides a built-in pesudo-SCM called "Filesystem VCS". Select it from the VCS dropdown when creating a build. Parabuild will watch a local directory for changes. If files in that directory change, Parabuild will launch a build.

Is this what you are looking for?

Slava

[mayank]

Actually I am trying to configure Parabuld with Perforce, but facing issues like below:-

Product: Viewtier Parabuild 4.0.53 08 Nov 2010 21:40 14785 build 1884
Build name: abc_perforce
Severity: ERROR
Description: Error while reloading Perforce configuration: Command hung. It is possible that it is still running and affect subsequent commands: "C:\Program Files\Perforce\p4v.exe" -s -p localhost:1666 -u parag -P "parag" client -o //depot/mcl/...
Subsystem: Scheduling
Trace: java.lang.IllegalStateException: Error while reloading Perforce configuration: Command hung. It is possible
that it is still running and affect subsequent commands: "C:\Program Files\Perforce\p4v.exe" -s -p
localhost:1666 -u parag -P "parag" client -o //depot/mcl/...
at viewtier.autobuild.c.a.d.d(d.java:583)
at viewtier.autobuild.build.ic.i(ic.java:40)
at viewtier.autobuild.build.ic.run(ic.java:18)
Caused by: java.io.IOException: Command hung. It is possible that it is still running and affect subsequent
commands: "C:\Program Files\Perforce\p4v.exe" -s -p localhost:1666 -u parag -P "parag" client -o
//depot/mcl/...
at viewtier.autobuild.b.l.d(l.java:94)
at viewtier.autobuild.b.l.c(l.java:207)
at viewtier.autobuild.c.a.d.f(d.java:257)
at viewtier.autobuild.c.a.d.d(d.java:382)
... 2 more



Product: Viewtier Parabuild 4.0.53 08 Nov 2010 21:40 14785 build 1884
Build name: abc_perforce
Host name: <Build Manager>
Severity: FATAL
Description: Version control command hung
Details: Version control command ""C:\Program Files\Perforce\p4v.exe" -s 1666 -u parag client -o //depot/mcl/..." hung after 7200 seconds timeout. System attempted and failed to stop the command. System requires immediate attention of a build administrator. The command should be stopped manually.
Possible cause: Version control system has become unavailable or time out value is set too low.
Time: 07:14 PM 01/05/2011
Support forum: viewtier.parabuild.support

---------------------------------
So as an alternative I am looking at the possibility of building from a local folder just to test the build process through Parabuild as a start.

---Mayank

[support]

You need to enter C:\Program Files\Perforce\p4.exe in the Perforce exe path. Could you try that?

Slava

[parag]

i have tried with
C:\Program Files\Perforce\p4.exe also but didnt help.

[support]

[parag]

[support]