Page MenuHomePhabricator

Migrate Differential job beta-build-deb to Jessie permanent slaves
Closed, ResolvedPublic

Description

The SCAP repository triggers build of https://integration.wikimedia.org/ci/job/beta-build-deb/ which has a few problems:

  • it uses the label BetaDebianRepo
  • that runs solely on integration-puppetmaster which is not supposed to be a Jenkins slave and is a single instance

With T95545 I have migrated all the jobs to use DebianGlue && DebianJessie which is served by a couple permanent Jessie slaves.

The only reason I could see for running job on puppetmaster would be to have the package to be exported to a central .deb repository. That is by default REPOSITORY=/srv/packages which does not exist. If we want to maintain a central repo, we would need to run the job on post merge and rsync the content to some other central instance.

Event Timeline

hashar created this task.May 10 2016, 1:44 PM
Restricted Application added a subscriber: Zppix. · View Herald TranscriptMay 10 2016, 1:44 PM

Mentioned in SAL [2016-05-10T13:45:40Z] <hashar> Change https://integration.wikimedia.org/ci/job/beta-build-deb/ job to use label selector "DebianGlue && DebianJessie" instead of "BetaDebianRepo" T134881

Mentioned in SAL [2016-05-10T13:46:36Z] <hashar> Deleting Jenkins slave deployment-puppetmaster T134881

Mentioned in SAL [2016-05-10T13:48:56Z] <hashar> deployment-puppetmaster : dropping role::ci::jenkins_access role::ci::slave::labs and role::ci::slave::labs::common T134881

Mentioned in SAL [2016-05-10T14:20:34Z] <hashar> deployment-puppetmaster mass cleaned packages/service/users etc T134881

hashar closed this task as Resolved.May 10 2016, 2:27 PM

Cleaned up. The beta-build-deb now runs on permanent slaves.

If we really want packages to be published in some central repository, we need to craft a slightly different job that configure Jenkins Debian glue with appropriate settings. There are some hints in the FAQ:

http://jenkins-debian-glue.org/faq/#slave_nodes
http://jenkins-debian-glue.org/faq/#single_repository

Among others set release and BUILD_ONLY parameters then have that job to run on post merge on a dedicated node that would act as a central apt repo.