CODEWITHSUNDEEP
gitlab-ci
Gregory Kuhn
Gregory Kuhn

Reputation: 1697

gitlab-ci job not running script

I am new to gitlab-ci and trying a minimal Python application based on a gitlab template.

My .gitlab-ci.yml file is below:

# This file is a template, and might need editing before it works on your project.
# Official language image. Look for the different tagged releases at:
# https://hub.docker.com/r/library/python/tags/
#image: python:latest

# Change pip's cache directory to be inside the project directory since we can
# only cache local items.
variables:
  PIP_CACHE_DIR: "$CI_PROJECT_DIR/.cache"

stages:
  - test
  - run

# Pip's cache doesn't store the python packages
# https://pip.pypa.io/en/stable/reference/pip_install/#caching
#
# If you want to also cache the installed packages, you have to install
# them in a virtualenv and cache it as well.
#cache:
#  paths:
#    - .cache/pip
#    - venv/

before_script:
  - python -V               # Print out python version for debugging
    #- pip install virtualenv
    #- virtualenv venv
  - python -m venv venv
  - venv/scripts/activate

job1:
  stage: test
  script:
  - python setup.py test
  #- pip install tox flake8  # you can also use tox
  #- tox -e py36,flake8

job2:
  stage: run
  script:
  - pip install wheel
  - python setup.py bdist_wheel
  artifacts:
    paths:
      - dist/*.whl

      #pages:
      #  script:
      #  - pip install sphinx sphinx-rtd-theme
      #  - cd doc ; make html
      #  - mv build/html/ ../public/
      #  artifacts:
      #    paths:
      #    - public
      #  only:
      #  - master

The jobs are seen within the gitlab web UI and they appear to run on my (windows based shell executor) runner.

When I look at the output for the jobs, it appears as if the actual script commands for each job aren't running at all.

Here's the output from job1:

Running with gitlab-runner 11.2.0 (35e8515d)
  on GKUHN-L04 b0162458
Using Shell executor...
Running on GKUHN-L04...
Fetching changes...
Removing venv/
HEAD is now at 2484105 And agai..
From https://gitlab.analog.com/GKuhn/test_gitlab_ci
 - [deleted]         (none)     -> origin/test_ci
   fdd4216..cd618ba  master     -> origin/master
Checking out cd618ba9 as master...
Skipping Git submodules setup
$ python -V
Python 3.7.0
$ python -m venv venv
$ venv/scripts/activate
Job succeeded

And job2:

Running with gitlab-runner 11.2.0 (35e8515d)
  on GKUHN-L04 b0162458
Using Shell executor...
Running on GKUHN-L04...
Fetching changes...
Removing venv/
HEAD is now at cd618ba updated .gitlab-ci.yml file
Checking out cd618ba9 as master...
Skipping Git submodules setup
$ python -V
Python 3.7.0
$ python -m venv venv
$ venv/scripts/activate
Uploading artifacts...
WARNING: dist/*.whl: no matching files             
ERROR: No files to upload                          
Job succeeded

What am I doing wrong??

Upvotes: 6

Views: 4096

Answers (1)

Gregory Kuhn
Gregory Kuhn

Reputation: 1697

Turns out this is bug on Windows with the shell executor: https://gitlab.com/gitlab-org/gitlab-runner/issues/2730

And a duplicate of this question: Gitlab CI does not execute npm scripts

Upvotes: 3

Related Questions