Re: mvn release does not work, only publishes SNAPSHOT releases

gt; Has similar problem recently and your fix did help. But latest parent ( > http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/jenkins/1.33/) > still uses 2.2.2 -- is there any plan to fix that? > > > On Saturday, March 8, 2014 11:05:15 PM U

Re: Backporting for 1.554.2 started

I am strongly inclined to advocate for the inclusion of: https://github.com/jenkinsci/jenkins/commit/7c620e9fd321029e05f7cc994d3da1dde48411f7 But I also understand if this is too late in the day and we need to wait for 1.554.3... On 5 May 2014 22:13, oliver gondža wrote: > Backporting window

Re: Solidifying acceptance-test-harness API

s there is value in testing the path... but the more complex ones where the setup path is already covered... they can get value On 13 May 2014 12:21, Stephen Connolly wrote: > Well I have a scalability test framework that makes it very easy to test > jenkins at scale. I also think that the

Re: Solidifying acceptance-test-harness API

we just go ahead > and commit the required changes. Up to now it was not clear that we need to > publish a „stable“ version at all. > Are there any other plans for additional test suites that are based on the > acceptance test harness project (besides your Cloudbees test suite)? > >

Re: Solidifying acceptance-test-harness API

You know I have *very* strong feelings on a lot of the lower layers... but you also know that I haven't had the time to get the replacement layer published yet... It's coming... there is the possibility that it may break some stuff... but I am reasonably confident that it shouldn't On 12 May 2014

Re: Literate plugin: mvn hpi:run doesn't work

as soon as you have the ui-samples-plugin in your ./work/plugins you can remove it as a dependency from the pom... On 9 May 2014 16:46, Stephen Connolly wrote: > if you add the ui-samples-plugin as an optional dependency... there be > bugs with the hpi plugin from 1.509... or just upda

Re: Literate plugin: mvn hpi:run doesn't work

if you add the ui-samples-plugin as an optional dependency... there be bugs with the hpi plugin from 1.509... or just update the parent to something more recent On 9 May 2014 16:19, Christoph Kutzinski wrote: > Hi all and Stephen especially ;-), > > I wanted to give the literate-plugin a try: >

Re: Check if plugin is running on master node

Depending on where the code is running you might want to add && Jenkins.instance!=null On Saturday, 26 April 2014, Jesse Glick wrote: > builtOn == Jenkins.instance > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe fr

Re: New plugin Perforce

On Sunday, 20 April 2014, Paul Allen wrote: > Hi Guys, > > Sorry I han't been checking email over the Easter break. > > I like Kohsuke Kawaguchi's idea of running the two together, it will allow > user to try out the now plugin and provide feedback. I'm not sure how easy > it would be to provide

Re: New plugin Perforce

e the maintenance/development of > the original Perforce plugin just hangs. This plugin definitely requires a > major refactoring (the Hudson compatibility has been maintained for a long > time, so there is no support of tasty Jenkins features), so we definitely > need to sele

Re: New plugin Perforce

hope you are integrating with the credentials and the scm-api plugins On 18 April 2014 10:33, Paul Allen wrote: > Hi Rob, > > The refactoring effort would be so wide spread there would be very little, > if anything, left. > > By removing the underlying p4 command wrapper (Tek42) and replacing i

Re: (Ab)use of Groovy for test code

On 15 April 2014 16:18, Jesse Glick wrote: > @Kohsuke why do you use Groovy so much for tests? He is a Groovy fanboy... the shame! > (i.e., > src/test/groovy/) It is a PIA to edit and run tests you have written, > due to variable IDE support and the cryptic errors which gmaven-plugin > is alw

Re: Requiring Java8 for acceptance-test?

I have an env variable that should allow using a different JVM to launch Jenkins from the JVM to run the acceptance test harness... of course my refactoring will split all this out into separate modules, so the selenium stuff will be able to use Java 8 safely On 11 April 2014 16:01, Kohsuke Kawa

Re: Cannot run single cucumber test w/ acceptance-test-harness?

