What tools are included with ToolsCloud?
See the complete list of tools.
Can I keep using my current IDE or do I need to switch?
You can use any existing IDE, so your developers can start using ToolsCloud right away.
If I cancel my ToolsCloud subscription, do I lose my data?
No, your data is yours. If you cancel your subscription, your data will be available for you to download for 30 days. Since ToolsCloud is based entirely on open source tools, you can take your data with you.
Will additional ToolsCloud customers make my environment slow?
No. Each ToolsCloud customer has its own isolated and exclusive environment, like having your own server. There is also no sharing of data disks, so no risk of another customer accessing to your information.
Can I run ToolsCloud in my own private cloud?
Yes! Contact us and we’ll be happy to go over your requirements and create a solution that works for you.
What if one of my builds crashes the environment?
Using ToolsCloud Manager you can manage your app servers and configure their needed memory consumption. You can restart the app server if anything goes wrong.
Do I have shell access?
No. To preserve your environment, admin tasks are done by ToolsCloud. You have full access to the tools, but no shell access to the environment.
Can I install other tools, or choose a different toolset?
No. The environment is provided as a standard configuration which has been tried and tested by the ToolsCloud team. If you need a specific configuration, talk to us and we can discuss your project.
Can I run Windows-specific builds on Jenkins?
If you need a Windows build environment, contact us and we can discuss configuring one for you. The ToolsCloud environment runs on Linux, which means you can’t run Windows-specific build tasks by default. The rest of the environment (Subversion, Git, Sonar, Nexus, Redmine) can be used to save and track Windows specific source code and libraries.
I already have a Subversion repository. Can I import its history to the ToolsCloud environment?
Yes. See here how to do that.
How to can I pass my GIT user and password to Hudson?
While bug HUDSON-3807 is not fixed, there is no way to specify a user name and a password to your GIT repository if you are accessing GIT via https from Hudson. However, there are a few workarounds that you can do. A simple workaround is to define an environment variable with the user name and password that you want to passs to GIT. For example:
After that, use this variable in the GIT repository URL that you will inform in your Hudson build, as in this example:
You can define this environment variable in Hudson: go to Hudson/Manage Hudson/Configure System. In Global Properties, add a new item. The name will be your variable name (GIT_USER, for example) and the value will be the user name and password you will use (myUser:myPassword, in the example above). Note that his workaround can bring security issues if many people have access to the Hudson configuration panel, since the password will be visible to all that have access to this panel.
Redmine does not send emails. What should I do?
Try sending a test email. In Redmine, go to Administration/Settings/Email notifications. In the end of this page there is a “Send a test email” link. Click on this link. If the email settings are ok, it will send an email to the user you are using. Check if the email was sent correctly.
If the email was not sent, go to the ToolsCloud Manager tool and check the email configurations in the Advanced Configurations screen. Make sure all configurations are correct.
Check if the email used by Redmine as sender is correct. In Redmine, go to Administration/Settings/Email notifications. In the “Emission email address” you should have the same email you configured to send the emails, in case you are using authenticated SMTP.
If you are using GMail to send emails, note that TLS should be activated. To do that, using ToolsCloud Manager, check the email configurations in the Advanced Configurations screen. Make TLS and Enable StartTLS Auto are checked.
Don’t forget that you have to restart Apache after changing the email configurations.
How do I use Gradle with Nexus?
Para utilizar o Gradle na build dos seus projetos integrado com o repositório de artefatos Nexus do seu ambiente ToolsCloud, faça o seguinte:
No diretório .gradle criado no Home do seu usuário, crie um arquivo gradle.properties com o seguinte conteúdo:
repo.realm=Sonatype Nexus Repository Manager
Por exemplo, se o seu servidor se chama example.toolscloud.net, o seu arquivo seria:
repo.realm=Sonatype Nexus Repository Manager
Para referenciar o seu repositório Nexus no seu arquivo build.gradle, faça como neste exemplo:
apply plugin: ‘java’
apply plugin: ‘maven’
group = ‘example’
version = ‘1.0.0-SNAPSHOT’
artifactRepositoryRoot = project[“repo.root”]
artifactRepositoryUrl = project[“repo.url”]
artifactRepositoryRealm = project[“repo.realm”]
artifactRepositoryUser = project[“repo.username”]
artifactRepositoryPassword = project[“repo.password”]
org.apache.ivy.util.url.CredentialsStore.INSTANCE.addCredentials(artifactRepositoryRealm, artifactRepositoryRoot, artifactRepositoryUser, artifactRepositoryPassword);
mavenRepo urls: artifactRepositoryUrl
compile group: ‘org.apache.poi’, name: ‘poi’, version: ‘3.7’
runtime group: ‘jline’, name: ‘jline’, version: ‘0.9.94’
Fazendo isso, você consegue acessar o repositório de artefatos do Nexus para resolver suas dependências a partir da build criada em Gradle.