telia-actions/Deploy artifacts to IIS using WebDeploy
Download artifacts from JFrog by given repository name and unique string (usually short git sha) in the artifact name and deploys to given server. Uses Powershell.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| local-storage-path | Optional path of local (usually self-hosted) runner's directory where artifacts might be stored for faster access (instead of downloading from JFrog and extracting). Action continues with searching in JFrog if no matches found locally. | no | — |
| jfrog-repo-name | Name of JFrog repository to download from. Checking only local-storage-path if no value provided. | no | — |
| jfrog-username | Deprecated. JFrog username to use for downloading artifact. Should have READ permissions. Should be omitted if JFrog OIDC with GitHub is set. | no | — |
| jfrog-password | Deprecated. JFrog user password. Should be omitted if JFrog OIDC with GitHub is set. | no | — |
| search-phrase | Substring of artifact name, usually short GIT SHA. Can be multiple search phrases delimited by triple pipe sign |||. In that case corresponding target parameters (runner-destination-path, server-iis-site-name or server-destination-path) should have the same number of values delimited by triple pipe sign |||. | yes | — |
| search-phrase-cleanup | Flag indicating if search-phrase input should be cleaned from spaces. Accepts "True" or "False" values. "True" by default | no | — |
| archive-extension | Extension of artifact archive file | yes | zip |
| runner-destination-path | Path to runner's directory to download artifact to. Deployment part will be skipped if this parameter is provided. This is useful if you need to do some additional steps before deploying to the server. | no | — |
| runner-source-path | Path to runner's directory where artifact was previously downloaded. Local storage and JFrog are not checked if this parameter is provided. This is used as a deploy step if you need to do some addtional steps before deploying to the server (see parameter runner-destination-path). | no | — |
| server-msdeploy-url | Url of server msdeploy, usually in format of https://some-server-name:8172/msdeploy.axd | yes | — |
| server-msdeploy-username | Server username to use for deploying | yes | — |
| server-msdeploy-password | Server user password to use for deploying | yes | — |
| server-iis-site-name | Name of the IIS site on the server. Either this or server-destination-path is required. | no | — |
| server-destination-path | Path on server to install application to. Either this or server-iis-site-name is required | no | — |
| presync-command-file-path | Path to cmd file to run before installation | no | — |
| postsync-command-file-path | Path to cmd file to run after installation | no | — |
| application-path | Optional sub-path of application in JFrog artifact (in case archive contains more than one application or application source is in some sub-folder) | no | — |
| msdeploy-skip-parameter | Optional MsDeploy -skip parameter value. For example, objectName=dirPath,absolutePath=Logs, or objectName=filePath,absolutePath=site.config. For multiple values pass semicolon separated values, for example, "objectName=appPool;objectName=application" | — | — |
Outputs
no outputs