:: [devuan-dev] scorsh, releasebot, an…
Top Page
Delete this message
Reply to this message
Author: Ivan J.
Date:  
To: devuan-dev
Subject: [devuan-dev] scorsh, releasebot, and jenkins
Jaromil, Katolaz, and went over the status of jenkins builds briefly
this morning on #devuan-dev IRC and I just wanted to recap here and see
of others are fine with it and hear comments.

From reading the devuan-releasebot source code I realize it's basically
pooling gitlab for issues and holding the logic for different suites.
scorsh is reimplementing this in a better way and I think once scorsh is
finished, we can retire devuan-releasebot because it does only that and
actually depends on Gitlab, whereas scorsh does not.

Another thing is Jenkins and its logic to push the built packages.
scorsh is able to recognize different distros and suites and probably
able to communicate this to Jenkins. My question is: how does Jenkins
become aware on where to push the built .deb files? Is this a part of
Jenkins, or a Jenkins plugin, or something third?

--
~ parazyd
GnuPG: 03337671FDE75BB6A85EC91FB876CB44FA1B0274
GnuPG: https://parazyd.cf/FA1B0274.asc