I have a build that has been stuck in job received for 2+ hours. Here is the build:
https://travis-ci.org/awslabs/aws-service-catalog-puppet/builds/529475283
The build is set to run on a new release being triggered from a github repo. It has been working for some time without any configuration changes - it worked earlier today.
Is there anything I can do to see why the job is stuck or if it is just in a queue?
The organization https://travis-ci.org/awslabs has a lot of jobs queued up (103, to be more precise, including the ones that are running at this very moment, such as https://travis-ci.org/awslabs/s2n/jobs/529425133 and https://travis-ci.org/awslabs/s2n/jobs/529425136). Your particular job is #9 in the queue, so it will start soon.
Thanks a million for the response.
Is there anywhere I can view the queue?
Unfortunately this information isn’t available on travis-ci.org.