I am planning on reworking it so that the tests are run with surefire via a testcase runner rather than the current pile of hacks... Sadly a lot of this framework needs refactoring into a shape that makes things easier for others. Hopefully I will be able to do this without breaking anything On

Re: Stable branch rebump

On Thursday, 3 April 2014 20:59:13 UTC+1, Kohsuke Kawaguchi wrote: > > The 'stable' branch is now based on 1.554 [1]. > > I know JENKINS-22570 is only hot off the press, but from code-analysis it is very low risk and gives a major UI fix for a

Re: Classloading issues between git and git-client plugins?!

> > > > *Robert Sandell* > > *Sony Mobile Communications* > > Tel: +46 10 80 12721 > > sonymobile.com > > > > *From:* jenkinsci-dev@googlegroups.com [mailto: > jenkinsci-dev@googlegroups.com] *On Behalf Of *Stephen Connolly > *Sent:* den 7 april 2014

Re: Classloading issues between git and git-client plugins?!

I have nothing jumping to mind... this looks like something to do with remoting though... in other words the class is failing to load on the remote classloader not Jenkins core's classloader itself which probably points to Kohsuke as the best placed to comment. Robert, you could always open a s

Re: Opensourcing a plugin under a different github org

On Tuesday, 1 April 2014, Kohsuke Kawaguchi wrote: > On 03/26/2014 03:06 AM, Nigel Magnay wrote: > >> >> +1. >> I don't like the idea of having some plugins referenced under the >> official update center that don't actually come from the jenkinsci >> github organization. >> Th

Re: Backporting for 1.532.3 started

A fix for Java 8 probably really needs to go in the RC now that java 8 is out On Sunday, 23 March 2014, Stefan Wolf wrote: > Hi, > > there has still been no RC posted. Will this happen shortly? > > Regards, > Stefan > > Am Samstag, 1. März 2014 13:38:12 UTC+1 schrieb ogondza: >> >> Backporting f

[no subject]

