You can set a global timeout in _&quot;Project settings -&gt; CI/CD Pipelines -&gt; Timeout&quot;_ or _&quot;Project settings -&gt; Builds -&gt; Timeout&quot;_ in older versions.

As of version 12.3, you can set a timeout per stage in your CI .yml file using [`timeout`](https://docs.gitlab.com/ee/ci/yaml/#timeout):

&gt; `timeout` allows you to configure a timeout for a specific job. For example:

```
build:
  script: build.sh
  timeout: 3 hours 30 minutes

test:
  script: rspec
  timeout: 3h 30m
```

&gt; The job-level timeout can exceed the project-level timeout but can’t exceed the Runner-specific timeout.

There are two timeout can be set: **project timeout** and **runner timeout**.

**Project timeout:**  

It is possible to set timeout per job from **Settings** -&gt; **CI/CD** -&gt; **General pipelines**

[![enter image description here][1]][1]


**Runner timeout:**   

runner&#39;s timeout can be set from  **Settings** -&gt; **CI/CD** -&gt; **Runners**, select the runner from **Runners activated for this project** and edit the *Maximum job timeout* from the runner edit form. 
[![enter image description here][2]][2]

Be aware that these two types of timeout can be overridden by each other. Refer the [docs][3].


  [1]: https://i.stack.imgur.com/4Q9Oa.png
  [2]: https://i.stack.imgur.com/RQwJ5.png
  [3]: https://docs.gitlab.com/ee/ci/runners/#setting-maximum-job-timeout-for-a-runner

A job-specific timeout was introduced in Gitlab 12.3

https://docs.gitlab.com/ce/ci/yaml/README.html#timeout

```yaml
build:
  script: build.sh
  timeout: 3 hours 30 minutes

test:
  script: rspec
  timeout: 3h 30m
```

If running it at Gitlab, then the above stated answers has already told the right way. But if you would like to run the Gitlab CI locally that too with tour own runner, then runners timeout you need to pass with command.   

gitlab-runner exec docker job_name --timeout 3600

here it is setting runners timeout as 3600 seconds

I created a library based on .NET 4.6.2 version.   
To the library, I&#39;ve added the EntityFramework version 6.1.3 package.   
I created a model as follow  

    using System;
    using System.ComponentModel.DataAnnotations;
    using System.ComponentModel.DataAnnotations.Schema;
    
    namespace Components.Models
    {
      public class Session
      {
        [DatabaseGenerated(DatabaseGeneratedOption.Identity)]
        public string Id { get; set; }
    
        [Key]
        [Required]
        public string Identity { get; set; }
    
        [Required]
        public DateTime CreatedAt { get; set; }
    
        [Required]
        public DateTime UpdatedAt { get; set; }
      }
    } 

And the dbcontext

    using System.Configuration;
    using System.Data.Entity;
    using System.Data.Entity.ModelConfiguration.Conventions;
    using Components.Models;
    
    namespace Components.DataContexts
    {
      public class SessionContext : DbContext
      {
        public SessionContext() : base(ConfigurationManager.ConnectionStrings[&quot;sessiondb&quot;].ConnectionString)
        {
        }
    
        public DbSet&lt;Session&gt; Sessions { get; set; }
    
        protected override void OnModelCreating(DbModelBuilder modelBuilder)
        {
          modelBuilder.Conventions.Remove&lt;PluralizingEntitySetNameConvention&gt;();
        }
    
      }
    }

Then I tried to enable migration and did via 

    PM&gt; Enable-Migrations
statement, got the error message:

    Exception calling &quot;SetData&quot; with &quot;2&quot; argument(s): &quot;Type &#39;Microsoft.VisualStudio.ProjectSystem.VS.Implementation.Package.Automation.OAProject&#39; in assembly &#39;Microsoft.VisualStudio.ProjectSystem.VS.Implementation, Version=14.1.0.0, Culture=neutral, 
    PublicKeyToken=b03f5f7f11d50a3a&#39; is not marked as serializable.&quot;At D:\C#\IndustryCloud\packages\EntityFramework.6.1.3\tools\EntityFramework.psm1:720 char:5
    +     $domain.SetData(&#39;startUpProject&#39;, $startUpProject)
    +     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
        + FullyQualifiedErrorId : SerializationException
     
    System.NullReferenceException: Object reference not set to an instance of an object.
       at System.Data.Entity.Migrations.Extensions.ProjectExtensions.GetProjectTypes(Project project, Int32 shellVersion)
       at System.Data.Entity.Migrations.Extensions.ProjectExtensions.IsWebProject(Project project)
       at System.Data.Entity.Migrations.MigrationsDomainCommand.GetFacade(String configurationTypeName, Boolean useContextWorkingDirectory)
       at System.Data.Entity.Migrations.EnableMigrationsCommand.FindContextToEnable(String contextTypeName)
       at System.Data.Entity.Migrations.EnableMigrationsCommand.&lt;&gt;c__DisplayClass2.&lt;.ctor&gt;b__0()
       at System.Data.Entity.Migrations.MigrationsDomainCommand.Execute(Action command)
    Object reference not set to an instance of an object.

What do I doing wrong?  


**Update** 
Here the structure, how projet is build

[![enter image description here][1]][1]

In the sessiontest.cs, I wrote the test for db. 

    [Test]
    public void InsertARow_DbInitial_ExpectDbValue()
    {
    
      var sn = new Session()
      {
        Identity = Random.Generate(15),
        CreatedAt = DateTime.Now,
        UpdatedAt = DateTime.Now
      };
    
      db.Sessions.Add(sn);
      db.SaveChanges();
    
    }

The ComponentsTest project, where I wrote the unit test, the app.config looks as follow:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;configuration&gt;
      &lt;connectionStrings&gt;
        &lt;add connectionString=&quot;Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=Session;Integrated Security=True;Connect Timeout=30;Encrypt=False;TrustServerCertificate=True;ApplicationIntent=ReadWrite;MultiSubnetFailover=False&quot; name=&quot;sessiondb&quot; /&gt;
      &lt;/connectionStrings&gt;
    &lt;/configuration&gt;

And in the library(Component) itself the app.config:

    &lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;
    &lt;configuration&gt;
     
      &lt;configSections&gt;
        
        &lt;section name=&quot;entityFramework&quot; type=&quot;System.Data.Entity.Internal.ConfigFile.EntityFrameworkSection, EntityFramework, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089&quot; requirePermission=&quot;false&quot; /&gt;
      &lt;!-- For more information on Entity Framework configuration, visit http://go.microsoft.com/fwlink/?LinkID=237468 --&gt;&lt;/configSections&gt;
      &lt;entityFramework&gt;
        &lt;defaultConnectionFactory type=&quot;System.Data.Entity.Infrastructure.LocalDbConnectionFactory, EntityFramework&quot;&gt;
          &lt;parameters&gt;
            &lt;parameter value=&quot;mssqllocaldb&quot; /&gt;
          &lt;/parameters&gt;
        &lt;/defaultConnectionFactory&gt;
        &lt;providers&gt;
          &lt;provider invariantName=&quot;System.Data.SqlClient&quot; type=&quot;System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer&quot; /&gt;
        &lt;/providers&gt;
      &lt;/entityFramework&gt;
    
      &lt;connectionStrings&gt;
        &lt;add connectionString=&quot;Data Source=(localdb)\MSSQLLocalDB;Initial Catalog=Session;Integrated Security=True;Connect Timeout=30;Encrypt=False;TrustServerCertificate=True;ApplicationIntent=ReadWrite;MultiSubnetFailover=False&quot; name=&quot;sessiondb&quot; /&gt;
      &lt;/connectionStrings&gt;
      
    &lt;/configuration&gt;



  [1]: http://i.stack.imgur.com/EBI5N.png


Enable-Migrations Exception calling &quot;SetData&quot; with &quot;2&quot; argument(s)

I am trying to access `appsetting.json` file from a class library. So far the solution that I found is to create a configuration class implementing interface `IConfiguration` from  `Microsoft.Extensions.Configuration` and add the json file to class and read from the same.

    var configuration = new Configuration();
    configuration.AddJsonFile(&quot;appsetting.json&quot;);
    var connectionString= configuration.Get(&quot;connectionString&quot;);

This seems to be bad option as we have to add the json file each time we have to access the appsetting configuration. Dont we have any alternative like `ConfigurationManager` in  **ASP.NET**.

Access from class library to appsetting.json in Asp.net-core

I&#39;m using a self-hosted `GitLab CI server` (community edition v8.9.5) and `gitlab-ci-multi-runner` 1.2.0 to build a project.  One of my pipeline stages (test) takes a while to run and I get the following erm:

&gt;     ERROR: Build failed: execution took longer than 3600 seconds

Where do I put the override for this timeout?  Can I apply it to just the test pipeline stage?

GitLab CI Pipeline Stage Timeout

I'm using a self-hosted <code>GitLab CI server</code> (community edition v8.9.5) and <code>gitlab-ci-multi-runner</code> 1.2.0 to build a project. One of my pipeline stages (test) takes a while to run and I get the following erm:
> ERROR: Build failed: execution took longer than 3600 seconds
Where do I put the override for this timeout? Can I apply it to just the test pipeline stage?

I recently updated to Android Studio 2.3, and now when I try to run the application, the emulator does not come online. It times out after 300 seconds.

Additionally, The app has been experiencing a FATAL EXCEPTION ERROR (OOM), and I am not sure how to fix that either, or if that is part of the emulator problem. 

Any help is much appreciated. Again, my knowledge in the program is very limited so if your answer can be kept simple, that would be great.

Waiting for Target Device to Come Online

I use GitLab on their servers. I would like to download my latest built artifacts (build via GitLab CI) via the API like this:

```
curl --header &quot;PRIVATE-TOKEN: 9koXpg98eAheJpvBs5tK&quot; &quot;https://gitlab.com/api/v3/projects/1/builds/8/artifacts&quot;
```

Where do I find this project ID? Or is this way of using the API not intended for hosted GitLab projects?


Where do I find the project ID for the GitLab API?

I have a `.gitlab-ci.yml` file which contains following:

&lt;!-- language: lang-yaml --&gt;

    image: docker:latest
    
    services:
      - docker:dind
    
    before_script:
      - docker info
      - docker-compose --version
    
    buildJob:
      stage: build
      tags:
        - docker
      script:
        - docker-compose build

But in `ci-log` I receive message:

&lt;!-- language: lang-bash

    $ docker-compose --version
    /bin/sh: eval: line 46: docker-compose: not found

What am I doing wrong?

Run docker-compose build in .gitlab-ci.yml

I&#39;m trying to write a `gitlab-ci.yml` file which uses a multi-line string for the command. However, it seems like it is not being parsed. I&#39;ve tried both the `- |` and `- &gt;` with identical results.

    stages:
      - mystage

    Build:
      stage: mystage
      script:
        - |
            echo -e &quot;
                echo &#39;hi&#39;;
                echo &#39;bye&#39;;
            &quot;

When it tries to run, it only shows `echo -e &#39;` as the script to run, and not the whole multiline string. This causes issues for me.

What would be the correct syntax to write something like this?

Multiline YAML string for GitLab CI (.gitlab-ci.yml)

How do I run a .gitlab-ci.yml job only on a tagged Master branch?

    job:
      script:
      - echo &quot;Do something&quot;
      only:
      - master
      - tags

The above code will run if either condition exists: a Master branch or a tagged commit. 

My goal is to have this run for a production deploy, but it would require that it be on the Master branch and that it be tagged (with a version). Otherwise, I&#39;ll have another job that will push to staging if its missing a tag.

How to run a gitlab-ci.yml job only on a tagged branch?

Gitlab provides a `.gitlab-ci.yml` template for building and publishing images to its own registry (click &quot;new file&quot; in one of your project, select `.gitlab-ci.yml` and `docker`). The file looks like this and it works out of the box :)

&lt;!-- language: lang-yaml --&gt;

    # This file is a template, and might need editing before it works on your project.
    # Official docker image.
    image: docker:latest

    services:
      - docker:dind

    before_script:
      - docker login -u &quot;$CI_REGISTRY_USER&quot; -p &quot;$CI_REGISTRY_PASSWORD&quot; $CI_REGISTRY

    build-master:
      stage: build
      script:
        - docker build --pull -t &quot;$CI_REGISTRY_IMAGE&quot; .
        - docker push &quot;$CI_REGISTRY_IMAGE&quot;
      only:
        - master

    build:
      stage: build
      script:
        - docker build --pull -t &quot;$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG&quot; .
        - docker push &quot;$CI_REGISTRY_IMAGE:$CI_COMMIT_REF_SLUG&quot;
      except:
        - master

But by default, this will publish to gitlab&#39;s registry. How can we publish to [docker hub](https://hub.docker.com/) instead?

Content Type	Original Author	Original Content on Stackoverflow
Question	Jackpot	View Question on Stackoverflow
Solution 1 - Timeout	tmt	View Answer on Stackoverflow
Solution 2 - Timeout	Chuan	View Answer on Stackoverflow
Solution 3 - Timeout	PhilLab	View Answer on Stackoverflow
Solution 4 - Timeout	shaktisinghmoyal	View Answer on Stackoverflow

GitLab CI Pipeline Stage Timeout

Timeout Problem Overview

Timeout Solutions

Solution 1 - Timeout

Solution 2 - Timeout

Solution 3 - Timeout

Solution 4 - Timeout

Access from class library to appsetting.json in Asp.net-core

Enable-Migrations Exception calling "SetData" with "2" argument(s)

Attributions