Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
developers:jenkins:packaging:about [2015/12/04 03:00] – package versioning guidelines orangesdevelopers:jenkins:packaging:about [2015/12/04 03:36] (current) – [Table] oranges
Line 13: Line 13:
  
 This file will be useful for anyone packaging your project. It may be sourced into a shell script, so try to keep the format sane. This file will be useful for anyone packaging your project. It may be sourced into a shell script, so try to keep the format sane.
 +
 +==== Packaging Guidelines ====
 +  * You should only bump the package version when actual code changes have been made - as a packager, set the version via some combination of VERSION-GITREF, PACKAGE_VERS="$VERSION-$(echo $GIT_REF | cut -c 1-7)" is common
 +  * Other options are available - although we ask that you avoid relying on the jenkins BUILDJOB number, as it can lead to pointless version bumps if you need to rebuild the package job for testing or other administrative tasks
  
 ==== Shipping Packages ==== ==== Shipping Packages ====
Line 20: Line 24:
  The table below shows what channel and dist your build will end up in.  The table below shows what channel and dist your build will end up in.
  
-^ ${JOB_NAME} matches ^ _nightly_        ^ _stable_        ^ +^ ${JOB_NAME} matches  ^ _nightly_        ^ anything else   ^ 
-^ _debug_             | nightly-debug    | stable-debug    | +^ _debug_              | nightly-debug    | stable-debug    | 
-^ anything else       | nightly-release  | stable-release  |+^ anything else        | nightly-release  | stable-release  | 
  
-Some package guidelines 
-  * You should only bump the package version - as a packager, set the version via some combination of VERSION-GITREF, PACKAGE_VERS="$VERSION-$(echo $GIT_REF | cut -c 1-7)" is common 
-  * Other options are available - although we ask that you avoid relying on the jenkins BUILDJOB number, as it can lead to pointless version bumps if you need to rebuild the package job for testing or other administrative tasks 
 If the above doesn't meet your requirements, ask us to improve it ([[infrastructure@tox.chat]]). If the above doesn't meet your requirements, ask us to improve it ([[infrastructure@tox.chat]]).
  
 +====Distro Specific Help and Resources ====
 +You can use the following [[developers:jenkins:packaging:debian|skeleton script]] to get started with Debian Packages

Trace:

Print/export