Kohsuke, Could you please delete the following repos (all code has been pushed to the s/codahale-//g version) https://github.com/jenkinsci/codahale-metrics-plugin https://github.com/jenkinsci/codahale-metrics-graphite-plugin https://github.com/jenkinsci/codahale-metrics-ganglia-plugin https://gith

Re: New naming: Item vs. Job

As I understand it, the "New Job" link only makes sense when you are limited to top level items that are all "Job"s. Once you install a plugin like folders or the cloudbees update center plugin or the cloudbees templates plugin or other plugins that define new top level item types... well "New Job"

Re: Testing Jenkins - Ideas wanted

On Friday, 14 March 2014, Vivek Pandey wrote: > Hi Ulli, > > This sounds great. We have started on Java based LTS test harness, while > its still being developed but you can start hacking it. The workspace is > at, g...@github.com:jenkinsci/acceptance-test-harness.git. It lacks > documentation th

Re: @midnight and DST

Did I ever tell you about the bug we found when the conference call was created on the Friday the 1st of Oct for every Monday? DST bugs are fun fun fun! On 10 March 2014 16:27, Jesse Glick wrote: > Anyone in the US have a @midnight Jenkins job skipped on Sunday? > Occurred to me that this could

Re: Request: Active Directory Plugin - Merge Existing "Fix forceLdaps" Pull Request

2014 15:45, Stephen Connolly wrote: > Scott... you cheeky monkey... coming right up since I'm on CloudBees time > now! > > > On 10 March 2014 15:33, Stephen Connolly > wrote: > >> I am not assuming ownership of the plugin. I do not have the spare time >> to c

Re: Request: Active Directory Plugin - Merge Existing "Fix forceLdaps" Pull Request

Scott... you cheeky monkey... coming right up since I'm on CloudBees time now! On 10 March 2014 15:33, Stephen Connolly wrote: > I am not assuming ownership of the plugin. I do not have the spare time to > cut a release of this plugin. (If there was I have a paying customer with

Re: Request: Active Directory Plugin - Merge Existing "Fix forceLdaps" Pull Request

n Mon, Mar 10, 2014 at 9:57 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> I've merged the two open pull requests. Note: I am not assuming ownership >> of this plugin, just those changes look ok to me >> >> Kohsuke still considers the Ac

Re: Request: Active Directory Plugin - Merge Existing "Fix forceLdaps" Pull Request

I guess some of the tidy-up of LDAP that I have done is making it easier to get LDAP working... not that LDAP is necessarily the best to use... On 10 March 2014 13:57, Stephen Connolly wrote: > I've merged the two open pull requests. Note: I am not assuming ownership > of this p

Re: Request: Active Directory Plugin - Merge Existing "Fix forceLdaps" Pull Request

I've merged the two open pull requests. Note: I am not assuming ownership of this plugin, just those changes look ok to me Kohsuke still considers the Active Directory plugin to be preferred to using the LDAP plugin... so I wouldn't say it is abandoned... more the COM4j leak causes lots of people

Re: mvn release does not work, only publishes SNAPSHOT releases

does only work if the plugin is top-level. I'm > releasing in a sub-folder. > > Am 08.03.2014 um 12:36 schrieb Stephen Connolly < > stephen.alan.conno...@gmail.com > >: > > What version of git are you using? > > Anything after 1.8.4 needs m-r-p 2.5 or the depe

Re: mvn release does not work, only publishes SNAPSHOT releases

t; 1.9 > > > > > was enough to work with latest git (1.8.5.2). > > HTH, > > Vincent > > > 2014/1/13 Dominik Bartholdi > > ;-) > > I'll try to take a look at the m-r-p, but I currently can't promise any > time - sorry :( >

Re: Attempting Java port of selenium tests

On Friday, 28 February 2014, Kohsuke Kawaguchi wrote: > Stephen made a point to me in a dev meet-up at FOSDEM that he likes > Cucumber in that tests are more readable (even to developers), even though > he was sympathetic to the overhead for authors of tests. > > > So I think I am going to leave

Re: Writing tests which use credentials?

On Saturday, 1 March 2014, Mark Waite wrote: > I'd like to write several tests for the git-client-plugin which use > credentials, since there are many ways that the git-client-plugin may fail > in the context of using credentials. The failure modes tend to be platform > dependent, and installati

Re: 1.532.2 RC posted

But isn't 1.532 after the 1.6 only switch? On Thursday, 20 February 2014, Jesse Glick wrote: > Just realized that 1.532.2 will not run on Java 5, since to pick up > some fixes it bundles a newish Stapler release, which has since been > switched to compile on Java 6. > > (The Jenkins core POMs ve

Re: Announcing copyartifact-git-plugin

& B installed the connector functionality works. But better is to keep A & B with no knowledge of each other and then have C (with a hard dependency on both) provide the interconnect functionality... of course how do you know to install C in the first place? On 20 February 2014 15:35, Step

Re: Announcing copyartifact-git-plugin

They are certainly an issue when it comes to plugin upgrades and compat testing On 20 February 2014 14:44, Jesse Glick wrote: > On Wed, Feb 19, 2014 at 8:07 PM, Patrick Higgins > wrote: > > write a plugin that has > > optional dependencies on several SCM plugins and provides the branch > > inf

Re: [ANN] Subversion Plugin 2.0 being released

lean checkouts to a Linux slave work fine. > > > > I guess Stephen does not want to know ;-) I can raise a JIRA. > > > > Best regards > > > > David > > > > *From:* jenkinsci-us...@googlegroups.com [mailto: > jenkinsci-us...@googlegroups.com] *On Behalf

Re: [ANN] Subversion Plugin 2.0 being released

The only change is the integration of the credentials plugin. Everything else remains the same. There has been zero feedback on the experimental releases. The kind of feedback needed is from real users and real systems. The considered opinion of the three non-CB people and the feedback from NdL wa

Re: [ANN] Subversion Plugin 2.0 being released

