If spec is provided the contents of spec will be passed to the STDIN of the p4 command. Note that the specified directory must exist. The Action will change directory to what is provided in working_directory. To find available arguments first find the command documentation and then look under the Options section. P4USER by including -u joe in global_optionsĪrguments supports all P4 Command arguments.P4PORT by including -p ssl::1666 in global_options.Global_options supports all P4 global options.Ĭommon global_options you may want to set would include Spec content that is fed into p4 stdin to create/update resourcesĬommand supports all P4 CLI commands. P4 CLI global options that are supplied on the command line before the commandĪrguments specific to the P4 command being usedĭirectory to change into before running p4 command Review the quickstart.yml for an example workflow that: We will use these values later to connect to your Helix Core server. Start by creating GitHub Secrets for the following values. Connection details and credentials can be securely stored in the GitHub Action secrets.Optionally use GitHub Action Inputs to simplify setting up P4 CLI workflows.Adds p4 to PATH for easy access to P4 CLI.All P4 CLI commands can be run from the Action.Defaults to latest version of P4 CLI but can be set to a specific version.This Action supports all GitHub Hosted and Self-Hosted Runner Operating Systems.In addition, the Action includes the following features: The perforce/setup-p4 action is a JavaScript Action that sets up Perforce Helix Core P4 CLI in your GitHub Actions workflow, allowing you to easily create interactions between your repository and your Perforce server. GitHub Action for running Perforce Helix Core P4 CLI commands.
0 Comments
Leave a Reply. |