DevConsole is distributed through JitPack.
The Gradle plugin is the one exception: it lives in the gradle-plugin included build and goes to
the Gradle Plugin Portal, because the plugins { } DSL cannot resolve a plugin marker from
JitPack.
All 34 modules under sdk/ are wired with the
Vanniktech Maven Publish plugin
(via the devconsole.publishing convention). Artifact IDs follow the mapping in
PublishingConventionPlugin: :sdk:full → devconsole, :sdk:noop → devconsole-noop,
everything else → devconsole-<module>. Each publication carries sources, a Dokka-generated
javadoc jar, and a POM with license/developer/SCM metadata.
There is nothing to run to release. JitPack builds a ref the first time someone asks for it and
serves the result under the group com.github.devconsole-android.DevConsole. Cutting a release is
just pushing a tag; the first consumer request triggers the build.
jitpack.yml pins the JDK to 17 and otherwise leaves JitPack's default command alone — that
default already passes -xtest -xlint -xsignMavenPublication, so overriding it with an install:
block would silently start running the full unit suite on every consumer-triggered build.
To verify the whole pipeline locally before tagging:
./gradlew publishToMavenLocalThat produces the same artifacts JitPack does, with one difference that matters for a smoke test:
the POM group stays io.github.devconsole-android, because JitPack rewrites the group to
com.github.devconsole-android.DevConsole when it serves a build. So a local consumer test against
mavenLocal() must name io.github.devconsole-android:devconsole:<version> — the
com.github.… coordinates in this document only resolve from jitpack.io.
Check a real JitPack build at
https://jitpack.io/api/builds/com.github.devconsole-android/DevConsole.
SDK_VERSION in
build-logic/convention-publishing/src/main/kotlin/io/devconsole/buildlogic/PublishingConventionPlugin.kt
and version in gradle-plugin/build.gradle.kts are kept in step. The plugin generates its auto-wire
version resource from its own declared version, so there is no third version constant to bump. JitPack
derives the consumer-facing version from the tag or branch rather than from SDK_VERSION, but the
two should match so publishToMavenLocal output and the tag agree.
One-time: create an account at plugins.gradle.org and generate an API key. Then either publish from CI (preferred) or locally.
From CI. The Publish Gradle plugin workflow runs on a v* tag and on workflow_dispatch.
Pushing the tag is the release decision, so it publishes without further confirmation. Before it
does, it checks the tag agrees with gradle-plugin's declared version and runs the plugin's test
suite — a tag asserts the intent to release, not that the version string is right.
One-time setup: add the repo secrets GRADLE_PUBLISH_KEY and GRADLE_PUBLISH_SECRET (Settings →
Secrets and variables → Actions).
Because the publish is irreversible, two things are worth knowing: the version guard fails the run rather than publishing a mismatched coordinate, and re-pushing an already-published version is rejected by the Portal, so a deleted-and-recreated tag will fail rather than overwrite.
Locally. Put gradle.publish.key / gradle.publish.secret in ~/.gradle/gradle.properties:
./gradlew -p gradle-plugin publishPluginsFirst-time publication of a new plugin ID may sit in a short manual approval queue on the Portal side.
Add JitPack to the settings file, not the module:
dependencyResolutionManagement {
repositories {
google()
mavenCentral()
maven { url = uri("https://jitpack.io") }
}
}plugins {
id("io.github.devconsole-android") version "<version>"
}
dependencies {
debugImplementation("com.github.devconsole-android.DevConsole:devconsole:<version>")
releaseImplementation("com.github.devconsole-android.DevConsole:devconsole-noop:<version>")
}<version> is a git ref. JitPack looks it up as a tag and falls back to the v-prefixed spelling
when no bare tag exists, so a release resolves either way — 1.4.1 and v1.4.1 both serve the
v1.4.1 build. Prefer the bare form: it is what the docs show, and it matches the version the
Gradle plugin carries on the Portal. Any branch works as <branch>-SNAPSHOT, with / written as
~, so a feature/x branch is feature~x-SNAPSHOT. JitPack support starts at 1.1.1; earlier
tags do not build there, and bare 1.2.1 is a cached failed build — that one release resolves only
as v1.2.1.
See BUILD_VARIANTS_AND_PRODUCTION_SAFETY.md for what the plugin enforces about the debug/release split.