-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
CI acquia task number output? #84
Comments
We have access to the notification ID from the task that kicks it off e.g. database backup so we could definitely display that in the output (notifications seem to be superseding tasks on the Acquia platform now). I'll have a little play over the weekend and see how we can provide extra info here. |
Cool that sounds good! Thanks for looking into it. Back in the day I wrote a acquia api v1 deploy script that had a similar "wait_for_acquia" and print task info in it https://github.com/danshumaker/ac-deploy/blob/master/deploy#L389 . |
The small change above provides an output as follows. I'll pop in a PR later today:
|
Issue that prompts the request
We use gitlab + kubernetes + acquia_cli to do autodeploys each night. Some nights the builds&deploys fail for various reasons. However the standard output does not indicate which Acquia task is the one that failed. We obviously know the job that failed but not the Acquia Task ID in the standard out. Usually, if there is a failure, we go to the Acquia Admin UI and browse through the task list and look for the failed job. This works fine until the acquia task list is truncated by the interface and we can no longer browse for the task in question.
Our output looks like this:
Proposed Solution
What would be great is to see the task ID that the progress meter is monitoring so we can research them better. So an output like this would be great:
Describe alternatives you've considered
I've only briefly looked through the options to see if one exists for this already. Does it?
The text was updated successfully, but these errors were encountered: