-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Atlantis does not include full path specified in config when calling bitbucket API #508
Comments
Previously we were stripping the basepath from the passed in URL. i.e. if I passed in --bitbucket-base-url=https://me.com/basepath then we would just strip off /basepath. This change fixes that bug (#508).
😭well that's not good! I've got a patch coming. You'll have to run off of the master Docker image |
Fixed in #509 |
Awesome, thanks @lkysow! I will test that on Monday! |
@lkysow when you say runatlantis/atlantis:master do you mean I need to build the docker image myself from the master branch? Because if I pull runatlantis/atlantis:latest it will still be version v0.4.15 running in the container even though I can see on docker hub that latest was updated 3 days ago: Tags (35) Don't know if I'll be able to build the master docker myself as it is failing here:
|
Oops, I meant |
I can't get Atlantis to work with our private bitbucket stash server. Problem seems to be that our bitbucket base url is defined like this: https://bitbucket.domain.com/bitbucket which is also what I provide for the --bitbucket-base-url flag when starting Atlantis. However this yields 404's when Atlantis uses the bitbucket api.
For example got the following when creating a new PR
And this when commenting on a PR with
atlantis plan
:So, right now we can't use Atlantis at all because of this :(
The text was updated successfully, but these errors were encountered: