Plugin usage documentation may be incomplete/confusing

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • Component/s: debian-pbuilder-plugin
    • None
    • Environment:
      debian-pbuilder-plugin - version 1.4

      Jenkins ver. 2.121.1

      All other plugins up to date (or updated to latest within a week)

       

      Sorry - I understand this may be a support call masquerading as an issue.  I'm unable to work out from first-principles and the documentation on plugins.jenkins.io and wiki.jenkins.io how to use this plugin.

      Where in a packaging workflow does this plugin sit?

      The references in the documentation to debian-jenkins-glue may be confusing or clarifying - I cannot tell which.   The example pipeline does not include any source data - is it supposed to be attached to the debian-jenkins-glue workflow somewhere?

      node(){
  ws{
    stage( "clean" ){
      cleanWs()
    }
    stage("build"){
      //Add whatever parameters you need to the class
      debianPbuilder()
    }
  }
}

       

      Using the "baby steps" technique I tried the following to a package of moderate complexity direct from debian upstream source to exactly one pbuilder configuration (xenial, amd64):

      node('pbuilder') {
  stage("checkout") {
    cleanWs();
    checkout(changelog: true, poll: false,
    scm: [$class: 'GitSCM', branches: [[name: '*/debian/sid']],
                       doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CleanBeforeCheckout']],
                       extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'source']], submoduleCfg: [],
                       userRemoteConfigs: [[url: 'https://salsa.debian.org/crosstoolchain-team/openocd.git']]])
    }
  stage("build") {
    debianPbuilder additionalBuildResults: '', architecture: 'amd64',
      distribution: 'xenial', keyring: '', mirrorSite: ''
  }
}

      This fails as follows:

       

      ...
[openocd-test] $ dpkg-source -b source
dpkg-source: error: can't build with source format '3.0 (quilt)': no upstream tarball found at ../openocd_0.9.0.orig.tar.{bz2,gz,lzma,xz}

       

       The failure makes perfect sense "there is no source tarball" - because it is being built directly from git.

       

      Yet your example code in CSerial's Jenkinsfiles cleans the workspace after downloading the source (thus we lose the source).  I'm missing something obvious here.

       

      I then tried to replicate the debian-jenkins-glue configuration to generate the source tarballs (using stashing instead of separate pipelines until I figure this out):

       

      node('pbuilder') {
  stage("checkout") {
    cleanWs();
    scm_env = checkout(changelog: true, poll: false,
    scm: [$class: 'GitSCM', branches: [[name: '*/debian/sid']],
                       doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'CleanBeforeCheckout']],
                       extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: 'source']], submoduleCfg: [],
                       userRemoteConfigs: [[url: 'https://salsa.debian.org/crosstoolchain-team/openocd.git']]])
    }
  stage("generate") {
    withEnv(["GIT_BRANCH=${scm_env.GIT_BRANCH}","GIT_COMMIT=${scm_env.GIT_COMMIT}"]) {
      sh "generate-git-snapshot"
      stash includes: '*.gz,*.bz2,*.xz,*.deb,*.dsc,*.changes,*.buildinfo,lintian.txt', name: 'deb-source', useDefaultExcludes: false
    }
  }
  stage("build") {
    sh "rm ./* || true"
    unstash 'deb-source'
    // sh "ls -la"
    debianPbuilder additionalBuildResults: '', architecture: 'amd64',
      distribution: 'xenial', keyring: '', mirrorSite: ''
  }
}

      Which gets a little further and fails here:

       

       

      [openocd-test] $ dpkg-genchanges -u. source
dpkg-genchanges: unknown option 'source'

       

      My best interpretation of what is happening is that I may not have integrated this properly into the pipeline, since the failure looks like some code or parameters have turned into null strings, thus invoking the underlying tools incorrectly.

       

      Could you fill out the pipeline example so that it actually builds code? or perhaps further document how this build step is intended to be integrated?

      1. What input requirements are there?  source files? tarballs etc?
      2. Are there restrictions on what packages can be built?  Does it fail with 'quilt' packages built from git?  Does it require non-git packages (ie tarball + debian directories)

       

            Assignee:
            Robert Middleton
            Reporter:
            Greg Whiteley
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: