-
Notifications
You must be signed in to change notification settings - Fork 36
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
Only see stdout on Errors #187
Comments
Hi @shanep2300, Not sure how we can help, but you should try running your build with verbose logs (set the That said, this doesn't appear to be a bug or a feature request, and issues like those are mostly what that repo's for. For general usage questions I would suggest using our discuss forum for that, as the community may be able to help with your question/problem. I'll close this issue now, but please feel free to reopen if you think I've been too quick to jump the gun here. Thanks! |
Hello,
Running Packer through Jenkins (not sure if this is a Jenkins issue or Packer/Ansible config).
Jenkins console will get to the
packer build
step, print that line, and then I get nothing until the ansible scripts either completes or throws an error. If it's successful, I don't see any of the ansible output. But if there is an error I see the normal ansible output up until the error in one fell swoop.I would like to see the ansible steps being printed out in the Jenkins console ouput as they're happening.
ansible.cfg
main.pkr.hcl
The text was updated successfully, but these errors were encountered: