Gitlab Needs Vs Dependencies. Getting started with GitLab CI At first glance it seems like it should replace dependencies entirely, and some guides advise switching to needs as it should work "better" The job will start right away once all the declared jobs complete, irrespective of what stage: is declared.needs: also implies the same effect as dependencies:.
Dependency list GitLab from docs.gitlab.cn
When GitLab knows the dependencies between your jobs, jobs can run as fast as possible, even starting earlier than other jobs in the same stage. dependencies: only says which artifacts your job is going to download, as opposed to the default behavior of jobs, which is to download all artifacts of all preceding jobs
Dependency list GitLab
If efficiency is important and you want everything to run as quickly as possible, you can use the needs keyword to define dependencies between your jobs In the below example, the pack jobs will start running as soon as the test job completes, so if, in future, someone adds more tests in the test stage, the package jobs will start to run before. Which leads me to conclude that you only need to use dependencies when needing to pass artifacts between jobs in the same or later stages
How to more productive with Gitlab CI. GitLab has a special keyword needs, which creates dependencies between jobs, and allows jobs to run earlier, as soon as their dependent jobs complete Mike's Work Labbook This is for tracking general issues/todos/snippets/wiki whatever, that is not connected to a specific Project
How to more productive with Gitlab CI. needs: is about order of execution and creating DAGs In documentation there is an advice "You should not combine dependencies with needs in the.