How can we perform code signing using an HSM with module-signer?

Module Development
21

UPDATE #2 2024-03-22

Hilarious, we still have some automation that successfully publishes to the Gradle Plugin Portal. It's up there under Perrry's personal account.

So there is probably no custom configuration needed in settings.gradle.kts if you are already pulling from GPP.

UPDATE 2024-03-22

That PR has been merged and the Gradle plugin published to our nexus.inductiveautomation.com public repo. Make sure your Gradle project is using 7.6 or later for it to run reliably.

To use our Nexus repository for plugin resolution, add the following configuration to your settings.gradle.kts and build.gradle.kts (if using the Gradle Groovy DSL the syntax is similar):

// settings.gradle.kts

pluginManagement {
    repositories {
        maven {
            name = "publicNexusRelease"
            url = uri("https://nexus.inductiveautomation.com/repository/inductiveautomation-releases")
        }

        // if you want to use snapshot builds of the plugin
        // maven {
        //             name = "publicNexusSnapshot"
        //             url = uri("https://nexus.inductiveautomation.com/repository/inductiveautomation-        // snapshots")
        //         }

        gradlePluginPortal()

        // and any other plugin repos you may be using
    }
}

// build.gradle.kts

plugins {
    // any other plugins
    id("io.ia.sdk.modl") version "0.2.0"
}

For the time being we are not publishing to the Gradle Plugin Portal, even though an older version of this plugin is published there now. We're considering this down the road after ironing out some process issues.

Draft PR is up on GitHub.

inductiveautomation/ignition-module-tools#43

2 Likes