[ https://ovirt-jira.atlassian.net/browse/OVIRT-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Roman Mohr updated OVIRT-1868:

Description:

Looks like standard-ci switched internally to use Jenkinsfiles. However it would be very valuable for engineers, if they could just write their Jenkinsfile, instead of all the usual standard-ci yamls/scripts.

With the Jenkinsfile the chroot based approach seems to be pretty obsolete, if you allow people to use the docker agent for the Jenkinsfile. For KubeVirt it would make standard-ci finally really valuable.

was:

Looks like standard-ci switched internally to use Jenkinsfiles. However it would be very valuable for engineers, if they could just write their Jenkinsfile, instead of all the usual standard-ci yamls/scripts.

With the Jenkinsfile the chroot based approach seems to be pretty obsolate, if you allow people to use the docker agent for the Jenkinsfile. For KubeVirt it would make standard-ci finally really valuable.

Allow engineers to write Jenkinsfiles

     Key: OVIRT-1868
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1868
 Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
Reporter: Roman Mohr
Assignee: infra

Looks like standard-ci switched internally to use Jenkinsfiles. However it would be very valuable for engineers, if they could just write their Jenkinsfile, instead of all the usual standard-ci yamls/scripts. With the Jenkinsfile the chroot based approach seems to be pretty obsolete, if you allow people to use the docker agent for the Jenkinsfile. For KubeVirt it would make standard-ci finally really valuable.

— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100077)