Robert and Baptiste, you were 100% correct. Removing the checked in
release.properties file fixed this issue. it was checked in by the previous
developer of this plugin and i did not realize its impact.
thank you for all your help.
I am able to release to the artifactory now.
On Friday, March 9,
I see a checked in release.properties in the root
https://github.com/jenkinsci/apprenda-plugin/blob/master/release.properties
that shouldn't be there. Probably accidentally checked in from some earlier
botched release.
Since the file is there I'm guessing the release plugin assumes :prepare
has alr
You committed & push the release.properties and pom.xml.releaseBackup
files, delete and add them to .gitignore to never ever do it again.
Also, the version in the pom.xml should always contain -SNAPSHOT in the
end. Only the release plugin will remove it when releasing.
Cheers
2018-03-09 4:48 GMT
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, Michael Michael > wr
i am working in a git repository. see command output below.
<<
[root@jenkinsslavecentos apprenda-plugin]# git status
# On branch master
nothing to commit, working directory clean
[root@jenkinsslavecentos apprenda-plugin]# dir pom.xml
pom.xml
[root@jenkinsslavecentos apprenda-plugin]# pwd
/root/appr
> 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-release'
> [INFO] Checking in modified POMs...
>
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 then in the output tr
hi Daniel,
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-release'
[INFO] Checking in modified POMs...
[INFO] Executing: /bin/sh -c cd /root/apprenda-plugin &
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 right now, cleaned up the target and the
> On 9. Mar 2018, at 02:56, Michael Michael wrote:
>
> i need to be setting up for SVN and its communication/interaction with git.
It's unclear why you're asking this. Subversion should not be involved at all.
Git is its replacement for us. Whatever link you followed is probably long
obsolete
i removed that line right now, cleaned up the target and the .m2\repository
folders and still seeing the same failure.
is there anything specific i need to be setting up for SVN and its
communication/interaction with git.
On Friday, March 9, 2018 at 4:34:42 AM UTC+3, Daniel Beck wrote:
>
>
> > O
> 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" group.
To unsubscribe from this group and stop receiving emails from i
is there anyone that can provide additional guidance? i installed a linux
virtual machine running CentOS 7.4 and i am still hitting the same issue.
Some additional, but important details.
* If i just run "mvn deploy", my package is uploaded the artifactory. so my
creds in settings.xml are accura
I updated the repo.jenkins-ci.org to be https.
I also checked my maven\conf\settings.xml and it is the vanilla one that
comes with installation (everything is commented out).
any other ideas? thanks for the pointers so far.
On Thursday, March 1, 2018 at 11:36:14 AM UTC-6, Oleg Nenashev wrote:
>
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, Michael Michael wrote:
>
> thank you Ullrich for the re
thank you Ullrich for the reply.
i don't see any subversion folders in my git repo working folder. is there
something specific i should be looking for?
i deleted everything and cloned my repo again and i got the same error.
On Thursday, March 1, 2018 at 3:24:46 AM UTC-6, Ullrich Hafner 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,
>
> i performed all the steps and got permi
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
18 matches
Mail list logo
