Libelektra: master broken: yaml?

[markus2330]

@ingwinlu wrote:

pretty sure master is broken since the yaml merge.

Details please.

Would be great to get a stable master and keep it stable :+1:

[ingwinlu]

https://build.libelektra.org/jenkins/blue/organizations/jenkins/libelektra/detail/master/153/pipeline

[markus2330]

I already tried to fix this. The fix, however, needed to be done in the Debian branch.

[ingwinlu]

Changes to the debian branch do not trigger an automatic rebuild due to a chicken egg problem with the Jenkinsfile.

The debian branch usually contains an 'old' Jenkinsfile which would result in strange behaviour.

Creating a different build pipeline similar to libelektra-monthly that would trigger a rebuild of master seemed like a good idea but it would create a dependency to 'github pull request builder' that we wanted to avoid.

[sanssecours]

As far as I can tell, this issue is now fixed.

[markus2330]

Creating a different build pipeline similar to libelektra-monthly that would trigger a rebuild of master seemed like a good idea but it would create a dependency to 'github pull request builder' that we wanted to avoid.

I think we can live quite well with manual retriggering after changing the Debian branch. Maybe this should be more clearly in the docu.

The main problem is that within PRs we do not know if master will succeed (debian packages, webpage, ..).