CODEWITHSUNDEEP
dockerelasticsearchjenkinsapache-kafka
fledgling
fledgling

Reputation: 1051

Port allocation when running build job in Jenkins

My project is structured in such a way that the build job in Jenkins is triggered from a push to Git. As part of my application logic, I spin up kafka and elastic search instances to be used in my test cases downstream.

The issue I have right now is, when a developer pushes his changes to Git, it triggers a build in Jenkins which in turn runs our code and spawns kafka broker in localhost:9092 and elastic search in localhost:9200.

When another developer working on some other change simultaneously, pushes his code, it triggers the build job again and tries to spin up another instance of kafka/elastic search but fails with the exception “Port already in use”.

I am looking at options on how to handle this scenario.

Will running these instances inside of docker container help to some extent? How do I handle the port issue in that case?

Upvotes: 0

Views: 680

Answers (1)

Ivonet
Ivonet

Reputation: 2731

Yes dockerizing these instances can indeed help as you can spawn them multiple times.

You could create a docker container per component including your application and then let them talk to each other by linking them or using docker-compose

That way you would not have to expose the ports to the "outside" world but keep it internal within the docker environment.

That way you would not have the “Port already in use”. The only problem is memory in that case. e.g. if 100 pushes are done to the git repo, you might run out of memory...

Upvotes: 1

Related Questions