Clojurians Log v2

I’ve been contributing to clj-commons/citrus and would like to help getting a deploy out. Roman sort of approved the new release here but it hasn’t been deployed yet: https://github.com/clj-commons/citrus/pull/62 — should I reach out to Roman to help with this or are there others here helping with release management?

@martinklepsch read back a couple of messages. if @slipset has set up deployment the same as for clj-yaml you can do it like that by pushing a tag with the bb script

so:

/tmp/clj-yaml (master) $ /tmp/infra/deployment/release.bb
Working-directory is clean, releasing 0.7.107
done

I haven’t done that, I believe, as Roman has been dealing with citrus (edit: this is a blatant lie, as I was the last to deploy to clojars :/). I can have a look later today.

Actually seems quite handy if this type of thing is streamlined across all clj-commons projects

Totally agree. I tend to do it kind’a lazily, so whenever I need to deploy something.

@martinklepsch what’s the command to produce an artifact?

lein uberjar ? or lein jar ?

seems like lein install does what’s expected. Then I guess lein deploy clojars is the incantation which is needed to deploy to clojars, so I can set that up.

Automagic deploys are in place for citrus. I’ve deployed two new versions to Clojars by pushing two tags, Release-3.3.0-rc1 and Release-3.3.0-rc2 @martinklepsch you can push a Release-whatever tag and the current version will be deployed to clojars.

Or you can do it from the github ui 🙂

@slipset ohhh amazing! Does that mean there’s no dependency between released versions and project.clj ?

Correctish

project.clj picks up the version from the environment.