Configuration
This is your centralized hub for configuring all settings of JamOps on a global scope. Settings configured here apply universally across your JamOps environment, influencing operations at the highest level.
You can fine-tune various parameters and preferences that shape the behavior and performance of your JamOps environment. Whether it's defining rules for handling vulnerabilities, setting up email notifications, or determining error-handling strategies, you to tailor JamOps to suit your organization's specific needs and workflows.
#
Accessible by- Default homepage
- Navigation
#
Configurable FieldsFind below detailed information about the various fields that can be configured on the Configuration page.
#
Dependency vulnerability excludes as jsonDependency Vulnerability Excludes applied to all projects.
#
Fail only on vulnerability if app store module update existsThe process will only fail if there's an update available for the module with the vulnerability, and that update is compatible with the current Mendix version. Note that some updates may require an upgrade of the Mendix version itself.
#
Slack channel idThe slack channel id where all messages will be posted. Can be found in the URL of the channel.
#
UsernameThe Mendix username that JamOps will use to communicate with Mendix.
#
Personal access tokenThe Mendix personal access token that JamOps will use to communicate with Mendix.
#
Appcenter api keyThe Appcenter API-Key that JamOps will use to communicate to Appcenter.
#
Framework vulnerability excludes as jsonMendix Framework Vulnerability Excludes applied to all projects.
#
Email filter only user in commitOnly email the user that made the commit.
#
Global analyser rule config as jsonA Model Analyser rule config that will be used for projects where rule config level is set to global.
#
Slack enable notificationsIf enabled events will be sent to slack.
#
App store connect api key idThe App store connect api key id that JamOps will use to communicate with App store connect.
#
Slack bot user o auth access tokenPlease create a Slack app and add the appropriate scopes (chat:write, channels:join, channels:manage, groups:write, im:write, mpim:write) and workspace so you can generate an access code that can be used here.
#
Email filter only active usersActive users are users that logged in at least once.
#
Email filter as regular expressionAn email will only be sent if the receiver email mathes with this regular expression. If left empty no emails will be sent.
#
Module vulnerability excludes as jsonDependency Module Excludes applied to all projects.
#
Github ownerThe The Github owner that JamOps will use to communicate with GitHub.
#
Api keyThe Mendix API-key that JamOps will use to communicate with Mendix.
#
EnabledDisable all communications with Mendix.
#
App store connect api issuer idThe App store connect api issuer id that JamOps will use to communicate with App store connect.
#
Jam audit log config as jsonAudit Log Configuration that will be available by a webservice so it can be used to configure multiple applications from a central point.
#
Slack user ids to be invited in newly created channelsA comma separated list of userIds to be invited in newly created channels
#
Appcenter ownerThe Appcenter owner that JamOps will use to communicate to Appcenter.
#
Allow mpr analyser violation excludeLet users decide if they can exclude certain rule violations.
#
Fail only on vulnerability if maven dependency update existsThe process will only fail if there's an update available for the Java library with the vulnerability
#
Github api keyThe The Github API-key that JamOps will use to communicate with GitHub.
#
Mpr analyser violation exclude needs peer reviewThis option indicates that if a user wishes to exclude certain rule violations (as mentioned in the "Behaviour" section), their decision to exclude should be reviewed by another peer or team member.
#
Aggregate failuresDecide if multiple failures should be grouped together or treated separately.
#
Slack create channel for each projectPost all messages in one channel or post in project specific channels.
#
Continue on module errorDecide if the process should continue even if there's an error in a module.
#
App store connect api keyThe App store connect api key that JamOps will use to communicate with App store connect.
#
PasswordThe Mendix password that JamOps will use to communicate with Mendix.