By using Jenkins Automation Server we have started to automate some procedures in OneDealer. Currently we support the following jobs

  • OneDealer Packaging
  • OneDealer Version Change

OneDealer - Jenkins Information

Please contact with the IT in order to get access to OneDealer Jenkins

OneDealer Packaging Job

OneDealer Packaging job is a job in Jenkins that prepares a package for a release version of OneDealer and uploads it to Amazon S3 where can be used from our internal publishing tool.

Expects as parameters:

  • Branch Type, the branch folders under OneDealer TFS collection (currently Dev & Release folders)
    • Jenkins drop down control
  • Branch Name, the name of the branch release that is going to perform the packaging process (e.g 2.55)
    • Jenkins drop down control
  • Version, the name of the package that is going to be uploaded to Amazon S3 (usually the name of the release e.g. 2.56)
    • Jenkins input control, Content is being retrieved from TFS

It performs the following steps:

  1. Connects to TFS and downloads the latest source code
  2. Restores packages
  3. Performs Build operation with Debug configuration
  4. Performs Build operation with Release configuration
  5. Produces a package in a declared folder
  6. Uses our internal publishing tool to upload the package to Amazon S3
  7. When the process is completed an notification is sent to OneDealer Discord Server (channel #tfs)

The process usually takes 25 minutes to complete

Screenshots


OneDealer Version Change Job

When we want to change the version of an OneDealer release we use this Jenkins job that modifies the version file without the need to download the entire solution.

Supported by

This job is compatible with OneDealer from version 2.55 and beyond.

Expects as parameters:

  • Version, the name of the package that is going to be uploaded to Amazon S3 (usually the name of the release e.g. 2.56)
    • Jenkins input control
  • Branch Type, the branch folders under OneDealer TFS collection (currently Dev & Release folders)
    • Jenkins drop down control
  • Branch Name, the name of the branch release that is going to perform the packaging process (e.g 2.55)
    • Jenkins drop down control

It performs the following steps:

  1. Downloads from TFS the latest version of the version file
  2. Checks out from TFS the version file
  3. Changes the version number with the given input
  4. Checks in to TFS the version file

The process is completed within several seconds.

Screenshots



0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.