I like the idea and looks good. One thing to think about though is in
the trafficserver.spec file, if there are any good ways to dynamically do those
config files includes at the end. Im no spec expert so Im not sure if there may
be a better way but recently here I worked on getting our internal spec and
build system to be able to do builds of ATS master and it looks like starting
with 8/9 some more of those files will be going away and another new one
introduced. So those files change frequently across version numbers
On 6/15/18, 11:27 AM, "Eric Friedrich (efriedri)" <efrie...@cisco.com.INVALID>
wrote:
I’ve opened a PR to produce Trafficserver and astats RPMs in the Traffic
Control build process. Previously, new users would need to create their own
build environments or ask for RPMS on Slack.
This PR will lower the barrier to entry for new users. For more involved
users, theres now a set of scripts that will build inside a Dockerized Jenkins
environment.
The changes rely on having all TS changes in a single git repository to
form the RPM source tarball. I understand there are some users which have
private tooling to build from multiple repos. I’m open to including this if
possible. Until that tool gets open sourced, I think this is a step forward for
TC builds.
https://github.com/apache/trafficcontrol/pull/2399
Any concerns with bringing this in?
—Eric
