Re: Plugin Tutorial seems broken, help wanted

[Sean Jones]

I ran mvn help:effective-settings and it only showed me my local 
repository. I double checked my .m2 folder and I had named settings.xml to 
setting.xml.

*sigh* Sorry for wasting your time but thank you for your help!

On Wednesday, March 16, 2016 at 9:38:46 PM UTC, Baptiste Mathus wrote:
>
> Normally, that should come from http://repo.jenkins-ci.org/public/
>
> Which maven version do you use?
> What's in mvn help:effective-settings?
>
> HTH
>
> 2016-03-16 1:52 GMT+01:00 Sean Jones <neurals...@gmail.com >:
>
>> I am trying to break a plugin up to date but I am not having much luck 
>> with Maven.
>>
>> I decided to try create a plugin from scratch, copy the source over and 
>> add the dependencies one at a time to clean things up.
>>
>> However, the Plugin Tutorial 
>> <https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial> appears 
>> not to work.
>>
>> My .m2/settings.xml only has the contents they page wants and executing 
>> the command
>>
>> mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create
>>>
>>>
>> But I get this error:
>>
>> [INFO] Scanning for projects...
>> Downloading: 
>> https://repo.maven.apache.org/maven2/org/jenkins-ci/tools/maven-hpi-plugin/maven-metadata.xml
>> [INFO] 
>> 
>> [INFO] BUILD FAILURE
>> [INFO] 
>> 
>> [INFO] Total time: 1.161 s
>> [INFO] Finished at: 2016-03-16T00:39:38+00:00
>> [INFO] Final Memory: 12M/309M
>> [INFO] 
>> 
>> [ERROR] Error resolving version for plugin 
>> 'org.jenkins-ci.tools:maven-hpi-plugin' from the repositories [local 
>> (/Users/neuralsandwich/.m2/repository), central (
>> https://repo.maven.apache.org/maven2)]: Plugin not found in any plugin 
>> repository -> [Help 1]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the 
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions, 
>> please read the following articles:
>> [ERROR] [Help 1] 
>> http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException
>>
>> Any help would be great, thank you. 
>>
>> -- 
>> 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 jenkinsci-de...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-dev/f843f2fd-a8a9-4fd4-b9e6-7342866ff5aa%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/jenkinsci-dev/f843f2fd-a8a9-4fd4-b9e6-7342866ff5aa%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/41ea0f4c-bb2a-4030-adb5-2342b4ecf270%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Plugin Tutorial seems broken, help wanted

[Sean Jones]

I am trying to break a plugin up to date but I am not having much luck with 
Maven.

I decided to try create a plugin from scratch, copy the source over and add 
the dependencies one at a time to clean things up.

However, the Plugin Tutorial 
 appears not 
to work.

My .m2/settings.xml only has the contents they page wants and executing the 
command

mvn -U org.jenkins-ci.tools:maven-hpi-plugin:create
>
>
But I get this error:

[INFO] Scanning for projects...
Downloading: 
https://repo.maven.apache.org/maven2/org/jenkins-ci/tools/maven-hpi-plugin/maven-metadata.xml
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 1.161 s
[INFO] Finished at: 2016-03-16T00:39:38+00:00
[INFO] Final Memory: 12M/309M
[INFO] 

[ERROR] Error resolving version for plugin 
'org.jenkins-ci.tools:maven-hpi-plugin' from the repositories [local 
(/Users/neuralsandwich/.m2/repository), central 
(https://repo.maven.apache.org/maven2)]: Plugin not found in any plugin 
repository -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException

Any help would be great, thank you. 

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/f843f2fd-a8a9-4fd4-b9e6-7342866ff5aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Enabling Jenkins to Build Git Tags

[Sean Jones]

Does this work? I have been attempting to do this but the latest commit 
from master is always built.

On Friday, April 12, 2013 2:20:08 AM UTC+1, Jon Schewe wrote:

 Are you saying that I should put +refs/tags/*:refs/remotes/origin/tags/* 
 in the Refspec field under advanced and */tags/* in the branch specifier 
 and that will build only tags?


 On Mon, Apr 8, 2013 at 7:49 AM, Christopher Orr ch...@orr.me.uk 
 javascript: wrote:

 Hi there,

 You can already do most of this with (for example):

 Refspec: +refs/tags/beta/*:refs/remotes/origin/tags/beta/*
 Branch spec: */tags/beta/*

 We use that config to cause a build only when a new tag called 
 beta/whatever is pushed.  No branches are built.

 I think the one thing missing that you've added is the full wildcard 
 support.  So maybe it would be better to add generic full wildcard support 
 to ref- and branch-specs, rather than adding this tag-specific feature?

 Maybe Nicolas has some other ideas...

 Regards,
 Chris



 On 07/04/13 09:34, ryenus wrote:

 Is there anyone interested in allowing Jenkins to build tags as well
 other than just branches?

 In our team, we have a special requirement that every tag pushed to our
 Git repository should trigger a Jenkins build. We've done that via some
 customization to the Jenkins Git Plugin:

 I've attached the patch (based on git-1.2.0), and a screen shot of the
 result build configuration section and it's working as expected.

 Notes:
 1. The patch is made in a way that by default nothing would be changed.
 2. By setting the 'Tags to build' field, you can specify shell patterns
 as in `git tag -l pattern` to specify the tags to be built.
 3. By checking the 'Don't build branches' checkbox, branches can be 
 skipped

 I'm curious about whether this could be adopted by the community, and
 how? I'd love to hear your feedback.

 Cheers

 --
 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 jenkinsci-de...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.


  
 -- 
 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 jenkinsci-de...@googlegroups.com javascript:.
 For more options, visit https://groups.google.com/groups/opt_out.





 -- 
 http://mtu.net/~jpschewe

  

-- 
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 jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.