Re: Why is GIT_BRANCH set twice in GitSCM.checkout

I would set it in both places, and write tests to confirm it behaves as expected. Mark Waite On Monday, February 22, 2016 at 2:43:17 PM UTC-7, Michael Giroux wrote: > > I'm looking to add a new environment variable to expose the LocalBranch > name as GIT_LOCAL_BRANCH. I'm looking at the code

Re: IntelliJ licenses

Maybe ask JetBrains directly, it's their license terms. On 23.02.2016, at 00:07, Kanstantsin Shautsou wrote: > Terms are not clear: are they about of sharing license of matched people or > about using for matched people? > > On Tuesday, February 23, 2016 at 1:02:42

Re: Commit access - Job import plugin

Sure I am trying ping the recent maintainers. You linked to a pull request for the harvest plugin - but not for the job import plugin. Did you just want to release what is already merged there? On Friday, February 19, 2016 at 5:26:45 PM UTC+11, Adam E wrote: > > Hi Michael, i already have

Re: maven plugin release

3 months later, Should we need to consider to add the plugin in the list of plugins to be adopted ? cheers On Wed, Dec 2, 2015 at 2:06 PM, Oleg Nenashev wrote: > I can press the release button in the CI instance. > BTW it would be grateful if somebody reviews PRs and

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

In general, wait at least 8 to 12 hours before worrying. Cheers 2016-02-22 20:45 GMT+01:00 : > Hi , > It's still unpublished in > http://ftp-chi.osuosl.org/pub/jenkins/updates/current/update-center.json for > version 1.7 > and in Jenkins update center > > Am I

Re: IntelliJ licenses

Terms are not clear: are they about of sharing license of matched people or about using for matched people? On Tuesday, February 23, 2016 at 1:02:42 AM UTC+3, Daniel Beck wrote: > > Hi everyone, > > JetBrains recently changed the rules on open-source licenses, and KK is no > longer eligible to

Re: [Google Summer of Code 2016] - We're looking for mentors

Hi Oleg, Since I'm contributing to Jenkins plugins I always found it hard to reproduce issues because of the complexity of interaction between Jenkins and its plugins. It's often when you have a problem that you think that it comes from plugin and you finish by fixing another one

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

Looks like we're having an issue with our infra, likely caused by the maintenance this weekend. https://ci.jenkins-ci.org/job/Update%20Center/job/infra_update_center_mirror/ I'll poke Tyler about it, unfortunately he's at a conference today. On 22.02.2016, at 22:45, Radek Antoniuk

IntelliJ licenses

Hi everyone, JetBrains recently changed the rules on open-source licenses, and KK is no longer eligible to manage them. https://www.jetbrains.com/buy/opensource/?product=idea Ideally, someone else who qualifies would handle the IntelliJ IDEA licenses for the software project. Any volunteers?

Re: Why is GIT_BRANCH set twice in GitSCM.checkout

I added a few log messages to track the progress of a build and discovered that buildEnvVars is called several times. I doubt this hurts anything, but it seems this could be optimized some. Feb 22, 2016 2:56:26 PM hudson.plugins.git.GitSCM buildEnvVars INFO: ENTER Feb 22, 2016 2:56:26 PM

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

Actually I think something's wrong. I have the same issue with jira-plugin that was released over 24h ago. v.2.2 is visible in both places: http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/jira/ http://updates.jenkins-ci.org/download/plugins/jira/ but still not visible in Update Center

Why is GIT_BRANCH set twice in GitSCM.checkout

I'm looking to add a new environment variable to expose the LocalBranch name as GIT_LOCAL_BRANCH. I'm looking at the code in GitSCM.checkout and am not able to figure out why GIT_BRANCH is being set twice. GIT_BRANCH is set first when checkout sets environment: EnvVars environment =

Re: [ANN] Openstack plugin 2.0 Beta is out

Version 2.0 is out[1], it should be available in update centers shortly. [1] http://maven.jenkins-ci.org:8081/content/repositories/releases/org/jenkins-ci/plugins/openstack-cloud/2.0/ -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers"

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

Hi , It's still unpublished in http://ftp-chi.osuosl.org/pub/jenkins/updates/current/update-center.json for version 1.7 and in Jenkins update center Am I doing something wrong? Thanks again. On Monday, February 22, 2016 at 5:18:20 PM UTC+2, Daniel Beck wrote: > > > On 22.02.2016, at 16:02,

Re: LTS status

My testing of the LTS found no surprises with the git plugin. On Mon, Feb 22, 2016 at 11:51 AM ogondza wrote: > I went through my regular routine and all looks good. Nobody else reported > anything so I guess that is a green light for you. > > -- > oliver > > -- > You

Re: LTS status

I went through my regular routine and all looks good. Nobody else reported anything so I guess that is a green light for you. -- oliver -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving

Re: Problem releasing new plugin‏

Yes, but I have a different error, see below. [ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare (default-cli) on project loadfocus-loadtest: Unable to tag SCM On Sunday, February 21, 2016 at 3:11:07 AM UTC, Daniel Beck wrote: > > Have you read and

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

On 22.02.2016, at 16:02, anna.ro...@whitesourcesoftware.com wrote: > So i still need to wait for a while? > Yes. -- 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

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

Hi Daniel, Thanks for the quick answer. According to your link Now I can see my plugin in these two links but not in the update center 1. http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/whitesource/1.7/ 2.https://updates.jenkins-ci.org/download/plugins/whitesource/ So i still need to

LTS status

Oliver, Did LTS testing (second RC) reveal any issues, or are we good to go? Daniel -- 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

Re: Publishing new version of White Source Jenkins plugin in Jenkins update center

See: https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-Help\!Mypluginisnotshowingupintheupdatecenter > This file is updated every 4 hours (plus mirror propagation time), so there's > some delay before your new version appears here. Daniel On 22.02.2016, at 15:27,

Publishing new version of White Source Jenkins plugin in Jenkins update center

Hi, I've made a successful push request and a build in Jenkins for my Jenkins Plugin( https://github.com/jenkinsci/whitesource-plugin*) - *about 5 hours ago*.* I can't see the new version of the plugin in Jenkins update center, how long it should take? Thanks, Anna -- You received this

Rebuild bug with jenkins dynamic choice parameter

Hi *Jenkins team and users*, This is wrt Jenkins bug JENKINS-32833- I used Jenkins dynamic choice parameter scriptler to get dynamic drop down list on the basis of a script output. When I attempt to rebuild the job using dynamic choice parameter, it does fetch the right parameters