Skip to content
This repository has been archived by the owner on Sep 26, 2019. It is now read-only.

Upload jars to bintray as part of releases #1608

Merged
merged 19 commits into from
Jun 30, 2019

Conversation

ajsutton
Copy link
Contributor

PR description

Testing upload of jars to bintray (targeting a test repo for now).

@ajsutton ajsutton marked this pull request as ready for review June 28, 2019 01:44
@ajsutton ajsutton changed the title Upload jars to bintray. WCPGW? Upload jars to bintray as part of releases Jun 28, 2019
Copy link
Contributor

@shemnon shemnon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does the bintray release still work (and is there any way to find out other than doing a release?)

build.gradle Outdated
publishing {
publications {
mavenJava(MavenPublication) {
groupId "tech.pegasys.${project.group}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(a) do we really want each sob jar to be it's own maven group? Since they are all needed in pantheon and only used in pantheon and can't be severed from pantheon (except for two cases: metrics and plugins api) wouldn't one group make more sense? Could we all put them in to one group and let the artifact name do the work?

(b) regardless of (a) should the group name include something like "internal" or "unstable" to make it clear it's not a stable API?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything in tech.pegasys.pantheon makes sense to me.

Including 'internal' probably makes sense. We may need to find a way to override some of this info on a per-package basis (eg would be nice if metrics wasn't marked internal) but starting with everything internal and then some migrating out if/when we work out how to do that makes sense to me.

}
}
}
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think if you add a repository block you may get the maven metadata

  repositories {
    maven {
      // change URLs to point to your repos, e.g. http://my.org/repo
      def releasesRepoUrl = "$buildDir/repos/releases"
      def snapshotsRepoUrl = "$buildDir/repos/snapshots"
      url = version.endsWith('SNAPSHOT') ? snapshotsRepoUrl : releasesRepoUrl
    }
  }

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No luck. But I've tested with both gradle and maven depending on these publish jars and it works even without the metadata.

@ajsutton
Copy link
Contributor Author

Unfortunately there's no way to know for sure the release will still work until we actually try it next. I have disabled the automatic publishing on every master build because that will conflict (both the release job and master job would be trying to publish the same release). Will discuss the various options to avoid that and go from there.

@ajsutton ajsutton merged commit 285f9f8 into PegaSysEng:master Jun 30, 2019
@ajsutton ajsutton deleted the upload-jars branch June 30, 2019 22:29
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants