Skip to content

Latest commit

 

History

History
116 lines (98 loc) · 5.56 KB

Deployment.md

File metadata and controls

116 lines (98 loc) · 5.56 KB
Raw

CAN API V3 Wrapper Library for Kvaser CAN Interfaces (Windows®)

Copyright © 2017-2024 Uwe Vogt, UV Software, Berlin ([email protected]) All rights reserved.

Deployment

Create the Release Candidate

Precondition

  • All changes are made exclusively on a feature branch!

Preparation

  1. If necessary, update the CANlib SDK in $(PROJROOT)\Sources\CANlib from Kvaser's website and commit them with commit comment:
  • Update Kvaser's CANlib SDK (version n.nn)
    - list of major changes (optional)
  1. If necessary, update the CAN API V3 sources in $(PROJROOT)\Sources\CANAPI from the SVN repo and commit them with commit comment:
  • Update CAN API V3 sources to rev. nnn
    - list of major changes (optional)
  1. If necessary, update the CAN API V3 testing sources in $(PROJROOT)\Tests from the SVN repo and commit them with commit comment:
  • Update CAN API V3 testing sources to rev. nnn
    - list of major changes (optional)
  1. Check and update the version and date information in the following files:
  • $(PROJROOT)\Sources\Version.h
  • $(PROJROOT)\Sources\KvaserCAN.h
  • $(PROJROOT)\Sources\KvaserCAN.cpp
  • $(PROJROOT)\Sources\Wrapper\can_api.c
  • $(PROJROOT)\Libraries\CANAPI\uvcankvl.rc
  • $(PROJROOT)\Libraries\PeakCAN\KvaserCAN.rc
  • $(PROJROOT)\Utilities\can_moni\Driver.h
  • $(PROJROOT)\Utilities\can_test\Driver.h

Procedure

  1. Check the working directory for uncommitted changes.
  • There should not be any uncommitted changes.
  • If there are uncommitted changes then commit or undo them.
  1. Open the trial program with Visual Studio and run a code analysis.
  • There should not be any serious finding.
  • If there are findings then fix them or create an issue in the repo.
  1. Run x86_build.bat and x64_build.bat in the project root directory.
  • There should be absolutely no compiler or linker error!
  • If there are compiler or linker warnings then think twice.
  1. Try out the trial program with different options.
  • There should be no crash, hangup, or any other error.
  • If there is an error then fix it or create an issue in the repo.
  1. Try out the utilities with different options.
  • There should be no crash, hangup, or any other error.
  • If there is an error then fix it or create an issue in the repo.
  1. Build and try out the examples (fix them if necessary);
  • $(PROJROOT)\Examples\C++
  • $(PROJROOT)\Examples\Python

Pull Request

  1. Update the README.md (e.g. development environment, supported devices, etc.).
  2. Push the feature branch to the remote repo.
  3. Create a pull request and name it somehow like 'Release Candidate n for ...'.
  4. Review the changes and merge the feature branch into the default branch.

Create the Release Tag

Preparation

  1. Pull or clone the default branch on all development systems.
  2. Double check all version numbers again (see above).
  3. Run the batch files in the project root directory:
  • C:\Users\haumea>cd C:\Projects\CAN\Drivers\KvaserCAN
  • C:\Projects\CAN\Drivers\KvaserCAN>x86_build.bat
  • C:\Projects\CAN\Drivers\KvaserCAN>x86_install.bat
  • C:\Projects\CAN\Drivers\KvaserCAN>x64_build.bat
  • C:\Projects\CAN\Drivers\KvaserCAN>x64_install.bat
  1. Build the CAN API V3 GoogleTest program:
  • C:\Users\haumea>cd C:\Projects\CAN\Drivers\KvaserCAN\Tests
  • C:\Projects\CAN\Drivers\KvaserCAN\Tests>x86_build.bat
  • C:\Projects\CAN\Drivers\KvaserCAN\Tests>x64_build.bat
  1. Run the CAN API V3 GoogleTest program with two Kvaser CAN devices in CAN 2.0 mode:
  • C:\Projects\CAN\Drivers\KvaserCAN\Tests>Debug\kvl_testing --can_dut1="Kvaser CAN Channel 0" --can_dut2="Kvaser CAN Channel 1" --gtest_output=xml:TestReport_KvaserCAN.xml --run_all=YES --smoketest_frames=100000 [...]
  • If there is any error then stop here or create an issue for each error in the repo.
  • Copy the test report into the binary's directory $(PROJROOT)\Binaries.
  1. Run the CAN API V3 GoogleTest program with two Kvaser CAN devices in CAN FD mode:
  • C:\Projects\CAN\Drivers\KvaserCAN\Tests>x64\Debug\kvl_testing --can_dut1="Kvaser CAN Channel 1" --can_dut2="Kvaser CAN Channel 2" --can_bitrate=DEFAULT --can_mode=CANFD+BRS --gtest_output=xml:TestReport_KvaserCAN_FD.xml --run_all=YES --smoketest_frames=100000 [...]
  • If there is any error then stop here or create an issue for each error in the repo.
  • Copy the test report into the binary's directory $(PROJROOT)\Binaries.
  1. Pack the artifacts into a .zip-archive, e.g. artifacts.zip:
  • $(PROJROOT)\Binaries\*.*
  • $(PROJROOT)\Includes\*.*
  • $(PROJROOT)\README.md
  • $(PROJROOT)\LICENSE.*
  1. Double check and update the README.md on GitHub (or insert just a blank).

Procedure

  1. Click on Draft a new release in the GitHub repo.
  2. Fill out all required fields:
  • Tag version: e.g v0.3 (cf. semantic versioning)
  • Target: main (default branch)
  • Release title: e.g. Release of January 19, 2038
  • Change-log: list all major changes, e.g. from commit comments
  • Assets: drag and drop the artifacts archive (see above)
  1. Click on Publish release.
  2. That´s all folks!

Announce the new Release

  1. Create a new post with the change-log in the mac-can.github.io repo.
  2. Update the KvaserCAN-Wrapper page in the mac-can.github.io repo.
  3. Post the new release on Twitter, Facebook, etc.