Skip to content

do not use the $PORT env var#29

Closed
kpacha wants to merge 4 commits intodrone:masterfrom
kpacha:rename_port_envvar
Closed

do not use the $PORT env var#29
kpacha wants to merge 4 commits intodrone:masterfrom
kpacha:rename_port_envvar

Conversation

@kpacha
Copy link

@kpacha kpacha commented Nov 4, 2015

...because it doesn't allow you to use drone-wall in mesos environments

@Tathanen
Copy link
Contributor

Tathanen commented Mar 5, 2016

None of this much applies to the current release of the wall, feel free to open a new PR if you are having a similar issue with the latest version.

@Tathanen Tathanen closed this Mar 5, 2016
@kpacha
Copy link
Author

kpacha commented Mar 5, 2016

I'm glad this doesn't apply to the latest version! I'll check it next week.

I think this PR could be merged into the v2 branch anyway. Even if the branch is not going to be maintained anymore. Docker is not yet supported in v3 and I don't know if this latest version supports drone v0.3 as v2 did... what do you think?

@Tathanen
Copy link
Contributor

Tathanen commented Mar 5, 2016

Sure, I've gone ahead and made a branch for the v2 version, since it's true that v3 doesn't support drone v0.3. Go ahead and re-open a pull on that branch. Mention WALL_PORT in the README as well, I see now that the old PORT var was never even noted in there.

@kpacha
Copy link
Author

kpacha commented Mar 6, 2016

done! see #34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants