You need to decide how much of the unpleasant side-work you're willing to take.
You're a programmer. That means that there are a lot of bits of side-work that naturally accrete to the job. People are going to want you to do CI work and testing work and docs work and database work. They may wind up trying to push you towards project management, computer security, and/or proposal writing. The more of these you are willing to do, and the more you're willing to do them, the more valuable you are as an employee. For each of them, you'll want to set the slider in your mind.
1 - You could decide that you love Thing X, and want to make it a focus of your career. To do that, you express an interest verbally, you study it at home, and you volunteer openly and enthusiastically whenever it becomes available. (not what you want in this case)
2 - You could decide that you're okay with Thing X, and don't mind being shuffled in that direction if that' what's called for. To do that, admit this openly, volunteer when you seem like the right person for the job, and make sure you stay current.
3 - You could decide that you're okay doing this some, but you don't want it to turn into the Thing You Do. To do this, acknowledge willingness and capability, accept a reasonable level of tasking (whatever reasonable is for you - often best expressed as a percentage of total work hours), make it clear that you have limits (in willingness and/or aptitude), and push back when they try to push you too far.
4 - You could decide that you're entirely unwilling to do thing X. To do this, flatly refuse to acknowledge that you have any ability in it at all under any circumstances.
In general, unless you're an amazing programmer, you won't want to try to go with #4 on everything. Having some degree of flexibility, and willingness to adjust, is really helpful for convincing leadership that you're a team player. It sounds like in your particular case, you're wanting to go for #3, which is cool, but the fact is that it's not safe. It depends on your management actually caring about your preferences, and/or on your ability to tell them "no" once in a while.
So... assuming that your management is reasonably sane/helpful, you just need to present it straight. CI is something you don't enjoy, but you can tell that in this particular case you could save a lot of wasted time and energy setting this thing up. You're willing to put in the setup effort (even though you don't like it) and the (hopefully minimal) maintenance effort (this is necessary) for the good of the company, but you were hired as a programmer, and it's important to you that you stay a programmer. Then, be ready. Six months down the line, when they try to push more CI work on you than you're okay with (however much that is), you have to push back, and tell them that you're not happy with the degree to which it's taken over your job. Recognize that if the management situation is toxic enough, you may have to quit. Realize that by doing this now, you're signing up to possibly having to deal with that situation in the future.
That's really all you can do... on any of those things.
