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

Move CI job to GitHub Actions? #550

Closed
lumaxis opened this issue Jan 31, 2024 · 2 comments · Fixed by clearlydefined/website#1038
Closed

Move CI job to GitHub Actions? #550

lumaxis opened this issue Jan 31, 2024 · 2 comments · Fixed by clearlydefined/website#1038
Assignees
@lumaxis

Comments

@lumaxis
Copy link
Contributor

lumaxis commented Jan 31, 2024

This repo currently runs its builds on Azure DevOps, however clearlydefined/service also already has a GitHub Actions workflow for running the tests. Is there any plan and/or interest in moving these to GitHub Actions permanently? I'd be happy to add an analogous workflow to the one from service.
This was referenced Feb 14, 2024
Merged
Merged
@lumaxis
Copy link
Contributor Author

lumaxis commented Feb 14, 2024

This has been done in both the crawler and the service. I'll look at making the move for the website repo next to complete this.

@lumaxis lumaxis self-assigned this Feb 14, 2024
@lumaxis lumaxis mentioned this issue Apr 4, 2024
Merged
@lumaxis
Copy link
Contributor Author

lumaxis commented May 30, 2024

All 3 main projects now use GitHub Actions and the last Azure Pipelines config has been removed. Additionally (but I think tracked separately), all 3 projects use Actions to deploy now (except maybe the production crawler?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lumaxis lumaxis

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove Azure Pipelines config clearlydefined/website
1 participant
@lumaxis