Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,557,547
Community Members
 
Community Events
184
Community Groups

BuildAgentRequirementFilter does not filter agents

Dear All, 

 

I'd like to set up a bamboo plugin that implements BuildAgentRequirementFilter module. Unfortunately, when I override filter function, it seems that the Collection<BuildAgent> agents returns unfiltered lists rather than a collection of agents filtered by requirements. Please see below code as an example:

public Collection<BuildAgent> filter(CommonContext buildContext, Collection<BuildAgent> agents, MinimalRequirementSet requirementSet) {
agents.toString(); //return all available agents instead of filtered agents
return agents;
}

Is it the expected behavior? if yes, is there any way for me to get the list of filtered agents based on requirements?

Thanks in advance.

 

1 answer

1 accepted

0 votes
Answer accepted
Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 26, 2020 • edited

It's expected behaviour.

Why do you need filtered agents? Filter the agents based on your criteria, let Bamboo filter them by requirements afterwards.

Hmm understood... I was a bit confused as the behavior is different on Bamboo version < 6.9.x where the agents are already filtered by Bamboo requirements before we filter it further with our criteria.

Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 27, 2020

We made this change, because in our experience, plugin-provided filtering is (usually) faster than filtering by requirements, so it makes sense to apply it first.

@Marcin Gardias  thanks for the explanation...  by the way, where can I find this kind of information (about changes) in the future?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events