|Re: Team concept and API access [message #1184954 is a reply to message #1184930]
||Wed, 13 November 2013 20:20
| Henrik Lynggaard Hansen
Registered: November 2013
Bob Foster wrote on Wed, 13 November 2013 14:59|
The REST API knows nothing about teams. So the behavior you describe, sys admin jobs go to public team and team member jobs go to first team found, is as planned. You can specify a particular team using, e.g., the create-job CLI command, which allows a team argument.
You might also want to look into the create-team, list-jobs and list-teams CLI commands for various aspects team management.
Please let us know of any duplicated jobs bugs you can reproduce in 3.1.0. We've fixed a few team bugs for 3.1.1, but I thought we'd gotten all those for 3.1.0.
Not really the answer I was hoping for
I can understand the idea that sys admin jobs go to public, but the pick random team if user is member than more than one team I still consider a bug. randomness is hardly planned behaviour (I have created the following BugZilla https://bugs.eclipse.org/bugs/show_bug.cgi?id=421671)
I don't think it would be too hard to support the team concept in xml API, all it need to do is look for a period sign in the job name and split it into team part and job part. I have created Bz https://bugs.eclipse.org/bugs/show_bug.cgi?id=421672 for this.
It is at good to know the CLI supports it, although at this point I would consider it a fallback since we migrated away from that and to the XML API given the performance problems of the CLI application.
When we last tested it, it took 5+ minutes to load a pipeline of ~50 jobs while the XML API does it in around 30 seconds.
Do you know if there has been any performance improvements on the CLI side?
Powered by FUDForum
. Page generated in 0.13537 seconds