Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 27 07:56
    trolley813 synchronize #29
  • Jan 27 07:40
    trolley813 synchronize #29
  • Oct 21 2020 08:01
    ldeluigi commented #26
  • Oct 20 2020 18:42
    laughedelic commented #26
  • Oct 20 2020 11:43
    laughedelic commented #26
  • Oct 20 2020 09:28
    ldeluigi commented #26
  • Oct 19 2020 22:21
    laughedelic commented #26
  • Oct 19 2020 21:05
    ldeluigi commented #26
  • Oct 19 2020 20:47
    laughedelic commented #26
  • Oct 19 2020 19:35
    ldeluigi commented #26
  • Oct 19 2020 19:35
    ldeluigi commented #26
  • Oct 19 2020 18:08
    laughedelic closed #2
  • Oct 19 2020 18:08
    laughedelic closed #19
  • Oct 19 2020 18:08
    laughedelic closed #26
  • Oct 19 2020 18:08
    laughedelic commented #26
  • Oct 19 2020 18:01
    ldeluigi commented #26
  • Oct 19 2020 18:01
    ldeluigi commented #26
  • Jun 29 2020 13:25
    laughedelic unassigned #2
  • Apr 16 2020 22:17
    laughedelic commented #29
  • Apr 15 2020 06:27
    steinybot commented #29
Alexey Alekhin
@laughedelic
this renames notes (and tags the commit)
but if you don't want to use it, you can just set version manually
Nicolas Rouquette
@NicolasRouquette
Thanks! I'll give this a try.
Alexey Alekhin
@laughedelic
I mean, this nice-sbt-settings plugin is made primarily for our internal use, so some things may appear inconvenient. but if you find it useful and want to try I'm glad to hear your suggestions for improvement
By the way, that prepareReleaseNotesAndTag is part of this task
Nicolas Rouquette
@NicolasRouquette
do you have somewhere a description of your development / CI / release workflow?
i have to move a couple of dozen projects from our internal environment => public.
internally, we use nexus pro and the 2-stage publish/release process.
so far, the github release support seems to be a good match for that and i find it easier to understand & work with than bintray's
Alexey Alekhin
@laughedelic
And you want to resolve artifacts from github as well? It seems to be not very reliable..
Nicolas Rouquette
@NicolasRouquette
i see that you use amazon s3; which I suppose is more reliable than github.
Alexey Alekhin
@laughedelic

do you have somewhere a description of your development / CI / release workflow?

Nope, I'm going to write some docs for this once I finish ohnosequences/nice-sbt-settings#49 (hopefully this or next week)

Nicolas Rouquette
@NicolasRouquette
for now, i'll try github and if that is problematic, then maybe i'll try to follow your example and use s3.
Alexey Alekhin
@laughedelic
Right. But what's the problem with bintray?
Nicolas Rouquette
@NicolasRouquette
I created an organization (jpl-imce) and a repo (jpl-imce/gov.nasa.jpl.imce) and a package: https://bintray.com/jpl-imce/gov.nasa.jpl.imce/imce.sbt.plugin
I tried to configure travis-ci to publish there but that fails with an authentication and/or incorrect upload path: https://travis-ci.org/JPL-IMCE/imce.sbt.plugin/builds/154060867
I tried to use the bintray-sbt plugin; which depends on another library to access the bintray api.
so there are several intermediaries involved; it's difficult to understand what is going on and where the problem comes from. I googled around but didn't find good examples of what I've been trying to do.
Alexey Alekhin
@laughedelic
But did bintray-sbt plugin work for you? I think it should work on Travis fine if you setup an encrypted API token.
Nicolas Rouquette
@NicolasRouquette
no and I struggled with the configuration quite a bit.
at this point, i spent too much time with this so i'm giving up on bintray.
Alexey Alekhin
@laughedelic
I was going to publish there some of my personal projects and some sbt plugins. Let's see if I run into such issues as well..
Nicolas Rouquette
@NicolasRouquette
Well, on my side, I haven't found a github resolver, similar to your ivy/sbt-s3-resolver; on the other hand, I managed to fix the bintray deployment from travis.
Not quite what I was expecting at the beginning of the day but good progress. Now, I want to use your nice-sbt-settings to simplify my development workflow!
Alexey Alekhin
@laughedelic
That's great :smile: You can use 0.8.0-RC2 meanwhile and I think you can customize your workflow redefining prepareRelease and makeRelease tasks (they are just sequences of other tasks). The idea of the release command is
  • to run prepareRelease (which runs checks and makes a tag),
  • then reload to update the version (with the new git tag),
  • then run makeRelease (which publishes artifacts and does which ever else release-related stuff)