Go for it On Saturday, February 1, 2014, jieryn wrote: > Is the wiki going to be updated with the changes? > > On Fri, Jan 31, 2014 at 7:25 AM, Stephen Connolly > > wrote: > > all voted me down and suggest that we just go and release the 2.0 > version. > > -- >

[ANN] Subversion Plugin 2.0 being released

At the Jenkins Code Camp the issue of releasing version 2.0 of the Subversion plugin came up. I would have liked to hear from some users who have tried to test the 2.0-beta-1. After 3 months we have had no feedback, so: Kevin P Flemming Robert Sandell Nicolas de Loof Vincent Latombe all voted me

Re: Backports for 1.532.2

After some issues we have found with the credentials plugin < 1.9.4 and Jenkins 1.532.1, I am now recommending that we bump the plugin to 1.9.4 for the 1.532.2 release. https://github.com/jenkinsci/jenkins/pull/1104 This is low risk as the 1.9.4 release has been available for over two months now.

Re: Issues.jenkins-ci.org email notifications

He did, but sadly the email update was lost because the queue was not persisted to disk and they had to restart their JIRA because emails were getting stuck... maybe we should get them to file a JIRA On 26 January 2014 17:58, Slide wrote: > File a JIRA against JIRA...Inception JIRA. > On Jan 26

Re: Fixed time schedule for LTS releases

My understanding is that the community is only supporting two versions: * OSS HEAD (i.e. today that is 1.548) * OSS LTS (i.e. today that is 1.532.1) There are no community backports to older LTS lines. If you want support for the older LTS lines then you need to engage with a commercial org that

Re: Where are Jenkins users?

20, 2014 6:30:42 PM UTC+1, Stephen Connolly wrote: >> >> No direct flights from dublin :-( >> >> >> On 20 January 2014 17:17, Dominik Bartholdi wrote: >> >>> Yeah, Cologne is also good from switzerland :) >>> Domi >>> >>>

Re: Where are Jenkins users?

No direct flights from dublin :-( On 20 January 2014 17:17, Dominik Bartholdi wrote: > Yeah, Cologne is also good from switzerland :) > Domi > > On 19.01.2014, at 23:42, FredG wrote: > > Hi Alyssa, > > I'd recommend Cologne. Not just because I live there. ;) > It can be reached easily from mos

Re: Adventurous users wanted! Literate multi-branch project type

I see them in http://updates.jenkins-ci.org/experimental/ so not sure what you are getting at... On 14 January 2014 16:36, sandersw wrote: > Am I right that the plugins are no longer present in the experimental > update > centre? > > If so, then does that mean I need to build them from source?

Re: JIRA "current" version option

which is why my primary suggestion is to have the update center metadata generator create the version labels while it's doing its stuff... covers the 99% use case... only have hpi plugin goals and/or and IRC bot for those cases where you want to create the version number up front... though the is

Re: JIRA "current" version option

t; Mirko > -- > Sent from my mobile > On Jan 13, 2014 12:32 AM, "Stephen Connolly" < > stephen.alan.conno...@gmail.com> wrote: > >> What you mean is a REST service that uses your deployment credentials to >> create/mark released versions... And then add a go

Re: mvn release does not work, only publishes SNAPSHOT releases

On Sunday, 12 January 2014, Dominik Bartholdi wrote: > The maven team > Nice dodge of self promotion there ;-) Btw do you want to take a run at m-r-p? > has just release a git provider based on jgit, if you configure the > release plugin to use this one, then you don’t have to downgrade git.

Re: JIRA "current" version option

h should be a mandatory field then), these versions need to > have a status „Released" > b) IRC bot commands to create a new version for a developer to plan the > next release (status is ‚Unreleased‘), and another command to release that > version > > Am 12.01.2014 um 2

Re: JIRA "current" version option

Far far simpler... we just index the poms in the repo and create versions every time the index runs... That way there is a version for every release, since people want to report issues against released versions... if you are cutting a release with new known issues you can wait the 24hr anyway... o

Re: Problem running tests when building maven-plugin

