[JIRA] [build-flow-plugin] (JENKINS-30102) The wrong build is cancelled if it is still in queue
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30102 Re: The wrong build is cancelled if it is still in queue Code changed in jenkins User: Stefan Thomasson Path: src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy src/test/groovy/com/cloudbees/plugins/flow/AbortTest.groovy http://jenkins-ci.org/commit/build-flow-plugin/9711dc28d6caed8ed2c8c46beebc64a3ee8aba60 Log: JENKINS-30102 Cancel the correct queued build Search in Jenkins.instance.queue for the queued object that matches the future returned by scheduleBuild2. Adding unittest for cancelling queued jobs. 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-flow-plugin] (JENKINS-30102) The wrong build is cancelled if it is still in queue
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30102 Re: The wrong build is cancelled if it is still in queue Code changed in jenkins User: Damien Nozay Path: src/main/groovy/com/cloudbees/plugins/flow/JobInvocation.groovy src/test/groovy/com/cloudbees/plugins/flow/AbortTest.groovy http://jenkins-ci.org/commit/build-flow-plugin/ad7f8de266cee4ea97146d8ef99224f2c066b0df Log: Merge pull request #61 from thomaste/cancelation_correction JENKINS-30102 Cancel the correct queued build Compare: https://github.com/jenkinsci/build-flow-plugin/compare/e835b49f1b66...ad7f8de266ce 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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005
Title: Message Title Ronny Borchert updated an issue Jenkins / JENKINS-30479 TFS plugin did not support version 2005 Change By: Ronny Borchert Labels: 2005 2008 Server TFS change log notes release scm 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-30481) jobs folder should be moveable for easy backup
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-30481 jobs folder should be moveable for easy backup Issue Type: New Feature Assignee: Unassigned Components: core Created: 16/Sep/15 5:03 AM Environment: all Labels: jobs backup Priority: Major Reporter: Ronny Borchert We had the problem that our server is splitted into 3 partitions. First one is Os, Second, the installed programs, Third. the data partitiion. This means that partition three is more often backuped than the other two. To reduce the amount to backup it would be good to separated jobs folder from the jenkins home folder. When I am right the change would be in: https://github.com/jenkinsci/jenkins/blob/5e9492d1229921d0c1701d880650671fddd6cbfd/core/src/main/java/jenkins/model/Jenkins.java
[JIRA] [core] (JENKINS-30478) "(updates available)" should to supressable
Title: Message Title Ronny Borchert updated an issue Jenkins / JENKINS-30478 "(updates available)" should to supressable Change By: Ronny Borchert Labels: TFS supress suppress update updateCenter 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-30480) documentation of any change in build configuration
Title: Message Title Ronny Borchert updated an issue Jenkins / JENKINS-30480 documentation of any change in build configuration Change By: Ronny Borchert Labels: 9001 EN ISO build configuration documentation 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-30480) documentation of any change in build configuration
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-30480 documentation of any change in build configuration Issue Type: New Feature Assignee: Unassigned Components: core Created: 16/Sep/15 4:53 AM Environment: all Labels: build documentation EN ISO 9001 configuration Priority: Minor Reporter: Ronny Borchert In our case, we want to know every change. Because if you change the build config, you can not back to an older version of build configuration. This would it make easier to understand why older build are failed. This would allow to move back to an older build configuration. I am not sure, but this could also be good for a "EN ISO 9001" certification.
[JIRA] [core] (JENKINS-26775) Items reported twice via ItemGroup /api on java 8
Title: Message Title
Oliver Gondža commented on JENKINS-26775
Re: Items reported twice via ItemGroup /api on java 8
It seems that javac in case of:
public interface ItemGroup extends PersistenceRoot, ModelObject {
Collection getItems();
...
}
@ExportedBean
public class Jenkins extends AbstractCIBase implements DirectlyModifiableTopLevelItemGroup, StaplerProxy, StaplerFallback, ModifiableViewGroup, AccessControlled, DescriptorByNameOwner, ModelObjectWithContextMenu, ModelObjectWithChildren {
@Exported(name="jobs")
public List getItems() {
...
generates synthetic bridge method that has all annotation copied since [1], hence causing the bug. We should either skip m.isSynthetic() && m.isBridge() (we should not need methods generated by @WithBridgeMethods) or pick only one method/field per exported name (assuming synthetic bridge method will do as well as the original for API generation).
[1] http://bugs.java.com/view_bug.do?bug_id=6695379
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-29543) "if: Expression Syntax" Error During Build Step w/ C Shell Script
Title: Message Title Daniel Beck resolved as Cannot Reproduce The issue tracker isn't the correct venue for getting that kind of help. Since it appears to have resolved itself, any further investigation is basically impossible. Jenkins / JENKINS-29543 "if: _expression_ Syntax" Error During Build Step w/ C Shell Script Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce 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] [tfs-plugin] (JENKINS-30479) TFS plugin did not support version 2005
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-30479 TFS plugin did not support version 2005 Issue Type: Improvement Assignee: redsolo Components: tfs-plugin Created: 16/Sep/15 4:47 AM Environment: environments with TFS 2005 Labels: TFS Server 2005 2008 release notes change log Priority: Minor Reporter: Ronny Borchert Since version 4.0.0 is the TFS plugin not supporting TFS Server 2005 (and probably TFS Server 2008) anymore. It would be nice to say the drop of support in changelog on website https://wiki.jenkins-ci.org/display/JENKINS/Team+Foundation+Server+Plugin Also would it be good, to have support for it in the current plugin, to get improvments. This could be done by separate the logics into new and old TFS implementation.
[JIRA] [core] (JENKINS-30478) "(updates available)" should to supressable
Title: Message Title Ronny Borchert created an issue Jenkins / JENKINS-30478 "(updates available)" should to supressable Issue Type: Improvement Assignee: Unassigned Components: core Created: 16/Sep/15 4:41 AM Environment: all Labels: supress update TFS updateCenter Priority: Minor Reporter: Ronny Borchert In case Jenkins find an update, you will get on "Manage Jenkins" overview a red text "(updates available)". In our case is since last TFS plugin update the case, which did not support our TFS Server 2005 anymore. This means for me we see all the time the red hint text. I wanna suppress this red update help for this TFS plugin. It should be enough to suppress only the version which was found by last plugin list update, this means in case the TFS plugin get an update you have to declare it again. Because maybe is in future a workaround for it there.
[JIRA] [git-plugin] (JENKINS-30475) bad design for Polling vs Checkout algorithms
Title: Message Title Mark Waite closed an issue as Duplicate Duplicate of JENKINS-30474 Jenkins / JENKINS-30475 bad design for Polling vs Checkout algorithms Change By: Mark Waite 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] [core] (JENKINS-30477) When using custom workspaces determined by parameters, delete workspace does not delete the directory to be used in this build
Title: Message Title
Tim Hargreaves updated an issue
Jenkins / JENKINS-30477
When using custom workspaces determined by parameters, delete workspace does not delete the directory to be used in this build
Change By:
Tim Hargreaves
I have a job setup that sets a custom workspace, the name of which is dependent on job parameters:Use custom workspace: bq. /jenkins/slave/workspace/${JOB_NAME}_${DEPOT}_${PLATFORM}where {{DEPOT}} and {{PLATFORM}} are choice parameters.This job is often run twice in succession, once for one value of {{PLATFORM}} and right after for another value.When the job is run and the "{{Delete workspace before build starts}}" box is checked, it deletes the workspace from the previous iteration of the job, rather than the previous iteration of the job that had the same parameters.Example:if the job is being run with a workspace of:{{/jenkins/slave/workspace/My_Job_dev_ios}}instead of deleting that directory so it's fresh for that iteration, it deletes{{/jenkins/slave/workspace/My_Job_dev_android}}as that's what the previous build had as parameters.
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-30477) When using custom workspaces determined by parameters, delete workspace does not delete the directory to be used in this build
Title: Message Title
Tim Hargreaves updated an issue
Jenkins / JENKINS-30477
When using custom workspaces determined by parameters, delete workspace does not delete the directory to be used in this build
Change By:
Tim Hargreaves
I have a job setup that sets a custom workspace, the name of which is dependent on job parameters: bq. Use custom workspace: bq. /jenkins/slave/workspace/${JOB_NAME}_${DEPOT}_${PLATFORM}where {{DEPOT}} and {{PLATFORM}} are choice parameters.This job is often run twice in succession, once for one value of {{PLATFORM}} and right after for another value.When the job is run and the "{{Delete workspace before build starts}}" box is checked, it deletes the workspace from the previous iteration of the job, rather than the previous iteration of the job that had the same parameters.Example:if the job is being run with a workspace of:{{/jenkins/slave/workspace/My_Job_dev_ios}}instead of deleting that directory so it's fresh for that iteration, it deletes{{/jenkins/slave/workspace/My_Job_dev_android}}as that's what the previous build had as parameters.
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-30477) When using custom workspaces determined by parameters, delete workspace does not delete the directory to be used in this build
Title: Message Title
Tim Hargreaves updated an issue
Jenkins / JENKINS-30477
When using custom workspaces determined by parameters, delete workspace does not delete the directory to be used in this build
Change By:
Tim Hargreaves
I have a job setup that sets a custom workspace, the name of which is dependent on job parameters: {{ Use custom workspace:/jenkins/slave/workspace/${JOB_NAME}_${DEPOT}_${PLATFORM} }} where {{DEPOT}} and {{PLATFORM}} are choice parameters.This job is often run twice in succession, once for one value of {{PLATFORM}} and right after for another value.When the job is run and the "{{Delete workspace before build starts}}" box is checked, it deletes the workspace from the previous iteration of the job, rather than the previous iteration of the job that had the same parameters.Example:if the job is being run with a workspace of:{{/jenkins/slave/workspace/My_Job_dev_ios}}instead of deleting that directory so it's fresh for that iteration, it deletes{{/jenkins/slave/workspace/My_Job_dev_android}}as that's what the previous build had as parameters.
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-30477) When using custom workspaces determined by parameters, delete workspace does not delete the directory to be used in this build
Title: Message Title
Tim Hargreaves created an issue
Jenkins / JENKINS-30477
When using custom workspaces determined by parameters, delete workspace does not delete the directory to be used in this build
Issue Type:
Bug
Assignee:
Unassigned
Components:
core
Created:
16/Sep/15 1:11 AM
Environment:
Server: 3.2.63-2+deb7u1 x86_64 Slave: OS X Yosemite Jenkins LTS 1.596.1 Running directly Installed via deb SSH slave connections Chrome, 45.0.2454.85 m
Priority:
Minor
Reporter:
Tim Hargreaves
I have a job setup that sets a custom workspace, the name of which is dependent on job parameters: {{Use custom workspace: /jenkins/slave/workspace/$ {JOB_NAME}
_$ {DEPOT}
_$ {PLATFORM}
}}
where DEPOT and PLATFORM are choice parameters.
This job is often run twice in succession, once for one value of PLATFORM and right after for another value.
When the job is run and the "Delete workspace before build starts" box is checked, it deletes the workspace from the previous iteration of the job, rather than the previous iteration of the job that had the same parameters.
[JIRA] [managed-scripts-plugin] (JENKINS-30476) Bad link in config element for managed-scripts plugin when jenkins in subdir
Title: Message Title Nathan Neulinger created an issue Jenkins / JENKINS-30476 Bad link in config element for managed-scripts plugin when jenkins in subdir Issue Type: Bug Assignee: Dominik Bartholdi Components: managed-scripts-plugin Created: 16/Sep/15 12:08 AM Priority: Minor Reporter: Nathan Neulinger If you have jenkins hosted at /jenkins, the managed scripts plugin generates a link to "/configfiles" in it's error message if you don't have any defined instead of to "/jenkins/configfiles". Add Comment
[JIRA] [git-plugin] (JENKINS-30475) bad design for Polling vs Checkout algorithms
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-30475 bad design for Polling vs Checkout algorithms Change By: Kanstantsin Shautsou After long time of debugging i found that current polling algorithm works in the next way:Polling:# Get from remote repo branchnames + sha1# compare with existed BuilData from latest build (ONE logic)# If sha1/branch not found -> trigger build (NO RPA attached)Checkout:# Build is running and it calls checkout() step in GITScm# checkout() calls getBuildRevision that calls DefaultBuildChooser that calls getAdvancedCandidateRevisions() that calls revs = GitUtils.filterTipBranches(revs); (SECOND logic)# filter tips removes all intermediate branches and they never appears in BuildDataThat ends in situations that Polling needs branches, but checkout didn't build them.I fixed this issue by commenting tips filtering https://github.com/KostyaSha/git-plugin/commit/8336202ee5ec8d5a12caa875aeba27b89ac3af58 this allowed build all branches and Polling now satisfied.Suggestion:# Put RPA as polling result for triggered build as polling result -> allows ensure that BuildData will get what polling wants# Use the same logic for checkout and polling -> more or less allows hope that checkout will pick what polling mean 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 mor
[JIRA] [git-plugin] (JENKINS-30475) bad design for Polling vs Checkout algorithms
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-30475 bad design for Polling vs Checkout algorithms Change By: Kanstantsin Shautsou After long time of debugging i found that current polling algorithm works in the next way: Polling: # Get from remote repo branchnames + sha1# compare with existed BuilData from latest build (ONE logic)# If sha1/branch not found -> trigger build (NO RPA attached) Checkout: # Build is running and it calls checkout() step in GITScm# checkout() calls getBuildRevision that calls DefaultBuildChooser that calls getAdvancedCandidateRevisions() that calls revs = GitUtils.filterTipBranches(revs); (SECOND logic)# filter tips removes all intermediate branches and they never appears in BuildDataThat ends in situations that Polling needs branches, but checkout didn't build them.I fixed this issue by commenting tips filtering https://github.com/KostyaSha/git-plugin/commit/8336202ee5ec8d5a12caa875aeba27b89ac3af58 this allowed build all branches and Polling now satisfied.Suggestion:# Put RPA as polling result for triggered build -> allows ensure that BuildData will get what polling wants# Use the same logic for checkout and polling -> more or less allows hope that checkout will pick what polling mean 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 h
[JIRA] [git-plugin] (JENKINS-30475) bad design for Polling vs Checkout algorithms
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-30475 bad design for Polling vs Checkout algorithms Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 15/Sep/15 11:31 PM Environment: 2.4.0/1.18.0 1.609.3 Priority: Blocker Reporter: Kanstantsin Shautsou After long time of debugging i found that current polling algorithm works in the next way: Get from remote repo branchnames + sha1 compare with existed BuilData in latest build (ONE logic) If sha1/branch not found -> trigger build (NO RPA attached) Build is running and it calls checkout() step in GITScm
[JIRA] [git-plugin] (JENKINS-30475) bad design for Polling vs Checkout algorithms
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-30475 bad design for Polling vs Checkout algorithms Change By: Kanstantsin Shautsou After long time of debugging i found that current polling algorithm works in the next way:# Get from remote repo branchnames + sha1# compare with existed BuilData in from latest build (ONE logic)# If sha1/branch not found -> trigger build (NO RPA attached)# Build is running and it calls checkout() step in GITScm# checkout() calls getBuildRevision that calls DefaultBuildChooser that calls getAdvancedCandidateRevisions() that calls revs = GitUtils.filterTipBranches(revs); (SECOND logic)# filter tips removes all intermediate branches and they never appears in BuildDataThat ends in situations that Polling needs branches, but checkout didn't build them.I fixed this issue by commenting tips filtering https://github.com/KostyaSha/git-plugin/commit/8336202ee5ec8d5a12caa875aeba27b89ac3af58 this allowed build all branches and Polling now satisfied.Suggestion:# Put RPA as polling result for triggered build -> allows ensure that BuildData will get what polling wants# Use the same logic for checkout and polling -> more or less allows hope that checkout will pick what polling mean 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.g
[JIRA] [git-plugin] (JENKINS-30474) bad design for Polling vs Checkout algorithms
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-30474 bad design for Polling vs Checkout algorithms Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 15/Sep/15 11:29 PM Environment: 2.4.0/1.18.0 1.609.3 Priority: Blocker Reporter: Kanstantsin Shautsou After long time of debugging i found that current polling algorithm works in the next way: Get from remote repo branchnames + sha1 compare with existed BuilData in latest build (ONE logic) If sha1/branch not found -> trigger build (NO RPA attached) Build is running and it calls checkout() step in GITScm
[JIRA] [thinBackup] (JENKINS-30472) Testing Backup Created by ThinBackup Fails.
Title: Message Title Cal Barkman commented on JENKINS-30472 Re: Testing Backup Created by ThinBackup Fails. For reference here is a list of all the plugins I have installed. Active Directory plugin This plugin enables authentication through Active Directory on Windows environment. 1.41 Ant Plugin This plugin adds Apache Ant support to Jenkins. 1.2 Build Pipeline Plugin This plugin renders upstream and downstream connected jobs that typically form a build pipeline. In addition, it offers the ability to define manual triggers for jobs that require intervention prior to execution, e.g. an approval process outside of Jenkins. 1.4.8 build timeout plugin This plugin allows builds to be automatically terminated after the specified amount of time has elapsed. 1.15 ChuckNorris Plugin ChuckNorris plugin displays a picture of Chuck Norris (instead of Jenkins the butler) and a random Chuck Norris 'The Programmer' fact on each build page. 0.5 ClearCase Plug-in This plugin makes it possible to retrieve files from a ClearCase SCM using a configspec. 1.6 Credentials Plugin This plugin allows you to store credentials in Jenkins. 1.23 CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.12 Email Extension Plugin This plugin is a replacement for Jenkins's email publisher 2.40.5 Environment Injector Plugin This plugin makes it possible to set an environment for the builds. 1.92.1 External Monitor Job Type Plugin Adds the ability to monitor the result of externally executed jobs. 1.4 Filesystem Trigger Plug-in The plug-in makes it possible to monitor changes of a file or a set of files in a folder. 0.39 Groovy This plugin executes Groovy code. 1.27 Groovy Postbuild Groovy postbuild task. 2.2.1 Hudson global-build-stats plugin This plugin will allow you to manage global hudson build stats concerning build failures 1.3 Javadoc Plugin This plugin adds Javadoc support to Jenkins. 1.3 Job Configuration History Plugin Job history plugin for Jenkins. 2.12 jQuery plugin This allows other plugins to use jQuery in UI. 1.11.2-0 JUnit Plugin Allows JUnit-format test results to be published. 1.9 LDAP Plugin Adds LDAP authentication to Jenkins 1.11 Mailer Plugin This plugin allows you to configure email notifications. This is a break-out of the original core based email component. 1.15 MapDB API Plugin This plugin provides a shared dependency on the MapDB library so that other plugins can co-operate when using this library. 1.0.6.0 Matrix Authorization Strategy Plugin Offers matrix-based security authorization strategies (global and per-project). 1.2 Matrix Project Plugin Multi-configuration (matrix) project type. 1.6 Maven Integration plugin Jenkins plugin for bui
[JIRA] [git-plugin] (JENKINS-30473) polling fails when cloud slaves shutdowns fast
Title: Message Title Kanstantsin Shautsou resolved as Not A Defect Jenkins / JENKINS-30473 polling fails when cloud slaves shutdowns fast Change By: Kanstantsin Shautsou Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30473) polling fails when cloud slaves shutdowns fast
Title: Message Title Kanstantsin Shautsou commented on JENKINS-30473 Re: polling fails when cloud slaves shutdowns fast Caused by randomly changing configuration in BranchSpec. Without my changes it replaced "blank" with "**" that is #JENKINS-30345 Closing this issue as it obviously failed with closed channel because git scm configuration required WS. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-30473) polling fails when cloud slaves shutdowns fast
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-30473 polling fails when cloud slaves shutdowns fast Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 15/Sep/15 11:04 PM Environment: 2.4.0/1.18.0 1.609.3 Priority: Minor Reporter: Kanstantsin Shautsou When no WS required polling is run as usually, but when build is going it tries poll using this build that ends in stacktrace? Started on Sep 16, 2015 1:51:41 AM Polling SCM changes on docker-5f823700b921 Using strategy: Default [poll] Last Built Revision: Revision 653b08cf73531b28015ff601b1e292236ed3b898 (origin/branch) FATAL: remote file operation failed: /home/jenkins/workspace/JOB at hudson.remoting.Channel@534f2fda:docker-5f823700b921: hudson.remoting.ChannelClosedException: channel is already closed java.io.IOException: remote file operation failed: /home/jenkins/workspace/JOB at hudson.remoting.Channel@534f2fda:docker-5f823700b921: hudson.remoting.ChannelClosedException: channel is already closed at hudson.FilePath.act(FilePath.java:985) at hudson.FilePath.act(FilePath.java:967) at org.jenkinsci.plugins.gitclient.Git.getClient(Git.java:131) at hudson.plugins.git.GitSCM.createClient(GitSCM.java:705) at hudson.plugins.git.GitSCM.comp
[JIRA] [subversion-plugin] (JENKINS-17228) Fail build when subversion workspace is locked
Title: Message Title Frank Hickman commented on JENKINS-17228 Re: Fail build when subversion workspace is locked I would dearly love an option to fail the build, instead of automatically checking out a fresh workspace. Let me explain the use case, which has nothing to do with shared workspaces: We've got a CI job that runs for our huge game development project. Because of all the large binary assets involved, checking out a fresh workspace (from a remove SVN repository) can take about 6 hours. Our ISP is not great either, so frequently a long SVN operation may fail due to some network error. At present, every time that happens, the next run of the job decides that 'Workspace appear to be locked, so getting a fresh workspace'. This means we have to wait another 6 hours for the job to finish. We'd much rather have the option to fail the build, and attend to the SVN working copy manually. Thank you! 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] [thinBackup] (JENKINS-30472) Testing Backup Created by ThinBackup Fails.
Title: Message Title Cal Barkman assigned an issue to Unassigned Jenkins / JENKINS-30472 Testing Backup Created by ThinBackup Fails. Change By: Cal Barkman Assignee: Cal Barkman 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] [thinBackup] (JENKINS-30472) Testing Backup Created by ThinBackup Fails.
Title: Message Title Cal Barkman created an issue Jenkins / JENKINS-30472 Testing Backup Created by ThinBackup Fails. Issue Type: Bug Assignee: Cal Barkman Attachments: BackupPluginsVSWorkingPlugins.PNG, JenkinsError.PNG, ThinBackupConfiguration.PNG Components: thinBackup Created: 15/Sep/15 10:44 PM Environment: Jenkins version: 1.628 ThinBackup version: 1.7.4 Windows 7 Enterprise Labels: plugin jenkins windows exception Priority: Minor Reporter: Cal Barkman I am currently working on backing up our Jenkins system. The ThinBackup plugin seemed perfect as it allows us to do weekly backups. To ensure that the backups are working correctly I am attempting to test a recently created backup. I am doing this by assigning an environment v
[JIRA] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title Kanstantsin Shautsou commented on JENKINS-30200 Re: Nullpointer exception while connecting to a docker container Tom Canova please provide full log, also to what ip and port is it trying connect and what is the right ip/port of running container (login into docker host and docker inspect appeared containerId)? 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] [docker-plugin] (JENKINS-30200) Nullpointer exception while connecting to a docker container
Title: Message Title
Tom Canova commented on JENKINS-30200
Re: Nullpointer exception while connecting to a docker container
we are also running into an issue with jenkins connecting to a remote docker which is on docker version 1.8.1, api 1.20 {{Will provision 'evarga/jenkins-slave', for label: 'evarga', in cloud: 'dockerac3'
Sep 15, 2015 4:56:13 PM WARNING com.nirima.jenkins.plugins.docker.DockerCloud provision
Bad template 'evarga/jenkins-slave' in cloud 'dockerac3': 'shaded.org.apache.http.conn.ConnectTimeoutException: Connect to }}
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-30139) OldDataMonitor makes Jenkins single threaded for all saves.
Title: Message Title Daniel Beck commented on JENKINS-30139 Re: OldDataMonitor makes Jenkins single threaded for all saves. stephenconnolly It's going into 1.625.1. Time to test its RC (tomorrow) or 1.629+ for any old data monitor problems, since this isn't soaked at all. 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-30139) OldDataMonitor makes Jenkins single threaded for all saves.
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-30139 OldDataMonitor makes Jenkins single threaded for all saves. Change By: Daniel Beck Labels: lts 1.625.1 - candidate 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Jesse Glick commented on JENKINS-10860 Re: Unable to determine Maven version Yes… 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Ben Fallah commented on JENKINS-10860 Re: Unable to determine Maven version u mean, get the snapshot build@ https://jenkins.ci.cloudbees.com/job/plugins/job/artifactory-plugin/58/org.jenkins-ci.plugins$artifactory/artifact/org.jenkins-ci.plugins/artifactory/2.3.2-SNAPSHOT/artifactory-2.3.2-SNAPSHOT.hpi and load the plugin and restart ? 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-choices-plugin] (JENKINS-28617) Implement a pre-parameter Groovy script for totally dynamic parameters
Title: Message Title Bruno P. Kinoshita commented on JENKINS-28617 Re: Implement a pre-parameter Groovy script for totally dynamic parameters Hi @cristalp! Thanks for updating the issue, and for closing it off. Feel free to send any suggestions, issues, questions and comments to the mailing list. I'm currently on a development cycle for BioUno and Jenkins, working on the image-gallery-plugin, but will eventually come back to active-choices-plugin and will try to fix as many issues as possible. Bruno 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Jesse Glick commented on JENKINS-10860 Re: Unable to determine Maven version Download the file I linked to, go to http://jenkins/pluginManager/advanced, upload the file, agree to restart Jenkins. 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-30471) Manual trigger fails with jquery error
Title: Message Title Akrem A created an issue Jenkins / JENKINS-30471 Manual trigger fails with jquery error Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 15/Sep/15 8:35 PM Environment: Jenkins ver. 1.609.2 Delivery Pipeline plugin 0.9.7 Build pipeline plugin 1.4.8 Web browser: chrome Priority: Minor Reporter: Akrem A I've a downstream project setup with a manual trigger. On the delivery pipeline view, I've enabled the manual triggers so I see the button to trigger a manual downstream. The downstream job I'm trying to trigger is named "(master) - Deploy - Notification Facade Service - Qual" without the quotes When I click on the manual downstream job from the delivery pipeline view, it fails with the following _javascript_ stack on Chrome: Uncaught Error: Syntax error, unrecognized _expression_: #manual-task-(master)_ Deploy Notification_Facade_Service-_Qual0 Sizzle.error @ jquery.full.js:1491 Sizzle.tokenize @ jquery.full.js:2108 Sizzle.select @ jquery.full.js:2512 Sizzle @ jquery.full.js:888 jQuery.fn.extend.find @ jquery.full.js:2728 jQuery.fn.init @ jquery.full.js:2845 jQuery @ jquery.full.js:73 triggerManual @
[JIRA] [core] (JENKINS-26775) Items reported twice via ItemGroup /api on java 8
Title: Message Title
Oliver Gondža edited a comment on JENKINS-26775
Re: Items reported twice via ItemGroup /api on java 8
Update:- This is reproducible in OpenJDK 1.7.0_85- It seems that Model found 2 properties with following signatures:{noformat}public java.util.Collection jenkins.model.Jenkins.getItems() declared in class jenkins.model.Jenkins public java.util.List jenkins.model.Jenkins.getItems() declared in class jenkins.model.Jenkins {noformat} I dare to speculate that certain JDK version returns it as 2 different methods in case the overload specifies subtype as return type (List vs. Collection).
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-26775) Items reported twice via ItemGroup /api on java 8
Title: Message Title Oliver Gondža commented on JENKINS-26775 Re: Items reported twice via ItemGroup /api on java 8 Update: This is reproducible in OpenJDK 1.7.0_85 It seems that Model found 2 properties with following signatures: public java.util.Collection jenkins.model.Jenkins.getItems() declared in class jenkins.model.Jenkins public java.util.List jenkins.model.Jenkins.getItems() declared in class jenkins.model.Jenkins 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Ben Fallah edited a comment on JENKINS-10860 Re: Unable to determine Maven version s Is there a doc or mabye few basic steps you can share with me..so I can follow and put the temporary fix in my jenkins/maven/artifactory setup? 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Ben Fallah commented on JENKINS-10860 Re: Unable to determine Maven version s there a doc or mabye few basic steps you can share with me..so I can follow and put the temporary fix in my jenkins/maven/artifactory setup? 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Jesse Glick commented on JENKINS-10860 Re: Unable to determine Maven version I just linked to a build of my PR that should be installable using Plugin Manager » Advanced. As noted there: Arguably does not count as a full fix, since it does not address the root causes of the exceptions, but at least prevents them from breaking everything. so may be complementary to whatever was done in HAP-583 (I did not manage to find any actual patch linked from there). 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] [envinject-plugin] (JENKINS-30174) Streamline the ordering of property content and script sections in config pages
Title: Message Title Oleg Nenashev commented on JENKINS-30174 Re: Streamline the ordering of property content and script sections in config pages Manuel Jesús Recena Soto, 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] [promoted-builds-plugin] (JENKINS-30411) Add the PROMOTION_ENV token macro
Title: Message Title Oleg Nenashev closed an issue as Fixed Jenkins / JENKINS-30411 Add the PROMOTION_ENV token macro Change By: Oleg Nenashev Status: Resolved Closed 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] [websphere-deployer-plugin] (JENKINS-30250) StackOverflowError in Websphere Deployer
Title: Message Title Rusty Bentz commented on JENKINS-30250 Re: StackOverflowError in Websphere Deployer Nope, no resolution yet, though I haven't had too much time to investigate over the past 2 weeks. Please let me know if you find a solution as well. 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] [promoted-builds-plugin] (JENKINS-30212) [Promoted Builds] - Missing icons of the medium (M) size for list views
Title: Message Title Oleg Nenashev closed an issue as Fixed Jenkins / JENKINS-30212 [Promoted Builds] - Missing icons of the medium (M) size for list views Change By: Oleg Nenashev Status: Resolved Closed 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Ben Fallah commented on JENKINS-10860 Re: Unable to determine Maven version I am sorry, I don't understand your pull request that had been ignored and all the comments in there.. Is there a build somethere..or can someone can just pull the fork and modify and compile it and test it out on their own system? 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-26445) Browser freezes when clicking more link on a job to see other builds
Title: Message Title mcrooney commented on JENKINS-26445 Re: Browser freezes when clicking more link on a job to see other builds I took a quick stab and was able to improve performance 4x, and submitted a PR: https://github.com/jenkinsci/jenkins/pull/1829. I tested some overflows with and without it and all appears well, though there could be edge cases I'm missing. That said, a simple solution would also seem to be, since the button just says "More builds" to not load all builds, but just 50/100 more, and keep the button there so it can be clicked again. That's what I expected it to do anyway 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Jesse Glick commented on JENKINS-10860 Re: Unable to determine Maven version I was referring to https://github.com/jenkinsci/artifactory-plugin/pull/14 which has a snapshot build available. 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] [websphere-deployer-plugin] (JENKINS-30250) StackOverflowError in Websphere Deployer
Title: Message Title Daniel Rodriguez commented on JENKINS-30250 Re: StackOverflowError in Websphere Deployer I have the same issue, did you find a way to resolve it ? Regards 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] [promoted-builds-plugin] (JENKINS-30411) Add the PROMOTION_ENV token macro
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30411 Re: Add the PROMOTION_ENV token macro Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/hudson/plugins/promoted_builds/tokenmacro/PromotedEnvVarTokenMacro.java src/main/resources/hudson/plugins/promoted_builds/tokenmacro/help.jelly src/test/java/hudson/plugins/promoted_builds/tokenmacro/PromotedEnvVarTokenMacroTest.java http://jenkins-ci.org/commit/promoted-builds-plugin/59fa76a11661d2aa9c1be1f283505ada87661b69 Log: Merge pull request #67 from jenkinsci/ JENKINS-30411 [FIXED JENKINS-30411] - Add the PROMOTION_ENV token macro Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/2a2ea4d0be78...59fa76a11661 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-30470) User interface is really slow
Title: Message Title Christian Duchesneau updated an issue Jenkins / JENKINS-30470 User interface is really slow Change By: Christian Duchesneau Environment: Windows Server 2012Java jdk1.7.0_79Jenkins ver. 1.628 PLUGIN:irectory 1.41ansicolor 0.4.1ant 1.2antisamy-markup-formatter 1.3any-buildstep 0.1build-name-setter 1.3build-timeout 1.15build-user-vars-plugin 1.4buildresult-trigger 0.17conditional-buildstep 1.3.3copyartifact 1.36credentials 1.23cvs 2.12discard-old-build 1.05dynamicparameter 0.2.0email-ext 2.40.5envinject 1.92.1external-monitor-job 1.4fail-the-build-plugin 1.0files-found-trigger 1.4flexible-publish 0.15.2fstrigger 0.39git 2.4.0git-client 1.19.0git-server 1.6greenballs 1.14groovy 1.27groovy-label-assignment 1.1.0groovy-postbuild 2.2.1hipchat 0.1.9htmlpublisher 1.6http_request 1.8.8ivytrigger 0.34javadoc 1.3jenkins-jira-issue-updater 1.13jira 2.0JiraTestResultReporter 1.0.4jobConfigHistory 2.12jquery 1.11.2-0jsunit 1.6junit 1.9ldap 1.11log-parser 1.0.8mailer 1.15mapdb-api 1.0.6.0matrix-auth 1.2matrix-project 1.6maven-plugin 2.12nodelabelparameter 1.5.1pam-auth 1.2parameterized-trigger 2.28poll-mailbox-trigger 0.16postbuild-task 1.8postbuildscript 0.17powershell 1.2rebuild 1.25rich-text-publisher-plugin 1.3role-strategy 2.2.0run-condition 1.0scm-api 0.2script-security 1.15scriptler 2.7scripttrigger 0.31selected-tests-executor 1.3.3ssh-credentials 1.11ssh-slaves 1.10subversion 2.5.3template-project 1.5.1TestComplete 1.3text-finder 1.10thinBackup 1.7.4token-macro 1.10translation 1.12urltrigger 0.40versionnumber 1.5view-job-filters 1.27windows-slaves 1.1workflow-step-api 1.10ws-cleanup 0.28xtrigger 0.54xunit 1.97 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [core] (JENKINS-30470) User interface is really slow
Title: Message Title Christian Duchesneau created an issue Jenkins / JENKINS-30470 User interface is really slow Issue Type: Bug Assignee: Unassigned Components: core Created: 15/Sep/15 7:14 PM Environment: Windows Server 2012 Java jdk1.7.0_79 Jenkins ver. 1.628 Labels: jenkins Priority: Minor Reporter: Christian Duchesneau Sometimes my slave is really slow and I can not target the problem. I can not use the graphical interface and I need to restart my service every week. Can you help me ? My heapdump.hprof is too big to put an attachment
[JIRA] [promoted-builds-plugin] (JENKINS-30411) Add the PROMOTION_ENV token macro
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30411 Re: Add the PROMOTION_ENV token macro Code changed in jenkins User: Oleg Nenashev Path: pom.xml src/main/java/hudson/plugins/promoted_builds/tokenmacro/PromotedEnvVarTokenMacro.java src/main/resources/hudson/plugins/promoted_builds/tokenmacro/help.jelly src/test/java/hudson/plugins/promoted_builds/tokenmacro/PromotedEnvVarTokenMacroTest.java http://jenkins-ci.org/commit/promoted-builds-plugin/71dd42048d54d9984bbf6a1710d6f99729659452 Log: [FIXED JENKINS-30411] - Add the PROMOTION_ENV token macro 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Ben Fallah commented on JENKINS-10860 Re: Unable to determine Maven version I think the fix is here https://www.jfrog.com/jira/browse/HAP-583 can anyone with time please compile the fix and send me the plugin to add to jenkins and test? 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] [docker] (JENKINS-30361) Dependencies are not resolved for plugins.txt
Title: Message Title Jesse Glick commented on JENKINS-30361 Re: Dependencies are not resolved for plugins.txt From plugins.txt in a support bundle you just strip off the last field. But the support bundle also includes a complete Dockerfile. 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-30432) "Scripts not permitted to use method" in Jenkins Workflow
Title: Message Title Jesse Glick commented on JENKINS-30432 Re: "Scripts not permitted to use method" in Jenkins Workflow Well, you would either use Support Core (plugins/active.txt is almost right—just strip off /:(not-)?pinned$/), or simply look at /pluginManager/installed if there are only a few plugins relevant to the image. 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] [artifactory-plugin] (JENKINS-10860) Unable to determine Maven version
Title: Message Title Jesse Glick commented on JENKINS-10860 Re: Unable to determine Maven version Well my pull request has been ignored for most of a year now, so good luck. 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-30139) OldDataMonitor makes Jenkins single threaded for all saves.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30139 Re: OldDataMonitor makes Jenkins single threaded for all saves. Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java http://jenkins-ci.org/commit/jenkins/806f529d8fcd3f91a2fef49c63a2274c8d3f2228 Log: JENKINS-30139 Oleg wants to keep the data accessible so we have to go for immutable (cherry picked from commit e9471744338546539ed163d106763be021f278f8) Compare: https://github.com/jenkinsci/jenkins/compare/f1b47c8a007f...806f529d8fcd 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-30139) OldDataMonitor makes Jenkins single threaded for all saves.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30139 Re: OldDataMonitor makes Jenkins single threaded for all saves. Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java http://jenkins-ci.org/commit/jenkins/52b265b18688ce9142024d1bc2b3b986d9b066f9 Log: JENKINS-30139 Forgot to change this one (cherry picked from commit 67cce20291be4d4002d7e293f1e0de6ee60058f3) 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-30139) OldDataMonitor makes Jenkins single threaded for all saves.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30139 Re: OldDataMonitor makes Jenkins single threaded for all saves. Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java http://jenkins-ci.org/commit/jenkins/108f2c4b23aa0fd4fc8343a446a5de46b7ac87dc Log: JENKINS-30139 Add @Restricted to prevent external use of internal data (cherry picked from commit 9a57858a925aea1a01da9061d60e91e37d319873) 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-30139) OldDataMonitor makes Jenkins single threaded for all saves.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30139 Re: OldDataMonitor makes Jenkins single threaded for all saves. Code changed in jenkins User: Stephen Connolly Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java http://jenkins-ci.org/commit/jenkins/d68bbfcf86531f0b27cc2ba3bf0b8b8666ee4813 Log: JENKINS-30139 Switch from a big fat lock to a concurrent collection (cherry picked from commit 2c5deeb6c061a91aeac232e978756de3b1d0be98) 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] [subversion-plugin] (JENKINS-30196) SVN Exception : svn: E210004: Malformed network data
Title: Message Title João Leonardo Pereira edited a comment on JENKINS-30196 Re: SVN Exception : svn: E210004: Malformed network data same here, verified my firewall and it's ok. I can checkout from command line svn client but jenkins gives me an exception. Also, the SVN Plugin is up to date (version 2.5.3). I think it's a problem with the svn:// protocol URL instead of the "default" http://... 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-30469) expose NodeMonitoring API for cloud slaves
Title: Message Title Kanstantsin Shautsou created an issue Jenkins / JENKINS-30469 expose NodeMonitoring API for cloud slaves Issue Type: Improvement Assignee: stephenconnolly Components: core Created: 15/Sep/15 6:37 PM Priority: Minor Reporter: Kanstantsin Shautsou linking to the actual implementation description https://issues.jenkins-ci.org/browse/JENKINS-30052?focusedCommentId=236555&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-236555 Add Comment
[JIRA] [p4-plugin] (JENKINS-30425) Change information unavailable when using workflow plugin
Title: Message Title Michael Rose commented on JENKINS-30425 Re: Change information unavailable when using workflow plugin I didn't realize that the changelog is supposed to have a lot more information inside of it. The changelog I attached a couple days ago was also bad then. Any idea why this happens? Also, I could have sworn there was a toggle field to disable/enable the changelog in the Snippet Generator at one point, but I am not seeing it now. 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] [subversion-plugin] (JENKINS-30196) SVN Exception : svn: E210004: Malformed network data
Title: Message Title João Leonardo Pereira commented on JENKINS-30196 Re: SVN Exception : svn: E210004: Malformed network data same here, verified my firewall and it's ok. I can checkout from command line svn client but jenkins gives exception. SVN Plugin is up to date (version 2.5.3). I think it's a problem with the svn:// protocol URL instead of the "default" http://... 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-29235) p4jenksin not pickup latest changes
Title: Message Title Michael Rose commented on JENKINS-29235 Re: p4jenksin not pickup latest changes Both a scheduled 'Poll SCM' and a 'Build Now' build will use the latest Perforce change at the point when they are triggered (unless of course a Poll Filter or 'Pin build at Perforce Label' option is set). I have noticed that there are times when this is not true. The plugin seems to get in a weird state where it holds on to an old changelist. This just happened earlier today. Notice the "p4 changes -m" says that the latest changelist is 141219 but the changelist that it decided to sync was 140984. 00:00:00.177 ... client: jenkins-master-ndica-main 00:00:00.209 ... p4 client -o jenkins-master-ndica-main + 00:00:00.221 ... p4 counter change + 00:00:00.236 ... p4 changes -m1 //jenkins-master-ndica-main/... - 00:00:00.236 p4 changes -m1 //jenkins-master-ndica-main/... 00:00:00.236 00:00:00.243 Change 141219 on 2015/09/15 by ... 'Copying ...' 00:00:00.243 00:00:00.243 Building Parent on Node: master 00:00:00.280 ... p4 client -o jenkins-master-ndica-main + 00:00:00.363 00:00:00.363 P4 Task: establishing connection. 00:00:00.363 00:00:00.363 P4 Task: reverting all pending and shelved revisions. 00:00:00.364 ... p4 revert /jenkins/workspaces/ndica/main/... + 00:00:00.369 ... rm [abandoned files] 00:00:00.369 duration: (6ms) 00:00:00.369 00:00:00.369 P4 Task: syncing files at change: 0 00:00:00.370 ... p4 sync -f /jenkins/workspaces/ndica/main/...@0 + 00:00:00.450 duration: (81ms) 00:00:00.450 00:00:00.450 ... rm -rf /jenkins/workspaces/ndica/main 00:00:00.453 P4 Task: syncing files at change: 140984 00:00:00.454 ... p4 sync -f /jenkins/workspaces/ndica/main/...@140984 + 00:00:00.820 duration: (367ms) 00:00:00.820 00:00:00.820 P4 Task: saving built changes. 00:00:00.850 Usually when this happens, I restart Jenkins and everything goes back to working order. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [job-dsl-plugin] (JENKINS-30433) Documentation is out of sync with code
Title: Message Title Daniel Spilker resolved as Fixed Jenkins / JENKINS-30433 Documentation is out of sync with code 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] [p4-plugin] (JENKINS-30464) Separate Jobs that are not triggered by swarm are sending back pass/fail responses to swarm.
Title: Message Title Rami Alia commented on JENKINS-30464 Re: Separate Jobs that are not triggered by swarm are sending back pass/fail responses to swarm. I had this issue on 1.3.0, I just upgraded to 1.3.1 and will report if the issue persists. 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] [email-ext-plugin] (JENKINS-14755) Mail address resolution can take a significant amount of time
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-14755 Mail address resolution can take a significant amount of time Change By: Jesse Glick Labels: performance 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-24915) Extremely slow startup with template-project in combination with jobConfigHistory
Title: Message Title Brantone commented on JENKINS-24915 Re: Extremely slow startup with template-project in combination with jobConfigHistory Sadly not yet that 500ms timeout is a bit ridiculous, even with 500ms with around 1,000 jobs, that accounts for 8 minutes. That functionality on the Listener was added per https://github.com/jenkinsci/template-project-plugin/pull/5 -> https://issues.jenkins-ci.org/browse/JENKINS-16800 such that publishers behave as if they were there all along (ex: not part of template). Are you seeing this added functionality? Or even make use of it? 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-30433) Documentation is out of sync with code
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30433 Re: Documentation is out of sync with code Code changed in jenkins User: Daniel Spilker Path: README.md docs/Job-DSL-Commands.md http://jenkins-ci.org/commit/job-dsl-plugin/ba5015dd388b2a96437e8a45c30059763e76da6d Log: Merge pull request #610 from daspilker/JENKINS-30433 JENKINS-30433 Updated README Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/c25e6266ea59...ba5015dd388b 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-30464) Separate Jobs that are not triggered by swarm are sending back pass/fail responses to swarm.
Title: Message Title Michael Rose commented on JENKINS-30464 Re: Separate Jobs that are not triggered by swarm are sending back pass/fail responses to swarm. What version of p4 plugin are you using? I was seeing this occur in version 1.2.7, but have not come across this problem since upgrading to 1.3.1. 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] [schedule-build-plugin] (JENKINS-29263) Schedule builds plugin does not work with folders
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29263 Re: Schedule builds plugin does not work with folders Code changed in jenkins User: Markus Strand Path: src/main/resources/org/jenkinsci/plugins/schedulebuild/ScheduleBuildAction/index.jelly http://jenkins-ci.org/commit/schedule-build-plugin/bfceda3afd1015e3003d3d924d1b9ecf70549d38 Log: Fix to https://issues.jenkins-ci.org/browse/JENKINS-29263 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] [schedule-build-plugin] (JENKINS-29263) Schedule builds plugin does not work with folders
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29263 Re: Schedule builds plugin does not work with folders Code changed in jenkins User: anderl86 Path: src/main/resources/org/jenkinsci/plugins/schedulebuild/ScheduleBuildAction/index.jelly http://jenkins-ci.org/commit/schedule-build-plugin/d000582b465b0482692005cb9cba2c98662b7e52 Log: Merge pull request #4 from MarkusStrand/master Fix to https://issues.jenkins-ci.org/browse/JENKINS-29263 Compare: https://github.com/jenkinsci/schedule-build-plugin/compare/2d04becce8e6...d000582b465b 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] [timestamper-plugin] (JENKINS-30394) Browser hangs when opening build log with Timestamper plugin installed
Title: Message Title Jack Yerabutar commented on JENKINS-30394 Re: Browser hangs when opening build log with Timestamper plugin installed This is happening on Safari, Chrome and IE 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] [timestamper-plugin] (JENKINS-30394) Browser hangs when opening build log with Timestamper plugin installed
Title: Message Title Jack Yerabutar edited a comment on JENKINS-30394 Re: Browser hangs when opening build log with Timestamper plugin installed This is happening on Safari, Chrome and IE . 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] [zaproxy-plugin] (JENKINS-29687) From ZAP 2.4.1 an API key is added by default, which will break the API calls
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29687 Re: From ZAP 2.4.1 an API key is added by default, which will break the API calls Code changed in jenkins User: ludovicRoucoux Path: src/main/java/fr/novia/zaproxyplugin/ZAProxy.java http://jenkins-ci.org/commit/zaproxy-plugin/d882682d077d56774b0cd7bf19da868666ef9079 Log: Fix JENKINS-29687 issue 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] [zaproxy-plugin] (JENKINS-29687) From ZAP 2.4.1 an API key is added by default, which will break the API calls
Title: Message Title Ludovic Roucoux resolved as Fixed Jenkins / JENKINS-29687 From ZAP 2.4.1 an API key is added by default, which will break the API calls Change By: Ludovic Roucoux 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] [configurationslicing-plugin] (JENKINS-25536) Adding some parameters
Title: Message Title gjd6640 commented on JENKINS-25536 Re: Adding some parameters I'd benefit from the "Subversion: Credentials" feature described here. Can you provide me a link to a document describing the strategy used to add this type of functionality? If I knew where to start I'd be a lot more likely to implement a feature for the config slicer. I'm hoping that the document that you point me to describes whether the model to embed into the config slicing plugin's codebase information about every plugin's setting that it manipulates OR if you teach the other plugin to expose 'sliceable' config values to the config slicing plugin. 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] [support-core-plugin] (JENKINS-30468) Option to include job configurations and build histories
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-30468 Option to include job configurations and build histories Issue Type: New Feature Assignee: Steven Christou Components: support-core-plugin Created: 15/Sep/15 4:53 PM Priority: Major Reporter: Jesse Glick Very often a support issue turns on the details of a job configuration and/or build results. There should be an option for the user to select one or more TopLevelItem whose config.xml should be included in the bundle. Also for Job, you should be able to select one or more builds from which to include build.xml, log, and optionally other files (or at least a directory listing). To make the selection simpler, show a list of the last ten builds to have run on the system and offer to include some or all of those build records, and the corresponding job configuration(s). Add Comment
[JIRA] [youtrack-plugin] (JENKINS-30216) YouTrack plugin doesn't perform actions on issues
Title: Message Title Konstantin Gribov closed an issue as Fixed Jenkins / JENKINS-30216 YouTrack plugin doesn't perform actions on issues Change By: Konstantin Gribov Status: Resolved Closed 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] [youtrack-plugin] (JENKINS-30216) YouTrack plugin doesn't perform actions on issues
Title: Message Title Konstantin Gribov resolved as Fixed Fixed in 0.6.5, thanks Erik Zielke! Jenkins / JENKINS-30216 YouTrack plugin doesn't perform actions on issues Change By: Konstantin Gribov 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] [zaproxy-plugin] (JENKINS-28922) Support authentication
Title: Message Title Ludovic Roucoux resolved as Fixed Authentication is now possible. Jenkins / JENKINS-28922 Support authentication Change By: Ludovic Roucoux 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] [build-alias-setter-plugin] (JENKINS-30426) Allow overwrite of aliases
Title: Message Title Jo Shields commented on JENKINS-30426 Re: Allow overwrite of aliases https://github.com/jenkinsci/build-alias-setter-plugin/pull/1 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] [jira-plugin] (JENKINS-26385) Jira Plugin: "Generate release notes" not work
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-26385 Jira Plugin: "Generate release notes" not work Change By: Radek Antoniuk Labels: jira-plugin-2.0.1 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-30387) P4 changes date are offset by 12 hours on changes page
Title: Message Title Morne Joubert commented on JENKINS-30387 Re: P4 changes date are offset by 12 hours on changes page have found and fixed the problem. shelving 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] [p4-plugin] (JENKINS-30387) P4 changes date are offset by 12 hours on changes page
Title: Message Title Morne Joubert updated an issue Jenkins / JENKINS-30387 P4 changes date are offset by 12 hours on changes page Have track the actual problem but not yet had a look at the code. In the screenshot the dates in green are correct and the date in red are incorrect. The incorrect dates are only for unshelved changes, so there must be a difference on how the dates are extracted for the different set of changes Change By: Morne Joubert Attachment: jenkins_date_problem_2.png 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] [envinject-plugin] (JENKINS-30467) Recursive variable substitution
Title: Message Title
Michele Pagot created an issue
Jenkins / JENKINS-30467
Recursive variable substitution
Issue Type:
Bug
Assignee:
Oleg Nenashev
Components:
envinject-plugin
Created:
15/Sep/15 3:43 PM
Environment:
Jenkins LTS 1.596.3 Envinject plugin 1.92.1
Labels:
plugin
Priority:
Minor
Reporter:
Michele Pagot
If one of the variables from file is something like GATTO=$ {GATTO} miao The plugin iteratively try to solve it. Result is GATTO=${GATTO}
miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao miao
[JIRA] [active-choices-plugin] (JENKINS-28617) Implement a pre-parameter Groovy script for totally dynamic parameters
Title: Message Title cristalp closed an issue as Fixed Jenkins / JENKINS-28617 Implement a pre-parameter Groovy script for totally dynamic parameters Change By: cristalp 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] [p4-plugin] (JENKINS-30466) plugin does not return error if unshelve fails
Title: Message Title Morne Joubert created an issue Jenkins / JENKINS-30466 plugin does not return error if unshelve fails Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 15/Sep/15 3:19 PM Priority: Minor Reporter: Morne Joubert We have detected a few time that the unshelve fails for various reasons: Below is one such example, the p4 plugin should throw an error so it is obvious to the Jenkins job that there was an scm errom. p4 unshelve -f -s141408 -cdefault Librarian checkout /p4/mlb.1/depots/atf/int_mlb/jenkins_batch/atf_l1phy_anritsurtd_build_step.bat failed. Error opening librarian file /p4/mlb.1/depots/atf/int_mlb/jenkins_batch/atf_l1phy_anritsurtd_build_step.bat revision 1.141408. open for read: /p4/mlb.1/depots/atf/int_mlb/jenkins_batch/atf_l1phy_anritsurtd_build_step.bat,d/1.141408.gz: No such file or directory Add Comment
[JIRA] [jira-plugin] (JENKINS-30333) Thread Leak due to use of deprecated JiraSize.createSession
Title: Message Title Radek Antoniuk resolved as Fixed Jenkins / JENKINS-30333 Thread Leak due to use of deprecated JiraSize.createSession Change By: Radek Antoniuk Status: Reopened 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] [jira-plugin] (JENKINS-30408) JIRA REST API requests lead to 404 (not found)
Title: Message Title Radek Antoniuk resolved as Fixed Jenkins / JENKINS-30408 JIRA REST API requests lead to 404 (not found) Change By: Radek Antoniuk 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] [jira-plugin] (JENKINS-30333) Thread Leak due to use of deprecated JiraSize.createSession
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-30333 Thread Leak due to use of deprecated JiraSize.createSession Change By: Radek Antoniuk Labels: jira-plugin-2.0.2 release-queue 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-choices-plugin] (JENKINS-28617) Implement a pre-parameter Groovy script for totally dynamic parameters
Title: Message Title cristalp commented on JENKINS-28617 Re: Implement a pre-parameter Groovy script for totally dynamic parameters I finally got around to use the AC Reactive Reference parameter - what a cool feature! I can do (almost) everything I need with it, so I'm going to close the issue. The only thing that would be great is to be able to run a Groovy script beforehand, because now I'm reading the same XML three times, because I need the data in three different Reactive Reference parameters. But that's just a minor niggle. I still have some questions about the layout, but I'll ask these on the mailing list. 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] [jira-plugin] (JENKINS-30333) Thread Leak due to use of deprecated JiraSize.createSession
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30333 Re: Thread Leak due to use of deprecated JiraSize.createSession Code changed in jenkins User: Gerhard Langs Path: src/main/java/hudson/plugins/jira/JiraSite.java http://jenkins-ci.org/commit/jira-plugin/f238b971bca8f682040e0344dc4e8778fd7da112 Log: JENKINS-30333 use direct references instead of WeakReference, added createSession logging Conflicts: src/main/java/hudson/plugins/jira/JiraSite.java 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] [jira-plugin] (JENKINS-30333) Thread Leak due to use of deprecated JiraSize.createSession
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30333 Re: Thread Leak due to use of deprecated JiraSize.createSession Code changed in jenkins User: Gerhard Langs Path: src/main/java/hudson/plugins/jira/JiraSite.java http://jenkins-ci.org/commit/jira-plugin/f6d0f1fc927fcd373dd05eada22dd87a24a2fe0b Log: JENKINS-30333 use direct references instead of WeakReference, added createSession logging Conflicts: src/main/java/hudson/plugins/jira/JiraSite.java 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] [azure-slave-plugin] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Jay Kah edited a comment on JENKINS-30014 Re: Builds hang, Jenkins still browseable Ping [~snallami] , would you be able to take a look at this? 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] [azure-slave-plugin] (JENKINS-30014) Builds hang, Jenkins still browseable
Title: Message Title Jay Kah commented on JENKINS-30014 Re: Builds hang, Jenkins still browseable Ping suresh nallamilli 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.
