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

push fails due to process problem #74

Open
jonathanl-telenav opened this issue Oct 4, 2022 · 1 comment
Open

push fails due to process problem #74

jonathanl-telenav opened this issue Oct 4, 2022 · 1 comment
Assignees

Comments

@jonathanl-telenav
Copy link
Contributor

[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 11.013 s
[INFO] Finished at: 2022-10-04T17:55:38-06:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal com.telenav.cactus:cactus-maven-plugin:1.5.31:push (default-cli) on project telenav-build: com.telenav.cactus.cli.ProcessFailedException: git --no-pager -c push.default=current -c pull.rebase=false -c diff.renamelimit=0 -c init.defaultBranch=main push (in /Users/jonathanl/Workspaces/telenav-build/cactus) exited 128
[ERROR] error: unable to read askpass response from '/usr/bin/false'
[ERROR] fatal: could not read Username for 'https://github.com': terminal prompts disabled
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :telenav-build

@timboudreau
Copy link
Collaborator

You are logged out from Github. So, git is trying to ask for a password, but Maven doesn't do interactive, so you need do some operation that logs you in (i.e. so git's credential cache has your access token).

Perhaps, since we're using environment variables with the access token for calling gh, there is some way to detect this situation and retry with the credentials somehow - or shove them into git's credentials cache somehow.

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

No branches or pull requests

2 participants