Well, alright, thank you.
Here are my changes:
https://github.com/jenkinsci/slack-plugin/commit/28c09a905b936cf259a55d43223090ac3c23f9f8
Unfortunately, it failed:
https://slack-files.com/T024BE7LD-F024KPN92-bd3386/mvn_release_full.txt
What did I do wrong?
On Thu, Dec 12, 2013 at 5:59 PM, Jesse
Hi all,
I would like to write a plugin which executes a build step to compile
a Green Hills Integrity RTOS project using their MULTI compiler. Are
there any legal issues with me writing this plugin since I am in no
way affiliated with Green Hills?
Thanks,
Woz
--
You received this message becaus
On Thu, Dec 12, 2013 at 7:08 PM, Myles Grant wrote:
> Is there something wrong in my pom.xml?
Delete the distributionManagement, the maven-release-plugin
configuration, and the groupId and try again.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Develope
Hello,
I recently released a plugin and got jenkins-ci.org hosting. The plugin
resides at: https://github.com/jenkinsci/slack-plugin
I am trying to get this plugin listed in the directory. The first time I
did an mvn release, it seemed to work fine, but never showed up in the
directory in my j
So I've hand removed those lines from beta2 and the templates are happy.
What's not so happy is the "Use Rest API" - all I get when I enter a username
password and try to test is "Connection error : peer not authenticated"
I even tried a user in the Gerrit Administrators group but I still get th
On Wed, Dec 11, 2013 at 5:02 PM, Daniel Beck wrote:
> JENKINS-16936: This allows use of advanced API features disabled by default
FYI, I have written a plugin exercising this extension point:
https://wiki.jenkins-ci.org/display/JENKINS/Secure+Requester+Whitelist+Plugin
--
You received this mes
Hi,
i have a requirement to save the build data to database.
Requirement is to get the tag name being built in java class (custom
plug-in to develop),
Is there any simple way to get the tag name into java class.
My class extends Builder class, tried all the ways to get the SVN tag name
but di
You can make the dependency to the dashboard view optional. You can have a
look at the findbugs plugin: here I'm providing some portlet's related to
findbugs. If the user does not install the dashboard view, then the
portlets just not show up, without causing a failure...
Am Donnerstag, 12. Dezemb
On Thu, Dec 12, 2013 at 4:54 AM, James Nord (jnord) wrote:
> although the actual job that
> the trigger will be added to will eventually be some form of
> hudson.model.Job
Indeed a FreestyleProject, in the example given.
> when the configuration jelly is called it’s not actually
> the job that’s
Yes, this variable is not used anywhere, so we can remove the tag safely.
On Thursday, December 12, 2013 4:41:15 AM UTC-5, Robert Sandell wrote:
>
> Actually the GerritTrigger class is quite explicit in its declaration to
> Jenkins that it asserts AbstractProject to be the item it is added to.
>
I would definitely suggest adding new portlets as new plugins. Then it's up
to you to categorize them... In your case I see two different plugins, one
for sonar, one for all the others.
My idea would be to have all the portlets out of the main plugin (which
then would contain only the infrastructur
I think we cannot add the sonar portlets to the sonar plugin, because that
would introduce the dependency to the dashboard plugin (this would mean
forcing all users of the sonar plugin to install the dashboard plugin).
It would be an option to add the portlets to the dashboard view plugin - on
Hi everyone,
I've published a new plugin developed by Kalray on github:
https://github.com/nmorey/parameterized-build-QDH
The goal of this plugin is to be able to merge builds in the build queue if
they have the same value for a list of specified parameters.
We use a lot of project whose parame
I assumed wrongly that the declaration "class GerritTrigger extends
Trigger" was signal enough to core that it only applied to
AbstractProject, but upon further inspection I noticed that the descriptor is
returning true for everything in the isApplicable(Item) method. It should be
checking for
Hi,
I am using SVN for version controlling and Jenkins for continuous
integration.
I am using a script, on the Jenkins machine only, to build the PDF files
after building the .sln file.
Now I want to upload these PDF files to SVN server so that everyone would
be able to see the PDF files.
1) In
That is correct as I read the template code... but Jesse has spent more
time in the templates plugin and KK wrote it while I was working on the
RBAC plugin... so I usually defer to KK on this plugin
On 12 December 2013 09:54, James Nord (jnord) wrote:
> In this case as this is a Cloudbees Temp
Hi Ulli,
Thanks for your help, but still no luck for me.
This is what I get:
C:\...\GitHub\webload-plugin [master]> git push
Warning: Permanently added 'github.com,192.30.252.129' (RSA) to the list of
known hosts.
ERROR: Permission to jenkinsci/webload-plugin.git denied to jane-king.
fatal: Cou
In this case as this is a Cloudbees Template although the actual job that the
trigger will be added to will eventually be some form of hudson.model.Job when
the configuration jelly is called it's not actually the job that's being
configured but the template instance - which isn't even a Hudson.m
I can probably construct a literate build job or any multi-branch based
project job that would blow up if you are assuming that you are always
being added to an AbstractProject...
On 12 December 2013 09:41, Sandell, Robert wrote:
> Actually the GerritTrigger class is quite explicit in its declar
Actually the GerritTrigger class is quite explicit in its declaration to
Jenkins that it asserts AbstractProject to be the item it is added to. Whatever
kind of trickery the template plugin does after that is somewhat beyond its
control.
On the other hand I did a quick usage search for the trig
I do think the Claim Plugin allows to claim test failures. It's available
as a new option as part of existing test results report actions (Look for
Additional test report features)
Vincent
2013/12/12 Otto P
> Hi Vincent,
>
> Thanks for the hint - this plugin is a step in the right direction. I
Hi Vincent,
Thanks for the hint - this plugin is a step in the right direction. I'll
see how far it gets us. Originally I was thinking about something smart
that reports back in the context of a particular failing test, but simply
doing it per failed build is already helpful.
Cheers
Otto
O
22 matches
Mail list logo
