This repository has been archived by the owner on Oct 31, 2019. It is now read-only.
[WORK IN PROGRESS] deploy full environment from Jenkins #47
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
afeld
changed the title
afeld
force-pushed
the
jenkins-env-full
branch
6 times, most recently
from
c9bbe04
to
5e58db2
Compare
|
Running into some gnarly bugs in (one or more of) Ansible/Jenkins/Packer
|
Collecting links that seem to be relevant here:
afeld
force-pushed
the
jenkins-env-full
branch
2 times, most recently
from
b029631
to
e78da0d
Compare
afeld
force-pushed
the
jenkins-env-full
branch
from
e78da0d
to
5e9f1cc
Compare
|
Going a different direction. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Split out from #41.