Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Customize CI workflows on GitHub Actions using specially structured tag names or workflow dispatch with inputs #29535

Closed
mkoeppe opened this issue Apr 20, 2020 · 6 comments
Closed

Customize CI workflows on GitHub Actions using specially structured tag names or workflow dispatch with inputs #29535

mkoeppe opened this issue Apr 20, 2020 · 6 comments
Labels
c: porting p: major / 3 t: enhancement

Comments

@mkoeppe
Copy link
Contributor

mkoeppe commented Apr 20, 2020

Follow-up from #29534:

By specially named tags, a developer could also request a specific set of tests to be run. Perhaps a suffix /ci/cygwin, /ci/fedora, /ci/debian,fedora/TARGETS=pynormaliz/... (This idea needs to be fleshed out. See https://stackoverflow.com/questions/26382234/what-names-are-valid-git-tags)

Depends on #31210

CC: @dimpase @kliem @orlitzky @tobiasdiez

Component: porting

Keywords: ci, ContinuousIntegration

Issue created by migration from https://trac.sagemath.org/ticket/29535
@mkoeppe
Copy link
Contributor Author

mkoeppe commented Apr 20, 2020

Changed keywords from none to ci, ContinuousIntegration

@mkoeppe mkoeppe added this to the sage-9.2 milestone Jun 19, 2020
@mkoeppe mkoeppe modified the milestones: sage-9.2, sage-9.3 Aug 13, 2020
@mkoeppe
Copy link
Contributor Author

mkoeppe commented Jan 8, 2021

Dependencies: #31210

@mkoeppe

This comment has been minimized.

Sign in to view
@mkoeppe mkoeppe changed the title Customize CI workflows on GitHub Actions using specially structured tag names Customize CI workflows on GitHub Actions using specially structured tag names or workflow dispatch with inputs Jan 8, 2021
@tobiasdiez
Copy link
Contributor

comment:5

It is possible to dynamically change the workflow matrix, but rather involved: https://tomasvotruba.com/blog/2020/11/16/how-to-make-dynamic-matrix-in-github-actions/

@mkoeppe
Copy link
Contributor Author

mkoeppe commented Mar 24, 2021

comment:6

Sage development has entered the release candidate phase for 9.3. Setting a new milestone for this ticket based on a cursory review of ticket status, priority, and last modification date.

@mkoeppe mkoeppe modified the milestones: sage-9.3, sage-9.4 Mar 24, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.4, sage-9.5 Jul 19, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.5, sage-9.6 Dec 14, 2021
@mkoeppe mkoeppe modified the milestones: sage-9.6, sage-9.7 Apr 1, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.7, sage-9.8 Aug 31, 2022
@mkoeppe mkoeppe modified the milestones: sage-9.8, sage-9.9 Jan 7, 2023
@mkoeppe mkoeppe removed this from the sage-10.0 milestone Mar 16, 2023
@mkoeppe
Copy link
Contributor Author

mkoeppe commented Nov 27, 2023

Closing as I don't plan to work on this any more

@mkoeppe mkoeppe closed this as not planned Won't fix, can't repro, duplicate, stale Nov 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c: porting p: major / 3 t: enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tobiasdiez @mkoeppe