Spalloc Server integration testing #76
Conversation
dkfellows
added
the
jenkins trigger
Jenkinsfile
Outdated
| @@ -271,10 +255,28 @@ pipeline { | |||
| } | |||
| } | |||
|
|
|||
| def makeConfig(String filename) { | |||
| //def spalloc = 'spalloc://[email protected]:22246' | |||
| def spalloc = 'spalloc://[email protected]:22246' | |||
There was a problem hiding this comment.
Note - the internal IP address is used as both the Jenkins server and the machine have addresses on this internal network. Using the external IP means that traffic is likely to flow out of and in to the machine room i.e. the tests become more dependent on the networking state outside of the machine room.
There was a problem hiding this comment.
Yes, but tests fail catastrophically if I do that. I'm guessing there's some sort of iptables issue causing trouble. (Configuring /etc/hosts is better than using hardcoded IP addresses.)
There was a problem hiding this comment.
This probably means that the service isn't listening on all IP addresses. I believe that you can fix this by adding:
address: 0.0.0.0
to the yml file here (or whereever the actual config comes from):
https://github.com/SpiNNakerManchester/JavaSpiNNaker/blob/spalloc-server/SpiNNaker-allocserv/src/main/resources/application.yml#L57
|
Note that this depends on having a server instance up already. It doesn't stand up a new instance for the tests. |
https://github.com/SpiNNakerManchester/IntegrationTests into spalloc-server-jdbc
dkfellows
removed
the
jenkins trigger
No description provided.