[JIRA] [email-ext] (JENKINS-21449) Add new trigger for claimed builds
kutzi commented on JENKINS-21449 Add new trigger for claimed builds Sounds great. I didn't know about this extension point. Is it also possible to override another trigger via the extension point like the Still Unstable trigger does for the Unstable trigger? I'd like to stop sending e-mails for all Unstable, Still Unstable, Failed, Still Failed triggers once the build has been claimed. 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21510) Plugin result icons on build page are broken
Hua Zhang created JENKINS-21510 Plugin result icons on build page are broken Issue Type: Bug Assignee: Ulli Hafner Attachments: status-icon-missing.png Components: analysis-core Created: 27/Jan/14 9:31 AM Description: The icon of plugin result on the build page is broken. Should be: https://my.jenkins.server/jenkins/static/bc778632/images/16x16/blue.png but was https://my.jenkins.server/static/bc778632/images/16x16/blue.png Jenkins URL in global configuration is https://my.jenkins.server/jenkins/ Jenkins is running on debian, started with "--prefix=/jenkins" and behind apache reverse proxy. Environment: Jenkins 1.547, analysis-core 1.54, pmd 3.37, findbugs 4.51, dry 2.38, tasks 4.38 Project: Jenkins Priority: Minor Reporter: Hua Zhang 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21510) Plugin result icons on build page are broken
Hua Zhang commented on JENKINS-21510 Plugin result icons on build page are broken Looks similar to JENKINS-6416. 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/groups/opt_out.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney edited a comment on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Full list of plugins: [root@hudson0 plugins]# ls -1d *.?pi analysis-core.jpi ant.jpi audit-trail.jpi batch-task.jpi blame-upstream-commiters.hpi build-flow-plugin.jpi buildgraph-view.jpi build-name-setter.hpi build-pipeline-plugin.jpi build-user-vars-plugin.jpi cifs.hpi ci-game.hpi conditional-buildstep.jpi config-file-provider.jpi configurationslicing.jpi copyartifact.jpi credentials.jpi cvs.jpi dashboard-view.jpi description-setter.jpi disk-usage.jpi doxygen.jpi dry.jpi ec2.jpi email-ext.jpi emma.hpi envinject.jpi external-monitor-job.jpi findbugs.jpi ftppublisher.hpi git-client.jpi github-api.jpi github.jpi git.jpi greenballs.jpi htmlpublisher.jpi jacoco.jpi javadoc.jpi jenkins-cloudformation-plugin.jpi jenkins-multijob-plugin.jpi jira.jpi jquery.jpi ldap.jpi locks-and-latches.hpi m2release.jpi m2-repo-reaper.hpi mailer.jpi managed-scripts.jpi matrix-auth.jpi maven-plugin.jpi monitoring.jpi msbuild.jpi mstest.hpi multi-module-tests-publisher.jpi nant.hpi next-build-number.jpi node-iterator-api.jpi nunit.jpi pam-auth.jpi parameterized-trigger.jpi performance.hpi phing.jpi plot.hpi pmd.jpi port-allocator.jpi promoted-builds.jpi python.hpi release.jpi repository-connector.hpi run-condition.jpi s3.jpi scm-api.jpi scm-sync-configuration.jpi scons.hpi scp.hpi sectioned-view.jpi shelve-project-plugin.jpi slave-status.hpi sonar.jpi ssh-credentials.jpi ssh-slaves.jpi subversion.jpi svn-release-mgr.hpi svn-tag.hpi testflight.jpi testInProgress.jpi testng-plugin.jpi text-finder.hpi throttle-concurrents.jpi timestamper.jpi token-macro.jpi translation.jpi url-change-trigger.hpi URLSCM.hpi urltrigger.jpi violations.hpi ws-cleanup.jpi xunit.jpi zentimestamp.jpi [root@hudson0 plugins]# 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/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-19863) Can we get more colors for promotion stars?
Marvi Benedet assigned JENKINS-19863 to Marvi Benedet Can we get more colors for promotion stars? Change By: Marvi Benedet (27/Jan/14 10:28 AM) Assignee: MarviBenedet 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/groups/opt_out.
[JIRA] [cvs] (JENKINS-6312) cvs log error
Vishwaradhya J commented on JENKINS-6312 cvs log error HI Michael, I have similar, Version 2.0 of jenkins.war file. From where do I download? Thanks 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21449) Add new trigger for claimed builds
Alex Earl commented on JENKINS-21449 Add new trigger for claimed builds Yes, you can do that as part of your descriptor, though currently you need to use the name of the trigger to do it. You can find examples in the built in triggers. 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/groups/opt_out.
[JIRA] [parameterized-remote-trigger] (JENKINS-20828) Allow to block the build untill target job finished
Tim Brown commented on JENKINS-20828 Allow to block the build untill target job finished I tried checking into github and it returned me a 403. I have it in a branch I can commit if you like? I have added the code I ahve changed to the gist - not sure I've done it right, but I can updated if required - got to rush out atm . 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21180) Attach Build Log conflicts with the ansi-color plugin
Alex Earl commented on JENKINS-21180 Attach Build Log conflicts with the ansi-color plugin I have a test build for this, are you willing to try a test build? 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/groups/opt_out.
[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)
SCM/JIRA link daemon commented on JENKINS-14026 git plugin doesnt support branch name contains slash (/) Code changed in jenkins User: Nicolas De loof Path: src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java http://jenkins-ci.org/commit/git-plugin/b22146d14997edaaf9bd95a054c65b623606d379 Log: Merge pull request #195 from Vlatombe/JENKINS-14026 JENKINS-14026 DefaultBuildChooser should handle smartly branches with / Compare: https://github.com/jenkinsci/git-plugin/compare/dcae49362fc1...b22146d14997 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/groups/opt_out.
[JIRA] [git] (JENKINS-14026) git plugin doesn't support branch name contains slash (/)
SCM/JIRA link daemon commented on JENKINS-14026 git plugin doesnt support branch name contains slash (/) Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/git/util/DefaultBuildChooser.java http://jenkins-ci.org/commit/git-plugin/ea5cad7e2759d0c9f5ed723fe590f982b0bb818d Log: JENKINS-14026 DefaultBuildChooser should handle smartly branches with / When encountering a single branch containing a '/', it is either a qualified branch or a branch containing a '/' In the first case, the branch should start with the name of a declared remote Otherwise, we fall back to unqualified behaviour, and we try to match the branch name as if it was */BRANCH 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-21180) Attach Build Log conflicts with the ansi-color plugin
Alex Earl commented on JENKINS-21180 Attach Build Log conflicts with the ansi-color plugin You can get the test build here: https://jenkins.ci.cloudbees.com/job/plugins/job/email-ext-plugin/159/org.jenkins-ci.plugins$email-ext/ 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/groups/opt_out.
[JIRA] [claim] (JENKINS-21449) Add new trigger for claimed builds
kutzi assigned JENKINS-21449 to Christian Åkerström Add new trigger for claimed builds Change By: kutzi (27/Jan/14 1:16 PM) Assignee: ChristianÅkerström 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/groups/opt_out.
[JIRA] [claim] (JENKINS-21449) Add new trigger for claimed builds
kutzi updated JENKINS-21449 Add new trigger for claimed builds Change By: kutzi (27/Jan/14 1:15 PM) Assignee: AlexEarl Component/s: claim Component/s: email-ext 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-20692) Optionally show action in CHANGES token
Alex Earl commented on JENKINS-20692 Optionally show action in CHANGES token According to the comment on getAffectedFiles, it's possible that an SCM might not implement getAffectedFiles "Noted: since this is a new interface, some of the SCMs may not have implemented this interface. The default implementation for this interface is throw UnsupportedOperationException" Would probably need a fallback to getAffectedPaths in the case of an UnsupportedOperationException. 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/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-18515) Improve folder support
teilo commented on JENKINS-18515 Improve folder support Still present in 2.9.2, although the UI implies that this should work. If you check "Recurse in subfolders" and even if you select all jobs no jobs are reported in the dashboard. unchecking "Recurse in subfolders" and selecting the immediate children works as expected - but is pretty useless in the aboce setup where you want the dashboard to look at all "commit" jobs which are nested under 2 folders. 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/groups/opt_out.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING @Jeremy: I'm not sure I understand your workround. Could you be more precise about exactly what you did when "deleting all of the modules of the failing builds"? 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/groups/opt_out.
[JIRA] [grails] (JENKINS-19643) [Executor exception] java.lang.VerifyError: Incompatible argument to function
Karel Maesen commented on JENKINS-19643 [Executor exception] java.lang.VerifyError: Incompatible argument to function FYI, I had the same issue. But the swarm-client 1.12-SNAPSHOT (with pull request #8) didn't solve the problem. When I applied PR #7 the problem was resolved. 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/groups/opt_out.
[JIRA] [claim] (JENKINS-11638) When claimed, stop sending e-mails to individuals who broke the build
kutzi commented on JENKINS-11638 When claimed, stop sending e-mails to individuals who broke the build As Alex wrote in JENKINS-21449 this could be solved by implementing a trigger extension point in email-ext 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/groups/opt_out.
[JIRA] [jenkins-jira-issue-updater] (JENKINS-21514) Add fixed version support to jira issue updater plugin
Hua Zhang created JENKINS-21514 Add fixed version support to jira issue updater plugin Issue Type: Improvement Assignee: Unassigned Attachments: jira-issue-update-pr.png Components: jenkins-jira-issue-updater Created: 27/Jan/14 1:57 PM Description: Pull request: https://github.com/jenkinsci/jira-issue-updater-plugin/pull/1 This PR added the possibility to update fixed versions of jira issues: appends the versions to / overwrites the original fixed versions environment/build variable substitution supported (as the plugin already did) non-applicable versions (since versions are project specific) are ignored, error messages are logged. Reviews and comments are greatly appreciated. Project: Jenkins Priority: Major Reporter: Hua Zhang 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/groups/opt_out.
[JIRA] [jenkins-multijob-plugin] (JENKINS-21515) Occassional failures of downstream Nunit jobs (failed access to TestResult.xml)
Steven Kitchen created JENKINS-21515 Occassional failures of downstream Nunit jobs (failed access to TestResult.xml) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: jenkins-multijob-plugin Created: 27/Jan/14 2:00 PM Description: Multi-phase job has passing job(s) which register (intermittently) as failure due to UnauthorizedAccessException Selected test(s): LocalTest.SearchTests+ForRent.FRC_BrowseFeatProps_PhoneNumberVerification .. Tests run: 2, Errors: 0, Failures: 0, Inconclusive: 0, Time: 27.1172522 seconds Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0 Unhandled Exception: System.UnauthorizedAccessException: Access to the path 'c:\jenkins\workspace\Browse Featured Property Phone Number Verification\TestResult.xml' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy) at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options) at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize) at System.IO.StreamWriter..ctor(String path) at NUnit.ConsoleRunner.ConsoleUi.Execute(ConsoleOptions options) at NUnit.ConsoleRunner.Runner.Main(String[] args) c:\jenkins\workspace\Browse Featured Property Phone Number Verificationexit -100 Build step 'Execute Windows batch command' marked build as failure Recording NUnit tests results Finished: FAILURE Environment: Unix Server/Windows 2008 RC2 slave Project: Jenkins Priority: Major Reporter: Steven Kitchen 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/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-21497) Maven jobs: Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher
ikedam commented on JENKINS-21497 Maven jobs: Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher It reproduced in my environment. Install Flexible Publish and xUnit plugin Create a new Maven 2/3 job. Add the flexible publish post-build action, and configure "Publish xUnit test result report" in it. Save Edit again Save (no need for modification) I get: Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher It does not output any stacktraces on browsers nor system logs. 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/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-21497) Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher
ikedam updated JENKINS-21497 Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher Change By: ikedam (27/Jan/14 2:15 PM) Environment: Jenkins1.532.1FlexiblePublishplugin0.12MavenIntegrationplugin2.0.1 xUnitplugin1.80 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/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-21497) Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher
ikedam updated JENKINS-21497 Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher I found it reproduces even free style projects. I think this happens combined with xUnit plugin (I updated the summary). Please report if you find same problems with other plugins. Change By: ikedam (27/Jan/14 2:14 PM) Summary: Mavenjobs: CombiningwithxUnitPlugincause Failedtoinstantiateclassorg.jenkins_ci.plugins.flexible_publish.ConditionalPublisher 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21512) Cli for ContextHashCode
Ralf Hain commented on JENKINS-21512 Cli for ContextHashCode Should not be too difficult, but I failed. This is actually more a 'help request ' than a 'feature request '. What I've got: I didn't manage to resolve the dependencies. Here I stuck: import hudson.util.FormValidation; EncodingValidator.java:30: error: cannot find symbol didn't get mvn - build to run yet 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/groups/opt_out.
[JIRA] [rtc] (JENKINS-21477) Enable multiple Jazz servers per project
Heather Fraser-Dube commented on JENKINS-21477 Enable multiple Jazz servers per project I don't have any easy answers for you. It does sound like you need a job that builds the code from Server A and then a job that builds the code from Server B on top of it. It does introduce a dependency in jobs, but it simply reflects the dependency already there. If you wanted everything built only in 1 job, then you would need to do scripting to accept load the code from Server A (using CLI), but this would not give you much in terms of traceability in the build to know what changed in the build from Server A. It would also be harder to reproduce a build unless you also start creating snapshots on Server A too. Which would mean you pretty much replicate in the CLI what a dependent job would do. It also means that changes on Server A would not result in triggering the build of B to occur either. Another option would be to use distributed SCM. That would mean the build workspace on Server B would pull components from 2 different streams (one on Server A and one on Server B). This means that states of the code on Server A would be replicated on Server B. The snapshot would contain every component so you have reproducability and traceability. We would need to make a change to the Plugin though to support the multiple credentials. Having us support multiple build workspaces would be interesting but I am not sure it would be in our immediate plans when multiple jobs or distributed SCM could do it. 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/groups/opt_out.
[JIRA] [core] (JENKINS-20682) Starting Jenkins with defined --webroot or JETTY_HOME not working.
Chad Woolley commented on JENKINS-20682 Starting Jenkins with defined --webroot or JETTY_HOME not working. This is a serious issue, especially because https://issues.jenkins-ci.org/browse/JENKINS-20858 renders Jenkins essentially unusable until a reboot. I am having this issue on multiple Jenkins installations. Can we please get a fix for this recently introduced major bug prioritized? Thanks... 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21518) Error while using SSH credentials to fetch git repository.
Meta Stable created JENKINS-21518 Error while using SSH credentials to fetch git repository. Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: jenkins_bug.txt Components: git-client, ssh-credentials Created: 27/Jan/14 2:57 PM Description: System is configured to use an SSH agent to get the build from the Git server, and build on the build agent. The system works intermittently, and when it doesn't, the error reported is: Started by an SCM change Started by an SCM change Started by an SCM change Building remotely on Build Agent 1 in workspace C:\Jenkins\workspace\Fusion 3.69 FATAL: java.io.IOException: Remote call on Build Agent 1 failed hudson.remoting.RemotingSystemException: java.io.IOException: Remote call on Build Agent 1 failed at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:183) at com.sun.proxy.$Proxy75.addCredentials(Unknown Source) at org.jenkinsci.plugins.gitclient.RemoteGitImpl.addCredentials(RemoteGitImpl.java:196) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:584) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:561) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:866) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:652) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:557) at hudson.model.Run.execute(Run.java:1665) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:230) Caused by: java.io.IOException: Remote call on Build Agent 1 failed at hudson.remoting.Channel.call(Channel.java:723) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:167) ... 13 more Caused by: java.lang.Error: Failed to deserialize the Callable object. at hudson.remoting.UserRequest.perform(UserRequest.java:104) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1$1.run(Engine.java:58) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassCastException: cannot assign instance of com.cloudbees.plugins.credentials.CredentialsScope$2 to field com.cloudbees.plugins.credentials.BaseCredentials.scope of type com.cloudbees.plugins.credentials.CredentialsScope in instance of com.cloudbees.jenkins.plugins.sshcredentials.impl.BasicSSHUserPrivateKey at java.io.ObjectStreamClass$FieldReflector.setObjFieldValues(Unknown Source) at java.io.ObjectStreamClass.setObjFieldValues(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readArray(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.defaultReadFields(Unknown Source) at java.io.ObjectInputStream.readSerialData(Unknown Source) at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.UserRequest.deserialize(UserRequest.java:182) at hudson.remoting.UserRequest.perform(UserRequest.java:98) ... 9 more This seems similar to a few other
[JIRA] [support-core] (JENKINS-21517) Capture startup log
Jesse Glick created JENKINS-21517 Capture startup log Issue Type: Improvement Assignee: Unassigned Components: support-core Created: 27/Jan/14 2:54 PM Description: It is often desirable to see all errors thrown during Jenkins startup. The list of logs in a support bundle should include one specifically capturing everything from boot until hudson.WebAppMain$3#run: Jenkins is fully up and running Project: Jenkins Priority: Major Reporter: Jesse Glick 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/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Anatoly Bubenkov commented on JENKINS-17632 Please add an option for uncompressed cloning to use --uncompressed you need write permissions to the repository, which is not always the case, and not most common case for sure, because usually the access level for jenkins is just to be able to read 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/groups/opt_out.
[JIRA] [core] (JENKINS-21087) Don't hold off building until saved for jobs copied and updated from REST API
Magnus Jacobsson commented on JENKINS-21087 Dont hold off building until saved for jobs copied and updated from REST API Any plans to fix this issue or a suggestion for a workaround that I can use from the REST API? I use this feature to create a quite large number of jobs and it's not really feasible to disable/enable them manually and I can't restart Jenkins either since it's running jobs all the time. 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/groups/opt_out.
[JIRA] [copyartifact] (JENKINS-21519) Copy Artifacts plugin should support build selector from Run Parameter
Ioannis Moutsatsos created JENKINS-21519 Copy Artifacts plugin should support build selector from Run Parameter Issue Type: Improvement Assignee: Unassigned Components: copyartifact, plugin Created: 27/Jan/14 4:03 PM Description: Using a run parameter, users can pick a single build of a certain project. This resembles the 'Specific Build' option of the Copy Artifacts but with a major advantage. A run parameter is human readable as it can include a human readable build label. Provide a Copy Artifacts BUILD_SELECTOR parameter linked to any Job, similar to how Run Parameter works (including the filter). When this option is selected the available copy source options should include the list of jobs as currently shown when a Run Parameter selection is displayed. Project: Jenkins Priority: Major Reporter: Ioannis Moutsatsos 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/groups/opt_out.
[JIRA] [analysis-core] (JENKINS-21512) Cli for ContextHashCode
Ralf Hain commented on JENKINS-21512 Cli for ContextHashCode Similar Issue: https://issues.jenkins-ci.org/browse/JENKINS-17434 "Allow to call parsers without jenkins (standalone)" (But thats not easy) 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/groups/opt_out.
[JIRA] [support-core] (JENKINS-21517) Capture startup log
Jesse Glick commented on JENKINS-21517 Capture startup log (Without this feature, there is no guarantee that logs from the last startup are even present: they might have been rotated out of sight. If they are present, it may be hard to find them intermixed among other historical log files, and there might be multiple startups captured in which case it takes some work to find the most recent.) 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/groups/opt_out.
[JIRA] [xcode] (JENKINS-21293) Xcode integration 1.4.2 Generate IPA Failed to build
Glenn Austin commented on JENKINS-21293 Xcode integration 1.4.2 Generate IPA Failed to build There are no tools to package an iPhoneSimulator build. Xcode only allows you to package iPhone builds. 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/groups/opt_out.
[JIRA] [flexible-publish] (JENKINS-21497) Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher
ikedam updated JENKINS-21497 Combining with xUnit Plugin cause Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher I found wrong codes in Flexible publish handling error messages. The message "Failed to instantiate class org.jenkins_ci.plugins.flexible_publish.ConditionalPublisher" was wrong, but should be: Failed to instantiate: class not found hudson.tasks.test.AggregatedTestResultPublisher,hudson.tasks.ArtifactArchiver,hudson.tasks.BuildTrigger,hudson.tasks.junit.JUnitResultArchiver,hudson.tasks.JavadocArchiver,org.jenkinsci.plugins.xunit.XUnitPublisher,hudson.tasks.Fingerprinter,hudson.tasks.Mailer I'll fix this problem (improper error message) in the next release. The root cause is that, Jenkins passes a broken json data. I attach that json. "stapler-class" should be the class name of the selected publisher, but passed a list of all publishers. I'm not sure why this happens only when combined with xUnit plugin. Change By: ikedam (27/Jan/14 3:01 PM) Attachment: posted_json.txt 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/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Dirk Heinrichs commented on JENKINS-17632 Please add an option for uncompressed cloning I don't understand what is meant by the last comment, could you please explain in more detail? 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/groups/opt_out.
[JIRA] [config-file-provider] (JENKINS-21494) Credentials are not injected in the settings via the environment variable
Olivier Billard commented on JENKINS-21494 Credentials are not injected in the settings via the environment variable I hope i'll be able to provide a clean pull request soon. I managed to make it work on my side. 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/groups/opt_out.
[JIRA] [teamconcert] (JENKINS-21483) java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common.
Heather Fraser-Dube commented on JENKINS-21483 java.lang.IllegalStateException: Found two dtoEvolution elements with the same componentVersion value in bundle com.ibm.team.scm.common. Thanks, I haven't seen this before. Can you provide a full stack trace. What release of the RTC Build toolkit are you using? On which platform? Have you made any changes to the toolkit since originally installed (upgraded/applied patch/etc.)? Is this occurring on the master or a slave? 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/groups/opt_out.
[JIRA] [core] (JENKINS-21087) Don't hold off building until saved for jobs copied and updated from REST API
Magnus Jacobsson commented on JENKINS-21087 Dont hold off building until saved for jobs copied and updated from REST API Found a workaround myself. I use jenkinsapi job.disable() and job.enable(). 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21516) GIT setting check in job configuration screen fails to connect
Timothy Rundle created JENKINS-21516 GIT setting check in job configuration screen fails to connect Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Attachments: Screen Shot 2014-01-27 at 9.29.03 AM.png Components: git-client Created: 27/Jan/14 2:30 PM Description: While configuring a project, the GIT connection check fails. The job succeeds when run. I added some logging and found that the workspace variable is null when the check is run so the local git repo is not found. Here is the error: Failed to connect to repository : Command "git config --local credential.helper store --file=\"/var/folders/6d/s0zlqfsn4nv866d__vsp0ff8gp/T/git6993554687459647324.credentials\"" returned status code 255: stdout: stderr: error: could not lock config file .git/config: No such file or directory Environment: Mac OSX Maverick Project: Jenkins Priority: Minor Reporter: Timothy Rundle 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/groups/opt_out.
[JIRA] [cli] (JENKINS-18282) Support node manipulation via Jenkins CLI
SCM/JIRA link daemon commented on JENKINS-18282 Support node manipulation via Jenkins CLI Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/03a04ac327b2237e5fdfffe493deecc0017c43fe Log: JENKINS-18282 Noting retroactively. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
Jesse Glick updated JENKINS-21024 Miscellaneous exceptions in config.xml can prevent entire job from loading Change By: Jesse Glick (27/Jan/14 4:39 PM) Labels: lts-candidate robustnessxstream 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/groups/opt_out.
[JIRA] [core] (JENKINS-18366) Jetty should be used rather than Winstone for embedded deployments
S Stack commented on JENKINS-18366 Jetty should be used rather than Winstone for embedded deployments Solaris 10: CLI broken at Jenkins 1.535+ Per https://issues.jenkins-ci.org/browse/JENKINS-20128?focusedCommentId=188660page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-188660, CLI works fine up to and including 1.534 @Josh, we're running Solaris 10 and while the Jenkins UI appears to work just fine in 1.535 and above, the CLI hangs: java -jar 1.538/WEB-INF/jenkins-cli.jar -s http://cits.icc.intcx.net:8080 version Exception in thread "main" java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at hudson.cli.CLI.connectViaCliPort(CLI.java:211) at hudson.cli.CLI.init(CLI.java:134) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:469) at hudson.cli.CLI.main(CLI.java:384) Observations Jetty is unpacked to the -Djava.io.tmpdir directory regardless of setting -DJETTY_HOME=/some/dir/. JNLP port is enabled; setting this to either random or a fixed port did not address the CLI timeout. 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/groups/opt_out.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Jeremy Sullivan commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING Sure Tony, In my maven builds there is a "modules" section under "configure" the issue was these modules pointed to a directory that didn't exist, and that's what it was trying to read the pom.xml from (so the pom.xml didn't exist either) and instead of throwing a file not found jenkins complains about POM_PACKAGING being null. When I deleted a module, it forced jenkins to grab everything (including the pom) from version control again, and so pom.xml was present again and POM_PACKAGING wasn't null anymore. Hope this helps. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21024) Miscellaneous exceptions in config.xml can prevent entire job from loading
Jesse Glick commented on JENKINS-21024 Miscellaneous exceptions in config.xml can prevent entire job from loading Should be considered for backport. For example, saw a job which had a number of historical builds none of which could be loaded: WARNING hudson.model.RunMap retrieve could not load /…/jobs/…/builds/2013-06-05_17-40-05 hudson.util.IOException2: Unable to read /…/jobs/…/builds/2013-06-05_17-40-05/build.xml at hudson.XmlFile.unmarshal(XmlFile.java:170) at hudson.model.Run.reload(Run.java:320) at hudson.model.Run.(Run.java:309) at hudson.model.AbstractBuild.(AbstractBuild.java:187) at hudson.model.Build.(Build.java:103) at hudson.model.FreeStyleBuild.(FreeStyleBuild.java:41) at sun.reflect.GeneratedConstructorAccessor104.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at hudson.model.AbstractProject.loadBuild(AbstractProject.java:1152) at hudson.model.AbstractProject$1.create(AbstractProject.java:339) at hudson.model.AbstractProject$1.create(AbstractProject.java:337) at hudson.model.RunMap.retrieve(RunMap.java:225) at hudson.model.RunMap.retrieve(RunMap.java:59) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:677) at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:660) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:459) at jenkins.model.lazy.AbstractLazyLoadRunMap.getByNumber(AbstractLazyLoadRunMap.java:536) at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:382) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:221) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:105) at hudson.model.Job.getBuildStabilityHealthReport(Job.java:1082) at hudson.model.Job.getBuildHealthReports(Job.java:1042) at hudson.model.Job.getBuildHealth(Job.java:1007) at sun.reflect.GeneratedMethodAccessor174.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:146) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
[JIRA] [xcode] (JENKINS-12563) Build multiple configuration
Glenn Austin
commented on JENKINS-12563
Build multiple configuration
I've done this successfully, using ${YOUR_AXIS_NAME_HERE} in the appropriate fields in the Xcode plugin configuration, e.g. General Build SettingsTarget.
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/groups/opt_out.
[JIRA] [active-directory] (JENKINS-11990) After updating Active Directory plugin the Jenkins People database is experiencing massive performance issues synching because it is trying to authenticate us
evernat commented on JENKINS-11990 After updating Active Directory plugin the Jenkins People database is experiencing massive performance issues synching because it is trying to authenticate users that are no longer in company Active Directory but are part of the Jenkins Database @alex This issue with build history may have been fixed with lazy loading in recent Jenkins versions. Anyway, the recommended heap size depends on the number of jobs, build history, etc (and 1024M is not large nowadays). Is the issue reproduced or can we close this? 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/groups/opt_out.
[JIRA] [subversion] (JENKINS-16488) doNotifyCommit fails after update to 1.45
evernat resolved JENKINS-16488 as Cannot Reproduce doNotifyCommit fails after update to 1.45 If it works now, I suppose that we can close this issue. Change By: evernat (27/Jan/14 5:06 PM) Status: Open Resolved Resolution: CannotReproduce 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/groups/opt_out.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Tony Sweeney commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING I still don't understand what you mean by "deleting a module". Are you simply wiping the build slave workspace, or are you making a change to some of the build configuration? 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/groups/opt_out.
[JIRA] [maven2] (JENKINS-21522) Enable Archive maven artifacts post-build action for free-style jobs
dma_k created JENKINS-21522 Enable Archive maven artifacts post-build action for free-style jobs Issue Type: New Feature Assignee: Unassigned Components: maven2 Created: 27/Jan/14 5:32 PM Description: With Maven3 Plugin (in Hudson) it was possible to configure the job to archive maven artifacts in free-style job, in particular the following options where available as post-build actions: * Archive Maven 3 artifacts * Include generated POMs I cannot find such options in settings for Jenkins free-style job. What I want to achieve is automatic archiving of Maven artifacts, attached to lifecycle (including those by maven-assebly-plugin). Now I have to set either */target/.jar or */target/.war, or ... for every project depending on it's maven type. Project: Jenkins Priority: Minor Reporter: dma_k 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/groups/opt_out.
[JIRA] [core] (JENKINS-9146) Allow archiving of empty directories to be enabled/disabled
Lukáš Vasek commented on JENKINS-9146 Allow archiving of empty directories to be enabled/disabled please in what state is this request? It's needed to have empty directories. +1 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/groups/opt_out.
[JIRA] [git-client] (JENKINS-21520) NoClassDefFoundError in git client 1.6.1
Gavin Swanson created JENKINS-21520 NoClassDefFoundError in git client 1.6.1 Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git-client Created: 27/Jan/14 5:16 PM Description: After update to 1.6.1 I now get the following: Building on master in workspace /usr/local/NAS/jenkins_jobs/master-Documentation/workspace Deleting project workspace... done FATAL: org.jenkinsci.plugins.gitclient.GitClient java.lang.NoClassDefFoundError: org.jenkinsci.plugins.gitclient.GitClient at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:63) at org.jenkinsci.plugins.gitclient.Git$1.invoke(Git.java:54) at hudson.FilePath.act(FilePath.java:914) at hudson.FilePath.act(FilePath.java:887) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:66) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:569) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:561) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:866) at hudson.model.AbstractProject.checkout(AbstractProject.java:1411) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Reverting to 1.6.0 resolves the issue. Environment: Linux, Jenkins Project: Jenkins Priority: Major Reporter: Gavin Swanson 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/groups/opt_out.
[JIRA] [git] (JENKINS-21521) Submodules are disabled by default as of git plugin 2.0.1
Mikhail Kalkov
created JENKINS-21521
Submodules are disabled by default as of git plugin 2.0.1
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
git
Created:
27/Jan/14 5:24 PM
Description:
Our Jenkins server has been recently upgraded. I am not sure about the plugin versions used before except for the Git Client plugin, which was 1.4.5.
After the upgrade several jobs, which relied on submodules stopped working because submodules were no longer fetched. I had to manually add the following snippet to the job configuration file in order to workaround the problem. I've also added a pre-step to run "git submodule status" so the revision number is visible in the logs.
hudson.plugins.git.extensions.impl.SubmoduleOption
disableSubmodulesfalse/disableSubmodules
recursiveSubmodulestrue/recursiveSubmodules
/hudson.plugins.git.extensions.impl.SubmoduleOption
I expected Git Plugin 2.0.1 to keep on updating submodules by default like it happened before. Furthermore, currently the "Disable submodules processing" checkbox lacks any meaning since they are disabled by default.
Here are excerpts from hudson.Proc log before and after the fix.
BEFORE
Running: git fetch --tags --progress ssh://gerritmirror:29418/tools/e4b +refs/heads/:refs/remotes/origin/
Running: git config remote.origin.url ssh://gerritmirror:29418/tools/e4b
Running: git fetch --tags --progress ssh://gerritmirror:29418/tools/e4b refs/changes/64/166564/1
Running: git rev-parse 3a97095d4de19552d9520491a186de73ed6477c5^{commit}
Running: git checkout -f 3a97095d4de19552d9520491a186de73ed6477c5
Running: git rev-parse FETCH_HEAD^{commit}
Running: git rev-list e7277f677fddf04ac67fac0dd922fbe53908093e
Running: git whatchanged --no-abbrev -M --pretty=raw -n 1024 3a97095d4de19552d9520491a186de73ed6477c5 ^e7277f677fddf04ac67fac0dd922fbe53908093e
Running: git tag -a -f -m Jenkins Build #33 jenkins-e4b-eclipse3-review-33
Running: /usr/bin/Xvfb :420 -screen 0 1024x768x24 -fbdir /proj/CoolTools/.builds/eselnlx1443/2014-01-27_15-45-23430600278062191031xvfb -auth /dev/null -audit 4
AFTER
Running: git rev-parse --is-inside-work-tree
Running: git config remote.origin.url ssh://gerritmirror:29418/tools/e4b
Running: git fetch --tags --progress ssh://gerritmirror:29418/tools/e4b refs/changes/64/166564/1
Running: git rev-parse 3a97095d4de19552d9520491a186de73ed6477c5^{commit}
Running: git checkout -f 3a97095d4de19552d9520491a186de73ed6477c5
Running: git rev-parse FETCH_HEAD^{commit}
Running: git rev-list e7277f677fddf04ac67fac0dd922fbe53908093e
Running: git whatchanged --no-abbrev -M --pretty=raw -n 1024 3a97095d4de19552d9520491a186de73ed6477c5 ^e7277f677fddf04ac67fac0dd922fbe53908093e
Running: git tag -a -f -m Jenkins Build #37 jenkins-e4b-eclipse3-review-37
Running: git remote
Running: git submodule init
Running: git submodule sync
Running: git config --get remote.origin.url
Running: git submodule update --init --recursive
Running: /usr/bin/Xvfb :409 -screen 0 1024x768x24 -fbdir /proj/CoolTools/.builds/eselnlx1443/2014-01-27_17-26-069168320542076878514xvfb -auth /dev/null -audit 4
Environment:
Jenkins Core LTS 1.532.1, Git Plugin 2.0.1, Git Client Plugin 1.6.1
Project:
Jenkins
Priority:
Minor
Reporter:
Mikhail Kalkov
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
[JIRA] [git] (JENKINS-21521) Submodules are disabled by default as of git plugin 2.0.1
Mikhail Kalkov
updated JENKINS-21521
Submodules are disabled by default as of git plugin 2.0.1
Possibly related issue: JENKINS-21057
Change By:
Mikhail Kalkov
(27/Jan/14 5:30 PM)
Description:
OurJenkinsserverhasbeenrecentlyupgraded.IamnotsureaboutthepluginversionsusedbeforeexceptfortheGitClientplugin,whichwas1.4.5.Aftertheupgradeseveraljobs,whichreliedonsubmodules
,
stoppedworkingbecausesubmoduleswerenolongerfetched.Ihadtomanuallyaddthefollowingsnippettothejobconfigurationfileinordertoworkaroundtheproblem.Ivealsoaddedapre-steptorungitsubmodulestatusso
the
submodule
revision
numberisvisibleinthelogs
numbersarelogged
.
Thiswouldhavesimplifieddebugging.
hudson.plugins.git.extensions.impl.SubmoduleOptiondisableSubmodulesfalse/disableSubmodulesrecursiveSubmodulestrue/recursiveSubmodules/hudson.plugins.git.extensions.impl.SubmoduleOptionIexpectedGitPlugin2.0.1tokeeponupdatingsubmodulesbydefaultlikeithappenedbefore.Furthermore,currentlytheDisablesubmodulesprocessingcheckboxlacksanymeaningsincetheyaredisabledbydefault.Hereareexcerptsfromhudson.Proclogbeforeandafterthefix.BEFORERunning:gitfetch--tags--progreh://gerritmirror:29418/tools/e4b+refs/heads/*:refs/remotes/origin/*Running:gitconfigremote.origin.urlssh://gerritmirror:29418/tools/e4bRunning:gitfetch--tags--progreh://gerritmirror:29418/tools/e4brefs/changes/64/166564/1Running:gitrev-parse3a97095d4de19552d9520491a186de73ed6477c5^{commit}Running:gitcheckout-f3a97095d4de19552d9520491a186de73ed6477c5Running:gitrev-parseFETCH_HEAD^{commit}Running:gitrev-liste7277f677fddf04ac67fac0dd922fbe53908093eRunning:gitwhatchanged--no-abbrev-M--pretty=raw-n10243a97095d4de19552d9520491a186de73ed6477c5^e7277f677fddf04ac67fac0dd922fbe53908093eRunning:gittag-a-f-mJenkinsBuild#33jenkins-e4b-eclipse3-review-33Running:/usr/bin/Xvfb:420-screen01024x768x24-fbdir/proj/CoolTools/.builds/eselnlx1443/2014-01-27_15-45-23430600278062191031xvfb-auth/dev/null-audit4AFTERRunning:gitrev-parse--is-inside-work-treeRunning:gitconfigremote.origin.urlssh://gerritmirror:29418/tools/e4bRunning:gitfetch--tags--progreh://gerritmirror:29418/tools/e4brefs/changes/64/166564/1Running:gitrev-parse3a97095d4de19552d9520491a186de73ed6477c5^{commit}Running:gitcheckout-f3a97095d4de19552d9520491a186de73ed6477c5Running:gitrev-parseFETCH_HEAD^{commit}Running:gitrev-liste7277f677fddf04ac67fac0dd922fbe53908093eRunning:gitwhatchanged--no-abbrev-M--pretty=raw-n10243a97095d4de19552d9520491a186de73ed6477c5^e7277f677fddf04ac67fac0dd922fbe53908093eRunning:gittag-a-f-mJenkinsBuild#37jenkins-e4b-eclipse3-review-37Running:gitremoteRunning:gitsubmoduleinitRunning:gitsubmodulesyncRunning:gitconfig--getremote.origin.urlRunning:gitsubmoduleupdate--init--recursiveRunning:/usr/bin/Xvfb:409-screen01024x768x24-fbdir/proj/CoolTools/.builds/eselnlx1443/2014-01-27_17-26-069168320542076878514xvfb-auth/dev/null-audit4
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/groups/opt_out.
[JIRA] [parameterized-remote-trigger] (JENKINS-20828) Allow to block the build untill target job finished
Maurice W. commented on JENKINS-20828 Allow to block the build untill target job finished Can you paste a link to the gist you created? 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/groups/opt_out.
[JIRA] [starteam] (JENKINS-21523) NPE during SCM polling of missing StarTeam repository
jan_ruzicka created JENKINS-21523 NPE during SCM polling of missing StarTeam repository Issue Type: Bug Affects Versions: current Assignee: jan_ruzicka Components: starteam Created: 27/Jan/14 6:34 PM Description: The SCM polling triggers NullPointerException (NPE) and fails to close socket to StarTeam server. This led to Jenkins exhausting allowed number of open file handles. Log entry: SEVERE: Failed to record SCM polling for hudson.maven.MavenModuleSet@196d898Learn about Maven 2 - again java.lang.NullPointerException at hudson.plugins.starteam.StarTeamConnection.close(StarTeamConnection.java:409) at hudson.plugins.starteam.StarTeamPollingActor.invoke(StarTeamPollingActor.java:92) at hudson.plugins.starteam.StarTeamPollingActor.invoke(StarTeamPollingActor.java:22) at hudson.FilePath.act(FilePath.java:842) at hudson.FilePath.act(FilePath.java:824) at hudson.plugins.starteam.StarTeamSCM.pollChanges(StarTeamSCM.java:190) at hudson.scm.SCM.poll(SCM.java:375) at hudson.model.AbstractProject._poll(AbstractProject.java:1402) at hudson.model.AbstractProject.poll(AbstractProject.java:1335) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:420) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:449) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) Environment: Jenkins ver. 1.509.2, StarTeam plugin 0.6.11 Project: Jenkins Priority: Major Reporter: jan_ruzicka 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/groups/opt_out.
[JIRA] [core] (JENKINS-21524) [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib
Martin Schröder created JENKINS-21524 [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: core, groovy Created: 27/Jan/14 6:59 PM Description: Due to a bug in Stapler-Groovy, it is impossible for plugins to define/use custom Taglibs that are written in Groovy. Jelly taglibs work fine, but groovy taglibs always throw an NPE as can be seen here: http://jenkins-ci.361315.n4.nabble.com/Groovy-Taglibs-td4662779.html The reason is a bug in Stapler, that causes the Groovy File resolution to fail with an NPE. Additionally, it also does not search the entire ClassLoader tree, and thus is incapable of finding the Groovy files (which to the above NPE in the first place). Replication of this issue is simple, by trying to create an empty Groovy taglib and then trying to use its tag from either a Groovy or Jelly UI file. The bug will be fixed as soon as the following patch is merged into the stapler source code and the Jenkins dependency to stapler updated: https://github.com/stapler/stapler/pull/31 Environment: N/A Project: Jenkins Priority: Major Reporter: Martin Schröder 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/groups/opt_out.
[JIRA] [core] (JENKINS-21524) [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib
Martin Schröder updated JENKINS-21524 [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib Change By: Martin Schröder (27/Jan/14 7:02 PM) Description: DuetoabuginStapler-Groovy,itisimpossibleforpluginstodefine/usecustomTaglibsthatarewritteninGroovy.Jellytaglibsworkfine,butgroovytaglibsalwaysthrowanNPEascanbeseenhere:http://jenkins-ci.361315.n4.nabble.com/Groovy-Taglibs-td4662779.htmlThereasonisabuginStapler,thatcausestheGroovyFileresolutiontofailwithanNPE.Additionally,italsodoesnotsearchtheentireClassLoadertree,andthusisincapableoffindingtheGroovyfiles(whichcausestheaboveNPEinthefirstplace).Replicationofthisissueissimple,bytryingtocreateanemptyGroovytaglib insideofaPlugin andthentryingtouseitstagfromeitheraGroovyorJellyUIfile. DONOTE:ThisissuedoesnotappearforJenkins-Core,becausethecoreusesadifferentClassLoaderthantheplugins.Assuch,StaplerwillfindtheGroovyfilesintheoutermostClassLoaderandthusnotthrowtheNPE. ThebugwillbefixedassoonasthefollowingpatchismergedintothestaplersourcecodeandtheJenkinsdependencytostaplerupdated:https://github.com/stapler/stapler/pull/31 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/groups/opt_out.
[JIRA] [core] (JENKINS-21524) [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib
Martin Schröder updated JENKINS-21524 [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib Change By: Martin Schröder (27/Jan/14 7:00 PM) Description: DuetoabuginStapler-Groovy,itisimpossibleforpluginstodefine/usecustomTaglibsthatarewritteninGroovy.Jellytaglibsworkfine,butgroovytaglibsalwaysthrowanNPEascanbeseenhere:http://jenkins-ci.361315.n4.nabble.com/Groovy-Taglibs-td4662779.htmlThereasonisabuginStapler,thatcausestheGroovyFileresolutiontofailwithanNPE.Additionally,italsodoesnotsearchtheentireClassLoadertree,andthusisincapableoffindingtheGroovyfiles(which to causes theaboveNPEinthefirstplace).Replicationofthisissueissimple,bytryingtocreateanemptyGroovytaglibandthentryingtouseitstagfromeitheraGroovyorJellyUIfile.ThebugwillbefixedassoonasthefollowingpatchismergedintothestaplersourcecodeandtheJenkinsdependencytostaplerupdated:https://github.com/stapler/stapler/pull/31 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/groups/opt_out.
[JIRA] [grails] (JENKINS-19643) [Executor exception] java.lang.VerifyError: Incompatible argument to function
Ulli Hafner reopened JENKINS-19643 [Executor exception] java.lang.VerifyError: Incompatible argument to function Change By: Ulli Hafner (27/Jan/14 7:12 PM) Resolution: Fixed Status: Resolved Reopened 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/groups/opt_out.
[JIRA] [grails] (JENKINS-19643) [Executor exception] java.lang.VerifyError: Incompatible argument to function
Ulli Hafner commented on JENKINS-19643 [Executor exception] java.lang.VerifyError: Incompatible argument to function Pull request adds a codec 1.4 dependency which is required to fix the problems with findbugs. Is grails using a newer version? 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/groups/opt_out.
[JIRA] [cli] (JENKINS-18282) Support node manipulation via Jenkins CLI
dogfood commented on JENKINS-18282 Support node manipulation via Jenkins CLI Integrated in jenkins_main_trunk #3188 JENKINS-18282 Noting retroactively. (Revision 03a04ac327b2237e5fdfffe493deecc0017c43fe) Result = UNSTABLE Jesse Glick : 03a04ac327b2237e5fdfffe493deecc0017c43fe Files : changelog.html 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/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Jesse Glick commented on JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 The split did not change the code, and should not have changed library versions either, but perhaps it introduced some kind of class loading issue. Will need @kohsuke’s assistance to get a suitable test environment. 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/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Jesse Glick updated JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 Change By: Jesse Glick (27/Jan/14 7:27 PM) Labels: regression Priority: Major Blocker Component/s: core Component/s: plugin 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/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Jesse Glick assigned JENKINS-21373 to Kohsuke Kawaguchi Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 Change By: Jesse Glick (27/Jan/14 7:27 PM) Assignee: KohsukeKawaguchi 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/groups/opt_out.
[JIRA] [windows-slaves] (JENKINS-21373) Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547
Jesse Glick commented on JENKINS-21373 Unable to connect to Windows slave after upgrade to Jenkins ver. 1.547 Should have gotten to the point of printing something like java -version returned 1.7.0_45. so since this did not happen, WindowsRemoteProcessLauncher hung. Anything in the Jenkins log? 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/groups/opt_out.
[JIRA] [core] (JENKINS-21525) Running external monitor job inside folder does not work
Jesse Glick created JENKINS-21525 Running external monitor job inside folder does not work Issue Type: Bug Assignee: Jesse Glick Components: core, external-monitor-job Created: 27/Jan/14 7:58 PM Description: While you can run an external build yourself and use either the REST or CLI to notify Jenkins of the result, if you use java -jar jenkins-core.jar folder/jobname cmd args... this does not work if the job is inside a folder. Project: Jenkins Labels: folders Priority: Major Reporter: Jesse Glick 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/groups/opt_out.
[JIRA] [core] (JENKINS-21525) Running external monitor job inside folder does not work
Jesse Glick started work on JENKINS-21525 Running external monitor job inside folder does not work Change By: Jesse Glick (27/Jan/14 7:58 PM) Status: Open InProgress 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/groups/opt_out.
[JIRA] [sloccount] (JENKINS-13235) sloccount report formating on build summary
Greg Moncreaff commented on JENKINS-13235 sloccount report formating on build summary Looks great! Thanks! 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/groups/opt_out.
[JIRA] [maven2] (JENKINS-21279) java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING
Jeremy Sullivan commented on JENKINS-21279 java.lang.IllegalArgumentException: Null value not allowed as an environment variable: POM_PACKAGING No, neither. There is a dropdown menu by the module name that will allow you to delete it. For the record, I tried to delete the workspace. It had no effect. 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/groups/opt_out.
[JIRA] [build-name-setter] (JENKINS-21526) Wrong status for Matrix jobs when using Execute concurrent builds if necessary and Set Build Name
Benoit Belbezet
created JENKINS-21526
Wrong status for Matrix jobs when using Execute concurrent builds if necessary and Set Build Name
Issue Type:
Bug
Affects Versions:
current
Assignee:
Kohsuke Kawaguchi
Components:
build-name-setter, matrix
Created:
27/Jan/14 8:35 PM
Description:
Seen with Jenkins ver. 1.548
Can be reproduced easily by creating a basic matrix job:
AXIS_A: A1 A2
AXIS_B: B1 B2 B3 B4
And setting:
Execute concurrent builds if necessary: True
Set Build Name: 123456 #${BUILD_NUMBER}
(Instead of 123456, we typically set the SCM Change ID)
As a build step:
Execute Shell: "sleep 30"
Fire 2 or 3 times "Build Now"
All the configurations should have a SUCCESS status and the global status should be SUCCESS too.
But, even if all the configurations' consoles tell "Finished: SUCCESS", some of them get a red ball failure icon anyway. And the global console tells, for example:
"A1,B1 completed with result FAILURE"
Then, the global status is FAILED, while all the configurations succeeded!
It works again if either of the options "Set Build Name" or "Execute concurrent builds if necessary" is removed.
Project:
Jenkins
Labels:
matrix
plugins
Priority:
Major
Reporter:
Benoit Belbezet
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/groups/opt_out.
[JIRA] [ec2] (JENKINS-19943) EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC)
Roman Stanchak commented on JENKINS-19943 EC2 plugin cannot connect to slaves outside us-east-1 on new AWS accounts (using EC2-VPC) Still facing the issue here...running my master on Rackspace and slave on EC2. As a quick hacky work-around, I've checked the "Use private DNS" box in Manage Jenkins Cloud Amazon EC2 Advanced...then mapped the private DNS name of my EC2 instance to the public IP address in master's /etc/hosts. 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/groups/opt_out.
[JIRA] [perforce] (JENKINS-18378) Regexp-driven validation of client workspace names
S Stack edited a comment on JENKINS-18378 Regexp-driven validation of client workspace names Jenkins 1.534 / Perforce plugin 1.3.27 In Manage Jenkins / Configure System, I've specified P4 Client name pattern as ^cits-.* In a new job, I'm able to configure Workspace as xyz-test-job. The GUI warns me Client name doesn't meet global pattern: ^cits-.* but the job is saved nonetheless. I'm able to run the job which creates the client xyz-test-job which breaks my naming pattern. JENKINS-19864 My apologies, there is already an opened task. 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/groups/opt_out.
[JIRA] [maven-info] (JENKINS-21450) NPE on Selected Module Last Version when Jenkins Job Name != artifactId
Emilio Jose Mena Cebrian assigned JENKINS-21450 to Emilio Jose Mena Cebrian NPE on Selected Module Last Version when Jenkins Job Name != artifactId Change By: Emilio Jose Mena Cebrian (27/Jan/14 10:31 PM) Assignee: olamy EmilioJoseMenaCebrian 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/groups/opt_out.
[JIRA] [maven-info] (JENKINS-20929) Maven Info Plugin NullPointer Exceptions
Emilio Jose Mena Cebrian assigned JENKINS-20929 to Emilio Jose Mena Cebrian Maven Info Plugin NullPointer Exceptions Change By: Emilio Jose Mena Cebrian (27/Jan/14 10:30 PM) Assignee: olamy EmilioJoseMenaCebrian 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/groups/opt_out.
[JIRA] [core] (JENKINS-21414) PermGen space OOME triggered on use of Jenkins GUI
Stuart Strickland commented on JENKINS-21414 PermGen space OOME triggered on use of Jenkins GUI In this URL https://www.dropbox.com/s/rdv1a69t2nau7ep/java_pid79986.hprof is a second heap dump of about 148 MB, this one triggered by attempting to view a large (6.8 MB) FindBugs warnings output. The PermGen values were set very high, 2048 MB in the creating job, 8192 MB in the JVM. Viewing a companion FindBugs warning output of about 800 KB did not trigger the heap dump. This can be triggered on demand, on an idle system that has just been restarted. I suspect some sort of memory leak in either the FindBugs plugin or Jenkins itself. I have further verified that I have installed all supporting plugins, and they are up to date. Jenkins itself was just upgraded today to 1.549, with the same result. As this screen capture shows, a large amount of this memory seems to be consumed by FindBugs. https://www.dropbox.com/s/1uc6nz2vda6ouae/HeapDump79986_memory_analysis_1.png If there is something I am doing wrong, please let me know. If there is something wrong with Jenkins or the FindBugs plugin, I hope this shines some light on it. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21525) Running external monitor job inside folder does not work
SCM/JIRA link daemon commented on JENKINS-21525 Running external monitor job inside folder does not work Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/Main.java http://jenkins-ci.org/commit/jenkins/c9d69d36bdaaa149bb64887218b35e2ca260da07 Log: FIXED JENKINS-21525 Make command to run an external job work with folders. 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/groups/opt_out.
[JIRA] [core] (JENKINS-21525) Running external monitor job inside folder does not work
SCM/JIRA link daemon resolved JENKINS-21525 as Fixed Running external monitor job inside folder does not work Change By: SCM/JIRA link daemon (27/Jan/14 10:47 PM) Status: InProgress Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [maven-info] (JENKINS-20929) Maven Info Plugin NullPointer Exceptions
Emilio Jose Mena Cebrian resolved JENKINS-20929 as Fixed Maven Info Plugin NullPointer Exceptions Fixed in version 0.1.3 Change By: Emilio Jose Mena Cebrian (27/Jan/14 11:15 PM) Status: InProgress Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [maven-info] (JENKINS-20929) Maven Info Plugin NullPointer Exceptions
Emilio Jose Mena Cebrian started work on JENKINS-20929 Maven Info Plugin NullPointer Exceptions Change By: Emilio Jose Mena Cebrian (27/Jan/14 11:14 PM) Status: Open InProgress 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/groups/opt_out.
[JIRA] [maven-info] (JENKINS-21450) NPE on Selected Module Last Version when Jenkins Job Name != artifactId
Emilio Jose Mena Cebrian commented on JENKINS-21450 NPE on Selected Module Last Version when Jenkins Job Name != artifactId which version of plugin? I can't find a version with this stacktrace at jenkins.plugins.maveninfo.columns.LastVersionColumn.getModulePattern(LastVersionColumn.java:101) at jenkins.plugins.maveninfo.columns.LastVersionColumn.getVersion(LastVersionColumn.java:113) 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/groups/opt_out.
[JIRA] [maven-info] (JENKINS-20929) Maven Info Plugin NullPointer Exceptions
SCM/JIRA link daemon commented on JENKINS-20929 Maven Info Plugin NullPointer Exceptions Code changed in jenkins User: Emilio Jose Mena Cebrian Path: src/main/java/jenkins/plugins/maveninfo/extractor/properties/PomPropertiesFinder.java http://jenkins-ci.org/commit/maven-info-plugin/8da217868f6f7e2e81609827fd8e3d5962f21152 Log: JENKINS-20929 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/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-21527) getting incorrect parameter values from upstream job when a manual downstream job is shared by multiple upstream jobs.
shane kim
created JENKINS-21527
getting incorrect parameter values from upstream job when a manual downstream job is shared by multiple upstream jobs.
Issue Type:
Bug
Assignee:
Unassigned
Components:
build-pipeline
Created:
27/Jan/14 11:57 PM
Description:
to reproduce the issue:
1. create a parameterized job called upstreamA with upstreamJobName parameter, add auto-downstream job as a downstream parameterized job, and add manual-downstream job as a manual downstream job
2. create a parameterized job called upstreamB with upstreamJobName parameter, add auto-downstream job as a downstream parameterized job, and add manual-downstream job as a manual downstream job
3. create a parameterized job called 'manual-downstream' with upstreamJobName parameter and set Build name to ${ENV,var="upstreamJobName"}-${BUILD_NUMBER} (have to use Set Build Name plugin)
4. create a parameterized job called 'auto-downstream' with upstreamJobName parameter and set Build name to ${ENV,var="upstreamJobName"}-${BUILD_NUMBER} (have to use Set Build Name plugin)
5. Create a build pipeline view named 'pipelineA' and set upstreamA as initial job
6. Create a build pipeline view named 'pipelineB' and set upstreamB as initial job
7. go to upstreamA and trigger the job with upstreamJobName = upstreamA
8. go to upstreamB and trigger the job with upstreamJobName = upstreamB
9. go to pipelineA view and trigger the manual downstream job
10. go to pipelineB view and trigger the manual downstream job
11. After a while, refresh pipelineA and pipelineB views' pages and then watch manual jobs' build names. Both will have the same names on manual jobs' builds.
Project:
Jenkins
Priority:
Major
Reporter:
shane kim
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/groups/opt_out.
[JIRA] [gradle-jpi-plugin] (JENKINS-21431) Build fails with newer versions of core
abayer resolved JENKINS-21431 as Fixed Build fails with newer versions of core Fixed and released, inadvertently as 0.5.2 'cos the gradle release plugin confused me. =) Change By: abayer (28/Jan/14 12:06 AM) Status: Open Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [core] (JENKINS-21525) Running external monitor job inside folder does not work
dogfood commented on JENKINS-21525 Running external monitor job inside folder does not work Integrated in jenkins_main_trunk #3189 FIXED JENKINS-21525 Make command to run an external job work with folders. (Revision c9d69d36bdaaa149bb64887218b35e2ca260da07) Result = UNSTABLE Jesse Glick : c9d69d36bdaaa149bb64887218b35e2ca260da07 Files : changelog.html core/src/main/java/hudson/Main.java 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/groups/opt_out.
[JIRA] [core] (JENKINS-21524) [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib
Jesse Glick updated JENKINS-21524 [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib Change By: Jesse Glick (28/Jan/14 12:18 AM) Labels: groovystapler Component/s: groovy 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/groups/opt_out.
[JIRA] [core] (JENKINS-21524) [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib
Jesse Glick assigned JENKINS-21524 to Unassigned [STAPLER] NullPointerException thrown when trying to use/define a Groovy Taglib Change By: Jesse Glick (28/Jan/14 12:18 AM) Assignee: JesseGlick 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/groups/opt_out.
[JIRA] [throttle-concurrents] (JENKINS-21044) Throttle Concurrent Builds blocking Jenkins queue
Jesse Glick commented on JENKINS-21044 Throttle Concurrent Builds blocking Jenkins queue No idea for a fix from me, sorry. The tip about unsynchronized access sounds plausible, but as you note, all accesses to the map should be synchronized from the same monitor. If you can reproduce the bug, then there are various ways of proceeding with debugging, such as switching to a (strong) HashMap to see if the endless loop goes away; this would of course introduce a memory leak, but at least you would have narrowed down the problem. 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/groups/opt_out.
[JIRA] [vsphere-cloud] (JENKINS-21528) Can't turn on a VM
Franck Y created JENKINS-21528 Cant turn on a VM Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: 1.png, 2.png Components: vsphere-cloud Created: 28/Jan/14 12:50 AM Description: Hi I have a problem and can't turn on a VM. I have NO problem to turn OFF a VM. My configuration My slave is configured to start with a snapshot of executors = 2 Remote FS root = /root/ Force VM launch = True I have attached the 2 screenshots of the slave config and the job config The exception that happen at the end is the following Building remotely on svr1 in workspace /root/workspace/turnon FATAL: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:722) at hudson.FilePath.act(FilePath.java:903) at hudson.FilePath.act(FilePath.java:887) at hudson.FilePath.mkdirs(FilePath.java:1057) at hudson.model.AbstractProject.checkout(AbstractProject.java:1404) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:651) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:560) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: hudson.remoting.RequestAbortedException: java.io.IOException: Unexpected termination of the channel at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:782) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2598) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1318) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:370) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:71) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: Jenkins 1.549, vSphere Plugin 1.1.3, Vsphere 5.1 Project: Jenkins Labels: plugin Priority: Blocker Reporter: Franck Y 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
[JIRA] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Erik Ylvisaker commented on JENKINS-20492 Re-Execute promotion button is gone I am experiencing this same bug. If I use the Force Promotion button to promote a build the re-execute promotion button never appears and I have to kick off another build to redo a promotion. This is a pretty serious problem for me. 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/groups/opt_out.
[JIRA] [jacoco] (JENKINS-21529) Add lines of code to the API
Kimon Papahadjopoulos created JENKINS-21529 Add lines of code to the API Issue Type: Improvement Assignee: Ognjen Bubalo Components: jacoco Created: 28/Jan/14 2:57 AM Description: API reports the percentages, but not the raw numbers. These numbers can be seen in the GUI (M(issed) and C(overed)), but appears to be unavailable via the API. Since for example line counting varies a lot tool to tool, this would be very valuable, especially to determine if one tool is counting differently than another. Project: Jenkins Priority: Minor Reporter: Kimon Papahadjopoulos 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/groups/opt_out.
[JIRA] [jacoco] (JENKINS-21529) Jacoco plugin: add raw number metrics to the API
Kimon Papahadjopoulos updated JENKINS-21529 Jacoco plugin: add raw number metrics to the API Change By: Kimon Papahadjopoulos (28/Jan/14 2:59 AM) Summary: Addlinesofcode Jacocoplugin:addrawnumbermetrics totheAPI 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/groups/opt_out.
[JIRA] [git] (JENKINS-14717) Wipe out workspace nonfunctional with local subdirecory
Mark Waite closed JENKINS-14717 as Fixed Wipe out workspace nonfunctional with local subdirecory Change By: Mark Waite (28/Jan/14 4:23 AM) Status: Resolved Closed 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/groups/opt_out.
[JIRA] [git] (JENKINS-14717) Wipe out workspace nonfunctional with local subdirecory
Mark Waite resolved JENKINS-14717 as Fixed Wipe out workspace nonfunctional with local subdirecory Since the original submitter reported that they are able to clear the repository with "git clean", and since the "wipe workspace" works correctly on Linux, I've closed this bug and left JENKINS-19994 as the placeholder bug for the Windows specific problem that pack files are left open. When the pack files are left open on Windows, the operating system will not allow the files to be deleted. Change By: Mark Waite (28/Jan/14 4:23 AM) Status: Open Resolved Resolution: Fixed 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/groups/opt_out.
[JIRA] [accelerated-build-now] (JENKINS-21028) I can get on to ci.bukkit.org
jim mccork started work on JENKINS-21028 I can get on to ci.bukkit.org Change By: jim mccork (28/Jan/14 4:29 AM) Status: Open InProgress 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/groups/opt_out.
[JIRA] [ws-cleanup] (JENKINS-21530) Workspace Cleanup Plugin implementation
Vignesh V created JENKINS-21530 Workspace Cleanup Plugin implementation Issue Type: New Feature Affects Versions: current Assignee: Unassigned Components: ws-cleanup Created: 28/Jan/14 4:51 AM Description: I'm currently trying to implement workspace cleanup plugin in my local Jenkins, but we do have an option in Jenkins job configuration page 'Clean Workspace before each build' which almost does the same job as of this plug-in apart from selectively removing the files or folders i.e (the pattern we give for inclusion /exclusion) I would like to implement this plug-in my local Jenkins to clear up the workspace after/before each build. A clarification b/n the above two features will be really helpful, how this plug-in differs from the option Clean Workspace before each build' or both the features does the exact same base work (cleaning-up the workspace) Thanks in advance ! --Vignesh Due Date: 29/Jan/14 12:00 AM Environment: Linux - Cent OS 5.5 Jenkins v1.509.3 Project: Jenkins Priority: Major Reporter: Vignesh V 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/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Dirk Heinrichs commented on JENKINS-17632 Please add an option for uncompressed cloning Hmm, I wonder where you got this information from. Never heard of such a restriction. 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/groups/opt_out.
[JIRA] [ownership] (JENKINS-21390) Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration
Oleg Nenashev commented on JENKINS-21390 Not able to build using build button when creating a job by using Inheritance Project together with ownership + project role configuration Sorry for the late response. Seems I've missed the notification. I have not much experience with Inheritance plugin, so I'm not sure how it generates jobs, handles inheritance, etc. I'll try to reproduce the issue on the next week. Then I'll be able to provide some ETAs. P.S.: I also recommend to use @OwnerNoSid and @CoOwnerNoSid macros (see the example in https://wiki.jenkins-ci.org/display/JENKINS/Ownership-Based+security). In such way you will be able to set ownership to groups (including "authenticated"), etc. 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/groups/opt_out.
[JIRA] [mercurial] (JENKINS-17632) Please add an option for uncompressed cloning
Anatoly Bubenkov commented on JENKINS-17632 Please add an option for uncompressed cloning did you try to use uncompressed for some readonly repo? 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/groups/opt_out.
