Re-publishing snapshots to the community ivy repo fails

[Gerolf Seitz]

Hi,

I wanted to republish the snapshots for sbt-release, but I always get this response:

Access to URL http://scalasbt.artifactoryonline.com/scalasbt/sbt-plugin-snapshots/com.github.gseitz/sbt-release/scala_2.9.1/sbt_0.11.3/0.5-SNAPSHOT/jars/sbt-release.jar was refused by the server: Forbidden

The initial publish worked fine and the credentials/publishTo settings haven't changed since then.

Eugene confirmed that he has no problems republishing snapshots so I'm a bit lost.

Can somebody with access to the artifactory machine help me out with troubleshooting?

Cheers

--

Gerolf Seitz

twitter: @gersei

code: github.com/gseitz

blog: www.gerolfseitz.com

[eugene yokota]

I realized that I'm an admin there with deletion rights on sbt-plugin-snapshot repo, while your account has "deployer" role without deletion rights.

Maybe we need to allow deletion for deployers too on snapshots?

-eugene

[Gerolf Seitz]

Sounds good. Deleting snapshots should be fine I guess.

Who is the "committee" for the community repo? (Just so I know in which direction I have to fire my bribes ;)

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/aJt3FJRcSHwJ.
To post to this group, send email to simple-b...@googlegroups.com.
To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.

[Heiko Seeberger]

On May 25, 2012, at 7:30 AM, Gerolf Seitz wrote:

> Sounds good. Deleting snapshots should be fine I guess.
>
> Who is the "committee" for the community repo? (Just so I know in which direction I have to fire my bribes ;)

I am working on it. But as I am not an Artifactory power user, it might take a while. Please bear with me …

Heiko

[Heiko Seeberger]

OK, all deployers should now be able to delete / overwrite artifacts in the snapshot repository.

Heiko

[Gerolf Seitz]

Thanks, works.

Heiko

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.

To post to this group, send email to simple-b...@googlegroups.com.
To unsubscribe from this group, send email to simple-build-t...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.

[Josh Suereth]

Guys this is a terrible idea.

You should *not* delete public artifacts in a cached environment.  You're asking ofr issues.  I specifically didn't allow deletion for non-admins for that reason.

SIDE NOTE:  The committee is everyone who signed up.  ANyone have suggestions for how to start an admin mailing list?

Now, as for SNAPSHOTs, remember SBT uses *ivy* which means SNAPSHOTS are the wrong way of doing it.   We really should be using integrations and someone needs to figure out how to do it the right ivy way, or we're just asking for issues.

Be deleting artifacts you're *asking* for problems from users and resolution nightmares.   Let's not add to an already terrible situations.   Let's not fight Ivy if we have to use it.

- Josh

[Josh Suereth]

Please do!

On Fri, May 25, 2012 at 9:23 AM, eugene yokota <eed3...@gmail.com> wrote:

On Fri, May 25, 2012 at 9:08 AM, Josh Suereth <joshua....@gmail.com> wrote:
> SIDE NOTE:  The committee is everyone who signed up.  ANyone have
> suggestions for how to start an admin mailing list?

I can make a google group for it if that's ok.

-eugene

[eugene yokota]

On Fri, May 25, 2012 at 9:08 AM, Josh Suereth <joshua....@gmail.com> wrote:

> SIDE NOTE:  The committee is everyone who signed up.  ANyone have
> suggestions for how to start an admin mailing list?

[Heiko Seeberger]

> Be deleting artifacts you're *asking* for problems from users and resolution nightmares. Let's not add to an already terrible situations. Let's not fight Ivy if we have to use it.

Not being able to overwrite a snapshot version of an artifact is certainly the worst case. Until there is a better mechanism in place I vote for living with the issues that might come up. Remember, we are talking about snapshots …

Heiko

[Josh Suereth]

Yes, we're talking about snapshots + proxy repositories + build servers.    That's a nightmare I don't want to have to deal with... or push on anyone else...

I think there is an alternative solution in Ivy that's viable, we just haven't looked into how to use it yet.

See the sbt-repo-admin list for Eugene's research.   It looks viable *and* it's cache-friendly.   We just can't call things "-SNAPSHOT" directly....

Heiko

[dave]

On Friday, May 25, 2012 8:08:25 AM UTC-5, jsuereth wrote:

Be deleting artifacts you're *asking* for problems from users and resolution nightmares.   Let's not add to an already terrible situations.   Let's not fight Ivy if we have to use it.

Aren't snapshots, by definition, temporary artifacts that will eventually go away?

If we're talking about just the world of SBT plugins published to the community Ivy repo, then storage will very likely be able to keep up with demand. But as a general rule, especially if you include actively maintained libraries or applications, then you will get to the point where you'll need (or at least want) to get rid of old snapshots. 

I've certainly filled up my share of disks by not having a good artifact retention policy :-)

 

- Josh

dave

<>< 

[Josh Suereth]

Getting rid of snapshots isn't the issue.  Understanding, as a caching solution, when to hit the repo and when not to, is an issue.   Ivy has no special behavior for a thing called -SNAPSHOT, which people assume it does.   This means we're wreaking havoc on caching solutions because an ivy repository implies a different mechanism.

Removing old snpashots is perfectly fine, and we need to make sure that happens.   Right now we're deleting/replacing old snapshot artifacts, and that's an issue.

<>< 

--

You received this message because you are subscribed to the Google Groups "simple-build-tool" group.

To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/tw0w_fYc0v0J.

[Mark Harrah]

On Fri, 25 May 2012 16:57:09 -0400
Josh Suereth <joshua....@gmail.com> wrote:

> Getting rid of snapshots isn't the issue. Understanding, as a caching
> solution, when to hit the repo and when not to, is an issue. Ivy has no
> special behavior for a thing called -SNAPSHOT, which people assume it does.

It is true the cache can get confused, but it is not true that Ivy doesn't understand resolving snapshots. Eugene explained it in another thread, perhaps on the admin list. There is an issue with sbt's auto-update that was addressed in 0.12.

What Ivy does not support, as far as I know, is publishing snapshots in the manner Maven does. I believe I have stated this elsewhere, but if anyone wants to improve the situation, my opinion is that effort is best spent working with the Gradle team to reuse their dependency management code.

-Mark