Alexey Alekhin
@laughedelic

I haven't found a github resolver

how does this work then? doesn't it resolve artifacts from github?

on the other hand, I managed to fix the bintray deployment from travis

this is nice. what was the key to the solution? I see quite complicated bintray configuration at imce.sbt.plugin. is it really necessary? can't you just use bintray-sbt plugin and run sbt publish from Travis?

Nicolas Rouquette
@NicolasRouquette
That was for source project dependencies — see http://www.scala-sbt.org/0.13/docs/Plugins.html, (1d).
Yes I agree it is complicated; at this time, it’s the only working solution i have — I need to go back and revisit the bintray-sbt attempt.
Nicolas Rouquette
@NicolasRouquette
the travis deploy bintray solution is cumbersome because it is necessary to put an explicit version string in the json descriptor. This descriptor could be generated somehow; there might be a capability to do some kind of variable expansion — I’ve seen some travis configurations with variables but not bintray deployment configurations. I’m not very keen about this solution because it only works on travis and there’s no way to do any kind of local build/deployment at all.
Alexey Alekhin
@laughedelic
@/all new release is out: v0.4.0
Sina
@sinaghaffari

Hey, every time i run: sbt githubRelease I get:

[error] (*:githubRelease) Repository https://github.com/Woombot/woombot-config doesn't e
xist or is not accessible.

Even though The token I created has full access to my account and I have access to that repository!

Alexey Alekhin
@laughedelic
hi @sinaghaffari
Are you sure the repo name is correct?
have you tried the plugin on any other repos with this token?
Sina
@sinaghaffari
Hey @laughedelic I ended up finding the problem, but ran into a different issue that wasn't related to sbt-github-release.
Essentially, I wanted publish my projects to github-releases, then use releases as a repository.
I gave up and went back to my old method
Alexey Alekhin
@laughedelic
I'm not sure I got you right: was the problem related to sbt-github-release or not? If yes, would be nice to know it.
Resolving from Github releases is tricky, but I think, still possible
Alexey Alekhin
@laughedelic
@/all Just released v0.6.0. The only change is updated Github API library: now you don't need to add an extra resolver to your project/plugins.sbt when you use this plugin :ok_hand:
Samuel
@garraspin
Hello! I made a PR to enable github enterprise, i hope you guys can review it: ohnosequences/sbt-github-release#34
Faiaz Sanaulla
@fsanaulla
Hello, is it possible to make a release in the multi-module project? As one release.
Alexey Alekhin
@laughedelic
@fsanaulla sure. Have you tried it?
Faiaz Sanaulla
@fsanaulla
@laughedelic just solved it by myself using as example https://github.com/twilio/guardrail
Anyway Thank you!
Alexey Alekhin
@laughedelic
Great! :+1:
Naseem Mahasneh
@naseem91
How do I fork an existing repo from my sbt ?
Alexey Alekhin
@laughedelic
@naseem91 hi. this plugin is not meant for that. it's purpose is to publish release notes on github.
ldeluigi
@ldeluigi
is this project still active?
Alexey Alekhin
@laughedelic
This message was deleted
@ldeluigi unfortunately, no. I don't have access to the repo anymore and apparently no one else is maintaining it.