Project 'rfhf19/cleanning-portalmec' was moved to 'rfhferreira/cleanning-portalmec'. Please update any links and bookmarks that may still have the old path.
failed Pipeline #29506 triggered by
Richard Fernando Heise Ferreira
@rfhferreira

Adding method to create all the progresses for an user.

1 job for update-gemfile in 3 minutes and 3 seconds (queued for 3 seconds)
Status
Job
Stage
Name
Duration
Coverage
No jobs to show
Name Stage Failure
failed
test Test
    omniauth-facebook was resolved to 8.0.0, which depends on
omniauth-oauth2 (~> 1.2) was resolved to 1.7.1, which depends on
omniauth (>= 1.9, < 3)

Deleting your Gemfile.lock file and running `bundle install` will rebuild your
snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
Cleaning up project directory and file based variables
ERROR: Job failed: exit code 1

Speed up your pipelines with Needs relationships

Using the needs keyword makes jobs run before their stage is reached. Jobs run as soon as their needs relationships are met, which speeds up your pipelines.

If you add needs to jobs in your pipeline you'll be able to view the needs relationships between jobs in this tab as a Directed Acyclic Graph (DAG).

There are no test reports for this pipeline

You can configure your job to use unit test reports, and GitLab displays a report here and in the related merge request.