Search the Community
Showing results for tags 'mergebots'.
Found 3 results
I'm setting up mergebots to help with our CI/CD and I've run into a problem. We use the default trunkbot that comes with plastic server installation, but when we run it, it seems like it doesn't build from a shelve. Our plastic version is 22.214.171.12408 and TeamCity version 2019.2.1 Plastic mergebot logs show that the bot makes a shelve, but TeamCity runs the changeset already on main instead of that shelve. We did a test where we made changes to a branch to make it unable to build, but the mergebot still sucesfully merged it into main because main could build. After the merge main could no longer build. The logs in case you can see why it didn't work as expected. If there are any other logs that show why this happened, please let me know trunkbot.trunk.log.txtteamcityplug.TeamCityForMerges.log.txt Thanks in advance
Hi, is it possible to run the plastic server on one machine and merge bots on another? I've found no mentions of it so far, but i believe it should be possible... We wish to switch to using bots for merges but are a bit hesitant about having extra services share the memory and process power on the server machine.
Hi there, I'm busy experimenting with custom mergebots and I'm using the trunk mergebot as a base and editing it from there. What I want to do: I want to be able to listen for a changeset's attribute being changed, and not for a BranchAttributeChanged event. What I've tried: I've looked at this documentation, and there are apparently only two different events that can be received through the WebSocket. I've made the mergebot log any messages received from the WebSocket, and it appears to only receive BranchAttributeChanged events. Am I missing something obvious? Is there some setting I'm supposed to enable to make the server announce more events? Running version 126.96.36.19919 Edit: I'm fairly new to this kind of programming. I come from a 3D/Unity/simulation programming background, so forgive me if this is a silly question.