[JIRA] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title ikedam closed an issue as Fixed Fixed in 1.16.1. It will be available in the update center in a day. Jenkins / JENKINS-31318 Retry button invisible with "Build" project role Change By: ikedam 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] [workflow-plugin] (JENKINS-29780) unarchive should support "Flatten directories"
Title: Message Title Dominik Bartholdi commented on JENKINS-29780 Re: unarchive should support "Flatten directories" Andrew Bayer yes please and yes its probably a good idea to target it for stash, unstash. But as for me, even though unarchive I still have it in use and seems like a required counterpart to archive - how else would I get the archived artifacts of an old build? e.g. when I wanna archive the artifacts of a build and also have to reuse them at a later stage in the same build, do I then have to archive and stash the same artifacts just to be able to use unstash because unarchive is deprecated? That does not sound right. 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] [naginator-plugin] (JENKINS-24903) Unabortable builds due to catastrophic backtracking regular expression
Title: Message Title ikedam closed an issue as Fixed Fixed in 1.16.1. It will be available in the update center in a day. Jenkins / JENKINS-24903 Unabortable builds due to catastrophic backtracking regular _expression_ Change By: ikedam 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] [core] (JENKINS-31916) Broken Serializable structure for Slave class
Title: Message Title Oleg Nenashev commented on JENKINS-31916 Re: Broken Serializable structure for Slave class I propose it for 2.0, because the issue cannot be fixed in 1.x due to the public exposure of the RetentionStrategy class. Even if you fix the issue in the core, it's implementations in plugins will be non-serializable in general => the problem of class serialization cannot be fixed without major changes like extension loading validation or static analysis. Hence it's a subject for 2.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] [workflow-plugin] (JENKINS-31878) False warning on no sense parameters in the build a job snippet generator
Title: Message Title Jesse Glick commented on JENKINS-31878 Re: False warning on no sense parameters in the build a job snippet generator It is impossible for `propagate` to be meaningful when `!wait`. By the time the downstream build completes, the upstream could be long gone. And the `build` step has always already completed successfully. 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-31878) False warning on no sense parameters in the build a job snippet generator
Title: Message Title
Jesse Glick edited a comment on JENKINS-31878
Re: False warning on no sense parameters in the build a job snippet generator
It is impossible for ` {{ propagate ` }} to be meaningful when ` {{ !wait ` }} . By the time the downstream build completes, the upstream could be long gone. And the ` {{ build ` }} step has _always_ already completed successfully.
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] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31318 Re: Retry button invisible with "Build" project role Code changed in jenkins User: ikedam Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorRetryAction.java http://jenkins-ci.org/commit/naginator-plugin/91d88d911038f3866829f711ae8f1bb3e3aa672c Log: [FIXED JENKINS-31318] Check BUILD permissions not for Jenkins but for each projects. 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] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31318 Re: Retry button invisible with "Build" project role Code changed in jenkins User: ikedam Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorRetryAction.java src/test/java/com/chikli/hudson/plugin/naginator/NaginatorActionFactoryTest.java http://jenkins-ci.org/commit/naginator-plugin/888e8f4bb8081edc990be3c790cb17d9e6c69cde Log: Merge pull request #22 from ikedam/feature/ JENKINS-31318 _UserPermission JENKINS-31318 Retry button invisible with "Build" project role Compare: https://github.com/jenkinsci/naginator-plugin/compare/d46742e5c2d5...888e8f4bb808 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] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-31318 Retry button invisible with "Build" project role Change By: SCM/JIRA link daemon Status: In Progress 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] [naginator-plugin] (JENKINS-31318) Retry button invisible with "Build" project role
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31318 Re: Retry button invisible with "Build" project role Code changed in jenkins User: ikedam Path: src/test/java/com/chikli/hudson/plugin/naginator/NaginatorActionFactoryTest.java http://jenkins-ci.org/commit/naginator-plugin/9d3e5bbccbec13e50089c8312e9b329f2cb9e1ed Log: JENKINS-31318 Added tests for NaginatorActionFactory including a test reproducing JENKINS-31318 , doesn't check for permissions for each projects. 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] [naginator-plugin] (JENKINS-21241) Plugin should expose environment variables to tell how many times naginator has restarted the build
Title: Message Title Tomer Galun commented on JENKINS-21241 Re: Plugin should expose environment variables to tell how many times naginator has restarted the build Hi Kevin Bella, Right now I don't have the time to implement it. Maybe ikedam will be able to do it or you can add it and do a Pull request. 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] [naginator-plugin] (JENKINS-21241) Plugin should expose environment variables to tell how many times naginator has restarted the build
Title: Message Title Tomer Galun assigned an issue to Unassigned Jenkins / JENKINS-21241 Plugin should expose environment variables to tell how many times naginator has restarted the build Change By: Tomer Galun Assignee: Tomer Galun 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] [naginator-plugin] (JENKINS-24903) Unabortable builds due to catastrophic backtracking regular expression
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24903 Re: Unabortable builds due to catastrophic backtracking regular _expression_ Code changed in jenkins User: ikedam Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorPublisher.java src/main/java/com/chikli/hudson/plugin/naginator/NaginatorPublisherScheduleAction.java src/main/resources/com/chikli/hudson/plugin/naginator/NaginatorPublisher/global.jelly src/main/resources/com/chikli/hudson/plugin/naginator/NaginatorPublisher/help-regexpTimeoutMs.html src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java src/test/java/com/chikli/hudson/plugin/naginator/NaginatorPublisherTest.java http://jenkins-ci.org/commit/naginator-plugin/c4aff2b88aa6e1fd6e23bc8dccfcad4f710ebf47 Log: [FIXED JENKINS-24903] Aborts too long running regular expressions. Added a configuration field for the timeout. 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] [naginator-plugin] (JENKINS-24903) Unabortable builds due to catastrophic backtracking regular expression
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24903 Re: Unabortable builds due to catastrophic backtracking regular _expression_ Code changed in jenkins User: ikedam Path: src/main/java/com/chikli/hudson/plugin/naginator/NaginatorPublisher.java src/main/java/com/chikli/hudson/plugin/naginator/NaginatorPublisherScheduleAction.java src/main/resources/com/chikli/hudson/plugin/naginator/NaginatorPublisher/global.jelly src/main/resources/com/chikli/hudson/plugin/naginator/NaginatorPublisher/help-regexpTimeoutMs.html src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java src/test/java/com/chikli/hudson/plugin/naginator/NaginatorPublisherTest.java http://jenkins-ci.org/commit/naginator-plugin/d86ff5bf9adb47c7911d1c83a28b1c43c67946a7 Log: Merge pull request #23 from ikedam/feature/ JENKINS-24903 _InfiniteRegularExpression JENKINS-24903 Aborts long running regular expressions Compare: https://github.com/jenkinsci/naginator-plugin/compare/888e8f4bb808...d86ff5bf9adb 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] [naginator-plugin] (JENKINS-24903) Unabortable builds due to catastrophic backtracking regular expression
Title: Message Title SCM/JIRA link daemon commented on JENKINS-24903 Re: Unabortable builds due to catastrophic backtracking regular _expression_ Code changed in jenkins User: ikedam Path: src/test/java/com/chikli/hudson/plugin/naginator/NaginatorListenerTest.java http://jenkins-ci.org/commit/naginator-plugin/4012e4cd8b6a22c9e7ff534d46d7d4058e42fd20 Log: JENKINS-24903 Added a test to reproduce a catastrophic backtracking regular _expression_. 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] [naginator-plugin] (JENKINS-24903) Unabortable builds due to catastrophic backtracking regular expression
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-24903 Unabortable builds due to catastrophic backtracking regular _expression_ Change By: SCM/JIRA link daemon Status: In Progress 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] [copyartifact-plugin] (JENKINS-31563) Latest successful artifact cannot be copied from Maven build
Title: Message Title ikedam commented on JENKINS-31563 Re: Latest successful artifact cannot be copied from Maven build Could not reproduce in my environment. Please let me know the detailed steps to reproduce the problem. Tested steps (tested with Windows 8.1 64bits, Java 1.7.0_79): Install and launch jenkins.1.625.2. Install following plugins: copyartifact-plugin (tested with 1.37) git-plugin (tested with 2.4.0, requires restarting Jenkins) Setup maven in Manage Jenkins > Configure System (tested with maven-3.1.1) Create a maven project "job1" Git repository: https://github.com/jenkinsci/copyartifact-plugin.git Goals and options: package -DskipTests=true Check "Disable automatic artifact archiving" in the advanced section. Add "Archive the artifacts" to "Post-build Actions" Files to archive: target/*.hpi Run "job1". job1 #1 will finish successfully. Create a freestyle project "job2" Add "Copy artifacts from another project" Project name: job1
[JIRA] [workflow-plugin] (JENKINS-27396) Elastic timeout
Title: Message Title Andrew Bayer commented on JENKINS-27396 Re: Elastic timeout So the first thing that jumps out at me is having to find the "similar" block in previous builds. Once I understand that, the rest should be pretty easy. =) 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-26521) timeout step should support breaking on inactivity, not just a fixed duration
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-26521 timeout step should support breaking on inactivity, not just a fixed duration Change By: Andrew Bayer Assignee: Kohsuke Kawaguchi Andrew Bayer 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-31878) False warning on no sense parameters in the build a job snippet generator
Title: Message Title Jens Wilke commented on JENKINS-31878 Re: False warning on no sense parameters in the build a job snippet generator Yes, but it can also be the other way around: If `propagate` is enabled, `!wait` is not meaningful, since it always has to be waited. So, logically, the setting combination `propagate` and `!wait` is invalid or conflicting. But the warning appears for `!propagate` and `!wait`, which is perfectly valid. 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-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-5303 Upgrade Acegi Security to the latest Spring Security release Change By: Kanstantsin Shautsou Priority: Major Blocker 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-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Kanstantsin Shautsou commented on JENKINS-5303 Re: Upgrade Acegi Security to the latest Spring Security release In 2015 it's Blocker. Jenkins ships acegi-security released in 2008. 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-28718) withTool
Title: Message Title Andrew Bayer commented on JENKINS-28718 Re: withTool Agreed. There's real value in tool just installing the tool - in case you've got multiple versions of a tool used in the same workflow/node. 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-5303) Upgrade Acegi Security to the latest Spring Security release
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-5303 Upgrade Acegi Security to the latest Spring Security release Change By: Kanstantsin Shautsou Issue Type: Improvement Task 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-27396) Elastic timeout
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-27396 Elastic timeout Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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-31792) Ability to fingerprint artifacts on an ArtifactArchiverStep
Title: Message Title Andrew Bayer commented on JENKINS-31792 Re: Ability to fingerprint artifacts on an ArtifactArchiverStep I'm confused - thought something like step([$class: 'ArtifactArchiver', artifacts: 'output/*', excludes: null, fingerprint: true, onlyIfSuccessful: true]) would do that? 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-31916) Broken Serializable structure for Slave class
Title: Message Title
Kanstantsin Shautsou updated an issue
Jenkins / JENKINS-31916
Broken Serializable structure for Slave class
Change By:
Kanstantsin Shautsou
{code}public abstract class Slave extends Node implements Serializable {/** * Slave availablility strategy. */private RetentionStrategy retentionStrategy;/** * The starter that will startup this slave. */private ComputerLauncher launcher;{code}Both classes are not Serializable. Blocks for having clean FindBugs in 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] [sitemonitor-plugin] (JENKINS-19054) Improvement adding basic auth url feature with Site Montor plugin
Title: Message Title Francisco Hernandez Suarez assigned an issue to Francisco Hernandez Suarez Jenkins / JENKINS-19054 Improvement adding basic auth url feature with Site Montor plugin Change By: Francisco Hernandez Suarez Assignee: cliffano Francisco Hernandez Suarez 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] [sitemonitor-plugin] (JENKINS-12419) Sitemonitor: add Http proxy support
Title: Message Title Francisco Hernandez Suarez assigned an issue to Francisco Hernandez Suarez Jenkins / JENKINS-12419 Sitemonitor: add Http proxy support Change By: Francisco Hernandez Suarez Assignee: cliffano Francisco Hernandez Suarez 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] [sitemonitor-plugin] (JENKINS-12419) Sitemonitor: add Http proxy support
Title: Message Title Francisco Hernandez Suarez resolved as Fixed A pull request was made in order to fix it, so mark the issue as resolved. Jenkins / JENKINS-12419 Sitemonitor: add Http proxy support Change By: Francisco Hernandez Suarez 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] [workflow-plugin] (JENKINS-27092) create a step to abort the build with a NOT_BUILT status
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-27092 create a step to abort the build with a NOT_BUILT status Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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-27092) create a step to abort the build with a NOT_BUILT status
Title: Message Title Andrew Bayer commented on JENKINS-27092 Re: create a step to abort the build with a NOT_BUILT status My gut instinct is to take the Result as a String and use Result.fromString() at execution time rather than converting at specification time...or maybe I'm just getting distracted by the enum mention. =) 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-31153) Rename workflow to pipeline
Title: Message Title Andrew Bayer commented on JENKINS-31153 Re: Rename workflow to pipeline IMO, we're past the point where renaming is viable. Renaming to "pipeline" or whatever is just going to cause confusion. I'm a strong -1 on 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] [workflow-plugin] (JENKINS-31086) 'stash' step applies default ant exclude patterns, no way to disable this
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-31086 'stash' step applies default ant exclude patterns, no way to disable this Change By: Andrew Bayer Assignee: Jesse Glick Andrew Bayer 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-31916) Broken Serializable structure for Slave class
Title: Message Title Oleg Nenashev commented on JENKINS-31916 Re: Broken Serializable structure for Slave class Seems it's a subject for 2.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] [sitemonitor-plugin] (JENKINS-19054) Improvement adding basic auth url feature with Site Montor plugin
Title: Message Title Francisco Hernandez Suarez resolved as Fixed A pull request was made on 6/Aug/13 in order to resolve this issue, mark this issue as resolved. Jenkins / JENKINS-19054 Improvement adding basic auth url feature with Site Montor plugin Change By: Francisco Hernandez Suarez 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] [core] (JENKINS-31916) Broken Serializable structure for Slave class
Title: Message Title
Kanstantsin Shautsou created an issue
Jenkins / JENKINS-31916
Broken Serializable structure for Slave class
Issue Type:
Bug
Assignee:
stephenconnolly
Components:
core
Created:
05/Dec/15 6:33 PM
Priority:
Major
Reporter:
Kanstantsin Shautsou
public abstract class Slave extends Node implements Serializable {
/**
* Slave availablility strategy.
*/
private RetentionStrategy retentionStrategy;
/**
* The starter that will startup this slave.
*/
private ComputerLauncher launcher;
Both classes are not Serializable.
Add Comment
[JIRA] [timestamper-plugin] (JENKINS-30143) logs for individual workflow steps do not contain timestamps
Title: Message Title Andrew Bayer commented on JENKINS-30143 Re: logs for individual workflow steps do not contain timestamps Yeah, I noticed that with multibranch. 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-29780) unarchive should support "Flatten directories"
Title: Message Title Andrew Bayer commented on JENKINS-29780 Re: unarchive should support "Flatten directories" Jesse Glick - given the deprecation of unarchive, is it worth me making a run 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] [workflow-plugin] (JENKINS-29881) WorkflowRun.getChangeSets should skip empty changesets
Title: Message Title Andrew Bayer commented on JENKINS-29881 Re: WorkflowRun.getChangeSets should skip empty changesets I'm a bit confused here - at first glance, WorkflowRun.getChangeSets feels like it should behave similarly - or is it a situation where SCMCheckout.changelogFile could exist but be empty, resulting in changeSets itself not being empty but the elements within it being empty? 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-31086) 'stash' step applies default ant exclude patterns, no way to disable this
Title: Message Title Andrew Bayer started work on JENKINS-31086 Change By: Andrew Bayer Status: Open In Progress 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-28276) Map collectEntries closure not behaving correctly
Title: Message Title Andrew Bayer commented on JENKINS-28276 Re: Map collectEntries closure not behaving correctly fwiw, verified that this fails in Workflow normally, but works in Jenkins /script console and in Workflow with @NonCPS. 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] [sitemonitor-plugin] (JENKINS-19054) Improvement adding basic auth url feature with Site Montor plugin
Title: Message Title Francisco Hernandez Suarez edited a comment on JENKINS-19054 Re: Improvement adding basic auth url feature with Site Montor plugin A pull request was made on 6/Aug/13 in order to resolve improve the plugin with this issue functionality , so mark this issue as resolved. 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] [global-post-script-plugin] (JENKINS-31907) Does not expose GIT_ variables
Title: Message Title Hao CHEN commented on JENKINS-31907 Re: Does not expose GIT_ variables I believe it's available. Try GIT_URL instead of $GIT_URL And make sure you have git plugin installed. 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] [global-post-script-plugin] (JENKINS-31907) Does not expose GIT_ variables
Title: Message Title Hao CHEN assigned an issue to Jo Shields I did a test, the followings are available: GIT_BRANCH GIT_COMMIT GIT_PREVIOUS_COMMIT GIT_PREVIOUS_SUCCESSFUL_COMMIT GIT_URL Jenkins / JENKINS-31907 Does not expose GIT_ variables Change By: Hao CHEN Assignee: Hao CHEN Jo Shields Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are
[JIRA] [core] (JENKINS-11364) Low memory debian systems cause IOException: No space left on device
Title: Message Title dwdyer reopened an issue There appears to have been a regression as this issue is re-occurring for me with recent versions. I'm not sure when it started again but it was a problem when I updated a month or so ago and it's still a problem with 1.635. The WAR is being extracted to /run and filling it up, preventing Jenkins from starting. Jenkins / JENKINS-11364 Low memory debian systems cause IOException: No space left on device Change By: dwdyer Resolution: Duplicate Status: Resolved Reopened 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] [sitemonitor-plugin] (JENKINS-31540) SiteMonitor plugin doesn't support TLS1.2 encryption
Title: Message Title Francisco Hernandez Suarez assigned an issue to Francisco Hernandez Suarez Jenkins / JENKINS-31540 SiteMonitor plugin doesn't support TLS1.2 encryption Change By: Francisco Hernandez Suarez Assignee: cliffano Francisco Hernandez Suarez 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] [sitemonitor-plugin] (JENKINS-20494) Allow to override the response code individually on a job context
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20494 Re: Allow to override the response code individually on a job context Code changed in jenkins User: Francisco Hernández Suárez Path: .gitignore pom.xml src/main/java/hudson/plugins/sitemonitor/SiteMonitorDescriptor.java src/main/java/hudson/plugins/sitemonitor/SiteMonitorRecorder.java src/main/java/hudson/plugins/sitemonitor/SiteMonitorValidator.java src/main/java/hudson/plugins/sitemonitor/mapper/JsonToSiteMapper.java src/main/java/hudson/plugins/sitemonitor/mapper/JsonToSuccessResponseList.java src/main/java/hudson/plugins/sitemonitor/mapper/SuccessCodeListToCvString.java src/main/java/hudson/plugins/sitemonitor/model/Site.java src/main/resources/hudson/plugins/sitemonitor/SiteMonitorRecorder/config.jelly src/main/webapp/successresponsecodes_sites.html http://jenkins-ci.org/commit/sitemonitor-plugin/71238ff028b99da3b30c3dd336dc4c49053c7aab Log: Merge pull request #9 from onuba/master https://issues.jenkins-ci.org/browse/JENKINS-20494 Initial commit Compare: https://github.com/jenkinsci/sitemonitor-plugin/compare/0c805d07864d...71238ff028b9 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] [sitemonitor-plugin] (JENKINS-20494) Allow to override the response code individually on a job context
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20494 Re: Allow to override the response code individually on a job context Code changed in jenkins User: onuba - Francisco Hernandez Path: .gitignore pom.xml src/main/java/hudson/plugins/sitemonitor/SiteMonitorDescriptor.java src/main/java/hudson/plugins/sitemonitor/SiteMonitorRecorder.java src/main/java/hudson/plugins/sitemonitor/SiteMonitorValidator.java src/main/java/hudson/plugins/sitemonitor/mapper/JsonToSiteMapper.java src/main/java/hudson/plugins/sitemonitor/mapper/JsonToSuccessResponseList.java src/main/java/hudson/plugins/sitemonitor/mapper/SuccessCodeListToCvString.java src/main/java/hudson/plugins/sitemonitor/model/Site.java src/main/resources/hudson/plugins/sitemonitor/SiteMonitorRecorder/config.jelly src/main/webapp/successresponsecodes_sites.html http://jenkins-ci.org/commit/sitemonitor-plugin/2601c3360ceeba62843151276a4bf30d1890448f Log: https://issues.jenkins-ci.org/browse/JENKINS-20494 Initial commit 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] [sitemonitor-plugin] (JENKINS-20494) Allow to override the response code individually on a job context
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20494 Re: Allow to override the response code individually on a job context Code changed in jenkins User: onuba - Francisco Hernandez Path: .gitignore pom.xml src/main/java/hudson/plugins/sitemonitor/SiteMonitorDescriptor.java src/main/java/hudson/plugins/sitemonitor/SiteMonitorRecorder.java src/main/java/hudson/plugins/sitemonitor/SiteMonitorValidator.java src/main/java/hudson/plugins/sitemonitor/mapper/JsonToSiteMapper.java src/main/java/hudson/plugins/sitemonitor/mapper/JsonToSuccessResponseList.java src/main/java/hudson/plugins/sitemonitor/mapper/SuccessCodeListToCvString.java src/main/java/hudson/plugins/sitemonitor/model/Site.java src/main/resources/hudson/plugins/sitemonitor/SiteMonitorRecorder/config.jelly src/main/webapp/successresponsecodes_sites.html src/test/java/hudson/plugins/sitemonitor/SiteMonitorRecorderTest.java src/test/java/hudson/plugins/sitemonitor/SiteMonitorRootActionTest.java src/test/java/hudson/plugins/sitemonitor/model/ResultTest.java src/test/java/hudson/plugins/sitemonitor/model/SiteTest.java http://jenkins-ci.org/commit/sitemonitor-plugin/23671e0cda5c446d316beebc65adf56f868cd74c Log: https://issues.jenkins-ci.org/browse/JENKINS-20494 Initial commit, tests classes updated 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] [sitemonitor-plugin] (JENKINS-20494) Allow to override the response code individually on a job context
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20494 Re: Allow to override the response code individually on a job context Code changed in jenkins User: Francisco Hernández Suárez Path: .gitignore src/test/java/hudson/plugins/sitemonitor/SiteMonitorRecorderTest.java src/test/java/hudson/plugins/sitemonitor/SiteMonitorRootActionTest.java src/test/java/hudson/plugins/sitemonitor/model/ResultTest.java src/test/java/hudson/plugins/sitemonitor/model/SiteTest.java http://jenkins-ci.org/commit/sitemonitor-plugin/6f76b0614257d3b85eccf484e7dfe2e1a8e551a5 Log: Merge pull request #10 from onuba/master https://issues.jenkins-ci.org/browse/JENKINS-20494, new feature Compare: https://github.com/jenkinsci/sitemonitor-plugin/compare/71238ff028b9...6f76b0614257 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-29780) unarchive should support "Flatten directories"
Title: Message Title Jesse Glick commented on JENKINS-29780 Re: unarchive should support "Flatten directories" Should probably be recast to be an option for unstash or even stash. 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] [bitbucket-plugin] (JENKINS-31919) bitbucket plugin hook does not work for Jenkins behind SSL with self-signed cert: "NET_ERR"
Title: Message Title Alex Java updated an issue Jenkins / JENKINS-31919 bitbucket plugin hook does not work for Jenkins behind SSL with self-signed cert: "NET_ERR" Change By: Alex Java Summary: bitbucket plugin hook does not work for Jenkins behind SSL with self-signed cert : "NET_ERR" 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] [bitbucket-plugin] (JENKINS-31919) bitbucket plugin hook does not work: "NET_ERR"
Title: Message Title
Alex Java updated an issue
Jenkins / JENKINS-31919
bitbucket plugin hook does not work: "NET_ERR"
Change By:
Alex Java
Summary:
bitbucket plugin hook does not work: " A JSONObject text must begin with '{' at character 0 of NET_ERR "
I installed Bitbucket Plugin 1.1.2 to my Jenkins (v 1.638)created a webhook in my BitBucket repository:https://ta-dev.ddns.net:8193/bitbucket-hookpushed a change to the repo. the build did not start in Jenkins. I looked as "requests log" in Bitbucket, it said "NET_ERR".I tried calling "https://ta-dev.ddns.net:8193/bitbucket-hook" directly in the browser (GET request) and got this:javax.servlet.ServletException: net.sf.json.JSONException: A JSONObject text must begin with '{' at character 0 of at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] [sitemonitor-plugin] (JENKINS-31540) SiteMonitor plugin doesn't support TLS1.2 encryption
Title: Message Title Francisco Hernandez Suarez commented on JENKINS-31540 Re: SiteMonitor plugin doesn't support TLS1.2 encryption Pavel Saab I have tested the actual release 0.4 against my github home URL (uses TLS 1.2 encryption) and the result is OK. Could you please give more details? Thanks in advanced 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] [sitemonitor-plugin] (JENKINS-20494) Allow to override the response code individually on a job context
Title: Message Title SCM/JIRA link daemon commented on JENKINS-20494 Re: Allow to override the response code individually on a job context Code changed in jenkins User: Francisco Hernández Suárez Path: .gitignore pom.xml src/main/java/hudson/plugins/sitemonitor/SiteMonitorDescriptor.java src/main/java/hudson/plugins/sitemonitor/SiteMonitorRecorder.java src/main/java/hudson/plugins/sitemonitor/SiteMonitorValidator.java src/main/java/hudson/plugins/sitemonitor/mapper/JsonToSiteMapper.java src/main/java/hudson/plugins/sitemonitor/mapper/JsonToSuccessResponseList.java src/main/java/hudson/plugins/sitemonitor/mapper/SuccessCodeListToCvString.java src/main/java/hudson/plugins/sitemonitor/model/Site.java src/main/resources/hudson/plugins/sitemonitor/SiteMonitorRecorder/config.jelly src/main/webapp/successresponsecodes_sites.html http://jenkins-ci.org/commit/sitemonitor-plugin/81ce822f07056d808180d01be039ad7bfe1a27b2 Log: Revert "https://issues.jenkins-ci.org/browse/JENKINS-20494 Initial commit" 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-27396) Elastic timeout
Title: Message Title Jesse Glick commented on JENKINS-27396 Re: Elastic timeout I think the only reliable way to do that is to have the option include a unique textual ID, whereupon an Action gets attached to the FlowNode recording the ID and observed run time for use in subsequent builds. (TimingAction might already cover the latter.) 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-27092) create a step to abort the build with a NOT_BUILT status
Title: Message Title Jesse Glick commented on JENKINS-27092 Re: create a step to abort the build with a NOT_BUILT status Well this kind of addition to DescribableHelper should be easy, and may be useful in the future. 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-31916) Broken Serializable structure for Slave class
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-31916 Broken Serializable structure for Slave class Change By: Kanstantsin Shautsou Labels: 2.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] [core] (JENKINS-31916) Broken Serializable structure for Slave class
Title: Message Title Kanstantsin Shautsou commented on JENKINS-31916 Re: Broken Serializable structure for Slave class Why 2.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] [bitbucket-plugin] (JENKINS-31919) bitbucket plugin hook does not work: "A JSONObject text must begin with '{' at character 0 of "
Title: Message Title
Alex Java created an issue
Jenkins / JENKINS-31919
bitbucket plugin hook does not work: "A JSONObject text must begin with '{' at character 0 of "
Issue Type:
Bug
Assignee:
Unassigned
Components:
bitbucket-plugin
Created:
06/Dec/15 12:44 AM
Priority:
Blocker
Reporter:
Alex Java
I installed Bitbucket Plugin 1.1.2 to my Jenkins (v 1.638) created a webhook in my BitBucket repository: https://ta-dev.ddns.net:8193/bitbucket-hook pushed a change to the repo. the build did not start in Jenkins. I looked as "requests log" in Bitbucket, it said "NET_ERR". I tried calling "https://ta-dev.ddns.net:8193/bitbucket-hook" directly in the browser (GET request) and got this:
javax.servlet.ServletException: net.sf.json.JSONException: A JSONObject text must begin with '{' at character 0 of at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:132) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:123) at
[JIRA] [scm-api-plugin] (JENKINS-31917) Saving/Applying job config causes NullPointerException at hudson.scm.SubversionSCM
Title: Message Title Geoff Kirk created an issue Jenkins / JENKINS-31917 Saving/Applying job config causes NullPointerException at hudson.scm.SubversionSCM Issue Type: Bug Assignee: Unassigned Attachments: support_2015-12-05_19.01.09.zip Components: scm-api-plugin Created: 05/Dec/15 8:06 PM Environment: Jenkins 1.638 CentOS 6.5 Subversion plugin 2.5.3 Labels: plugin exception scm configuration subversion Priority: Minor Reporter: Geoff Kirk While saving a job configuration the Exception occurs intermittently. When I go back into the job configuration, many times all configuration for the particular job is missing from the configuration form. I usually have to open the config.xml and
[JIRA] [sitemonitor-plugin] (JENKINS-20494) Allow to override the response code individually on a job context
Title: Message Title Francisco Hernandez Suarez started work on JENKINS-20494 Change By: Francisco Hernandez Suarez Status: Open In Progress 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] [sitemonitor-plugin] (JENKINS-20494) Allow to override the response code individually on a job context
Title: Message Title Francisco Hernandez Suarez assigned an issue to Francisco Hernandez Suarez Jenkins / JENKINS-20494 Allow to override the response code individually on a job context Change By: Francisco Hernandez Suarez Assignee: cliffano Francisco Hernandez Suarez 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] [sitemonitor-plugin] (JENKINS-20494) Allow to override the response code individually on a job context
Title: Message Title Francisco Hernandez Suarez commented on JENKINS-20494 Re: Allow to override the response code individually on a job context Working on this issue for the next 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] [swarm-plugin] (JENKINS-31918) Workflow Parallel task causing serialization error with Swarm Node
Title: Message Title
Ming Fang created an issue
Jenkins / JENKINS-31918
Workflow Parallel task causing serialization error with Swarm Node
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
swarm-plugin, workflow-plugin
Created:
05/Dec/15 9:25 PM
Priority:
Minor
Reporter:
Ming Fang
I have 2 Swarm Nodes running. This is my workflow script.
def tasks = [:] for(node in Jenkins.instance.nodes){ def name = node.name tasks[name] = { node(name) { echo name }
} } parallel tasks
Error
[Workflow] echo adding jenkins-swarm-client-cjww8-1ec8e67c [Workflow] echo adding jenkins-swarm-client-njiq5-8e4b034d [Workflow] Execute sub-workflows in parallel : Start [Workflow] [jenkins-swarm-client-cjww8-1ec8e67c] parallel {: Parallel branch: jenkins-swarm-client-cjww8-1ec8e67c [Workflow] [jenkins-swarm-client-njiq5-8e4b034d] parallel {: Parallel branch: jenkins-swarm-client-njiq5-8e4b034d [Workflow] } //parallel [Workflow] } //parallel [Workflow] End of Workflow java.io.NotSerializableException: hudson.plugins.swarm.SwarmSlave$1 at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:860) at org.jboss.marshalling.river.RiverMarshaller.doWriteFields(RiverMarshaller.java:1032) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:988) at org.jboss.marshalling.river.RiverMarshaller.doWriteSerializableObject(RiverMarshaller.java:967) at org.jboss.marshalling.river.RiverMarshaller.doWriteObject(RiverMarshaller.java:854) at
[JIRA] [workflow-plugin] (JENKINS-29413) Parallel with an empty map will run forever
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-29413 Parallel with an empty map will run forever Change By: SCM/JIRA link daemon Status: In Progress 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] [workflow-plugin] (JENKINS-29413) Parallel with an empty map will run forever
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29413 Re: Parallel with an empty map will run forever Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/parallel/ParallelStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/85330f60060d84c9d4d5b05a2062e9fc97063a74 Log: Merge pull request #265 from jglick/parallel- JENKINS-29413 JENKINS-29413 Hung build when running the parallel step with an empty map Compare: https://github.com/jenkinsci/workflow-plugin/compare/be558db587b9...85330f60060d 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-29413) Parallel with an empty map will run forever
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29413 Re: Parallel with an empty map will run forever Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/parallel/ParallelStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/steps/ParallelStepExecution.java http://jenkins-ci.org/commit/workflow-plugin/1ecc56e967940fbc6047aa432d5d5e556670eca2 Log: [FIXED JENKINS-29413]: hung build when running the parallel step with an empty map. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-23345) Git Plugin should have an option to use clone instead of init/fetch
Title: Message Title Mark Waite commented on JENKINS-23345 Re: Git Plugin should have an option to use clone instead of init/fetch There is no ETA for any implementation that will replace the current init/fetch with clone. Is your use case one of the use cases already described, or something different? 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] [snsnotify-plugin] (JENKINS-31444) SNS Notify Plugin fails because of missing dependency
Title: Message Title Edwin Fine commented on JENKINS-31444 Re: SNS Notify Plugin fails because of missing dependency The answer appears to be a duplicate library, as seen in this post, which has a workaround, but it's not a good one for people like me, who automate building the Jenkins server. https://wiki.jenkins-ci.org/display/JENKINS/Amazon+SNS+Notifier?focusedCommentId=83362519#comment-83362519 If this is the solution, it would be great if you could fix this problem. Thanks for a nifty 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] [snsnotify-plugin] (JENKINS-31444) SNS Notify Plugin fails because of missing dependency
Title: Message Title Edwin Fine commented on JENKINS-31444 Re: SNS Notify Plugin fails because of missing dependency I have a similar situation. Dec 06, 2015 1:41:52 AM INFO hudson.model.Run execute test_stash_webhook-deploy #13 main build action completed: SUCCESS Dec 06, 2015 1:41:52 AM INFO org.jenkinsci.plugins.snsnotify.AmazonSNSNotifier onCompleted Prepare SNS notification for build completed... Dec 06, 2015 1:41:52 AM INFO org.jenkinsci.plugins.snsnotify.AmazonSNSNotifier send Setup SNS client 'sns.eu-central-1.amazonaws.com' ... Dec 06, 2015 1:41:52 AM WARNING hudson.model.listeners.RunListener report RunListener failed java.lang.NoClassDefFoundError: org/apache/http/util/Args at org.apache.http.conn.scheme.Scheme.(Scheme.java:90) at org.apache.http.impl.conn.SchemeRegistryFactory.createDefault(SchemeRegistryFactory.java:50) at com.amazonaws.http.ConnectionManagerFactory.createPoolingClientConnManager(ConnectionManagerFactory.java:29) at com.amazonaws.http.HttpClientFactory.createHttpClient(HttpClientFactory.java:104) at com.amazonaws.http.AmazonHttpClient.(AmazonHttpClient.java:198) at com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:132) at com.amazonaws.AmazonWebServiceClient.(AmazonWebServiceClient.java:116) at com.amazonaws.services.sns.AmazonSNSClient.(AmazonSNSClient.java:147) at com.amazonaws.services.sns.AmazonSNSClient.(AmazonSNSClient.java:128) at org.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.send(AmazonSNSNotifier.java:144) at org.jenkinsci.plugins.snsnotify.AmazonSNSNotifier.onCompleted(AmazonSNSNotifier.java:85) at org.jenkinsci.plugins.snsnotify.BuildListener.onCompleted(BuildListener.java:30) at org.jenkinsci.plugins.snsnotify.BuildListener.onCompleted(BuildListener.java:8) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:201) 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.
