Publishing to bintray #9
Conversation
* Add publications to build.gradle * Add gradle-semantic-release configuration * Model travis.yml after gradle-semantic-release
build.gradle
Outdated
| 'gradle-plugin': 'com.adtran.betablocker-plugin:com.adtran:scala-multiversion-plugin' | ||
| ] | ||
| gpg { | ||
| sign = System.env['GPG_PASS'] != null ? true : false |
There was a problem hiding this comment.
The ternary seems pointless here.
There was a problem hiding this comment.
👍 Was mostly for local testing. I can just set it to true now.
build.gradle
Outdated
| } | ||
| } | ||
|
|
||
| /** |
There was a problem hiding this comment.
we should delete this if it's unused.
There was a problem hiding this comment.
👍 Wasn't sure if we wanted to keep it around in case we needed to bring it back (guess we can always dig it out of commit history).
build.gradle
Outdated
| ghToken = project.ghToken | ||
| releaseAsset jar | ||
| releaseAsset sourcesJar, name: "sources.jar", label: 'sources jar', contentType: 'application/zip' | ||
| releaseAsset sourcesJar, name: "javadoc.jar", label: 'javadoc jar', contentType: 'application/zip' |
There was a problem hiding this comment.
copy-paste error? I think this should be releaseAsset javadocJar ...
| def root = asNode() | ||
| root.appendNode('description', 'Gradle plugin to build a project against multiple versions of scala') | ||
| root.appendNode('name', "$artifact_group:$artifact_name") | ||
| root.appendNode('url', 'https://github.com/ADTRAN/gradle-scala-multiversion-plugin') |
There was a problem hiding this comment.
Do we have to do XML manipulation here like this? Can these three fields go in pomConfig and be set using the DSL?
There was a problem hiding this comment.
I'm not sure. I was working from the bintray/gradle-bintray-plugin example. I'll check.
There was a problem hiding this comment.
Looking at MavenPublication, using description, name, or url directly isn't documented, so I'm inclined to leave it as is.
Take two on #8. I'm hitting some issues locally with publishing but I believe when its merged into master it should work out. It builds a snapshot locally and haven't found a way to fake that out to get fully through the process. I have verified
bintrayindividually andreleasedoes seem to be consuming GH_TOKEN properly.