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

[CI][multi-repository] build on client python that requires an opencti branch not working for push build #746

Open
aHenryJard opened this issue Oct 14, 2024 · 0 comments
Labels
bug use for describing something not working as expected
Milestone

Comments

@aHenryJard
Copy link
Member

Please replace every line in curly brackets { like this } with an appropriate answer, and remove this line.

Description

Working fine for pr build.

But for push build it's not working, ending on master instead of opencti/issue/xxxx.

Discovered on #745

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: { e.g. OpenCTI 1.0.2 }
  3. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. { e.g. Run ... }
  2. { e.g. Click ... }
  3. { e.g. Error ... }

Expected Output

opencti service start with a dedicated branch

Actual Output

opencti service starts on master branch.

{ Please describe what actually happened. }

Additional information

If not too long, look at taking the PR target branch as default instead of hardcoded "master".

@aHenryJard aHenryJard added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Oct 14, 2024
@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Oct 16, 2024
@nino-filigran nino-filigran added this to the Bugs Backlog milestone Oct 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected
Projects
None yet
Development

No branches or pull requests

2 participants