I am releasing this plugin to deliver the feature early. In the meantime,
someone might find it useful.
https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Realtime+Test+Reporter+Plugin
--
You received this message because you are subscribed to the Google Groups
Jenkins Developers group.
To
Hi Stephan,
unfortunately I was not able to catch you lately on the chat, but I have
question I want your opinion before I go ahead with my implementation.
I'm working on the credentials integration for the settigns.xml again and I
have some questions about the usage of domains in the
My view is that you can add a Maven Server Id domain specification and
requirement pair of classes. Thus people can add those specifications to
their domains and presto-chango... magic happens
On 16 August 2013 10:37, domi d...@fortysix.ch wrote:
Hi Stephan,
unfortunately I was not able to
To put this another way, I could have called them credentials zones or
federation zones or something like that...
they are just a set of specifications that say when these credentials are
appropriate. The most obvious specifications are hostname, scheme, etc...
but the specifications and
I see, that makes perfect sense - thanks for the clarification!
Domi
Am 16.08.2013 um 12:03 schrieb Stephen Connolly
stephen.alan.conno...@gmail.com:
To put this another way, I could have called them credentials zones or
federation zones or something like that...
they are just a set of
The way specifications work, by the way, is that if there is a requirement
that a specification applies to then the specification can decide is the
requirement is:
* a hard match - don't check this requirement against any more
specifications
* a soft match - check this requirement against any
So if you create a domain with the specification:
* schemes: http, https, ssh, svn
* hostnames: *.acme.org
* maven server ids: acme-*
* widget colour: red, green
And a plugin asks for credentials with the domain requirements of
* maven server id: acme-foobar
Then in evaluating the domain
Hi,
I've created a pull request for the backend-jenkins-plugin-info-plugin
repo: https://github.com/jenkinsci/backend-jenkins-plugin-info-plugin/pull/4
I know the wait time has not passed on this, but there's another pull
request on the same repo that's 9 months old.
I'd be happy to merge
Hi,
It seems that the daemon listens to all repos and all branches belonging
to the jenkinsci organisation. When I reverted a couple of commits on the
stable branch it got linked to the jira[1] so it might seem to get
reverted in master which it was not. (in case you are wondering why the
at http://mirrors.jenkins-ci.org/ in the stable-rc column.
--
Kohsuke Kawaguchi
--
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
On Fri, Aug 16, 2013 at 10:02 AM, oliver gondža ogon...@gmail.com wrote:
I prefer to link only commit that are in master branch of a repository.
Presumably if a commit is initially pushed to some other branch, and
then that branch is merged into master, you want the notification—even
though the
Hi all,
I'm attempting to write a buildflow extension.
However as soon as I attempt to register the extension (not even use it)
all existing flow functionality breaks.
e.g.
the following DSL:
def concExt = extension.build-flow-concurrent-extensions
build(job1, param: build.number)
build(job2,
Can you publish this on some github repo so I can check ?
(or share in private = nicolas.del...@gmail.com / github:ndeloof)
2013/8/16 teilo teilo+goo...@teilo.net
Hi all,
I'm attempting to write a buildflow extension.
However as soon as I attempt to register the extension (not even use it)
I'm working though legal to get the extension and fixes to buildflow
approved - and I can't share until that happens.
However I think I have found the cause (and confusion).
I tried using
def concExt = extension.bogus-wibble
and my extension is called with bogus as the extension name not
Thanks to all for feedback and contribution,
Ownership Plugin v. 0.2.1 is available for download.
I've added usage guidelines and examples to the Wiki, so at the current
state plugin is ready for public use.
Best regards,
Oleg Nenashev
www.synopsys.com
суббота, 13 июля 2013 г., 23:12:50
On Friday, August 16, 2013 3:42:25 PM UTC+2, Jim Gallagher wrote:
Hi,
I've created a pull request for the backend-jenkins-plugin-info-plugin
repo:
https://github.com/jenkinsci/backend-jenkins-plugin-info-plugin/pull/4
I know the wait time has not passed on this, but there's another pull
I have 10+ git repositories pulled down for the same Jenkins job. I use
repo-pluggin Repo+Plugin [1] and Gerrit trigger pluggin. Hope this solves
our issue.
Asmund
[1] https://wiki.jenkins-ci.org/display/JENKINS/Repo+Plugin
Den 15. aug. 2013 13:23 skrev Sapone mylniko...@gmail.com følgende:
Hello,
Could anybody configure a default assignee for several components in JIRA?
My user id is oleg_nenashev.
Components to be modified:
• ownership: component/17721
• custom-tools: component/17446
• customtools-plugin: component/16520 (BTW, it would be great to merge
components somehow)
•
18 matches
Mail list logo