-
Suggestion
-
Resolution: Answered
-
None
-
None
It would be great to have an IDE plugin for Eclipse and/or IntelliJ IDEA to allow users to view code changes and test failures in the build system and then with one click have the change or failing test open in the IDE.
The plugin should support the option for personal builds that pass all tests to be automatically committed to the repository as described at BAM-1313
- incorporates
-
- Closed
[BAM-868] Add IDE integration with Eclipse and IntelliJ IDEA plugins
Hi guys,
We have released Atlassian IDE plugin which ties JIRA, Bamboo and Crucible into your IDE.
Currently, plugins are available for IDEA and Eclipse:
http://confluence.atlassian.com/display/IDEPLUGIN/IDE+Plugin+Documentation
Please feel free to download the plugins and give them a go in your IDE. As always, we really appreciate any feedback, suggestions, or recommendations you may have for us. You can raise them here:
https://studio.atlassian.com/browse/PLE
Cheers,
Edwin
Jacques Morel
added a comment - I am not sure what you are referring to by "TC add". They have a plugin specific to each IDE they support (IDEA, Eclipse, VS) that adds support for delayed run/pre-tested commits.
BTW since I posted this, my team is COMPLETELY dependent on remote builds. We have a farm of servers that run a build faster than our local box could ever do. Since our build is almost impossible to do locally the ability to submit private builds to a server as easily as running a build locally with the option to commit if successful is a life saver. This feature is so important for us that we could not migrate to any CI tool that does not support it. I believe that once you have tested the goods, you never come back... Try it.
Jacques Morel
added a comment - I am not sure what you are referring to by "TC add". They have a plugin specific to each IDE they support (IDEA, Eclipse, VS) that adds support for delayed run/pre-tested commits.
BTW since I posted this, my team is COMPLETELY dependent on remote builds. We have a farm of servers that run a build faster than our local box could ever do. Since our build is almost impossible to do locally the ability to submit private builds to a server as easily as running a build locally with the option to commit if successful is a life saver. This feature is so important for us that we could not migrate to any CI tool that does not support it. I believe that once you have tested the goods, you never come back... Try it. 
John Allen
added a comment - Jacques is that a TC add? I'm tempted to go re-visit. I recently posted this thread on the Bamboo forums re IDE integrations so will be interested to see what comes up
John Allen
added a comment - Jacques is that a TC add? I'm tempted to go re-visit. I recently posted this thread on the Bamboo forums re IDE integrations so will be interested to see what comes up Jacques Morel
added a comment - Once we started to use Teamcity, the reaction of almost everybody was to be surprised by the power of personal builds and the "delayed commit". Once someone touched the goods, you are not coming back. I can almost single this feature alone to attribute the amazing smooth transition to TC from cruisecontrol. Our team is somewhat agile but people were still viewing CI as an annoyance, something that globally was making the team faster. However TC made it into a personal productivity tool.
The compute power at your disposal is already too constrained. Builds are not getting faster. Schedule pressure is always rising. Personal build/delayed commits allow you to send your changes to be built by a "certified" environment and commit if successful. In the meantime, your machine is free to be used on the next problem to solve or you are free to go home knowing that your changes will be committed automatically if they did not conflict with others and they did not break the build.
Jacques Morel
added a comment - Once we started to use Teamcity, the reaction of almost everybody was to be surprised by the power of personal builds and the "delayed commit". Once someone touched the goods, you are not coming back. I can almost single this feature alone to attribute the amazing smooth transition to TC from cruisecontrol. Our team is somewhat agile but people were still viewing CI as an annoyance, something that globally was making the team faster. However TC made it into a personal productivity tool.
The compute power at your disposal is already too constrained. Builds are not getting faster. Schedule pressure is always rising. Personal build/delayed commits allow you to send your changes to be built by a "certified" environment and commit if successful. In the meantime, your machine is free to be used on the next problem to solve or you are free to go home knowing that your changes will be committed automatically if they did not conflict with others and they did not break the build.
Resolving this issue in Bamboo project.
Please visit: https://studio.atlassian.com/browse/PLE.