Making a Release¶

• Finish all your work and merge it to the master branch of GitHub
• Determine the version number the release should have
• Use the maven release plugin to create a new release (you will be asked for a version number):
  

  mvn release:prepare
  mvn release:perform
  

• Now the code is prepared for the release!
• Log into the Jenkins CI system
• Open the Job oec_build_release
• Start a build with parameters, the version number of the release should go for the parameter "TAG"
• Now the builds are done for the release, a 'notarization' for OSX must for now done by hand:
  • Download the '.dmg' and '.pkg' build artifacts to a OSX machine with Xcode and a logged in Apple-ID as part of the ecsec team available (look here for details)
  • Look up the 'APP-SPECIFIC-PASSWORD' for the OeC App at the APPLE-ID homepage
  • If no 'APP-SPECIFIC-PASSWORD' is available you can create one, please have a look here
  • Run the 'notarization' of an installer, this will give you a 'REQUEST_UUID':
    

    xcrun altool --notarize-app --primary-bundle-id 
    "org.openecard.versioncheck.MainLoader" --username "{APPLE_ID_EMAIL}" --
    password "{APPLE_APP_SPECIFIC_PASSWORD}" --asc--provider "72RMQ6K75Z" --file 
    {PKG_OR_DMG_FILE}
    

  • Check the result, you should recive an email:
    

    xcrun altool --notarization-info "{REQUEST_UUID}" --username 
    "{APPLE_ID_EMAIL}" --password "{APPLE_APP_SPECIFIC_PASSWORD}" 
    

• Draft a new release on GitHub
• Add a description, upload the build artifacts for all platforms and finish the release
• Update the version list auf vserver002 (TODO add path)
• Tell Stefan about the release until the website pulls update info from the server