You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Neil C Smith <ne...@apache.org> on 2020/09/07 09:35:59 UTC

Installer move and website update

Hi,

I'm chasing up with infra but still can't connect to either dist.a.o
or netbeans.a.o.

If anyone wants to move the Windows and Linux installers to release,
and link them in to the website, please feel free to do so.  I cannot
at the moment!

If the mac installer is still there (can't check) don't move that to release.

Not sure why the problem - only thing I can think of is hammering
repository.a.o with 7GB of data the other day, but I can still access
that - so Maven vote about to kick off.

Thanks,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Installer move and website update

Posted by John Mc <mc...@gmail.com>.
Hi,

I've made a change to the mac osx installer and had some users test that it
could be installed on BigSur.  I've triggered the notarisation process now,
so I should be getting another vote started for this installer within the
next 24 hours.

Regards

John

On Mon, 7 Sep 2020 at 12:18, Neil C Smith <ne...@apache.org> wrote:

> On Mon, 7 Sep 2020 at 11:53, Eric Barboni <sk...@apache.org> wrote:
> >
> > Hi Neil I'm on it.
>
> Thanks!  I've fixed up redirects on the VM for the update centre too.
> Hopefully it's good - checked with curl from there.  Again, no access
> to parts of the chain here so it's timing out.
>
> I've copied over the licenses files as we had for 12.0-u1 too for now
> - probably better handled by a different redirect at some point - will
> have a look at that some time.
>
> Best wishes,
>
> Neil
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>

Re: Installer move and website update

Posted by Neil C Smith <ne...@apache.org>.
On Mon, 7 Sep 2020 at 11:53, Eric Barboni <sk...@apache.org> wrote:
>
> Hi Neil I'm on it.

Thanks!  I've fixed up redirects on the VM for the update centre too.
Hopefully it's good - checked with curl from there.  Again, no access
to parts of the chain here so it's timing out.

I've copied over the licenses files as we had for 12.0-u1 too for now
- probably better handled by a different redirect at some point - will
have a look at that some time.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




RE: Installer move and website update

Posted by Eric Barboni <sk...@apache.org>.
Hi Neil I'm on it.

-----Message d'origine-----
De : Neil C Smith <ne...@apache.org> 
Envoyé : lundi 7 septembre 2020 11:36
À : dev <de...@netbeans.apache.org>
Objet : Installer move and website update

Hi,

I'm chasing up with infra but still can't connect to either dist.a.o or netbeans.a.o.

If anyone wants to move the Windows and Linux installers to release, and link them in to the website, please feel free to do so.  I cannot at the moment!

If the mac installer is still there (can't check) don't move that to release.

Not sure why the problem - only thing I can think of is hammering repository.a.o with 7GB of data the other day, but I can still access that - so Maven vote about to kick off.

Thanks,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




RE: Installer move and website update

Posted by Eric Barboni <sk...@apache.org>.
I'm not aware of such a cli like tools (we have no maven project in this phase).

I populate RELEASE120 with inconsistent cluster pom dependencies. Only at build time of an application (for fun) involving 1 of the 2 bad constructed pom. So I had to go for RELEASE120-1.

Best Regards
Eric

-----Message d'origine-----
De : Neil C Smith <ne...@apache.org> 
Envoyé : mardi 8 septembre 2020 18:28
À : dev <de...@netbeans.apache.org>
Objet : Re: Installer move and website update

On Tue, 8 Sep 2020 at 14:50, Randall Wood <ra...@alexandriasoftware.com> wrote:
> The maven-enforcer-plugin can enforce a no snapshot rule prior to 
> uploading, but I don’t know of any ant toolkit that can enforce that

Strictly speaking I'm not sure if it would - at least the version wasn't a snapshot in this case, it was in the artefact ID.  Maybe other rules (ban dependencies?) could do this though?

Ideally we'd be able to run all the checking that uploading and closing the staging repository does locally before attempting to upload.  This doesn't have to involve Ant - the process already involves some local work and direct use of nexus-staging-maven-plugin
- could run other Maven plugin actions directly (and in a CI check).

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Installer move and website update

Posted by Neil C Smith <ne...@apache.org>.
On Tue, 8 Sep 2020 at 14:50, Randall Wood
<ra...@alexandriasoftware.com> wrote:
> The maven-enforcer-plugin can enforce a no snapshot rule prior to uploading, but I don’t know of any ant toolkit that can enforce that

Strictly speaking I'm not sure if it would - at least the version
wasn't a snapshot in this case, it was in the artefact ID.  Maybe
other rules (ban dependencies?) could do this though?

Ideally we'd be able to run all the checking that uploading and
closing the staging repository does locally before attempting to
upload.  This doesn't have to involve Ant - the process already
involves some local work and direct use of nexus-staging-maven-plugin
- could run other Maven plugin actions directly (and in a CI check).

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Installer move and website update

Posted by Randall Wood <ra...@alexandriasoftware.com>.
The maven-enforcer-plugin can enforce a no snapshot rule prior to uploading, but I don’t know of any ant toolkit that can enforce that

Randall Wood

> On Sep 8, 2020, at 09:36, Neil C Smith <ne...@apache.org> wrote:
> 
> On Tue, 8 Sep 2020 at 13:24, Eric Barboni <sk...@apache.org> wrote:
>> I would say it's better to close it and avoid merging on same staging repo. But will this help the plugin ?
> 
> I'm not suggesting that, just closing it manually via the web UI.  The
> plugin attempts to auto-close, times out, and then deletes the staging
> repository - seems to be doing roughly what is described at
> https://issues.sonatype.org/browse/NEXUS-10174
> 
>> For SNAPSHOT we may need detection at
>> 1) maven level by  fixing nb-repository-plugin so we fail the build for release (globally) .  (On a normal maven release the release plugin to that kind of check but what we do it's not standard)
>> 2) ant level by failing build in case of SNAPSHOT text detected in the maven dependencies type of external.
>> 
>> Option 2 sounds  better because it fail earlier.
> 
> Agreed on that, but I wondered if there was anyway to test the full
> repository against all the Apache rule set locally?  Would pick up
> other potential problems before hitting repository.a.o with 800MB.
> 
> Best wishes,
> 
> Neil
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
> For additional commands, e-mail: dev-help@netbeans.apache.org
> 
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> 
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Installer move and website update

Posted by Neil C Smith <ne...@apache.org>.
On Tue, 8 Sep 2020 at 13:24, Eric Barboni <sk...@apache.org> wrote:
>  I would say it's better to close it and avoid merging on same staging repo. But will this help the plugin ?

I'm not suggesting that, just closing it manually via the web UI.  The
plugin attempts to auto-close, times out, and then deletes the staging
repository - seems to be doing roughly what is described at
https://issues.sonatype.org/browse/NEXUS-10174

>  For SNAPSHOT we may need detection at
> 1) maven level by  fixing nb-repository-plugin so we fail the build for release (globally) .  (On a normal maven release the release plugin to that kind of check but what we do it's not standard)
> 2) ant level by failing build in case of SNAPSHOT text detected in the maven dependencies type of external.
>
> Option 2 sounds  better because it fail earlier.

