mockitoguy

~/mockito/src$ ./gradlew testRelease
Parallel execution is an incubating feature.

> Configure project : 
  Building version '2.17.3' (value loaded from 'version.properties' file).

> Task :testRelease 
  Performing release in dry run, with cleanup:
    ./gradlew releaseNeeded performRelease releaseCleanUp -PdryRun
[releaseNeeded] Starting a Gradle Daemon, 1 busy Daemon could not be reused, use --status for details

mockitoguy

Could not resolve all files for configuration :inlay:inlay-impl:compileClasspath.
Could not resolve com.linkedin.statserver-api:statserver-api-restli:0.0.13.
Required by:
    project :inlay:inlay-impl
> Could not resolve com.linkedin.statserver-api:statserver-api-restli:0.0.13.
Required by:
    project :inlay:inlay-impl
> Could not resolve com.linkedin.statserver-api:statserver-api-restli:0.0.13.
  > Could not get resource 'http://lva1-artifactory.corp.linkedin.com:8081/artifactory/release/com/linkedin/statserver-api/statserver-api-restli/0.0.13/statserver-api-restli-0.0.13.ivy'.
    > Could not HEAD 'http://lva1-artifactory.corp.linkedin.com:8081/artifactory/release/com/linkedin/statserver-api/statserver-api-restli/0.0.13/statserver-api-restli-0.0.13.ivy'.

mockitoguy

> Task :testRelease
  Performing release in dry run, with cleanup:
    ./gradlew releaseNeeded performRelease releaseCleanUp -PdryRun
[releaseNeeded] Starting a Gradle Daemon, 1 busy Daemon could not be reused, use --status for details
[releaseNeeded] Parallel execution is an incubating feature.
[releaseNeeded]   Building version '2.12.1' (value loaded from 'version.properties' file).
[releaseNeeded] :android:downloadPreviousReleaseArtifacts
[releaseNeeded] :downloadPreviousReleaseArtifacts
[releaseNeeded] :extTest:downloadPreviousReleaseArtifacts
[releaseNeeded] :inline:downloadPreviousReleaseArtifacts

mockitoguy

Shipkit is a toolkit of shipping it. You have code that wants to be delivered to your clients, Shipkit has tools to help you out:
 - automatic version bumps - don’t waste time managing your version manually
 - automatically generated changelog - offer your customer clean information what changed and why
 - changelog that highlights each individual contributor by name - build engaged community
 - avoiding publishing binaries if nothing changed - respect your customers’ time
 - automatically ship to Bintray and Maven Central - use every opportunity to give your product to the hands of customers.

Great tools for engineers are invisible - you immerse in the flow of coding features, never noticing the machinery that keeps you productive. Focus on code and features, never on release overhead. Shipkit will take care of your releases.

Core use cases, for engs who have code to ship but no existing automation to make it smooth. Shipkit offers plugins that hide most complexity of shipping releases.

mockitoguy

Potential design:

GitPlugin
    gitCommit
    gitCommitCleanUp
    gitTag
    gitTagCleanUp
    gitPush
        mustRunAfter gitCommit
        mustRunAfter gitTag

mockitoguy

apply plugin: "org.mockito.mockito-release-tools.continuous-delivery"

releasing {
    gitHub.repository = "mockito/mockito-release-tools-example"
    gitHub.readOnlyAuthToken = "e7fe8fcdd6ffed5c38498c4c79b2a68e6f6ed1bb"
    gitHub.writeAuthUser = "shipkit"
}

allprojects {
    plugins.withId("org.mockito.mockito-release-tools.bintray") {

mockitoguy

~/mockito/src$ ./gradlew comparePublications -s
Parallel execution is an incubating feature.
  Building version '2.8.26' (value loaded from 'version.properties' file).
:fetchAllProjectContributorsFromGitHub
  Fetching all contributors for project SKIPPED (output file exist)
:inline:sourcesJar
:generatePomFileForJavaLibraryPublication
:android:sourcesJar UP-TO-DATE
:inline:sourcesJar UP-TO-DATE
:inline:generatePomFileForJavaLibraryPublication

mockitoguy

~/mockito/example-release$ 
~/mockito/example-release$ ./gradlew testRelease
Starting a Gradle Daemon (subsequent builds will be faster)
  Using version '0.8.3' of Mockito Release Tools
  Building version '0.15.3' (value loaded from 'version.properties' file).
:bumpVersionFile
:bumpVersionFile - updated version file 'version.properties'
  - new version: 0.15.4
  - previous version: 0.15.3
  - notable versions updated: false

mockitoguy

~/linkedin/composite/ligradle-composite/ligradle-composite$ gradle idea --include-build ../ligradle-core/ -s
[composite-build] Configuring build: /Users/sfaber/linkedin/composite/ligradle-composite/ligradle-core
:ligradle-core:precompileAll
Precompiling...
:ligradle-core:compileJava UP-TO-DATE
:ligradle-core:processResources UP-TO-DATE
:ligradle-core:classes UP-TO-DATE
:ligradle-core:jar UP-TO-DATE
:ligradle-jvm:precompileAll
Precompiling...

mockitoguy

mint setup | [INFO] Running voyager-ios './scripts/setup.sh'
[INFO] Executing: clean reinit generate-static-app-def -Prelease=true
[INFO] Using versions:
[INFO] 	Environment: Gradle 3.3, JDK 1.8.0_40
[INFO] 	Gradle Plugins: client-typed-urn-generator:1.0.18, ligradle-jvm:2.0.22, lix-cleanup-plugin:0.1.20, mntf-ios-plugins:1.0.0, rum-ios:3.0.63, tracking-constants:0.1.4

FAILURE: Build failed with an exception.

* What went wrong:
Unable to find a usable idle daemon. I have connected to 100 different daemons but I could not use any of them to run the build. BuildActionParameters were DefaultBuildActionParameters{, currentDir=/export/home/tester/hudson/data/workspace/MP_TRUNKDEV_MP_DEP/voyager-ios_92b43ac4cc8751cc3fe08defaa544e0cc376caf8, systemProperties size=55, envVariables size=104, logLevel=LIFECYCLE, useDaemon=true, continuous=false, interactive=false, injectedPluginClasspath=[]}.