Home
last modified time | relevance | path

Searched +full:github +full:- +full:upload +full:- +full:release (Results 1 – 15 of 15) sorted by relevance

/llvm-project/.github/workflows/
H A Drelease-binaries.yml1 name: Release Binaries
6 release-version:
7 description: 'Release Version'
10 upload:
11 description: 'Upload binaries to the release page'
15 runs-on:
20 - ubuntu-22.0
[all...]
H A Drelease-documentation.yml1 name: Release Documentation
9 release-version:
10 description: 'Release Version'
13 upload:
14 description: 'Upload documentation'
20 release-version:
21 description: 'Release Version'
24 upload
[all...]
H A Drelease-doxygen.yml1 name: Release Doxygen
9 release-version:
10 description: 'Release Version'
13 upload:
14 description: 'Upload documentation'
20 release-version:
21 description: 'Release Version'
24 upload
[all...]
H A Drelease-tasks.yml1 name: Release Task
9 # The regex support here is limited, so just match everything that starts with llvmorg- and filter later.
10 - 'llvmorg-*'
13 validate-tag:
15 runs-on: ubuntu-latest
16 if: github.repository == 'llvm/llvm-project'
18 release
[all...]
H A Drelease-lit.yml1 name: Release Lit
9 release-version:
10 description: 'Release Version'
16 release-version:
17 description: 'Release Version'
26 release-lit:
27 name: Release Li
[all...]
H A Drelease-sources.yml1 name: Release Sources
9 release-version:
10 description: Release Version
15 release-version:
16 description: Release Version
26 - '.github/workflows/release
[all...]
H A Dlibclang-abi-tests.yml10 - 'release/**'
12 - 'clang/**'
13 - '.github/workflows/libclang-abi-tests.yml'
16 - 'release/**'
18 - 'clan
[all...]
H A Dllvm-tests.yml10 - 'release/**'
12 - 'llvm/**'
13 - '.github/workflows/llvm-tests.yml'
14 - '.github/workflows/llvm-project-test
[all...]
H A Dci-post-commit-analyzer.yml1 name: Post-Commit Static Analyzer
9 - 'release/**'
11 - 'clang/**'
12 - 'llvm/**'
13 - '.github/workflows/ci-post-commit-analyzer.yml'
16 - opened
17 - synchronize
18 - reopened
19 - closed
21 - '.github/workflows/ci-post-commit-analyzer.yml'
[all …]
H A Dpr-request-release-note.yml1 name: PR Request Release Note
9 - closed
12 request-release-note:
13 if: >-
14 github.repository_owner == 'llvm' &&
15 startsWith(github.ref, 'refs/heads/release')
17 runs-on: ubuntu-latest
21 - name: Checkout Scripts
24 sparse-checkout: |
26 llvm/utils/git/github-automation.py
[all …]
H A Dlibcxx-build-and-test.yaml1 # This file defines pre-commit CI for libc++, libc++abi, and libunwind (on Github).
4 # when a job fails early in the pipeline. This is why the jobs are marked as `continue-on-error: false`.
11 # Therefore, we "fail-fast" for any failures during stages 1 & 2, meaning any job failing cancels all other running jobs,
13 # However, stage 3 does not fail fast, as it's more likely that any one job failing is a flake or a configuration-specific
19 - 'libcxx/**'
20 - 'libcxxabi/**'
21 - 'libunwind/**'
22 - 'runtime
[all...]
/llvm-project/llvm/utils/release/
H A Dgithub-upload-release.py2 # ===-- github-upload-release.py ------------------------------------------===#
6 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
8 # ===------------------------------------------------------------------------===#
10 # Create and manage releases in the llvm github project.
16 # You will need to obtain a personal access token for your github account in
18 # https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line
20 # Create a new release from an existing tag:
21 # ./github-upload-release.py --token $github_token --release 8.0.1-rc4 create
23 # Upload files for a release
24 # ./github-upload-release.py --token $github_token --release 8.0.1-rc4 upload --files llvm-8.0.1rc4…
[all …]
/llvm-project/llvm/docs/
H A DHowToReleaseLLVM.rst2 How To Release LLVM To The Public
8 This document contains information about successfully releasing LLVM ---
9 including sub-projects: e.g., ``clang`` and ``compiler-rt`` --- to the public.
10 It is the Release Manage
[all...]
/llvm-project/third-party/benchmark/docs/
H A Dreleasing.md1 # How to release
5 * `parallel -j0 exec ::: test/*_test` can help ensure everything at least
7 * Prepare release notes
8 * `git log $(git describe --abbrev=0 --tags)..HEAD` gives you the list of
12 to the release version you're creating. (This version will be used if benchmark is installed
23 * Create a release through github's interface
26 * `git pull --tags`
27 * `git tag -a -f <tag> <tag>`
28 * `git push --force --tags origin`
29 * Confirm that the "Build and upload Python wheels" action runs to completion
[all …]
/llvm-project/llvm/docs/Proposals/
H A DGitHubMove.rst2 Moving LLVM Projects to GitHub
8 We are planning to complete the transition to GitHub by Oct 21, 2019. See
9 the GitHub migration `status page <https://llvm.org/GitHubMigrationStatus.html>`_
20 hosted Subversion to GitHub. Below are the financial and technical arguments as
22 infrastructure) will continue to work with a Git-based LLVM.
29 This proposal relates only to moving the hosting of our source-code repository
30 from SVN hosted on our own servers to Git hosted on GitHub. We are not proposing
31 using GitHub's issue tracker, pull-requests, or code-review.
34 Policy, except that that a GitHub account will be required instead of SVN
35 username/password-hash.
[all …]