Agreed on that, but I wondered if there was anyway to test the full
repository against all the Apache rule set locally?  Would pick up
other potential problems before hitting repository.a.o with 800MB.

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




RE: Installer move and website update

Posted by Eric Barboni <sk...@apache.org>.
Hi Neil,
 I would say it's better to close it and avoid merging on same staging repo. But will this help the plugin ?

 For SNAPSHOT we may need detection at 
1) maven level by  fixing nb-repository-plugin so we fail the build for release (globally) .  (On a normal maven release the release plugin to that kind of check but what we do it's not standard)
2) ant level by failing build in case of SNAPSHOT text detected in the maven dependencies type of external. 

Option 2 sounds  better because it fail earlier.

Best Regards
Eric
-----Message d'origine-----
De : Neil C Smith <ne...@apache.org> 
Envoyé : mardi 8 septembre 2020 12:00
À : dev <de...@netbeans.apache.org>
Objet : Re: Installer move and website update

On Mon, 7 Sep 2020 at 10:35, Neil C Smith <ne...@apache.org> wrote:
> Not sure why the problem - only thing I can think of is hammering 
> repository.a.o with 7GB of data the other day, but I can still access 
> that - so Maven vote about to kick off.

OK, confirmation from infra that my IP was blocked due to going over the ban limit on repository.a.o.  We may need to be aware of that as we're uploading so much - only takes a few failures.

Firstly, I think we need to add -DskipStagingRepositoryClose=true in the documented command to stop the plugin timing out and dropping everything?

Secondly, is there a way to validate the repository against upload and closing rules to pick up potential failures (eg. SNAPSHOT) before pushing to staging?

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists




Re: Installer move and website update

Posted by Neil C Smith <ne...@apache.org>.
On Mon, 7 Sep 2020 at 10:35, Neil C Smith <ne...@apache.org> wrote:
> Not sure why the problem - only thing I can think of is hammering
> repository.a.o with 7GB of data the other day, but I can still access
> that - so Maven vote about to kick off.

OK, confirmation from infra that my IP was blocked due to going over
the ban limit on repository.a.o.  We may need to be aware of that as
we're uploading so much - only takes a few failures.

Firstly, I think we need to add -DskipStagingRepositoryClose=true in
the documented command to stop the plugin timing out and dropping
everything?

Secondly, is there a way to validate the repository against upload and
closing rules to pick up potential failures (eg. SNAPSHOT) before
pushing to staging?

Best wishes,

Neil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.apache.org
For additional commands, e-mail: dev-help@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists