Using SonarQube's New-Code Quality Gate to Enforce Clean as You Code
Learn how to configure SonarQube's Quality Gate to evaluate only New Code, enabling the Clean as You Code strategy in a typical CI pipeline with Maven and GitHub Actions.
Loading…
ReadMeFeed / Community knowledge
#ci-integration
Real questions. Useful conversations. Find the people who know your stack.
Designing Data‑Driven Postman Collections with External CSV Sources
A concise architecture note for using external CSV files with Postman Collection Runner (and Newman) to drive data‑tests, covering requirements, minimal design, trust boundaries, checks, failures, and when to evolve the design.
qTest API result submission in CI: limits on testing the integration without production credentials
Goal I want to exercise our CI pipeline's integration with the qTest Manager REST API — creating test runs and submitting automated test results — without using production credentials or writing results into our live project. The plan is a separate sandbox or trial project with its own API token, generated by a least-privilege account, so a leaked token in C
qtestTransitioning Maven Enforcer Plugin Rules from Fail to Warn for External Alerting
The goal is to configure Maven Enforcer Plugin rules to emit warnings instead of failing the build, while ensuring those warnings are captured as external notifications (e.g., Slack, email) so stakeholders are informed without adding noise to the build output. The Enforcer plugin provides a <fail> flag to decide whether a rule violation stops the build
mavenQodana Incremental Cache Behavior During Parallel CI Job Execution
Determine whether Qodana’s incremental analysis cache remains consistent when two or more scans run concurrently on the same repository, a scenario common in CI pipelines that trigger parallel jobs. The documentation describes the cache as a performance optimization but does not specify locking or isolation mechanisms for simultaneous access. Observed latenc
qodanaPyPI Trusted Publishing Branch Scoping Gap
The goal is to determine the enforcement boundary for branch identifiers when using PyPI Trusted Publishing with OIDC-based tokenless uploads. Publisher bindings specify repository, workflow filename, and optionally environment, but do not include a branch or ref constraint. OIDC tokens emitted by CI providers carry branch information such as ref: refs/heads
BrowserStack REST API retries and CI result reporting: preventing duplicate session entries and artifact uploads
Our CI pipeline integrates with BrowserStack Automate through the REST API. When a session fails, we call the retry endpoint, which creates a brand-new session with a fresh session_id while copying the original test name, tags, and custom metadata verbatim. The problem is on the reporting side: each retry appears as a separate entry in the results dashboard
browserstack