If you want to add a project that extends an other, you must add the parent project. When you add a project with sub-projects, Continuum will add all sub-projects, so you need to provide a URL instead of uploading a POM so that Continuum can find all sub-projects.
If your project has modules, you need to provide a URL instead of uploading a POM. When you add a project with modules, Continuum will add all sub-projects, and this only works by submitting a URL.
File protocol is disabled by default for security reasons. In Continuum 1.1, you can allow it in
$CONTINUUM_HOME/apps/continuum/webapp/WEB-INF/classes/META-INF/plexus/application.xml
File protocol is disabled by default for security reasons. In Continuum 1.2, you can allow it in
$CONTINUUM_HOME/apps/continuum/WEB-INF/classes/META-INF/plexus/application.xml
Uncomment the following line :
Jabber Host : talk.google.com
Jabber Port : 5222
Jabber Login : your google talk login without '@gmail.com'
Jabber Domain Name : gmail.com
Is it a SSL Connection? false
In the JNDI configuration, defined in your container for Continuum webapp and in $CONTINUUM_HOME/conf/jetty.xml for standalone version, you can use this parameters:
mvn.bat distributed with Maven 2.0.7 doesn't set correctly the exit code. You can use Maven 2.0.8 to fix it or directly a fixed mvn.bat file. The fixed version is available here.
Continuum uses the command line return code for detecting a successful or failed execution.
If you use ant, you need to add the following lines at the end of ant.bat
:
If your bat file contains an exit /B
at the end, this line must be inserted before it.
The code above is for ANT 1.7, you can download fixed scripts for older ANT here.
Continuum uses the command line return code for detecting a successful or failed execution.
You need to add the following lines at the end of script :
If your bat file contains an exit /B
at the end, this line must be inserted before it.
Port 8080 is used by the instance of Jetty that supplies the web interface for Continuum.
If you have another application already running on port 8080, you will get an exception when you start Continuum.
If you want to change the port that Continuum uses you should edit the file conf/jetty.xml
.
Find the following section in that file:
Change the appropriate <jetty.port>
element to the port number you want for jetty.
You need to restart Continuum for the changes to take effect.
Yes, just change the port as described in the above question.
IIRC, Continuum won't respect a change to the working directory for existing projects, it will still check them out in the old location. Until/unless this is fixed, be sure to make configuration changes before adding any projects, or delete them and re-add.
If you have a native CVS client installed, you can use it instead of the embedded java CVS client. You should add the following property in your startup script:
You're probably running the CVSNT client, or another application based on it, like TortoiseCVS. CVSNT stores passwords in the registry,
rather than the ~/.cvspass
file. You'll need to issue the following command manually (but only once), with the appropriate information filled in:
Also, note that the login will only be saved for the particular user who typed it. If you're running Continuum as a service, double-check the user
it is running as, and make sure that you run cvs login
as that user.
If you keep getting this build error on your projects:
Modify the SCM URL of your Continuum Project from something like this:
to something like this:
Please note the : before @servername. Save changes and try to build again, this time checkout should succeed.
You can learn more about SCM URLs here.
If you want to build recursively from the parent, you have to remove the --non-recursive
or -N
argument under the
"Build Definitions" section of your parent project. Or use the checkbox "For multi modules project, load only root as recursive build" when adding a m2 project.
Ensure that your entire project can be checked out using the SCM URL in your parent project.
For CVS users who have each child project in a separate module, you have several options:
If your SCM support hook scripts, you'll need to write an xml-rpc client for Continuum and call it in your post-commit script.