[JIRA] [violations-plugin] (JENKINS-14970) XML File pattern for JSLINT is not getting persisted.
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-14970 XML File pattern for JSLINT is not getting persisted. Change By: Tomas Bjerre Status: Open Resolved Assignee: peterkittreilly TomasBjerre Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [violations-plugin] (JENKINS-22364) Jenkins Violation Plugin Does Not Populate XML Filename Pattern
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-22364 Jenkins Violation Plugin Does Not Populate XML Filename Pattern Change By: Tomas Bjerre Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cloudfoundry-plugin] (JENKINS-28885) NPE when deploying w/o any services
Title: Message Title William Gautier commented on JENKINS-28885 Re: NPE when deploying w/o any services It seems a saved 1.3.x configuration does not convert well into the 1.4 configuration because of the added option. I'll have to see what I can do about that next time. To fix your problem, have you tried adding a service creation, applying the changes, then removing the service creation and applying the changes again, like Andreas did? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-29016) Option If the scripts fails doesn't cause build failure
Title: Message Title Walter Kacynski created an issue Jenkins / JENKINS-29016 Option If the scripts fails doesn't cause build failure Issue Type: Bug Assignee: wolfs Components: groovy-postbuild-plugin Created: 22/Jun/15 4:53 PM Priority: Minor Reporter: Walter Kacynski If the groovy script fails; the build result will not be downgraded. I assume that this is related to JENKINS-12010 Add Comment This message was sent by Atlassian JIRA
[JIRA] [violations-plugin] (JENKINS-28880) Maven builds fail with IllegalStateException: cannot change build result while in COMPLETED
Title: Message Title Tomas Bjerre stopped work on JENKINS-28880 Change By: Tomas Bjerre Status: InProgress Open Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [violations-plugin] (JENKINS-28762) violations plugin breaks jobs GUI and fail builds those configured with compiler warning
Title: Message Title Tomas Bjerre updated an issue Jenkins / JENKINS-28762 violations plugin breaks jobs GUI and fail builds those configured with compiler warning Change By: Tomas Bjerre Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29015) Error building vbp projects, 99.9% of builds are ok, just 1 project gets chopped
Title: Message Title Sebastian Segovia created an issue Jenkins / JENKINS-29015 Error building vbp projects, 99.9% of builds are ok, just 1 project gets chopped Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jun/15 3:19 PM Environment: Jenkins version 1.547Ant Plugin 1.2 Credentials Plugin 1.9.3 CVS Plugin 2.11 Javadoc Plugin 1.1 LDAP Plugin 1.6 Mailer 1.6 Mask Passwords Plugin 2.7.2 Matrix Authorization Strategy Plugin 1.1 Maven Project Plugin 2.1 Monitoring external jobs 1.2 PAM Authentication plugin 1.1 SSH Credentials Plugin 1.6 SSH Slaves plugin 1.5 Subversion Plugin 1.54 Translation Assistance Plugin 1.10 Windows Slaves Plugin 1.0 Priority: Critical Reporter: Sebastian Segovia Hi, I have a jenkins task that runs an ant script to build and deploy VBP files. Everything is good but ONE and just ONE project: When I do a full build from Jenkins, we get few display issues (like few user controls being chopped off). But when we do a full build from Visual Basic 6, from command line invoking ant, from a batch file invoking ant, etc., it throws no such issues. But if i use the same scripts from jenkins, it chops some user controls. Please let me know if this
// ASIC Physical Design Engineer // Hillsboro, OR // 6 Months
*Role: ASIC Physical Design Engineer* *Duration: 3 to 6 months (extension possible)* *Location: Hillsboro, OR* *Job Description * *Qualifications Basic* · Bachelor’s degree or foreign equivalent required. · 4 to 6 years of experience in ASIC Physical Design *Preferred Expertise* · At least 4 years of experience in the following skills - Netlist-GDS flow with Synthesis, Layout (Floorplan, Place and Route, clock tree synthesis), Static Timing Analysis, Formal Verification, Physical Verification(DRC, LVS) and Power Analysis(IR drop, EMIG), Leakage Power Optimization using ICCLR/PTLR flows, on 22nm, 14nm, or lower process technology · Desired Tools Experience: Synopsys ICC flow, Prime Time, Design Compiler, Redhawk, LEC/Formality, and Caliber. · At least 4 years of experience in Project life cycle activities on development and maintenance projects. · At least 4 years of experience in Physical Design and STA review. · At least 4 years of experience in ASIC development life cycle. · Ability to work in team in diverse/ multiple stakeholder environment -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Kevin Phillips commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock Why were such large changes rushed into an LTS release? My sentiments exactly. We hit at least 6 or 7 hugely critical, production stop bugs just like this when doing our latest upgrade and we've had to devote significant time and effort just to get back to a state similar to what we were in before the upgrade - and that work is still ongoing today after weeks of effort. I'd like to say this is an isolated circumstance but the last 2 or 3 upgrades we've tried since our adoption of the tool a couple of years ago have had similar results. In fact, I've even gone so far as to question whether there is any value whatsoever in adopting the LTS edition at all. It's benefit is supposed to provide a stable working environment for production use but in-so-far as upgrades are concerned, that seems far from the truth. Then, to make matters worse, fixes for the critical bugs are expected to be rolled out and tested on the mainline first, meaning that fixes take way longer to get released on the LTS branch - which compounds the problem. Really, we love the tool - when it works. But managing upgrades is so painful that we may need to consider adopting a different tool in the longer term. We just can't afford to spend this amount of time and effort managing the tool, and the cost of the downtime it causes for our production teams. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Trey Bohon commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock This was pretty brutal for us. v1.609.1 is completely broken without a working queue system for build blocker - we use it extensively along with job weight to control safe parallelism on single nodes. After mutating all of our build history to v1.609.1, going back to v1.596.3 removed all build history visibility. v1.608 fixes the queue system and most of build history, but we have some weird items...seems like any builds on v1.609.1 are identified as happening in year 1969, and tons of jobs claim never to have run or failed even though they have hundreds of times. I don't feel like v1.609.1 was delivered with the spirit of LTS. After remoting in a few hours over the weekend to update our Jenkins master (took 3 hours to mutate build history) I got in office to this bug. Why were such large changes rushed into an LTS release? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-27371) Parent builds sometimes hang on successful child builds of same type
Title: Message Title Simon Weber commented on JENKINS-27371 Re: Parent builds sometimes hang on successful child builds of same type Mathieu Cantin bummer; we just had a build hang. Here are the logs, my comments like this so jira highlights them. From the build itself: Started by upstream project platform_deploy_listener build number 219 snip [MultiJob] Starting job platform_parallel. [MultiJob] Starting job platform_parallel. [MultiJob] Starting job venmo_platform_external_integration. [MultiJob] Starting job venmo_platform_external_integration. [MultiJob] Starting job scope_frontend. [MultiJob] Finished Build : #96 - deploy of Job : scope_frontend with status : SUCCESS [MultiJob] Finished Build : #6837 of Job : platform_parallel with status : SUCCESS [MultiJob] Finished Build : #6836 of Job : platform_parallel with status : SUCCESS [MultiJob] Finished Build : #1248 - deploy of Job : venmo_platform_external_integration with status : SUCCESS Build timed out (after 20 minutes). Marking the build as aborted. [MultiJob] Aborting all subjobs. [MultiJob] Aborting platform_parallel. [MultiJob] Aborting platform_parallel. [MultiJob] Aborting venmo_platform_external_integration. [MultiJob] Aborting venmo_platform_external_integration. [MultiJob] Aborting scope_frontend. Build was aborted snip [MultiJob] Finished Build : #1247 - deploy of Job : venmo_platform_external_integration with status : ABORTED here's the build that hung From Jenkins: Jun 22, 2015 2:58:55 PM INFO venmo_platform_test_and_deploy - #863 Started by ... Jun 22, 2015 3:09:10 PM INFO hudson.model.Run execute venmo_platform_external_integration #1247 main build action completed: SUCCESS here we see it completed successfully Jun 22, 2015 3:09:11 PM INFO hudson.model.Run execute venmo_platform_external_integration #1248 main build action completed: SUCCESS Jun 22, 2015 3:09:20 PM SEVERE hudson.model.Executor finish1 Executor threw an exception java.util.NoSuchElementException perhaps this is related? We keep the most recent 1000 builds. at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:76) at jenkins.model.lazy.LazyLoadRunMapEntrySet$1.next(LazyLoadRunMapEntrySet.java:63) at java.util.AbstractMap$2$1.next(AbstractMap.java:385) at hudson.util.RunList.subList(RunList.java:139) at hudson.tasks.LogRotator.perform(LogRotator.java:125) at hudson.model.Job.logRotate(Job.java:467) at hudson.model.Run.execute(Run.java:1808) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:374) these look to be expected Jun 22, 2015 3:18:48 PM INFO hudson.model.Run execute platform_deploy_listener #219 aborted java.lang.InterruptedException at java.lang.Object.wait(Native Method) at java.lang.Object.wait(Object.java:503) at hudson.remoting.AsyncFutureImpl.get(AsyncFutureImpl.java:73) at hudson.plugins.parameterizedtrigger.TriggerBuilder.perform(TriggerBuilder.java:135) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) at hudson.model.Build$BuildExecution.build(Build.java:205) at hudson.model.Build$BuildExecution.doRun(Build.java:162) at
[JIRA] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Trey Bohon edited a comment on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock Thiswasprettybrutalforus.v1.609.1iscompletelybrokenwithoutaworkingqueuesystemforbuildblocker-weuseitextensivelyalongwithjobweighttocontrolsafeparallelismonsinglenodes.Aftermutatingallofourbuildhistorytov1.609.1,goingbacktov1.596.3removedallbuildhistoryvisibility.v1.608fixesthequeuesystemandmostofbuildhistory,butwehavesomeweirditems...seemslikeanybuildsonv1.609.1areidentifiedashappeninginyear1969,andtonsofjobsclaimnevertohaverunorfailedeventhoughtheyhavehundredsoftimes.Idon'tfeellikev1.609.1wasdeliveredwiththespiritofLTS.AfterremotinginafewhoursovertheweekendtoupdateourJenkinsmaster(took3hourstomutatebuildhistory)Igotinofficetothisbug.WhyweresuchlargechangesrushedintoanLTSrelease? Edit:IfKeviniscorrectanditisapre-existingbugthathappenstobeexposedbycorechanges,thenIcouldseehowthisstreakofbadluckhappened. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-29018) Store a stable unique ID for each credential
Title: Message Title Christopher Orr created an issue Jenkins / JENKINS-29018 Store a stable unique ID for each credential Issue Type: Improvement Assignee: Unassigned Components: google-oauth-plugin Created: 22/Jun/15 6:37 PM Priority: Minor Reporter: Christopher Orr Currently the project name is the only way to refer to a credential, e.g. via GoogleRobotCredentials.getById(projectName); However as this is a free text field, users can rename the credential, and jobs configured to use that credential (having stored the project name value, aka id in the job config) will no longer work. Other credential types seem to use the id field to store a stable UUID value (which isn't shown to the user), e.g. https://github.com/jenkinsci/credentials-plugin/blob/a6c40a1/src/main/java/com/cloudbees/plugins/credentials/impl/BaseStandardCredentials.java#L73 So it seems like id here should really be projectName — it would be nice if this plugin used the id field in the same way as other credential plugins.
[JIRA] [violations-plugin] (JENKINS-19260) Cannot parse codenarc xml, due to empty path attribute in element Package
Title: Message Title SCM/JIRA link daemon commented on JENKINS-19260 Re: Cannot parse codenarc xml, due to empty path attribute in element Package Code changed in jenkins User: Tomas Bjerre Path: src/main/java/hudson/plugins/violations/parse/AbstractParser.java src/main/java/hudson/plugins/violations/types/codenarc/CodenarcParser.java src/test/java/hudson/plugins/violations/types/codenarc/CodenarcParserHudsonTest.java src/test/resources/hudson/plugins/violations/types/codenarc/CodeNarcReportEmptyPath.xml http://jenkins-ci.org/commit/violations-plugin/c74da20e0b4272f09556001b07b4e70028c5a76c Log: JENKINS-19260 Allowing empty path in CodenarcParser Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-24571) support private keys from new google developer console
Title: Message Title Christopher Orr closed an issue as Fixed This is included in version 0.3 of the plugin. Jenkins / JENKINS-24571 support private keys from new google developer console Change By: Christopher Orr Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26860) restrict parallel runs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26860 Re: restrict parallel runs Code changed in jenkins User: Jesse Glick Path: CHANGES.md job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowJob/configure-entries.jelly http://jenkins-ci.org/commit/workflow-plugin/795ee9a9d64bc8cda649e1fb19546be4d31e5985 Log: Merge pull request #142 from jglick/concurrent- JENKINS-26860 JENKINS-26860 WorkflowJob.concurrentBuild Compare: https://github.com/jenkinsci/workflow-plugin/compare/4d53ca2b683d...795ee9a9d64b Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29021) Under certain configurations queued jobs can deadlock each other
Title: Message Title Erik Lattimore created an issue Jenkins / JENKINS-29021 Under certain configurations queued jobs can deadlock each other Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jun/15 9:47 PM Environment: Jenkins 1.609.1, Linux OpenJDK 6, Plugins: active-directory 1.41 true false all-changes 1.3 true false analysis-collector 1.43 true false analysis-core 1.72 true false ant 1.2 true false antisamy-markup-formatter 1.3 true true artifactdeployer 0.33 true false async-http-client 1.7.8 true false build-monitor-plugin 1.6+build.149 true false build-name-setter 1.3 true false build-timeout 1.14.1 true false buildgraph-view 1.1.1 true false buildtriggerbadge 2.0 true false categorized-view 1.8 true false 0.6 true false claim 2.7 true false cloudbees-folder 4.8 true false cobertura 1.9.7 true false conditional-buildstep 1.3.3 true false config-file-provider 2.8.1 true false copyartifact 1.35.1 true false cppcheck 1.20 true false credentials 1.22 true true cvs 2.12 false true dashboard-view 2.9.4 true false doclinks 0.6 true false downstream-buildview 1.9 true false doxygen 0.16 true false email-ext 2.40.5 true false extended-read-permission 1.0 true false external-monitor-job 1.4 true false global-build-stats 1.3 true false groovy 1.25 true false javadoc 1.3 true true jenkins-jira-plugin 1.4.6.1 true false jenkins-tag-cloud-plugin 1.6 true false jenkinswalldisplay 0.6.30 true false jira 1.41 true false job-dsl 1.34 true false job-exporter 0.4 true false jobConfigHistory 2.11 true false jquery 1.11.2-0 true false junit 1.6 true true label-linked-jobs 4.0.2 true false ldap 1.11 false true log-command 1.0.1 true false log-parser 1.0.8 true false mailer 1.15 true true managed-scripts 1.2.1 true false mapdb-api 1.0.6.0 true false mashup-portlets-plugin 1.0.5 true false matrix-auth 1.2 true true matrix-project 1.5 true true maven-plugin 2.10 true true multi-slave-config-plugin 1.2.0 true false naginator 1.15 true false nested-view 1.14 true false node-iterator-api 1.5 true false nodelabelparameter 1.5.1 true false notification 1.9 true false nunit 0.17 true false p4 1.2.4 false false pam-auth 1.2 false true parameterized-trigger 2.26 true false perforce 1.3.35 true false platformlabeler 1.1
[JIRA] [fitnesse-plugin] (JENKINS-27955) Add ability to define fitnesse port as enironment variable
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27955 Re: Add ability to define fitnesse port as enironment variable Code changed in jenkins User: antoine-aumjaud Path: src/main/java/hudson/plugins/fitnesse/FitnesseBuilder.java src/main/java/hudson/plugins/fitnesse/FitnesseExecutor.java src/test/java/hudson/plugins/fitnesse/FitnesseBuilderTest.java http://jenkins-ci.org/commit/fitnesse-plugin/a0bedbc137c62d3458ca4215ed6644231af4b998 Log: JENKINS-27955 Add ability to define fitnesse port as enironment variable Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mqtt-notification-plugin] (JENKINS-29020) Test connection ignores credentials
Title: Message Title Steffen Private created an issue Jenkins / JENKINS-29020 Test connection ignores credentials Issue Type: Bug Assignee: Unassigned Components: mqtt-notification-plugin Created: 22/Jun/15 9:05 PM Priority: Minor Reporter: Steffen Private The button test connection ignores the credentials. I made a fix and created a pull request. Add Comment This message was sent by Atlassian JIRA
[JIRA] [maven-plugin] (JENKINS-29004) Build is running with wrong JDK Version
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-29004 Build is running with wrong JDK Version Maven jobs, due to their tight integration with Jenkins, absolutely cannot build with a JDK not able to run Jenkins itself. So 1.6 builds are out unless you downgrade Jenkins, or move to using freestyle jobs. This is by design. What's left is the wrong log text (there's an issue for it), and the automatic retry which may be undesirable. Change By: Daniel Beck Component/s: core Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Antoine Aumjaud commented on JENKINS-29019 Re: FitNesse 1.13 does not render properly FitNesse history Yes my bad... I have done a new version yesterday with a not stable pull request. I have not have your case, but I think it is fix in last version. Could you please check and confirm ? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Antoine Aumjaud started work on JENKINS-29019 Change By: Antoine Aumjaud Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-blocker-plugin] (JENKINS-28513) Build-Blocker-Plugin blocks on builds queued leading to deadlock
Title: Message Title Daniel Beck commented on JENKINS-28513 Re: Build-Blocker-Plugin blocks on builds queued leading to deadlock After mutating all of our build history to v1.609.1, going back to v1.596.3 removed all build history visibility. v1.608 fixes the queue system and most of build history, but we have some weird items...seems like any builds on v1.609.1 are identified as happening in year 1969, and tons of jobs claim never to have run or failed even though they have hundreds of times. https://wiki.jenkins-ci.org/display/JENKINS/JENKINS-24380+Migration Unfortunately we are currently not able to mention major changes like these in the LTS changelog, it's purely a backporting changelog. For the actual changes, you need to review the regular weekly changelog. I'll go annoy Kohsuke again about this, but don't hold your breath. Also, 1.609.1 (or rather 1.607) changed how slave configs are stored. Downgrading will probably lose those entirely. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29011) Jenkins 1.609.1 reverse migration script doesn't always work after an upgrade
Title: Message Title Daniel Beck commented on JENKINS-29011 Re: Jenkins 1.609.1 reverse migration script doesn't always work after an upgrade 'jobs' has always been the default location for build logs, 'logs' was never used for build logs. It can be customized in the global Jenkins config (first 'Advanced' button on the right) though. Only the default workspace location was moved in newly set up installs only (from '/job/foo/workspace' to 'workspace/foo'). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-29017) P4 Plugin improperly handles filenames with ampersands
Title: Message Title
A C updated an issue
Jenkins / JENKINS-29017
P4 Plugin improperly handles filenames with ampersands
Change By:
A C
AfilewithanampersandinitsnameiscausingtheP4ChangeParsertofail,sincetheampersandisbeingoutputtothechangelogXMLas-isinsteadofbeingescapedwith{code:java}amp;{code}.PotentiallyactuatedbyallcharacterswhichmustbeescapedinXML.Thisisinthe'depot'fieldofa'file'tag.Hereistheexceptionstack:{code:java}Causedby:org.xml.sax.SAXParseException;systemId:file:[redacted]/builds/286/changelog8.xml;lineNumber:2133;columnNumber:133;Theentitynamemustimmediatelyfollowthe''intheentityreference. atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(UnknownSource) atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLScanner.scanAttributeValue(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XMLParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(UnknownSource) atjavax.xml.parsers.SAXParser.parse(UnknownSource) *{color:red} atorg.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:46) {color}* atorg.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:546) atorg.jenkinsci.plugins.workflow.job.WorkflowRun.access$1100(WorkflowRun.java:99) atorg.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:707) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:70) atorg.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) atorg.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:136) atorg.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:98) atorg.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) atorg.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
[JIRA] [p4-plugin] (JENKINS-29017) P4 Plugin improperly handles filenames with ampersands
Title: Message Title
A C updated an issue
Jenkins / JENKINS-29017
P4 Plugin improperly handles filenames with ampersands
Change By:
A C
AfilewithanampersandinitsnameiscausingtheP4ChangeParsertofail,sincetheampersandisbeingoutputtothechangelogXMLas-isinsteadofbeingescapedwith { noformat code:java }amp;{ noformat code } .PotentiallyactuatedbyallcharacterswhichmustbeescapedinXML.Thisisinthe'depot'fieldofa'file'tag.Hereistheexceptionstack: { { code:java} Causedby:org.xml.sax.SAXParseException;systemId:file:[redacted]/builds/286/changelog8.xml;lineNumber:2133;columnNumber:133;Theentitynamemustimmediatelyfollowthe''intheentityreference. atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(UnknownSource) atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLScanner.scanAttributeValue(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XMLParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(UnknownSource) atjavax.xml.parsers.SAXParser.parse(UnknownSource) atorg.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:46) atorg.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:546) atorg.jenkinsci.plugins.workflow.job.WorkflowRun.access$1100(WorkflowRun.java:99) atorg.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:707) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:70) atorg.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) atorg.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:136) atorg.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:98) atorg.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45) atorg.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:42)
[JIRA] [p4-plugin] (JENKINS-29017) P4 Plugin improperly handles filenames with ampersands
Title: Message Title A C updated an issue Jenkins / JENKINS-29017 P4 Plugin improperly handles filenames with ampersands Change By: A C Environment: Jenkins1.6. 16 17 P41.2.4Workflow1.8 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-29022) Using configure block for scm results in extraneous NullSCM entry
Title: Message Title
A C created an issue
Jenkins / JENKINS-29022
Using configure block for scm results in extraneous NullSCM entry
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
22/Jun/15 11:12 PM
Priority:
Minor
Reporter:
A C
The following configure block:
def p4ConfigureCoordinator( ) {
{ project -
project / scm( class: 'org.jenkinsci.plugins.p4.PerforceScm' ) {
}
}
}
freeStyleJob('scratch-dsl') {
configure p4ConfigureCoordinator()
}
Results in a job config.xml with both:
scm class=hudson.scm.NullSCM/
scm class=org.jenkinsci.plugins.p4.PerforceScm/
Prioritizing as Minor since this does not appear to have any negative consequences functionally.
[JIRA] [p4-plugin] (JENKINS-29017) P4 Plugin improperly handles filenames with ampersands
Title: Message Title
A C updated an issue
Jenkins / JENKINS-29017
P4 Plugin improperly handles filenames with ampersands
Change By:
A C
AfilewithanampersandinitsnameiscausingtheP4ChangeParsertofail,sincetheampersandisbeingoutputtothechangelogXMLas-isinsteadofbeingescapedwith{code:java}amp;{code} . PotentiallyactuatedbyallcharacterswhichmustbeescapedinXML.Thisisinthe'depot'fieldofa'file'tag. Crashishere:{code:java} atorg.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:46){code} Hereistheexceptionstack:{code:java}Causedby:org.xml.sax.SAXParseException;systemId:file:[redacted]/builds/286/changelog8.xml;lineNumber:2133;columnNumber:133;Theentitynamemustimmediatelyfollowthe''intheentityreference. atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(UnknownSource) atcom.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLScanner.scanAttributeValue(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanAttribute(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanStartElement(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(UnknownSource) atcom.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.XMLParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(UnknownSource) atcom.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(UnknownSource) atjavax.xml.parsers.SAXParser.parse(UnknownSource) *{color:red} atorg.jenkinsci.plugins.p4.changes.P4ChangeParser.parse(P4ChangeParser.java:46) {color}* atorg.jenkinsci.plugins.workflow.job.WorkflowRun.onCheckout(WorkflowRun.java:546) atorg.jenkinsci.plugins.workflow.job.WorkflowRun.access$1100(WorkflowRun.java:99) atorg.jenkinsci.plugins.workflow.job.WorkflowRun$SCMListenerImpl.onCheckout(WorkflowRun.java:707) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80) atorg.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:70) atorg.jenkinsci.plugins.workflow.steps.AbstractSynchronousStepExecution.start(AbstractSynchronousStepExecution.java:34) atorg.jenkinsci.plugins.workflow.cps.DSL.invokeMethod(DSL.java:136) atorg.jenkinsci.plugins.workflow.cps.CpsScript.invokeMethod(CpsScript.java:98) atorg.codehaus.groovy.runtime.callsite.PogoMetaClassSite.call(PogoMetaClassSite.java:45)
[JIRA] [hp-application-automation-tools-plugin] (JENKINS-16464) Could not create scheduler
Title: Message Title Vijay Kumar commented on JENKINS-16464 Re: Could not create scheduler Hi All, i installed the HP ALM Client Registration plug-in IE with administrator rights and able to trigger the HP ALM test scripts from Jenkins. Regards, Vijay Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-publisher-plugin] (JENKINS-29009) Do not atampt to send jobs that does not exist
Title: Message Title Oliver Gondža created an issue Jenkins / JENKINS-29009 Do not atampt to send jobs that does not exist Issue Type: Bug Assignee: vjuranek Components: build-publisher-plugin Created: 22/Jun/15 10:26 AM Priority: Minor Reporter: Oliver Gondža In case of IOException it should be rechecked if job still exists and item removed from queue it if does not. The plugin does not seem to do that proactively when run/project is deleted. Waiting for a time out before a retry, after encountering an error while sending JOB_NAME #34 (5 min 35 sec before retry): hudson.plugins.build_publisher.ServerFailureException: java.io.FileNotFoundException: /jenkins/jobs/JOB_NAME/config.xml (No such file or directory) at hudson.plugins.build_publisher.HTTPBuildTransmitter.followRedirects(HTTPBuildTransmitter.java:193) at hudson.plugins.build_publisher.HTTPBuildTransmitter.executeMethod(HTTPBuildTransmitter.java:158) at hudson.plugins.build_publisher.PublisherThread.executeMethod(PublisherThread.java:306) at hudson.plugins.build_publisher.PublisherThread.submitConfig(PublisherThread.java:273) at hudson.plugins.build_publisher.PublisherThread.createOrSynchronize(PublisherThread.java:266) at hudson.plugins.build_publisher.PublisherThread.synchronizeProjectSettings(PublisherThread.java:220) at hudson.plugins.build_publisher.PublisherThread.run(PublisherThread.java:113) Caused by: java.io.FileNotFoundException: /jenkins/jobs/JOB_NAME/config.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at
[JIRA] [core] (JENKINS-27436) 'Check Now' function seems to have no effect
Title: Message Title dogfood commented on JENKINS-27436 Re: 'Check Now' function seems to have no effect Integrated in jenkins_main_trunk #4193 JENKINS-27436 Fix button link appearance (Revision 17fb4a4ffb41b44ff54a0233afeb64ee3a34469f) Result = SUCCESS ogondza : 17fb4a4ffb41b44ff54a0233afeb64ee3a34469f Files : war/src/main/webapp/css/style.css Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-23485) TokenMacro for getting a version value stored in environment variable
Title: Message Title
Lars Strojny updated an issue
Jenkins / JENKINS-23485
TokenMacro for getting a version value stored in environment variable
Change By:
Lars Strojny
TokenMacroforgettingaversionvaluestoredinenvironmentvariable.Asaparameteritispossibletoremove-SNAPSHOTfromtheversion.Example: {code} ${ENV_VERSION,var=POM_VERSION,stripSnapshot=true}${ENV_VERSION,var=POM_VERSION} {code}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Title: Message Title Sorin Sbarnea updated an issue Jenkins / JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm Change By: Sorin Sbarnea Environment: TheJenkinsserveris jenkins- 1.534onUbuntuwithActiveDirectoryplugin1.33,configuredwithjustthedomain(nobindDNorpassword). jenkins-1617too Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-6217) Links to fitnesse test results are not valid
Title: Message Title Antoine Aumjaud closed an issue as Fixed fixed in last version Jenkins / JENKINS-6217 Links to fitnesse test results are not valid Change By: Antoine Aumjaud Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-24930) Use alternating row colors in history table
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-24930 Use alternating row colors in history table Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-9287) Configuration is not saven when two git repositories are added
Title: Message Title Nimi Sukumaran commented on JENKINS-9287 Re: Configuration is not saven when two git repositories are added Is this issue resolved? I am getting the same error with TFS multipple SCM option. The configurations are getting wiped out . My Jenkins version is 1.558 and multiple scm plugin version is : 0.3.. Please help me to resolve this issue.Thanks!!! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12983) Redundat syncs when using matrix jobs
Title: Message Title Charles Blessing commented on JENKINS-12983 Re: Redundat syncs when using matrix jobs Specifically for Perforce, I've managed to get some improvement by running a local Perforce proxy. This caches commonly accessed files locally. The first query pulls all of the files into the cache, and then the synch for each matrix configuration just reads the files out of the cache. Charles Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-29008) HTML publisher cannot run concurrently
Title: Message Title Dave Taddei created an issue Jenkins / JENKINS-29008 HTML publisher cannot run concurrently Issue Type: Bug Assignee: mcrooney Attachments: htmlpublisher.txt Components: htmlpublisher-plugin Created: 22/Jun/15 9:19 AM Environment: Ubuntu 12.04, amd64 Labels: jenkins plugin htmlpublisher Priority: Major Reporter: Dave Taddei The HTML publisher plugin causes problems when running concurrently with other instances of the same job. It looks like both running tasks attempt to update the front page link at the same time and cannot. Please see attached log file. I have edited some project specific names for the sake of confidentiality. We are attempting several work arounds:
[JIRA] [job-dsl-plugin] (JENKINS-29005) Jobs areremoved that had been under seed control weeks ago
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29005 Re: Jobs areremoved that had been under seed control weeks ago Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/actions/GeneratedObjectsAction.java job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ExecuteDslScriptsSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/9d9a53b3e7b6319054825af4edb78b462ebdadaf Log: fixed regression introduced in 1.33 JENKINS-29005 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-29005) Jobs areremoved that had been under seed control weeks ago
Title: Message Title Daniel Spilker resolved as Fixed Jenkins / JENKINS-29005 Jobs areremoved that had been under seed control weeks ago Change By: Daniel Spilker Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-20263) Artifact Resolver does not retrieve the latest version from central Maven Repository
Title: Message Title Robert Kleinschmager assigned an issue to Robert Kleinschmager Jenkins / JENKINS-20263 Artifact Resolver does not retrieve the latest version from central Maven Repository Change By: Robert Kleinschmager Assignee: RobertKleinschmager Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29010) Installed jenkins plugins should also be listed in 'available' section in jenkins admin
Title: Message Title Martin Hcker created an issue Jenkins / JENKINS-29010 Installed jenkins plugins should also be listed in 'available' section in jenkins admin Issue Type: Improvement Assignee: Unassigned Components: core Created: 22/Jun/15 11:22 AM Labels: jenkins configuration user-experience Priority: Minor Reporter: Martin Hcker The problem is that I just spent about an hour searching for a plugin (build timeout in my case) in the available plugins section, in the end going down to manually scanning the list believing that it may be displayed under a different name perhaps. Well, turns out that the plugin was already installed, which hides it from the available list. This should not be. I'm perfectly happy to have it marked differently, so I can see right away that it is installed - but it should at least be findable in that list. Because that plugin is most definitely available. It's also already installed, but it's definitely available. I'm also ok with a hide installed checkbox if you need that - but I don't think it's necessary. So back to the problem at hand: every package manager I know also lists installed packages when I search for a package. As far as I can see Jenkins plugin package manager
[JIRA] [core] (JENKINS-29011) Jenkins 1.609.1 reverse migration script doesn't always work after an upgrade
Title: Message Title Kevin Phillips created an issue Jenkins / JENKINS-29011 Jenkins 1.609.1 reverse migration script doesn't always work after an upgrade Issue Type: Bug Assignee: Unassigned Components: core Created: 22/Jun/15 11:39 AM Priority: Major Reporter: Kevin Phillips We recently upgraded our Jenkins LTS instance from v1.532.3 to the latest 1.609.1 version, after which we discovered some critical defects that required us to roll back to the prior version, 1.596.3. In so doing we encountered issues loading build logs and such due to the incompatible configuration changes applied by 1.609.1. We proceeded to run the downgrade script as described here to no avail. The script appeared to have completed without error but it didn't actually apply any changes to the configuration. Further ad-hoc testing seems to indicate that the underlying problem has to do with the way newer versions of Jenkins store their build logs. For example, from what I can tell, if you install 1.609.1 on a clean system it will place build logs under the ./jobs subfolder along with the job they are associated with. However in older Jenkins versions the build logs were stored under the ./logs folder, disconnected from the job configurations. The interesting bit is that when you update from the legacy versions to the latest version the build logs don't appear to get moved to the new location under ./jobs. The master appears to have some way of indicating to itself that legacy build logs existed during the upgrade and that it should continue to maintain the logs in that location instead of the new location. Everything, that is, except for this
[JIRA] [core] (JENKINS-29010) Installed jenkins plugins should also be listed in 'available' section in jenkins admin
Title: Message Title Robert Buchholz commented on JENKINS-29010 Re: Installed jenkins plugins should also be listed in 'available' section in jenkins admin Note that the search field at the top could also list plugins independent of status. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [sauce-ondemand-plugin] (JENKINS-29012) Latest sauce on demand plugin is not available from jenkins plugin manager
Title: Message Title Pasi Romo created an issue Jenkins / JENKINS-29012 Latest sauce on demand plugin is not available from jenkins plugin manager Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: sauce-ondemand-plugin Created: 22/Jun/15 12:00 PM Priority: Major Reporter: Pasi Romo Hi, the latest version 1.129 of sauce on demand plugin does not seem to be available from jenkins plugin manager even though it war released already a month ago. The latest version, which plugin manager offers is 1.128. Best regards, Pasi Romo Add Comment
[JIRA] [active-directory-plugin] (JENKINS-20064) Cannot use CLI or URL with API token with Active Directory as the access control security realm
Title: Message Title Sorin Sbarnea reopened an issue I can confirm the the issue, tried to use API_TOKEN as a password for the CLI usage and I got the error below from a jenkins instance that is configured to accept LDAP logins: org.acegisecurity.AuthenticationServiceException: Application name and/or password are not valid.; nested exception is com.atlassian.crowd.exception.InvalidAuthenticationException: Account with name svcacct_scale failed to authenticate at de.theit.jenkins.crowd.CrowdSecurityRealm.authenticate(CrowdSecurityRealm.java:394) at hudson.security.AbstractPasswordBasedSecurityRealm.doAuthenticate(AbstractPasswordBasedSecurityRealm.java:114) at hudson.security.AbstractPasswordBasedSecurityRealm.access$100(AbstractPasswordBasedSecurityRealm.java:39) at hudson.security.AbstractPasswordBasedSecurityRealm$1.authenticate(AbstractPasswordBasedSecurityRealm.java:81) at hudson.cli.CLICommand.main(CLICommand.java:231) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:326) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:301) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:260) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:325) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) at hudson.remoting.CallableDecoratorAdapter.call(CallableDecoratorAdapter.java:18) at hudson.remoting.CallableDecoratorList$1.call(CallableDecoratorList.java:21) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: com.atlassian.crowd.exception.InvalidAuthenticationException: Account with name svcacct_scale failed to authenticate at com.atlassian.crowd.exception.InvalidAuthenticationException.newInstanceWithName(InvalidAuthenticationException.java:50) at com.atlassian.crowd.integration.rest.service.RestCrowdClient.handleInvalidUserAuthentication(RestCrowdClient.java:1187) at com.atlassian.crowd.integration.rest.service.RestCrowdClient.authenticateUser(RestCrowdClient.java:128) at de.theit.jenkins.crowd.CrowdSecurityRealm.authenticate(CrowdSecurityRealm.java:376) ... 24 more Jenkins / JENKINS-20064 Cannot use CLI or URL with API token with Active Directory as the access control security realm
[JIRA] [junit-plugin] (JENKINS-27415) Junit plugin fails to parse output, all tests are marked as failed
Title: Message Title Oliver Gondža closed an issue as Duplicate Jenkins / JENKINS-27415 Junit plugin fails to parse output, all tests are marked as failed Change By: Oliver Gondža Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-27415) Junit plugin fails to parse output, all tests are marked as failed
Title: Message Title Oliver Gondža commented on JENKINS-27415 Re: Junit plugin fails to parse output, all tests are marked as failed Closing as a duplicate of JENKINS-18687. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-18687) Intermittent failure whilst recording test results caused by java.util.MissingResourceException
Title: Message Title Oliver Gondža commented on JENKINS-18687 Re: Intermittent failure whilst recording test results caused by java.util.MissingResourceException What Java version was used when this exception was thrown? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-24930) Use alternating row colors in history table
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24930 Re: Use alternating row colors in history table Code changed in jenkins User: Stefan Brausch Path: src/main/resources/hudson/plugins/jobConfigHistory/ComputerConfigHistoryAction/index.jelly src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectAction/index.jelly src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistoryRootAction/history.jelly src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistoryRootAction/index.jelly src/main/resources/hudson/plugins/jobConfigHistory/table.css http://jenkins-ci.org/commit/jobConfigHistory-plugin/7a17fa88fa50a0303c51f800835bca65eac0e50e Log: Merge pull request #46 from daniel-beck/ JENKINS-24930 [FIXED JENKINS-24930] Alternating row bg colors Compare: https://github.com/jenkinsci/jobConfigHistory-plugin/compare/fd40f6bd7a9b...7a17fa88fa50 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jobconfighistory-plugin] (JENKINS-24930) Use alternating row colors in history table
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24930 Re: Use alternating row colors in history table Code changed in jenkins User: Daniel Beck Path: src/main/resources/hudson/plugins/jobConfigHistory/ComputerConfigHistoryAction/index.jelly src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistoryProjectAction/index.jelly src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistoryRootAction/history.jelly src/main/resources/hudson/plugins/jobConfigHistory/JobConfigHistoryRootAction/index.jelly src/main/resources/hudson/plugins/jobConfigHistory/table.css http://jenkins-ci.org/commit/jobConfigHistory-plugin/66a44a8062782368d381da69aa31412662a0b474 Log: [FIXED JENKINS-24930] Alternating row bg colors Also switches to using the PNG icons so there's no ugly white background. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mantis-plugin] (JENKINS-28381) My mantis plugin does not show me any project and category
Title: Message Title rake kniven closed an issue as Not A Defect Cause by wrong formatted xml string. It has a BOM somewhere in the middle. Java SAX is not very tolerant Jenkins / JENKINS-28381 My mantis plugin does not show me any project and category Change By: rake kniven Status: Open Closed Resolution: NotADefect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mantis-plugin] (JENKINS-28381) My mantis plugin does not show me any project and category
Title: Message Title rake kniven edited a comment on JENKINS-28381 Re: My mantis plugin does not show me any project and category Ifinallyfoundthecause.OnmantiswehaveaplugincalledRemindertosendoutduedatenotifications.Assoonasthispluginisactivethetroublestarts.Trieditnowafewtimesandbehaviourisreproducible.Openendticketatmantisbt.Link:https://www.mantisbt.org/bugs/view.php?id=19848Youcanclosethisissuefrommyside. PluginloadslanguagefilewhichisUTF8withBOM.AssoonasIremoveBOMconnectionworksfine. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-12983) Redundat syncs when using matrix jobs
Title: Message Title Andy Bigos commented on JENKINS-12983 Re: Redundat syncs when using matrix jobs As the matrix functionality has now moved from the core maybe this issue should be moved to the Matrix Project plugin, or maybe to the Perforce plugin as it seems the 'fix' is most likely to be optimizations to reduce syncing in the P4 plugins itself (if possible). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-28263) Use same changeset number for all phases
Title: Message Title Thomas Fields closed an issue as Fixed Jenkins / JENKINS-28263 Use same changeset number for all phases Change By: Thomas Fields Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-28263) Use same changeset number for all phases
Title: Message Title Thomas Fields commented on JENKINS-28263 Re: Use same changeset number for all phases It was the This build is parameterized bit of the downstream job that I was missing. This works just fine now. Thanks. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [compress-artifacts-plugin] (JENKINS-28980) Properties file not read when non-default artifact manager used
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28980 Re: Properties file not read when non-default artifact manager used Code changed in jenkins User: Oliver Gondža Path: src/main/java/hudson/plugins/parameterizedtrigger/FileBuildParameters.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/ed34853248e8561ffb403a016b4764986e412742 Log: [FIXED JENKINS-28980] Do not rely on default ArtifactManager implementation Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [compress-artifacts-plugin] (JENKINS-28980) Properties file not read when non-default artifact manager used
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28980 Re: Properties file not read when non-default artifact manager used Code changed in jenkins User: Oliver Gondža Path: src/test/java/hudson/plugins/parameterizedtrigger/test/FileBuildParameterFactoryTest.java src/test/java/hudson/plugins/parameterizedtrigger/test/FileBuildTriggerConfigTest.java http://jenkins-ci.org/commit/parameterized-trigger-plugin/a31d1de1f487bb2a5bb9ee7c2dc8dcb8d6623611 Log: JENKINS-28980 Cover archived properties file Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [compress-artifacts-plugin] (JENKINS-28980) Properties file not read when non-default artifact manager used
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-28980 Properties file not read when non-default artifact manager used Change By: SCM/JIRA link daemon Status: InProgress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [slave-utilization] (JENKINS-29003) 'No file' option when run jenkins slave agent
Title: Message Title Sasha Neftin created an issue Jenkins / JENKINS-29003 'No file' option when run jenkins slave agent Issue Type: Bug Assignee: Unassigned Components: slave-utilization Created: 22/Jun/15 8:01 AM Environment: Windows Server 2012 R2, Windows 8.1, Windows 10 Priority: Major Reporter: Sasha Neftin Hello, I would like get another Jenkins server, first server work as properly for me. On second I encountered follow problem: I've try install Windows Service from Jenkins Slave Agent running on slave machine. Unfortunately, I can't see 'File' option in menu while jnlp agent is opened. Used latest 1.617 version. What is problem here? Did you heard about it? How can I work normally? Meanwhile, I have tried cumbersome work around (that finally works for me) by editing jenkins-slave.xml and directly copy jenkins-slave.exe to c:\jenkins directory and then run from cmd follow command: sc.exe create Jenkins Slave start= auto binPath=c:\jenkins\jenkins-slave.exe DisplayName=jenkinsslave-c__jenkins Thanks, Sasha
[JIRA] [sonar] (JENKINS-28790) Passwords in build console output not masked since LTS version 1.596.3
Title: Message Title Jan-Jaap Spijkerman updated an issue Jenkins / JENKINS-28790 Passwords in build console output not masked since LTS version 1.596.3 Change By: Jan-Jaap Spijkerman Whenusingversion1.596.3 and or 1.609.1ofJenkinswenoticedthatthepasswordsbySonarbuilds inthebuildlog weren'tmaskedanymorebutshowedasplaintext.AfterwedowngradedJenkinstoversion1.596.2 again thepasswordsweremaskedagain.I'vetestedseveral version versions oftheSonarQubepluginbutthatdidn'thadanyeffect,thereforitseemstobeaJenkinsrelatedissue. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-29005) Jobs areremoved that had been under seed control weeks ago
Title: Message Title Daniel Spilker created an issue Jenkins / JENKINS-29005 Jobs areremoved that had been under seed control weeks ago Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 22/Jun/15 8:47 AM Environment: Job DSL 1.33+ Priority: Minor Reporter: Daniel Spilker From https://groups.google.com/forum/#!msg/job-dsl-plugin/pPidUdUZbls/41ys10kfMfoJ: We switched from Jenkins 1.580.1 to 1.596.3, job-dsl 1.34. We use job-dsl to run a groovy script that generates many jobs and one view. Some weeks ago, we removed some jobs from the generation. Running the dsl-job removed them as expected. Later, we created manually some of these jobs again. The dsl-job seemed to know that this was out of its control and did not removed the manually created jobs. Now, after our upgrade to Jenkins 1.596.3 and new plugins, the dsl-job suddenly tries in every application to remove all things that it ever generated. Previous jobs as well as a non-existing view. I'm not sure, what is more unexpected: that the old version did not remove my manually created jobs, or that the new version does it now.
[JIRA] [tfs-plugin] (JENKINS-29006) TFS Local workfolder variable setting can't use job variables like ${VAR}
Title: Message Title
Olga Jdanov created an issue
Jenkins / JENKINS-29006
TFS Local workfolder variable setting can't use job variables like ${VAR}
Issue Type:
Improvement
Assignee:
redsolo
Components:
tfs-plugin
Created:
22/Jun/15 8:54 AM
Priority:
Major
Reporter:
Olga Jdanov
TFS Local workfolder variable setting can't use job variables like $ {VAR}
I need to build different projects, and I don't want clean workspace each time... Can you please add this functionality?
Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-29005) Jobs areremoved that had been under seed control weeks ago
Title: Message Title Daniel Spilker commented on JENKINS-29005 Re: Jobs areremoved that had been under seed control weeks ago Will be fixed in the next release: https://github.com/jenkinsci/job-dsl-plugin/pull/505 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-29005) Jobs areremoved that had been under seed control weeks ago
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29005 Re: Jobs areremoved that had been under seed control weeks ago Code changed in jenkins User: Daniel Spilker Path: job-dsl-plugin/src/main/groovy/javaposse/jobdsl/plugin/actions/GeneratedObjectsAction.java job-dsl-plugin/src/test/groovy/javaposse/jobdsl/plugin/ExecuteDslScriptsSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/3caed33fa5cda36dd63a80c0fc16900bae0e8b6d Log: Merge pull request #505 from CoreMedia/ JENKINS-29005 JENKINS-29005 fixed regression introduced in 1.33 Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/9da56d3cb526...3caed33fa5cd Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27436) 'Check Now' function seems to have no effect
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27436 Re: 'Check Now' function seems to have no effect Code changed in jenkins User: Oliver Gondža Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/17fb4a4ffb41b44ff54a0233afeb64ee3a34469f Log: JENKINS-27436 Fix button link appearance Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27436) 'Check Now' function seems to have no effect
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27436 Re: 'Check Now' function seems to have no effect Code changed in jenkins User: Oliver Gondža Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/df9588270c08926f76bd94649fef84286c14442f Log: Merge pull request #1744 from olivergondza/fix-button-link JENKINS-27436 Fix button link appearance Compare: https://github.com/jenkinsci/jenkins/compare/5fa7dc0b6c9e...df9588270c08 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [python-plugin] (JENKINS-29007) python3 support
Title: Message Title Szymon S created an issue Jenkins / JENKINS-29007 python3 support Issue Type: New Feature Assignee: Unassigned Components: python-plugin Created: 22/Jun/15 9:02 AM Priority: Minor Reporter: Szymon S It would be nice to have python3 as an option, since python2 is to be deprecated in most distributions. python3 command for linux, py -3 for windows ideally the plugin could check #! line, and/or have a dropdown to select the proper interpreter Add Comment
[JIRA] [job-dsl-plugin] (JENKINS-29005) Jobs areremoved that had been under seed control weeks ago
Title: Message Title Jrgen Bohn commented on JENKINS-29005 Re: Jobs areremoved that had been under seed control weeks ago Thanks a lot! Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-29005) Jobs areremoved that had been under seed control weeks ago
Title: Message Title Daniel Spilker commented on JENKINS-29005 Re: Jobs areremoved that had been under seed control weeks ago That's a regression introduced in Job DSL 1.33. Before 1.33, only the last but one run of the seed job was used to calculate which items have been deleted. Since 1.33, all jobs ever generated by any run in the history of the seed job are used to calculate which items have been deleted. So you can either delete the history of the seed job or downgrade to 1.32 to avoid the problem. The problem has been introduced in this commit: https://github.com/jenkinsci/job-dsl-plugin/commit/e14c45293a489880842f3a7ff6a4cd94f6620c6d Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-25120) Failed to archive artifacts: *.tar.gz NoClassDefFoundError
Title: Message Title Peter Backx commented on JENKINS-25120 Re: Failed to archive artifacts: *.tar.gz NoClassDefFoundError I've had a similar issue. It seems to be caused by a bad slave.jar installation/download. After restarting the slave, everything was back to normal. Also see: http://lists.ovirt.org/pipermail/infra/2014-October/008170.html Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-29017) P4 Plugin improperly handles filenames with ampersands
Title: Message Title
A C created an issue
Jenkins / JENKINS-29017
P4 Plugin improperly handles filenames with ampersands
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
22/Jun/15 6:08 PM
Environment:
Jenkins 1.6.16 P4 1.2.4 Workflow 1.8
Priority:
Blocker
Reporter:
A C
A file with an ampersand in its name is causing the P4ChangeParser to fail, since the ampersand is being output to the changelog XML as-is instead of being escaped with . Potentially actuated by all characters which must be escaped in XML. This is in the 'depot' field of a 'file' tag. Here is the exception stack:
{{Caused by: org.xml.sax.SAXParseException; systemId: file:[redacted]/builds/286/changelog8.xml; lineNumber: 2133; columnNumber: 133; The entity name must immediately follow the '' in the entity reference. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source) at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(Unknown Source) at
[JIRA] [parameterized-trigger-plugin] (JENKINS-28699) Password type parameterized fields get bogus auto-population of default value despite empty field on job save
Title: Message Title Gordon Pettey commented on JENKINS-28699 Re: Password type parameterized fields get bogus auto-population of default value despite empty field on job save The default value being forced is the crypt/hash of the passphrase from the first global credential (an ssh key). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [junit-plugin] (JENKINS-27415) Junit plugin fails to parse output, all tests are marked as failed
Title: Message Title Oliver Gondža commented on JENKINS-27415 Re: Junit plugin fails to parse output, all tests are marked as failed Cristian Magherusan-Stanciu, what was your java version? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-play-android-publisher-plugin] (JENKINS-25933) Credentials for the configured Google Account could not be found when registering only one Google Play credential
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25933 Re: Credentials for the configured Google Account could not be found when registering only one Google Play credential Code changed in jenkins User: Christopher Orr Path: src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/ApkUploadTask.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/CredentialsException.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/CredentialsHandler.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/GooglePlayBuilder.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/GooglePlayPublisher.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/Util.java http://jenkins-ci.org/commit/google-play-android-publisher-plugin/d22f9a0002bfd8b8daf13814d9876efe3f7c4c7b Log: JENKINS-25933 Improve errors when credentials are missing or misconfigured. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [fitnesse-plugin] (JENKINS-29019) FitNesse 1.13 does not render properly FitNesse history
Title: Message Title Serge Zukov created an issue Jenkins / JENKINS-29019 FitNesse 1.13 does not render properly FitNesse history Issue Type: Bug Assignee: Antoine Aumjaud Components: fitnesse-plugin Created: 22/Jun/15 8:03 PM Environment: Jenkins 1.617, FitNesse plugin 1.13 Priority: Major Reporter: Serge Zukov After upgrade to FitNesse plugin 1.13 (from 1.12) FitNesse History is no longer rendered as a single table. FitNesse history shows one table per each FitNesse test name without actual test value. Add Comment
[JIRA] [core] (JENKINS-25625) SECURITY-144-compat usage breaks tests due to code signing
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25625 Re: SECURITY-144-compat usage breaks tests due to code signing Code changed in jenkins User: Jesse Glick Path: pom.xml src/main/java/hudson/maven/MavenModuleSet.java src/main/java/hudson/maven/MavenModuleSetBuild.java http://jenkins-ci.org/commit/maven-plugin/c5223dea3ec253d24e76f1939501a1a80cfad348 Log: Update baseline to 1.580.1. This allows us to pick up the SECURITY-144 fix from core and thus avoid JENKINS-25625. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26860) restrict parallel runs
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-26860 restrict parallel runs Change By: SCM/JIRA link daemon Status: InProgress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29015) Error building vbp projects, 99.9% of builds are ok, just 1 project gets chopped
Title: Message Title Sebastian Segovia updated an issue Jenkins / JENKINS-29015 Error building vbp projects, 99.9% of builds are ok, just 1 project gets chopped Change By: Sebastian Segovia Labels: ANTCIVB6 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29015) Error building vbp projects, 99.9% of builds are ok, just 1 project gets chopped
Title: Message Title Sebastian Segovia updated an issue Jenkins / JENKINS-29015 Error building vbp projects, 99.9% of builds are ok, just 1 project gets chopped Change By: Sebastian Segovia Environment: Jenkinsversion1. 547 617 AntPlugin 1.2 CredentialsPlugin 1.9.3 CVSPlugin 2.11 JavadocPlugin 1.1 LDAPPlugin 1.6 Mailer 1.6 MaskPasswordsPlugin 2.7.2 MatrixAuthorizationStrategyPlugin 1.1 MavenProjectPlugin 2.1 Monitoringexternaljobs 1.2 PAMAuthenticationplugin 1.1 SSHCredentialsPlugin 1.6 SSHSlavesplugin 1.5 SubversionPlugin 1.54 TranslationAssistancePlugin 1.10 WindowsSlavesPlugin 1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [violations-plugin] (JENKINS-19260) Cannot parse codenarc xml, due to empty path attribute in element Package
Title: Message Title SCM/JIRA link daemon commented on JENKINS-19260 Re: Cannot parse codenarc xml, due to empty path attribute in element Package Code changed in jenkins User: Tomas Bjerre Path: src/main/java/hudson/plugins/violations/parse/AbstractParser.java src/main/java/hudson/plugins/violations/types/codenarc/CodenarcParser.java src/test/resources/hudson/plugins/violations/types/codenarc/CodeNarcXmlReport.xml src/test/resources/hudson/plugins/violations/types/codenarc/CodeNarcXmlReportWithSourceDirectory.xml http://jenkins-ci.org/commit/violations-plugin/34527bf81b0623ad9120ceac1b9042f06019a5bf Log: JENKINS-19260 Reformatting code before fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-play-android-publisher-plugin] (JENKINS-25933) Credentials for the configured Google Account could not be found when registering only one Google Play credential
Title: Message Title SCM/JIRA link daemon commented on JENKINS-25933 Re: Credentials for the configured Google Account could not be found when registering only one Google Play credential Code changed in jenkins User: Christopher Orr Path: src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/ApkUploadTask.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/CredentialsHandler.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/GooglePlayBuilder.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/GooglePlayPublisher.java src/main/java/org/jenkinsci/plugins/googleplayandroidpublisher/Util.java http://jenkins-ci.org/commit/google-play-android-publisher-plugin/c30a83de8cfc1540215571d8e50e06be8fdf68b2 Log: JENKINS-25933 Improve errors when credentials are missing or misconfigured. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [violations-plugin] (JENKINS-19260) Cannot parse codenarc xml, due to empty path attribute in element Package
Title: Message Title SCM/JIRA link daemon commented on JENKINS-19260 Re: Cannot parse codenarc xml, due to empty path attribute in element Package Code changed in jenkins User: Tomas Bjerre Path: src/main/java/hudson/plugins/violations/parse/AbstractParser.java src/main/java/hudson/plugins/violations/types/codenarc/CodenarcParser.java src/test/java/hudson/plugins/violations/types/codenarc/CodenarcParserHudsonTest.java src/test/resources/hudson/plugins/violations/types/codenarc/CodeNarcReportEmptyPath.xml http://jenkins-ci.org/commit/violations-plugin/f6eece31c835182039201f4fa64d02f86888c085 Log: JENKINS-19260 Allowing empty path in CodenarcParser Compare: https://github.com/jenkinsci/violations-plugin/compare/a4fe06f210fd...f6eece31c835 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [violations-plugin] (JENKINS-19260) Cannot parse codenarc xml, due to empty path attribute in element Package
Title: Message Title Tomas Bjerre resolved as Fixed Jenkins / JENKINS-19260 Cannot parse codenarc xml, due to empty path attribute in element Package Change By: Tomas Bjerre Status: Open Resolved Assignee: peterkittreilly TomasBjerre Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-29018) Store a stable unique ID for each credential
Title: Message Title Christopher Orr assigned an issue to Unassigned Jenkins / JENKINS-29018 Store a stable unique ID for each credential Change By: Christopher Orr Assignee: ChristopherOrr Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26860) restrict parallel runs
Title: Message Title SCM/JIRA link daemon commented on JENKINS-26860 Re: restrict parallel runs Code changed in jenkins User: Jesse Glick Path: CHANGES.md job/src/main/java/org/jenkinsci/plugins/workflow/job/WorkflowJob.java job/src/main/resources/org/jenkinsci/plugins/workflow/job/WorkflowJob/configure-entries.jelly http://jenkins-ci.org/commit/workflow-plugin/0d606030c249905e2c4073b8d6b471b1e199522c Log: [FIXED JENKINS-26860] WorkflowJob.concurrentBuild Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-29018) Store a stable unique ID for each credential
Title: Message Title Christopher Orr assigned an issue to Christopher Orr Jenkins / JENKINS-29018 Store a stable unique ID for each credential Change By: Christopher Orr Assignee: ChristopherOrr Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-29018) Store a stable unique ID for each credential
Title: Message Title Christopher Orr assigned an issue to Matthew Moore Jenkins / JENKINS-29018 Store a stable unique ID for each credential Change By: Christopher Orr Assignee: MatthewMoore Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-oauth-plugin] (JENKINS-29018) Store a stable unique ID for each credential
Title: Message Title Christopher Orr commented on JENKINS-29018 Re: Store a stable unique ID for each credential Note that this issue also means (according to this comment) it's not possible to create multiple Google Service Account credentials with the same project name (not that that's a great idea to start with). Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-failure-analyzer-plugin] (JENKINS-29024) Support displaying all matching captures
Title: Message Title
CyberTech created an issue
Jenkins / JENKINS-29024
Support displaying all matching captures
Issue Type:
New Feature
Assignee:
Tomas Westling
Components:
build-failure-analyzer-plugin
Created:
23/Jun/15 3:17 AM
Priority:
Minor
Reporter:
CyberTech
Currently, we can do $ {1,1}
for the first item from the first capture group $ {1,2}
for the second $ {2,1}
for the first item from the second capture group etc.
I would like to show all matches for an indication. For example a file:
foo foo bar foo
that matched on foo would give me 3 results.
Is this currently supported? I'm not even sure the plugin continues scanning for each indication once an indication has matched once.
Add Comment
[JIRA] [build-failure-analyzer-plugin] (JENKINS-29023) Propagate results from subjobs from MultiJob plugin
Title: Message Title CyberTech created an issue Jenkins / JENKINS-29023 Propagate results from subjobs from MultiJob plugin Issue Type: New Feature Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 23/Jun/15 3:13 AM Priority: Minor Reporter: CyberTech I do not believe this is currently supported, but if it is, please, someone let me know how to enable it. I'm looking to aggregate the results of the subjobs from a multi-job plugin job, for display. Add Comment
[JIRA] [pathignore-plugin] (JENKINS-12094) ruby-runtime plugin fails to initialize
Title: Message Title
Dougal McRae edited a comment on JENKINS-12094
Re: ruby-runtime plugin fails to initialize
Idon'tthinkthisisfixed.IgetthefollowingwhentryingtoinstallRubyRuntimePlugin(ruby-runtime)v0.12toJenkins v1.609.1 runningonlocalhostWindows764-bit,Jenkinsisinstalledin'C:\ProgramFiles(x86)\Jenkins'.{quote}java.io.IOException:Failedtodynamicallydeploythisplugin athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1322) athudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1121) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) athudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) atjava.lang.Thread.run(UnknownSource)Causedby:java.nio.file.FileSystemException:C:\ProgramFiles(x86)\Jenkins\plugins\ruby-runtime\WEB-INF\lib\classes.jar:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess. atsun.nio.fs.WindowsException.translateToIOException(UnknownSource) atsun.nio.fs.WindowsException.rethrowAsIOException(UnknownSource) atsun.nio.fs.WindowsException.rethrowAsIOException(UnknownSource) atsun.nio.fs.WindowsFileSystemProvider.implDelete(UnknownSource) atsun.nio.fs.AbstractFileSystemProvider.delete(UnknownSource) atjava.nio.file.Files.delete(UnknownSource) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.Util.deleteFile(Util.java:247) athudson.Util.deleteRecursive(Util.java:310) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:522) athudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:166) athudson.PluginManager.dynamicLoad(PluginManager.java:448) athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1318) ...5more{quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [pathignore-plugin] (JENKINS-12094) ruby-runtime plugin fails to initialize
Title: Message Title Dougal McRae commented on JENKINS-12094 Re: ruby-runtime plugin fails to initialize I don't think this is fixed. I get the following when trying to install Ruby Runtime Plugin (ruby-runtime) v0.12 to Jenkins running on localhost Windows 7 64-bit, Jenkins is installed in 'C:\Program Files (x86)\Jenkins'. java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1322) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1121) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Unknown Source) Caused by: java.nio.file.FileSystemException: C:\Program Files (x86)\Jenkins\plugins\ruby-runtime\WEB-INF\lib\classes.jar: The process cannot access the file because it is being used by another process. at sun.nio.fs.WindowsException.translateToIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source) at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source) at sun.nio.fs.AbstractFileSystemProvider.delete(Unknown Source) at java.nio.file.Files.delete(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at hudson.Util.deleteFile(Util.java:247) at hudson.Util.deleteRecursive(Util.java:310) at hudson.Util.deleteContentsRecursive(Util.java:212) at hudson.Util.deleteRecursive(Util.java:301) at hudson.Util.deleteContentsRecursive(Util.java:212) at hudson.Util.deleteRecursive(Util.java:301) at hudson.Util.deleteContentsRecursive(Util.java:212) at hudson.Util.deleteRecursive(Util.java:301) at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:522) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:166) at hudson.PluginManager.dynamicLoad(PluginManager.java:448) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1318) ... 5 more Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [pathignore-plugin] (JENKINS-12094) ruby-runtime plugin fails to initialize
Title: Message Title
Dougal McRae edited a comment on JENKINS-12094
Re: ruby-runtime plugin fails to initialize
Idon'tthinkthisisfixed . IgetthefollowingwhentryingtoinstallRubyRuntimePlugin(ruby-runtime)v0.12toJenkinsv1.609.1runningonlocalhostWindows764-bit,Jenkinsisinstalledin'C:\ProgramFiles(x86)\Jenkins'.{quote}java.io.IOException:Failedtodynamicallydeploythisplugin athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1322) athudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1121) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) athudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) atjava.lang.Thread.run(UnknownSource)Causedby:java.nio.file.FileSystemException:C:\ProgramFiles(x86)\Jenkins\plugins\ruby-runtime\WEB-INF\lib\classes.jar:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess. atsun.nio.fs.WindowsException.translateToIOException(UnknownSource) atsun.nio.fs.WindowsException.rethrowAsIOException(UnknownSource) atsun.nio.fs.WindowsException.rethrowAsIOException(UnknownSource) atsun.nio.fs.WindowsFileSystemProvider.implDelete(UnknownSource) atsun.nio.fs.AbstractFileSystemProvider.delete(UnknownSource) atjava.nio.file.Files.delete(UnknownSource) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.Util.deleteFile(Util.java:247) athudson.Util.deleteRecursive(Util.java:310) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:522) athudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:166) athudson.PluginManager.dynamicLoad(PluginManager.java:448) athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1318) ...5more{quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [mqtt-notification-plugin] (JENKINS-29020) Test connection ignores credentials
Title: Message Title Gareth Western started work on JENKINS-29020 Change By: Gareth Western Status: Open InProgress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mqtt-notification-plugin] (JENKINS-29020) Test connection ignores credentials
Title: Message Title Gareth Western assigned an issue to Gareth Western Jenkins / JENKINS-29020 Test connection ignores credentials Change By: Gareth Western Assignee: GarethWestern Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-29015) Error building vbp projects, 99.9% of builds are ok, just 1 project gets chopped
Title: Message Title Daniel Beck resolved as Not A Defect Hi Sebastian, this is an issue tracker, not a support site. For assistance, ask on the jenkinsci-users mailing list, or in #jenkins on Freenode. While there may be a bug involved, you don't include enough information here to investigate further. Jenkins / JENKINS-29015 Error building vbp projects, 99.9% of builds are ok, just 1 project gets chopped Change By: Daniel Beck Status: Open Resolved Resolution: NotADefect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [pathignore-plugin] (JENKINS-12094) ruby-runtime plugin fails to initialize
Title: Message Title
Dougal McRae edited a comment on JENKINS-12094
Re: ruby-runtime plugin fails to initialize
Isthisdefinitelyfixed?IgetthebelowerrorwhentryingtoinstallRubyRuntimePlugin(PluginId'ruby-runtime')v0 . 12toJenkinsv1.609.1runningatlocalhostonWindows764-bit(Jenkinsisinstalledin'C:\ProgramFiles(x86)\Jenkins').JRubyv1.7.19isinstalled(inC:\jruby-1.7.19).{quote}java.io.IOException:Failedtodynamicallydeploythisplugin athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1322) athudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1121) atjava.util.concurrent.Executors$RunnableAdapter.call(UnknownSource) atjava.util.concurrent.FutureTask.run(UnknownSource) athudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) atjava.lang.Thread.run(UnknownSource)Causedby:java.nio.file.FileSystemException:C:\ProgramFiles(x86)\Jenkins\plugins\ruby-runtime\WEB-INF\lib\classes.jar:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess. atsun.nio.fs.WindowsException.translateToIOException(UnknownSource) atsun.nio.fs.WindowsException.rethrowAsIOException(UnknownSource) atsun.nio.fs.WindowsException.rethrowAsIOException(UnknownSource) atsun.nio.fs.WindowsFileSystemProvider.implDelete(UnknownSource) atsun.nio.fs.AbstractFileSystemProvider.delete(UnknownSource) atjava.nio.file.Files.delete(UnknownSource) atsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod) atsun.reflect.NativeMethodAccessorImpl.invoke(UnknownSource) atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource) atjava.lang.reflect.Method.invoke(UnknownSource) athudson.Util.deleteFile(Util.java:247) athudson.Util.deleteRecursive(Util.java:310) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.Util.deleteContentsRecursive(Util.java:212) athudson.Util.deleteRecursive(Util.java:301) athudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:522) athudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:166) athudson.PluginManager.dynamicLoad(PluginManager.java:448) athudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1318) ...5more{quote}
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [m2release-plugin] (JENKINS-3644) Support for MAVEN_OPTS in release builds
Title: Message Title Indra Gunawan commented on JENKINS-3644 Re: Support for MAVEN_OPTS in release builds I am getting the same error. I have set the MAVEN_OPTS to the build environment section of the job via EnvInject but it is not passed to the maven release. The m2/3 type job does clean deploy with -Xms512m –Xmx2048m” MAVEN_OPTS. I am setting the MAVEN_OPTS again in Build Environment - Inject environment variables to the build process” : MAVEN_OPTS='-Xms512m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=512m’ However the maven release is still failing with OOM PermGen. I see this in the console: At revision 154784 [EnvInject] - Executing scripts and injecting environment variables after the SCM step. [EnvInject] - Injecting as environment variables the properties content MAVEN_OPTS='-Xms512m -Xmx2048m -XX:PermSize=256m -XX:MaxPermSize=512m’ … [checkout] $ /users/px-build/commonTools/java/jdk1.7.0_67/LNX-64/bin/java -Xms512m -Xmx2048m -cp /scratch/jenkins_slave_sjc-bld62-lnx/maven3-agent.jar:/users/px-build/commonTools/maven/sjc-hudson62-lnx/apache-maven-3.0.4/boot/plexus-classworlds-2.4.jar org.jvnet.hudson.maven3.agent.Maven3Main /users/px-build/commonTools/maven/sjc-hudson62-lnx/apache-maven-3.0.4 /scratch/jenkins_slave_sjc-bld62-lnx/slave.jar /scratch/jenkins_slave_sjc-bld62-lnx/maven3-interceptor.jar /scratch/jenkins_slave_sjc-bld62-lnx/maven3-interceptor-commons.jar 38360 … Executing Maven: -B -f /scratch/jenkins_slave_sjc-bld62-lnx/workspace/comp-ps_cluster_parent-PI_3_0_NIHAU/checkout/pom.xml -Dmaven.repo.local=/scratch/jenkins_slave_sjc-bld62-lnx/workspace/comp-ps_cluster_parent-PI_3_0_NIHAU/.repository -DdevelopmentVersion=3.0.29-SNAPSHOT -DreleaseVersion=3.0.28 -e -B -Prelease-profile -DgenerateReleasePoms=true release:prepare release:perform -Dresume=false -s /users/px-build/commonTools/maven/sjc-hudson62-lnx/apache-maven-3.0.4/conf/settings-rel.xml -Dmaven.test.skip=true … -Indra Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
