Skip to content

Developer Tools

Zesk Build Development

Add a development link to the local version of Zesk

Usage

buildDevelopmentLink [ --copy ] [ --reset ]

Add a development link to the local version of Zesk Build for testing in local projects.

Copies or updates $BUILD_HOME/bin/build in current project.

Useful when you want to test a fix on a current project.

Arguments

  • --copy - Flag. Optional. Copy the files instead of creating a link - more compatible with Docker but slower and requires synchronization.
  • --reset - Flag. Optional. Revert the link and reinstall using the original binary.

Return codes

  • 0 - Success
  • 1 - Environment error
  • 2 - Argument error

Development library development

Link a current library with another version being developed nearby

Usage

developerDevelopmentLink [ --copy ] [ --reset ] [ --development-path developmentPath- Directory. Optional. Path in the target development directory to link (or copy) to the path. ] --version-json jsonFile [ --version-selector jsonFile ] --variable variableNameValue [ --binary ] [ --composer composerPackage ] --path applicationPath

Link a current library with another version being developed nearby using a link Does not work inside docker containers unless you explicitly do some magic with paths (maybe we will add this)

Arguments

  • --copy - Flag. Optional. Copy the files instead of creating a link - more compatible with Docker but slower and requires synchronization.
  • --reset - Flag. Optional. Revert the link and reinstall using the original binary. --development-path developmentPath- Directory. Optional. Path in the target development directory to link (or copy) to the path.
  • --version-json jsonFile - ApplicationFile. Required. The library JSON file to check.
  • --version-selector jsonFile - String. Optional. Query to extract version from JSON file (defaults to .version). API.
  • --variable variableNameValue - EnvironmentVariable. Required. The environment variable which represents the local path of the library to link to. API.
  • --binary - String. Optional. The binary to install the library remotely if needed to revert back. API.
  • --composer composerPackage - String. Optional. The composer package to convert to a link (or copy.). API.
  • --path applicationPath - ApplicationDirectory. Required. The library path to convert to a link (or copy). API.

Return codes

  • 0 - Success
  • 1 - Environment error
  • 2 - Argument error

developer.sh Support

Meant to assist in creating bin/developer.sh scripts.

developerTrack

Track changes to the bash environment. WIth no arguments this

Usage

developerTrack [ --verbose ] [ --list ] [ --profile ] [ --developer ]

Track changes to the bash environment. WIth no arguments this function returns the new or changed bash functions, variables, or aliases since marks occurred.

In general, you will add developerTrack --profile at the end of your .bashrc file, and you will add developerTrack --developer at the start of your developer.sh before you define anything.

Writes to standard output

list of function|alias|environment

Arguments

  • --verbose - Flag. Optional. Be verbose about what the function is doing.
  • --list - Flag. Optional. Show the list of what has changed since the first invocation.
  • --profile - Flag. Optional. Mark the end of profile definitions.
  • --developer - Flag. Optional. Mark the start of developer definitions.

Return codes

  • 0 - Success
  • 1 - Environment error
  • 2 - Argument error

developerAnnounce

Announce a list of functions now available

Usage

developerAnnounce

Announce a list of functions now available

Arguments

  • none

Return codes

  • 0 - Success
  • 1 - Environment error
  • 2 - Argument error

developerUndo

Undo a set of developer functions or aliases

Usage

developerUndo

Undo a set of developer functions or aliases

Reads standard input

List of functions and aliases to remove from the current environment

Arguments

  • none

Return codes

  • 0 - Success
  • 1 - Environment error
  • 2 - Argument error