Skip to content
Browse files

fix links

  • Loading branch information
markus2330 committed Nov 23, 2019
1 parent a912a23 commit ba8ffe00c0735610a4b6c5f4af57e6ca7c207dfd
@@ -1,7 +1,7 @@
# Elektra

[![Jenkins Build Status](](
[![Jenkins Build Status](](
[![Travis Build Status](](
[![Cirrus Build Status](](
[![Coverage Status](](
@@ -48,14 +48,14 @@ Currently Elektra uses two different files.
#### Jenkinsfile.daily

- [Jenkinsfile.daily](/scripts/jenkins/Jenkinsfile.daily) contains daily maintenance tasks, like cleaning up build servers.
- [Buildjob: libelektra-daily](
- [Buildjob: libelektra-daily](
- [Jenkinsfile.daily](

#### Jenkinsfile

- Triggered on code changes and is for testing changes to the codebase.
- [Jenkinsfile](/scripts/jenkins/Jenkinsfile) contains descriptions how to build, test and deploy Elektra.
- [Buildjob: libelektra](
- [Buildjob: libelektra](
- [Jenkinsfile](

#### DSL
@@ -68,7 +68,7 @@ is executed in a sandbox which might block certain calls.
Since plugins might extend the pool of available commands or variables a full
list of currently available syntax can be seen in
after a login to the build server.
Some functionality is not covered by this page when the responsible plugin is
not implementing it.
@@ -185,7 +185,7 @@ verified or added to build Elektra correctly:
- `Advanced clone behaviors` should be added and the path to the git mirror
needs to be specified: `/home/jenkins/git_mirrors/libelektra`.
This reference repository is created and maintained by our
[daily buildjob](
[daily buildjob](
- Under Property strategy you can add `Trigger build on pull request comment`.
`jenkins build (libelektra|all) please` is a good starting point.
This functionality is provided by the
@@ -223,8 +223,8 @@ To reliable determine which stages failed it is best to look over the build
results in the Jenkins Blue Ocean view.
It is the default View opened when accessing the build results from GitHub.
For libelektra the URLs are and and

Failed stages are marked in red.
@@ -280,24 +280,23 @@ sure to test any modifications locally first.

All Triggers are described in the configuration of the respective build jobs.

The [libelektra](
The [libelektra](
build is triggered for all branches of the libelektra repository except for
Additionally all open branches in forks targeting libelektra's repository via
PRs are going to be build.
Pushes to any of those branches will trigger a new build automatically.

[daily build](
[daily build](
is executed according to a cron schedule.

The following phrases can be used as comments to manually trigger a specific

- jenkins build [libelektra]( please
- jenkins build [website]( please
- jenkins build [daily]( please
- jenkins build [monthly]( please
- jenkins build [libelektra]( please
- jenkins build [daily]( please
- jenkins build [monthly]( please

Additionally `jenkins build all please` can be used to trigger all build jobs
relevant for PR's.
@@ -16,8 +16,7 @@ The GSoC efforts have their first large contribution to Elektra, the 3
way merge finally arrives with this release. It is still a long way to
go, however, because augeas plugins can only be mounted with a
workaround and the package integration of the 3-way merge is still in
its infancy. More information about GSoC and its progress can be found
its infancy.

A special thanks to Felix Berlakovich for his contributions to the
3-way merge, including meta merging, conflict resolving strategies and
@@ -115,10 +115,7 @@ issues and setting up travis:
Now (nearly) every build job can be triggered from Pull Requests.
For example:

- jenkins build [git-buildpackage-jessie]( please
- jenkins build [git-buildpackage-wheezy]( please
- jenkins build [icc]( please
- jenkins build [local-installation]( please
- jenkins build [libelektra]( please

For a full list see [here](

@@ -1,5 +1,5 @@
On potential changes of the API/ABI as detected by
please check following list:

- API is reviewed
@@ -1,5 +1,5 @@
// vim: ts=2:sw=2:expandtab:syntax=groovy
* This file describes how the elektra-jenkinsfile buildjob should be
* executed.
@@ -14,7 +14,7 @@
* A Snippet generator is available to the public at
* A list of available commands on the build server can be found after a login at

// TODO have a per plugin/binding deps in Dockerfile for easier maintenance
@@ -1,5 +1,5 @@
// vim: ts=2:sw=2:expandtab:syntax=groovy
/* */
/* */

// Set properties for buildjob
@@ -22,8 +22,8 @@ if (DEPENDENCY_PHASE)

# ~~~
# Disable on GCC 4 and earlier:
# -
# -
# -
# -
# ~~~

@@ -137,7 +137,7 @@ <h4 class="list-group-item-heading pull-left">{{ post.title}}</h4>
<p><a href=""><img src="" alt="Release" /></a>
<a href=""><img src="" alt="Jenkins Build Status" /></a>
<a href=""><img src="" alt="Jenkins Build Status" /></a>
<a href=""><img src="" alt="Travis Build Status" /></a>
<a href=""><img src="" alt="Cirrus Build Status" /></a>
<a href=""><img src="" alt="Coverage Status" /></a>
@@ -5,7 +5,7 @@
# The following link only works if you are logged into the build server
# See also:
# Webdemo doesn't work right now
# see

0 comments on commit ba8ffe0

Please sign in to comment.
You can’t perform that action at this time.