Re: New Allure report publisher plugin
Can anybody handle this please? That's a good plugin! On Wednesday, May 21, 2014 3:53:32 PM UTC+4, Denis Chernilevskiy wrote: Hello! I'd like to publish our Allure report publisher plugin. The plugin is currently hosted here: https://github.com/allure-framework/allure-jenkins-plugin My GitHub ID is dchr. Please also add eroshenkoam, pupssman, vania-pooh, mavlyutov to supporters list and give them commit rights. We're currently using it widely across our company and will present it at a conference soon, so it would be great to get it published as soon as possible. Thanks a lot in advance for your assistance! P.S. Our company is already hosting a Debian package builder plugin and maintaining JClouds plugin. -- 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.
Re: What does FS mean in Remote FS root?
On Wed, May 21, 2014 at 6:00 AM, Stéphane Bruckert
stephane.bruck...@gmail.com wrote:
I know what the Remote FS root is, I am just looking for the meaning of the
acronym.
Then the label (in DumbSlave/configure-entries.jelly) ought to be
changed. Is “Remote working directory” clearer? Though this might
imply that it is the working directory of builds ($PWD / ${user.dir} /
etc.), when that is generally ${remoteFS}/workspace/${job.fullName}.
“Remote root directory”?
--
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.
AT-harness corrupted UC cache: fyi
Hi! This is just to let you know about the issue I just came across, in case you'd need to become aware of this hint: - If you get this exception when running your ATH test, (..) Failed to parse update center data of https://updates.jenkins-ci.org/update-center.json.html (..) - then you might have a corrupted cache file under that temp folder mentioned in the exception - in which case all you need to do is to (obviously now) remove that file - to force its re-creation the next time you run your test. /Marco -- 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.
Re: extension points for UI files
On Wed, May 21, 2014 at 7:48 PM, Marc MacIntyre marc...@purestorage.com wrote: I know that the config.jelly and global.jelly files will do global config for a plugin, for instance, and that a summary.jelly on a nodeProperty will display on the node's page, but I'm not sure where all of these associations are documented. Usually in the Javadoc of whatever class renders those views, or is associated with the code which renders them. I'm adding actions to the build, and would like to display a set of them on the summary page. Then you want a summary.jelly containing a t:summary or other tr. This case does not appear to be documented anywhere. I will add a note to AbstractBuild.addAction. -- 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.
Re: Jenkins Koji integration plugin - call for features
Hey Martin, have you got a chance to check my release out? https://wiki.jenkins-ci.org/display/JENKINS/Koji+Plugin It's still a prototype, and I concentrate mainly on maven builds. See my announcement from 15th May for details. If you want support for RPMs or for other platforms, feel free to file a Jira: https://issues.jenkins-ci.org/browse/JENKINS/component/18821 I am basically waiting for the community to tell me what they wish to be added. Cheers, Vaclav On 01/20/2014 10:42 AM, Martin Wilhelm wrote: Hi, this sounds very promising! Is there something to try out already? Martin Am Donnerstag, 31. Oktober 2013 15:02:41 UTC+1 schrieb Vaclav Tunka: The goal of the prepared Jenkins Koji integration plugin is to: 1) run regular CI in Jenkins 2) after several successful integration testsuite runs (unit tests) trigger the production builds in Koji 3) stage the artifacts after successful completion (ideally on some stage with API) 4) run smoke tests on the production bits from Koji in Jenkins 5a) if the smoke tests pass, promote the build to a candidate build 5b) if the smoke tests fail, repeat the process -- 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/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-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
