team city bot permissions to trigger builds
Hello colleagues,
I have troubles invoking builds and re-runs from the team city bot
interface.
If I click on the corresponding buttons ("Trigger build" or "Re-run
possible blockers") it shows the "Internal Server Error [500]." in the
UI and the chrome dev tools shows that bot backend actually return the
following error message:
--
Service https://ci.ignite.apache.org/app/rest/buildQueue returned
Invalid Response Code : 403:
Responding with error, status code: 403 (Forbidden).
Details: jetbrains.buildServer.serverSide.auth.AccessDeniedException:
You do not have "Comment build" permission in project with internal id:
project17
Access denied. Check the user has enough permissions to perform the
operation.
--
Is it a bug or I need more permissions in fact?
If my current permissions are not enough would you please give me more?
My teamcity user name is: serge.korotkov
Thanks,
--
Sergey
[MTCGA]: new failures in builds [6544163] needs to be handled
Hi Igniters, I've detected some new issue on TeamCity to be handled. You are more than welcomed to help. If your changes can lead to this failure(s): We're grateful that you were a volunteer to make the contribution to this project, but things change and you may no longer be able to finalize your contribution. Could you respond to this email and indicate if you wish to continue and fix test failures or step down and some committer may revert you commit. *Recently contributed test failed in master IgniteSetClientTestsColocated.TestCopyToInvalidArguments https://ci2.ignite.apache.org/test/7088095684091633079?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3E *Recently contributed test failed in master IgniteSetClientTests.TestCopyToInvalidArguments https://ci2.ignite.apache.org/test/-420042244593401280?currentProjectId=IgniteTests24Java8&branch=%3Cdefault%3E Changes may lead to failure were done by - pavel tupitsyn https://ci2.ignite.apache.org/viewModification.html?modId=978726 - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 21:38:22 03-08-2022
Performance of cancelling services (related to IGNITE-17274)
Testing with 60,000+ services, found that cancelling large numbers of services takes significant time. Found another linear lookup that can be optimized with a map. Here is a commit that fixes the problem in local testing: https://github.com/artnaseef/ignite/commit/4ca87f7f6e7aae193faf1404736e0b4ee7168752 The difference, on my local system, with and without the patch: CANCEL 60,000 *WITHOUT PATCH* = 67s 358ms CANCEL 60,000 *PATCHED* = 1s 323ms Note that, with the IGNITE-17274 fix, startup of the same 60,000 services only takes ~ 9s. Appreciate any feedback, and I hope we can push this fix forward. I can create a new Jira ticket and pull request. Art
