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

[CI/CD] - Drive CI/CD requirements via requirements file #3340

Open
flavienSindou opened this issue Jan 28, 2025 · 0 comments
Open

[CI/CD] - Drive CI/CD requirements via requirements file #3340

flavienSindou opened this issue Jan 28, 2025 · 0 comments
Labels
bug use for describing something not working as expected improvement needs triage use to identify issue needing triage from Filigran Product team test automation use to identify issue related to test automation implementation

Comments

@flavienSindou
Copy link
Contributor

Description

CI/CD pipeline does install any version of black and isort linters. This leads to formatting conflict.

Environment

NA

Reproducible Steps

See https://app.circleci.com/jobs/github/OpenCTI-Platform/connectors/35230

Expected Output

A ci-requirements.txt file could drive the connectors CI/CD dependencies versions.

Screenshots (optional)
@flavienSindou flavienSindou added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 28, 2025
@flavienSindou flavienSindou changed the title [CI/CD] - Drive CI/CD requirements via requirements [CI/CD] - Drive CI/CD requirements via requirements file Jan 28, 2025
@flavienSindou flavienSindou added test automation use to identify issue related to test automation implementation improvement labels Jan 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug use for describing something not working as expected improvement needs triage use to identify issue needing triage from Filigran Product team test automation use to identify issue related to test automation implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@flavienSindou