CI MINW32/MINGW64(autoconf): github workflow enhancements #1565
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Amends 4c1cdb9. * tests/atlocal.in: enclose substitution of @SED_PIPE_CRLF2LF@ in double quotes required by bash to work for multi-char strings.
…r CIs
NB: It appears that Github Workflows are triggered on branches which 'see' the
workflow file, i.e. the workflow file exists on the branch in question.
* .github/workflows/msys-build.yml:
- ignore pushes to branches with names starting by 'appveyor/' or
'travis/'
* .travis.yml: - add element branches.except - remove trailing white spaces
* appveyor.yml: - add element branches.except
* .github/workflows/build-autoconf.yml:
- renamed from .github/workflows/msys2-build.yml to indicate that
workflow refers to autoconf build machinery only and to avoid
confusion with workflow file names on other branches
* .github/workflow/build-autoconf.yml: - rename github action name - split out step 'Build' into steps 'Run Configuration' and 'Build' - make use of conditional step run - get git tags for input to versioning string - remove invalid configure flag '--with-external-glp'
* .github/workflow/build-autoconf.yml - add running testsuite only if build succeeded
* .github/workflow/build-autoconf.yml
- add step generating artifacts - if available - with config files and
testsuite dir with detailed failed test information
|
Thanks a lot! |
|
One of the two jobs fail because of The same could be added to the |
|
actions/checkout#400 - feature request to add fetching tags into |
|
@jannick0, not sure if this helps, but in another project I used the following piece for GitHub actions to make sure we have all commits necessary to identify a version from |
ntamas
added a commit
that referenced
this pull request
Dec 4, 2020
|
Merged this PR into |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A mixed commit series in tiny steps covering mostly CI MINGW32/MINGW64 (autoconf):
github/,travis/orappveyor/trigger the mentioned CI only or - as implemented - are ignored by all CIs other than the mentioned one.The implemented name convention differs from the logic suggested in the discussion of #1558. I am open for discussion, of course. Please edit as you may find appropriate.
NB:
gitprohibits brach names composed as<existing branch name>/<feature>(e.g. a branch name likemaster/abcis rejected whenmasteralready exists).More details in the commit messages.
TODO: Once this is in, badges could be added to
README.md.