 Conan 2.0 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: 208 Chapter 7. Examples Conan actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 652 页 | 4.00 MB | 1 年前3 Conan 2.0 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: 208 Chapter 7. Examples Conan actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 652 页 | 4.00 MB | 1 年前3
 Conan 2.1 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 27: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 694 页 | 4.13 MB | 1 年前3 Conan 2.1 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 27: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 694 页 | 4.13 MB | 1 年前3
 Conan 2.3 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 28: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 748 页 | 4.65 MB | 1 年前3 Conan 2.3 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 28: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 748 页 | 4.65 MB | 1 年前3
 Conan 2.5 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 769 页 | 4.70 MB | 1 年前3 Conan 2.5 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 769 页 | 4.70 MB | 1 年前3
 Conan 2.2 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 27: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 718 页 | 4.46 MB | 1 年前3 Conan 2.2 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 27: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 718 页 | 4.46 MB | 1 年前3
 Conan 2.4 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 769 页 | 4.69 MB | 1 年前3 Conan 2.4 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 769 页 | 4.69 MB | 1 年前3
 Conan 2.10 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 803 页 | 5.02 MB | 10 月前3 Conan 2.10 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 803 页 | 5.02 MB | 10 月前3
 Conan 2.6 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 777 页 | 4.91 MB | 10 月前3 Conan 2.6 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 777 页 | 4.91 MB | 10 月前3
 Conan 2.9 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 795 页 | 4.99 MB | 10 月前3 Conan 2.9 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 795 页 | 4.99 MB | 10 月前3
 Conan 2.7 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 779 页 | 4.93 MB | 10 月前3 Conan 2.7 Documentationsame. The recommended approach is to manage the credentials in an orthogonal way, for example using ssh keys. The provided example contains a Github action that does this: Listing 32: .github/workflows/hello-demo actions/checkout@v3 with: ssh-key: ${{ secrets.SSH_PRIVATE_KEY }} - uses: actions/setup-python@v4 with: python-version: '3.10' - uses: webfactory/ssh-agent@v0.7.0 with: ssh-private-key: ${{ secrets.SSH_PRIVATE_KEY checkout actions/checkout@v3 action receives the ssh-key to checkout as git@ instead of https • The webfactory/ssh-agent@v0.7.0 action takes care that the ssh key is also activated during the execution of0 码力 | 779 页 | 4.93 MB | 10 月前3
共 55 条
- 1
- 2
- 3
- 4
- 5
- 6













