Jenkins Git Plugin and Maven Release Builds

Using Jenkins 1.609.3, Git plugin 2.4.0. We have configured most of our jobs to allow jobs to be initiated by the Stash Webhook to Jenkins. To allow developers to manually initiate a build of any branch, the jobs use the Git Parameter to set a BRANCH variable. Using this configuration, the Git

Re: Jenkins Git Plugin and Maven Release Builds

ference notation. Perhaps this is the solution. Extend the "checkout to local branch" to provide full bash resolution of the variable name. On Tuesday, December 29, 2015 at 10:03:25 AM UTC-7, Michael Giroux wrote: > > Using Jenkins 1.609.3, Git plugin 2.4.0. > > We have

Re: Jenkins Git Plugin and Maven Release Builds

it-plugin/pull/304 for two different > possibilities. > > Mark Waite > > On Tue, Dec 29, 2015 at 8:36 PM Michael Giroux > wrote: > >> Yes. >> >> The issue I'm describing is a result of using the Git Parameter plugin >> which allows the user to select a branch

Re: Jenkins Git Plugin and Maven Release Builds

hat might meet your need. I suspect that one > or the other will eventually be merged, but not both. > > Mark Waite > > On Wed, Dec 30, 2015 at 7:21 AM Michael Giroux > wrote: > >> Mark, I'm taking a look at the two pull requests. I cloned the repo so I >&g

Re: Jenkins Git Plugin and Maven Release Builds

quot;;); p.setScm(scm); -configRoundtrip(p); +configRoundtrip((Item)p); assertEqualDataBoundBeans(scm,p.getScm()); } On Wednesday, December 30, 2015 at 10:29:37 AM UTC-7, Michael Giroux wrote: > > Not making any changes to code, just trying to examine pri

Re: Jenkins Git Plugin and Maven Release Builds

