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, 2018 at 1:39:24 PM UTC+3, Robert Sandell wrote:
>
> 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 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 Michael Michael <[email protected] <javascript:>
> >:
>
>> 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 <[email protected]> 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... 
>>> > [INFO] Executing: /bin/sh -c cd /root/apprenda-plugin && svn 
>>> --non-interactive commit --file /tmp/maven-scm-1675137483.commit --targets 
>>> /tmp/maven-scm-9172792877660663843-targets 
>>> > [INFO] Working directory: /root/apprenda-plugin 
>>> > >> 
>>> > 
>>>
>>> Are you working in a Git repository (working copy), or did you download 
>>> the sources? Perhaps it checks if you're in a Git repo, and if not, falls 
>>> back to SVN? IOW, in the directory that also contains pom.xml, does `git 
>>> status` show an error? 
>>>
>>> Besides that, 
>>> https://github.com/jenkinsci/apprenda-plugin/blob/b0e8592ba5b83f3ee63802bdf9a83ee14c84d3bc/pom.xml#L54
>>>  
>>> should be long obsolete, so it's unclear to me how you managed to deploy a 
>>> snapshot with that. (Unrelated to SCM problems though.) 
>>>
>>> -- 
>> 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 it, send an 
>> email to [email protected] <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/9dbd768f-c3c8-47f5-a59a-d394f2bb0220%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/9dbd768f-c3c8-47f5-a59a-d394f2bb0220%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> *Robert Sandell*
> Software Engineer
> CloudBees, Inc.
> [image: CloudBees-Logo.png] <http://www.cloudbees.com/>
> E: [email protected] <javascript:>
> Twitter: robert_sandell
>

-- 
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 it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/fdaf0350-bc09-4746-989b-c5ad7d3b8702%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to