We’re thrilled to announce that Scoped Organization Tokens can now be created for ALL current and future projects within an organization! This change makes the analysis automation much easier and more seamless as it removes the need to create a different token whenever a new project is onboarded.
You can also edit previously created tokens allowing to add or remove projects from the scope.
As usual, please feel free to share your feedback so that we continue improving our solution.
Hello! This new feature is greatly appreciated, and very well timed as well: the user who our current token belongs to just left the company, so I can now use a proper scoped token instead of my own (which’ll break again in the future when I leave).
It’s working well for main branch scans, however when it’s kicked off as part of a GitHub pull request it’s erroring out in the end task:
20:59:41.09 INFO: Github event: pull_request
20:59:41.107 INFO: Auto-configuring pull request 123
20:59:41.307 ERROR: Could not find the pullrequest with key ‘123’
20:59:41.637 The scanner engine did not complete successfully
20:59:41.637 Post-processing failed. Exit code: 1
That PR exists, and changing the token to my personal one causes it to work. Seems strange this scenario wouldn’t be supported since this new feature was specifically created for automated CI/CD scenarios like this. Anything I’m missing?
Thank you for the report! We confirmed there is an edge case for GitHub PRs analysis which makes them fail. We are actively working on resolution and the fix should be deployed early this week. We’ll update the thread.