gitlab-pages

问题 I used pelican as the static site generator to build a static site. I wanted to host it on GitLab Pages and let the site generate with GitLab's continuous integration with Makefile. The site successfully builds locally as well as on GitLab via its CI/CD pipeline. The build code passes with artifacts uploaded and job succeeded. The content files are built and produced in the public folder. Somehow, after the build being passed and artifacts being uploaded in public folder as desired, it was

问题 I have a group project with the following name (hosted in Gitlab): gitlab.com/my-group/my-project. I have generated coverage reports during testing and saved them as artifacts using Gitlab CI. Here is Gitlab CI config: test: stage: test image: node:11 before_script: - npm install -g yarn - yarn cache: paths: - node_modules/ script: - yarn lint - yarn test --all --coverage src/ except: - tags artifacts: paths: - coverage/ coverage: '/Statements\s+\:\s+(\d+\.\d+)%/' deploy-pages: stage: deploy

问题 This morning I got emails for each of my Gitlab Pages that are hosted on custom domains, saying that the domain verification failed. That's fine, because I don't think I ever verified them in the first place - good on Gitlab for getting this going. When I head on over the the Settings>Pages>Domain_Details on each repo, I see the instructions to create the following record: _gitlab-pages-verification-code.blog.ollyfg.com TXT gitlab-pages-verification-code={32_digit_long_code} On creating this

问题 This answer by @joki to a previous question suggests that it is possible to deploy each active branch in a GitLab repo to a dynamic environment, by giving browsable artifacts a public URL. Trying this out with a mkdocs material project, I've found two issues. Firstly, if the GitLab repo is within a group or a subgroup the URLs in the .gitlab-ci.yml file needs to be something more like this: environment: name: review/$CI_COMMIT_REF_NAME url: "$CI_PAGES_URL/-/jobs/$CI_JOB_ID/artifacts/public

问题 This answer by @joki to a previous question suggests that it is possible to deploy each active branch in a GitLab repo to a dynamic environment, by giving browsable artifacts a public URL. Trying this out with a mkdocs material project, I've found two issues. Firstly, if the GitLab repo is within a group or a subgroup the URLs in the .gitlab-ci.yml file needs to be something more like this: environment: name: review/$CI_COMMIT_REF_NAME url: "$CI_PAGES_URL/-/jobs/$CI_JOB_ID/artifacts/public

问题 I'm creating a simple java project using Gradle which generates a test report (i.e. BDD Cucumber, JUnit, etc.). This project is deployed to Gitlab where the project is built as part of the Gitlab CI process. My JUnit reports are generated in the folder build/reports/tests/test/ relative to the project path (as an index.html and some CSS files, etc.). How do I configure my .gitlab-ci.yml to publish the content of build/reports/tests/test/ to the Gitlab Pages even after my test cases fail ?

问题 How do I use PowerShell commands/scripts with Gitlab CI in a .gitlab-ci.yml file which is used to deploy to gitlab pages? I am trying to execute the build.ps1 file from .gitlab-ci.yml , but when it reaches the build.ps1 line, it gives an error saying /bin/bash: line 5: .build.ps1: command not found I am trying to use the PowerShell script to convert a file in my repo and have the converted file deployed to gitlab pages using .gitlab-ci.yml Here is my code: .gitlab.yml pages: stage: deploy

问题 I am following this tutorial https://about.gitlab.com/2016/04/11/tutorial-securing-your-gitlab-pages-with-tls-and-letsencrypt/ Next step instructions are: Make sure your web server displays the following content at http://YOURDOMAIN.org/.well-known/acme-challenge/5TBu788fW0tQ5EOwZMdu1Gv3e9C33gxjV58hVtWTbDM before continuing: 5TBu788fW0tQ5EOwZMdu1Gv3e9C33gxjV58hVtWTbDM.ewlbSYgvIxVOqiP1lD2zeDKWBGEZMRfO_4kJyLRP_4U # # output omitted # Press ENTER to continue According to the tutorial, it's using

问题 I am following this tutorial https://about.gitlab.com/2016/04/11/tutorial-securing-your-gitlab-pages-with-tls-and-letsencrypt/ Next step instructions are: Make sure your web server displays the following content at http://YOURDOMAIN.org/.well-known/acme-challenge/5TBu788fW0tQ5EOwZMdu1Gv3e9C33gxjV58hVtWTbDM before continuing: 5TBu788fW0tQ5EOwZMdu1Gv3e9C33gxjV58hVtWTbDM.ewlbSYgvIxVOqiP1lD2zeDKWBGEZMRfO_4kJyLRP_4U # # output omitted # Press ENTER to continue According to the tutorial, it's using

问题 I am deploying my React app using GitLab Pages, and it works well. Here is my gitlab-ci.yml : # Using the node alpine image to build the React app image: node:alpine # Announce the URL as per CRA docs # https://github.com/facebook/create-react-app/blob/master/packages/react-scripts/template/README.md#advanced-configuration variables: PUBLIC_URL: / # Cache node modules - speeds up future builds cache: paths: - client/node_modules # Name the stages involved in the pipeline stages: - deploy #