[JIRA] (JENKINS-50501) Jenkins won't load after updating maven plugin
Title: Message Title Tomas Norre Mikkelsen commented on JENKINS-50501 Re: Jenkins won't load after updating maven plugin Igor Koyfman Thanks for sharing.. Can you tell a little more about which files and where they are located ? 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-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman resolved as Fixed The issue was due to locked up tmp files. Jenkins / JENKINS-50501 Jenkins won't load after updating maven plugin Change By: Igor Koyfman 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-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman updated an issue Jenkins / JENKINS-50501 Jenkins won't load after updating maven plugin Change By: Igor Koyfman Comment: The issue was due to locked up tmp files. 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-50501) Jenkins won't load after updating maven plugin
Title: Message Title Igor Koyfman commented on JENKINS-50501 Re: Jenkins won't load after updating maven plugin I got the issue fixed after deleting some locked up tmp files. 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-50673) Jenkins job in not getting trigger if another system did commit
Title: Message Title Priyanga G closed an issue as Not A Defect Jenkins / JENKINS-50673 Jenkins job in not getting trigger if another system did commit Change By: Priyanga G Status: Open Closed Assignee: Ivan Fernandez Calvo Priyanga G Resolution: Not A Defect 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-36089) Pipeline support for Promoted Builds Plugin
Title: Message Title lsb want commented on JENKINS-36089 Re: Pipeline support for Promoted Builds Plugin Jesse Glick Only if you put input inside node, which generally you should not. An input paused at top level can sit there for days without occupying any resources on Jenkins (not even a native Thread). The workspace of next stage will be reallocated if I put directive input into a standalone stage and set up agent as none, but my next stage need use the same workspace with the previous stage. this is my difficulty, otherwise, I need set up a pipeline global agent, then directive input will occupy executor. 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-50725) Active Choice Reactive Parameter list without scroll bar
Title: Message Title Jani Rautio created an issue Jenkins / JENKINS-50725 Active Choice Reactive Parameter list without scroll bar Issue Type: Improvement Assignee: Bruno P. Kinoshita Attachments: option_off.jpg, option_on.jpg Components: active-choices-plugin Created: 2018-04-11 05:14 Environment: Jenkins 2.73.2 Active Choices Plug-in 2.1 Browser: chrome or firefox Priority: Minor Reporter: Jani Rautio Adding functinality\option to 'Active Choice Reactive Parameter' to disable scroll bar if list is long => show all list values without scroll bar no matter how long list is. Option OFF (current operation mode): Option ON: Add Comment
[JIRA] (JENKINS-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Alex Earl commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together token-macro 2.5 has been released with this fix 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-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Alex Earl closed an issue as Fixed Jenkins / JENKINS-49746 Regex returns more matches than it should if errors are close together Change By: Alex Earl Status: Open Closed 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-48437) Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId
Title: Message Title Jon B commented on JENKINS-48437 Re: Docker Pipeline Plugin withRegistry and Authorize Plugin fails to get credentialsId I'm seeing this error too but I'm not 100% sure if its the same exact problem or not. In my case, I a using the aws credentials plugin in order to leverage the fact my ec2 hosts have an AWS role assigned to them. I fill out the credential with the correct role and then I save it in the global credential namespace, and then when i try it use it, I get: ERROR: Could not find credentials matching JENKINS_SLAVE_AWS_ROLE 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-41854) Contextualize a fresh FilePath after an agent reconnection
Title: Message Title Basil Crow commented on JENKINS-41854 Re: Contextualize a fresh FilePath after an agent reconnection Is there any workaround for this issue? Is there any way for me to run my scripted pipeline on a node without using the problematic PlaceholderExecutable? 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-50655) Add support for folder credentials
Title: Message Title Allan BURDAJEWICZ updated JENKINS-50655 Jenkins / JENKINS-50655 Add support for folder credentials Change By: Allan BURDAJEWICZ 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-50655) Add support for folder credentials
Title: Message Title Allan BURDAJEWICZ assigned an issue to Allan BURDAJEWICZ Jenkins / JENKINS-50655 Add support for folder credentials Change By: Allan BURDAJEWICZ Assignee: Allan BURDAJEWICZ 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-50655) Add support for folder credentials
Title: Message Title Allan BURDAJEWICZ started work on JENKINS-50655 Change By: Allan BURDAJEWICZ 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-50652) Post stages are incorrectly handled
Title: Message Title Steve Todorov commented on JENKINS-50652 Re: Post stages are incorrectly handled Sorry for the delayed reply. The issue is that both the post-abort and post-failure steps are triggered when you abort a build. What should have happened was to receive only post-abort when you hit the Abort button. In our case we are trying to execute specific steps only for post-abort and other specific steps only for post-failure, however we end up having both steps for post-abort and post-failure executed which is messing things up. 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-50681) Startup Trigger label list doesnt work with master
Title: Message Title Emory Penney commented on JENKINS-50681 Re: Startup Trigger label list doesnt work with master I've pushed a change to master that fixes the issue for me in my environment, are you able to verify this fixes the issue for you? 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-50681) Startup Trigger label list doesnt work with master
Title: Message Title Emory Penney updated JENKINS-50681 Jenkins / JENKINS-50681 Startup Trigger label list doesnt work with master Change By: Emory Penney 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-38046) Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline
Title: Message Title Taylor Patton commented on JENKINS-38046 Re: Gerrit Trigger Plugin Should be a Source for Multibranch Pipeline Will this capability be added to gerrit-trigger-plugin? I am weary of installing another gerrit plugin and having 2 ways of configuring pipelines (multi-branch and regular). 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-50681) Startup Trigger label list doesnt work with master
Title: Message Title Emory Penney started work on JENKINS-50681 Change By: Emory Penney 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-50693) Script to interoperate with maven-release-plugin
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50693 Script to interoperate with maven-release-plugin Change By: Jesse Glick Summary: Investigate interaction Script to interoperate with maven-release-plugin Issue Type: Task Story Component/s: 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-50693) Investigate interaction with maven-release-plugin
Title: Message Title Jesse Glick stopped work on JENKINS-50693 Change By: Jesse Glick 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-50693) Investigate interaction with maven-release-plugin
Title: Message Title Jesse Glick commented on JENKINS-50693 Re: Investigate interaction with maven-release-plugin If interoperability with MRP is necessary, which it surely will be for Jenkins core at least, then perhaps we need to have a tool to fix up the POM after a release as in JENKINS-50699 and require that to be run. 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-50724) Verify applicability of versions:display-dependency-updates
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50724 Verify applicability of versions:display-dependency-updates Issue Type: Task Assignee: Jesse Glick Components: plugin-pom Created: 2018-04-10 22:50 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
[JIRA] (JENKINS-50723) Consider impact on CERT workflows
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-50723 Consider impact on CERT workflows Issue Type: Task Assignee: Jesse Glick Components: plugin-pom Created: 2018-04-10 22:45 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-50693) Investigate interaction with maven-release-plugin
Title: Message Title Jesse Glick commented on JENKINS-50693 Re: Investigate interaction with maven-release-plugin It gets somewhat confused. As seen here, the right version is actually released, but the “next development iteration” is not configured correctly and would require manual cleanup before again being ready for publishing to Incrementals. 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-44704) specify vault path as a parameter
Title: Message Title Peter Tierno started work on JENKINS-44704 Change By: Peter Tierno 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-44704) specify vault path as a parameter
Title: Message Title Peter Tierno updated JENKINS-44704 Jenkins / JENKINS-44704 specify vault path as a parameter Change By: Peter Tierno Status: Reopened 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-44704) specify vault path as a parameter
Title: Message Title Peter Tierno commented on JENKINS-44704 Re: specify vault path as a parameter Padmaja SasidharanI was able to reproduce this issue. will look into it. thanks for reporting. 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-44704) specify vault path as a parameter
Title: Message Title Peter Tierno closed an issue as Fixed Jenkins / JENKINS-44704 specify vault path as a parameter Change By: Peter Tierno Status: Open Closed 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-44704) specify vault path as a parameter
Title: Message Title Peter Tierno reopened an issue Jenkins / JENKINS-44704 specify vault path as a parameter Change By: Peter Tierno Resolution: Fixed Status: Closed Reopened 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-48892) Vault plugin exits on specifying a secret that is a large base64 encoded value
Title: Message Title Peter Tierno commented on JENKINS-48892 Re: Vault plugin exits on specifying a secret that is a large base64 encoded value Raghu I am going to attempt to duplicate this during the week. Will follow up. thanks for reporting. 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-48892) Vault plugin exits on specifying a secret that is a large base64 encoded value
Title: Message Title Peter Tierno reopened an issue Jenkins / JENKINS-48892 Vault plugin exits on specifying a secret that is a large base64 encoded value Change By: Peter Tierno Resolution: Fixed Status: Closed Reopened 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-48892) Vault plugin exits on specifying a secret that is a large base64 encoded value
Title: Message Title Peter Tierno closed an issue as Fixed Jenkins / JENKINS-48892 Vault plugin exits on specifying a secret that is a large base64 encoded value Change By: Peter Tierno Status: Open Closed 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-44801) Support wildcards for Vault module 'Key name'
Title: Message Title Peter Tierno closed an issue as Won't Do Jenkins / JENKINS-44801 Support wildcards for Vault module 'Key name' Change By: Peter Tierno Status: Open Closed Resolution: Won't Do 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-44801) Support wildcards for Vault module 'Key name'
Title: Message Title Peter Tierno commented on JENKINS-44801 Re: Support wildcards for Vault module 'Key name' Otto Helweg I'm going to close this. I think considering the nature of vault, knowing the name of the key before hand is an important security consideration. 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-44900) Getting 404 Error While Reading Vault Secret
Title: Message Title Peter Tierno commented on JENKINS-44900 Re: Getting 404 Error While Reading Vault Secret Otto Helweg I have not been able to replace this on the *nix side. Will be testing on the windows end in the coming weeks. 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-44900) Getting 404 Error While Reading Vault Secret
Title: Message Title Peter Tierno started work on JENKINS-44900 Change By: Peter Tierno 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-50693) Investigate interaction with maven-release-plugin
Title: Message Title Jesse Glick started work on JENKINS-50693 Change By: Jesse Glick 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-50689) Document opt-in process
Title: Message Title Jesse Glick resolved as Fixed Jenkins / JENKINS-50689 Document opt-in process Change By: Jesse Glick Status: In Progress 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-49744) Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API
Title: Message Title Andrew Barnish commented on JENKINS-49744 Re: Users with Manage Ownership permissions are unable to change Foler ownership from CLI/REST API Oleg Nenashev, is there any progress with this issue? Do you require any further information to help with the debug? 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Michael Krotscheck edited a comment on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Well, the short answer is no: I can't set up a whole public infrastructure for you that will allow you to test this use case. I mucked around to see if I can get a similar effect by trying this, however I can't seem to get the GIT_COMMIT environment variable into the declarative pipeline itself - that's probably an artifact of the Gerrit plugin and how it assigns a trigger events' parameters to a job.{{libraries \{}}{{ lib("kangaroo-jenkins@$\{env.GIT_COMMIT}")}}{{}}}But, what I _can_ do, is tell you where the "bug" is and the appropriate gerrit workaround. The issue seems to be in AbstractGitSCMSource around 'Could not find a branch containing' The assumption the plugin makes is that remote branches will _all_ live under refs/remotes/$\{context}/, and filters out anything else. As such, gerritt's usage of `refs/changes/` etc is entirely ignored.The workaround is - when declaring the library in jenkins - to also include the following refspec mappings. In our case, we're doing this in the System Library Configuration:{code:java}+refs/heads/*:refs/remotes/@{remote}/* # Remote master, for regular library usage.+refs/changes/*:refs/changes/* # So that rev-parse works on gerrit refspec parameters.+refs/changes/*:refs/remotes/@{remote}/changes/* # To bypass the filter exclusion in AbstractGitSCMSource{code}The above makes the current plugin work for me (And now I know far more about refspecs than I ever wanted). {color:#ff}EDIT: {color:#33}Also, I don't see why this couldn't work for bitbucket, github, etc. Others would have to confirm that though.{color}{color}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Michael Krotscheck commented on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Well, the short answer is no: I can't set up a whole public infrastructure for you that will allow you to test this use case. I mucked around to see if I can get a similar effect by trying this, however I can't seem to get the GIT_COMMIT environment variable into the declarative pipeline itself - that's probably an artifact of the Gerrit plugin and how it assigns a trigger events' parameters to a job. libraries { lib("kangaroo-jenkins@${env.GIT_COMMIT}") } But, what I can do, is tell you where the "bug" is and the appropriate gerrit workaround. The issue seems to be in AbstractGitSCMSource around 'Could not find a branch containing' The assumption the plugin makes is that remote branches will all live under refs/remotes/${context}/, and filters out anything else. As such, gerritt's usage of `refs/changes/` etc is entirely ignored. The workaround is - when declaring the library in jenkins - to also include the following refspec mappings. In our case, we're doing this in the System Library Configuration:
+refs/heads/*:refs/remotes/@{remote}/* # Remote master, for regular library usage.
+refs/changes/*:refs/changes/* # So that rev-parse works on gerrit refspec parameters.
+refs/changes/*:refs/remotes/@{remote}/changes/* # To bypass the filter exclusion in AbstractGitSCMSource
The above makes the current plugin work for me (And now I know far more about refspecs than I ever wanted).
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50458) JNLP agent died while reconnecting to master with java.lang.ClassNotFoundException: jenkins.slaves.restarter.JnlpSlaveRestarterInstaller
Title: Message Title Philipp Garbe commented on JENKINS-50458 Re: JNLP agent died while reconnecting to master with java.lang.ClassNotFoundException: jenkins.slaves.restarter.JnlpSlaveRestarterInstaller Had a similar issue and updating the agent (to 3.19) fixed 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-49332) Jenkins unable to manage webhooks of Github organization
Title: Message Title Samuel Loretan commented on JENKINS-49332 Re: Jenkins unable to manage webhooks of Github organization Also encountering this same error. Is there a workaround that can be used while this issue is being worked on, or a previous version of a plugin that doesn't exhibit this behavior? 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-49928) Add editor ATH coverage for changing agent settings in a Jenkinsfile
Title: Message Title Karl Shultz updated JENKINS-49928 Jenkins / JENKINS-49928 Add editor ATH coverage for changing agent settings in a Jenkinsfile Change By: Karl Shultz 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-49930) Add editor ATH coverage for setting and changing environment variables
Title: Message Title Karl Shultz updated JENKINS-49930 Jenkins / JENKINS-49930 Add editor ATH coverage for setting and changing environment variables Change By: Karl Shultz 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-50604) Modify existing Bitbucket ATH test to perform end to end create flow
Title: Message Title Karl Shultz resolved as Done Merged 1713. Jenkins / JENKINS-50604 Modify existing Bitbucket ATH test to perform end to end create flow Change By: Karl Shultz Status: In Progress Resolved Resolution: Done 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-49746) Regex returns more matches than it should if errors are close together
Title: Message Title SCM/JIRA link daemon commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together Code changed in jenkins User: Alex Earl Path: src/main/java/org/jenkinsci/plugins/tokenmacro/impl/BuildLogRegexMacro.java src/test/java/org/jenkinsci/plugins/tokenmacro/impl/BuildLogRegexMacroTest.java src/test/resources/org/jenkinsci/plugins/tokenmacro/impl/JENKINS-49746-input.txt src/test/resources/org/jenkinsci/plugins/tokenmacro/impl/JENKINS-49746-output.txt http://jenkins-ci.org/commit/token-macro-plugin/135d69852894a4349446e7b78a244abe6b401102 Log: Fix JENKINS-49746 Added greedy parameter to break out of match checking when numMatches reaches maxMatches 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-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Alex Earl commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together I am going to introduce a new parameter to this macro named "greedy" which will default to true (the current behavior). If greedy is set to false, then the macro will kick out of the check when numMatches >= maxMatches, which matches the behavior you are looking for. So, when I release the new version, you should add greedy=false to your macro usage. 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-50722) origins field is never saved or I do not understand its role
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-50722 origins field is never saved or I do not understand its role Issue Type: Task Assignee: Unassigned Components: metrics-plugin Created: 2018-04-10 19:28 Priority: Minor Reporter: Baptiste Mathus How to reproduce Open /configure and create an access key set origins to something else than the default value of * Save Open /configure and see that origins stays to * whatever you do Expected The field origins should be saved, or the documentation should clarify at least its role and expected values, if possibly the change gets reverted because using a bad format. Add Comment
[JIRA] (JENKINS-50722) origins field is never saved
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50722 origins field is never saved Change By: Baptiste Mathus Labels: essentials essentials-triggered 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-50722) origins field is never saved
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50722 origins field is never saved Change By: Baptiste Mathus Summary: origins field is never saved or I do not understand its role 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-50714) SonarQube Scanner 2.7 blocks Jenkins start
Title: Message Title todd bastress commented on JENKINS-50714 Re: SonarQube Scanner 2.7 blocks Jenkins start JENKINS 50663 - The fix might be in 2.7.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-41873) NPE when using HockeyAppPlugin with HTTP Proxy
Title: Message Title Mez Pahlan commented on JENKINS-41873 Re: NPE when using HockeyAppPlugin with HTTP Proxy Am I correct in thinking that a full fix also requires https://github.com/jenkinsci/hockeyapp-plugin/pull/47 to be merged? 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title Mark Waite commented on JENKINS-48061 Re: git plugin 3.6.4 regression with shared libraries Michael Krotscheck can you provide detailed steps that describe your working case, preferably using a public repository and without requiring that I install and configure a Gerrit server? I can't verify it works (or fails) at the moment, because it is not apparent to me how to duplicate the case you're describing. I could spend hours guessing, with the risk of wrong guesses, or I could follow steps you provide to reduce my guessing. I appreciate the desire to have the gerrit use case work, but I'm not yet sure that the gerrit use case should be done as a standard part of the plugin, rather than as an extension point that is enabled by installing an additional plugin to implement that extension. The more we can explore the use case you've been using, the better we are able to understand the best location to modify. 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-50716) Include scm/tag in flattened POM
Title: Message Title
Jesse Glick updated an issue
Jenkins / JENKINS-50716
Include scm/tag in flattened POM
Change By:
Jesse Glick
Would be useful for PCT and generally other tools. Might require changes to {{flatten-maven-plugin}}.
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-41873) NPE when using HockeyAppPlugin with HTTP Proxy
Title: Message Title Mez Pahlan commented on JENKINS-41873 Re: NPE when using HockeyAppPlugin with HTTP Proxy Can we get an update on this please. 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-50558) Valgrind plugin results error
Title: Message Title Pieter Duchi commented on JENKINS-50558 Re: Valgrind plugin results error Also saw the same issue on our CI-server 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-50694) Draft process JEP
Title: Message Title Jesse Glick started work on JENKINS-50694 Change By: Jesse Glick 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-50721) Ensure that the Evergreen backend is using a configured secret for JWT
Title: Message Title R. Tyler Croy created an issue Jenkins / JENKINS-50721 Ensure that the Evergreen backend is using a configured secret for JWT Issue Type: Bug Assignee: R. Tyler Croy Components: essentials Created: 2018-04-10 17:56 Priority: Minor Reporter: R. Tyler Croy Just a reminder not to leave this set to hello before deployment Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-38582) Add support for node online trigger
Title: Message Title Emory Penney closed an issue as Fixed Jenkins / JENKINS-38582 Add support for node online trigger Change By: Emory Penney Status: Resolved Closed 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-20718) Add Documentation and help for startup-trigger-plugin
Title: Message Title Emory Penney closed an issue as Fixed Jenkins / JENKINS-20718 Add Documentation and help for startup-trigger-plugin Change By: Emory Penney Status: Resolved Closed 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-32659) Cannot start a job located in a Folder
Title: Message Title Emory Penney closed an issue as Fixed Jenkins / JENKINS-32659 Cannot start a job located in a Folder Change By: Emory Penney Status: Resolved Closed 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-22422) Make the name of the node that trigger the startup job available
Title: Message Title Emory Penney closed an issue as Fixed Jenkins / JENKINS-22422 Make the name of the node that trigger the startup job available Change By: Emory Penney Status: Resolved Closed 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-16841) Add delay to startup trigger
Title: Message Title Emory Penney closed an issue as Fixed Jenkins / JENKINS-16841 Add delay to startup trigger Change By: Emory Penney Status: Resolved Closed 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-40823) pipeline job isn't triggered when initiated by startup trigger
Title: Message Title Emory Penney closed an issue as Fixed This issue has been resolved in 2.8 for about a year, marking it closed. Jenkins / JENKINS-40823 pipeline job isn't triggered when initiated by startup trigger Change By: Emory Penney Status: Resolved Closed 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-40823) pipeline job isn't triggered when initiated by startup trigger
Title: Message Title Emory Penney commented on JENKINS-40823 Re: pipeline job isn't triggered when initiated by startup trigger Typically the XML looks something like this: "startup-trigger-plugin@2.8"> build_pool_A build_pool_B 5 label ON_CONNECT 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-49023) Cannot upload file using cifs-plugin
Title: Message Title Alex Earl commented on JENKINS-49023 Re: Cannot upload file using cifs-plugin I believe I have a fix for this, I need to test out some stuff and make sure. 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-49304) Not able to execute sudo command on ssh slave machine
Title: Message Title Alex Earl commented on JENKINS-49304 Re: Not able to execute sudo command on ssh slave machine If sudo isn't in the path, then it won't work. You would need to specify the full path to sudo 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-40831) Make the name of the node that triggered the startup job available via environment
Title: Message Title Emory Penney closed an issue as Fixed Change has been in for a year I've heard no complaints, closing this ticket. Jenkins / JENKINS-40831 Make the name of the node that triggered the startup job available via environment Change By: Emory Penney Status: Resolved Closed 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-49582) uninformative "Failure" error message when publish-over-ssh fails due to disk space on destination
Title: Message Title Alex Earl resolved as Not A Defect Jenkins / JENKINS-49582 uninformative "Failure" error message when publish-over-ssh fails due to disk space on destination Change By: Alex Earl Status: Open Resolved Resolution: Not A Defect 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-48061) git plugin 3.6.4 regression with shared libraries
Title: Message Title
Michael Krotscheck commented on JENKINS-48061
Re: git plugin 3.6.4 regression with shared libraries
Another +1 here for the gerrit use case. We run our shared jenkins groovy library through CI/CD testing before merging to master, to make sure we don't introduce regressions. That requires checking out either based on the gerrit refspec (`refs/changes/*`) or directly on the sha from one of those refspecs. Neither of these works anymore. Our current system jenkins library configuration for refspecs is:
+refs/heads/:refs/remotes/@{remote}/
+refs/changes/:refs/changes/
Relevant log output: using GIT_SSH to set credentials Key to access gerrit > git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ +refs/changes/:refs/changes/ > git rev-parse refs/changes/58/30058/11^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains d471affea1e4847a3d06d974e373632181ff5872 # timeout=10 Could not find a branch containing commit d471affea1e4847a3d06d974e373632181ff5872 I've played around with various different refspec structures, but nothing obvious seems to 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
[JIRA] (JENKINS-46794) Dynamic secrets should optionally be revoked after build wrapper completes
Title: Message Title Peter Tierno resolved as Done Jenkins / JENKINS-46794 Dynamic secrets should optionally be revoked after build wrapper completes Change By: Peter Tierno Status: In Progress Resolved Resolution: Done 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-30744) multibranch issues if branch contains /
Title: Message Title Varun Reddy commented on JENKINS-30744 Re: multibranch issues if branch contains / Yes we are using git-flow and we are having same above issue as Philip O'Gorman . Is there another defect that we need to track this issue? 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-30744) multibranch issues if branch contains /
Title: Message Title Philip O'Gorman commented on JENKINS-30744 Re: multibranch issues if branch contains / I couldn't figure this out either. If we use gitflow - we have to make sure that we don't use the default branch names: feature/myfeat bug/themess I don't know why this issue is marked as closed? What are we missing here? 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-30744) multibranch issues if branch contains /
Title: Message Title Varun Reddy commented on JENKINS-30744 Re: multibranch issues if branch contains / Is this issue being addressed in the coming release? Or is this has to be fixed by the build tools? In this msbuild and nuget.exe? 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-46794) Dynamic secrets should optionally be revoked after build wrapper completes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46794 Re: Dynamic secrets should optionally be revoked after build wrapper completes Code changed in jenkins User: Peter Tierno Path: src/test/java/com/datapipe/jenkins/vault/VaultBuildWrapperWithMockAccessor.java src/test/java/com/datapipe/jenkins/vault/it/VaultConfigurationIT.java src/test/java/com/datapipe/jenkins/vault/it/folder/FolderIT.java http://jenkins-ci.org/commit/hashicorp-vault-plugin/7f3e243de6832658aef421a3949d2da779e199ec Log: JENKINS-46794 Fix tests 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-46794) Dynamic secrets should optionally be revoked after build wrapper completes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46794 Re: Dynamic secrets should optionally be revoked after build wrapper completes Code changed in jenkins User: Peter Tierno Path: src/main/java/com/datapipe/jenkins/vault/VaultAccessor.java http://jenkins-ci.org/commit/hashicorp-vault-plugin/d10c59afc690d54a14a40a0a02d583e235e7f4e1 Log: JENKINS-46794 transient fields in VaultAccessor com.bettercloud.vault.Vault and com.bettercloud.vault.VaultConfig are not Serializable. 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-46794) Dynamic secrets should optionally be revoked after build wrapper completes
Title: Message Title SCM/JIRA link daemon commented on JENKINS-46794 Re: Dynamic secrets should optionally be revoked after build wrapper completes Code changed in jenkins User: Peter Tierno Path: src/main/java/com/datapipe/jenkins/vault/VaultAccessor.java http://jenkins-ci.org/commit/hashicorp-vault-plugin/92717cb5552e6c2ca1a5495ef9a7b72a43d85029 Log: JENKINS-46794 Add serialVersionUID to VaultAccessor 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value i have no other values set in the pod template other then the container definition. i am currently using version 0.11 - i had tried newer 1.x versions but had to roll back b/c of that issue where an additional container was spun up which i believe was fixed in 1.3.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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Jae Gangemi updated an issue Jenkins / JENKINS-50525 Error When Provisioning Slave: mountPath: Required value Change By: Jae Gangemi Attachment: image-2018-04-10-10-48-36-384.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-46794) Dynamic secrets should optionally be revoked after build wrapper completes
Title: Message Title Peter Tierno commented on JENKINS-46794 Re: Dynamic secrets should optionally be revoked after build wrapper completes Going to stick with this NOT being optional and have dynamic secrets leases revoked after build wrapper execution. This can be revisited if needed. 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-50597) Verify behavior of timeouts, interrupts, and network disconnections in S3 storage
Title: Message Title Carlos Sanchez commented on JENKINS-50597 Re: Verify behavior of timeouts, interrupts, and network disconnections in S3 storage I'll add that we need to make sure calls to AWS APIs are retried with backoff given my previous experience 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-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title Steven Foster commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Does this only work on environment variables configured on the node in jenkins? and so wouldn't work for non-static agents i.e. launched from cloud provider? Or does it work on environment variables set on the agent itself? 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-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title
ritica r updated an issue
Jenkins / JENKINS-50605
Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Change By:
ritica r
{{Jenkins}} version 2.114 (upgraded from 2.107.1 to try to resolve issue) is running builds but they seem to disappear from the Dashboard after a restart. I have Jenkins setup on {{Linux}} and all the log is present under {{$\{JENKINS_HOME}/jobs/$\{ITEM_FULL_NAME}/builds}}I have tried Reload Configuration from Disk with following set in {{/etc/sysconfig/jenkins}}\{\{JENKINS_JAVA_OPTIONS="-Djava.awt.headless=true }}Below is build and workspace directory settings: \{\{ Workspace Root Directory :$\{JENKINS_HOME}/workspace/$\{ITEM_FULL_NAME} Build Record Root Directory: $\{ JENKINS_HOME ITEM_ROOTDIR }/ jobs/$\{ITEM_FULL_NAME}/ builds }} Below you can see the build number 117 and 118 for one of my jobs, but still, the lastFailedBuild, lastStableBuild , lastSuccessfulBuild are set to -1, which doesn't existdrwxr-xr-x 4 jenkins jenkins 4096 Apr 2 20:17 117 drwxr-xr-x 4 jenkins jenkins 4096 Apr 3 20:17 118 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 11:09 lastFailedBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 10:44 lastStableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 4 03:21 lastSuccessfulBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnstableBuild -> -1 lrwxrwxrwx 1 jenkins jenkins 2 Apr 3 10:58 lastUnsuccessfulBuild -> -1 I have also set the{{Discard Old Builds Slicer - Days to keep artifacts as 30 Discard Old Builds Slicer - Max # of builds to keep as 40}}I ran the jenkins-job-checker[ [https://github.com/docwhat/jenkins-job-checker] ] on one of the jobs and found the following : Problem: NOTLINK: The number link builds/1 is not a symlink! Problem: NOTLINK: The number link builds/2 is not a symlink! Problem: NOTLINK: The number link builds/3 is not a symlink! Proposal: Archive non-link builds/1 Proposal: Archive non-link builds/2 {{Proposal: Archive non-link builds/3}} Really appreaciate some help
Add Comment
[JIRA] (JENKINS-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title ritica r assigned an issue to Unassigned Jenkins / JENKINS-50605 Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server Change By: ritica r Assignee: Andrew Bayer 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-45022) Pipeline duration should not include the time it was paused for input or waiting on resources
Title: Message Title Daniel Spencer commented on JENKINS-45022 Re: Pipeline duration should not include the time it was paused for input or waiting on resources Has there been any progress on 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-50605) Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server
Title: Message Title ritica r assigned an issue to Andrew Bayer Jenkins / JENKINS-50605 Jenkins build history disappears after reload config from disk, restart/start application, and restart managed server Change By: ritica r Assignee: Andrew Bayer 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-50720) Sonarqube Scanner 2.7 is ignoring the Server URL setting in Jenkins config when checking quality gate
Title: Message Title David Sanftenberg created an issue Jenkins / JENKINS-50720 Sonarqube Scanner 2.7 is ignoring the Server URL setting in Jenkins config when checking quality gate Issue Type: Bug Assignee: Sonar Team Components: sonar Created: 2018-04-10 15:54 Environment: Sonarqube scanner 2.7 Jenkins 2.107.1 (docker) Priority: Major Reporter: David Sanftenberg The Sonarqube scanner is ignoring the Server URL parameter in the Jenkins config when querying Sonar for the quality gate status. It is using Sonar's own address instead. I have an IP address set in Jenkins (as the intranet DNS will not resolve there), whereas for users I have a friendly hostname set in Sonar. Jenkins tries to resolve the friendly hostname instead of the Server URL I specify, which fails, and breaks the build. I've reverted back to 2.6.x for now. Add Comment
[JIRA] (JENKINS-50635) NUnit plugin does not fail build on test-runner error
Title: Message Title Alex Earl commented on JENKINS-50635 Re: NUnit plugin does not fail build on test-runner error I don't think failing the build would be correct for everyone, I would propose treating Error status as a failing test and mark the build as unstable as is done for failing tests. 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-50633) JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting
Title: Message Title Oleg Nenashev commented on JENKINS-50633 Re: JEP-200 - org.apache.maven.model.Model might be dangerous, so rejecting I fixed something && clearly understand why this issue may happen. So with this issue I would rather appreciate testing of the https://github.com/jenkinsci/pipeline-utility-steps-plugin/pull/46 pull request (you will still need to run commands in NonCPS there). For JENKINS-50632 an info would be useful, because I do not see how to proceed there 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-48939) PRQA Plugin is affected by JEP-200 in Jenkins 2.102+
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-48939 PRQA Plugin is affected by JEP-200 in Jenkins 2.102+ Change By: Oleg Nenashev Priority: Minor Blocker 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-50460) Builds marked as failed - Dr Memory plugin (JEP-200)
Title: Message Title Oleg Nenashev commented on JENKINS-50460 Re: Builds marked as failed - Dr Memory plugin (JEP-200) Bue Petersen thanks for the update! Please feel free to ping me and Jesse Glick if any reviews are needed 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-50719) Declarative Pipeline: if one child of parallel failed, all next childs trigger failure in post
Title: Message Title
Sergii Kremko updated an issue
Jenkins / JENKINS-50719
Declarative Pipeline: if one child of parallel failed, all next childs trigger failure in post
Change By:
Sergii Kremko
If one of {{parallel}}'s child failed, in {{post}} of next childs will trigerred triger {{failure}} even this stages {{success}} Example:{code:java}pipeline {stages {stage('Paralel'){parallel {stage('One'){agent anysteps{ echo "child one"}post{ failure{ echo "FAIL ONE" }}}stage ('Two'){agent anysteps{ echo "child two" error('fail')}post{ failure{ echo "FAIL TWO" }}}stage ('Three'){agent anysteps{ echo "child three"}post{ failure{ echo "FAIL THREE" }}}stage ('Four'){agent anysteps{ echo "child four"}post{ failure{ echo "FAIL FOUR" }}}}post {failure {echo "FAIL PARALLEL"}}}}}{code} Output:{code :java }child onechild twochild threechild fourFAIL TWOFAIL THREEFAIL FOURFAIL PARALLELFinished: FAILURE{code}
Add Comment
[JIRA] (JENKINS-50719) Declarative Pipeline: if one child of parallel failed, all next childs trigger failure in post
Title: Message Title
Sergii Kremko created an issue
Jenkins / JENKINS-50719
Declarative Pipeline: if one child of parallel failed, all next childs trigger failure in post
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2018-04-10 15:44
Environment:
Jenkins ver. 2.111 pipeline-model-definition-plugin 1.2.7
Priority:
Major
Reporter:
Sergii Kremko
If one of parallel's child failed, in post of next childs will trigerred failure even this stages success Example:
pipeline {
stages {
stage('Paralel'){
parallel {
stage('One'){
agent any
steps{
echo "child one"
}
post{
failure{
echo "FAIL ONE"
}
}
}
stage ('Two'){
agent any
steps{
echo "child two"
error('fail')
}
post{
failure{
echo "FAIL TWO"
}
}
}
stage ('Three'){
agent any
steps{
echo "child three"
}
post{
failure{
echo "FAIL THREE"
}
}
}
stage
[JIRA] (JENKINS-50710) essentials plugin Jenkinsfile should trigger a full evergreen build with the change
Title: Message Title R. Tyler Croy assigned an issue to Unassigned For right now I don't think this is important for us to address. If we're putting enough logic into the "Essentials plugin" to where we risk introducing regressions in the plugin/client interaction then I believe we should be revisiting the model of putting code into the plugin in general. Going to leave this unassigned in the backlog to bring back in if we find it necessary. Jenkins / JENKINS-50710 essentials plugin Jenkinsfile should trigger a full evergreen build with the change Change By: R. Tyler Croy Assignee: R. Tyler Croy 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
[JIRA] (JENKINS-50642) intermittent JenkinsRule test timeout failure
Title: Message Title Mark Waite commented on JENKINS-50642 Re: intermittent JenkinsRule test timeout failure I've intentionally based it on 2.60.3 to bring it to Java 8 and still give as many users as possible the chance to update to the new plugin version when it releases, without requiring that they are on the latest Jenkins LTS. Once the JENKINS-48061 fix is complete, verified, and released, I'll merge the require-jdk-8 branch to master and deliver a beta release of git plugin 4.0.0. At that time, I'll re-evaluate the adoption numbers of various Jenkins releases so that I can follow the same pattern that Stephen Connolly is using with the credentials plugin. 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-50634) Triggered probe option
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50634 Re: Triggered probe option Code changed in jenkins User: Paul Allen Path: src/main/java/org/jenkinsci/plugins/p4/trigger/P4Hook.java src/test/java/org/jenkinsci/plugins/p4/DefaultEnvironment.java src/test/java/org/jenkinsci/plugins/p4/client/PollingTest.java http://jenkins-ci.org/commit/p4-plugin/3d037546b4230d57c5a3045182bde967aab38e23 Log: Skip probing disabled Jobs. Includes minor updates to Polling tests. JENKINS-50634 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-50525) Error When Provisioning Slave: mountPath: Required value
Title: Message Title Carlos Sanchez commented on JENKINS-50525 Re: Error When Provisioning Slave: mountPath: Required value do you have a minimal podTemplate example that shows the issue ? 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.
