[JIRA] (JENKINS-58007) ERROR: Processing failed due to a bug in the code. Please report this to the issue tracker
Title: Message Title michael giroux created an issue Jenkins / JENKINS-58007 ERROR: Processing failed due to a bug in the code. Please report this to the issue tracker Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-06-13 12:57 Environment: Jenkins: 2.150.3 JRE: OpenJDK 1.8.0_212 Linux: 3.10.0-957.12.1.el7.x86_64 #1 SMP Wed Mar 20 11:34:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Priority: Minor Reporter: michael giroux ERROR: Processing failed due to a bug in the code. Please report this to the issue tracker ( https://jenkins.io/redirect/report-an-issue ). java.lang.NullPointerException at jenkins.plugins.maveninfo.extractor.properties.PomPropertiesFinder.findProperties(PomPropertiesFinder.java:42) at jenkins.plugins.maveninfo.extractor.MavenInfoExtractor.extract(MavenInfoExtractor.java:58) at jenkins.plugins.maveninfo.extractor.MavenInfoEnvironment.tearDown(MavenInfoEnvironment.java:42) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:908) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:504) at hudson.model.Run.execute(Run.java:1810) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:543) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) project=hudson.maven.MavenModuleSet@4d4a6172[Mobile-Android-Perfecto-Regression-Tests] project.getModules()=[hudson.maven.MavenModule@54c0b0c9[Mobile-Android-Perfecto-Regression-Tests/choicehotels.mobile:choice-mobile-android][Mobile-Android-Perfecto-Regression-Tests/choicehotels.mobile:choice-mobile-android][relativePath:]]
[JIRA] (JENKINS-54740) Jenkins running build for every branch in repository.
Title: Message Title
michael giroux created an issue
Jenkins / JENKINS-54740
Jenkins running build for every branch in repository.
Issue Type:
Bug
Assignee:
Mark Waite
Components:
git-plugin
Created:
2018-11-21 00:13
Environment:
Jenkins 2.138.3 Git-Plugin 3.9.1 Linux ${HOSTNAME} 3.10.0-862.14.4.el7.x86_64 #1 SMP Fri Sep 21 09:07:21 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
Priority:
Minor
Reporter:
michael giroux
User has configured a job with branch specifier "**". When the user ran the build, Jenkins ran a build for every branch in the repository. We've seen this before. The twist here is that we upgraded the Jenkins hardware, and Jenkins version. We did an rsync of the old jenkins data directory to the new server. On the old server, the job only ran when a new commit was pushed to the repository, and only the branch that changed. This ticket is more of a question than a problem since we expect this for a fresh install, but we were surprised that the builds were running for every branch since we copied the original workspace. The question than is how does jenkins keep track of which branches/commits have been built? What additional files, and/or precautions do we need to take to make sure this does not happen again. We are unable to locate any documentation that explains exactly how the git plugin manages to keep track of which commits have been build.
[JIRA] (JENKINS-42555) Allow host name alias for Git notifyCommit URLs
Title: Message Title michael giroux created an issue Jenkins / JENKINS-42555 Allow host name alias for Git notifyCommit URLs Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2017/Mar/07 9:12 PM Environment: Jenkins 2.32.2, Linux Redhat EL7, Java 1.8.0_121 Priority: Minor Reporter: michael giroux Recently upgraded from Atlassian Stash to Atlassian Bitbucket Server. At that time, we updated the host name from 'stash' to 'bitbucket' to provide a URL consistent with the tool name. This has the adverse effect of breaking the Stash Webhook To Jenkins in that the notifyCommit messages include the Bitbucket Server base URL which has now changed from stash.xxx.xx to bitbucket.xxx.xx. It would be nice if the Git plugin allowed to configure alias names for the git host such that notifyCommit for 'stash.xxx.xx/some/repository' would trigger polling for all associated host aliases. This would eliminate the need to do a bulk edit on the Jenkins jobs to reconfigure the git urls. Add Comment
[JIRA] [maven-plugin] (JENKINS-29004) Build is running with wrong JDK Version
Title: Message Title michael giroux commented on JENKINS-29004 Re: Build is running with wrong JDK Version For more about toolchains see https://maven.apache.org/guides/mini/guide-using-toolchains.html Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-29004) Build is running with wrong JDK Version
Title: Message Title michael giroux commented on JENKINS-29004 Re: Build is running with wrong JDK Version I want to be sure I understand what is being said. If we configure a Jenkins job as a maven project, the JDK used to run maven compiles must be at least JDK 1.7 required to run Jenkins. If we configure the job as a freestyle job, and execute a maven build step, the JDK used for the job may be JDK 1.6. What about toolchains? It seems that the whole point of maven toolchains is to allow maven-compiler-plugin to use a different JDK than the one running maven itself. Should we be able to configure the job as a maven project, building in JDK 1.7 or even 1.8, and using toolchains mechanism, specify the JDK 1.6 path for the maven-compiler-plugin? This seems like it should be the advice. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-33084) Git Parameter plugin should prune stale remote branches
Title: Message Title michael giroux commented on JENKINS-33084 Re: Git Parameter plugin should prune stale remote branches Thanks for the support. Will watch for the update. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-32712) Job with Git polling "succeeds" with "no changes" although the Git polling failed
Title: Message Title michael giroux commented on JENKINS-32712 Re: Job with Git polling "succeeds" with "no changes" although the Git polling failed > I'm not sure there is currently any location to show that git polling failed. Perhaps this type of failure could result in a job being triggered. The job would fail (hopefully) during the git checkout leaving the git responses in the job's console output. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33202) Enhance Git Plugin LocalBranch to better support Maven release builds
Title: Message Title michael giroux updated an issue Jenkins / JENKINS-33202 Enhance Git Plugin LocalBranch to better support Maven release builds Change By: michael giroux Maven SCM support for branches relies on the local branch name being the same as the remote branch name. Tools such as the maven-release-plugin will push changes using the same local and remote branch names as explained at https://maven.apache.org/scm/git.htmlEx. git push pushUrl currentBranch:currentBranchJenkins jobs that perform a maven release MUST configure the LocalBranch extension with the correct branch name sans the remote name. For example, if building a release for origin/master, you must configure LocalBranch to be master.To facilitate this requirement, LocalBranch values of "**" or null should be allowed and result in using the remote branch name. Pull Request covering this feature submitted https://github.com/jenkinsci/git-plugin/pull/381 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-33202) Enhance Git Plugin LocalBranch to better support Maven release builds
Title: Message Title michael giroux created an issue Jenkins / JENKINS-33202 Enhance Git Plugin LocalBranch to better support Maven release builds Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 28/Feb/16 3:21 PM Priority: Minor Reporter: michael giroux Maven SCM support for branches relies on the local branch name being the same as the remote branch name. Tools such as the maven-release-plugin will push changes using the same local and remote branch names as explained at https://maven.apache.org/scm/git.html Ex. git push pushUrl currentBranch:currentBranch Jenkins jobs that perform a maven release MUST configure the LocalBranch extension with the correct branch name sans the remote name. For example, if building a release for origin/master, you must configure LocalBranch to be master. To facilitate this requirement, LocalBranch values of "**" or null should be allowed and result in using the remote branch name. Add Comment
[JIRA] [git-plugin] (JENKINS-32998) add condition to the GIT clone/pull step
Title: Message Title
michael giroux commented on JENKINS-32998
Re: add condition to the GIT clone/pull step
Perhaps the Git plugin is overkill for this type of job. Have you considered setting SCM to none and using a simple build step to execute a shell script that tests the parameter, and does the checkout as appropriate?
[ "$ {parameter}
" = "checkout" ] && git checkout ...
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-33084) Git Parameter plugin should prune stale remote branches
Title: Message Title michael giroux created an issue Jenkins / JENKINS-33084 Git Parameter plugin should prune stale remote branches Issue Type: Bug Assignee: Niklaus Giger Components: git-parameter-plugin Created: 22/Feb/16 4:22 PM Priority: Minor Reporter: michael giroux The git-parameter plugin presents a list of branches based on the current workspace. The list can include remote branches that have been deleted. The plugin should prune the remote branches (similar to git plugin prune stale remote branches) before presenting the list. Add Comment
[JIRA] [cli] (JENKINS-26291) cli list-jobs returns display name instead of job name
michael giroux created JENKINS-26291 cli list-jobs returns display name instead of job name Issue Type: Bug Assignee: Unassigned Components: cli Created: 05/Jan/15 3:11 PM Description: cli list-jobs returned the display-name for a job. Subsequent attempt to use the job name to get the configuration returned an error: No such job 'springframework-beanmapper-util'; perhaps you meant 'Springframework-Extensions-Release'? Example script: IFS=$'\n' for a in cli list-jobs do cli get-job "$a" done The cli get-job fails for any job that has a display-name set to a value that does not match the actual job name. Environment: Jenkins 1.565.2 Linux 2.6.18-398.el5 #1 SMP Tue Aug 12 06:26:17 EDT 2014 x86_64 x86_64 x86_64 GNU/Linux Project: Jenkins Priority: Minor Reporter: michael giroux This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
