Hi,
I was asked if I would be interested in becoming a maintainer for the
CppCheck plugin and advised to post a request here if so.
Thanks
Craig
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To unsubscribe from this group and stop
https://github.com/jenkinsci/bearychat-plugin
I left out the 'jenkins-', as it's redudant for Jenkins plugins in the
jenkinsci org.
Tell us your jenkins-ci.org user name (used on Wiki and in Jira;
jenkins-ci.org/account) and we can create a component in Jira for you.
On 10.11.2014, at 07:03,
Hello,
have you checked the Workaround section in the page you mentioned? There
has been a lot of reported issues because of mixing old
maven-release-plugin and recent git versions.
Vincent
2014-11-10 8:26 GMT+01:00 levsa levon...@gmail.com:
Hi,
I'm having trouble releasing the xvnc-plugin
On 9 November 2014 01:16, Daniel Beck m...@beckweb.net wrote:
A few days ago I renamed most components in Jira as decided in the
governance meeting to add a -plugin suffix to each name (foo - foo-plugin)
to make it clear to users that e.g. 'logging' or 'slave-setup' are plugins
and not
Thank you!
And my jenkins-ci.org account is otbzi
--
otbzi
曾凡禹
http://www.douban.com/people/otbzi/
http://weibo.com/u/1976871651
https://twitter.com/otbzi
https://github.com/otbzi
On 10 November, 2014 at 5:27:29 pm, Daniel Beck (m...@beckweb.net) wrote:
Yes, the groovy script console should have access to all classes in Jenkins
including plugin classes.
On Mon, Nov 10, 2014 at 6:51 AM, munsingh munsi...@gmail.com wrote:
Thanks Robert.
QQ: How do I instantiate this class via groovy script, can I import this
class in groovy and use it?
Ok. I tried creating an instance of SSHLauncher class in my script and
imported the plugins as follows:
import hudson.plugins.sshslaves.*;
And I try to instantiate the SSHLauncher object by calling:
new SSHLauncher( 172.16.222.142, 22, jenkins )
however I get the error:
startup failed:
Hi,
Not sure how this has happened, but the update-center.json shows the latest
version of the integrity-plugin as 1.17 when in fact the latest is 1.28. How
do I fix this problem?
Thanks!
Cletus
--
You received this message because you are
Ok I got it working. I was trying to execute my script as part of a job via
the Execute System Groovy Script-Groovy Command option. The Check-Syntax
was unable to check the syntax as it was unable to find the SSHSlaves
class. However it was working when running the job.
This could be a bug in
Same problem with our plugin:
https://wiki.jenkins-ci.org/display/JENKINS/ClearCase+UCM+Plugin. Shows
latest release 1.4.4 (one year ago, We're currently at 1.5.4),
On Mon, Nov 10, 2014 at 12:12 PM, Cletus D'Souza cletusdso...@hotmail.com
wrote:
Hi,
Not sure how this has happened, but the
Jenkins passes the current version as parameter to the update center. Try
http://updates.jenkins-ci.org/update-center.json?version=1.588 and you'll get
the current versions.
The one without argument is the oldest possible, that's probably what breaks
the wiki. Filed as INFRA-196.
On
Hi All,
I have installed sonar and artifactory plugin in jenkins. I want to do both
sonar and artifactory configurations via groovy script.
I am able to do using GUI Manage Jenkins - configure system but need to do
similar activity via groovy script.
Anyone please help me on this.
Thanks,
On 10.11.2014, at 11:30, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
There should be two components:
literate-api
literate-plugin
The literate-api is a separate beast that is potentially independent of
Jenkins in order to allow people to develop additional tooling, we may
+1 for the rename,
but would we not need some kind of aliasing in the core for to ease renaming.
after all, there are plugins which have dependencies to others in the code by
there name like this (or similar): updateCenter.getPlugin(“ghprb”)
Domi
On 10.11.2014, at 14:38, Daniel Beck
This is just about the Jira component. Independent of plugin artifactId, repo
name, wiki page name, or anything else.
On 10.11.2014, at 16:58, domi d...@fortysix.ch wrote:
+1 for the rename,
but would we not need some kind of aliasing in the core for to ease renaming.
after all, there are
On Sun, Nov 9, 2014 at 5:00 AM, Jeremy Marshall
jeremystuartmarsh...@gmail.com wrote:
I'd like to add a 'file form workspace' option to the script security
plugin. A radio button where you can pick either a script or a file from
SCM. I've been trying to add this in but I think the main problem
On Mon, Nov 10, 2014 at 11:21 AM, Daniel Beck m...@beckweb.net wrote:
This is just about the Jira component. Independent of plugin artifactId, repo
name, wiki page name, or anything else.
-1; I think JIRA component names should consistently follow the plugin
shortName.
--
You received this
On 10.11.2014, at 19:19, Jesse Glick jgl...@cloudbees.com wrote:
-1; I think JIRA component names should consistently follow the plugin
shortName.
The short names are almost never exposed on the UI. Are you going to fix all
the crap that gets filed because regular users simply cannot find
Well It works on my machine (TM)
println(hudson.plugins.sshslaves.SSHLauncher.class.getName())
provides an output without an error. Try that.
It could be mistaking the error from that there is no known constructor
that only takes three arguments from what I can see?
/B
On Mon, Nov 10, 2014
Alright, I was afraid of changing git history by removing the failed
release commit, so I ended up just making version 1.0.1 even though there's
no changes.
This time I used the full maven-release-plugin 2.5 name and I noticed a
different output, and I can now see my plugin in the repositories.
On Mon, Nov 10, 2014 at 1:28 PM, Daniel Beck m...@beckweb.net wrote:
Renaming plugins with weird short names isn't really possible
I think we should focus on fixing that, rather than introducing ad-hoc
inconsistencies to a small percentage of cases that will invariably
lead to a hard-to-notice
I thought the idea was to make these be fully aligned.
This request has multiple goals, none of them are about the short name:
- Remove redundant or unused components (the latter only if no related repo or
plugin can be found)
- Add the plugin suffix for components I skipped in the first run
Hi,
it seems like the automatically created plugin info hasn't been updated
since 2012:
https://wiki.jenkins-ci.org/display/JENKINS/Jabber+Plugin
Latest release show 1.25, but it should at least show 1.28 (1.29 was
released today, so probably not in there, yet)
--
You received this message
Hello fellow devs!
I'd like to move away from using CSS and start using LESS in my Jenkins
Build Monitor Plugin. Of course LESS can be compiled to CSS using the wro4j
library together with the wro4j-maven-plugin quite easily, so the
build-time LESS-to-CSS generation is not at all a problem.
Done!
https://issues.jenkins-ci.org/browse/JENKINS/component/19827
On 11.11.2014, at 00:35, Tyler Fitch tfi...@gmail.com wrote:
Hello,
I went to add a new feature to my Chef Identity plugin and didn't seem it on
the Components list in Jira. Looks like I need to send a request to this
25 matches
Mail list logo
