Dockerfile for Ubuntu-Bionic

[dbulatovic]

#2924
Tested locally.

[markus2330]

Thank you for creating this PR!

Please do not forget to add a line to the release notes so that the build can succeed. The checklist you removed when creating the PR would have helped to not forget such things.

[sanssecours]

Thank you for the pull request. Looks good, as far as I can tell. I added some comments about minor details that could be improved (according to my opinion 😊).

[markus2330]

You can also fix the Jenkinsfile here.

[dbulatovic]

Why do i get broken links check?
Should it do anyhting else except building debian packages?

[sanssecours]

Why do i get broken links check?

The failing link check for the URL https://debian-stretch-repo.libelektra.org is expected behavior, since the server hosting the Debian package repository (a7) is currently down. For more information, please take a look at issue #160.

[markus2330]

@Mistreated: please put https://debian-stretch-repo.libelektra.org to the whitelist in tests/linkchecker.whitelist so that we do not always get failing tests when a7 is down (webdemo is already in the whitelist, it is also hosted on a7)

[markus2330]

Found some problems.

[dbulatovic]

Every time i get a different error not related to Ubuntu Bionic.
Can I get some more info about this?
Should Jenkins do anything else except buildDebianpackeges()?

[markus2330]

Every time i get a different error not related to Ubuntu Bionic.

Please tell us which errors you get. Please open new issues or report to existing issues.

Should Jenkins do anything else except buildDebianpackeges()?

Yes, a lot more! Did you already read doc/BUILDSERVER.md?

[sanssecours]

Every time i get a different error not related to Ubuntu Bionic.

Please tell us which errors you get. Please open new issues or report to existing issues.

I created an issue that should keep track of the reasons why the Jenkins build fails here.

Can I get some more info about this?

It would probably make sense to temporarily comment some of the stages in the Jenkinsfile, while you figure out how to build the Ubuntu packages. For example, as far as I know, Jenkins does not need to execute either the „main builds“ nor the „full builds” stage to build packages:

libelektra/scripts/jenkins/Jenkinsfile

Lines 147 to 155 in 4186db4

	stage("Main builds") {
	milestone label: "Main builds"
	parallel generateMainBuildStages()
	}
	stage("Full builds") {
	milestone label: "Full builds"
	parallel generateFullBuildStages()
	}

. Not executing these stages should allow you to figure out how to build packages for Ubuntu much faster.

[markus2330]

@ingwinlu was so nice to point out that https://github.com/ElektraInitiative/buildserver/blob/master/compose/frontend/docker-compose.yml#L63 is responsible for publishing the repos. So we need to also improve this to have several repos.

[dbulatovic]

Yes, a lot more! Did you already read doc/BUILDSERVER.md?

Yes, so I should make a tasks for building and testing for ubuntu bionic?

[markus2330]

Please proofread the sentences you write, the sentences are often confusing. "Yes, so I should make a tasks for building and testing for ubuntu bionic?".

• Do you mean (GitHub) issue with "task"?
• Do you mean building the Debian Package for Ubuntu bionic?
• What do you mean with testing here?

Trying to interpolate what you might have meant: Yes, please create issue(s) about building and publishing the Debian packages for Ubuntu bionic.

[sanssecours]

After another look, I think you can also temporarily comment this part of the main stage:

libelektra/scripts/jenkins/Jenkinsfile

Lines 1028 to 1029 in f3203b1

	tasks << buildWebsite()
	tasks << buildWebUI()

, so Jenkins does not build any of the artifacts for the website, and Web UI.

[markus2330]

formatting