I think an infra that wants to prevent adopters for giving feedback on
snapshots is harmful for an open-source project. Are alternatives like
Sonatype OSSRH considered for replacement?
not sure as infra wants to avoid too much usage of r.a.o
so we will avoid noise
On Wed, 29 May 2019 at 17:00, Mickael Istria wrote:
> Thanks a lot!
> I think it would be worth a dedicated announce post on the mailing-list or
> other community channels (blog, twitter...).
>
--
Olivier
Concretely, m2e can now pretty easily test against Maven snapshot:
https://git.eclipse.org/r/142991 . This should allow m2e to detect and
report Maven issues sooner, and to adopt newer Maven shortly after release
as we can span integration effort all along the development phase instead
of starting
Thanks a lot!
I think it would be worth a dedicated announce post on the mailing-list or
other community channels (blog, twitter...).
Thanks!
merged with a small changes and everything working fine now (
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/maven-core/3.6.2-SNAPSHOT/
)
enjoy your fresh snapshots of Maven :)
cheers
Olivier
On Tue, 28 May 2019 at 23:13, Mickael Istria wrote:
> Ok, here
Ok, here is my proposal: https://github.com/apache/maven/pull/250
On Tue, 28 May 2019 at 15:27, Mickael Istria wrote:
> Why is the CI stuff in a dedicated repo and not on the main repo? Could we
> try to change it? That would make Maven more "normal" and more accessible
> in term of contribution.
> I found
Why is the CI stuff in a dedicated repo and not on the main repo? Could we
try to change it? That would make Maven more "normal" and more accessible
in term of contribution.
I found https://github.com/apache/maven/blob/master/Jenkinsfile in the main
repo. What is the purprose of this file vs the
PR welcome
the code is at https://github.com/apache/maven-jenkins-lib
Regards,
Hervé
Le lundi 27 mai 2019, 11:40:00 CEST Mickael Istria a écrit :
> Up!
> What's blocking for publication of snapshots from master to some snapshot
> repo? I'd gladly try to help.
Up!
What's blocking for publication of snapshots from master to some snapshot
repo? I'd gladly try to help.
Il dom 12 mag 2019, 23:01 Olivier Lamy ha scritto:
> +1
> definitely agree on that let's make it simple
> simple deploy of one build with java8 and voila.
> it's snapshot and NOT a release... so we do not have to jump on every bugs
> immediately.
>
Yes
+1
Enrico
It will be already a
+1
definitely agree on that let's make it simple
simple deploy of one build with java8 and voila.
it's snapshot and NOT a release... so we do not have to jump on every bugs
immediately.
It will be already a great forward to have quick feedback from maven
consumers
On Mon, 13 May 2019
IMO, if some patch managed to get to master, it's worth being released,
even if IT test fail.
So I would make the first step being a `mvn deploy` of what[s in master,
before running other tests.
I think this would be much simpler, allow community to test some "master"
snapshot even if it's bugged
Hello!
The Jenkins library revision can be specified in the Jenkinsfile. For exemple,
we can use a specific version of ‘my-shared-library’ with tag 1.0 by putting
the following line at the beginning of the Jenkinsfile:
@Library('my-shared-library@1.0') _
Regards,
Amine TAYEB CHERIF
Le 12
You can update the librairies as much as you want, without the need to
restart the instance. The shared libraries are cloned when the build
starts.
The fear I had during the hackergarten is more about the scope of the
change. Because the shared library is implicitly loaded, it means we cannot
notice 2:
one issue we had when working on such not so trivial Jenkins library updates
is: how to test locally before updating the production server, particularly
when the lib is shared then updates cannot be done without server restart?
this one probably deserves some
during latest Hackergarten in Paris [1], I had the chance to have Adrien
Lecharpentier [2] with me, then I gave him my ideal:
- deploy only from master = summary of previous discussions
- don't deploy until full ITs have been run on every platform, to avoid
deploying broken artifacts
- let for
Ok, thanks I'll try that.
But I'm still not really understanding what prevents Maven from calling
'mvn deploy' on that job to push snapshots to apache Maven repo. Anything
one can help with??
On Saturday, May 11, 2019, Sylwester Lachiewicz
wrote:
> Hi Mickael,
> i think You can try download
Hi Mickael,
i think You can try download latest snapshot dist from our Jenkins build
from master branch [1]
Sylwek
[1]
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven/job/master/lastSuccessfulBuild/artifact/org/apache/maven/apache-maven
czw., 9 maj 2019 o 14:55 Mickael
Hi all,
I'd like to set up for Tycho an automated build that runs it's master
against latest Maven snapshots, so we could more immediately spot
incompatibility like MNG-6642.
This should be quite easy to set up as a CI job.
However, what URL can I use to get access to the current snapshot of
20 matches
Mail list logo