On Tuesday, 7 January 2014, Jesse Glick wrote: > On Tue, Jan 7, 2014 at 3:17 PM, James Wilson > > > wrote: > > Is there a document or posting somewhere indicating what the maven-plugin > > maintainers use for a successful build? Version of maven, MAVEN_OPTS > > settings, etc. > > All tests pass f

Re: Plugin parent version

n and you'll get good API coverage If you are happy appealing to only ~65% (my guess from the feel of the graph, but do a real calculation if you are using this) of Jenkins installations you could be aggressive and pick 1.532 On 7 January 2014 10:24, Stephen Connolly wrote: > I will

Re: Plugin parent version

I will probably bump credentials up past 1.424 in the near future... I have yet to decide on the minimum version to bump to... I think it will have to be post 1.480 though as there are some UI glitches that are only fixable in newer Jenkins versions... and it is those UI glitches that will drive th

Re: Beta release of Gerrit Trigger plugin 2.11.0

> > I’m assuming that Stephen will correct me very shortly on this – or weigh > in with some more information J > > > > /James > > > > *From:* jenkinsci-dev@googlegroups.com [mailto: > jenkinsci-dev@googlegroups.com] *On Behalf Of *Stephen Connolly > *Sent:* 1

Re: Beta release of Gerrit Trigger plugin 2.11.0

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

Re: credentials extension

Damn reply to vs reply to all On Saturday, 7 December 2013, Stephen Connolly wrote: > I also have a fair chunk of an oauth impl for the credentials stuff... But > I hit some issues with oauth 1 vs oauth 2 in respect of producing a > consolidated api. > > At a minimum I think oa

Re: Fix needed for jenkins-ci.org: current LTS version listed as 1.509.4

; Given the openness of the community I find it a little strange that only > one person seems to be able to release things? Are there plans for what > would happen in an extended absence of KK? > > Richard. > (Just curious - not trying to create a big fuss :) ) > > &g

Re: Fix needed for jenkins-ci.org: current LTS version listed as 1.509.4

1.532.1 is ready... we are just driving KK like mad doing stuff in CloudBees and he hasn;t had time to push the changes to the website On 4 December 2013 17:25, Leandro Lucarella wrote: > On Saturday, November 30, 2013 10:20:39 AM UTC+1, David Resnick wrote: >> >> The LTS changelog shows 1.532.

Re: Process to move from a new release of Jenkins(1.529) to LTS 1.509

I am 99.999% certain you are hitting JENKINS-18836, JENKINS-18879, JENKINS-19619. The root cause was fixed in 1.536 and was backported to the latest LTS release 1.532.1 I would recommend using the latest LTS, i.e. 1.532.1 and not the 1.509 line On 3 December 2013 13:19, Kishore RP wrote: > Si

Re: Version non stable

The LTS line is the stable line... 1.540 is a bleeding edge release... use at your own risk On 19 November 2013 17:12, MohamedAMINE OSMAN wrote: > bonjour, > je viens de déployé la version 1.540 qui n'est pas fonctionnel. > j’étais obligé de déployer la version antérieure 1.539 > merci > > -- >

Re: Commit loss prevention

