Problem/Motivation
The results of mkdoc build cannot be seen without merging into the default branch. It would be nice to be able to preview changes.
Steps to reproduce
- Create an issue fork repository.
- Make changes to documentation in the /docs directory.
- Push your changes to your forked repository.
- The mkdocs job will not run and you cannot see your changes.
Proposed resolution
Separate the mkdocs build and the GitLab pages deploy into two jobs so the build results can be seen in the artifact browser.
Ideally, the changes would be deployed using GitLab Pages to a separate URL that doesn't overwrite the deployment from the default branch, but I don't know if this is possible.
Remaining tasks
- Separate the current job into a build job and a deploy job.
User interface changes
The pipelines in GitLab will change slightly.
Issue fork member-3516150
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
alexdmccabeComment #4
alexdmccabeComment #5
jdleonard@alexdmccabe there's now a merge conflict that I think you'll be able to resolve more efficiently than I.
I think we saw this work recently here, no?
Comment #6
alexdmccabeConflict fixed. Ready for re-review.
It's fancier now. Looking at the artifacts didn't quite work correctly. Example:
http://member-3516150-6209f7.pages.drupalcode.org/preview-6
Comment #8
jdleonardVery nifty, thanks!
I tried to find a way to get the preview URL bubbled up somewhere more discoverable than the job logs, but failed :(
Comment #9
jdleonardComment #10
alexdmccabeI might have figured that out with the environment key in the GitLab CI/CD YAML.
I'll open a follow-up issue.