[JIRA] (JENKINS-55884) Loading library fails with commit referenced by tag but not any branch
Title: Message Title
Daniel Blixt created an issue
Jenkins / JENKINS-55884
Loading library fails with commit referenced by tag but not any branch
Issue Type:
Bug
Assignee:
Mark Waite
Components:
bitbucket-branch-source-plugin, git-plugin
Created:
2019-01-31 07:35
Environment:
Jenkins 2.121.3 on RedHat Linux Git plugin 3.9.2 Git Client Plugin 2.7.6 Bitbucket Branch Source Plugin 2.4.0
Priority:
Major
Reporter:
Daniel Blixt
We have a library loaded dynamically in Pipeline script with library "mylib@8c8a4a95f3187b82112cc2eb8539ba470c1eebff" the sha1 in question is tagged on the remote, but not contained in any branch Jenkins fails to load the library: Loading library mylib@8c8a4a95f3187b82112cc2eb8539ba470c1eebff Attempting to resolve 8c8a4a95f3187b82112cc2eb8539ba470c1eebff from remote references... > git --version # timeout=10 using GIT_SSH to set credentials Jenkins Account > git ls-remote -h ssh://g...@our-bitbucket.com:7999/libProject/mylib.git # timeout=10 Could not find 8c8a4a95f3187b82112cc2eb8539ba470c1eebff in remote references. Pulling heads to local for deep search... > git rev-parse --is-inside-work-tree # timeout=10 Setting origin to ssh://g...@our-bitbucket.com:7999/libProject/mylib.git > git config remote.origin.url ssh://g...@our-bitbucket.com:7999/libProject/mylib.git # timeout=10 Fetching origin... Fetching upstream changes from origin > git --version # timeout=10 > git config --get remote.origin.url # timeout=10 using GIT_SSH to set credentials Jenkins Account > git fetch --tags --progress origin +refs/heads/:refs/remotes/origin/ > git rev-parse 8c8a4a95f3187b82112cc2eb8539ba470c1eebff^{commit} # timeout=10 > git branch -a -v --no-abbrev --contains 8c8a4a95f3187b82112cc2eb8539ba470c1eebff # timeout=10 Could not find a branch containing commit
[JIRA] (JENKINS-53200) Pipeline Replay Editor Displays Offset Cursor
Title: Message Title Randy Zulueta updated an issue Jenkins / JENKINS-53200 Pipeline Replay Editor Displays Offset Cursor Change By: Randy Zulueta Component/s: workflow-cps-plugin Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55883) vararg closure does not work in pipeline script
Title: Message Title
Di Shang created an issue
Jenkins / JENKINS-55883
vararg closure does not work in pipeline script
Issue Type:
Bug
Assignee:
vjuranek
Components:
groovy-plugin
Created:
2019-01-31 06:22
Environment:
Jenkins 2.150.1 Pipeline: Groovy plugin 2.62
Labels:
groovy
Priority:
Minor
Reporter:
Di Shang
Defining closure with vararg does not work in a pipeline script:
def fn = {String... args -> echo args.toString()}
fn('one', 'two', 'three')
Output:
one
Only workaround I can find is to not use closure:
def fn(String... args){echo args.toString()}
fn('one', 'two', 'three')
[JIRA] (JENKINS-39810) Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error
Title: Message Title Sarath Kumar commented on JENKINS-39810 Re: Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error Try to Update your Update Site URl with relevant version, say for Eg: https://updates.jenkins.io/2.150/update-center.json Once Update and Submit.Check the Check now button. Finally revert back to default url. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-39810) Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error
Title: Message Title Sarath Kumar updated an issue Jenkins / JENKINS-39810 Jenkins can't connect to any HTTP sites for plug-ins, complains about 403 error Change By: Sarath Kumar Attachment: image-2019-01-31-11-47-27-041.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55882) Expose "Publish Micro Focus tests result" in pipeline job
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-55882 Expose "Publish Micro Focus tests result" in pipeline job Issue Type: Improvement Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-01-31 05:55 Priority: Major Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55718) Support ALM15SSO/Make sure the login process could work in some problematic ALM env
Title: Message Title Roy Lu updated JENKINS-55718 Jenkins / JENKINS-55718 Support ALM15SSO/Make sure the login process could work in some problematic ALM env Change By: Roy Lu Status: In Review Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55862) jira-trigger-plugin logs not created
Title: Message Title Govind Chaudhari closed an issue as Not A Defect Logs are generated now Jenkins / JENKINS-55862 jira-trigger-plugin logs not created Change By: Govind Chaudhari Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55859) jira-trigger-plugin not triggering build after creating issue
Title: Message Title Govind Chaudhari updated an issue Jenkins / JENKINS-55859 jira-trigger-plugin not triggering build after creating issue Change By: Govind Chaudhari Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55859) jira-trigger-plugin not triggering build after creating issue
Title: Message Title Govind Chaudhari updated an issue Jenkins / JENKINS-55859 jira-trigger-plugin not triggering build after creating issue Change By: Govind Chaudhari Settings done as given in document NOTE- Webhook Facing Proxy Problem when comment is disabled as I want to get environment variables from Jira added but still build is triggered. Question:: Do I need to do setting for both Jenkins JOB and in Webhook ? Also log But when issue is created or updated , build is not getting enable for web hooks triggered . Error: Received Webhook callback with an invalid event type or a body without comment/changelog. Event type: jira:issue_created Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55859) jira-trigger-plugin not triggering build after creating issue
Title: Message Title Govind Chaudhari commented on JENKINS-55859 Re: jira-trigger-plugin not triggering build after creating issue Jan 31, 2019 10:35:54 AM java_util_logging_Logger$warning$1 call WARNING: Received Webhook callback with an invalid event type or a body without comment/changelog. Event type: jira:issue_created. Event body contains: [timestamp, webhookEvent, issue_event_type_name, user, issue]. Jan 31, 2019 10:43:24 AM java_util_logging_Logger$warning$1 call WARNING: Received Webhook callback with an invalid event type or a body without comment/changelog. Event type: jira:issue_created. Event body contains: [timestamp, webhookEvent, issue_event_type_name, user, issue]. Jan 31, 2019 10:44:10 AM java_util_logging_Logger$warning$1 call WARNING: Received Webhook callback with an invalid event type or a body without comment/changelog. Event type: jira:issue_created. Event body contains: [timestamp, webhookEvent, issue_event_type_name, user, issue]. Jan 31, 2019 10:45:23 AM java_util_logging_Logger$warning$1 call WARNING: Received Webhook callback with an invalid event type or a body without comment/changelog. Event type: jira:issue_created. Event body contains: [timestamp, webhookEvent, issue_event_type_name, user, issue]. Log data Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55794) Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN
Title: Message Title Liora Milbaum edited a comment on JENKINS-55794 Re: Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN Benonit Benoit Le Gall,Same problem with 2.162 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55794) Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN
Title: Message Title Liora Milbaum commented on JENKINS-55794 Re: Client error : ACCESS_REFUSED - Login was refused using authentication mechanism PLAIN Benonit Le Gall, Same problem with 2.162 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55881) Connection error With PTC Integrirty
Title: Message Title Cai Hao created an issue Jenkins / JENKINS-55881 Connection error With PTC Integrirty Issue Type: Bug Assignee: PTC ALM Attachments: jenkins.err.log Components: integrity-plugin Created: 2019-01-31 03:34 Environment: PTC Integrity 12.0 Jenkins 2.162 PTC Integrity Plugin 2.2 Priority: Critical Reporter: Cai Hao 警告: Error while serving http://localhost:8080/descriptorByName/hudson.scm.IntegritySCM/testConnection java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at
[JIRA] (JENKINS-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray assigned an issue to Subhransubala Routray Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Change By: Subhransubala Routray Assignee: Devin Nusbaum Subhransubala Routray Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray assigned an issue to Subhransubala Routray Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Change By: Subhransubala Routray Assignee: Subhransubala Routray Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray assigned an issue to Devin Nusbaum Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Change By: Subhransubala Routray Assignee: Subhransubala Routray Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55722) jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection
Title: Message Title Subhransubala Routray assigned an issue to Devin Nusbaum Jenkins / JENKINS-55722 jenkins.plugins.publish_over.BapPublisherException: Failed to connect and initialize SSH connection Change By: Subhransubala Routray Assignee: Subhransubala Routray Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55826) how to delete workspace forcely?
Title: Message Title Hokwang Lee commented on JENKINS-55826 Re: how to delete workspace forcely? Karl Wirth Both are checked. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55745) Migrate from analysis-core to warnings-ng
Title: Message Title Steve Springett commented on JENKINS-55745 Re: Migrate from analysis-core to warnings-ng I'm hoping to announce this when Dependency-Check 5.0 is GA (after it's milestones). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55745) Migrate from analysis-core to warnings-ng
Title: Message Title Steve Springett commented on JENKINS-55745 Re: Migrate from analysis-core to warnings-ng Yes, there are plans on doing this. I need to determine if I need to write a whole plugin (similar to how it's done now) or if I can simply contribute a parser. I've iterated with the author numerous times over the past 6 months and I think everything is in place for us to do a proper plugin, but we'll see. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55865) Ability to add additional tags
Title: Message Title Jie Shen commented on JENKINS-55865 Re: Ability to add additional tags I will check this, thanks for reporting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55880) Connection error With PTC Integrirty
Title: Message Title Cai Hao updated an issue Jenkins / JENKINS-55880 Connection error With PTC Integrirty Change By: Cai Hao Summary: Connection errot error With PTC Integrirty Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-47643) Allow [ci skip] to work for non-pull request changes
Title: Message Title Alex Simenduev commented on JENKINS-47643 Re: Allow [ci skip] to work for non-pull request changes Javier Delgado any updates on this. We are really looking forward to this feature... Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-42422) Add support for directory caching in pod jobs
Title: Message Title R C commented on JENKINS-42422 Re: Add support for directory caching in pod jobs [Comment almost lost thanks to JIRA] Right, there's that, too, but I would be OK if jobs were scheduled starting from the lowest index available. In our case, with a hot cache (which is what we'd like to achieve), an agent's longest run wouldn't be orders of magnitude worse than the average or best case. That is still a net win, even with the occasional inefficiency here and there, like job 1 being idle every once in a while. I came across someone else's [experience with stateful agents|https://hiya.com/blog/2017/10/02/kubernetes-base-jenkins-stateful-agents/.] We don't spend 20 minutes doing setup work like they do, but there are pipelines where installing dependencies takes up longer than the actual tests. Is the current design of the plugin too reliant on creating pods manually? The least invasive way might be for the scaling to be handled by a HorizontalPodAutoscaler (it should work with StatefulSets). Then the plugin would pick available slaves in alphabetical order. Is there much left to the Kubernetes plugin, at that point? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55880) Connection errot With PTC Integrirty
Title: Message Title Cai Hao created an issue Jenkins / JENKINS-55880 Connection errot With PTC Integrirty Issue Type: Bug Assignee: Cai Hao Attachments: configuration Integrity Test Connection.PNG, jenkins.err.log Components: integrity-plugin Created: 2019-01-31 01:20 Environment: Jenkins 2.155 PTC Integrity Server 12.0 Windows Priority: Blocker Reporter: Cai Hao Connection success use when I link PTC Integrity 11.0 with PTC Integrity Plugin; Connection error when linking PTC Integrity 12.0。 The following is the error message Error while serving http://192.168.6.100:8080/descriptorByName/hudson.scm.IntegritySCM/testConnection java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:282) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at
[JIRA] (JENKINS-50887) Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch
Title: Message Title Martin d'Anjou commented on JENKINS-50887 Re: Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch Torsten Kleiber, I am not a user of the multi-branch plugins, so I do not understand your requirement. Would you be able to explain it here or in this new proposal please? Feel free to add pictures or diagrams if that helps. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55879) Declarative SCM checkout not running on certain branches
Title: Message Title Travis Ball commented on JENKINS-55879 Re: Declarative SCM checkout not running on certain branches Hi Mark, Thanks for the quick reply. I switched the SCM provider to Git, but it looks like Pull Requests are not supported so I can't test my case that way. Just to be safe I tried merging my branch with the Jenkinsfile to the 'qa' branch and built that through the Git provider. It worked as expected, but this doesn't help my case. The job definition is not marked to skip the 'qa' branch. I must have checked this hundreds of times I checked capitalization of the "Jenkinsfile" and it is fine. Remember, this is building from a PR so the source is always the same. It just fails when the destination branch is 'qa'. I don't think the branch name exclusion has anything to do with this because the PR is discovered, it just doesn't checkout to the branch during the pipeline. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54209) Can't read file: Can't access the file
Title: Message Title Yan Liang commented on JENKINS-54209 Re: Can't read file: Can't access the file In my case, I updated the cppcheck from 1.21 to 1.24, then this issue happens. Jenkins 2.162. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50887) Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch
Title: Message Title Martin d'Anjou commented on JENKINS-50887 Re: Need a buildDiscarder in a pipeline, which deletes only failing jobs in master branch The project is being proposed for GSoC 2019 see https://docs.google.com/document/d/1W7YX4Y6PhIhraEQc9G-PKLSheJ6jXKgy8HmKVz1lCqs The proposal needs some work though. Oleg Nenashev I am not clear on how the build discarded is an extension point, is it because there is a drop down Strategy called "Log Rotation"? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55879) Declarative SCM checkout not running on certain branches
Title: Message Title
Mark Waite edited a comment on JENKINS-55879
Re: Declarative SCM checkout not running on certain branches
You might try copying the multibranch Pipeline job that you're using and then redefine the source code provider from Bitbucket Cloud or Bitbucket Server to Git. That may provide some additional diagnostics. You won't want to run with that long term, since there are additional features in the Bitbucket implementation that you will want, but it may help diagnose the issue with that branch.You might also try modifying the Jenkinsfile on the problem branch to [skip the default checkout|https://devops.stackexchange.com/questions/650/set-a-jenkins-job-to-not-to-clone-the-repo-in-scm/1074] and then perform a git checkout with the {{checkout scm}} step. That may provide further diagnostics as well.You might check that the job definition is not configured to ignore the qa branch (with a wildcard exclusion of that name).You might check that the Jenkinsfile is not stored in the repository with unexpected case (for example, was it written from a Windows machine or a Mac with the name "jenkinsfile" instead of "Jenkinsfile"). You might review the online help for the branch name exclusion field, just in case the values in that field need to be separated by something other than spaces or need to be expressed as a regular _expression_ rather than a list of space separated matching strings.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-55879) Declarative SCM checkout not running on certain branches
Title: Message Title Mark Waite commented on JENKINS-55879 Re: Declarative SCM checkout not running on certain branches You might try copying the multibranch Pipeline job that you're using and then redefine the source code provider from Bitbucket Cloud or Bitbucket Server to Git. That may provide some additional diagnostics. You won't want to run with that long term, since there are additional features in the Bitbucket implementation that you will want, but it may help diagnose the issue with that branch. You might also try modifying the Jenkinsfile on the problem branch to skip the default checkout and then perform a git checkout with the checkout scm step. That may provide further diagnostics as well. You might check that the job definition is not configured to ignore the qa branch (with a wildcard exclusion of that name). You might check that the Jenkinsfile is not stored in the repository with unexpected case (for example, was it written from a Windows machine or a Mac with the name "jenkinsfile" instead of "Jenkinsfile"). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55879) Declarative SCM checkout not running on certain branches
Title: Message Title
Travis Ball created an issue
Jenkins / JENKINS-55879
Declarative SCM checkout not running on certain branches
Issue Type:
Bug
Assignee:
Mark Waite
Attachments:
Screen Shot 2019-01-30 at 6.55.53 PM.png
Components:
bitbucket-branch-source-plugin, git-client-plugin
Created:
2019-01-31 00:07
Environment:
Jenkins version 2.150.2, Kubernetes plugin 1.14.3, Bitbucket Branch Source Plugin 2.4.0, Git client plugin 2.7.6
Labels:
bitbucket-branch-source-plugin git-client
Priority:
Major
Reporter:
Travis Ball
I am running a Multibranch Pipeline with the Bitbucket branch source plugin (my configuration is in the screenshot below). When creating a Pull Request in Bitbucket against the 'qa' branch the Declarative SCM Checkout stage does not do anything:
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
[Pipeline] }
When creating a Pull Request in Bitbucket against the 'uat' branch or the 'master' branch the pipeline everything checkouts out fine:
[JIRA] (JENKINS-55878) JEP-200
Title: Message Title Jackie Hammell created an issue Jenkins / JENKINS-55878 JEP-200 Issue Type: Bug Assignee: Unassigned Components: core Created: 2019-01-31 00:02 Environment: Linux RedHat 7 Priority: Major Reporter: Jackie Hammell Upgraded from 2.89.4 to 2.138.4 and I have a script that sets the Tool Location on Nodes and I am getting error Refusing to marshal ToolLocationNodeProperty$ToolLocation1_groovyProxy (see dump): java.lang.UnsupportedOperationException: Refusing to marshal ToolLocationNodeProperty$ToolLocation1_groovyProxy for security reasons; see https://jenkins.io/redirect/class-filter/ at hudson.util.XStream2$BlacklistedTypesConverter.marshal(XStream2.java:546) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:265) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:252) Caused: java.lang.RuntimeException: Failed to serialize hudson.tools.ToolLocationNodeProperty#locations for class hudson.tools.ToolLocationNodeProperty at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at
[JIRA] (JENKINS-48258) git client plugin occasionally fails with "text file busy" error
Title: Message Title Mark Waite commented on JENKINS-48258 Re: git client plugin occasionally fails with "text file busy" error Thanks very much joe ferr! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54950) offer default implementation for Descriptor#configure to use declarative data-binding
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-54950 offer default implementation for Descriptor#configure to use declarative data-binding Change By: Jesse Glick Labels: stalled-pr Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Eric Maras commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost I think I may have found the issue. I am not sure why my browser auto-fill thought the "Marker File" field is a username field, but it has been putting my username in that field every time I edited a configuration file. I am thinking this may be the case for others as well and could be an issue. How this was causing all branch pipelines to disappear for me I still do not understand. This issue could be different from the one this ticket is meant to address. Apologies if that is the case. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50328) Pipeline editor not working if Script Path is set
Title: Message Title Christopher Stelma commented on JENKINS-50328 Re: Pipeline editor not working if Script Path is set I couldn't find any reference to the path in the /blue/rest/ api responses, which makes some sense because the objects on that API all seem to be from the perspective of the pipeline, not from the job that defines the pipeline. i.e. I'm not sure where the path would go, maybe on the pipeline object, maybe on the scm object below that, but neither feels quite right. However, since this is the api used to fill the editor, it really should go somewhere. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55862) jira-trigger-plugin logs not created
Title: Message Title Wisen Tanasa commented on JENKINS-55862 Re: jira-trigger-plugin logs not created Would you be able to provide the following: Current behaviour Expected behaviour Steps to reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55220) Multibranch Pipeline jobs get randomly lost
Title: Message Title Eric Maras commented on JENKINS-55220 Re: Multibranch Pipeline jobs get randomly lost I am experiencing issues as well. I have been able to reproduce this. Every time I change a multibranch config file all of my branch pipelines seem to disappear. This was not happening every time before but now it is consistently happening. Deleting a lot of branches in Bitbucket seems to cause this issue for me as well. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55877) Jenkins Post-Build Action Not Updating to Associated Pull Request
Title: Message Title Barry Schneider created an issue Jenkins / JENKINS-55877 Jenkins Post-Build Action Not Updating to Associated Pull Request Issue Type: Bug Assignee: redsolo Components: tfs-plugin Created: 2019-01-30 21:22 Environment: Windows 2016 Jenkin v2.150.2 TFS Plugin 5.142.0 Priority: Minor Reporter: Barry Schneider TFS Plugin has been configured and test connectivity is successful. Jenkin builds are triggered by SCM polling. Build completes but TFS PR and work items are not update with build status. Jenkins logs report the following: SCM changes detected in nichd-dotnet-jenkins. Triggering #12 Jan 30, 2019 4:04:13 PM INFO hudson.model.Run execute nichd-dotnet-jenkins #12 main build action completed: SUCCESS Jan 30, 2019 4:04:13 PM INFO hudson.plugins.tfs.listeners.JenkinsRunListener onCompleted onCompleted: nichd-dotnet-jenkins #12 What can I do to get more logging to help identify the problem? What should the logs contain if updating TFS was working? Add Comment
[JIRA] (JENKINS-54186) No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults
Title: Message Title Nick Jones commented on JENKINS-54186 Re: No @DataBoundConstructor on any constructor of class jenkins.plugins.git.GitSCMSourceDefaults Sam Van Oort is there a PR where we can see your logspam fix in progress? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55876) Recursive submodule URLs are not synchronized when changed on a checkout
Title: Message Title Richard Whitehouse commented on JENKINS-55876 Re: Recursive submodule URLs are not synchronized when changed on a checkout git-plugin change is at https://github.com/jenkinsci/git-plugin/pull/671 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55876) Recursive submodule URLs are not synchronized when changed on a checkout
Title: Message Title Richard Whitehouse commented on JENKINS-55876 Re: Recursive submodule URLs are not synchronized when changed on a checkout git-client-plugin change is at https://github.com/jenkinsci/git-client-plugin/pull/405 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55592) GIT_COMMIT contains unknown value
Title: Message Title Mark Waite updated JENKINS-55592 Jenkins / JENKINS-55592 GIT_COMMIT contains unknown value Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55592) GIT_COMMIT contains unknown value
Title: Message Title Mark Waite closed an issue as Cannot Reproduce Jenkins / JENKINS-55592 GIT_COMMIT contains unknown value Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55592) GIT_COMMIT contains unknown value
Title: Message Title Mark Waite updated JENKINS-55592 Jenkins / JENKINS-55592 GIT_COMMIT contains unknown value Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55876) Recursive submodule URLs are not synchronized when changed on a checkout
Title: Message Title Richard Whitehouse started work on JENKINS-55876 Change By: Richard Whitehouse Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55875) Submodule update fails when the submodule isn't clean
Title: Message Title Richard Whitehouse commented on JENKINS-55875 Re: Submodule update fails when the submodule isn't clean https://github.com/jenkinsci/git-client-plugin/pull/404 has a fix for this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55876) Recursive submodule URLs are not synchronized when changed on a checkout
Title: Message Title Richard Whitehouse created an issue Jenkins / JENKINS-55876 Recursive submodule URLs are not synchronized when changed on a checkout Issue Type: Bug Assignee: Richard Whitehouse Components: git-client-plugin, git-plugin Created: 2019-01-30 20:10 Priority: Minor Reporter: Richard Whitehouse If a submodule itself has submodules, and the URL of those submodules changes, then the second submodule's URL will not be updated. This can cause checkout to fail, because the referenced commit may well not exist in the old submodule. This causes build failures, and either the workspace must be cleaned, or manual intervention must take place. Add Comment
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title
Mark Waite edited a comment on JENKINS-55836
Re: Unable to delete workspace due to locked git .pack file
Please [~carsten_hilber], please provide more details to duplicate the problem. A detailed set of steps which others can use to see the problem is preferred. If that is not possible, then please answer the following questions: * What is {{WS-CLEANUP}} and how is it used in that job?* Is the Jenkins job a Pipeline job or a Freestyle job?* If a Freestyle job, does the same problem exist if you modify the job definition to add the "Wipe out repository and force clone" additional behavior to the git configuration of the job?* If a Pipeline job, does the same problem exist if you use the {{deleteDir}} step?* Is the Jenkins job configured to use command line git or JGit to clone and checkout the workspace?* What git related options are included in the job definition?* Is there an anti-virus program running on the Windows computer? If so, is the problem still visible if virus scanning is disabled for the workspace directory?I can't duplicate the problem in [my experiment|https://github.com/MarkEWaite/docker-lfs/blob/lts-with-plugins/ref/jobs/Bugs-Individual/jobs/JENKINS-55836-windows-wipe-workspace/config.xml]. I don't recognize WS-CLEANUP, so I approximated it with "Wipe out repository and force clone".
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-55875) Submodule update fails when the submodule isn't clean
Title: Message Title
Richard Whitehouse updated an issue
Jenkins / JENKINS-55875
Submodule update fails when the submodule isn't clean
Change By:
Richard Whitehouse
Jenkins doesn't forcibly update submodules. This means that a checkout can fail with: {code:java}hudson.plugins.git.GitException: Command "git submodule update --init --recursive modules/gmock" returned status code 1:stdout: stderr: error: Your local changes to the following files would be overwritten by checkout:build-aux/config.guessbuild-aux/config.subgtest/build-aux/config.guessgtest/build-aux/config.subPlease, commit your changes or stash them before you can switch branches.AbortingUnable to checkout 'ec44c6c1675c25b9827aacd08c02433cccde7780' in submodule path 'modules/gmock'{code}Note, while JENKINS-22510 is relevant, and cleaning the checkout before checking out would resolve the problem, that's not a viable solution. Cleaning the checkout throws away all built files, which means the build is no longer incremental.Note, this means the behaviour makes Jenkins's behaviour for submodules doesn't match it's behaviour for the standard checkout (which is checked out with --force).
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop
[JIRA] (JENKINS-55875) Submodule update fails when the submodule isn't clean
Title: Message Title Richard Whitehouse created an issue Jenkins / JENKINS-55875 Submodule update fails when the submodule isn't clean Issue Type: Bug Assignee: Richard Whitehouse Components: git-client-plugin, git-plugin Created: 2019-01-30 20:00 Priority: Minor Reporter: Richard Whitehouse Jenkins doesn't forcibly update submodules. This means that a checkout can fail with: hudson.plugins.git.GitException: Command "git submodule update --init --recursive modules/gmock" returned status code 1: stdout: stderr: error: Your local changes to the following files would be overwritten by checkout: build-aux/config.guess build-aux/config.sub gtest/build-aux/config.guess gtest/build-aux/config.sub Please, commit your changes or stash them before you can switch branches. Aborting Unable to checkout 'ec44c6c1675c25b9827aacd08c02433cccde7780' in submodule path 'modules/gmock' Note, while JENKINS-22510 is relevant, and cleaning the checkout before checking out would resolve the problem, that's not a viable solution. Cleaning the checkout throws away all built files, which means the build is no longer incremental. Note, this behaviour makes Jenkins's behaviour for submodules match it's behaviour for the standard checkout (which is checked out with --force).
[JIRA] (JENKINS-55875) Submodule update fails when the submodule isn't clean
Title: Message Title Richard Whitehouse started work on JENKINS-55875 Change By: Richard Whitehouse Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55874) Adding credentials is awkward when one only has one domain
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-55874 Adding credentials is awkward when one only has one domain Issue Type: Improvement Assignee: Unassigned Attachments: image-2019-01-30-14-43-20-594.png Components: core Created: 2019-01-30 19:44 Priority: Minor Reporter: Josh Soref visit jenkins/credentials/ see lots of credentials – from the only store Jenkins – and from the only domain (global)). Look for "Add credentials" – can't find it. See "New Item" (this doesn't do the right thing™) See "New View" (this doesn't do the right thing™) In the left, See Credentials>System and click System See Global credentials (unrestricted) and still no way to Add credentials In the left, See Credentials>System and Add domain which is still not the right thing to click Click Global credentials (unrestricted) The bread crumbs for this are: Jenkins > Credentials > System > Global credentials (unrestricted) and there's finally a drop down for Add credentials
[JIRA] (JENKINS-54972) Build Changelogs don't expose SCM Name for Git repo
Title: Message Title Richard Whitehouse started work on JENKINS-54972 Change By: Richard Whitehouse Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54972) Build Changelogs don't expose SCM Name for Git repo
Title: Message Title Richard Whitehouse updated JENKINS-54972 Jenkins / JENKINS-54972 Build Changelogs don't expose SCM Name for Git repo Change By: Richard Whitehouse Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54972) Build Changelogs don't expose SCM Name for Git repo
Title: Message Title Richard Whitehouse commented on JENKINS-54972 Re: Build Changelogs don't expose SCM Name for Git repo This is fixed by https://github.com/jenkinsci/git-plugin/pull/642 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54126) Jenkinsfile not found in PR on GitHub
Title: Message Title Nelson Wolf commented on JENKINS-54126 Re: Jenkinsfile not found in PR on GitHub As a workaround, is it safe to nuke $jenkins_home/org.jenkinsci.plugins.github_branch_source.GitHubSCMProbe.cache while jenkins is running as a workaround? Would this potentially cause us to miss any events? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril updated an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Julia Mril Attachment: Reported warnings.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril updated an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Julia Mril Attachment: image_png_1_786×1_344_pixels.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril updated an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Julia Mril Attachment: Static_Analysis_Warnings__Jenkins_.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril updated an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Julia Mril Attachment: image-2019-01-30-10-35-09-643.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril updated an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Julia Mril Attachment: image_png_1_422×1_098_pixels.jpg Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title
Julia Mril updated an issue
Jenkins / JENKINS-55873
The Maven Enforcer plugin warnings are not reported correctly
Change By:
Julia Mril
I started to use the Enforce Maven plugin and added the following rules:{code:java}false {code}Now I can see a lot of warnings in the Jenkins console: {code:java} !image_png_1_786×1_344_pixels // 15:46:06 [WARNING] 15:46:06 Dependency convergence error for com . jpg! google.http-client:google-http-client-jackson2:1.22.0 paths to dependency are: 15:46:06 +-com.:web:165.0-SNAPSHOT 15:46:06 +-com.:notestore:165.0-SNAPSHOT15:46:06 +-com..service:gcs-lib:2.1-SNAPSHOT15:46:06 +-com.google.cloud:google-cloud-storage:1.3.115:46:06 +-com.google.cloud:google-cloud-core-http:1.3.115:46:06 +-com.google.http-client:google-http-client-jackson2:1.22.015:46:06 and15:46:06 +-com.:web:165.0-SNAPSHOT15:46:06 +-com.:notestore:165.0-SNAPSHOT15:46:06 +-com.google.cloud:google-cloud-spanner:0.21.1-beta15:46:06 +-com.google.api:gax-grpc:0.22.015:46:06 +-com.google.auth:google-auth-library-oauth2-http:0.7.015:46:06 +-com.google.http-client:google-http-client-jackson2:1.19.015:46:06 and15:46:06 +-com.:web:165.0-SNAPSHOT15:46:06 +-com.google.api-client:google-api-client:1.22.015:46:06 +-com.google.http-client:google-http-client-jackson2:1.22.015:46:06 15:46:06 [WARNING] 15:46:06 Dependency convergence error for com.google.code.gson:gson:2.2.1 paths to dependency are:15:46:06 +-com.:web:165.0-SNAPSHOT15:46:06 +-com.:notestore:165.0-SNAPSHOT15:46:06 +-com.:telesign:1.115:46:06 +-com.google.code.gson:gson:2.2.1{code} but in the plugin report i can see: ! Static_Analysis_Warnings__Jenkins_ Plugin Console . jpg png|thumbnail ! ! image_png_1_422×1_098_pixels Reported warnings . jpg png|thumbnail ! It looks like the plugin reported just the 1st warning.Could you, please, take a look at it?
Add Comment
[JIRA] (JENKINS-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril updated an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Julia Mril Attachment: Reported warnings.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril updated an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Julia Mril Attachment: Plugin Console.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril updated an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Change By: Julia Mril Attachment: Reported warnings.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55873) The Maven Enforcer plugin warnings are not reported correctly
Title: Message Title Julia Mril created an issue Jenkins / JENKINS-55873 The Maven Enforcer plugin warnings are not reported correctly Issue Type: Bug Assignee: Ulli Hafner Attachments: image-2019-01-30-10-35-09-643.png, image_png_1_422×1_098_pixels.jpg, image_png_1_786×1_344_pixels.jpg, Static_Analysis_Warnings__Jenkins_.jpg Components: warnings-ng-plugin Created: 2019-01-30 18:47 Environment: Jenkins 2.150.2, warning-ng 2.1.1 Priority: Major Reporter: Julia Mril I started to use the Enforce Maven plugin and added the following rules: false Now I can see a lot of warnings in the Jenkins console: but in the plugin report i can see: It looks like the plugin reported just the 1st warning. Could you, please, take a look at it?
[JIRA] (JENKINS-55872) Have a Continus Integration Server Protocol for build tools?
Title: Message Title Robin Björklin created an issue Jenkins / JENKINS-55872 Have a Continus Integration Server Protocol for build tools? Issue Type: New Feature Assignee: Unassigned Components: pipeline Created: 2019-01-30 18:41 Priority: Minor Reporter: Robin Björklin Just throwing the idea out there but would it make sense for Jenkins and other CI servers to have a common protocol which build tools such as maven or go build can implement support for in the same vein as LSP? https://en.wikipedia.org/wiki/Language_Server_Protocol Feel free to close this suggestion if it is completely off the walls! Add Comment
[JIRA] (JENKINS-55871) Update without losing plugins settings
Title: Message Title Fernando Felipe created an issue Jenkins / JENKINS-55871 Update without losing plugins settings Issue Type: Bug Assignee: Patrik Boström Components: branch-api-plugin, delivery-pipeline-plugin, environment-manager-tools-plugin, job-dsl-plugin, pipeline, ssh-slaves-plugin Created: 2019-01-30 17:58 Environment: I currently have a version of Jenkins see. 2.85), I am using centos, I would like to check what is the best way to not lose plugins settings, since I need updates as well. Would you help me ? SO: Centos7 Newer Version : 2.162 Labels: plugin security jenkins Priority: Critical Reporter: Fernando Felipe I currently have a version of Jenkins see. 2.85), I am using centos, I would like to check what is the best way to not lose plugins settings, since I need updates as well. Would you help me ? SO: Centos7 Newer Version : 2.162
[JIRA] (JENKINS-53960) Mac agents fail to connect on vSphere plugin
Title: Message Title DhruvaKumar Jonnagaddala commented on JENKINS-53960 Re: Mac agents fail to connect on vSphere plugin that was good suggestion pjdarton. After installing VMWare tools, VSphere plugin was able to provision the Mac VM and join them back to master. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55870) mercurial-scm hard codes --clean in updates
Title: Message Title Sanjay Bhandari created an issue Jenkins / JENKINS-55870 mercurial-scm hard codes --clean in updates Issue Type: Bug Assignee: Unassigned Components: mercurial-plugin Created: 2019-01-30 17:55 Priority: Major Reporter: Sanjay Bhandari See line: link Note that –clean option for update is hardcoded. Instead, it should respect the clean option that was passed in (see line: link). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-55818) Extend REST API to enable navigation by modules, issue types, priority etc.
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-55818 Extend REST API to enable navigation by modules, issue types, priority etc. Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55818) Extend REST API to enable navigation by modules, issue types, priority etc.
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55818 Extend REST API to enable navigation by modules, issue types, priority etc. Change By: Ulli Hafner Labels: help-wanted Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55838) Some MsBuild Compiler Warnings not reported
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-55838 Some MsBuild Compiler Warnings not reported Change By: Ulli Hafner Labels: help-wanted newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55838) Some MsBuild Compiler Warnings not reported
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-55838 Some MsBuild Compiler Warnings not reported Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55418) Pipeline Syntax generator not present
Title: Message Title Ulli Hafner resolved as Not A Defect Jenkins / JENKINS-55418 Pipeline Syntax generator not present Change By: Ulli Hafner Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55418) Pipeline Syntax generator not present
Title: Message Title Ulli Hafner commented on JENKINS-55418 Re: Pipeline Syntax generator not present Yes, everything is included in recordIssues. You can split this step into scanForIssues and publishIssues, but that is rarely required. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55840) Doxygen parser not fully compatible with warnings-ng-plugin
Title: Message Title Ulli Hafner commented on JENKINS-55840 Re: Doxygen parser not fully compatible with warnings-ng-plugin Can you please attach the generated doxygen report as well? I don‘t use doxygen on my own, so it’s hard to see what is broken. Btw: the parser has some other severe problems (exceptions in regexp engine of JDK) and should be rewritten from scratch using a newer api. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52966) Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError
Title: Message Title Erik Miller commented on JENKINS-52966 Re: Two sequential stages in a parallel stage in a declarative pipeline making use of the same agent can cause a StackOverflowError Happening for me as well. I have the most up to date Jenkins and all plugins. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50317) Pipeline job is failed with java.lang.StackOverflowError
Title: Message Title Erik Miller commented on JENKINS-50317 Re: Pipeline job is failed with java.lang.StackOverflowError Happening for me as well. Update? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55846) No issues found when parsing Error-Prone output from console log during gradle build
Title: Message Title Ulli Hafner commented on JENKINS-55846 Re: No issues found when parsing Error-Prone output from console log during gradle build Seems that I accidentally removed the parser while I added support for error prone in maven. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55827) Git Plugin 3.9.2 ignores agent local tool definition
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-55827 Git Plugin 3.9.2 ignores agent local tool definition Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55827) Git Plugin 3.9.2 ignores agent local tool definition
Title: Message Title Mark Waite updated JENKINS-55827 Jenkins / JENKINS-55827 Git Plugin 3.9.2 ignores agent local tool definition Change By: Mark Waite Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55827) Git Plugin 3.9.2 ignores agent local tool definition
Title: Message Title Mark Waite updated JENKINS-55827 Fixed in git plugin 3.9.3 released January 30, 2019. Sorry about the regression! Jenkins / JENKINS-55827 Git Plugin 3.9.2 ignores agent local tool definition Change By: Mark Waite Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes
Title: Message Title German Pineda commented on JENKINS-55517 Re: Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes This is starting to become a bigger issue for us since keeping the Bitbucket Branch Source plugin at version 2.2.12 is now causing dependency issues with Blue Ocean (see picture below): For anyone else experiencing this problem, you might need to hold back on updating Blue Ocean as well until this issue is fixed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55517) Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes
Title: Message Title German Pineda updated an issue Jenkins / JENKINS-55517 Bitbucket Mercurial Multibranch Pipeline: Scan triggers all builds regardless of any changes Change By: German Pineda Attachment: image-2019-01-30-08-34-53-641.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-52754) GitBranchSource does not consult with GitTool's node-specific ToolInstallers when running on master
Title: Message Title Alex Earl commented on JENKINS-52754 Re: GitBranchSource does not consult with GitTool's node-specific ToolInstallers when running on master I see this was already reported and reverted (https://github.com/jenkinsci/git-plugin/commit/6d2b42cc676c8baa8c624625f6e0235cd63dd5f3) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title Nisarg Shah commented on JENKINS-55738 Re: NodeMonitor out of disk space message is wrong for master Baptiste Mathus Okay, great I had a thought of copying and pasting big files and manually create an out of disk event. But actually after this I have a doubt that how to run jenkins code on local and test that fixed part? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50586) SSH support
Title: Message Title Stefano Galarraga started work on JENKINS-50586 Change By: Stefano Galarraga Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-54214) NPE when no credentials provided on Gerrit SCM URL for Declarative Pipeline
Title: Message Title Stefano Galarraga assigned an issue to Stefano Galarraga Jenkins / JENKINS-54214 NPE when no credentials provided on Gerrit SCM URL for Declarative Pipeline Change By: Stefano Galarraga Assignee: lucamilanesio Stefano Galarraga Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-50586) SSH support
Title: Message Title Stefano Galarraga assigned an issue to Stefano Galarraga Jenkins / JENKINS-50586 SSH support Change By: Stefano Galarraga Assignee: lucamilanesio Stefano Galarraga Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55713) No agents created when using google compute engine and missing instance template entry
Title: Message Title
sowmith koppula commented on JENKINS-55713
Re: No agents created when using google compute engine and missing instance template entry
400 Bad Request { "code" : 400, "errors" : [ { "domain" : "global", "message" : "Invalid value for field 'sourceInstanceTemplate': ''. The URL is malformed.", "reason" : "invalid" } ], "message" : "Invalid value for field 'sourceInstanceTemplate': ''. The URL is malformed." } we ran into same issue today morning.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-52754) GitBranchSource does not consult with GitTool's node-specific ToolInstallers when running on master
Title: Message Title Alex Earl commented on JENKINS-52754 Re: GitBranchSource does not consult with GitTool's node-specific ToolInstallers when running on master There is an issue with this PR, please see my comment here https://github.com/jenkinsci/git-plugin/commit/77967dbb349c8d1df02e4a21e0ff9d9e107e94ee#r32120075. Basically, if you don't pass along builtOn, then the default git will be used. This affects git plugin 3.9.2 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55788) Error when configuring Kubernetes Plugin v1.14.3
Title: Message Title Ravi Sharma commented on JENKINS-55788 Re: Error when configuring Kubernetes Plugin v1.14.3 I am also facing the same issue. My jenkins master runs on K8s and trying the agent provisioning on same cluster and namespace. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop 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-55738) NodeMonitor out of disk space message is wrong for master
Title: Message Title
Baptiste Mathus edited a comment on JENKINS-55738
Re: NodeMonitor out of disk space message is wrong for master
[~nisarg14] are you on Windows or Linux?On Linux, the usual way for this is simply to use {{fallocate}} or {{dd}}, see https://stackoverflow.com/a/5688625/345845.On Windows, the simplest low-tech way I did that in the past is the following:* find a big enough file, or very big if you have a lot of free disk space* copy paste it as many times as needed, even using the UI and Ctrl-C Ctrl-V should be quick enough** i.e. if you have 10 GB of free disk space, find a big file, like 1GB, and copy-paste it like nine of or ten timesOr maybe try https://blogs.msdn.microsoft.com/oldnewthing/20150710-00/?p=45171 but didn't try it myself.HTH
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-40723) Built Dockerfile images are never removed
Title: Message Title
Allan Lewis commented on JENKINS-40723
Re: Built Dockerfile images are never removed
Hrm. So for a GitHub Organisation PR, the $JOB_NAME will be github-org/project/PR-XX.
I'm not using a GitHub org, so I'm not sure about that. My case is using a manually-configured Git URL.
First of all, that's an invalid tag name. But let's assume we can make it sane by removing the {{/}}s.
I'm not using the job name as a tag, I'm using it as the image name, and image names can contain slashes.
Granted when (the locally written script for) garbage cleanup removes that PR-XX image because PR-XX is closed, the master branch build will build a new (identical) docker image to replace the just removed one. But that's an extra build that shouldn't be necessary.
Doesn't deleting all of the Jenkins produced hashy type tags mean that Jenkins won't be able to find an image to re-use for a future run of a job where the Dockerfile has not changed?
No, because when master is built, it will build the image again - cached if it's on the same node or if one implements push-pull with a registry - and tag it as /master. If we then prune the tag from the branch, we'll still have the image as it will be tagged for master. I'm not saying my solution will work for everyone, I just posted it in case it was useful for others.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-40723) Built Dockerfile images are never removed
Title: Message Title
Attila Szeremi edited a comment on JENKINS-40723
Re: Built Dockerfile images are never removed
{quote}[~brianjmurrell]Doesn't deleting all of the Jenkins produced hashy type tags mean that Jenkins won't be able to find an image to re-use for a future run of a job where the Dockerfile has not changed?{quote}First of all, Jenkins doesn't even do that. If a build would be rerun, it would just build the Docker image again. Secondly, it's not like Jenkins does any kind of caching for non-Docker agents (like caching the node_modules/ generated from an npm install). And besides, Docker already has decent caching built into it; any step in the Dockerfile where the involved files did not change since last time, Docker automatically just re-uses the cached layer; so no additional help from Jenkins is needed.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop 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-40723) Built Dockerfile images are never removed
Title: Message Title Attila Szeremi commented on JENKINS-40723 Re: Built Dockerfile images are never removed Brian J Murrell Doesn't deleting all of the Jenkins produced hashy type tags mean that Jenkins won't be able to find an image to re-use for a future run of a job where the Dockerfile has not changed? First of all, Jenkins doesn't even do that. If a build would be rerun, it would just build the Docker image again. Secondly, it's not like Jenkins does any kind of caching for non-Docker agents (like caching the node_modules/ generated from an npm install). And besides, Docker already has decent caching built into it; any step in the Dockerfile where the involved files did not change since last time, Docker automatically just re-uses the cached layer; so no additional help from Jenkins is needed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