I am less keen on Gerrit. If anything this recent experience has me feeling that I don;t want Gerrit anywhere near my workflow On 12 November 2013 15:43, Kevin Fleming (BLOOMBERG/ 731 LEXIN) < kpflem...@bloomberg.net> wrote: > Well, that would mean that merging a pull request on GitHub (especial

Re: Commit loss prevention

On 12 November 2013 14:40, Kevin Fleming (BLOOMBERG/ 731 LEXIN) < kpflem...@bloomberg.net> wrote: > When you say 'canonical' in this proposal, do you mean the repositories > used for making releases > I mean that they are the "official" repositories and all others are just mirrors... this is the

Re: Commit loss prevention

I think part of the issue is that our canonical repositories are on github... I would favour jenkins-ci.org being masters of its own destiny... hence I would recommend hosting canonical repos on project owned hardware and using GIT as a mirror of those canonical repositories... much like the way A

Re: AW - *PLEASE READ* Re: strange pushes on GitHub

I had pushed releases of credentials, ssh-credentials, ssh-agent and ec2 on Friday, so I just re-pushed them. I don't think anyone made changes to scm-api or branch-api since my last push, so I pushed those from my local also On 11 November 2013 09:05, nicolas de loof wrote: > git fetch + git p

Re: Backporting for 1.532.1 started

Thanks On 6 November 2013 12:03, ogondza wrote: > JENKINS-19739 backported > -- > oliver > >> -- > 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 jenk

Re: Backporting for 1.532.1 started

Oliver, I would strongly advise including 19739 as it would have helped prevent a lot of the plugin upgrade issues we saw when moving to ssh-slaves 1.0. If you need help backporting it I will be only to happy to help, but I do think it is very necessary to protect users -Stephen On 6 November 2

Re: New Plugin - ScriptCS

yeah, you'd need ikvm or such to attempt that ;-) On 5 November 2013 15:08, Slide wrote: > What I meant was, if the scripts that the plugin runs were able to import > the Jenkins object model and call methods and so forth, but I don't think > that is the point of the plugin based on further ana

Re: New Plugin - Reports

Sounds like a view rather than needing a root action On 5 November 2013 10:14, mr.kenneth.graham wrote: > It is not an exception in my code. It is the message " is > missing the Overall/Administer permission". > > The "Reports" produced is a single page for managing the complexity of > an Jenki

Re: Identify Jenkins Build Number

Because KK doesn't trust the code signing keys outside of his personal hardware. I think he may run Jenkins on his personal hardware to actually cut the release, but it is not a public accessible Jenkins. On Friday, 1 November 2013, Hyunil Shin wrote: > Thank you~ > > Manual build!!! > It's a lit

Re: How do I keep cloudbees from building the gh-pages branch

On Thursday, 31 October 2013, Jesse Glick wrote: > On Thu, Oct 31, 2013 at 6:47 AM, Hakan Tandoğan > > wrote: > > Is there a way to tell cloudbees that certain branches should not be > built? > > Now is the time for @stephenc to jump in with an exhortation to use > literate multibranch builds… I

Re: Identify Jenkins Build Number

533 On 31 October 2013 09:33, Hyunil Shin wrote: > Hello > > It's very simple question. > > How can I identify the build number (in Jenkins ci) which is used to > generate jenkins.war? > For example, what is build number of jenkins.war-1.533? > > Thank you~ > > -- > You received this message be

Re: Keeping configs after package change

I hope you are not using the org.jenkinsci.plugins package name bare without any plugin prefix... e.g. org.jenkinsci.plugins.somename is ok, but org.jenkins.plugins is not as you could hit the package must be from same jar style classloader conflicts if you haven't given yourself a unique namespac

Re: Lift Java6 API restrictions from core

Stop using the crappy maven project type and help me implement a real maven project type ;-) On Sunday, 27 October 2013, Domi wrote: > +1 > Just a thought: is there anything we could do to make this more easy in > the future, > ? like Jesse's comment on > https://issues.jenkins-ci.org/browse/JENK

Re: Jenkins JIRA

Go for it! On 25 October 2013 06:33, Owen Mehegan wrote: > I mentioned this issue to Kohsuke in IRC recently. One of the ways I've > tried to contribute to Jenkins has been by filing good bugs and following > up on them. Sometimes it takes some legwork to find the right person to > assign them

[ANN] CloudBees open sources (most) of our support plugin

Since Jesse has no time to read the user's list (but apparently has enough time to spam my tickets on ZenDesk) ;-) -- Forwarded message -- From: Stephen Connolly Date: 24 October 2013 14:37 Subject: [ANN] CloudBees open sources (most) of our support plugin To: "je

Re: Jenkins Plugin (Stephen Connolly) tutorial still valid?

when I finally get around to implementing the coverage plugin, I will probably see about rewriting my tutorial ;-) TL;DR don't hold your breath On 24 October 2013 14:46, Jesse Glick wrote: > On Thu, Oct 24, 2013 at 9:01 AM, Kaj Kandler > wrote: > > In part 2 he starts to unify plugins for Mav

