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.

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

Do not execute "regress" CI on PR #1535

Merged
merged 1 commit into from
Oct 16, 2023
Merged

Conversation

JeanRochCoulon
Copy link
Contributor

To reduce the CI execution time on servers

To reduce the CI execution time on servers
@JeanRochCoulon
Copy link
Contributor Author

@cathales Can you approve ?

@github-actions
Copy link
Contributor

✔️ successful run, report available here.

Copy link
Contributor

@cathales cathales left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I’m looking forward to two changes so that switching PR CI from regress to dev actually reduces latency for contributors:

  1. an FPGA build optimization (eg: caching Vivado primitives)
  2. triggering the Thales CI from a GitHub webhook on PR&master pushes instead of on schedule

@JeanRochCoulon
Copy link
Contributor Author

Agree on the two improvement proposals

@JeanRochCoulon JeanRochCoulon merged commit f4378ca into master Oct 16, 2023
22 checks passed
@JeanRochCoulon JeanRochCoulon deleted the JeanRochCoulon-patch-4 branch October 16, 2023 12:06
@cathales
Copy link
Contributor

2. triggering the Thales CI from a GitHub webhook on PR&master pushes instead of on schedule

Update: this should be working from now 🚀

@JeanRochCoulon should we create a task to investigate possible FPGA build duration optimizations?

@JeanRochCoulon
Copy link
Contributor Author

Yes and you can assign our specialist: Guillaume

@cathales
Copy link
Contributor

It seems I’m not allowed to add tasks

@JeanRochCoulon
Copy link
Contributor Author

Give me the texte you would like to add in kanban board, I will do the job

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants