Thanks! I was aware that I was accepting a risk by using a SNAPSHOT
dependency, but didn't know that I could refer to a timestamped snapshot.
I've switched to the timestamped snapshot dependency.
Mark Waite
On Mon, Jan 30, 2017 at 8:04 AM Jesse Glick wrote:
> On Sat, Jan 28, 2017 at 3:27 PM, D
On Sat, Jan 28, 2017 at 3:27 PM, Daniel Beck wrote:
> You don't specify the snapshot by date and time
*Always* use a timestamped snapshot dependency:
2.3.0-20170128.183609-2
If you use just
2.3.0-SNAPSHOT
as in
https://github.com/MarkEWaite/git-plugin/blob/ecab79f2cbfe7d8ff04bf1c7eac2b95b1ba
On Sat, Jan 28, 2017 at 1:15 PM Baptiste Mathus wrote:
> Do you really want to go through the Artifactory UI? I don't even remember
> even opening it.
>
>
I am not interested in using the Artifactory UI. I only used it as an
attempt to confirm that the file I had uploaded was in fact visible the
If the build works for you, that's good enough for me.
I don't understand what's damaged about my local maven repository, but it
doesn't take much to discard it and start a fresh cache.
Thanks,
Mark Waite
On Sat, Jan 28, 2017 at 1:28 PM Daniel Beck wrote:
>
> > On 28.01.2017, at 21:16, Mark Wa
> On 28.01.2017, at 21:16, Mark Waite wrote:
>
> Log is appended to the end of the message.
>
> I'm building from https://github.com/MarkEWaite/git-plugin using branch
> master-PR463-add-git-lfs. It includes a dependency on git-client-plugin
> 2.3.0-SNAPSHOT which is built from
> https://gi
Log is appended to the end of the message.
I'm building from https://github.com/MarkEWaite/git-plugin using
branch master-PR463-add-git-lfs. It includes a dependency on
git-client-plugin 2.3.0-SNAPSHOT which is built from
https://github.com/MarkEWaite/git-client-plugin using branch
master-PR232-s
Do you really want to go through the Artifactory UI? I don't even remember
even opening it.
Seems like your deploy is indeed visible: http://repo.jenkins-
ci.org/public/org/jenkins-ci/plugins/git-client/2.3.0-SNAPSHOT/
I also tried on ath and it worked indeed. Great Daniel!
2017-01-28 21:07 GMT+
> On 28.01.2017, at 19:56, Mark Waite wrote:
>
> when I try to download them from the web UI (or from my git plugin build),
> they fail to download.
I get that the UI fails, as the reverse proxy config is broken (see the extra
'jenkinsci' as web app context on download links on the UI) but th
On Wednesday, December 21, 2016 at 9:08:39 AM UTC-7, Daniel Beck wrote:
>
>
> > On 20.12.2016, at 16:21, Daniel Beck >
> wrote:
> >
> > Therefore I intend to relax the rules on the snapshots repository, so
> that anyone with an account will be able to publish snapshots of plugins to
> e.g. f
ented.
(If you think you have discovered a security issue with opening up snapshot
deployment like this, please file an issue in the SECURITY Jira project.)
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this
+1
On Dec 20, 2016 10:21 AM, "Daniel Beck" wrote:
> Hi everyone,
>
> Right now, snapshot deployment is limited to the users with permission to
> publish proper releases of the same component. This restriction exists to
> prevent unauthorized and possibly malicious releases of a component to
> us
+1. Can't think of a glaring hole with this change.
Le 20 déc. 2016 4:21 PM, "Daniel Beck" a écrit :
> Hi everyone,
>
> Right now, snapshot deployment is limited to the users with permission to
> publish proper releases of the same component. This restriction exists to
> prevent unauthorized a
Hi everyone,
Right now, snapshot deployment is limited to the users with permission to
publish proper releases of the same component. This restriction exists to
prevent unauthorized and possibly malicious releases of a component to users.
That reason does not apply to snapshots -- they are not
13 matches
Mail list logo