Subversion 2.0-beta-1 (Testers NEEDED)

This now has the credentials migration as good as I think I can make it. You are advised to backup $JENKINS_HOME/config.xml (should not be necessary, but just in case) $JENKINS_HOME/credentials.xml $JENKINS_HOME/hudson.scm.SubversionSCM.xml $JENKINS_HOME/jobs/**/config.xml $JENKINS_HOME/jobs/**/s

Re: Jenkins JIRA

JENKINS-455 fixed! On 22 October 2013 13:25, Andrew Gray wrote: > Thanks you Stephen > > > On 22 October 2013 23:10, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> Mwah ha ha... I decided to spend 45min closing some old issues... >> &

Can somebody remove the jenkinsci/console-tail repository... i created it by mistake

console-tail-plugin is the one we want to keep -- 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

Re: Jenkins JIRA

Mwah ha ha... I decided to spend 45min closing some old issues... On 22 October 2013 13:08, Jesse Glick wrote: > On Tue, Oct 22, 2013 at 6:53 AM, Andrew Gray > wrote: > > eliminate all the non-reproducible issues > > Unfortunately this would be most of the issues that get filed, even > those w

Re: Get the value of a project configuration value from a project instance

On Monday, 21 October 2013, Jesse Glick wrote: > On Mon, Oct 21, 2013 at 1:25 PM, Ronni Elken Lindsgaard > > wrote: > > Is it safe to typecast an AbstractProject to Project? > > Well, it is safe to check if the project is a Project. But it > certainly may not be, for example if it was a Maven modu

Re: Beware depending on Jenkins 1.509.4

Exactly, ranges are evil for release builds On Monday, 21 October 2013, Jesse Glick wrote: > On Mon, Oct 21, 2013 at 12:45 PM, Vincent Latombe > > wrote: > > Probably caused by http://jira.codehaus.org/browse/MNG-3092 > > which makes snapshot versions selected as part of version ranges. > > Right

Re: Jenkins checkUrl help!

if you set field you don;t need to set name On 21 October 2013 10:32, Iordan Boev wrote: > I also normally use the auto-bind but I had just the 'name' attribute set, > as soon as I aded the 'field' attribute it worked! Thanks a lot for the > hint, saved my day! > > Am Donnerstag, 17. Oktober 20

Re: Re: Beware depending on Jenkins 1.509.4

> http://illegalstateexception.blogspot.com/ > https://github.com/mfriedenhagen/ > https://bitbucket.org/mfriedenhagen/ > > > On Mon, Oct 21, 2013 at 10:12 AM, Stephen Connolly > wrote: > > There are two transitive -SNAPSHOT dependencies that have leaked into the > >

Re: Beware depending on Jenkins 1.509.4

irko > Regards Mirko > -- > http://illegalstateexception.blogspot.com/ > https://github.com/mfriedenhagen/ > https://bitbucket.org/mfriedenhagen/ > > > On Mon, Oct 21, 2013 at 10:12 AM, Stephen Connolly > wrote: > > There are two transitive -SNAPSHOT depe

Beware depending on Jenkins 1.509.4

There are two transitive -SNAPSHOT dependencies that have leaked into the 1.509.4 pom [DEBUG]org.jenkins-ci.main:jenkins-core:jar:1.509.4:provided [DEBUG] org.jenkins-ci.main:cli:jar:1.509.4:provided [DEBUG] org.jenkins-ci:version-number:jar:1.1:provided [DEBUG] org.jenkins-c

Re: Contributed localization drop

