Browse Source

Enable GitLab CI Pipelines

This includes not only the mandatory .gitlab-ci.yml file containing
the pipeline configuration but also an Emacs Lisp file for exporting
the blog post and pages from the content-org files to markdown using
Emacs and ox-hugo.

It was also necessary to remove thr orgit links from the "My Emacs
Package of the week: orgit" post since these required that the linked
repository is at the given path which is not possible in the CI build.
Well, it is /possible/ but there is no good way to do it.

Additional the .gitmodules file was updated to use a relative local
path instead of and SSH URL since GitLab can obviously not clone form
an SSH URL. This may make things more difficult for local setups but I
think I can live with the one additional clone command.
main
Marcel Kapfer 5 months ago
parent
commit
fe0029437c
Signed by: mmk2410
GPG Key ID: CADE6F0C09F21B09
  1. 35
      .build/ox-hugo-build.el
  2. 13
      .gitlab-ci.yml
  3. 2
      .gitmodules
  4. 2
      content-org/blog.org

35
.build/ox-hugo-build.el

@ -0,0 +1,35 @@
;; Package configuration
(package-initialize)
(add-to-list 'package-archives '("nongnu" . "https://elpa.nongnu.org/nongnu/") t)
(add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/") t)
(setq-default load-prefer-newer t)
(setq-default package-enable-at-startup nil)
(package-refresh-contents)
(package-install 'use-package)
(setq package-user-dir (expand-file-name "./.packages"))
(add-to-list 'load-path package-user-dir)
(require 'use-package)
(setq use-package-always-ensure t)
;; Install and configure necessary packages
(use-package org
:pin gnu
:config
(setq org-todo-keywords '((sequence
"TODO(t!)" "NEXT(n!)" "STARTED(a!)" "WAIT(w@/!)" "SOMEDAY(s)"
"|" "DONE(d!)" "CANCELLED(c@/!)"))))
(use-package ox-hugo
:after org)
;; Export blog posts
(defun mmk2410/export (file)
(save-excursion
(find-file file)
(org-hugo-export-wim-to-md t)))
(mapcar (lambda (file) (mmk2410/export file))
(directory-files (expand-file-name "./content-org/") t "\\.org$"))

13
.gitlab-ci.yml

@ -0,0 +1,13 @@
variables:
GIT_SUBMODULE_STRATEGY: recursive
build:
image: silex/emacs:27.2-alpine-ci
stage: build
script:
- emacs -Q --script .build/ox-hugo-build.el
- apk add --no-cache hugo
- hugo
artifacts:
paths:
- public

2
.gitmodules vendored

@ -1,3 +1,3 @@
[submodule "nextDESIGN"]
path = themes/nextDESIGN
url = git@git.mmk2410.org:mmk2410/nextDESIGN
url = ../nextDESIGN

2
content-org/blog.org

@ -333,7 +333,7 @@ But there is currently a problem. When exporting an Org buffer e.g. to Markdown
"https://git.mmk2410.org/%n/commit/%r")) ;; The link to the revision
#+end_src
As written in the documentation for =orgit-export-alist= it is also possible to set these values using the =git config= command with the keys =orgit.status=, =orgit.log= and =orgit.commit=. Thereby only the =%r= (the revision) must appear in the string of the last two keys. The =%n= in the code above will get expanded to the path of the project. Using this configuration the exporting works and I can now also link here to my projects overview page ([[orgit:~/projects/mmk2410.org/][projects overview page]]) and the commit of my last blog post ([[orgit-rev:~/projects/mmk2410.org/::e1b5ee5496fe7147c77985ac5f49e8bb7f4d4725][commit of my last blog post]] ).
As written in the documentation for =orgit-export-alist= it is also possible to set these values using the =git config= command with the keys =orgit.status=, =orgit.log= and =orgit.commit=. Thereby only the =%r= (the revision) must appear in the string of the last two keys. The =%n= in the code above will get expanded to the path of the project. Using this configuration the exporting works and I can now also link here to my projects overview page and the commit of my last blog post (/Update 2021-02-03: Well, at least in theory and also locally. But since I'm now probably building my block using a GitLab CI pipeline the links to not work since Orgit cannot find the directory in the link location. Therefore I needed to remove the links./).
That's it! I sure will integrate this package into my workflow and Emacs configuration and I hope you enjoyed this brief presentation.

Loading…
Cancel
Save