ans as well. I don't use Eclipse, so I'm > not much help wiht Eclipse specific failures. > > Mark Waite > > On Wed, Dec 30, 2015 at 8:31 AM Michael Giroux > wrote: > >> BTW, the following patch resolves my compile errors, but not sure if the >> cast to (I

Re: Jenkins Git Plugin and Maven Release Builds

Parameter plugin developers to strip the leading "origin/" from the branch names that are assigned to the parameter? Michael On Wednesday, December 30, 2015 at 11:22:33 AM UTC-7, Michael Giroux wrote: > > Thanks Mark. Command line build runs fine w/o compile errors. For your

Re: Jenkins Git Plugin and Maven Release Builds

though the git parameter plugin is technically > correct. It is showing the branch to be built, and the branch to be built > truly is "origin/master", since there is no local master branch tracking > the remote branch. > > Mark Waite > > On Wed, Dec 30, 2015 at 11:41 A

Re: Jenkins Git Plugin and Maven Release Builds

lready handle your case. > > Mark Waite > > On Thu, Dec 31, 2015 at 6:07 AM Michael Giroux > wrote: > >> Accepting that the Git Parameter plugin is technically correct, lets get >> back to the maven release build issue. >> 1. to do a maven release, we MUST confi

Re: Jenkins Git Plugin and Maven Release Builds

wse/JENKINS-25465 for > a discussion of the fullName=false parameter to GIT_BRANCH, in case that > will already handle your case. > > Mark Waite > > On Thu, Dec 31, 2015 at 6:07 AM Michael Giroux > wrote: > >> Accepting that the Git Parameter plugin is technically correc

Re: Jenkins Git Plugin and Maven Release Builds

esday, January 5, 2016 at 12:59:55 PM UTC-7, Mark Waite wrote: > > That is am interesting idea. Giving a semantic meaning to am empty field > should not alert behavior for non-empty fields. Will you be coding it? > > Mark Waite > > On Tue, Jan 5, 2016, 11:47 AM Michael

Re: Jenkins Git Plugin and Maven Release Builds

e, Jan 5, 2016, 11:47 AM Michael Giroux > wrote: > >> Mark, >> >> I think there may be a simple solution that can be implemented in the Git >> plugin. If the job is configured with additional behavior "checkout to >> local branch" AND the local branch

Re: Jenkins Git Plugin and Maven Release Builds

a semantic meaning to am empty field > should not alert behavior for non-empty fields. Will you be coding it? > > Mark Waite > > On Tue, Jan 5, 2016, 11:47 AM Michael Giroux > wrote: > >> Mark, >> >> I think there may be a simple solution that can be

Re: Jenkins Git Plugin and Maven Release Builds

t;> >> >> On Tuesday, January 5, 2016 at 12:59:55 PM UTC-7, Mark Waite wrote: >> >>> That is am interesting idea. Giving a semantic meaning to am empty >>> field should not alert behavior for non-empty fields. Will you be coding >>> it? >>&g

Re: Jenkins Git Plugin and Maven Release Builds

f development and test environments, so there may be something > specific to the Mac. > > Mark Waite > > On Tue, Jan 5, 2016 at 4:29 PM Michael Giroux > wrote: > >> Attaching build.log for complete build result. shows maven version and >> java versions at head of

Re: Jenkins Git Plugin and Maven Release Builds

t;>>> client plugin are able to clone repositories, but I can't compile and test >>>> successfully on FreeBSD with either OpenJDK 7 or OpenJDK 8. >>>> >>>> I think the problem you're seeing is either platform specific (like my >>>>

Re: Jenkins Git Plugin and Maven Release Builds

n the future. On Wednesday, January 6, 2016 at 1:29:13 PM UTC-7, Michael Giroux wrote: > > Really appreciate the suggestions. > > To eliminate eclipse, I cloned https://github.com/jenkinsci/git-plugin.git > to a new directory and built with maven. Same issue. Wonder if thi

git-plugin test cases running 5+ minutes

I'm attempting to build git-plugin and find that the test cases are taking a very long time. Several of the tests are running 270+ seconds. Tests run: 20, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 270.683 sec - in hudson.plugins.git.CliGitSCMTriggerRemotePollTest Tests run: 20, Failure

Re: Jenkins Git Plugin and Maven Release Builds

for non-empty fields. Will you be coding it? > > Mark Waite > > On Tue, Jan 5, 2016, 11:47 AM Michael Giroux > wrote: > >> Mark, >> >> I think there may be a simple solution that can be implemented in the Git >> plugin. If the job is configured with addition

Re: Running a Jenkins job from a shell script

If you are referring to the authtoken from build triggers, you could retrieve it using the jenkins cli to retrieve the config.xml for the job and extract the authToken element. (System) xxxyyy false On Tuesday, March 1, 2016 at 7:13:38 PM UTC-7, Alan Evangelista wrote: > > I do not

Re: Same Build number series for multiple projects

If you want to share a single build number over all branch builds, you will want to configure your job to accept a branch name to be built. Then run as a parameterized build and specify the branch to build. This will give you build numbers like this: master: 1 master: 2 branch-a: 3 branch-b:

Re: Same Build number series for multiple projects

> > On Wednesday, March 2, 2016 at 9:03:07 AM UTC+5:30, Michael Giroux wrote: >> >> If you want to share a single build number over all branch builds, you >> will want to configure your job to accept a branch name to be built. Then >> run as a parameterized build a

Enhancing LocalBranch to support maven release builds

I posted this topic to the Jenkins Developers group (https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!searchin/jenkinsci-dev/enhance/jenkinsci-dev/xuweZbwn9zE/6TqSO3r5EQAJ). There are a few questions in this group, and on Stack Overflow about the fact that local branch names

Git Plugin GIT_LOCAL_BRANCH environment variable implemented

There have been a couple of requests for an environment variable that publishes the local branch name. The current version of the Git Plugin has a new feature that targets Maven release builds, but can be leveraged by other builds. The maven release plugin pushes a commit to git using the loca

Re: One CI job for 4 branches

If you have created a post-update hook on the remote repository to notify Jenkins when a push occurs, you might consider configuration as: Branch to build: ** Checkout to specific local branch: ** (requires Git plugin 2.4.4) Build Triggers: Poll SCM but leave the schedule blank. The job will o

Git Polling initiated by notifyCommit failing on remote since version 2.4.4

Since updating to Git plugin version 2.4.4, our jobs that execute on a remote slave are failing. The full stack trace from the polling log is below. Do we need to install additional software on the slaves to accommodate the update? Michael Giroux Polling for changes in ERROR: Failed to

Re: Git Polling initiated by notifyCommit failing on remote since version 2.4.4

Seems another user has similar issue. https://issues.jenkins-ci.org/browse/JENKINS-33907 That is not exactly the same, but I've seen the same issue, and it could be related to my issue. On Tuesday, March 29, 2016 at 11:44:15 AM UTC-7, Michael Giroux wrote: > > Since updating to

Re: Git Polling initiated by notifyCommit failing on remote since version 2.4.4

> Have you been able to duplicate the problem on a fresh installation? > > Mark Waite > > On Thu, Mar 31, 2016 at 10:33 AM Michael Giroux > wrote: > >> Seems another user has similar issue. >> https://issues.jenkins-ci.org/browse/JENKINS-33907 >> >>

Re: Git Polling initiated by notifyCommit failing on remote since version 2.4.4

te the problem on a fresh installation? > > Mark Waite > > On Thu, Mar 31, 2016 at 10:33 AM Michael Giroux > wrote: > >> Seems another user has similar issue. >> https://issues.jenkins-ci.org/browse/JENKINS-33907 >> >> That is not exactly the same, but I'

Re: Git Polling initiated by notifyCommit failing on remote since version 2.4.4

it client plugin 1.19.6. > > I confirmed that the referenced class is included in one of the jar files > packaged with git client plugin 1.19.6. > > Have you been able to duplicate the problem on a fresh installation? > > Mark Waite > > On Thu, Mar 31, 2016 at 10:33 AM Mi

Re: Git Polling initiated by notifyCommit failing on remote since version 2.4.4

f >> this in docs, so I think this is an issue. >> >> Michael >> >> >> On Mar 31, 2016, at 12:24 PM, Mark Waite > > wrote: >> >> Git plugin 2.4.0 requires at least git client plugin 1.18.0. >> >> Git plugin 2.4.4 requires at least git cli

Job config updated by Git Parameter plugin

Parameter plugin details. >From the perspective of one trying to see configuration changes introduced by humans, this really seems like a defect. Is there a way to prevent changes in UUID from causing configuration updates? Michael Giroux -- You received this message because you are subs

Git Parameter 0.5.2-SNAPSHOT build errors

Just pulled latest source for Git Parameter plugin from github, and have 4 java errors due to undefined java.nio.file package references. java.nio.file is a new package in JDK 1.7. The effective pom for Git Parameter 0.5.2-SNAPSHOT is resolving source and target for the maven-compiler-plugin to

Re: Job config updated by Git Parameter plugin

changes resulting from a user making changes, we want to exclude config history that is injected by plugins unrelated to the actual change. On Wednesday, June 1, 2016 at 11:34:52 AM UTC-7, Michael Giroux wrote: > > Jenkins version: 1.609.3 > Git Parameter plugin: 0.4 > > I'm

How to prevent Git plugin from setting GIT_BRANCH to origin/pull-requests/*

This question involves Git plugin, Stash, and SonarQube integration, so there are multiple bits that we need to coordinate. 1. We are using Stash with the Jenkins Web Hook to trigger builds when developers push code to a branch. 2. The build checks the code out to a local branch using

Re: How to prevent Git plugin from setting GIT_BRANCH to origin/pull-requests/*

cause the branches to be pulled. This too is confusing. On Wednesday, July 13, 2016 at 8:58:52 AM UTC-7, Michael Giroux wrote: > > This question involves Git plugin, Stash, and SonarQube integration, so > there are multiple bits that we need to coordinate. > > >1. We are

Re: How to prevent Git plugin from setting GIT_BRANCH to origin/pull-requests/*

Also, if I log directly into Stash and cd to the repository, the git branch command does NOT show any of these phantom origin/pull-requests branches. These seem to be something being fabricated by Jenikins. On Wednesday, July 13, 2016 at 9:01:30 AM UTC-7, Michael Giroux wrote: > > BTW,

Re: How to prevent Git plugin from setting GIT_BRANCH to origin/pull-requests/*

to be something specific to Stash, but I'm not able to find any documentation. Would appreciate any links. Michael On Wednesday, July 13, 2016 at 8:58:52 AM UTC-7, Michael Giroux wrote: > > This question involves Git plugin, Stash, and SonarQube integration, so > there are multiple b

Git plugin notifyCommit url = localhost does not match jobs

I have configured Jenkins job to use git url: http://stash.server/scm/prj/repo.git Our repositories reside in Stash, and using the Stash Webhook to Jenkins. The default url for the notifyCommit is http://localhost/scm/prj/repo.git. Then curl http://jenkins.server/git/notifyCommit?url=http:

Re: Git plugin notifyCommit url = localhost does not match jobs

gt; It includes some heuristics that attempt to guess if two URL's are the > same, and it applies those heuristics when comparing the URL defined in the > job with the url parameter of the notifyCommit request. > > Mark Waite > > On Fri, Jul 22, 2016 at 3:54 PM Michael G

Re: Build failure with Exception in thread "main" java.lang.ClassNotFoundException: hudson.remoting.Launcher

Disconnecting the slave, and then reconnecting solved the problem for us. This causes jenkins to refresh the runtime jars on the slave. On Wednesday, June 17, 2015 at 12:55:57 PM UTC-7, 1eyed...@gmail.com wrote: > > We ultimately got our server administrator to restart Jenkins, and now the > bu

Sonarqube plugin with maven project

Our site has a single sonarqube server. Our builds have been configured as maven projects, and run the sonarqube plugin as a post build publisher. Not sure of the rationale for this approach. I have added the sonar:sonar goal to a maven build and get the same result aa jobs that use sonarqube

ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com

Job is a simple maven project. Project builds successfully from command line. Let me know what additional info you might want to look at this. ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.comjava.lang.NullPointerException

Collapsing Console Sections not parsing console in Jenkins 2.7.4

I've installed the Collapsing Console Sections plugin in Jenkins 2.7.4. I configured a couple of sections to identify SCM checkout and the start of a maven build. After running a job, the console output does not contain any sections. I see no options on job configuration to activate the plugin

Global "disable triggers" options

We have a large jenkins configuration with 1700 jobs. We have two use cases in which the configuration is copied. We make a copy of the configuration prior to any upgrade: 1. for purposes of testing new version and plugins prior to an upgrade 2. to have a running instance of the previous versio

How to solve

We upgraded from Jenkins 1.609.3 to Jenkins 2.19.2 LTS. Upgrade went very well, but we are seeing some plugin warnings on the "Manage Plugins" page (see below). The errors are all related to CloudBees plugins. There is a link to "correct" the problem, but that takes us to the plugin updates

How to remove plugins that do not appear in plugin management "Installed" tab

Sorry for the previous post. Subject line was incomplete. We upgraded from Jenkins 1.609.3 to Jenkins 2.19.2 LTS. Upgrade went very well, but we are seeing some plugin warnings on the "Manage Plugins" page (see below). The errors are all related to CloudBees plugins. There is a link to "cor

Re: How to remove plugins that do not appear in plugin management "Installed" tab

, Michael Giroux wrote: > > Sorry for the previous post. Subject line was incomplete. > > We upgraded from Jenkins 1.609.3 to Jenkins 2.19.2 LTS. Upgrade went very > well, but we are seeing some plugin warnings on the "Manage Plugins" page > (see below). The errors

What is "slave Java"

We are running Jenkins 2.19.2 with JDK 1.8. We have maven projects configured to run in older JDKs, and we get the following message: ERROR: ERROR : Invalid proje

Re: What is "slave Java"

er 18, 2016 at 8:46:22 AM UTC-7, Daniel Beck wrote: > > > > On 18.11.2016, at 15:46, Michael Giroux > > wrote: > > > > Could someone either explain, or point me to documentation that explains > what is really happening here? Specifically what does > > "R

Re: What is "slave Java"

use its behaviors > with Java 1.6. In this case the behavior is to run Maven using the JDK on > which Jenkins itself is running then set Maven properties for Java to point > @ JDK 1.6. > > Does that help? > > On Friday, November 18, 2016 at 12:46:48 PM UTC-5, Michael Giroux wro

Re: What is "slave Java"

been very helpful. Thank you very much. Michael On Saturday, November 19, 2016 at 8:38:05 AM UTC-7, Daniel Beck wrote: > > > > On 18.11.2016, at 18:46, Michael Giroux > > wrote: > > > > Thanks Daniel. But I'm still not clear on what is going on under the >

New Git Plugin Feature - configure alias host names

it plugin provided a means to configure host name aliases so that the notifyCommit message would trigger polling for 'stash.xxx.com' or 'bitbucket.xxx.com'. Would this be of general interest? Michael Giroux -- You received this message because you are subscribed to the Google Group