search

wolfeidau / rake-bamboo-plugin

Plugin for bamboo which enables building of ruby projects using rake
Other
34 stars 16 forks source link

Setting Executable in Task should make it a Requirement for the Job #48

Open eddiewebb opened 11 years ago

eddiewebb commented 11 years ago

With all other executable based tasks (Ant, Maven, JDK, etc) once an Executable version is selected in a Task it is automatically added as a Requirement to the Job.

This is not the case with the ruby plugin however, and jobs will be sent to any available agent, even if they do not have the required capabilities.

Please make the selected Executable reflected by the Job's Requirements.

https://developer.atlassian.com/display/BAMBOODEV/Tasks+Overview#TasksOverview-TaskRequirements

If you want your Tasks to have requirements on Capabilities for either your own plugin-defined Executables or any other Capabilities (such as JDK's), your TaskConfigurator will also need to implement TaskRequirementSupport. This class simply provides a method to return a list of Requirements of the Task which will then get managed internally by Bamboo.

wolfeidau commented 11 years ago

Cheers for the information.

I am working in this area at the moment so I will dig into how this works.

I have had a few issues which may be related to this with users who have more than one agent, this may explain it.

Thanks for pulling this information together.

Billiam commented 10 years ago

Was this added / resolved?

Due to current limitations in Bamboo, requirements for deployment projects are only set by the associated tasks (no adding requirements manually), so fixing this issue would also allow projects to be deployed when some build agents do not have ruby, or a specific ruby version.

wolfeidau commented 10 years ago

I did have a look over this but got side tracked I will have a look over the changes this week.