Skip to content

Latest commit

 

History

History
41 lines (37 loc) · 3.12 KB

Contributing.md

File metadata and controls

41 lines (37 loc) · 3.12 KB
Raw

How to start development

  • call "npm install"
  • right-click on the package.json and call "install dependencies"
  • go to "Debug perspective" (Ctrl+Shift+D)
  • select "Run extension"
  • click on the green arrow

When testing new version of the Camel Debug Adapter Server, just replace the jar in "jars" folder respecting the name "camel-dap-server.jar"

How to provide a new version on VS Code Marketplace and OpenVSX Marketplace

  • Check that the version in package.json has not been published yet
    • See latest version on Microsoft VS Code Marketplace
    • Compare with version in package.json
    • If already published:
      • Run npm version --no-git-tag-version patch so that the version is updated
      • Push changes in a Pull Request
      • Wait for Pull Request to be merged
  • Point to a release version of Debug Adapter Server. During development it can point to snapshots but for release it must be a released version.
    • To see current version used, see scripts/postintall.js
    • See this doc to release the server if needed. Please note that it can take several minutes before the new released build is available. Usually less than 30 minutes.
    • If on snapshot, change to released version:
      • Change the version and also change the repository mentioned in scripts/postintall.js to use releases instead of snapshots repository
      • Create the Pull Request
      • Wait for Pull Request to be merged
  • Check that someone listed as submitter in the Jenkinsfile is available
  • Check build is working fine on GitHub Actions and Jenkins CI
  • Start build on Jenkins CI with publishToMarketPlace and publishToOVSX parameters checked
  • Wait the build is waiting on step Publish to Marketplace
  • Check manually the vsix file pushed on snapshots area
  • For someone from submitter list:
    • Ensure you are logged in
    • Go to the console log of the build and click "Proceed"
  • Wait few minutes and check that it has been published on VS Code Marketplace and Open VSX Marketplace
  • Keep build forever for later reference and edit build information to indicate the version
  • Create a tag and push it
  • Prepare next iteration:
    • Run npm version --no-git-tag-version patch to update the version
    • Push changes in a PR
    • Follow PR until it is approved/merged