se.
> Since the file is there I'm guessing the release plugin assumes :prepare
> has already run and :release uses the data in that file to perform the
> release. It has a svn url for scm.url so is probably the culprit here.
>
> /B
>
> 2018-03-09 4:48 GMT+01:00 Micha
i added the distribution management section while i was troubleshooting to
see if i could find what was wrong.
i tried everything i would read online..and this was one of them.
On Friday, March 9, 2018 at 6:37:33 AM UTC+3, Daniel Beck wrote:
>
>
> > On 9. Mar 2018, at 03:03, Mic
On 9. Mar 2018, at 03:03, Michael Michael > wrote:
> >
> > may i ask what these commands do then in the output trail? It seems that
> SVN is called in here, and this is the command that is failing
> > <<
> > [INFO] Resuming release from phase 'scm-commit-releas
one last thing. not sure if it is relevant or not, but i am using github's
two factor authentication for logging in. this is required by my
organization.
On Friday, March 9, 2018 at 5:03:18 AM UTC+3, Michael Michael wrote:
>
> hi Daniel,
>
> may i ask what these commands do t
/apprenda-plugin && svn
--non-interactive commit --file /tmp/maven-scm-1675137483.commit --targets
/tmp/maven-scm-9172792877660663843-targets
[INFO] Working directory: /root/apprenda-plugin
>>
On Friday, March 9, 2018 at 4:59:12 AM UTC+3, Daniel Beck wrote:
>
>
> >
if i also run "svn status" i get
<<
[root@jenkinsslavecentos apprenda-plugin]# svn status
svn: warning: W155007: '/root/apprenda-plugin' is not a working copy
>>
On Friday, March 9, 2018 at 4:56:58 AM UTC+3, Michael Michael wrote:
>
> i removed that line ri
:
>
>
> > On 9. Mar 2018, at 02:15, Michael Michael > wrote:
> >
> > can someone help?
> >
>
> Why are you specifying m-r-p 2.5.2 in your POM?
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" g
lassworlds.launcher.Launcher.launch
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main
(Launcher.java:356)
On Thursday, March 1, 2018 at 9:53:29 PM UTC+3, Michael Michael wrote:
>
> I update
:
>
> Also check your global Maven settings. Maybe it overrides release
> destinations there.
> The plugin's POM XML looks good to me (repo.jenkins-ci.org should be
> ideally switched to HTTPs).
>
> BR, Oleg
>
> On Thursday, March 1, 2018 at 6:15:13 PM UTC+1, Michae
wrote:
>
> Seems that somehow SVN is still configured (I don’t see it in your pom).
> Do you have some Subversion folders in your working copy?
> You don’t need subversion, everything is stored in git.
>
> Am 01.03.2018 um 08:20 schrieb Michael Michael >:
>
> hi there,
&
hi there,
i performed all the steps and got permission to upload our plugin using
the
https://github.com/jenkins-infra/repository-permissions-updater/blob/master/permissions/plugin-apprenda.yml
process.
However, i can't get maven to execute the full process correctly.
A few notes on my envir
11 matches
Mail list logo
