The purpose of build tools like Jenkins ties in with the concept of Continuous Integration. Jenkins helps compile source code, perform code linting, static analysis, and more.
Typically Jenkins will be tied in with version control so each commit that you make will trigger a Commit Build in Jenkins.
In each commit build you will have a set of instructions for the CI Build to do. You will typically see Unit Tests, Integration Tests, code linting and depending on the programming language an application binary may be built on this step.
To answer your question though, yes Jenkins can compile your source code but it can do much more.
Jenkins can run build tools like Maven, and run them automatically when code is checked in, if you like. But Jenkins is much more than that. It can also run a whole raft of maintenance, testing and deployment tools as well as serving as a "one stop shopping" web site where you can track projects right down to the source code and the test results.
"privilege" comes from the Latin words for "private" and "law" (legal) and dates to feudal times. To "claim privilege" meant that you were above the laws that applied to the common people.
We must storm this mad man's lab and destroy his villanous bomb! Are you with me tiny ad?