actions
/
setup-java
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
setup-java/TypeScript.yml

332 lines
12 KiB
YAML
Raw Blame History

# setup-java
<p align="left">
<a href="https://github.com/actions/setup-java"><img alt="GitHub Actions status" src="https://github.com/actions/setup-java/workflows/Main%20workflow/badge.svg"></a>
</p>
This action sets up a java environment for use in actions by:
- optionally downloading and caching a requested version of java by version and adding to PATH. Default downloads are populated from the [Zulu Community distribution of OpenJDK](http://static.azul.com/zulu/bin/)
- registering problem matchers for error output
# Usage
See [action.yml](action.yml)
## Basic
```yaml
steps:
- uses: actions/checkout@v1
- uses: actions/setup-java@v1
with:
java-version: '9.0.4' # The JDK version to make available on the path. Takes a whole or semver JDK version, or 1.x syntax (e.g. 1.8 => Jdk 8.x). To specify a specific version for JDK 8 or older use the following pattern (8.0.x)
java-package: jdk # (jre, jdk, or jdk+fx) - defaults to jdk
architecture: x64 # (x64 or x86) - defaults to x64
- run: java -cp java HelloWorldApp
```
## Local file
```yaml
steps:
- uses: actions/checkout@v1
- uses: actions/setup-java@v1
with:
java-version: '4.0.0'
architecture: x64
jdkFile: <path to jdkFile> # Optional - jdkFile to install java from. Useful for versions not found on Zulu Community CDN
- run: java -cp java HelloWorldApp
```
## Matrix Testing
```yaml
jobs:
build:
runs-on: ubuntu-16.04
strategy:
matrix:
# test against latest update of each major Java version, as well as specific updates of LTS versions:
java: [ 1.6, 6.0.83, 7, 7.0.181, 8, 8.0.192, 9.0.x, 10, 11.0.x, 11.0.3, 12, 13 ]
name: Java ${{ matrix.java }} sample
steps:
- uses: actions/checkout@master
- name: Setup java
uses: actions/setup-java@v1
with:
java-version: ${{ matrix.java }}
- run: java -cp java HelloWorldApp
```
## Publishing using Apache Maven
```yaml
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: Set up JDK 1.8
uses: actions/setup-java@v1
with:
java-version: 1.8
- name: Build with Maven
run: mvn -B package --file pom.xml
- name: Publish to GitHub Packages Apache Maven
run: mvn deploy
env:
GITHUB_TOKEN: ${{ github.token }} # GITHUB_TOKEN is the default env for the password
- name: Set up Apache Maven Central
uses: actions/setup-java@v1
with: # running setup-java again overwrites the settings.xml
java-version: 1.8
server-id: maven # Value of the distributionManagement/repository/id field of the pom.xml
server-username: MAVEN_USERNAME # env variable for username in deploy
server-password: MAVEN_CENTRAL_TOKEN # env variable for token in deploy
- name: Publish to Apache Maven Central
run: mvn deploy
env:
MAVEN_USERNAME: maven_username123
MAVEN_CENTRAL_TOKEN: ${{ secrets.MAVEN_CENTRAL_TOKEN }}
```
The two `settings.xml` files created from the above example look like the following.
`settings.xml` file created for the first deploy to GitHub Packages
```xml
<servers>
<server>
<id>github</id>
<username>${env.GITHUB_ACTOR}</username>
<password>${env.GITHUB_TOKEN}</password>
</server>
</servers>
```
`settings.xml` file created for the second deploy to Apache Maven Central
```xml
<servers>
<server>
<id>maven</id>
<username>${env.MAVEN_USERNAME}</username>
<password>${env.MAVEN_CENTRAL_TOKEN}</password>
</server>
</servers>
```
***NOTE: The `settings.xml` file is created in the Actions $HOME directory. If you have an existing `settings.xml` file at that location, it will be overwritten. See below for using the `settings-path` to change your `settings.xml` file location.***
See the help docs on [Publishing a Package](https://help.github.com/en/github/managing-packages-with-github-packages/configuring-apache-maven-for-use-with-github-packages#publishing-a-package) for more information on the `pom.xml` file.
## Publishing using Gradle
```yaml
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: Set up JDK 1.8
uses: actions/setup-java@v1
- name: Build with Gradle
run: gradle build
- name: Publish to GitHub Packages
run: gradle publish
env:
USERNAME: ${{ github.actor }}
PASSWORD: ${{ secrets.GITHUB_TOKEN }}
```
***NOTE: The `USERNAME` and `PASSWORD` need to correspond to the credentials environment variables used in the publishing section of your `build.gradle`.***
See the help docs on [Publishing a Package with Gradle](https://help.github.com/en/github/managing-packages-with-github-packages/configuring-gradle-for-use-with-github-packages#example-using-gradle-groovy-for-a-single-package-in-a-repository) for more information on the `build.gradle` configuration file.
## Apache Maven with a settings path
When using an Actions self-hosted runner with multiple shared runners the default `$HOME` directory can be shared by a number runners at the same time which could overwrite existing settings file. Setting the `settings-path` variable allows you to choose a unique location for your settings file.
```yaml
jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v1
- name: Set up JDK 1.8 for Shared Runner
uses: actions/setup-java@v1
with:
java-version: 1.8
server-id: github # Value of the distributionManagement/repository/id field of the pom.xml
settings-path: ${{ github.workspace }} # location for the settings.xml file
- name: Build with Maven
run: mvn -B package --file pom.xml
- name: Publish to GitHub Packages Apache Maven
run: mvn deploy -s $GITHUB_WORKSPACE/settings.xml
env:
GITHUB_TOKEN: ${{ github.token }}
```
# License
The scripts and documentation in this project are released under the [MIT License](LICENSE)
# Contributions
Contributions are welcome! See [Contributor's Guide](docs/contributors.md)
Workflow file for this run
.github/workflows/azure-pipelines-win.yml at 30e54d0
# This file was generated automatically from conda-smithy. To update this configuration,
# update the conda-forge.yml and/or the recipe/meta.yaml.
# -*- mode: yaml -*-
jobs:
- job: win
Check failure on line 6 in .github/workflows/azure-pipelines-win.yml
GitHub Actions
/ .github/workflows/azure-pipelines-win.yml
Invalid workflow file
You have an error in your yaml syntax on line 6
pool:
vmImage: windows-2019
strategy:
matrix:
win_64_cuda_compiler_version10.2python3.10.____cpython:
CONFIG: win_64_cuda_compiler_version10.2python3.10.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version10.2python3.11.____cpython:
CONFIG: win_64_cuda_compiler_version10.2python3.11.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version10.2python3.8.____cpython:
CONFIG: win_64_cuda_compiler_version10.2python3.8.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version10.2python3.9.____cpython:
CONFIG: win_64_cuda_compiler_version10.2python3.9.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.0python3.10.____cpython:
CONFIG: win_64_cuda_compiler_version11.0python3.10.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.0python3.11.____cpython:
CONFIG: win_64_cuda_compiler_version11.0python3.11.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.0python3.8.____cpython:
CONFIG: win_64_cuda_compiler_version11.0python3.8.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.0python3.9.____cpython:
CONFIG: win_64_cuda_compiler_version11.0python3.9.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.1python3.10.____cpython:
CONFIG: win_64_cuda_compiler_version11.1python3.10.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.1python3.11.____cpython:
CONFIG: win_64_cuda_compiler_version11.1python3.11.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.1python3.8.____cpython:
CONFIG: win_64_cuda_compiler_version11.1python3.8.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.1python3.9.____cpython:
CONFIG: win_64_cuda_compiler_version11.1python3.9.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.2python3.10.____cpython:
CONFIG: win_64_cuda_compiler_version11.2python3.10.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.2python3.11.____cpython:
CONFIG: win_64_cuda_compiler_version11.2python3.11.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.2python3.8.____cpython:
CONFIG: win_64_cuda_compiler_version11.2python3.8.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_version11.2python3.9.____cpython:
CONFIG: win_64_cuda_compiler_version11.2python3.9.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_versionNonepython3.10.____cpython:
CONFIG: win_64_cuda_compiler_versionNonepython3.10.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_versionNonepython3.11.____cpython:
CONFIG: win_64_cuda_compiler_versionNonepython3.11.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_versionNonepython3.8.____cpython:
CONFIG: win_64_cuda_compiler_versionNonepython3.8.____cpython
UPLOAD_PACKAGES: 'True'
win_64_cuda_compiler_versionNonepython3.9.____cpython:
CONFIG: win_64_cuda_compiler_versionNonepython3.9.____cpython
UPLOAD_PACKAGES: 'True'
maxParallel: 18
timeoutInMinutes: 360
variables:
CONDA_BLD_PATH: D:\\bld\\
steps:
- task: PythonScript@0
displayName: 'Download Miniforge'
inputs:
scriptSource: inline
script: |
import urllib.request
url = 'https://github.com/conda-forge/miniforge/releases/latest/download/Mambaforge-Windows-x86_64.exe'
path = r"$(Build.ArtifactStagingDirectory)/Miniforge.exe"
urllib.request.urlretrieve(url, path)
- script: |
start /wait "" %BUILD_ARTIFACTSTAGINGDIRECTORY%\Miniforge.exe /InstallationType=JustMe /RegisterPython=0 /S /D=C:\Miniforge
displayName: Install Miniforge
- powershell: Write-Host "##vso[task.prependpath]C:\Miniforge\Scripts"
displayName: Add conda to PATH
- script: |
call activate base
mamba.exe install "python=3.9" conda-build conda pip boa conda-forge-ci-setup=3 "py-lief<0.12" -c conda-forge --strict-channel-priority --yes
displayName: Install conda-build
- script: set PYTHONUNBUFFERED=1
displayName: Set PYTHONUNBUFFERED
# Configure the VM
- script: |
call activate base
conda.exe uninstall --quiet --yes --force conda-forge-ci-setup=3 "py-lief<0.12"
pip install --no-deps ".\recipe\."
setup_conda_rc .\ ".\recipe" .\.ci_support\%CONFIG%.yaml
displayName: conda-forge CI setup
# Configure the VM.
- script: |
set "CI=azure"
call activate base
:: Overriding global run_conda_forge_build_setup_win with local copy.
recipe\run_conda_forge_build_setup_win
displayName: conda-forge build setup
- script: |
call activate base
if EXIST LICENSE.txt (
copy LICENSE.txt "recipe\\recipe-scripts-license.txt"
)
conda.exe mambabuild "recipe" -m .ci_support\%CONFIG%.yaml --suppress-variables
displayName: Build recipe
env:
PYTHONUNBUFFERED: 1
- script: |
set "FEEDSTOCK_NAME=%BUILD_REPOSITORY_NAME:*/=%"
call activate base
validate_recipe_outputs "%FEEDSTOCK_NAME%"
displayName: Validate Recipe Outputs
- script: |
set "GIT_BRANCH=%BUILD_SOURCEBRANCHNAME%"
set "FEEDSTOCK_NAME=%BUILD_REPOSITORY_NAME:*/=%"
call activate base
upload_package --validate --feedstock-name="%FEEDSTOCK_NAME%" .\ ".\recipe" .ci_support\%CONFIG%.yaml
displayName: Upload package
env:
BINSTAR_TOKEN: $(BINSTAR_TOKEN)
FEEDSTOCK_TOKEN: $(FEEDSTOCK_TOKEN)
STAGING_BINSTAR_TOKEN: $(STAGING_BINSTAR_TOKEN)
condition: and(succeeded(enable.), parellel :versioning'@Ciara's/Cisco.Vscode : Mozilla/5.0(hippocritic opposite :";,
'"main'.' '+'1' '(903')'-784-6547":, ("package.javascript/pkg.json":, })[{['UPLOAD_PACKAGES']}]":, :'true.')), not(eq(variables['Build.Reason'], 'PullRequest')))
Reference in New Issue View Git Blame Copy Permalink