This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-02-04
Channels
- # aatree (5)
- # admin-announcements (37)
- # alda (1)
- # announcements (4)
- # architecture (1)
- # aws (3)
- # beginners (82)
- # boot (230)
- # braid-chat (14)
- # cider (48)
- # cljs-dev (8)
- # cljsrn (31)
- # clojars (47)
- # clojure (72)
- # clojure-austin (2)
- # clojure-russia (396)
- # clojurescript (72)
- # community-development (3)
- # component (6)
- # core-async (6)
- # cursive (26)
- # datomic (42)
- # emacs (6)
- # events (35)
- # hoplon (57)
- # immutant (3)
- # jobs (2)
- # jobs-discuss (10)
- # ldnclj (16)
- # luminus (2)
- # off-topic (50)
- # om (181)
- # parinfer (285)
- # proton (68)
- # re-frame (19)
- # reagent (2)
- # ring-swagger (23)
- # yada (36)
@peeja - thanks for the report. what page do you see that on? are you logged in or out when you see it?
Shoot, that would have been good to have posted. I believe it was https://clojars.org/om, but I'm not seeing it now. I was logged out.
Oh, no, there it is: https://clojars.org/om/versions
Hey folks, following the pushing directions here https://github.com/clojars/clojars-web/wiki/Pushing I'm having trouble getting a Maven project to deploy correctly. The files upload, but then get rejected with a 503.
https://clojars.org/me.arrdem/clojarr well this exists so it worked at some point
that has a set of unauthed PUTs around 19:40:26, followed by authed ones that succeed
I think we must have a bug that triggers a 503 instead of a 401 on an unauthed deploy
As long as I have your attention, what's the policy about builds and snapshot jars? be nice and just deploy releases or is hooking CI up to deploy snapshots fair game.
@arrdem: project settings -> environment variables, though I use separate creds for CI
@juhoteperi: yeah I'm doing some digging in the name of paranoia, trying to figure out if I can use Maven encrypted values in combination with environment variables. I've got this vision of a malicious PR that echos env vars 😐
At least in Circle CI, PR's don't see env variables
Oh right and you can define encrypted vars in travis.yml, and they wont be available in PRs
sure but it'd be easy enough to write a PR containing code that does (println (System/getEnv "THE_PASSWORD_VAR_FROM_THE_CFG_FILES"))
But then you need to commit the encrypted value to repo
But the env variables are not at all set for PR builds in Circle
Looks like env vars in Travis settings are available to all builds
But this looks good: https://docs.travis-ci.com/user/environment-variables/#Encrypting-Variables-Using-a-Public-Key
I have just configured the creds via web ui