Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[JENKINS-49866] Automatically configure Docker Cloud if a Docker host is available #95

Merged
merged 14 commits into from Jun 7, 2018

Conversation

4 participants
@batmat
Copy link
Collaborator

commented May 30, 2018

No description provided.

@jenkinsadmin

This comment has been minimized.

Copy link

commented May 30, 2018

Build failed; the context from the latest run is:

Expand to view
test_not_root
ASSERT:expected:<jenkins> but was:<root>
ASSERT:expected:<jenkins> but was:<root>
ASSERT:expected:<jenkins> but was:<root>
ASSERT:expected:<jenkins> but was:<root>
ASSERT:expected:<jenkins> but was:<root>
shunit2:ERROR test_not_root() returned non-zero return code.
test_npm_5_plus
test_jep_307

Retrieving test run data (container logs, ...) before shutdown... Will be in the build/tests-run-2018-05-30_15-27-34 directory... Done getting logs for infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1
infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1
infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1
Cleaning up... Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
�[3A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[1A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1BRemoving infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
�[3A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[1A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1BRemoving network infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_default
Post stage
G'day!

Ran 4 tests.

FAILED (failures=9)
Makefile:29: recipe for target 'container-check' failed
make: *** [container-check] Error 1
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger



[program:socat]
command=socat -d -d TCP4-LISTEN:2375,fork UNIX-CONNECT:/var/run/docker.sock

This comment has been minimized.

Copy link
@rtyler

rtyler May 30, 2018

Member

I'm so confused 😸

@batmat

This comment has been minimized.

Copy link
Collaborator Author

commented May 30, 2018

@batmat batmat force-pushed the batmat:JENKINS-49866 branch 2 times, most recently from 746b215 to 7df6b26 May 31, 2018

@jenkinsadmin

This comment has been minimized.

Copy link

commented May 31, 2018

Build failed; the context from the latest run is:

Expand to view
Digest: sha256:e0a4ef30634c982ef395a1a4bdf221df06b3def015f79536fa2d658d5bce9c88
Status: Downloaded newer image for realguess/jq:1.4
test_logs_are_propagated
test_evergreen_home_is_fully_owned_by_jenkins_user
ASSERT:Some files are not owned by 'jenkins', should not happen! expected:<> but was:<./supervisord.pid
./supervisord.log>
shunit2:ERROR test_evergreen_home_is_fully_owned_by_jenkins_user() returned non-zero return code.
test_error_telemetry_service_is_secured

Retrieving test run data (container logs, ...) before shutdown... Will be in the build/tests-run-2018-05-31_10-19-03 directory... Done getting logs for infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1
infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1
infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1
Cleaning up... Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
�[3A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
Post stage
�[2B�[1A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1BRemoving infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
�[1A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1B�[2A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[3A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3BRemoving network infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_default
G'day!

Ran 15 tests.
./shunit2/shunit2: line 950: [: skipped=1: integer expression expected

FAILED (failures=5)
Makefile:29: recipe for target 'container-check' failed
make: *** [container-check] Error 1
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented May 31, 2018

Build failed; the context from the latest run is:

Expand to view
4317f356dab4: Pull complete
5ba1f428cec5: Pull complete
6e6f0848c9c7: Pull complete
Digest: sha256:e0a4ef30634c982ef395a1a4bdf221df06b3def015f79536fa2d658d5bce9c88
Status: Downloaded newer image for realguess/jq:1.4
test_logs_are_propagated
test_evergreen_home_is_fully_owned_by_jenkins_user
test_error_telemetry_service_is_secured

Retrieving test run data (container logs, ...) before shutdown... Will be in the build/tests-run-2018-05-31_10-27-44 directory... Done getting logs for infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1
infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1
infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1
Cleaning up... Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
�[3A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[1A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1BRemoving infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
�[1A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1B�[2A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[3A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3BRemoving network infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_default
Post stage
G'day!

Ran 15 tests.
./shunit2/shunit2: line 950: [: skipped=1: integer expression expected

FAILED (failures=3)
Makefile:29: recipe for target 'container-check' failed
make: *** [container-check] Error 1
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@batmat batmat referenced this pull request May 31, 2018

Merged

Split conf-as-code files #96

2 of 2 tasks complete

@batmat batmat force-pushed the batmat:JENKINS-49866 branch from c360203 to 3114dc4 May 31, 2018

connector:
attach:
user: "jenkins"
instanceCapStr: "10"

This comment has been minimized.

Copy link
@pjdarton

pjdarton Jun 4, 2018

Unless you're sure you need an instance cap, I'd suggest that you leave it blank.
If you leave it blank then Jenkins will (or should) start as many (of those) containers as it needs to.

If you're concerned about overloading the local docker engine then I'd suggest that setting a cloud-level cap would be the right thing to do.

This comment has been minimized.

Copy link
@batmat

batmat Jun 4, 2018

Author Collaborator

@pjdarton though I didn't put that with a strong thinking behind, I would be more leaning toward putting something, to somehow offer an acceptable default behaviour for most setups.

(Like: running 1000 containers looks definitely too high and would kill the master itself on most setups, 100? 20?
Also, I do plan to limit the memory per container, though same: not sure what value to put).

Anyway, thanks a bunch for reviewing this. It's really appreciated, and I'll make sure to put you in the loop for upcoming changes about this (and anything else if you're interested :-)).

This comment has been minimized.

Copy link
@pjdarton

pjdarton Jun 5, 2018

FYI we use docker a lot and we don't bother specifying a per-container memory limit.
Different usage scenarios will need very different values - some containers can run in a megabyte and some require over a gigabyte, and users of may be shocked that anyone could choose such a small/large number that's so very different to their needs. Docker itself defaults to not specifying a limit for this very reason.
We just limit the number of containers we run on each docker host, although for our smaller docker hosts we limit it to 6 (as our containers each run IBM db2, and that is not a lightweight bit of software).

If you want to specify a default limit then how about setting a per-cloud limit of 4 containers?
That's small enough that it shouldn't stress most docker daemons, but large enough to demonstrate that we can have multiple containers running at once.
By comparison, Jenkins defaults to having only two executors on the master, so a limit of 4 containers is showing twice that capacity.

This comment has been minimized.

Copy link
@batmat

batmat Jun 6, 2018

Author Collaborator

I think at that stage we should slightly conservative, and so yes I like the idea to set the limit at the cloud level to 4 or something.

Same goes for container memory: I do want us to be conservative for now, and open up as we better understand things and get feedback from users. "Closing" more features afterwards is as always more difficult IMO.
My idea would be to define "something", but the hard part comes indeed when defining actual values :)

As to:

If you want to specify a default limit then how about setting a per-cloud limit of 4 containers?

IIUC this would mean removing the instanceCapStr: "10" line under templates, and use containerCap: 4 directly under the docker yaml node right @pjdarton ?

@batmat batmat force-pushed the batmat:JENKINS-49866 branch from 3114dc4 to d37fd91 Jun 5, 2018

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 5, 2018

Build failed; the context from the latest run is:

Expand to view
[Services] npm ERR! errno 1
[Services] npm ERR! evergreen-services@0.0.0 jest: `jest --bail --forceExit ./test`
[Services] npm ERR! Exit status 1
[Services] npm ERR! 
[Services] npm ERR! Failed at the evergreen-services@0.0.0 jest script.
[Services] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[Services] 
[Services] npm ERR! A complete log of this run can be found in:
[Services] npm ERR!     /root/.npm/_logs/2018-06-05T13_52_41_443Z-debug.log
[Services] Makefile:20: recipe for target 'unit' failed
[Services] make[1]: *** [unit] Error 1
[Services] make[1]: Leaving directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/services'
[Services] Makefile:9: recipe for target 'check' failed
[Services] make: *** [check] Error 2
[Services] make: Leaving directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/services'
[Pipeline] [Services] }
[Pipeline] [Services] // stage
[Pipeline] [Services] }
[Services] Failed in branch Services
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build jenkins/evergreen)
Stage 'Build jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Test jenkins/evergreen)
Stage 'Test jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 5, 2018

Build failed; the context from the latest run is:

Expand to view
[Services] npm ERR! errno 1
[Services] npm ERR! evergreen-services@0.0.0 jest: `jest --bail --forceExit ./test`
[Services] npm ERR! Exit status 1
[Services] npm ERR! 
[Services] npm ERR! Failed at the evergreen-services@0.0.0 jest script.
[Services] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[Services] 
[Services] npm ERR! A complete log of this run can be found in:
[Services] npm ERR!     /root/.npm/_logs/2018-06-05T14_07_27_125Z-debug.log
[Services] Makefile:20: recipe for target 'unit' failed
[Services] make[1]: *** [unit] Error 1
[Services] make[1]: Leaving directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/services'
[Services] Makefile:9: recipe for target 'check' failed
[Services] make: *** [check] Error 2
[Services] make: Leaving directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/services'
[Pipeline] [Services] }
[Pipeline] [Services] // stage
[Pipeline] [Services] }
[Services] Failed in branch Services
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build jenkins/evergreen)
Stage 'Build jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Test jenkins/evergreen)
Stage 'Test jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 5, 2018

Build failed; the context from the latest run is:

Expand to view
[Client] 
[Client] 
[Client] =============================== Coverage summary ===============================
[Client] Statements   : 54.57% ( 203/372 )
[Client] Branches     : 42.05% ( 37/88 )
[Client] Functions    : 45.92% ( 45/98 )
[Client] Lines        : 54.92% ( 201/366 )
[Client] ================================================================================
[Client] 
[Client] Test Suites: 7 passed, 7 total
[Client] Tests:       36 passed, 36 total
[Client] Snapshots:   0 total
[Client] Time:        5.628s
[Client] Ran all test suites.
[Client] make[1]: Leaving directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/client'
[Client] make: Leaving directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/client'
[Pipeline] [Client] }
[Pipeline] [Client] // stage
[Pipeline] [Client] }
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Build jenkins/evergreen)
Stage 'Build jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Test jenkins/evergreen)
Stage 'Test jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@batmat batmat force-pushed the batmat:JENKINS-49866 branch from 037f609 to bf2bcd3 Jun 5, 2018

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 5, 2018

Build failed; the context from the latest run is:

Expand to view
[Docker Cloud image] latest: Pulling from library/hello-world
[Docker Cloud image] 9bb5a5d4561a: Pulling fs layer
[Docker Cloud image] 9bb5a5d4561a: Download complete
[Docker Cloud image] 9bb5a5d4561a: Pull complete
[Docker Cloud image] Digest: sha256:f5233545e43561214ca4891fd1157e1c3c563316ed8e237750d59bde73361e77
[Docker Cloud image] Status: Downloaded newer image for hello-world:latest
[Docker Cloud image] 
[Docker Cloud image] Retrieving test run data (container logs, ...) before shutdown... Will be in the build/tests-run-2018-06-05_16-31-46 directory... Done getting logs for infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1
[Docker Cloud image] infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1
[Docker Cloud image] infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1
[Docker Cloud image] Cleaning up... Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
[Docker Cloud image] Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
[Docker Cloud image] Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
[Docker Cloud image] �[3A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[1A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1BRemoving infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
[Docker Cloud image] Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
[Docker Cloud image] Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
[Docker Cloud image] �[1A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1B�[3A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2BRemoving network infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_default
[Docker Cloud image] G'day!
[Docker Cloud image] 
[Docker Cloud image] Ran 15 tests.
[Docker Cloud image] ./shunit2/shunit2: line 945: [: skipped=1: integer expression expected
[Docker Cloud image] 
[Docker Cloud image] OK
[Pipeline] [Docker Cloud image] }
[Pipeline] [Docker Cloud image] // stage
[Pipeline] [Docker Cloud image] }
[Pipeline] // parallel
Post stage
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 6, 2018

Build failed; the context from the latest run is:

Expand to view
[Base image] �[1A�[2K
Starting services_db_1 ... �[32mdone�[0m
[Base image] �[1B
[Base image] �[4mSequelize CLI [Node: 9.11.1, CLI: 4.0.0, ORM: 4.37.6]�[24m
[Base image] 
[Base image] Loaded configuration file "config/database.json".
[Base image] Using environment "development".
[Base image] Wed, 06 Jun 2018 14:09:56 GMT sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators at node_modules/sequelize/lib/sequelize.js:242:13
[Base image] File: .gitignore does not match pattern: /\.js$/
[Base image] File: .gitignore does not match pattern: /\.js$/
[Base image] == 20180424162454-null-update-level: migrating =======
[Base image] == 20180424162454-null-update-level: migrated (0.025s)
[Base image] 
[Base image] ../tools/compose run --rm db pg_dump \
[Base image] 	--inserts \
[Base image] 	-h db -U postgres -d evergreen_development > initdb.d/db.sql
[Base image] The DB_TRACING variable is not set. Defaulting to a blank string.
[Base image] The DEBUG variable is not set. Defaulting to a blank string.
[Base image] make[1]: Leaving directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/services'
[Base image] ./tests/offline-tests.sh
[Base image] ./tests/offline-tests.sh: line 67: ./shunit2/shunit2: No such file or directory
[Base image] Makefile:31: recipe for target 'base-container-check' failed
[Base image] make: *** [base-container-check] Error 1
[Pipeline] [Base image] }
[Pipeline] [Base image] // withEnv
[Docker Cloud image] Running on ubuntu-jenkinsinfrad3fce10 in /home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA
[Pipeline] [Base image] }
[Pipeline] [Base image] // node
[Pipeline] [Docker Cloud image] {
[Pipeline] [Base image] }
[Pipeline] [Base image] // stage
[Pipeline] [Base image] }
[Base image] Failed in branch Base image
[Pipeline] [Docker Cloud image] checkout
[Docker Cloud image] Fetching changes from the remote Git repository
[Docker Cloud image] Fetching without tags
[Docker Cloud image] Merging remotes/origin/master commit f6baad00eed9460e429d14c429ab18fd452ec2e0 into PR head commit 75045adf9a03e6fbc7832cb866e3aa63b4d322f2
[Docker Cloud image] Merge succeeded, producing 75045adf9a03e6fbc7832cb866e3aa63b4d322f2
[Docker Cloud image] Checking out Revision 75045adf9a03e6fbc7832cb866e3aa63b4d322f2 (PR-95)
[Docker Cloud image] Commit message: "Force an agent for each parallel stage"
[Docker Cloud image] 
[Docker Cloud image] GitHub has been notified of this commit’s build result
[Docker Cloud image] 
[Pipeline] [Docker Cloud image] withEnv
[Pipeline] [Docker Cloud image] {
[Pipeline] [Docker Cloud image] sh
[Docker Cloud image] [Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA] Running shell script
[Docker Cloud image] + make docker-cloud-container-check
[Docker Cloud image] make -C services dump
[Docker Cloud image] make[1]: Entering directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/services'
[Docker Cloud image] ../tools/compose stop

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 6, 2018

Build failed; the context from the latest run is:

Expand to view
[Docker Cloud image] Loaded configuration file "config/database.json".
[Docker Cloud image] Using environment "development".
[Docker Cloud image] Wed, 06 Jun 2018 14:10:26 GMT sequelize deprecated String based operators are now deprecated. Please use Symbol based operators for better security, read more at http://docs.sequelizejs.com/manual/tutorial/querying.html#operators at node_modules/sequelize/lib/sequelize.js:242:13
[Docker Cloud image] File: .gitignore does not match pattern: /\.js$/
[Docker Cloud image] File: .gitignore does not match pattern: /\.js$/
[Docker Cloud image] == 20180424162454-null-update-level: migrating =======
[Docker Cloud image] == 20180424162454-null-update-level: migrated (0.020s)
[Docker Cloud image] 
[Docker Cloud image] ../tools/compose run --rm db pg_dump \
[Docker Cloud image] 	--inserts \
[Docker Cloud image] 	-h db -U postgres -d evergreen_development > initdb.d/db.sql
[Docker Cloud image] The DB_TRACING variable is not set. Defaulting to a blank string.
[Docker Cloud image] The DEBUG variable is not set. Defaulting to a blank string.
[Docker Cloud image] make[1]: Leaving directory '/home/jenkins/workspace/Infra_evergreen_PR-95-D6LEI27MPDY4XPNI7YV3LFAYRY3WNMJZK3MUE42DPS736BJY5XYA/services'
[Docker Cloud image] ENVIRONMENT=docker-cloud ./tests/offline-tests.sh
[Docker Cloud image] ./tests/offline-tests.sh: line 67: ./shunit2/shunit2: No such file or directory
[Docker Cloud image] Makefile:36: recipe for target 'docker-cloud-container-check' failed
[Docker Cloud image] make: *** [docker-cloud-container-check] Error 1
[Pipeline] [Docker Cloud image] }
[Pipeline] [Docker Cloud image] // withEnv
[Pipeline] [Docker Cloud image] }
[Pipeline] [Docker Cloud image] // node
[Pipeline] [Docker Cloud image] }
[Pipeline] [Docker Cloud image] // stage
[Pipeline] [Docker Cloud image] }
[Docker Cloud image] Failed in branch Docker Cloud image
[Pipeline] // parallel
Post stage
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 6, 2018

Build failed; the context from the latest run is:

Expand to view
[Docker Cloud image]  ---> 918b3365d394
[Docker Cloud image] Step 28/41 : RUN mkdir -p /usr/local/bin
[Docker Cloud image]  ---> Running in a12bc1e0bb0b
[Docker Cloud image] Removing intermediate container a12bc1e0bb0b
[Docker Cloud image]  ---> 19a133faf532
[Docker Cloud image] Step 29/41 : COPY build/jenkins.sh /usr/local/bin/
[Docker Cloud image] Service 'instance' failed to build: COPY failed: stat /var/lib/docker/tmp/docker-builder980801238/build/jenkins.sh: no such file or directory
[Docker Cloud image] CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES
[Docker Cloud image] cc7e2536e091        postgres:alpine     "docker-entrypoint.s…"   3 minutes ago       Up 3 minutes        5432/tcp            services_db_1
[Docker Cloud image] Error: No such container: 
[Docker Cloud image] shunit2:FATAL oneTimeSetUp() returned non-zero return code.
[Docker Cloud image] ASSERT:Unknown failure encountered running a test
[Docker Cloud image] 
[Docker Cloud image] Ran 0 tests.
[Docker Cloud image] 
[Docker Cloud image] FAILED (failures=1)
[Docker Cloud image] Makefile:38: recipe for target 'docker-cloud-container-check' failed
[Docker Cloud image] make: *** [docker-cloud-container-check] Error 2
[Pipeline] [Docker Cloud image] }
[Pipeline] [Docker Cloud image] // withEnv
[Pipeline] [Docker Cloud image] }
[Pipeline] [Docker Cloud image] // node
[Pipeline] [Docker Cloud image] }
[Pipeline] [Docker Cloud image] // stage
[Pipeline] [Docker Cloud image] }
[Docker Cloud image] Failed in branch Docker Cloud image
[Pipeline] // parallel
Post stage
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@batmat batmat force-pushed the batmat:JENKINS-49866 branch from c858b7c to 89f828c Jun 6, 2018

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 6, 2018

Build failed; the context from the latest run is:

Expand to view
[Base image] Retrieving test run data (container logs, ...) before shutdown... Will be in the build/tests-run-2018-06-06_14-51-25 directory... Done getting logs for infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1
[Base image] infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1
[Base image] infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1
[Base image] Cleaning up... Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
[Base image] Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
[Base image] Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
[Base image] �[3A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[1A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1BRemoving infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
[Base image] Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
[Base image] Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
[Base image] �[3A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[1A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1BRemoving network infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_default
[Base image] G'day!
[Base image] 
[Base image] Ran 15 tests.
[Base image] ./shunit2/shunit2: line 950: [: skipped=3: integer expression expected
[Base image] 
[Base image] FAILED (failures=25)
[Base image] Makefile:33: recipe for target 'base-container-check' failed
[Base image] make: *** [base-container-check] Error 1
[Pipeline] [Base image] }
[Pipeline] [Base image] // withEnv
[Pipeline] [Base image] }
[Pipeline] [Base image] // node
[Pipeline] [Base image] }
[Pipeline] [Base image] // stage
[Pipeline] [Base image] }
[Base image] Failed in branch Base image
[Pipeline] // parallel
Post stage
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@jenkinsadmin

This comment has been minimized.

Copy link

commented Jun 6, 2018

Build failed; the context from the latest run is:

Expand to view
[Base image] Retrieving test run data (container logs, ...) before shutdown... Will be in the build/tests-run-2018-06-06_15-42-13 directory... Done getting logs for infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1
[Base image] infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1
[Base image] infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1
[Base image] Cleaning up... Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
[Base image] Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
[Base image] Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
[Base image] �[3A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[2A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2B�[1A�[2K
Stopping infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1BRemoving infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... 
[Base image] Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... 
[Base image] Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... 
Post stage
[Base image] �[3A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_instance_1 ... �[32mdone�[0m
�[3B�[1A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1       ... �[32mdone�[0m
�[1B�[2A�[2K
Removing infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_backend_1  ... �[32mdone�[0m
�[2BRemoving network infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_default
[Base image] G'day!
[Base image] 
[Base image] Ran 15 tests.
[Base image] ./shunit2/shunit2: line 950: [: skipped=3: integer expression expected
[Base image] 
[Base image] FAILED (failures=25)
[Base image] Makefile:33: recipe for target 'base-container-check' failed
[Base image] make: *** [base-container-check] Error 1
[Pipeline] [Base image] archiveArtifacts
[Base image] Archiving artifacts
[Pipeline] [Base image] }
[Pipeline] [Base image] // withEnv
[Pipeline] [Base image] }
[Pipeline] [Base image] // node
[Pipeline] [Base image] }
[Pipeline] [Base image] // stage
[Pipeline] [Base image] }
[Base image] Failed in branch Base image
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Publish jenkins/evergreen)
Stage 'Publish jenkins/evergreen' skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: script returned exit code 2
Finished: FAILURE

Powered by the Comment Logger

@batmat batmat force-pushed the batmat:JENKINS-49866 branch from 5938cae to 0b2a334 Jun 6, 2018

@batmat batmat changed the title WIP [JENKINS-49866] Automatically configure Docker Cloud if a Docker host is available [JENKINS-49866] Automatically configure Docker Cloud if a Docker host is available Jun 6, 2018

@batmat batmat removed the work-in-progress label Jun 6, 2018

@batmat batmat requested a review from rtyler Jun 6, 2018

@rtyler

rtyler approved these changes Jun 7, 2018

@rtyler

This comment has been minimized.

Copy link
Member

commented Jun 7, 2018

@batmat I think a conflict exists because of the hard-coded changes for the Update Levels in master, once you rebase feel free to merge

batmat added some commits May 31, 2018

[JENKINS-49866] Automatically configure Docker Cloud if a Docker host…
… is available

It works locally.

Still to be done: enable all things related Docker only if the socket
is available:

* Enable & configure the docker cloud
* Install the plugin and its deps only in that case
Force an agent for each parallel stage
To avoid conflict like this

```
---> Running in a1855d049c6f

Removing intermediate container a1855d049c6f

 ---> b134bc6c1cb3

Successfully built b134bc6c1cb3

Successfully tagged jenkinsciinfra/evergreen-backend:latest

Image for service backend was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.

Creating infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1 ...


Creating infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1 ... error

ERROR: for infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1  Cannot create container for service db: Conflict. The container name "/infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1" is already in use by container "984d2c8bc9e0de2b526717963d8808904d1bd58768deb6622b64aead323534df". You have to remove (or rename) that container to be able to reuse that name.



ERROR: for db  Cannot create container for service db: Conflict. The container name "/infraevergreenpr95d6lei27mpdy4xpni7yv3lfayry3wnmjzk3mue42dps736bjy5xya_db_1" is already in use by container "984d2c8bc9e0de2b526717963d8808904d1bd58768deb6622b64aead323534df". You have to remove (or rename) that container to be able to reuse that name.

Encountered errors while bringing up the project.

CONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS              PORTS               NAMES

6b90a47d7ad9        postgres:alpine     "docker-entrypoint.s…"   5 minutes ago       Up 2 minutes        5432/tcp            services_db_1

Error: No such container:

shunit2:FATAL oneTimeSetUp() returned non-zero return code.

ASSERT:Unknown failure encountered running a test



Ran 0 tests.



FAILED (failures=1)

Makefile:31: recipe for target 'base-container-check' failed

make: *** [base-container-check] Error 2

script returned exit code 2
```
Improve client target dependencies
Without this, running any target like `make unit` and so
on would fail. Only `make check` would succeed before that change.

@batmat batmat force-pushed the batmat:JENKINS-49866 branch from 0b2a334 to 187ac4b Jun 7, 2018

@batmat

This comment has been minimized.

Copy link
Collaborator Author

commented Jun 7, 2018

Rebased and force pushed to resolve the conflict. Will merge as agreed if the PR build succeeds.

Thanks for the review @rtyler !

@batmat batmat merged commit 1f49e95 into jenkins-infra:master Jun 7, 2018

1 check passed

continuous-integration/jenkins/pr-merge This commit looks good
Details

@batmat batmat deleted the batmat:JENKINS-49866 branch Jun 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.