Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
BuildMaster - Where is the code built?
-
Hello!
We are working on a PoC of BuildMaster and something we can't find in documentation is where exactly does the code get built? We are used to an environment where the code gets checked out on a dedicated agent server that has all the build tools needed installed on it and the code gets compiled there. I see BuildMaster has an Agent you can install and connect to other systems using WMI/SSH, but is code compiled on the target system?
Currently for us:
Bitbucket (source code checked out to) -> TeamCity Agent (compiles code/unit tests) -> Octopus Deploy -> IIS Server
How BuildMaster may work?
Bitbucket (source code checked out to) -> IIS Server (BuildMaster issues remote commands to compile code/unit tests)?
I guess we could still have agents with BuildMaster, but I guess they are more generic than how TeamCity defines it where we install a specific agent binary on there.
-
Hi @kichikawa_2913 ,
Given that you're already familiar and comfortable with using build agents, then we'd recommend a similar set-up with BuildMaster. To do this, you'd provision/configure your build server(s) and then have BuildMaster connect to them, generally using the Inedo Agent.
One common pattern is to create a role, such as
build-server, and then target it in your pipeline stage, like this:
This way, it will act as a server pool. You can also do this in OtterScript as well, for some very fine-grained control; it's considered a resource pool.
In any case, whatever server you target is where the code will retreived from source, built, and tested.
hope this helps!
-
@atripp thank you for the info! What's the typical setup you see with other customers? Is all this described in documentation somewhere I missed?
-
@kichikawa_2913 we don't have a typical set-up per se, really
A lot of set-ups are very simple, since the team is new to CI/CD, and they just have the BuildMaster server do everything.
Others have dozens of build agents configured in a pool to service various teams, and use lots of shared configuration.
Most are somewhere in the middle -- since they started simple, and gradually explored over time. That's generally what i'd start with -- tackle one pattern/team, then move on to the next and improve over time.
