Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
  • This project
    • Loading...
  • Sign in / Register
GitLab Community Edition
GitLab Community Edition
  • Project
    • Project
    • Details
    • Activity
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 11,072
    • Issues 11,072
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 665
    • Merge Requests 665
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLab Community EditionGitLab Community Edition
  • Issues
  • #30959

Closed
Open
Opened Apr 14, 2017 by Dominik Vilsmeier@Dominik1123 
  • Report abuse
  • New issue
Report abuse New issue

Gitlab page is not deployed from within group while it is from whithin user namespace

I want to deploy a page for a project which is located within a group. Everything runs without error (the pages job, the build steps, the job reports Uploading artifacts to coordinator... ok) however the page is not deployed. When I check the pipeline I see 1 job, namely pages which succeeded.

When I tried the same with a test project which I've setup under my user namespace then it worked and the page was served. Checking the pipeline there was also one job more - namely pages:deploy which is missing in the group case. This pages:deploy job is also tagged external. Both .gitlab.ci.yml files are similar:

pages:
  stage: deploy
  script:
    # Build the HTML here.
    - mkdir public
    - cp -r build/html/* public/
  artifacts:
    paths:
      - public

Note that I once had a Gitlab page for the group itself. However I deleted this page and I also checked the corresponding URI and got a 404, so I supposed the domain has been freed. Is it possible that there are still some fragments of that old group page in some database which prevent the project page from being deployed?

Related issues

Assignee
Assign to
Epic
None
Milestone
None
Assign milestone
Time tracking
None
Due date
No due date
1
Labels
awaiting feedback
Assign labels
  • View project labels
Reference: gitlab-org/gitlab-ce#30959