Fork me on GitHub
#clojars
<
2016-02-04
>
tcrawley15:02:24

@peeja - thanks for the report. what page do you see that on? are you logged in or out when you see it?

peeja15:02:37

Shoot, that would have been good to have posted. simple_smile I believe it was https://clojars.org/om, but I'm not seeing it now. I was logged out.

tcrawley15:02:42

ah, cool. I see it too. thanks!

tcrawley15:02:58

@peeja: fixed, will go live on the next deploy, whenever that happens to be :)

arrdem19:02:35

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.

arrdem20:02:33

not that I'm aware of I'll give it another go

arrdem20:02:09

https://clojars.org/me.arrdem/clojarr well this exists so it worked at some point

tcrawley20:02:33

that has a set of unauthed PUTs around 19:40:26, followed by authed ones that succeed

tcrawley20:02:06

I think we must have a bug that triggers a 503 instead of a 401 on an unauthed deploy

arrdem20:02:18

huh ok well I just put a bunch of stuff successfully

arrdem20:02:25

looks like it was an auth config issue

tcrawley20:02:50

I'll see if I can figure out why that gave a 503 instead of a 401

arrdem20:02:28

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.

tcrawley20:02:51

no, feel free to publish snapshots from CI, that's fine and dandy

tcrawley20:02:15

as long as you aren't building several times a minute, consistently

arrdem20:02:39

maybe 10 builds a day tops

tcrawley20:02:49

yeah, that's totally fine

tcrawley20:02:51

thanks for asking!

arrdem20:02:57

thanks for running this 😄

arrdem20:02:51

now I just gotta figure out how to give Travis my Clojars creds securely..

tcrawley20:02:28

yeah, no idea there :)

arrdem20:02:46

I'll figure it out. Thanks for the help.

tcrawley20:02:55

my pleasure!

juhoteperi20:02:19

@arrdem: project settings -> environment variables, though I use separate creds for CI

arrdem20:02:02

@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 😐

juhoteperi20:02:34

At least in Circle CI, PR's don't see env variables

juhoteperi20:02:26

Oh right and you can define encrypted vars in travis.yml, and they wont be available in PRs

arrdem20:02:32

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"))

juhoteperi20:02:36

But then you need to commit the encrypted value to repo

juhoteperi20:02:57

But the env variables are not at all set for PR builds in Circle

juhoteperi20:02:46

Looks like env vars in Travis settings are available to all builds

arrdem20:02:33

I meant circleci earlier not travis

arrdem20:02:48

looks like the circle folk don't support such a thing

juhoteperi20:02:25

I have just configured the creds via web ui

arrdem20:02:38

ok well that solves that problem then