Repository navigation
Create new or fix the current CI pipeline #751
Description
Activity
- changed the title
[-]Create new or fix the current CI pipeline for Junction[/-][+]Create new or fix the current CI pipeline of Junction[/+]on Apr 18, 2023 - changed the title
[-]Create new or fix the current CI pipeline of Junction[/-][+]Create new or fix the current CI pipeline[/+]on Apr 18, 2023 i can look into this.
Let's use GitHub Actions for CI
I can try this
I have raised a PR in #775 , ig the actions to run in this project requires one round of review
i tested in my fork of this project ref: https://github.com/indiVar0508/junction/actions/runs/5282162574/jobs/9556725306
this is kind off wip if you can mention further requirements i can them on top of this PR(s)- added 15 commits that reference this issue
on Jun 24, 2023 - linked a pull request that will close this issueadd(#751): add support for github actions #775
on Jul 4, 2023
Junction Upgrade for Python 3.10 and Django 3.2 is being tested on this branch and would eventually get merged into the master branch.
So in the existing setup(master branch), circle-ci is used for CI but I think it's broken. So we need to fix CI either using the circle CI or we can move to Gitub action.
Since we are going to put effort into fixing CI and in the meantime Junction repo is also getting containerized(#749), so we should develop CI pipeline thinking docker in mind.
To seek clarity on requirements, please ask questions here.