[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Vivek Pandey updated JENKINS-48357 Jenkins / JENKINS-48357 Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API Change By: Vivek Pandey Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51052) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on JENKINS-51052 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build foo-fs #3 (See http://localhost:8080/job/foo-fs/3/) JENKINS-51052 test (noreply: 1/05/18 2:23 PM https://github.com/olamy/foo/commit/e3ebe480cdb653738a84f47228d40fc9ca0cf438) (edit) pom.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Olivier Lamy commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API pr https://github.com/jenkinsci/jira-plugin/pull/145 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51052) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy started work on JENKINS-51052 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50140) Integration of JIRA plugin version 2.5.1 with Jenkins
Title: Message Title Olivier Lamy closed an issue as Fixed Jenkins / JENKINS-50140 Integration of JIRA plugin version 2.5.1 with Jenkins Change By: Olivier Lamy Status: Open Closed Assignee: Olivier Lamy Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Olivier Lamy started work on JENKINS-25829 Change By: Olivier Lamy Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-19075) Publish over CIFS fails with Out of memory error
Title: Message Title Maxime Viargues commented on JENKINS-19075 Re: Publish over CIFS fails with Out of memory error Well upgrading to the latest "Publish Over CIFS" plug-in v0.10 fixed the issue. They have changed the underlying library to use a new jcfis library which is a lot different and removed/changed the failing code. They've just release v0.10 like 3 days after our upgrade... Bad luck on the timing. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51050) Blueocean paused for Input requested, but never asks for it
Title: Message Title James Dumay commented on JENKINS-51050 Re: Blueocean paused for Input requested, but never asks for it Miguel C could you please post a simplified example Jenkinsfile that demonstrates this problem? cc Jenn Briden Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51052) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy commented on JENKINS-51052 Re: Issue for testing purpose so do not mind SUCCESS: Integrated in Jenkins build foo-fs #2 (See http://localhost:8080/job/foo-fs/2/) JENKINS-51052 test (noreply: 1/05/18 10:55 AM https://github.com/olamy/foo/commit/670b0316df5c300f1574e9c9614ee112989899f7) (edit) pom.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50020) CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage
Title: Message Title Sam Van Oort closed an issue as Duplicate The fixes to JENKINS-50752 should handle the serialization issues. Jenkins / JENKINS-50020 CpsFlowExecution unresponsive and Failed to serialize SimpleXStreamFlowNodeStorage Change By: Sam Van Oort Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-51052) Issue for testing purpose so do not mind
Title: Message Title Olivier Lamy created an issue Jenkins / JENKINS-51052 Issue for testing purpose so do not mind Issue Type: Task Assignee: Olivier Lamy Components: jira-plugin Created: 2018-04-30 23:49 Priority: Minor Reporter: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues"
[JIRA] (JENKINS-25829) Proxy configuration does not work
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-25829 Proxy configuration does not work Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Jenn Briden started work on JENKINS-48357 Change By: Jenn Briden Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-44699) Reduce step log length
Title: Message Title Jenn Briden stopped work on JENKINS-44699 Change By: Jenn Briden Status: In Progress Open Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-45455) Restarting stages
Title: Message Title Will Saxon commented on JENKINS-45455 Re: Restarting stages So is this a Blue Ocean feature, or a Pipeline feature? I know I would be pleased to have restart capability even if it was outside Blue Ocean, even if it was just an API call. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-45455) Restarting stages
Title: Message Title Jenn Briden commented on JENKINS-45455 Re: Restarting stages denis krizanovic, we are working through the user experience design now to be sure that we take various use cases into account. We have an offsite next week with the Blue Ocean and Pipeline teams, and one of our sessions is to define that UX. We'll then need to do that work. I cannot commit to a specific timeline for when it will be merged to the main Blue Ocean plugin, but we are working on it. I will be sure to update this ticket after our offsite, as well as the corresponding ticket for the UX. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title olamy commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API got the sources from maven repo. I don't mind the rest client I just to override the Atlassian httpclient ( https://packages.atlassian.com/maven-external/com/atlassian/httpclient/atlassian-httpclient-plugin/0.23.0/ ) The goal is to have a local copy of those classes so we can simply have our version of Apache httpclient. I have it done locally, I have to do more testing (separate Jenkins install with bo and real JIRA etc...) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51051) Trying to start new docker container and get credential error on login
Title: Message Title Stuart Karp created an issue Jenkins / JENKINS-51051 Trying to start new docker container and get credential error on login Issue Type: Bug Assignee: Stephen Connolly Components: credentials-plugin Created: 2018-04-30 21:31 Priority: Minor Reporter: Stuart Karp I'm trying to migrate a Jenkins from one docker container to another. I copied the HOME directory and everything works fine and until I login and get this error: org.apache.commons.jelly.JellyTagException: jar:file:/var/jenkins_home/.jenkins/war/WEB-INF/lib/jenkins-core-2.60.3.jar!/lib/hudson/actions.jelly:39:70: com.cloudbees.plugins.credentials.CredentialsProvider.enabled(Ljava/lang/Object;)Ljava/util/List; at org.apache.commons.jelly.impl.TagScript.handleException(TagScript.java:745) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:289) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161) at org.apache.commons.jelly.tags.core.ForEachTag.doTag(ForEachTag.java:150) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at
[JIRA] (JENKINS-50807) Add OwnershipHelperLocator implementations for Computer and Node classes
Title: Message Title Oleg Nenashev updated JENKINS-50807 Fixed in o.12.1 Jenkins / JENKINS-50807 Add OwnershipHelperLocator implementations for Computer and Node classes Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Oleg Nenashev commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Some bits have been released in 0.12.1. I am going to also address createItem() somehow, but it's not trivial Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title Devin Nusbaum commented on JENKINS-51049 Re: Folders Plugin GitHub Scanning Time not being copied into the Jobs Thanks for reporting the issue. To help figure out where things are going wrong, could you attach the config.xml of the parent folder that you are having issues with? You can get it from the UI by navigating the folder and then adding config.xml to the URL. You'll want to make sure to remove any sensitive content (I only want to see the general structure). Also, since you marked this ticket as a regression, can you list the environment in which things were previously working? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title
Mark Waite edited a comment on JENKINS-37050
Re: Pipeline Job Cannot Checkout Git Tag
[~allan_burdajewicz] described correctly why this is not a bug. The `git` step intentionally is a simple subset of the full capabilities of the `checkout` step. Use the `checkout` step[~ plabedan derrickgw ] you can find an example using the full checkout step to checkout a specific tag in the [Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-37050/Jenkinsfile] of my [jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/] on the [JENKINS-37050 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37050]. The default clone settings intentionally do not download tags so that less data is transferred for multi-branch pipelines that are building a single branch. The example file adds the {{CloneOption}} which downloads tags.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title
Mark Waite edited a comment on JENKINS-37050
Re: Pipeline Job Cannot Checkout Git Tag
[~allan_burdajewicz] described correctly why this is not a bug. The `git` step intentionally is a simple subset of the full capabilities of the `checkout` step. Use the `checkout` step[~plabedan] you can find an example using the full checkout step to checkout a specific tag in the [Jenkinsfile|https://github.com/MarkEWaite/jenkins-bugs/blob/JENKINS-37050/Jenkinsfile] of my [jenkins-bugs repository|https://github.com/MarkEWaite/jenkins-bugs/] on the [JENKINS-37050 branch|https://github.com/MarkEWaite/jenkins-bugs/tree/JENKINS-37050]. The default clone settings intentionally do not download tags so that less data is transferred for multi-branch pipelines that are building a single branch. The example file adds the {{CloneOption}} which download downloads tags.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-37050) Pipeline Job Cannot Checkout Git Tag
Title: Message Title Mark Waite resolved as Not A Defect Allan BURDAJEWICZ described correctly why this is not a bug. The `git` step intentionally is a simple subset of the full capabilities of the `checkout` step. Use the `checkout` step Paul Labedan you can find an example using the full checkout step to checkout a specific tag in the Jenkinsfile of my jenkins-bugs repository on the JENKINS-37050 branch. The default clone settings intentionally do not download tags so that less data is transferred for multi-branch pipelines that are building a single branch. The example file adds the CloneOption which download tags. Jenkins / JENKINS-37050 Pipeline Job Cannot Checkout Git Tag Change By: Mark Waite Status: Reopened Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Oleg Nenashev commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Régis Maura I am releasing what I have for this issue now. It is not a fix for the regression you reported, will follow-up on that separately. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51050) Blueocean paused for Input requested, but never asks for it
Title: Message Title
Miguel C updated an issue
Jenkins / JENKINS-51050
Blueocean paused for Input requested, but never asks for it
Change By:
Miguel C
To put simply we have a few jobs that we start from "blueocean" view.The job starts fine and moves onto "asking fro user input"The step will show the lines: {code:java}[Pipeline] input Input requested{code}But nothing is ever requested... If we switch to the "old UI" we can see the left link to provide input or do so from the console it slef self .
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-51050) Blueocean paused for Input requested, but never asks for it
Title: Message Title Miguel C updated an issue Jenkins / JENKINS-51050 Blueocean paused for Input requested, but never asks for it Change By: Miguel C Attachment: jenkis_blue_input.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51050) Blueocean paused for Input requested, but never asks for it
Title: Message Title
Miguel C updated an issue
Jenkins / JENKINS-51050
Blueocean paused for Input requested, but never asks for it
Change By:
Miguel C
To put simply we have a few jobs that we start from "blueocean" view.The job starts fine and moves onto "asking fro user input"The step will show the lines: ``` {code:java} [Pipeline] input Input requested {code} ``` But nothing is ever requested... If we switch to the "old UI" we can see the left link to provide input or do so from the console it slef .
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-51050) Blueocean paused for Input requested, but never asks for it
Title: Message Title Miguel C created an issue Jenkins / JENKINS-51050 Blueocean paused for Input requested, but never asks for it Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin, pipeline Created: 2018-04-30 20:14 Priority: Major Reporter: Miguel C To put simply we have a few jobs that we start from "blueocean" view. The job starts fine and moves onto "asking fro user input" The step will show the lines: ``` [Pipeline] input https://ci.plex.bz/blue/organizations/jenkins/QA%2Fqa-automation%20tools/detail/master-Jenkinsfile/430/pipeline#log-24Input requested ``` But nothing is ever requested... If we switch to the "old UI" we can see the left link to provide input or do so from the console it slef Add Comment
[JIRA] (JENKINS-51050) Blueocean paused for Input requested, but never asks for it
Title: Message Title Miguel C updated an issue Jenkins / JENKINS-51050 Blueocean paused for Input requested, but never asks for it Change By: Miguel C To put simply we have a few jobs that we start from "blueocean" view.The job starts fine and moves onto "asking fro user input"The step will show the lines:```[Pipeline] input [|https://ci.plex.bz/blue/organizations/jenkins/QA%2Fqa-automation%20tools/detail/master-Jenkinsfile/430/pipeline#log-24] Input requested```But nothing is ever requested... If we switch to the "old UI" we can see the left link to provide input or do so from the console it slef Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-42688) Provide a way to enable a post/* to run only under some context
Title: Message Title
Liam Newman edited a comment on JENKINS-42688
Re: Provide a way to enable a post/* to run only under some context
I'm sorry for not giving feedback on this earlier. Mostly this feels to me like one more step toward Scripted pipeline.What is the win here? Once a user hits this level of complexity, it makes more sense for them to move the functionality into a shared library where they can use if statements. Strong -1 for this feature as whole, sorry.Assuming we've already decided this feature is going to happen, the name {{condition}} is too generic/overloaded. We already call the status-based directives "conditions" in the documentation.{{conditional}}? {{complex}}? {{complex-condition}}? The fact that I can't think of a good term for this is further indication that this is not the place for this.[~abayer] Now that we hav have a JEP process, it probably makes sense to start what do you think of making language changes like this in to into JEPs. So I know it would add some additional overhead , that but it would also make people can be more aware of them upcoming plans and start participating in the design earlier.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-42688) Provide a way to enable a post/* to run only under some context
Title: Message Title Liam Newman commented on JENKINS-42688 Re: Provide a way to enable a post/* to run only under some context I'm sorry for not giving feedback on this earlier. Mostly this feels to me like one more step toward Scripted pipeline. What is the win here? Once a user hits this level of complexity, it makes more sense for them to move the functionality into a shared library where they can use if statements. Strong -1 for this feature as whole, sorry. Assuming we've already decided this feature is going to happen, the name condition is too generic/overloaded. We already call the status-based directives "conditions" in the documentation.conditional? complex? complex-condition? The fact that I can't think of a good term for this is further indication that this is not the place for this. Andrew Bayer Now that we hav a JEP process, it probably makes sense to start making language changes like this in to JEPs. So, that people can be aware of them and start participating in the design earlier. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51048) Setting workspace type to 'READONLY' doesn't work with servers running < 2017.1
Title: Message Title Aaron Ling updated an issue Jenkins / JENKINS-51048 Setting workspace type to 'READONLY' doesn't work with servers running < 2017.1 Change By: Aaron Ling Summary: Setting workspace type to 'READONLY' doesn't work for with servers running < 2017.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title John Mellor updated an issue Jenkins / JENKINS-51049 Folders Plugin GitHub Scanning Time not being copied into the Jobs Change By: John Mellor The Folders Plugin is not replicating required information into the sub-jobs.The Folders plugin is used in a Multi-Configuration project for multiple related jobs. The job configuration is specified in the folder, and prints-thru into the individual job configurations. However, the github scan time is not replicating into the jobs, and is instead defaulting to an unacceptable 1-hour for unknown reasons. It is not possible to alter the individual job configurations to compensate for plugin defects, as there is no save button on the sub-jobs. Screenshots are attached of (a) an offending folder an showing the requested 5-minute scan time, and (b) a typical folder sub- job showing the misconfiguration are attached and defaulting to 1-hour instead of the 5-minutes specified in the folder .This error makes the jobs almost unusable for normal development purposes, as source scans only occur a few times per day. Critical error. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Vivek Pandey commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API olamy there is also https://bitbucket.org/atlassian/atlassian-http. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title Vivek Pandey commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API olamy are you looking for https://bitbucket.org/atlassian/jira-rest-java-client? Its multi-module with sources for api api and core. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipDescription.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/ComputerOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerPropertyHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/AbstractOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java src/test/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobPropertyTest.java src/test/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/OwnerNodePropertyTest.java src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipPropertyTest.java http://jenkins-ci.org/commit/ownership-plugin/cb26e15b7b3d79da413b4c92deaf59b074f2a349 Log: Merge pull request #73 from oleg-nenashev/JENKINS-49744 JENKINS-49744 - Generalize permission checks via Ownership Helpers to support folders Compare: https://github.com/jenkinsci/ownership-plugin/compare/63d071ccf7d7...cb26e15b7b3d Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-50807) Add OwnershipHelperLocator implementations for Computer and Node classes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50807 Re: Add OwnershipHelperLocator implementations for Computer and Node classes Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/ComputerOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerPropertyHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java http://jenkins-ci.org/commit/ownership-plugin/408385f748e77240e4c7cdb379b646daeda2e455 Log: JENKINS-50807 - Add missing OwnershipHelperLocator implementations Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51049) Folders Plugin GitHub Scanning Time not being copied into the Jobs
Title: Message Title John Mellor created an issue Jenkins / JENKINS-51049 Folders Plugin GitHub Scanning Time not being copied into the Jobs Issue Type: Bug Assignee: Devin Nusbaum Attachments: Screenshot from 2018-04-30 15-35-34.png, Screenshot from 2018-04-30 15-36-14.png Components: cloudbees-folder-plugin Created: 2018-04-30 19:39 Environment: Cloudbees Folders Plugin 6.4 Jenkins 2.114 Ubuntu 14.04 w/ full updates Labels: plugin scm regression Priority: Blocker Reporter: John Mellor The Folders Plugin is not replicating required information into the sub-jobs. The Folders plugin is used in a Multi-Configuration project for multiple related jobs. The job configuration is specified in the folder, and prints-thru into the individual job configurations. However, the github scan time is not replicating into the jobs, and is instead defaulting to an unacceptable 1-hour for unknown reasons. It is not possible to alter the individual job configurations to compensate for plugin defects, as there is no save button on the sub-jobs. Screenshots of an offending folder an a job showing the misconfiguration are attached. This error makes the jobs almost unusable for normal development purposes, as source scans only occur a few times per day. Critical error.
[JIRA] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipDescription.java http://jenkins-ci.org/commit/ownership-plugin/bcc2c27aae247a8359a74c639eba54976a416be4 Log: JENKINS-49744 - Improve diagnostics messages when permission is missing Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkins/plugins/ownership/OwnershipDescription.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/ComputerOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/NodeOwnerPropertyHelper.java src/main/java/com/synopsys/arc/jenkins/plugins/ownership/util/AbstractOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/folders/FolderOwnershipHelper.java src/main/java/org/jenkinsci/plugins/ownership/model/runs/RunOwnershipHelper.java http://jenkins-ci.org/commit/ownership-plugin/2212e574d5bcd4a0552c882e066a0c5a8705bf02 Log: JENKINS-49744 - Generalize the permission handling logic using OwnershipHelper and locator extensions Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Code changed in jenkins User: Oleg Nenashev Path: src/test/java/org/jenkinsci/plugins/ownership/folders/FolderOwnershipPropertyTest.java http://jenkins-ci.org/commit/ownership-plugin/1f3d3846e50c2d994e99aa7eee485195e143862f Log: JENKINS-49744 - Add tests for FolderOwnership job property Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Code changed in jenkins User: Oleg Nenashev Path: src/test/java/com/synopsys/arc/jenkins/plugins/ownership/jobs/JobOwnerJobPropertyTest.java src/test/java/com/synopsys/arc/jenkins/plugins/ownership/nodes/OwnerNodePropertyTest.java http://jenkins-ci.org/commit/ownership-plugin/a5136e7ec830b40999cd320f322748ac801874bc Log: JENKINS-49744 - Annotate test methods created by @dwnusbaum Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51048) Setting workspace type to 'READONLY' doesn't work for servers running < 2017.1
Title: Message Title
Aaron Ling created an issue
Jenkins / JENKINS-51048
Setting workspace type to 'READONLY' doesn't work for servers running < 2017.1
Issue Type:
Bug
Assignee:
Unassigned
Components:
p4-plugin
Created:
2018-04-30 18:46
Environment:
P4 Plugin 1.8.9 p4 server 2016.2 Jenkins Enterprise 2.89.4.2-rolling
Priority:
Minor
Reporter:
Aaron Ling
I’m trying to implement readonly workspaces on one of our servers, which is running 2016.2. Readonly workspaces were introduced in 2015.2, so as expected, I can create them manually. However, if I go through the plugin, the workspace type is blank. I’ve uncovered this is because of a couple of if statements that restrict setting workspace type to server versions 2017.1 or later: In src\main\java\org\jenkinsci\plugins\p4\workspace\ManualWorkspaceImpl.java (Line 112) if (connection.getServerVersionNumber() >= 20171) { WorkspaceSpecType type = parseClientType(getSpec().getType()); implClient.setType(type.getId()); } [...] (Line 149) if (connection.getServerVersionNumber() >= 20171) { WorkspaceSpecType type = parseClientType(getSpec().getType()); [...] } I created a custom version of the plugin that replaces 20171 in both if statements with 20162, and everything works as expected – workspaces created through the plugin are correctly set as ‘READONLY’. The changes were added in this commit: https://github.com/jenkinsci/p4-plugin/commit/91e3a3c8284d2bb84061f1afe2d16f63aeb95ee7 for JENKINS-39753
[JIRA] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Code changed in jenkins User: Daniel Beck Path: content/_data/changelogs/weekly.yml http://jenkins-ci.org/commit/jenkins.io/62409d42a5769cac66337cbd4b5df5754f0e2384 Log: Merge pull request #1522 from daniel-beck/changelog-2.119-amended Remove JENKINS-9104 fix from release to unblock it Compare: https://github.com/jenkins-infra/jenkins.io/compare/58f029c79331...62409d42a576 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-9104) Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed
Title: Message Title SCM/JIRA link daemon commented on JENKINS-9104 Re: Visual studio builds started by Jenkins fail with "Fatal error C1090" because mspdbsrv.exe gets killed Code changed in jenkins User: Daniel Beck Path: content/_data/changelogs/weekly.yml http://jenkins-ci.org/commit/jenkins.io/0391fcb9b4c957e9e41fde03409de330a3de571d Log: Remove JENKINS-9104 fix from release to unblock it Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-46809) Allow sequential stages inside parallel in Declarative syntax
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46809 Re: Allow sequential stages inside parallel in Declarative syntax Code changed in jenkins User: Andrew Bayer Path: pipeline-model-api/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/ast/ModelASTStage.java pipeline-model-api/src/main/resources/ast-schema.json pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/model/Stage.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/JSONParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ModelParser.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/parser/RuntimeASTTransformer.groovy pipeline-model-definition/src/main/groovy/org/jenkinsci/plugins/pipeline/modeldefinition/validator/ModelValidatorImpl.groovy pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/Messages.properties pipeline-model-definition/src/main/resources/org/jenkinsci/plugins/pipeline/modeldefinition/ModelInterpreter.groovy pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AbstractModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/AgentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/BasicModelDefTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/DeclarativeUpgradeTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/EnvironmentTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/PostStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ToolsTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/ValidatorTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/WhenStageTest.java pipeline-model-definition/src/test/java/org/jenkinsci/plugins/pipeline/modeldefinition/parser/ExecuteConvertedTest.java pipeline-model-definition/src/test/resources/agentOnGroup.groovy pipeline-model-definition/src/test/resources/environmentInGroup.groovy pipeline-model-definition/src/test/resources/errors/emptyStagesInGroup.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesAndGroups.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesGroupsDeepNesting.groovy pipeline-model-definition/src/test/resources/errors/parallelStagesStepsAndGroups.groovy pipeline-model-definition/src/test/resources/errors/parallelStepsAndGroups.groovy pipeline-model-definition/src/test/resources/errors/topLevelStageGroupsDeepNesting.groovy pipeline-model-definition/src/test/resources/json/agentOnGroup.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesAndGroups.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesGroupsDeepNesting.json pipeline-model-definition/src/test/resources/json/errors/parallelStagesStepsAndGroups.json pipeline-model-definition/src/test/resources/json/errors/parallelStepsAndGroups.json pipeline-model-definition/src/test/resources/json/errors/topLevelStageGroupsDeepNesting.json pipeline-model-definition/src/test/resources/json/parallelStagesGroupsAndStages.json pipeline-model-definition/src/test/resources/json/topLevelStageGroup.json
[JIRA] (JENKINS-51046) Tool to incrementalify POM
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-51046 Tool to incrementalify POM Change By: Jesse Glick Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title simon Wall commented on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version I'm not sure if this is due to standard GutHub behaviour. As David Loomer has highlighted, the behaviour in the plugin has changed between versions. Using the odler verion, I can authenticate with the same gitHub Enterprise server using username and password, but with version 1.0.4 I only have success with an access token. It may be that there is also a relation to the version of GitHub enterprise that is running on the GH end, but there is definitely changes made in this plugin that causes the user's password to no longer be accepted. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title simon Wall edited a comment on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version I'm not sure if this is due to standard GutHub behaviour. As [~dloomer] has highlighted, the behaviour in the plugin has changed between versions. Using the odler verion older version , I can authenticate with the same gitHub Enterprise server using username and password, but with version 1.0.4 I only have success with an access token.It may be that there is also a relation to the version of GitHub enterprise that is running on the GH end, but there is definitely changes made in this plugin that causes the user's password to no longer be accepted. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51047) Multiple JVM crashes related to Trilead / SSH
Title: Message Title Andrew C updated an issue Jenkins / JENKINS-51047 Multiple JVM crashes related to Trilead / SSH See also https://issues.jenkins-ci.org/browse/JENKINS-41606 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-41606) Master SEGV caused by com.trilead.ssh2.crypto w/ java-1.8.0_102-b14
Title: Message Title Andrew C commented on JENKINS-41606 Re: Master SEGV caused by com.trilead.ssh2.crypto w/ java-1.8.0_102-b14 I just opened a possibly similar issue: https://issues.jenkins-ci.org/browse/JENKINS-51047 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51047) Multiple JVM crashes related to Trilead / SSH
Title: Message Title Andrew C created an issue Jenkins / JENKINS-51047 Multiple JVM crashes related to Trilead / SSH Issue Type: Bug Assignee: Unassigned Components: core Created: 2018-04-30 16:19 Priority: Minor Reporter: Andrew C Over the last couple months we have seen an uptick in Jenkins JVM crashes that seem to be related to Trilead. Here are three stack traces from crash logs: Stack: [0x7f5597b23000,0x7f5597c24000], sp=0x7f5597c22550, free space=1021k Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code) J 14468 C2 sun.security.provider.SHA5.implCompress([BI)V (331 bytes) @ 0x7f55ea496341 [0x7f55ea496060+0x2e1] J 18715 C2 sun.security.provider.DigestBase.engineUpdate([BII)V (189 bytes) @ 0x7f55eb87cba8 [0x7f55eb87c9c0+0x1e8] J 48093 C2 com.trilead.ssh2.transport.TransportConnection.receiveMessage([BII)I (470 bytes) @ 0x7f55f0bc7fd4 [0x7f55f0bc6e20+0x11b4] J 45325% C2 com.trilead.ssh2.transport.TransportManager.receiveLoop()V (549 bytes) @ 0x7f55eddc2d78 [0x7f55eddc2ca0+0xd8] j com.trilead.ssh2.transport.TransportManager$1.run()V+4 j java.lang.Thread.run()V+11 v ~StubRoutines::call_stub V [libjvm.so+0x65b9cb] V [libjvm.so+0x65cde7] V [libjvm.so+0x65d2a7] V [libjvm.so+0x6ac811] V [libjvm.so+0x9ebea5] V [libjvm.so+0x9ec168] V [libjvm.so+0x8ada22] C [libpthread.so.0+0x7aa1] Stack: [0x7fd9c44fe000,0x7fd9c45ff000], sp=0x7fd9c45fd420, free space=1021k Native frames: (J=compiled Java code,
[JIRA] (JENKINS-51047) Multiple JVM crashes related to Trilead / SSH
Title: Message Title Andrew C updated an issue Jenkins / JENKINS-51047 Multiple JVM crashes related to Trilead / SSH Change By: Andrew C Environment: Jenkins 2.89.4JRE version: OpenJDK Runtime Environment (8.0_161-b14) (build 1.8.0_161-b14)Java VM: OpenJDK 64-Bit Server VM (25.161-b14 mixed mode linux-amd64 compressed oops)running in an AWS EC2 instance Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title David Loomer commented on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version I'm not so sure about that explanation Raul Arabaolaza but I may be mistaken. First, the plugin code has definitely changed from 1.01 to 1.04: It used to call "GitHub.connectToEnterprise()" which I believe followed whatever configuration is set up for access, but now it calls "githubBuilder.withOAuthToken()". Second, I believe that latter method means that only a token will work now: https://github.com/jenkinsci/pipeline-githubnotify-step-plugin/blob/pipeline-githubnotify-step-1.0.4/src/main/java/org/jenkinsci/plugins/pipeline/githubstatusnotification/GitHubStatusNotificationStep.java#L249 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title Raul Arabaolaza commented on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version README updated, simon Wall Is better now? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title Raul Arabaolaza commented on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version Actually that is standard GitHub behaviour, nothing related to the plugin itself. Depending on you access configuration you may need the password or the access token, the plugin does not diferentiate between them it just yses it as is... The inline help says password or access token but I can easily update the readme also. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50575) Dash changed to underscore in custom prefix
Title: Message Title Mandy Prescott-Courville commented on JENKINS-50575 Re: Dash changed to underscore in custom prefix Yes, that's what I meant Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51021) plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version
Title: Message Title simon Wall commented on JENKINS-51021 Re: plugin reporting error "java.lang.IllegalArgumentException: The supplied credentials are invalid to login" on latest version Thanks David Loomer, changing the password to a personal access token has resolved the issue. Raul Arabaolaza, could the documentation for this plugin please be updated to state that the password in the Username andPassword credentialsId should be a personal access token rather than the user's actual password? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-47254) Support for building tags for Bitbucket Server/Cloud
Title: Message Title Arnaud Deprez edited a comment on JENKINS-47254 Re: Support for building tags for Bitbucket Server/Cloud Hi,Thanks to this new feature, I can discover tags and trigger build manually from Jenkins.Thanks for that!However, Jenkins does not trigger build when a new tag is created. It even does not register a new build for this new tag it unless I'm running the whole Organization scan.Doesn't it suppose to bring this feature ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-47254) Support for building tags for Bitbucket Server/Cloud
Title: Message Title Arnaud Deprez edited a comment on JENKINS-47254 Re: Support for building tags for Bitbucket Server/Cloud Hi,Thanks to this new plugin feature , I can discover tags and trigger build manually from Jenkins.Thanks for that!However, Jenkins does not trigger build when a new tag is created. It even does not register a new build for this new tag unless I'm running the whole Organization scan.Doesn't it suppose to bring this feature ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-47254) Support for building tags for Bitbucket Server/Cloud
Title: Message Title Arnaud Deprez commented on JENKINS-47254 Re: Support for building tags for Bitbucket Server/Cloud Hi, Thanks to this new plugin, I can discover tags and trigger build manually from Jenkins. Thanks for that! However, Jenkins does not trigger build when a new tag is created. It even does not register a new build for this new tag unless I'm running the whole Organization scan. Doesn't it suppose to bring this feature ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50658) xUnit does not support the flaky surefire tests generated by maven with rerun property
Title: Message Title Nikolas Falco resolved as Fixed Jenkins / JENKINS-50658 xUnit does not support the flaky surefire tests generated by maven with rerun property Change By: Nikolas Falco Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51046) Tool to incrementalify POM
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-51046 Tool to incrementalify POM Issue Type: Bug Assignee: Jesse Glick Components: plugin-pom Created: 2018-04-30 15:24 Priority: Minor Reporter: Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-50953) Tool to offer incremental updates
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50953 Tool to offer incremental updates Change By: Jesse Glick Summary: Consider creating separate deployment repository for master commits Tool to offer incremental updates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-26883) SEVERE: Restarting VM as requested by username
Title: Message Title Victor Martinez commented on JENKINS-26883 Re: SEVERE: Restarting VM as requested by username I just started to work on this ticket. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-26883) SEVERE: Restarting VM as requested by username
Title: Message Title Victor Martinez updated JENKINS-26883 Jenkins / JENKINS-26883 SEVERE: Restarting VM as requested by username Change By: Victor Martinez Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-26883) SEVERE: Restarting VM as requested by username
Title: Message Title Victor Martinez started work on JENKINS-26883 Change By: Victor Martinez Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-26883) SEVERE: Restarting VM as requested by username
Title: Message Title Victor Martinez assigned an issue to Victor Martinez Jenkins / JENKINS-26883 SEVERE: Restarting VM as requested by username Change By: Victor Martinez Assignee: Victor Martinez Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51045) Support user configuration in JSon format
Title: Message Title Ingo Rissmann started work on JENKINS-51045 Change By: Ingo Rissmann Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51045) Support user configuration in JSon format
Title: Message Title Ingo Rissmann created an issue Jenkins / JENKINS-51045 Support user configuration in JSon format Issue Type: Improvement Assignee: Ingo Rissmann Components: arachni-scanner-plugin Created: 2018-04-30 14:16 Priority: Minor Reporter: Ingo Rissmann Give users the possibility to add their own configuration in json format. Merge this configuration with the config fields. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50575) Dash changed to underscore in custom prefix
Title: Message Title Aleksi Simell commented on JENKINS-50575 Re: Dash changed to underscore in custom prefix "Tag values can have underscore." You mean to say tag values can have dashes? Otherwise this is already the functionality. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51044) Using non-pipeline directives in pipeline job definitions should result in warning or error
Title: Message Title Aaron Marasco updated an issue Jenkins / JENKINS-51044 Using non-pipeline directives in pipeline job definitions should result in warning or error Change By: Aaron Marasco Summary: Using conflicting non- pipeline directives in pipeline job definitions should result in warning or error Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51044) Using conflicting pipeline directives should result in error
Title: Message Title Aaron Marasco commented on JENKINS-51044 Re: Using conflicting pipeline directives should result in error More experimentation seems to imply the directives are always ignored in any pipelineJob, even if I don't set the definition - which also makes sense. These things are supposed to be in the groovy script, so are ignored and the user should be notified. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51044) Using conflicting pipeline directives should result in error
Title: Message Title Aaron Marasco created an issue Jenkins / JENKINS-51044 Using conflicting pipeline directives should result in error Issue Type: Bug Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2018-04-30 10:42 Environment: EnvInject 2.1.5 Job DSL 1.69 Jenkins 2.107.2 Priority: Minor Reporter: Aaron Marasco It seems that certain directives within a pipelineJob are totally ignored if using the definition directive to read in an external groovy script. At a minimum, it seems label and steps are, and possibly wrappers. For a new user (like me!) this can be frustrating. If a directive is invalid or ignored, there should be some message sent to the seed job's console (minimum) or the seed job should have result set to unstable/failed. Add Comment
[JIRA] (JENKINS-51038) Re-defining existing job loses environment variables
Title: Message Title Aaron Marasco commented on JENKINS-51038 Re: Re-defining existing job loses environment variables Since the queue command doesn't seem to be designed to pass parameters, with this not working, I'm running out of ideas on how to have a Job DSL launcher for a pipeline job work. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-48945) Testreport lacks of those test in which the hashcode of two different testsuite name coincide
Title: Message Title Sascha Friederich commented on JENKINS-48945 Re: Testreport lacks of those test in which the hashcode of two different testsuite name coincide is there a plan, when this bugfix will be released? (its not part of Version: 1.103) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50879) The secretVolume is not mounted to "jnlp" container in the multicontainer pod
Title: Message Title Roey Azroel commented on JENKINS-50879 Re: The secretVolume is not mounted to "jnlp" container in the multicontainer pod +1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51043) Update objects and dependency for Pipeline as a code flow
Title: Message Title Michael Seldin resolved as Fixed Jenkins / JENKINS-51043 Update objects and dependency for Pipeline as a code flow Change By: Michael Seldin Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51043) Update objects and dependency for Pipeline as a code flow
Title: Message Title Michael Seldin created an issue Jenkins / JENKINS-51043 Update objects and dependency for Pipeline as a code flow Issue Type: Bug Assignee: Ayellet Lazar Components: hp-application-automation-tools-plugin Created: 2018-04-30 08:01 Labels: 5.4 octane Priority: Blocker Reporter: Michael Seldin Octane plugin was crashing because of incompatability of pipeline as a code dependecy in the plugin org.jenkins-ci.plugins.pipeline-stage-view pipeline-rest-api the dependency was upgraded to 2.10 Add Comment
[JIRA] (JENKINS-37589) Replay link does not show up if Jenkinsfile had a syntax error
Title: Message Title Prince Raj Kumar updated an issue Jenkins / JENKINS-37589 Replay link does not show up if Jenkinsfile had a syntax error Change By: Prince Raj Kumar Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-48357) Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API
Title: Message Title olamy commented on JENKINS-48357 Re: Binary Compatibility between JIRA Plugin and Apache HttpComponents Client 4.x API too bad access denied to https://bitbucket.org/atlassian/atlassian-httpclient whereas the pom is here https://packages.atlassian.com/maven-external/com/atlassian/httpclient/atlassian-httpclient-parent/0.23.0/ Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-32866) Log Parser Plugin does not parse Pipeline console outputs
Title: Message Title Prince Raj Kumar updated an issue Jenkins / JENKINS-32866 Log Parser Plugin does not parse Pipeline console outputs Change By: Prince Raj Kumar Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-44623) JNLP slave fail to connect
Title: Message Title Liora Milbaum commented on JENKINS-44623 Re: JNLP slave fail to connect It was long time ago. That environment, no longer exists. But, I do remember that I had to configure ports 80 and 8080 and I have also configured port forwarding. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51042) I would like to span an new Slave pod on a near by K8S Cluster
Title: Message Title Chen Fliesher created an issue Jenkins / JENKINS-51042 I would like to span an new Slave pod on a near by K8S Cluster Issue Type: Improvement Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-04-30 06:29 Environment: My Azure data center has several k8s clusters. The main cluster contains a jenkins master, and is responsible of the CI. It creates a docker images, run Unit Test, Code Linting etc. Other k8s clusters are used to deploy and perform helm upgrade and run E2E tests. Priority: Major Reporter: Chen Fliesher I have a data center on Azure which have several kubernetes cluster. I would like to spawn a pod on a remote kubernetes cluster. This way I could deploy and run tests on a near by cluster. Is this feasible ? Add Comment
[JIRA] (JENKINS-51041) git-parameter-plugin: Tags are duplicated in pipeline
Title: Message Title bongyong choi updated an issue Jenkins / JENKINS-51041 git-parameter-plugin: Tags are duplicated in pipeline Change By: bongyong choi 1. create pipeline project2. set pipeline definition: pipeline script from scm3. add gitlab scm!Screenshot-2018-4-30 pipeline Config [Jenkins].png|width=458,height=328!4. add git parameter!Screenshot-2018-4-30 pipeline Config [Jenkins](1).png|width=399,height=318!5. Tags are duplicated (after first time build) !Screenshot-2018-4-30 Jenkins.png! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Tom Ghyselinck commented on JENKINS-50888 Re: NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Hi Sam Van Oort, Thank you for the explanation! Looking forward for the pull request Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Tom Ghyselinck assigned an issue to Sam Van Oort Jenkins / JENKINS-50888 NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Change By: Tom Ghyselinck Assignee: Tom Ghyselinck Sam Van Oort Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50888) NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information
Title: Message Title Tom Ghyselinck assigned an issue to Tom Ghyselinck Jenkins / JENKINS-50888 NullPointerException in org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$ConverterImpl.marshal when changing build information Change By: Tom Ghyselinck Assignee: Sam Van Oort Tom Ghyselinck Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50076) Unit Test for PropertyStatistics
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50076 Re: Unit Test for PropertyStatistics Code changed in jenkins User: Ullrich Hafner Path: src/main/java/io/jenkins/plugins/analysis/core/model/PropertyStatistics.java src/test/java/io/jenkins/plugins/analysis/core/model/PropertyStatisticsTest.java http://jenkins-ci.org/commit/analysis-core-plugin/c88399dc2df195f27275c59459d242e6e2ec4f06 Log: Merge pull request #121 from Martin4Prog/JENKINS-50076-NEW [FIXED JENKINS-50076] Added new tests for PropertyStatistics. Compare: https://github.com/jenkinsci/analysis-core-plugin/compare/c21578892de8...c88399dc2df1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50076) Unit Test for PropertyStatistics
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50076 Re: Unit Test for PropertyStatistics Code changed in jenkins User: Martin Path: src/main/java/io/jenkins/plugins/analysis/core/model/PropertyStatistics.java src/test/java/io/jenkins/plugins/analysis/core/model/PropertyStatisticsTest.java http://jenkins-ci.org/commit/analysis-core-plugin/cfc8cd512e25e4331705bae1d323717336c710c7 Log: JENKINS-50076 changed exception to match expectations. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50076) Unit Test for PropertyStatistics
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50076 Re: Unit Test for PropertyStatistics Code changed in jenkins User: Martin Path: src/test/java/io/jenkins/plugins/analysis/core/model/PropertyStatisticsTest.java http://jenkins-ci.org/commit/analysis-core-plugin/c82b43ae7aba3138b8eef64b608b21607563 Log: JENKINS-50076 created new unit-test for the class Propertystatistics. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
