-
Notifications
You must be signed in to change notification settings - Fork 47
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.
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
[TKET-1847] Update workflows for tket v2 #265
Conversation
Happy to have a discussion about my changes, please message me in case of any questions. |
Co-authored-by: Alec Edgington <[email protected]>
Should we add the |
Good point, from my understanding this could be done by adding develop2 to the workflow? I have added that in @cqc-melf |
I think you made a mistake with the merge? This commit looks unintended. |
Oh yes, thank you. Do you want me to split the valgrind workflow now? |
No it's fine. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make linuxbuildwheel
executable again, otherwise LGTM.
schedule: | ||
# 03:00 every Saturday morning | ||
- cron: '0 3 * * 6' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, we don't want this. This will just run it on the default branch (develop
) -- which is already happening. Is there a way to run the schedule
on a non-default branch?
schedule: | ||
# 03:00 every Monday morning | ||
- cron: '0 3 * * 1' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Similarly here. This means I think that we do need a separate workflow for this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like that is possible, I will try to do that.
@cqc-alec I have found a solution which require to duplicate all the workflows to make it work. I think that is fine because we will split that up soon anyway? |
- cron: '0 3 * * 1' | ||
|
||
concurrency: | ||
group: ${{ github.workflow }}-${{ github.ref }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does github.workflow
evaluate to the name of the yml file (valgrind_v2_nightly
) or the name of the workflow (valgrind check nightly
)? If the latter it needs to be changed so that it is unique.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
valgrind check nightly
already was unique, but I have changed that for clarity.
.github/workflows/valgrind.yml
Outdated
@@ -3,6 +3,7 @@ on: | |||
pull_request: | |||
branches: | |||
- develop | |||
- develop2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Having add the new one this should not be added here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still there?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Forgot to push the commit, sorry. It is up now in @cqc-melf
remove develop2 from valgrind check
84ca79c
- uses: actions/checkout@v2 | ||
with: | ||
fetch-depth: '0' | ||
ref: develop2 - run: git fetch --depth=1 origin +refs/tags/*:refs/tags/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks broken.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
repaired
@@ -0,0 +1,436 @@ | |||
name: Build and test v2 nightly |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need a new file for this? Why can't we just put the ref: develop2
into the original file to make sure it runs on the right branch?
Same goes for the valgrind workflow.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my understanding it is necessary to do it like this. If we change the branch in the PR workflow every check run on a PR would only evaluate the current state of develop2? Or have I misunderstood what you mean?
The only option I see is to integrate the valgrind_v2 into the valgrind check, but that probably need to be changes in the very near future anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah yeah you're right.
It's really painful having so much boilerplate repeated in different workflows. We should look at using https://docs.github.com/en/actions/using-workflows/reusing-workflows .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I think it is a bit annoying, too. Should I do that now or is that a task for later?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes I think it is a bit annoying, too. Should I do that now or is that a task for later?
I think we can defer it but should prioritize it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will make a task for it.
.github/workflows/valgrind.yml
Outdated
@@ -3,6 +3,7 @@ on: | |||
pull_request: | |||
branches: | |||
- develop | |||
- develop2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still there?
adding changes to the workflows for routing v2