Re: DTKit sources location?
xUnit plugin is based on DTKit (Data Transformation Kit), an assemble of many components with a core component, a managed JUnit format component and an other generic format component. Each component has currently a separate lifecycle. GitHub is not always simple for managing this kind of assemble. And so DTKit is still managed on the SVN repository. Making multiple git repository for DTKit is too compilcated. I suggest doing the migration by - do a git repository for DTKit core - migrate all resources for JUNit in the xUnit codebase - manage other resources format outside such as in the direct dtkit-plugin. - Grégory On Sun, Jul 27, 2014 at 12:11 PM, Vincent Latombe vincent.lato...@gmail.com wrote: Hi Gregory, would that be okay for you if I initiate a migration of dtkit tree to github? I plan to split the tree in multiple git repos, to match the current releasable. Vincent 2014-07-25 14:55 GMT+02:00 'Bruno P. Kinoshita' via Jenkins Developers jenkinsci-dev@googlegroups.com: Hi Vincent, Some time ago I was investigating an xUnit issue, and also tracked down the problem to dtkit. Since I couldn't send a pull request, I gave up and someone eventually fixed it later. +1 for that Bruno -- *From:* Vincent Latombe vincent.lato...@gmail.com *To:* Jenkins Dev jenkinsci-dev@googlegroups.com *Sent:* Friday, July 25, 2014 5:14 AM *Subject:* DTKit sources location? Hi, I'm trying to solve an issue related to xUnit, apparently it is located in one of the libs used by this plugin, dtkit. Apparently this lib is still on svn https://svn.jenkins-ci.org/tags/dtkit-default-junit-parent-0.39/ but hasn't been mirrored to github as part of the global github migration. Would it be possible to mirror it to the jenkinsci org? Vincent -- 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. -- 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. -- 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: Startup Trigger Plugin
Just the time for me to develop it. Version 2.0 answers your needs. On Wed, Jan 16, 2013 at 6:37 PM, punit jain punit.jain.pu...@gmail.com wrote: Hi guys, i posted this question here also : https://wiki.jenkins-ci.org/display/JENKINS/Startup+Trigger, got some replies from Gregory Boissinot, but still have the same issue. Issue is: This plugin triggers a job at jenkins (master node) gets restarted, but i want to do trigger a job when jenkins slave gets restarted. Does anyone has any idea regarding this? -- Thanks and Regards: Punit Jain
Re: Does UrlChangeTrigger plugin works with HTTPS?
URL Change Trigger doesn't support HTTPS. You could switch to URLTrigger Plugin. On Fri, Oct 5, 2012 at 3:00 AM, kaizers kaiz...@gmail.com wrote: Hi Kohsuke, So my server is using a self signed certificate. How can I include it so the Jenkins/plugin recognizes it? Thanks! -- View this message in context: http://jenkins.361315.n4.nabble.com/Does-UrlChangeTrigger-plugin-works-with-HTTPS-tp389238p4642270.html Sent from the Jenkins dev mailing list archive at Nabble.com.
Re: AsyncFutureImpl.get problems in 1.447.2 = ArtifactDeployer
ArtifactDeployer 0,17 should fix the issue. On Fri, Jul 6, 2012 at 3:55 PM, Sandell, Robert robert.sand...@sonymobile.com wrote: We found the issue! So I thought I’d let you know. We downgraded to 1.424.2 but the issue was still there. After a good night’s sleep we started to dig some more and found this in the log: ** ** Jul 5, 2012 11:00:24 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$DeleteRemoteArtifact.onDeleted(ArtifactDeployerPublisher.java:187) at org.jenkinsci.plugins.artifactdeployer.ArtifactDeployerPublisher$DeleteRemoteArtifact.onDeleted(ArtifactDeployerPublisher.java:171) at hudson.model.listeners.RunListener.fireDeleted(RunListener.java:208) at hudson.model.Run.delete(Run.java:1187) at hudson.model.AbstractBuild.delete(AbstractBuild.java:362) at hudson.tasks.LogRotator.perform(LogRotator.java:157) at hudson.model.Job.logRotate(Job.java:315) at hudson.model.Run.run(Run.java:1440) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:175) ** ** So for some reason the ArtifactDeployer throws a NPE for most builds that gets removed, and as you can see it is when a build is finished and the log rotator is removing the last builds to fit the new one in and this exception causes the Executor not to notify the Future object that the upstream build is waiting on, and I get hundreds of angry users breathing down my neck J We removed the ArtifactDeployer and all is well. I should probably do a bug report on it. ** ** Two separate; one for core and one for ArtifactDeployer, or just one with both components in it? * * *Robert Sandell* Software Tools Engineer - Tools and Integration Sony Mobile Communications ** ** *From:* jenkinsci-dev@googlegroups.com [mailto: jenkinsci-dev@googlegroups.com] *On Behalf Of *Sandell, Robert *Sent:* den 5 juli 2012 18:33 *To:* 'jenkinsci-dev@googlegroups.com' *Subject:* AsyncFutureImpl.get problems in 1.447.2 ** ** Hi, We upgraded yesterday from 1.424.2 to 1.447.2 and the first problems has started to arrive that we had missed during testing. ** ** We use the parameterized trigger quite heavily, and the issue is that sometimes, about every eight build or so, the upstream build that is waiting for the downstream build that it triggered still waits even though the downstream build has finished long ago. A thread dump reveals that the executor is still waiting in AsyncFutureImpl.get so my guess is that for some reason the thread hasn’t been notified about the build result as it should. We also have an in-house plugin doing similar stuff and it can also hang the same way. I haven’t found anything that recreates the circumstances yet just the “sometimes it happens” thing on a couple of critical jobs. ** ** I’ve been going through the parts of core I can find that is involved in this; a git diff between Jenkins-1.424.2 and Jenkins-1.447.2 shows some changes in hudson.model.Executor that from what I can see shouldn’t affect this, nothing in WorkUnitContext, and maybe something in hudson.model.Queue (but I tend to get lost in there every time I try to understand that code J ). ** ** Does anyone have any hints on where I can continue my investigation or ways of attack to try and recreate the issue to better debug it? ** ** ** ** ** ** ** ** *Robert Sandell* Software Tools Engineer Tools and Integration Sony Mobile Communications Tel: +46 (0)10 80 12721 sonymobile.com [image: SONY make.believe] ** ** ** ** image001.jpg
Re: Plugin to trigger a single build in the future
Maybe just encapsulate your script in a job and select 'Build periodically' the right cron expression - by default, no plugins On Fri, Jun 29, 2012 at 11:02 AM, Josef jose.flore...@gmail.com wrote: Hi there, Is there a plugin that allows you to schedule a single build in the future? ie. schedule a build to run once at 5am tomorrow only. At the moment, we use Unix at command to do this but would like use Jenkins instead. I've checked the Plugins page but I can't find one. Thanks,
Re: Pre SCM poll extension
Polling is aimed at checking if the job has to be triggered. I think there is a misunderstanding. Could you explain your need? On Fri, Jun 15, 2012 at 10:32 PM, Christian Wolfgang c...@praqma.net wrote: Yes, that's before checkout, but after polling. Checkout is part of the build, the polling is not. I need something before the polling. Christian On Fri, Jun 15, 2012 at 7:58 PM, domi d...@fortysix.ch wrote: simple search… https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep /Domi On 15.06.2012, at 15:01, Christian Wolfgang wrote: Hi all. Are there any listeners/extensions before an SCM poll? Can I execute something before a poll? That is, before the job is actually a job and queued. Thanks Christian Wolfgang
Re: Expose Maven POM values to Job environment
You're right. We need to have a dedicated tool to extract variables (such as version) in Maven pom. The tool must be Maven aware (to get as you noticed Maven version in the parent pom). And the tool must be self-contained (without to require an external Maven installation). On Wed, Mar 28, 2012 at 9:58 PM, Kirill Evstigneev k.evstign...@gmail.comwrote: On Tuesday, March 27, 2012 12:59:28 AM UTC+4, gboissinot wrote: On Mon, Mar 26, 2012 at 6:18 PM, Baron wrote: - What is the best way for me to access to parsed contents of the POM? Just parse it wit a XPath expression Unfortunately it won't work in many cases. E.g. when the version number is inherited from the parent POM. Workaround is possible but it's like re-implementing Maven.
Re: Why can't the SCM checkout be a build step?
SCM changes or any other trigger (look at the XTrigger plugin: https://wiki.jenkins-ci.org/display/JENKINS/XTrigger+Plugin) is the entry point of your CI process implemented by a Jenkins job. On Tue, Mar 27, 2012 at 9:22 PM, Nicky Ramone nixe...@gmail.com wrote: Hi I'm afraid this is a newbie question, but I was wondering why can't the SCM section be defined as a step in the order that the user wants. Thanks. Regards.
Re: Environment variables on the master
Use the method AbstractBuild#getEnvironment(TaskListener log) On Mon, Mar 12, 2012 at 3:36 PM, jonjendev jonatan.ekst...@gmail.comwrote: I'm trying to find a way to extract the environment variables stored on the master; the variables set in Configure System in Manage Jenkins. Could someone point me in the right direction?