On 20 October 2013 22:45, Christoph Kutzinski wrote: > Thanks for doing this Kohsuke! > > However, after looking at the German translation updates ( > https://github.com/jenkinsci/**jenkins/commit/** > 95f1d4b60d11fb0b68230690af7083**10de3cf07a

Re: Next LTS: 1.532.1

I know the issues I have listed are not "strictly" meeting the LTS criteria yet, but there are IMHO very valid reasons for including them anyway. On 18 October 2013 16:33, Stephen Connolly wrote: > critical: (as this is badly broken) > https://issues.jenkins-ci.org/browse/JENKI

Re: Next LTS: 1.532.1

critical: (as this is badly broken) https://issues.jenkins-ci.org/browse/JENKINS-18836 https://issues.jenkins-ci.org/browse/JENKINS-18879 https://issues.jenkins-ci.org/browse/JENKINS-19619 really nice to have: (as it will make like much less error prone when upgrading plugins) https://issues.jenki

Re: Jenkins checkUrl help!

On Thursday, 17 October 2013, Iordan Boev wrote: > Hi people, > > I have a class extending jenkins.model.GlobalConfiguration and a > repeatable property in my config.jelly file. There are some textfields I > want to validate using the checkUrl property of a textfield. > What I tried is this: > > >

Re: literate-api brings in its own version of Guava

Well literate-api wasn't even using guava... It was a left over dependency from some experiments... I agree that we need a better story but it might be a story than needs Jenkins 2.0 to enact On Thursday, 17 October 2013, Jesse Glick wrote: > On Wed, Oct 16, 2013 at 8:06 PM, Stephen

Re: literate-api brings in its own version of Guava

good catch... you know how I hate guava's asm-like treatment of api compat... I will sort it out tomorrow On 17 October 2013 00:43, Kohsuke Kawaguchi wrote: > Mostly to Stephen, > > I noticed that this library depends on a version of Guava, but when you > run inside Jenkins you end up loading G

Re: Open-source folders plugin

Ahem... this is just an "unofficial" announcement... it will be "officially" announced at JUC... :rolleyes: (In Ireland, there is a special pronunciation of the word 'marketing' that you use when you face craziness like the above: 'morketing' cf http://en.wikipedia.org/wiki/Ross_O'Carroll-Kelly)

Re: Backporting 1.509.4 complete

On 10 October 2013 16:08, Jesse Glick wrote: > On Thu, Oct 10, 2013 at 1:13 AM, Marnix Klooster > wrote: > > I'm assuming this is a Changelog oversight > > Probably. The changelog is generated by some script which in every LTS > release I have seen produces quite inaccurate results and should no

Re: Git plugin 2.0 release?

> 2013/10/9 Stephen Connolly > >> will they be stored in the git remote config in .git/config? >> >> >> On 9 October 2013 13:22, nicolas de loof wrote: >> >>> credentials won't appear on console log >>> >>> >>> 2013/

Re: Git plugin 2.0 release?

will they be stored in the git remote config in .git/config? On 9 October 2013 13:22, nicolas de loof wrote: > credentials won't appear on console log > > > 2013/10/9 Stephen Connolly > >> exactly, in any case the git plugin should be providing a warning to th

Re: Git plugin 2.0 release?

loof : > > I investigating another solution : > add the username:password dynamically to URL as git commands are executed > by git-client. > > This would be transparent for git-plugin > > > 2013/10/9 Stephen Connolly > >> can we add a method to git-client that lets us

Next LTS and JENKINS-18879

https://issues.jenkins-ci.org/browse/JENKINS-18879 I found and fixed a very critical issue in our build of the Trilead SSH library. The fix is rather trivial, but I think it would be very good if this was in the next LTS line. It is not an issue for the 1.509.x line as that is currently using tri

Re: Experimental update site

To: jenkinsci-dev@googlegroups.com > > Subject: Re: Experimental update site > > > > On 10/08/2013 01:39 PM, Stephen Connolly wrote: > > > Pity you implemented them as either or... I did the CloudBees one as > > a > > > layer, ie it just lists the alpha/beta p

Re: Git plugin 2.0 release?

> implement it, but some hack to force a gitcredentials property ... >>> >>> >>> 2013/10/8 Stephen Connolly >>> >>>> My only concern is GIT cli with user/pass credentials (I think we are >>>> doing ssh-agent for key based so that shou

<    1   2   3   4   5   6   7   8   >