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

Invalid option "app" #1230

Open
brunoparga opened this issue Jan 8, 2021 · 1 comment
Open

Invalid option "app" #1230

brunoparga opened this issue Jan 8, 2021 · 1 comment
Labels

Comments

@brunoparga
Copy link

Hi! I run dpl on a GitLab CI/CD pipeline. On December 2, while I was working on tests and really not paying attention to prod, the job started failing for seemingly no reason. It went from:

[...]
$ dpl --provider=heroku --app=$HEROKU_APP --api-key=$HEROKU_API_KEY
Installing deploy dependencies
[...]
Successfully installed dpl-heroku-1.10.16
6 gems installed
[...]

to:

[...]
$ dpl --provider=heroku --app=$HEROKU_APP --api-key=$HEROKU_API_KEY
invalid option "--app="
Cleaning up file based variables
ERROR: Job failed: exit code 1

I can provide more complete logs if needed, but I diffed them and the only differences are things like commit hashes and download times. There seems to be no difference in how dpl actually runs, except for the lines above - especially, no difference with versions of anything (which would show in the diff). My own commit doesn't touch anything related to this, it's an ExpressJS project where a test file is added and one line changes in production code related to seeding the DB.

I can tell that neither of the Heroku-related variables in question changed, at that time or otherwise, on either Heroku or GitLab.

How would I get this job working again?

@stale
Copy link

stale bot commented Jan 8, 2022

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

@stale stale bot added the stale label Jan 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant