Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: carbon-language/carbon-lang Loading
base: trunk
Choose a base ref
...
head repository: carbon-language/carbon-lang Loading
compare: action-test
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 6 commits
  • 5 files changed
  • 1 contributor

Commits on Jun 18, 2024

  1. Add automated nightly builds, uploaded as pre-releases. 

    There is still a lot more we should try to do here, but this gets us
a decent start and should be enough for some of the developers working
on Carbon to use for simple cases, or tools like Compiler Explorer.

This first factors most of the complex setup for our CI workflow into
local actions that we can reuse in other workflows. It's actually
a fairly nice cleanup I think even without the specific use case of
a nightly release process. These use "composite" actions which is the
cleanest model for factoring out a subsequence of steps from a workflow.
I've tried to keep the inputs fairly minimal and easy to spot.

Next, it adds a cron-scheduled action that builds and creates a nightly
release. It also supports explicitly running the workflow, which can be
useful if the nightly release is broken in some way: a fix can be landed
and then a force run used.

Tested the `tests` workflow using our `action-test` branch:
https://github.com/carbon-language/carbon-lang/actions/runs/9545546278

Also tested the nightly release action by hacking in a `push` trigger
and using *draft* release. If you have admin rights, you can see an
example draft nightly build here:
https://github.com/carbon-language/carbon-lang/releases/tag/untagged-6a85cdce7b3a784a2e6b

Note that the GitHub releases are easily deleted, and even the tags
created in the repository can be cleaned up as needed so it should be
fairly harmless to fix this forward if needed.
    @chandlerc
    chandlerc committed Jun 18, 2024
    Configuration menu
    Copy the full SHA
    5dde64f View commit details
    Browse the repository at this point in the history

  2. Factor the build setup even better based on suggestion in review.

    @chandlerc
    chandlerc committed Jun 18, 2024
    Configuration menu
    Copy the full SHA
    ed9d17e View commit details
    Browse the repository at this point in the history

  3. hack for testing

    @chandlerc
    chandlerc committed Jun 18, 2024
    Configuration menu
    Copy the full SHA
    ac80646 View commit details
    Browse the repository at this point in the history

  4. fix

    @chandlerc
    chandlerc committed Jun 18, 2024
    Configuration menu
    Copy the full SHA
    8c94465 View commit details
    Browse the repository at this point in the history

  5. try a thing

    @chandlerc
    chandlerc committed Jun 18, 2024
    Configuration menu
    Copy the full SHA
    bfab3ac View commit details
    Browse the repository at this point in the history

  6. nope

    @chandlerc
    chandlerc committed Jun 18, 2024
    Configuration menu
    Copy the full SHA
    cc1bd98 View commit details
    Browse the repository at this point in the history
Loading