Closed AditiSharma77 closed 3 years ago
I think the reason why the pipeline fails is because the image apache/nifi_1.12.1
is so large and it takes lot of time to pull down from Docker Hub. It seems that GitHub cancel the pipeline after 20 minutes. I suggest we try to increase the pipeline time by using timeout_minutes in on_pr_push_master.yml.
okei , let me check
I think the reason why the pipeline fails is because the image
apache/nifi_1.12.1
is so large and it takes lot of time to pull down from Docker Hub. It seems that GitHub cancel the pipeline after 20 minutes. I suggest we try to increase the pipeline time by using timeout_minutes in on_pr_push_master.yml.
Nifi fails after 20 m ,
jobs.
I think the reason why the pipeline fails is because the image
apache/nifi_1.12.1
is so large and it takes lot of time to pull down from Docker Hub. It seems that GitHub cancel the pipeline after 20 minutes. I suggest we try to increase the pipeline time by using timeout_minutes in on_pr_push_master.yml.Nifi fails after 20 m , jobs.
.timeout-minutes The maximum number of minutes to let a job run before GitHub automatically cancels it. Default: 360****
If the default value is 360 minutes, why does the workflow ends after 20 minutes?
I think the problem is in consul_acl_enabled. I am checking about this .
Current behaviour
Changed version from config.vm.box_version = ">= 0.9, < 0.10 , so getting error in consul_acl_enviroment while testing.
Expected behaviour
How to reproduce?
Suggestion(s)/solution(s) [Optional]
I checked this CI/CD with config.vm.box_version = ">= 0.7, < 0.8" still getting same error
Checklist (after created issue)